AIGO EROS Q Version 2.2 HW4 and restoring my rootfs and bootloader manually

[disrel]

Hey! I just got one of these.

It seems that the AIGO EROS Q variants have moved on to version 2.2. Not sure what hardware revision it is, but some person on Reddit claims hw4 files work.

https://www.reddit.com/r/rockbox/comments/1i4ceya/comment/md1tinu

EDIT: Confirmed on my end, the hw4 files indeed work for EROS Q v2.2 (jztool method on Windows 11 64-Bit). I backed up the original bootloader, please let me know how I can contribute to update the main rockbox page

Good to hear, if you want to go ahead and try the standard hw4 update file just to make sure, it's here: https://download.rockbox.org/bootloader/aigo/native/erosqnative-hw4-erosq_2024.upt. It will either work fine or it will reject it because the device name is different. You just need to put it on the SD card with filename "update.upt" and run the recovery mode from the bootloader.

If you also want to dump the entire flash and share that it would good too. I'll stash it away in case it's needed at some point. Lately it seems like we've been getting fewer and fewer stock update files from the manufacturer.

Hey! I dumped the flash after I installed the native port. Hope that doesn't ruin things?

I ended up restoring the original bootloader so I get an untampered nanddump. The SHA256 of the flash.img - 8999ea585bc700b64f5b12ab85d204c3fcf415e08f8149057856546df5119fbc
Also I was able to analyze the it using https://github.com/nlitsme/ubidump with block size 0x20000

https://drive.proton.me/urls/03N9J2RR1C#egKE3fHI5iAr

Also to confirm, hw4 upt files for the native port work for EROS Q v2.2! For those who get the new players, hope this helped

[dconrad]

Hey! I just got one of these.

It seems that the AIGO EROS Q variants have moved on to version 2.2. Not sure what hardware revision it is, but some person on Reddit claims hw4 files work.

https://www.reddit.com/r/rockbox/comments/1i4ceya/comment/md1tinu

EDIT: Confirmed on my end, the hw4 files indeed work for EROS Q v2.2 (jztool method on Windows 11 64-Bit). I backed up the original bootloader, please let me know how I can contribute to update the main rockbox page

Good to hear, if you want to go ahead and try the standard hw4 update file just to make sure, it's here: https://download.rockbox.org/bootloader/aigo/native/erosqnative-hw4-erosq_2024.upt. It will either work fine or it will reject it because the device name is different. You just need to put it on the SD card with filename "update.upt" and run the recovery mode from the bootloader.

If you also want to dump the entire flash and share that it would good too. I'll stash it away in case it's needed at some point. Lately it seems like we've been getting fewer and fewer stock update files from the manufacturer.

Hey! I dumped the flash after I installed the native port. Hope that doesn't ruin things?

I ended up restoring the original bootloader so I get an untampered nanddump. The SHA256 of the flash.img - 8999ea585bc700b64f5b12ab85d204c3fcf415e08f8149057856546df5119fbc
Also I was able to analyze the it using https://github.com/nlitsme/ubidump with block size 0x20000

https://drive.proton.me/urls/03N9J2RR1C#egKE3fHI5iAr

Also to confirm, hw4 upt files for the native port work for EROS Q v2.2! For those who get the new players, hope this helped

Excellent, thank you! I've got it stashed away. I think we can make our own "stock" updater if we really need to for some reason.

[disrel]

Hey! I just got one of these.

It seems that the AIGO EROS Q variants have moved on to version 2.2. Not sure what hardware revision it is, but some person on Reddit claims hw4 files work.

https://www.reddit.com/r/rockbox/comments/1i4ceya/comment/md1tinu

EDIT: Confirmed on my end, the hw4 files indeed work for EROS Q v2.2 (jztool method on Windows 11 64-Bit). I backed up the original bootloader, please let me know how I can contribute to update the main rockbox page

Good to hear, if you want to go ahead and try the standard hw4 update file just to make sure, it's here: https://download.rockbox.org/bootloader/aigo/native/erosqnative-hw4-erosq_2024.upt. It will either work fine or it will reject it because the device name is different. You just need to put it on the SD card with filename "update.upt" and run the recovery mode from the bootloader.

If you also want to dump the entire flash and share that it would good too. I'll stash it away in case it's needed at some point. Lately it seems like we've been getting fewer and fewer stock update files from the manufacturer.

Hey! I dumped the flash after I installed the native port. Hope that doesn't ruin things?

