Bricked Sansa View 16GB after 4 hours

[speedeep]

I received my Sansa View 16GB last night in the mail. I unpacked it and connected it to my Dell Inspiron 1420N running Ubuntu 7.10 (factory loaded and updated to current versions of all packages.) I installed mtp-tools, libmtp, libmtp-dev, libusb. Couldn't get MTP to work, so I switched to MSC/UMS mode. The device showed up as a mounted drive (/media/SANSA VIEW/, who put a "space" in the middle of that name? Why?!?) I successfully copied, then rsync'd mp3s onto the device and they played fine. I copied a bunch of videos. They didn't work, but I figured out that I needed to convert them to MP4. I saved a 1024x768x24bpp JPG image off my web-based photo album (via Firefox) directly to the PICTURES directory and saved it as whatever.jpeg. I couldn't see the image in the player, so I reconnected as MSC/UMS and renamed the file from whatever.jpeg to whatever.jpg. I unmounted, unplugged the device, and it booted to the splash screen.

From then on, the player would not boot past the splash screen. All functions of the player and connectivity to the storage is non-functional.

SanDisk Tech Support walked me through upgrading the firmware in recovery mode (it took) but no matter what, the player wouldn't boot past the splash screen.

I'm returning the player to Amazon for a replacement, but can someone please tell me this player isn't this delicate? I unmounted the filesystem before disconnecting each time. There were no transfers running when I unmounted/disconnected. Linux/View users: Am I doing something wrong here? I'd prefer not to repeat this performance with the replacement View...

[CrowdAds]

[advcomp2019]

Have you tried the "Sansa.fmt" and with the firmware in recovery mode? I am not sure if that will work with the View like the e200v1.

Plus could you post your version.txt file if you could too?

[speedeep]

The hardware is on a truck back to Amazon. While troubleshooting with SanDisk TS last night, they had me copy the latest 01.02.09 firmware on the recovery partition. It took (at least the Version.TXT file was updated) but the player still wouldn't boot beyond the splash screen.

[advcomp2019]

OK, if you have another issue, you come here and see if anyone could help you.