AIGO EROS Q / AIGO EROS K / IRULU Surfans F20 / AGPTek H3 / HIFI WALKER H2

[emilyinspace]

Thanks for both responses :-) I will continue using the hosted port on 1.8 for a while. Is it possible to move to the native port later on or am I "stuck" with the hosted?

[dconrad]

Thanks for both responses :-) I will continue using the hosted port on 1.8 for a while. Is it possible to move to the native port later on or am I "stuck" with the hosted?

You can definitely switch later, you're not locked in at all.

[emilyinspace]

can I ask another thing; does the hosted port alter the original device bootloader? or this happens only with the native port. thank you!

[dconrad]

My understanding is the hosted port doesn't alter the original bootloader - it just selects which application gets started after the OS is booted. If you really wanted, you could have both installed at the same time! I don't know why, but...

[NO_ob]

been looking at these they are cool, do they do usb-c models? i saw one on amazon but looks like micro usb

[dconrad]

been looking at these they are cool, do they do usb-c models? i saw one on amazon but looks like micro usb

Yes, I know for a fact that at least the hifiwalker variant has USB-C (I'm looking at it on my desk right now). They don't seem to have updated the product pictures since the initial release.

[hannahmuffins]

hi everyone, just got an eros Q and was hoping to put rockbox on it. it says its firmware veersion 1.9 but i couldnt find a patched firmware on here. would it be safe to use the 2.0 patched firmware? or is there a way i can dump the 1.9 firmware so it can be patched? thanks!

[dconrad]

hi everyone, just got an eros Q and was hoping to put rockbox on it. it says its firmware veersion 1.9 but i couldnt find a patched firmware on here. would it be safe to use the 2.0 patched firmware? or is there a way i can dump the 1.9 firmware so it can be patched? thanks!

What specific player is it? The update files are specific to the player brand and version number. if it's version 1.9 I will guess it's probably a HifiWalker H2?

It's rarely safe to install an original firmware version different from what came on the player from the factory, so the best thing to do is ask the manufacturer to provide you with a firmware update file. They seem to be pretty good about providing them so far.

[dconrad]

Update on the Native port for those in this thread, I'm working on integrating ZappBranigan2972's patches. Because I don't have a player which requires the new LCD initialization (we're calling them "v3" players, I think), I need someone to do a test for me, preferably someone who has used jztool already. Your player needs to be one of the ones which has the backwards and inverted LCD issue. It can have the hosted port installed on it, that won't matter for this test. This won't get written to your player, it's only temporary.

Basically, I just need you to temporarily load the test bootloader I will link and let me know if it shows up correctly, i.e.: White text on black background, and, you know, not backwards.

Steps:

• Download this bootloader file
• Download jztool if you don't already have it from JztoolInstall Wiki Page
• With the player off, hold Menu while plugging in USB. The blue LED near the Menu button should come on, but the screen should stay off. The player is now in usbboot mode.
• Run the appropriate jztool command to send the bootloader (temporarily) to the player. This might differ slightly based on your operating system (see the jztool wiki page for details), but will be something like "./jztool erosq load bootloader_v3.erosq" for Linux/Mac.
• The bootloader screen should come up on the player - what I need to know is if it looks normal! White text on black background, and not backwards!

[hannahmuffins]

What specific player is it? The update files are specific to the player brand and version number. if it's version 1.9 I will guess it's probably a HifiWalker H2?

its an AIGO eros Q, the one that looks like the H2 but different branding

[hannahmuffins]

oh i think i misunderstood how this all works, i thought i needed a prepatched update file before i could use the rockbox utility but it can patch the stock file can't it.. so i just need to figure out how to contact the manufacturer and get that then 

[speachy]

oh i think i misunderstood how this all works, i thought i needed a prepatched update file before i could use the rockbox utility but it can patch the stock file can't it.. so i just need to figure out how to contact the manufacturer and get that then 

Their web site is www.eroshifi.com.  Ideally you can get them to supply the original v1.9 firmware as an update file.  We don't know what hardware generation the v1.9 and v2.0 firmwares correspond with.

BTW, these folks are the original designers of this series of players; Surfans, HifiWalker and even AGPTek did little more than slap their own logo on the case and firmware.

Also, the way rbutil works with these things will have to change due to the multiple hardware (and firmware) variations with no way to detect the difference from the outside.

[hannahmuffins]

Their web site is www.eroshifi.com.  Ideally you can get them to supply the original v1.9 firmware as an update file.  We don't know what hardware generation the v1.9 and v2.0 firmwares correspond with.

thanks, i tried emailing them but apparently the email doesnt exist.. think im out of luck here. thanks for the help anyway

[ZappBranigan2972]

Update on the Native port for those in this thread, I'm working on integrating ZappBranigan2972's patches. Because I don't have a player which requires the new LCD initialization (we're calling them "v3" players, I think), I need someone to do a test for me, preferably someone who has used jztool already. ....

V3 Devices Testet ( SurfansF20 v3.2 / Hifi Walker H2 v1.8 ) Redirect File: rockbox_main.aigo_erosqn /_erosqn_v3
Bootloader    cd91c238de + g5877 (Compiled for Target 248), Rockbox cd91c238de + g5877 (compiled for Target 247)

