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
|-+  Support and General Use
| |-+  Hardware
| | |-+  Sansa e280R bricked?
« previous next »
  • Print
Pages: [1]

Author Topic: Sansa e280R bricked?  (Read 526 times)

rickygrewal

  • Guest
Sansa e280R bricked?
« on: August 28, 2018, 04:37:28 AM »
Hi all,

I found my old Sansa e280R the other day and decided to load Rockbox on it. I started following the special Rhapsody model instructions on the official site. Once the special bootloader section was done, it took me back to the regular Sansa e200 instructions. While I was copying pp5022.mi4 to the device but before I could copy OF.mi4, my device randomly disconnected from windows. When it attempted to reconnect, the Rockbox bootloader gave an error that it can't find the firmware, then pauses for a minute and errors that it can't find the original firmware, then shuts down. I can't get it to stay on long enough to register as a USB device to fix those firmware files. Is there any sort of recovery mode I can boot to to try to remedy this problem or have I bricked? Any advice is welcome.

Thanks!
Logged

Offline saratoga

  • Developer
  • Member
  • *
  • Posts: 8968
Re: Sansa e280R bricked?
« Reply #1 on: August 28, 2018, 10:07:26 AM »
Hold left when booting to start the Sandisk firmware then finish installing.
Logged

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Hardware
| | |-+  Sansa e280R bricked?
 

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

Page created in 0.123 seconds with 21 queries.