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

[muflone]

I created a user for your forum to confirm that an Eros Q with version 2.2 firmware (just received from aliexpress) works with the rockbox version 4. Using jztool, after seeing black screens with the other two bootloaders, I gave a try to  version 4 and was welcome by a visible menu. I completed the installation of rockbox and everything works fine.

I also downloaded flash.img. It is more than 130 Mb. What metod do you suggest for transferring it to you?

[Urko]

Good evening! Could someone please share the original bootloader of Hifi Walker H2 2.0 firmware version?

https://mega.nz/file/0FlAXICQ#JwMHdyDrdRV3My1cgIC91MMZhUU9HBiOPQk9Zp1xjyQ

 

[dconrad]

I created a user for your forum to confirm that an Eros Q with version 2.2 firmware (just received from aliexpress) works with the rockbox version 4. Using jztool, after seeing black screens with the other two bootloaders, I gave a try to  version 4 and was welcome by a visible menu. I completed the installation of rockbox and everything works fine.

I also downloaded flash.img. It is more than 130 Mb. What metod do you suggest for transferring it to you?

Hi, sorry for the late response, but any old file sharing service (google drive, etc.) is good. Thanks!

[InvictusMB]

Hey folks, does anyone have a stock HiFi Walker H2 v1.5 bootloader dump?

Or otherwise is there an instruction on how to obtain a bootloader or anything flashable from the images provided by the manufacturer here?

[dconrad]

Hey folks, does anyone have a stock HiFi Walker H2 v1.5 bootloader dump?

Or otherwise is there an instruction on how to obtain a bootloader or anything flashable from the images provided by the manufacturer here?

You're in luck, looks like I have a copy - see here. I can't remember what it needs to be named in order for the bootloader to find it... erosqnative-boot.bin, I think?

[InvictusMB]

You're in luck, looks like I have a copy - see here. I can't remember what it needs to be named in order for the bootloader to find it... erosqnative-boot.bin, I think?

Thanks, I was able to flash it form recovery successfully but it booted into black screen. I had to flash back Rockbox bootloader via jztool to unbrick.

Same happens with a uboot.bin posted by manufacturer. I guess there is a missing piece or a missing step somewhere.

[dconrad]

You're in luck, looks like I have a copy - see here. I can't remember what it needs to be named in order for the bootloader to find it... erosqnative-boot.bin, I think?

Thanks, I was able to flash it form recovery successfully but it booted into black screen. I had to flash back Rockbox bootloader via jztool to unbrick.

Same happens with a uboot.bin posted by manufacturer. I guess there is a missing piece or a missing step somewhere.

Hmm, that's unfortunate. Luckily it was easily recoverable. Are you trying to return the player to stock?

If you have the current bootloader on there, you can get into the Aigo Recovery mode from the bootloader menu (with the player off, hold VolUp + Power). Then you should be able to use an update file - The stock update file does not write the bootloader by default. But we can simply mark it to be updated and then run the stock updater. You can use the script in the rockbox tree at tools/hibyos_nativepatcher/hibyos_nativepatcher.sh to modify the stock update file, or I can do it when I get home tonight.

[InvictusMB]

Yes, I'm trying to revert native Rockbox installation back to stock then to hosted mode. I've observed that I boot into Hiby more often because of working Bluetooth.

The stock update file does not write the bootloader by default. But we can simply mark it to be updated and then run the stock updater.

Ah, that explains a lot. I'm not sure the stock updater actually does anything right now. The way I remember it working was rebooting and showing the progress bar while applying the update.

If I boot into Hiby and run an update it almost immediately reboots into Rockbox and does nothing.

[dconrad]

Yeah, the way it's supposed to work if everything is stock, is that it will reboot the device to the bootloader and then from there go into the updater. The rockbox bootloader doesn't know about whatever signal the stock OS is sending to indicate it should go into the updater, so it just boots into rockbox. You can still get to it though, it's just a different procedure via that bootloader menu.

[hawkshot2001]

Is it normal for the top edge of an H2 HWv4 (2.1 firmware) to be cut off when viewing the H2 straight on?

It is very noticeable on the default theme.  See attached.

Is there a way to adjust the global viewport in Rockbox or should I return the device as defective?

Edit: also a minor nitpick is the lower corner on the back squeaks/moves that normal too?

[dconrad]

Yes, I'm trying to revert native Rockbox installation back to stock then to hosted mode. I've observed that I boot into Hiby more often because of working Bluetooth.

The stock update file does not write the bootloader by default. But we can simply mark it to be updated and then run the stock updater.

Ah, that explains a lot. I'm not sure the stock updater actually does anything right now. The way I remember it working was rebooting and showing the progress bar while applying the update.

If I boot into Hiby and run an update it almost immediately reboots into Rockbox and does nothing.

Alright, give this file a shot. Put it on the SD card named "update.upt" and then, with the device off, hold VolUp + Power, and then select "Aigo Recovery". It should run the updater then and you'll be working with a totally stock player. (fingers crossed for no weirdness)

[dconrad]

Is it normal for the top edge of an H2 HWv4 (2.1 firmware) to be cut off when viewing the H2 straight on?

It is very noticeable on the default theme.  See attached.

Is there a way to adjust the global viewport in Rockbox or should I return the device as defective?

Edit: also a minor nitpick is the lower corner on the back squeaks/moves that normal too?

Both of those are pretty normal in my experience. Possible future improvement to change the position of that statusbar, but once you start using other themes it becomes much less of an issue. And yeah, the back just snaps in on three sides (left, right, and bottom), so it's possible for it to squeak a bit.

[hawkshot2001]

Both of those are pretty normal in my experience. Possible future improvement to change the position of that statusbar, but once you start using other themes it becomes much less of an issue. And yeah, the back just snaps in on three sides (left, right, and bottom), so it's possible for it to squeak a bit.

Thank you for the reply.  I am using the Nightpod theme and yes the cut off screen is not very noticeable using that theme.

This is a pretty solid device.  Rockbox has been very stable on it too.

[InvictusMB]

Alright, give this file a shot. Put it on the SD card named "update.upt" and then, with the device off, hold VolUp + Power, and then select "Aigo Recovery". It should run the updater then and you'll be working with a totally stock player. (fingers crossed for no weirdness)

This one worked like a charm. Thanks a lot!

So, regarding the Bluetooth support for H2, I might dig a little bit into that if you give me a direction where to start. I remember seeing some BlueZ examples among Ingenic's documentation so it should be doable.

[dconrad]

Alright, give this file a shot. Put it on the SD card named "update.upt" and then, with the device off, hold VolUp + Power, and then select "Aigo Recovery". It should run the updater then and you'll be working with a totally stock player. (fingers crossed for no weirdness)

This one worked like a charm. Thanks a lot!

So, regarding the Bluetooth support for H2, I might dig a little bit into that if you give me a direction where to start. I remember seeing some BlueZ examples among Ingenic's documentation so it should be doable.

If you're interested in looking at that, I would ping speachy about it - my understanding is getting it going on Hosted will be a significant undertaking but not impossible, whereas for the native port there's a lack of overlap between technically appropriate stack and compatible license.

There's this patch beginning to make a menu for it, at least.

Edit: I should add, I think interfacing between the pcm mixer and bluetooth interface to actually get data going to the right place would likely be a good place to start - it may take a bit to get it all straightened out.