Support and General Use > Hardware
sansa clip zip wont turn on. help!
Mihail Zenkov:
--- Quote from: m1ko on July 16, 2015, 07:11:09 AM ---How can i do that?
--- End quote ---
settings > general settings > database > auto update > off
settings > general settings > system > dircache > off
--- Quote from: m1ko on July 16, 2015, 07:11:09 AM ---and do you think that is what happened to my other zip player?
--- End quote ---
If it dosn't work without sd card - no. You should reformat it and reinstall rockbox. If you have error on formating - probably you have problem with hardware part in player.
23rwge:
--- Quote from: Mihail Zenkov on July 16, 2015, 07:43:40 AM ---
--- Quote from: m1ko on July 16, 2015, 07:11:09 AM ---How can i do that?
--- End quote ---
settings > general settings > database > auto update > off
settings > general settings > system > dircache > off
--- End quote ---
thanks
--- Quote from: Mihail Zenkov on July 16, 2015, 07:43:40 AM ---
--- Quote from: m1ko on July 16, 2015, 07:11:09 AM ---and do you think that is what happened to my other zip player?
--- End quote ---
If it dosn't work without sd card - no. You should reformat it and reinstall rockbox. If you have error on formating - probably you have problem with hardware part in player.
--- End quote ---
yea its most likely that, both the one i am using and the other one re refurbished.
Mohawk:
Try error checking your card.
With my Clip Zip, if there are any file system problems with the card, it would cause issues when booting. Either it wouldn't boot at all, or it would just boot up slowly.
Use a card reader, mount the card in windows, and right click-select properties-then find the tab which will let you check for errors. No need to find bad sectors, just the file system check.
martel:
Just sharing my experience as it seems to be very similar to what is being discussed in this thread.
Today, I decided to boot OF on my Rockbox'd Clip Zip because I wanted to add some more files onto the SD card (64GB) and this usually does not work from RB (the device locks up after certain volume of data transferred).
For some unknown reason, the player showed the sansa logo animation and then "froze" (the player has worked fine for the last 6 months using RB exclusively). I had to force shutdown by holding the power button for a while. After this event, it even started "freezing" on the RB boot screen (neither firmware would get past its initial booting screening). I removed the SD card which had no effect.
Since this is my second Zip (first one totally bricked from my recovery attempts), I made a full backup of the internal drive using the Linux 'dd' command. I hoped I would be able to 'dd' the image back in case the internal drive became "corrupted". So now I had a chance to test this idea - I booted into the "forced MSC" mode (holding the middle button while plugging the device to a PC). The internal drive mounted this way shows as a drive without any partition table. But the device seems to be read only and the player disconnects itself from USB when written to (gives I/O errors) and refuses to cooperate with Linux afterwards (see dmesg output at the end). Do not even try to re-create the partition table using fdisk or similar tools - it cannot be done and as far as I can tell it is not supposed to be done anyway. This low-level device mounting mode on Clip Zip seems practically useless for end users since it does not work as a "normal" drive. (Maybe the real drive/file system starts at some offset within this "device"?)
I intentionally wrapped "frozen" and "corrupted" in quotes because I managed to recover the player from this state. I simply powered the device to boot OF and I left it "frozen" on the Sansa logo boot screen. It eventually booted (after like 5-10 minutes). Then it started refreshing the library, which took eternity (10-20 minutes) despite the player being empty. And then I eventually got to the OF menus, where I chose "format"->"internal drive", then I did a factory reset of settings, then chose MSC USB mode, plugged it into a PC and extracted the v21 OF update onto it. After unplugging it, the player updated its FW. Now the device works fine again and behaves just like when I bought it (there are no visible traces of RockBox, not even the boot loader).
I hope this can save someone from actually bricking their player through the use of the recovery/force mount mode (plugging it into PC while holding the middle button).
--- Code: ---[ 192.260057] usb 1-2: new high-speed USB device number 5 using ehci_hcd
[ 192.396889] scsi9 : usb-storage 1-2:1.0
[ 193.396849] scsi 9:0:0:0: Direct-Access Rockbox Internal Storage 0.00 PQ: 0 ANSI: 4
[ 193.398799] sd 9:0:0:0: Attached scsi generic sg3 type 0
[ 193.399202] sd 9:0:0:0: [sdc] 7683072 512-byte logical blocks: (3.93 GB/3.66 GiB)
[ 193.399799] sd 9:0:0:0: [sdc] Write Protect is off
[ 193.399808] sd 9:0:0:0: [sdc] Mode Sense: 0b 00 00 08
[ 193.400307] sd 9:0:0:0: [sdc] No Caching mode page present
[ 193.400314] sd 9:0:0:0: [sdc] Assuming drive cache: write through
[ 193.402691] sd 9:0:0:0: [sdc] No Caching mode page present
[ 193.402700] sd 9:0:0:0: [sdc] Assuming drive cache: write through
[ 193.409467] sdc:
[ 193.412668] sd 9:0:0:0: [sdc] No Caching mode page present
[ 193.412674] sd 9:0:0:0: [sdc] Assuming drive cache: write through
[ 193.412678] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[ 234.192643] FAT-fs (sdc): bogus number of reserved sectors
[ 234.192655] FAT-fs (sdc): Can't find a valid FAT filesystem
ubuntu@ubuntu:~$ sudo fsck.vfat /dev/sdc
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
Logical sector size is zero.
This is what happens when trying to write to the device:
[ 2340.112068] usb 1-2: reset high-speed USB device number 5 using ehci_hcd
[ 2355.224065] usb 1-2: device descriptor read/64, error -110
[ 2370.440070] usb 1-2: device descriptor read/64, error -110
[ 2370.656070] usb 1-2: reset high-speed USB device number 5 using ehci_hcd
[ 2385.768070] usb 1-2: device descriptor read/64, error -110
[ 2400.984071] usb 1-2: device descriptor read/64, error -110
[ 2401.200071] usb 1-2: reset high-speed USB device number 5 using ehci_hcd
[ 2411.608053] usb 1-2: device not accepting address 5, error -110
[ 2411.720069] usb 1-2: reset high-speed USB device number 5 using ehci_hcd
[ 2422.128054] usb 1-2: device not accepting address 5, error -110
[ 2422.128133] usb 1-2: USB disconnect, device number 5
[ 2422.128142] sd 9:0:0:0: Device offlined - not ready after error recovery
[ 2422.128163] sd 9:0:0:0: [sdc] Unhandled error code
[ 2422.128169] sd 9:0:0:0: [sdc] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[ 2422.128178] sd 9:0:0:0: [sdc] CDB: Write(10): 2a 00 00 00 00 00 00 00 08 00
[ 2422.128201] end_request: I/O error, dev sdc, sector 0
[ 2422.128210] Buffer I/O error on device sdc, logical block 0
[ 2422.128216] lost page write due to I/O error on sdc
[ 2422.131043] sdc: detected capacity change from 3933732864 to 0
[ 2422.244075] usb 1-2: new high-speed USB device number 7 using ehci_hcd
[ 2437.356077] usb 1-2: device descriptor read/64, error -110
[ 2452.572066] usb 1-2: device descriptor read/64, error -110
[ 2452.788071] usb 1-2: new high-speed USB device number 8 using ehci_hcd
[ 2467.900067] usb 1-2: device descriptor read/64, error -110
[ 2483.116058] usb 1-2: device descriptor read/64, error -110
[ 2483.332090] usb 1-2: new high-speed USB device number 9 using ehci_hcd
[ 2488.752055] usb 1-2: device not accepting address 9, error -71
[ 2488.864090] usb 1-2: new high-speed USB device number 10 using ehci_hcd
[ 2494.284054] usb 1-2: device not accepting address 10, error -71
[ 2494.284093] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 2494.616068] usb 3-2: new full-speed USB device number 2 using ohci_hcd
[ 2509.752067] usb 3-2: device descriptor read/64, error -110
[ 2524.992069] usb 3-2: device descriptor read/64, error -110
[ 2525.232065] usb 3-2: new full-speed USB device number 3 using ohci_hcd
[ 2540.368069] usb 3-2: device descriptor read/64, error -110
[ 2555.608072] usb 3-2: device descriptor read/64, error -110
[ 2555.848064] usb 3-2: new full-speed USB device number 4 using ohci_hcd
[ 2566.256070] usb 3-2: device not accepting address 4, error -110
[ 2566.392073] usb 3-2: new full-speed USB device number 5 using ohci_hcd
[ 2576.800040] usb 3-2: device not accepting address 5, error -110
[ 2576.800104] hub 3-0:1.0: unable to enumerate USB device on port 2
--- End code ---
saratoga:
--- Quote from: martel on September 05, 2015, 02:37:01 PM ---Since this is my second Zip (first one totally bricked from my recovery attempts), I made a full backup of the internal drive using the Linux 'dd' command.
--- End quote ---
This doesn't help. The part you can dd doesn't even contain the firmware or bootloader, only your music.
--- Quote from: martel on September 05, 2015, 02:37:01 PM ---The internal drive mounted this way shows as a drive without any partition table. But the device seems to be read only and the player disconnects itself from USB when written to (gives I/O errors) and refuses to cooperate with Linux afterwards (see dmesg output at the end). Do not even try to re-create the partition table using fdisk or similar tools - it cannot be done and as far as I can tell it is not supposed to be done anyway.[/b] This low-level device mounting mode on Clip Zip seems practically useless for end users since it does not work as a "normal" drive. (Maybe the real drive/file system starts at some offset within this "device"?)
--- End quote ---
That happens when the player boots without the NAND responding. You can't write to that space because theres nothing there.
--- Quote from: martel on September 05, 2015, 02:37:01 PM ---I intentionally wrapped "frozen" and "corrupted" in quotes because I managed to recover the player from this state. I simply powered the device to boot OF and I left it "frozen" on the Sansa logo boot screen. It eventually booted (after like 5-10 minutes).
--- End quote ---
When you rebooted the NAND responded this time, so you got a working player. Possibly it was just a one time thing, or the NAND may be wearing out or becoming unreliable.
Navigation
[0] Message Index
[*] Previous page
Go to full version