GarlicOS / bootloader_anbernic_rg35xxplus

Other
175 stars 5 forks source link

RG35XXH can't boot GarlicOS. #7

Open icemeowzhi opened 4 months ago

icemeowzhi commented 4 months ago

Symptom: I was followed the instruction strictly. But when I press the power button, it just shows the Anbernic logo for a few seconds and turns off.

I tried to find some information on the Internet, but all of them are 35XX+, not 35XXH.

I tried to solve the problem by doing:

Sadly, none of them work.

I also made several tests:

I would be grateful if someone can tell me how to fix it. Sorry for my bad grammar, I'm not a native English speaker. :)

File status: TF1: stock os and bootloader ( dmenu.bin, device-resources/deviceinfo ) TF2: init script and armhf rootfs ( boot/init, boot/rootfs.f2fs )

marciniuk commented 3 months ago

Don't copy the init file, just download it. Windows Notepad cannot create a working init. This is enough for the system to start.

Use e.g. Free Download Manager - paste the download link https://raw.githubusercontent.com/GarlicOS/init_template/main/init

Then you can say thank you ;P

ndguardian commented 1 month ago

Hey, so I was having some issues with these and I was following instructions to the letter. Eventually I added a couple additional steps, though I'm not quite sure what was the secret sauce to finally getting it to work. These steps seem to be Mac-reliant (maybe Linux works too), though maybe there are Windows options available to do this too.

First, I forcefully switched my TF2 to use MBR partition scheme instead of GUID. On Mac, I did this by opening disk utility > selecting my SD card > erase. Then I set the partition scheme from GUID to MBR, and partition type to ExFAT.

I also did the same on my TF1 SD card, but I don't think that's necessary since reflashing it with Garlic seems to switch it back to GUID anyway. Once I reflashed it on my Mac though, I saw two partitions instead of one that I saw on my Windows PC. One was named something like "NONAME" and it showed the typical folders I normally would see on my Windows machine...bios, saves, etc. There was another one though that seemed like it had some boot-specific and battery-specific files called "VOLUMEN". Just to be safe, I copied the bootloader files onto the root directory in both partitions.

I also created the boot folder on TF2, copied over the init file and rootfs file, and after doing all that, I was finally able to boot into Garlic.

Hopefully this helps someone out!