Third Party > Repairing and Upgrading Rockbox Capable Players

e250r bricked [SOLVED]

(1/2) > >>

NorthboundTrain:
OS: Ubuntu 9.10
Player: Sansa e250r (v1)

I tried to upgrade Rockbox on my e250r from 3.3 to the latest using the Rockbox Utility.  When it rebooted the bootloader crashed, and it auto-restarted into the native Sansa software, so I tried to re-install the bootloader, too, but the e250r kept giving a "read-only" error (even though /etc/mtab showed it as rw), so after some digging I tried running Rockbox Utility as root.  No changes.  I tried using the sansapatcher tool to unload the bootloader but with no changes.


--- Code: ---</tmp> $ sudo ./sansapatcher
sansapatcher v0.8 with v6.0 bootloaders - (C) Dave Chapman 2006-2007
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[INFO] Scanning disk devices...
[INFO] e200 found - /dev/sdb
[INFO] Reading partition table from /dev/sdb
[INFO] Sector size is 512 bytes
[INFO] Part    Start Sector    End Sector   Size (MB)   Type
[INFO]    0             515       3885055      1896.7   W95 FAT32 (0x0b)
[INFO]    1         3885056       3926015        20.0   OS/2 hidden C: drive (0x84)
Enter i to install the Rockbox bootloader, u to uninstall
 or c to cancel and do nothing (i/u/c) :u
[INFO] Bootloader removed.
Press ENTER to exit sansapatcher :

--- End code ---

I did something with the -rf option without understanding it (never, never, never do this!) and now I have a brick :(


--- Code: ---</tmp> $ sudo ./sansapatcher -rf /dev/sdb
sansapatcher v0.8 with v6.0 bootloaders - (C) Dave Chapman 2006-2007
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[INFO] Scanning disk devices...
[INFO] e200 found - /dev/sdb
[INFO] Reading partition table from /dev/sdb
[INFO] Sector size is 512 bytes
[INFO] Part    Start Sector    End Sector   Size (MB)   Type
[INFO]    0             515       3885055      1896.7   W95 FAT32 (0x0b)
[INFO]    1         3885056       3926015        20.0   OS/2 hidden C: drive (0x84)
[INFO] Firmware read to file /dev/sdb.

--- End code ---

I've tried going into Recovery Mode and Manufacturing Mode, but Ubuntu never sees the device (it never mounts in /dev/media or /dev/sdb).  Running 'lsusb' gives me:


--- Code: ---</opt/product/Rockbox> $ ./sansapatcher -l
sansapatcher v0.8 with v6.0 bootloaders - (C) Dave Chapman 2006-2007
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[INFO] Scanning disk devices...
[ERR]  No E200s or C200s found, aborting
[ERR]  Please connect your sansa and ensure it is in UMS mode
[ERR]  You may also need to run sansapatcher as root.
[ERR]  Please refer to the Rockbox manual if you continue to have problems.

</opt/product/Rockbox> $ lsusb | grep Sansa
Bus 004 Device 008: ID 0781:0720 SanDisk Corp. Sansa C200 series in recovery mode

--- End code ---

Which is *way* odd, because I don't have a C200, I have an e250r.  I've downloaded e200tool, the .btl and .mi4 files and what not, but I'm afraid to proceed since it's being recognized as the wrong player.  Any ideas?  Thanks!

Chronon:
Can you mount it manually?

NorthboundTrain:
Nope, it's not showing up in mtab:


--- Code: ---</mnt> $ sudo mkdir foo

</mnt> $ sudo mount /dev/sdb /mnt/foo
mount: special device /dev/sdb does not exist

</mnt> $ sudo mount /dev/sdb
mount: can't find /dev/sdb in /etc/fstab or /etc/mtab

--- End code ---

gevaerts:
Can you give lsusb and dmesg outputs?

NorthboundTrain:

--- Quote from: gevaerts on February 21, 2010, 04:32:48 PM ---Can you give lsusb and dmesg outputs?

--- End quote ---

Appreciate the help!  Here's what I have:


--- Code: ---</mnt> $ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 004: ID 0781:0720 SanDisk Corp. Sansa C200 series in recovery mode
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

</mnt> $ dmesg
......
[110602.540147] usb 4-1: new full speed USB device using uhci_hcd and address 8
[110602.707425] usb 4-1: configuration #1 chosen from 1 choice
[111516.096181] usb 4-1: USB disconnect, address 8
[115009.428104] usb 5-2: new full speed USB device using uhci_hcd and address 2
[115014.548145] usb 5-2: device descriptor read/64, error -71
[115019.772455] usb 5-2: device descriptor read/64, error -71
[115019.988136] usb 5-2: new full speed USB device using uhci_hcd and address 3
[115020.152441] usb 5-2: configuration #1 chosen from 1 choice
[115203.360175] usb 5-2: USB disconnect, address 3
[118885.852148] usb 5-2: new full speed USB device using uhci_hcd and address 4
[118886.020396] usb 5-2: configuration #1 chosen from 1 choice
[118885.852148] usb 5-2: new full speed USB device using uhci_hcd and address 4
[118886.020396] usb 5-2: configuration #1 chosen from 1 choice
[119028.760210] usb 5-2: USB disconnect, address 4

</mnt> $

--- End code ---

Thanks!

Navigation

[0] Message Index

[#] Next page

Go to full version