I ended up restoring the original bootloader so I get an untampered nanddump. The SHA256 of the flash.img - 8999ea585bc700b64f5b12ab85d204c3fcf415e08f8149057856546df5119fbc
Also I was able to analyze the it using https://github.com/nlitsme/ubidump with block size 0x20000

https://drive.proton.me/urls/03N9J2RR1C#egKE3fHI5iAr

Also to confirm, hw4 upt files for the native port work for EROS Q v2.2! For those who get the new players, hope this helped

Excellent, thank you! I've got it stashed away. I think we can make our own "stock" updater if we really need to for some reason.

What would that consist? If you can give me some pointers I could get started on some things. I was looking at tools/hiby_patcher.pl to see if I could generate a hosted port for mine (for development).

[dconrad]

Hey! I just got one of these.

It seems that the AIGO EROS Q variants have moved on to version 2.2. Not sure what hardware revision it is, but some person on Reddit claims hw4 files work.

https://www.reddit.com/r/rockbox/comments/1i4ceya/comment/md1tinu

EDIT: Confirmed on my end, the hw4 files indeed work for EROS Q v2.2 (jztool method on Windows 11 64-Bit). I backed up the original bootloader, please let me know how I can contribute to update the main rockbox page

Good to hear, if you want to go ahead and try the standard hw4 update file just to make sure, it's here: https://download.rockbox.org/bootloader/aigo/native/erosqnative-hw4-erosq_2024.upt. It will either work fine or it will reject it because the device name is different. You just need to put it on the SD card with filename "update.upt" and run the recovery mode from the bootloader.

If you also want to dump the entire flash and share that it would good too. I'll stash it away in case it's needed at some point. Lately it seems like we've been getting fewer and fewer stock update files from the manufacturer.

Hey! I dumped the flash after I installed the native port. Hope that doesn't ruin things?

I ended up restoring the original bootloader so I get an untampered nanddump. The SHA256 of the flash.img - 8999ea585bc700b64f5b12ab85d204c3fcf415e08f8149057856546df5119fbc
Also I was able to analyze the it using https://github.com/nlitsme/ubidump with block size 0x20000

https://drive.proton.me/urls/03N9J2RR1C#egKE3fHI5iAr

Also to confirm, hw4 upt files for the native port work for EROS Q v2.2! For those who get the new players, hope this helped

Excellent, thank you! I've got it stashed away. I think we can make our own "stock" updater if we really need to for some reason.

What would that consist? If you can give me some pointers I could get started on some things. I was looking at tools/hiby_patcher.pl to see if I could generate a hosted port for mine (for development).

I don't feel confident enough on it to give instructions, but I think it would involve pulling out the various separate parts of the image (bootloader, system, ...others...?) and making them their own files, and then compiling a similar iso image like one of the stock updater files. Fortunately my understanding is that each part of the image has a fixed offset in memory. There's a manifest file that needs to have all the correct names and md5 hashes, etc. I hope that helps? Open up one of the stock update files and you'll see what I mean - You can simply rename it to "update.iso" and open it that way.

I will say though, I've messed with already-compiled update files and made our own bootloader-only update files, but writing to anything other than the bootloader is beyond my wheelhouse so you may wander a bit into uncharted territory, just so you know.

[disrel]

Hey! I just got one of these.

It seems that the AIGO EROS Q variants have moved on to version 2.2. Not sure what hardware revision it is, but some person on Reddit claims hw4 files work.

https://www.reddit.com/r/rockbox/comments/1i4ceya/comment/md1tinu

EDIT: Confirmed on my end, the hw4 files indeed work for EROS Q v2.2 (jztool method on Windows 11 64-Bit). I backed up the original bootloader, please let me know how I can contribute to update the main rockbox page

Good to hear, if you want to go ahead and try the standard hw4 update file just to make sure, it's here: https://download.rockbox.org/bootloader/aigo/native/erosqnative-hw4-erosq_2024.upt. It will either work fine or it will reject it because the device name is different. You just need to put it on the SD card with filename "update.upt" and run the recovery mode from the bootloader.

If you also want to dump the entire flash and share that it would good too. I'll stash it away in case it's needed at some point. Lately it seems like we've been getting fewer and fewer stock update files from the manufacturer.

Hey! I dumped the flash after I installed the native port. Hope that doesn't ruin things?

I ended up restoring the original bootloader so I get an untampered nanddump. The SHA256 of the flash.img - 8999ea585bc700b64f5b12ab85d204c3fcf415e08f8149057856546df5119fbc
Also I was able to analyze the it using https://github.com/nlitsme/ubidump with block size 0x20000

https://drive.proton.me/urls/03N9J2RR1C#egKE3fHI5iAr

