Deleted boot files in recovery mode, how do I fix?!?

[smug]

why would a different computer matter?

[smug]

I need someone who has had this problem before to post. I can get into recovery mode. My problem is, anything I drop in the 16MB-Format my player won't accept. How do I get my player to accept anything in recovery mode?

[chrisjs162216]

Little bit of my background - I've had a sansa for a year and a half, I've tried to brick it in every way possible, and still could not do it (note: this does not include hardware modifications). Any changes you make to your sansa from your computer can be reverted, unless there's hardware damage. Only problem is, if there's hardware damage, you can't get to recovery mode...meaning it can be fixed.

I've used recovery mode hundreds of times, have helped the Rockbox crew test e200R to e200 conversions, and have helped test getting Rockbox on the e200R. I've done just about every trick possible to my Sansa, so there's no point arguing.

In addition, based on the attitude it looked like you had based on your posts, I may come off a little mean. If I do, I apologize. However, keep in mind that I was once a Sansa Rockbox moderator here, specializing in Rockbox and repairing Sansas. If you try to go the Sandisk Customer Support route, you're going to end up waiting two to three weeks, while it would only take a few hours if you follow these directions. In addition, advcomp2019 is a Sansa moderator, meaning he's also been around Sansas for quite a while. While Cruleworld isn't a moderator, he's an ultra senior member - he's also seen quite a few cases similar to this, and has helped people recover quite a few Sansas.

Ultimate quoting:

It won't install the firmware.
It won't load that firmware.
It doesn't load anything. That's the problem. It won't take any files I put in it.

Most likely it's the wrong files (or filenames) then.

no, you guys don't understand. [snip] Will someone please help me already?!?!?

In all seriousness, if you don't think we understand, how can we help you?

I can get into recovery mode just fine every time.

Originally Posted by smug

I did use the e200 tool for linux. It still won't accept the files.

If you can get to recovery mode, you DO NOT need manu mode.

Originally Posted by smug

I can't put the new .txt file in the player. My player won't let me write anything to it. It's really corrupted.

If it was corrupt, you wouldn't be in recovery mode. Recovery mode and the other data (firmware, bootloader, music) are stored on the same drive, under different partitions (recovery mode, bootloader, firmware on one, music on the other). As I said before, if the memory was corrupt, recovery mode wouldn't load, and you'd need to use manu mode (since recovery mode does load, manu mode is not needed)

Originally Posted by smug

why would a different computer matter?

Because there's a very small chance that there'd be identical computers - same exact model number (if prebuilt), same exact settings, same updates, etc. In addition, it'd wipe out the possibility for any hardware problem on your computer. In other words, trying on a second computer would eliminate the possibility of it being a problem on the one you're using.

Originally Posted by smug

I need someone who has had this problem before to post. I can get into recovery mode. My problem is, anything I drop in the 16MB-Format my player won't accept. How do I get my player to accept anything in recovery mode?

I've read up on just about every problems there's been. From what it looks like, your sansa isn't accepting the files because you installed the beta firmware, which uses different filenames. A missing version.txt file could possibly be the cause, but I haven't experimented with that enough yet to know. Try the following:
Go into recovery mode: Turn on hold, begin holding record while turning your player on, and release REC when it says "Welcome to Recovery Mode". At this point, grab the file's you'll need:
Based on your problem, you'll probably need all four files to fully clean your sansa:
The bootloader, the firmware, version.txt, and sansa.fmt.

Grab the version.txt file advcomp2019 posted on the first page, and save it on to the 16MB-FORMAT drive that appears on your computer. Download the 1.02.18A firmware - the one on my site has been known to work: http://chrisjs.com/PP5022.mi4 . Save that onto your sansa, and rename it to firmware.mi4. Download the bootloader as well - http://chrisjs.com/download/firmware...DSUPPORTSD.ROM . Save that onto your sansa, and rename it to pribootLoader.rom. Note that firmware.mi4 and pribootLoader.rom are case sensitive. Create a blank file called sansa.fmt in notepad, and save it onto the 16MB-FORMAT drive as well.

