Rockbox Technical Forums

Installation / Removal => Manual Installation => Sandisk - Installation/Removal => Topic started by: AmazingAlliteration on March 24, 2016, 12:38:46 AM

Title: Sansa Clip+ Installation Problems-Stuck on 'Bootloader USB mode' [SOLVED]
Post by: AmazingAlliteration on March 24, 2016, 12:38:46 AM
Hi, my name is Michael, and I"m trying to install Rockbox on my Sansa Clip+. My player is bricked right now after an issue during Rockbox installation. My player is fixed and Rockbox is successfully installed, here's how it happened.

General Information:
PLAYER: Sansa Clip+
CLIP+ FIRMWARE: 01.02.16
ROCKBOX VERSION: 3.13
ROCKBOX THEME: Cliplined
OS: Windows XP, Windows 10

PROBLEM:

I downloaded the most recent stable version of the Rockbox utility. I plugged in my Clip+ and used the Rockbox utility to manually select a mountpoint and my player. I chose the theme I wanted and the latest stable version of Rockbox, 3.13. I installed Rockbox, and unplugged my player when it was done installing.
After turning my Clip+ on, my player shows a screen that has the Rockbox logo and 'Boot 4.0' on it. My Sansa Clip+ then goes to the 'Plug USB cord' screen. When I plug it into my computer, the Clip+'s screen changes to say 'Bootable USB mode', but it isn't recognized by RockboxUtility and nothing happens to the player. If I unplug my player the player changes to say '*Panic* Mount: 0' after a couple minutes. This repeats every time I turn on my Clip+.
No matter what I do the RockboxUtility will not recognize that the player is plugged in, and I cannot see the player in My Computer, so I can't access the player at all, in any way.

FAILED SOLUTIONS:

1. Holding down the Select button and plugging it into the computer causes it to turn on to the Rockbox logo screen and to eventually get stuck on the 'Bootloader USB mode' screen as if it was turned on normally. I still can't access it from My Computer.

2. Re downloading the Rockbox utility on a new computer and trying to access the player on that computer did not change anything at all.

3. Holding down the Left button and turning it on normally caused it to load to a screen that said 'FAT is corrupted connect player to PC and'. After showing this screen for a few seconds it turned off again.

WORKING SOLUTION:

Plugging the player into the computer and then holding down Left and turning it on allowed it to be recognized by the PC. I then wiped the external SD, the internal memory, and formatted the internal Clip+'s memory. When that was done I unplugged the player from my computer. I plugged it back in, and it was recognized by the Rockbox utility. I reinstalled Rockbox with the Cliplined theme, and when I ejected my player once everything was done installing it booted with Rockbox normally.
It now turns on and off, is recognized by the computer, and boots seamlessly into ROckbox every time. Hooray!
Title: Re: Sansa Clip+ Installation Problems-Stuck on 'Bootloader USB mode'
Post by: Mihail Zenkov on March 24, 2016, 04:34:45 AM
When player off - try hold select (middle button) and connect it to usb. Then try check disk for errors.
If disk is ok, download latest build (http://build.rockbox.org/data/rockbox-sansaclipplus.zip) and unpack it to disk.

Also you can try boot to OF (when player off, hold left button and press power).
Title: Re: Sansa Clip+ Installation Problems-Stuck on 'Bootloader USB mode'
Post by: AmazingAlliteration on March 24, 2016, 10:40:42 AM
Thanks for the advice, I'll experiment and see what happens.

EDIT: Holding down the Select button and plugging it into the computer causes it to turn on to the Rockbox logo screen and to eventually get stuck on the 'Bootloader USB mode' screen as if it was turned on normally. I still can't access it from My Computer.

EDIT 2: Holding down the Left button and turning it on normally caused it to load to a screen that said 'FAT is corrupted connect player to PC and'. After showing this screen for a few seconds it turned off again. Plugging the player in and then holding down Left and turning it on, however, allowed it to be recognized by the PC.

EDIT 3: Everything is fixed and working properly now, I'll update the OP with the solution. Thanks for all the help Mihail!