Also to confirm, hw4 upt files for the native port work for EROS Q v2.2! For those who get the new players, hope this helped

Excellent, thank you! I've got it stashed away. I think we can make our own "stock" updater if we really need to for some reason.

What would that consist? If you can give me some pointers I could get started on some things. I was looking at tools/hiby_patcher.pl to see if I could generate a hosted port for mine (for development).

I don't feel confident enough on it to give instructions, but I think it would involve pulling out the various separate parts of the image (bootloader, system, ...others...?) and making them their own files, and then compiling a similar iso image like one of the stock updater files. Fortunately my understanding is that each part of the image has a fixed offset in memory. There's a manifest file that needs to have all the correct names and md5 hashes, etc. I hope that helps? Open up one of the stock update files and you'll see what I mean - You can simply rename it to "update.iso" and open it that way.

I will say though, I've messed with already-compiled update files and made our own bootloader-only update files, but writing to anything other than the bootloader is beyond my wheelhouse so you may wander a bit into uncharted territory, just so you know.

Well I did compare the files and here are my findings. I used Surfans F20 v3.4 (hw4) as my base.

The UBOOT.BIN has changed, I haven't bindiffed it but that's interesting.
The UIMAGE.BIN remains the same.

I am working on SYSTEM.UBI. I just need to figure out the proper offsets so I can carve the "payload" out of my nandflash. I am using tools/hiby_patcher.pl as my base to figure out how the update files work (the hibyos_nativepatcher and agptek_rocker have been helpful as well).

I will report more soon. It's an uphill battle!

[disrel]

Haha I think this deserves a post of it's own.

So guess who fucked up their rootfs and bootloader while they were messing around (me lol)

From my flash.img, you can carve out the uboot.img, uimage.bin using these commands:

Code: [Select]

dd status=progress conv=notrunc,noerror,sync if=flash.img of=uimage.bin bs=1 skip=0 count=353924
dd status=progress conv=notrunc,noerror,sync if=flash.img of=uimage.bin bs=1 skip=3145728 count=2397712

For system.ubi

Code: [Select]

ubireader_extract_files -k flash.img
cd ubifs-root/0
mkfs.ubifs -e "124KiB" -c "1024" -m "2048" -j "8192KiB" -U -v -o "SYSTEM.UBI" -r "rootfs"

I put them all in a directory called 'update', salvaged the manifest from Surfans F20 v3.4 Hosted Port and added the bootloader to the manifest. Changed md5 hashes ofc.

Code: [Select]

mkisofs -volid "CDROM" -o update.upt update

and this is how I "unbricked" my OF for EROS Q v2.2. Here is the update file - https://drive.proton.me/urls/7CNTWMQ904#Yb1mlhIROA7i

[rednakes]

Haha I think this deserves a post of it's own.

So guess who fucked up their rootfs and bootloader while they were messing around (me lol)

From my flash.img, you can carve out the uboot.img, uimage.bin using these commands:

Code: [Select]

dd status=progress conv=notrunc,noerror,sync if=flash.img of=uimage.bin bs=1 skip=0 count=353924
dd status=progress conv=notrunc,noerror,sync if=flash.img of=uimage.bin bs=1 skip=3145728 count=2397712

For system.ubi

Code: [Select]

ubireader_extract_files -k flash.img
cd ubifs-root/0
mkfs.ubifs -e "124KiB" -c "1024" -m "2048" -j "8192KiB" -U -v -o "SYSTEM.UBI" -r "rootfs"

I put them all in a directory called 'update', salvaged the manifest from Surfans F20 v3.4 Hosted Port and added the bootloader to the manifest. Changed md5 hashes ofc.

Code: [Select]

mkisofs -volid "CDROM" -o update.upt update

and this is how I "unbricked" my OF for EROS Q v2.2. Here is the update file - https://drive.proton.me/urls/7CNTWMQ904#Yb1mlhIROA7i

Nice!  I need help doing the same for my hw4 Hifi Walker H2 V2.0 (same device, just re-branded).   Thanks for these instructions..  I think you made a typo in your first command - it should be uboot.bin, not uimage.bin?

The only problem I have is that I don't have Linux, I'm using a Mac so I don't have access to "mkfs.ubifs".  Any chance you can help me out?

I have a flash.img and the stock boot loader.



EDIT:  Never mind, I did it!  Thanks for the instructions!  I had to install an Ubuntu Server VM using UTM.  I used the flash.img for the H2 V2.0.

I also used your UPDATE.TXT and updated the MD5 sums.