Support and General Use > Hardware
[Solved]: Looking for help: iRiver H140 with Toshiba MK2431GAH
Uwe Z:
Thanks Bluebrother,
Not sure about the flashing procedure. I flashed it with 7pre4 and I think you are right I still had the stable build 3.12 on the disc. That makes sense.
So that means I should flash again with 7pre4??
(I will go through the procedure again but I am not sure as right now EVERYTHING works perfect. Database did build up, files are all there, themes are set ..... Nothing to complain about. Just happy. But if I do a reset I have to avoid starting from ROM or RAM image.)
Any risk involved with flashing 7pre4 and having the development build on the disc?
Uwe Z:
Questions answered!
I just did it: flashed rombox.river and rockbox.iriver using iriver_flash plugin .....SUCCESS! 8) 8) 8).
Restarted from ROM image ....done!
This made my day :). Now I am set for future travel.....see picture!
Thanks to the Rockbox team!
DTSyX:
Just as FYI and future reference:
I stepped away from using FAT32formatter because I think it might had something to do with my ssd having died off after about 2,5 years (= several Rockbox updates = several ssd reformats).
I think it's the bootloader (7pre4) that forces me to format and reinstall the whole disk every time I want to do an Rockbox update - even if I go back to the version that was on the disk before I get an checksum error at boot time.
[edit August 21st 2017]
Seems like others experience the same problem (see comment section of the linked site). Also, it might be that this problem affects only certain rockbox (main) releases:
https://www.rockbox.org/tracker/task/12769?string=h140&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=
[/edit]
And as the FAT32formatter seems to work "with brute force" (initialising disk) or maybe it's the sector size of 512 bytes it's using one sometimes has to tried a few times until the disk is finally formatted correctly.
Since I found out about the new main release of Rockbox (3.14) I did this procedure all over again and the ssd was reaction slowly afterward I got the feeling the FAT32formatter "did it again".
I also "updated" my 240GB hdd (as backup). But with that one I used the FAT32format (guiformat) tool (http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm). That proposes 32768 which work fine, too (the H140 boots).
I just found out that that's not 32768 bytes per sector but 512 bytes per sector * 64 sectors per cluster - so it's bytes per cluster. The program says allocation unit size. I thought that was bytes per sector because one can also choose 512 - my bad.
Anyway - I feel more comfortable using the FAT32format (guiformat) than the FAT32Formatter for now.
And thinking about that having to reformat every time I update Rockbox I came across https://www.rockbox.org/wiki/IriverFlashing (and http://www.rockbox.org/twiki/bin/view/Main/RoLo). I think I visited that page a few years back and fiddled with my H140. So, I thought maybe I flashed my H140 but never updated the flash version after updating the files on the disk. But as it turns out I never did it right, so I never actually flashed my H140.
So, this time I actually flashed my H140. But if you do so, please do NOT forget to do a backup = ROM dump first! I somehow missed it and would have been screwed (kind of) if I didn't have a backup H140 with which I could do a dump that also worked on my first H140. So I could reverse everything and start from scratch.
But now I'm booting from ROM. That's not only faster but I think I can bypass the having to re-format etc. with every update. Because now I just update the flash and ROM immediately after (as in before reboot) the Rockbox update and should be fine with subsequent reboots - no more checksum errors as I don't boot from disk anymore.
At least that's what I'm thinking and hoping. :-)
TheHistorian:
I had attempted to get the 240GB drive working in my H140 five years ago. I ended up with an unusable player, got frustrated, stuck it in a drawer, and mostly ignored music while enjoying other things.
This weekend I was inspired to take a look at it, found your recent post, and after charging, was back up and running in a few minutes! You made my year - thank you!
--- Quote from: DTSyX on August 20, 2017, 03:25:39 AM ---Just as FYI and future reference:
I stepped away from using FAT32formatter because I think it might had something to do with my ssd having died off after about 2,5 years (= several Rockbox updates = several ssd reformats).
I think it's the bootloader (7pre4) that forces me to format and reinstall the whole disk every time I want to do an Rockbox update - even if I go back to the version that was on the disk before I get an checksum error at boot time.
[edit August 21st 2017]
Seems like others experience the same problem (see comment section of the linked site). Also, it might be that this problem affects only certain rockbox (main) releases:
https://www.rockbox.org/tracker/task/12769?string=h140&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=
[/edit]
And as the FAT32formatter seems to work "with brute force" (initialising disk) or maybe it's the sector size of 512 bytes it's using one sometimes has to tried a few times until the disk is finally formatted correctly.
Since I found out about the new main release of Rockbox (3.14) I did this procedure all over again and the ssd was reaction slowly afterward I got the feeling the FAT32formatter "did it again".
I also "updated" my 240GB hdd (as backup). But with that one I used the FAT32format (guiformat) tool (http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm). That proposes 32768 which work fine, too (the H140 boots).
I just found out that that's not 32768 bytes per sector but 512 bytes per sector * 64 sectors per cluster - so it's bytes per cluster. The program says allocation unit size. I thought that was bytes per sector because one can also choose 512 - my bad.
Anyway - I feel more comfortable using the FAT32format (guiformat) than the FAT32Formatter for now.
And thinking about that having to reformat every time I update Rockbox I came across https://www.rockbox.org/wiki/IriverFlashing (and http://www.rockbox.org/twiki/bin/view/Main/RoLo). I think I visited that page a few years back and fiddled with my H140. So, I thought maybe I flashed my H140 but never updated the flash version after updating the files on the disk. But as it turns out I never did it right, so I never actually flashed my H140.
So, this time I actually flashed my H140. But if you do so, please do NOT forget to do a backup = ROM dump first! I somehow missed it and would have been screwed (kind of) if I didn't have a backup H140 with which I could do a dump that also worked on my first H140. So I could reverse everything and start from scratch.
But now I'm booting from ROM. That's not only faster but I think I can bypass the having to re-format etc. with every update. Because now I just update the flash and ROM immediately after (as in before reboot) the Rockbox update and should be fine with subsequent reboots - no more checksum errors as I don't boot from disk anymore.
At least that's what I'm thinking and hoping. :-)
--- End quote ---
Navigation
[0] Message Index
[*] Previous page
Go to full version