Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Welcome to the Rockbox Technical Forums!

+  Rockbox Technical Forums
|-+  Installation / Removal
| |-+  Manual Installation
| | |-+  Sandisk - Installation/Removal
| | | |-+  Bricked Sansa e270
« previous next »
  • Print
Pages: 1 [2]

Author Topic: Bricked Sansa e270  (Read 10464 times)

Offline dan_a

  • Developer
  • Member
  • *
  • Posts: 85
  • MD1CLV
Re: Was an e250, is now a brick :(
« Reply #15 on: February 19, 2008, 06:18:13 PM »
What happens when you try it?  I strongly suspect that I've done far more horrible things to my Sansa than you ever will, and have not managed to brick it yet...
Logged
iPod 3G
iPod 4G Mono
Sansa E250
Sansa Clip

Offline lewislink

  • Member
  • *
  • Posts: 42
Re: Was an e250, is now a brick :(
« Reply #16 on: February 19, 2008, 06:35:41 PM »
The worst thing I did was boot it into MSC mode. If it wasn't for that I'd have it going again. As far as what it does when I enter it into recovery mode, the 16MB file loads, I put the M4 file on it, reboot and the un-refresh screen still shows.

It doesn't help that, when trying to get it to work, I formatted the recovery mode. I also put other files onto the recovery mode file, files that were never mentioned to be put on it.

If I could get the player back into MTP mode, someway, I would be able to get it going again.
Logged

Offline dan_a

  • Developer
  • Member
  • *
  • Posts: 85
  • MD1CLV
Re: Was an e250, is now a brick :(
« Reply #17 on: February 19, 2008, 07:22:22 PM »
OK, that sounds fixable.  It sounds like you've gotten things into a state where the Sansa database scanner isn't working, so what we want to do is get the Sansa to think it's got no files on, so the database scan runs properly.

Boot into recovery mode.
Put the original firmware .mi4 file onto the 16Mb partition
Create an empty file called "sansa.fmt" and put that on the 16Mb partition
Do not put ANYTHING else into the 16Mb partition.
Safely disconnect your Sansa.

It should reboot straight into the original firmware - the Sansa will be exactly like it was when you got it out of the box the first time.
The downside to doing this is that it will delete all your files - but on the plus side, you'll have a working Sansa at the end of it!
Logged
iPod 3G
iPod 4G Mono
Sansa E250
Sansa Clip

Offline lewislink

  • Member
  • *
  • Posts: 42
Re: Was an e250, is now a brick :(
« Reply #18 on: February 19, 2008, 07:39:12 PM »
I don't have the M14 file any longer. I can't remember where I got it either. Since it didn't get my player working I figured why keep it.
Logged

Offline saratoga

  • Developer
  • Member
  • *
  • Posts: 8974
Re: Was an e250, is now a brick :(
« Reply #19 on: February 19, 2008, 07:52:02 PM »
Quote from: lewislink on February 19, 2008, 07:39:12 PM
I don't have the M14 file any longer. I can't remember where I got it either. Since it didn't get my player working I figured why keep it.

Then download a new one from here or one of the other hundred links on google:

http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick
Logged

Offline lewislink

  • Member
  • *
  • Posts: 42
Re: Was an e250, is now a brick :(
« Reply #20 on: February 19, 2008, 07:55:22 PM »
When talking about making afile is that a general wordpad file or what?
Logged

Offline Febs

  • Member
  • *
  • Posts: 2701
Re: Bricked Sansa e270
« Reply #21 on: February 19, 2008, 08:01:02 PM »
lewislink, I merged your thread with the existing thread in which you were also seeking advice for this same problem so that all of the advice that people have given you and your responses will be in one place.
Logged
Rockbox Forum Guidelines
The Rockbox Manual
How to Ask Questions the Smart Way
Please do not send me support questions via PM.

Offline lewislink

  • Member
  • *
  • Posts: 42
Re: Bricked Sansa e270
« Reply #22 on: February 19, 2008, 08:06:12 PM »
Well, I did what was said to do but the refresh screen still hangs. I booted the e250 into recovery mode, put the m14 file on the 16MB file folder that popped up on my PC and created a text doc. named sansa.fmt, rebooted and it still hangs. I tried the process again and this time deleted the "VERSION" text doc. and still hangs. :(
Logged

Offline lewislink

  • Member
  • *
  • Posts: 42
Re: Was an e250, is now a brick :(
« Reply #23 on: February 19, 2008, 08:31:40 PM »
Quote from: dan_a on February 19, 2008, 07:22:22 PM
OK, that sounds fixable.  It sounds like you've gotten things into a state where the Sansa database scanner isn't working, so what we want to do is get the Sansa to think it's got no files on, so the database scan runs properly.

Boot into recovery mode.
Put the original firmware .mi4 file onto the 16Mb partition
Create an empty file called "sansa.fmt" and put that on the 16Mb partition
Do not put ANYTHING else into the 16Mb partition.
Safely disconnect your Sansa.

It should reboot straight into the original firmware - the Sansa will be exactly like it was when you got it out of the box the first time.
The downside to doing this is that it will delete all your files - but on the plus side, you'll have a working Sansa at the end of it!

Just wanted to thank you for helping me get my e250 working again. :)

Yep, it is alive and well now. I figured out how to make a file by copying the m14 file and renaming it what sansa.fmt. My player immediately booted back up and works as though nothing was ever wrong.
Logged

  • Print
Pages: 1 [2]
« previous next »
+  Rockbox Technical Forums
|-+  Installation / Removal
| |-+  Manual Installation
| | |-+  Sandisk - Installation/Removal
| | | |-+  Bricked Sansa e270
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.082 seconds with 14 queries.