Installation / Removal > Other - Installation/Removal

Issues installing Rockbox on HIFI Walker H2 v1.3

(1/4) > >>

Arrefur:
Hello! I've been trying to install rockbox on my HIFI Walker H2 v1.3. I've tried every possible installation method to no avail. Here are all the errors and issues I've been having:

Installing through jztool, I get these errors in the command prompt:
[  ERROR] cannot open file bootloader.erosq (tar error: -2)
[  ERROR] Boot failed: -2

When using the jztooljs website installation, I manage to get to the rockbox recovery menu screen, but backing up and installing result in this error:
NAND open error (5)

Lastly when installing through the update files, the players system reboots, but never launches rockbox.

Any help would be much appreciated! <3

dconrad:
When you use the update files method, do you get a Success message? You have the special version of the HifiWalker which needs the unique update file, https://download.rockbox.org/bootloader/aigo/native/erosqnative-hw1hw2-eros_h2.upt.

If you could load up the bootloader with jztool, could you send the results of the bootloader flash info options "Flash Info" and "Flash ONFI Info", both under Debug tools? It almost sounds like your player has a flash chip that the bootloader doesn't know about.

Arrefur:
When I update files, I do not get a success message, the device simply reboots, with no changes.

I can get the flash_info without issues, but when getting the flash_onfi_info file, I get the "NAND open failed" prompt, and it dumps an empty txt file.
I have attached both to this message.
the flash_info.txt:

--- Quote ---readID opcode  = FF E5 71 E5
readID address = E5 71 E5 71
readID dummy   = E5 71 E5 71
sfc params0  = 06 05 04 03
sfc params1  = 02 55 AA 55
sfc params2  = 00 6E 02 02
sfc params3  = A4 2F 00 00

--- End quote ---

dconrad:
That NAND chip appears to be one of the ones in the list, but I'll try to look into this when I get a chance - I happen to have a V1.3 device at home to compare against. Hopefully it has the same chip installed.

Running the original firmware's updater should give either a "Success v_v" or "failed v_v" message, so it sounds like you're not even getting to the updater, which is weird. I'll have a think about it.

dconrad:
Just an update: My device has a different chip (ato25d1ga) from your (apparent) DS35X1GAXXX. The ds35x1gaxxx is apparently identical for our purposes to the gd5f1gq4xexx. I'm not sure if that's not true and our definition is wrong, or it's not identifying it correctly, or if something is physically wrong. Onwards and downwards.

Navigation

[0] Message Index

[#] Next page