Rockbox Technical Forums
Installation / Removal => Manual Installation => Iriver - Installation/Removal/Flashing => Topic started by: Otello on July 23, 2007, 07:46:33 PM
-
Hi, can someone help me?
I failed installing the patched file ihp 120.hex now my H 140 doesn't starts.
Now I can switch it on but it stops to the first page of bootloader of the Rockbox
The screen says:
Rock box boot loader
Version 6
Batt: 3.76V
Loading firmware
Length: 55FA0
Checksum: 1A303B3
Model name: h120
Sum: 1A303B3
Result: 0
I tried starting in Iriver OS but it stops at Iriver logo.
I also can access it in USB mode and browse into directories and open files etc..
Thanks to everybody will help me.
ps. sorry for my bad english
Otello
-
If somebody can help, they will answer. Please don't double post.
If you cannot boot Rockbox or the iRiver firmware, there is really nothing that can be done.
-
Flashing a H140 is the most critical phase of the whole rockbox procedure, somehow you messed up the procedure, unfortunately there is nothing that can be done here or at mistic.
Your only option is to send the unit back to iriver and ask them to re-flash your unit, its an easy procedure for them.
I'm curios, is this your first attempt at installing Rockbox ?
and
Which procedure were you following to flash your unit ?
-
IriverOS stopping to boot might also be caused by hard drive problems.
-
hmm, perhaps the 'user' was following the Rockbox RAM/ROM flashing procedure for an initial install instead of following the "Boot Flashing" procedure ?.
It would be nice to know what he did wrong so that others can learn form his mistake.
-
hmm, perhaps the 'user' was following the Rockbox RAM/ROM flashing procedure for an initial install instead of following the "Boot Flashing" procedure ?.
You can't do this for an initial install on h100 series -- you need to boot Rockbox first, and only afterwards you can flash rombox. Initial flashing needs to be done from IriverOS. It is of course possible he built the bootloader himself or used the wrong binary for patching the hex file. I consider this somewhat unrealistic as we provide fwpatcher for this task and have md5sums to verify the result -- ignoring this might be a bad idea ...
-
Try running scandisk on the drive from Windows.
Right-click the drive, select "properties > tools > check now", hopefully this is the problem.
If you're on Linux use fsck.vfat /dev/sda1 (where sda1 corresponds with your Iriver - it must not be mounted).
-
Update from the mistic thread:
The user did a diskscan, to no avail, still bricked.
He said he would send his unit to iviver for repair/reflashing.