What this will do is write a copy of the pre-beta firmware, which should let you use pp5022.mi4 and bl_sd_boardsupportsd.rom in the future, which is what probably caused issues for you. The firmware will bring you back down to a stable version of the firmware, which should fix and issues you have starting your Sansa. version.txt should allow those files to be written. sansa.fmt will erase all the files that are currently on the Sansa, which should also fix any issues. Note that all four of these files must be on the sansa before you disconnect it. If you have any problems, post them.

[Fafafooey]

I googled every place known to ..well, the free world..This was the only place that had the remedy..I alsmost threw it away and bought a refurbed one...
This was my last attempt..

ty
This in regards to the sansa.fmt, version.txt, ect files provided here..
Nothing else worked...I was stuck..even tried rockbox or whatever and that was an experience..

Ty so much guys

[Ric0h]

Can you mods sticky this?

Really helpful, or maybe a condensed version? But no doubt this should become a sticky.

[euripides]

I have the same problem. When I remove the 16MB drive safely from my computer and all my sansa says is "Safe to disconnect USB. Eixt USB 2.0 MSD mode" but it does not do anything else. I tried renamed .rom and .mi4 to pribootLoader.rom and firmware.mi4 respectively and my sansa still doing the same. (I've tried this process in 3 different computers).

[chrisjs162216]

Originally Posted by euripides

I have the same problem. When I remove the 16MB drive safely from my computer and all my sansa says is "Safe to disconnect USB. Eixt USB 2.0 MSD mode" but it does not do anything else. I tried renamed .rom and .mi4 to pribootLoader.rom and firmware.mi4 respectively and my sansa still doing the same. (I've tried this process in 3 different computers).

Does the Sansa restart when you disconnect, or does it freeze?

[euripides]

Originally Posted by chrisjs162216

Does the Sansa restart when you disconnect, or does it freeze?

It remains with the message on the screen and does´nt restart.

[advcomp2019]

Euripides, do you remember what firmware did you have on that Sansa?

[euripides]

i had 1.0.2.31 before...

[euripides]

because i had Rockbox installed

[advcomp2019]

The e200R use PP5022.mi4 and BL_SD_boardSupportSD.rom to update the firmware on the Sansa.

[epileptic]

My sansa e260 install like MTP device, but dont let me do it nothing, and when i see the properties, all is UNKNOW =S and dont let me put music in there. what can i do?

I installed the files of cris =S the firmware, the bootloader, sansa.ftm, and it has version.txt, in the recovery mode, it's ok? that files works with the sansa e260?

[epileptic]

Another thing, when i put the sansa in to recovery mode, only shows me the file Version.txt, but i can paste the other 3 files in there.. the sansa let me put the others file that i took from this pages in there. after that, it recognize but only like MTP device, =S and dont let me put music in there :S

[advcomp2019]

Have you tried MSC mode?

[mcflash23]

Originally Posted by chrisjs162216

Little bit of my background - I've had a sansa for a year and a half, I've tried to brick it in every way possible, and still could not do it (note: this does not include hardware modifications). Any changes you make to your sansa from your computer can be reverted, unless there's hardware damage. Only problem is, if there's hardware damage, you can't get to recovery mode...meaning it can be fixed.

I've used recovery mode hundreds of times, have helped the Rockbox crew test e200R to e200 conversions, and have helped test getting Rockbox on the e200R. I've done just about every trick possible to my Sansa, so there's no point arguing.

In addition, based on the attitude it looked like you had based on your posts, I may come off a little mean. If I do, I apologize. However, keep in mind that I was once a Sansa Rockbox moderator here, specializing in Rockbox and repairing Sansas. If you try to go the Sandisk Customer Support route, you're going to end up waiting two to three weeks, while it would only take a few hours if you follow these directions. In addition, advcomp2019 is a Sansa moderator, meaning he's also been around Sansas for quite a while. While Cruleworld isn't a moderator, he's an ultra senior member - he's also seen quite a few cases similar to this, and has helped people recover quite a few Sansas.

Ultimate quoting:


Most likely it's the wrong files (or filenames) then.


In all seriousness, if you don't think we understand, how can we help you?




If you can get to recovery mode, you DO NOT need manu mode.



If it was corrupt, you wouldn't be in recovery mode. Recovery mode and the other data (firmware, bootloader, music) are stored on the same drive, under different partitions (recovery mode, bootloader, firmware on one, music on the other). As I said before, if the memory was corrupt, recovery mode wouldn't load, and you'd need to use manu mode (since recovery mode does load, manu mode is not needed)



Because there's a very small chance that there'd be identical computers - same exact model number (if prebuilt), same exact settings, same updates, etc. In addition, it'd wipe out the possibility for any hardware problem on your computer. In other words, trying on a second computer would eliminate the possibility of it being a problem on the one you're using.



I've read up on just about every problems there's been. From what it looks like, your sansa isn't accepting the files because you installed the beta firmware, which uses different filenames. A missing version.txt file could possibly be the cause, but I haven't experimented with that enough yet to know. Try the following:
Go into recovery mode: Turn on hold, begin holding record while turning your player on, and release REC when it says "Welcome to Recovery Mode". At this point, grab the file's you'll need:
Based on your problem, you'll probably need all four files to fully clean your sansa:
The bootloader, the firmware, version.txt, and sansa.fmt.

Grab the version.txt file advcomp2019 posted on the first page, and save it on to the 16MB-FORMAT drive that appears on your computer. Download the 1.02.18A firmware - the one on my site has been known to work: http://chrisjs.com/PP5022.mi4 . Save that onto your sansa, and rename it to firmware.mi4. Download the bootloader as well - http://chrisjs.com/download/firmware...DSUPPORTSD.ROM . Save that onto your sansa, and rename it to pribootLoader.rom. Note that firmware.mi4 and pribootLoader.rom are case sensitive. Create a blank file called sansa.fmt in notepad, and save it onto the 16MB-FORMAT drive as well.

What this will do is write a copy of the pre-beta firmware, which should let you use pp5022.mi4 and bl_sd_boardsupportsd.rom in the future, which is what probably caused issues for you. The firmware will bring you back down to a stable version of the firmware, which should fix and issues you have starting your Sansa. version.txt should allow those files to be written. sansa.fmt will erase all the files that are currently on the Sansa, which should also fix any issues. Note that all four of these files must be on the sansa before you disconnect it. If you have any problems, post them.

I downloaded and put all four of the files on my sansa e260 and I still get the same error, "Load main image failed"

Here is my version info:

Version Info: Product Rev.: PP5022AF-05.51-S301-02.18-S301.02.18A-D
Base Code: 05.51-S301-02.18-S301.02.18A-D
ODM Ver.: S301-02.18-S301.02.18A-D
OEM Ver.: S301.02.18A-D
Build Type: -D
Build Date: 2006.11.03
Build Number: (Build 32.10)

Can anybody help me?

[justshams]

i too have the same.. i had fixed it hte last time i had this prob put i have forgotten how : P
i have done everything said but i think the version.txt file link given is of 01.02.15A and the firmware is 01.02.18A so i gues its not working
can someone provide a txt for 01.02.18A so tthat i will see if it works??

[justshams]

i have formatted my sansa recovery drive and now its dead.
it is able to come to recovery mode and i am able to detect the 16mb drive on my system and when i put the files as mentioned in one of your guides. but when i disconnect the drive it does not respond it jus displays the exit usb mode and freezes when i power it off by holding menu button and reboot again in the recovery mode it it shows the 16mb drive to be empty and it just containes a curropted version.txt file containing this

Version Info: Product Rev.: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ2œ¤_ú�ßBÙ|
Base Code: ÿÿÿÿÿÿÿÿÿÿ


it contains this crap and nomater how many times i put the firmware.rom pribootLoader.rom sansa.fmt version.txt it doesn change
it freezes on dissconnection from system and when i connect again as i told the 16mb drive is empty..

please help


i don mind having jus rockbox on my sansa also
i don need the original OS of sansa


please help

[advcomp2019]

Justshams, have you tried PP5022.mi4 and BL_SD_BOARDSUPPORTSD.ROM and not firmware.rom and pribootLoader.rom when you did it?

[justshams]

ya i did but it didn work but i did not replace the txt filw when i treid with pp50244.mi4 type of file
i don have a version .txt for 1.02.18A version i have only for 15 version as provided by u in this forum