problem installing rockbox

[naboo]

Hi

I have a problem getting rockbox installed onto a H140

I have 4 other Irivers 2xH140, H120 & a H320 and happily have rockbox installed on these for some time (before the new utility came out) So I know how the process works

This time around, no matter what I try everytime I switch this H140 on it just boots into the iriver firmware

I have manually patched an original firmware then updated this through the iriver itself and manually extracted the latest build onto the iriver but no joy

I wiped the drive completeley and formatted fat32 using swisknife  then used the new utility to install rockbox but still no joy

I then wiped the drive again and formatted the drive using the iriver original firmware option on the actual drive itself, then used the rockbox utility to install

followed all the instructions, bootloader installed first, after patching an original firmware, then booted into iriver firmware and do a firmware upgrade

then connect back to PC and install the rest of rockbox through the utility and no joy either

then finally I used the utility to do a complete install (without upgrading the firmware through the iriver itself) and letting it install all the rockbox files, then doing the firmware upgrade of the patched bootloader but it still just boots into the stock iriver firmare

There is no sign of the rockbox page at all, doesn't matter if I hold the record button down either

any thoughts ?

[bluebrother]

This time around, no matter what I try everytime I switch this H140 on it just boots into the iriver firmware

This clearly indicates that installing the bootloader failed.

I wiped the drive completeley and formatted fat32 using swisknife  then used the new utility to install rockbox but still no joy

How exactly did you install the bootloader? Rockbox Utility will only place the hex file on the player, you still need to flash the file using the flash option of the OF. I assume you did this, did it work?

[naboo]

Using the rockbox utility I installed the bootloader by pointing the utility to the H120(EU)-v166 I Have

I pressed OK and it did its stuff.

it then tells me to unplug usb then boot into original iriver firmware to do a firmware upgrade on this newly patched  H120(EU)-v166

I then used the utility to install the actual rockbox folder onto the iriver with all the themes etc etc.
I then uplugged the USB cable

So I turn off iriver. unplug power lead then plug power lead back in (don't know why I did that :lol:) then booted iriver back up

went into settings and pressed the upgrade firmware, which the iriver duly obliged then after while turns it self off (which is normal after a firmware upgrade)

I unplugged powere again and plugged back in, then I booted up iriver at which point I should see the rockbox loader page, but I dont, It just boots into Iriver firmware


I have tired the other way too where I just patched the bootloader and then did firmware upgrade on iriver then installed rockbox folders etc after, but still the same

[bluebrother]

it then tells me to unplug usb then boot into original iriver firmware to do a firmware upgrade on this newly patched  H120(EU)-v166

Ok. So this either is a problem with Rockbox Utility patching the hex file itself or with the flashing of your players OF. Can you md5sum the patched and unpatched hex file and compare them against the values at http://www.rockbox.org/twiki/bin/view/Main/IriverBoot#Checksums ?

[naboo]

1.66-EU
patched using   fwpatchernu.exe   gives   MD5 sum of
    
e26d2574f39cee0adcdd54fb9f316293    

which is the same as in the table



1.66-EU  patched using  fwpatcher.exe  gives   MD5 sum of

e26d2574f39cee0adcdd54fb9f316293    

which is the same as in the table



1.66-EU  patched using  the rockbox utility   gives   MD5 sum of

e26d2574f39cee0adcdd54fb9f316293    

which is the same as in the table




The unpatched   1.66-EU   gives MD5 sum of

a094999b41781f4322a57b9be7fa4534


I guess it must be the actual iriver player itself then

[Llorean]

And there are no other .hex files on your player when you run the update?

[naboo]

Nope  just the patched    ihp_120.hex is there

the .rockbox folder
and the RECORD folder of the original iriver


I think I am going to remove all trace of rockbox on one of my other irivers and put the original firmware back on it and try the rockbox utility on that

if it works then it most certainly points to a problem with the iriver firmware update procedure on this "problem" one

[Llorean]

As per our guidelines, please try to restrict yourself to real English words. Things like "deffo" may prove confusing to our non-native speakers who depend on machine translation.

[naboo]

edited accordingly

[Llorean]

Thanks

[naboo]

OK, so I removed ALL traces of rockbox from my "other" H140 and removed the bootloader and put on the original firmware and updated. 

Just the original iriver firmware on it when turned back on

I started the rockbox utility and put the bootloader back onto this other iriver and patched it.

booted into iriver firmware and started the upgrade.

player turned off and when turned back on the rockbox loader appeared so turned back off

installed  rockbox and its folders through the rockbox utility and did a reboot.

boots straight into rockbox on this other iriver



This confirms that there must be something wrong with my other H140's ability to accept a patched firmware.  It accepts original firmare as I can downgrade and upgrade any of the original firmware without a problem.  It also shows the firmware upgrade screen and turns itself off when I use the patched firmware, but, on reboot, just goes into the original iriver firmware.

I wonder what causes this then ?






EDIT

decided to try once more with the exact same steps I just did with my other iriver and SUCCESS
Rockbox is now working on both.

thankyou for your time

[petur]

I have seen on h300 that you sometimes needed to upgrade the firmware twice before it actually worked, this is a bit extreme.

I guess the firmware upgrade function of the OF does some checks and silently fails if something is wrong, giving you the impression it was done when in fact it was not.

Maybe a problem reading the file of writing to flash