Code: [Select]

1.
Bootloader Original Release cd91c238de + g5877 (no additional Patches) GCC4.9.4
Rockbox Original Release cd91c238de + g5877 (no additional Patches) GCC4.9.4

Installed Rockbox Bootloader (via Bootloader Menue)
        Boot OF via PlayBtn: Boot OK
        Boot OF via BL Menu: Boot OK
        Boot RB            : Boot OK
        Boot RB via BL Menu: Boot OK

        Roloing installed Kernel when Music Play:                   Black Screen(!)
        Roloing installed Kernel when Pausing/Stopped Music Play:   No Bootdata found, Wrong Display (V1/V2) orientation/color, no Redirect found


2.
Bootloader Original Release cd91c238de + g5877 (additional DMAFIX+ClkSleep Patches) GCC4.9.4
Rockbox Original Release cd91c238de + g5877 (additional DMAFIX+ClkSleep Patches) GCC4.9.4

Rockbox InRam Bootloader (via jztool)
        Boot OF via PlayBtn: not testet
        Boot OF via BL Menu: Boot OK
        Boot RB            : not testet
        Boot RB via BL Menu: Boot OK

        Roloing installed Kernel when Music Play:                   Black Screen(!)
        Roloing installed Kernel when Pausing/Stopped Music Play:   No Bootdata found, Wrong Display (V1/V2) orientation/color, no Redirect found

3.
Bootloader Original Release cd91c238de + g5877 (all additional GCC4.9.4 Patches) GCC4.9.4
Rockbox Original Release cd91c238de + g5877 (all additional GCC4.9.4 Patches) GCC4.9.4

Installed Rockbox Bootloader (via Bootloader Menue)
        Boot OF via PlayBtn: Boot OK
        Boot OF via BL Menu: Boot OK
        Boot RB            : Boot OK
        Boot RB via BL Menu: Boot OK

        Roloing installed Kernel when Music Play:                   Black Screen(!)
        Roloing installed Kernel when Pausing/Stopped Music Play:   No Bootdata found, Wrong Display (V1/V2) orientation/color, no Redirect found

4.
Bootloader Original Release cd91c238de + g5877 (all additional GCC4.9.4 Patches) GCC4.9.4
Rockbox Original Release cd91c238de + g5877 (all additional Patches) GCC14.2.0

Installed Rockbox Bootloader (via Bootloader Menue)
        Boot OF via PlayBtn: Boot OK
        Boot OF via BL Menu: Boot OK
        Boot RB            : Boot OK
        Boot RB via BL Menu: Boot OK

        Roloing installed Kernel when Music Play:                   Black Screen(!)
        Roloing installed Kernel when Pausing/Stopped Music Play:   No Bootdata found, Wrong Display (V1/V2) orientation/color, no Redirect found
V2 Devices Testet ( SurfansF20 V2,7 / Hifi Walker H2 v1.5 ) Redirect File: rockbox_main.aigo_erosqn /_erosqn
Bootloader    cd91c238de + g5877 (Compiled for Target 247), Rockbox cd91c238de + g5877 (compiled for Target 247)

Code: [Select]

5.
Bootloader Original Release cd91c238de + g5877 (no additional Patches) GCC4.9.4
Rockbox Original Release cd91c238de + g5877 (no additional Patches) GCC4.9.4

Installed Rockbox Bootloader (via Bootloader Menue)
        Boot OF via PlayBtn: Boot OK
        Boot OF via BL Menu: Boot OK
        Boot RB            : Boot OK
        Boot RB via BL Menu: Boot OK

        Roloing installed Kernel when Music Play:                   Black Screen(!)
        Roloing installed Kernel when Pausing/Stopped Music Play:   No Bootdata found, Right Display (V1/V2) orientation, no Redirect found

6.
Bootloader Original Release cd91c238de + g5877 (all additional GCC4.9.4 Patches) GCC4.9.4
Rockbox Original Release cd91c238de + g5877 (all additional Patches) GCC14.2.0

Installed Rockbox Bootloader (via Bootloader Menue)
        Boot OF via PlayBtn: Boot OK
        Boot OF via BL Menu: Boot OK
        Boot RB            : Boot OK
        Boot RB via BL Menu: Boot OK

        Roloing installed Kernel when Music Play:                   Black Screen(!)
        Roloing installed Kernel when Pausing/Stopped Music Play:   No Bootdata found, Right Display (V1/V2) orientation, no Redirect found
It works , only the Rolo Thing with redirect is a little borked (Fiio m3k, Sansa e200, Sansa Clipzip shows similar Rolo Behavior).
All my five Players are now on Bootloader cd91c238de + g5877  (GCC 4.9.4) and Rockbox cd91c238de + g5877 (all additional Patches GCC14.2.0)

[dconrad]

Thanks for testing!

Hmm, if I understand correctly, it works fine then on normal boot, but screws up the display upon reloading with rolo. I wonder if maybe bootdata isn't being passed through rolo...? In any case, I don't think that's a fundamental issue with this patchset.

Were you reloading from the same location or from a different location?

I think on reality the only time most people use rolo is when they update their installation and it asks them if they want to reload it.