Rockbox Technical Forums
Installation / Removal => Manual Installation => Sandisk - Installation/Removal => Topic started by: ildarion on January 14, 2014, 12:40:16 PM
-
There are about 2 months, I wanted to install windows 7 on a PC via USB, so I used my sansa fuze + I formatted (I made a backup before) and which I began Utility windows, ...
I had some difficulty compatibility, Sansa was not really happy, but I managed to install windows.
So I reformatted and installed my back up Rockbox. it's work.
But a few days after that, I wanted to update the bootloader and there ... I had some problems with the OF, when I boot I GET TIRED OF the message:
"Database error please format the device !", "Sansa Will now shutdown."
Impossible to update the bootloader or used the OF.
So I formatted several times, wipe the device data (with "EASEUS Partition"), check partition (OK), chkdsk / f (OK), I try forcing MSC mode (nothing happend), try to put the firmware .sb on the clear device, "sansa updater" don't reconize the device, ...
Now I'm quite out of ideas.
So now, my sansa is formatted with any file on the device. If I turn it on:
"Boot Version: 9f7c6g1 = 120606
arg = CAFEBABE addr = 40000000
up power source: 1
No partition found
loading firmware
file not found "
normally if I copy my back up, Rockbox work, but not the OF, and so, no updating possible.
Sorry for my english.
-
Problem solved, thanx to pamaury on IRC. the windows utility USB installer has changed the value of the sectors size.
Quick resum :<pamaury> the problem is the "logical sector size"
<pamaury> that is: when the OS reads the number for the MBR, those are units of "sectors"
<pamaury> more precisely, it's a logical sector, but the problem is difference software might have different notion of sector size.
<pamaury> The OF has been compiled to use a logical sector size of 2048 bytes, which is quite unusual
<pamaury> On the other hand, Rockbox tries to guess it at runtime
<pamaury> And finally Linux uses the value provided by the USB SCSI layer
<pamaury> By default the OF reports 2048 and since Rockbox guesses right, it reports 2048. So both Linux and Windows use that figure. Everyone is happy
<pamaury> What you did completely erased the partition table and when you plugged it again, OF couldn't boot so you had to use Rockbox
<pamaury> and Rockbox guessed 512 because that how the USB installer thing put on it
<pamaury> And then you couldn't do anything because both Linux and windows would helplessly use 512 instead of 2048
<pamaury> The trick to solve it is tricky: you first create a partition table using 512 sector size and put the partition at sector 2048.
<pamaury> then you create the partition at this sector
<pamaury> Then you rerun fdisk using the -b option to convince him it's actually a 2048 logical size and you recreate the partition at sector 512. And since 512 * 2048 bytes = 2048 * 512 bytes, the partition didn't move, but the figures use different units
<pamaury> Then you unplug and replug, now Rockbox guesses right: 2048 bytes and you are saved
<pamaury> I guess the conclusion is: the OF is stupid but we knew that before ^^
-
i cant speak english. i dont understant. i have same problem. try 2048,4096 but not work. please write me step by step. thank you.
-
Hi, I will put some step by step instruction on the wiki soon.
-
link? thank you.
-
I put the instructions on the wiki http://www.rockbox.org/wiki/STMP37xxRecovery (http://www.rockbox.org/wiki/STMP37xxRecovery), I didn't test them so be careful with them.