Sansa Fuze+

[Trailblazer7818]

I've been using the new developer firmware for the past few days, but now the unit is locked up, and Is now unusable no matter what I do. Is there any way to delete the RB firmware, so that I can reinstall? Please advise..

Thanks!

[pamaury]

It has been explained several times in this thread: reboot to the OF using volume down and reinstall the OF.

[Trailblazer7818]

I guess I didn't explain myself all that well... When I connect the device to the computer, it won't boot. It shows the bootloader id, and that's it. When I unplug the device from the computer, it turns off. Thinking the battery might be low, I left it plugged in for a couple of hours, and got the same result. When I remove the device from the computer, it shuts off, and will not restart, so there is no way to boot into either firmware. When connected to the computer, I can see the files through explorer even though the unit remains dark, other than the boot loader id. The Rockbox utility also sees and auto detects the unit. I tried reloading the FW, and it appeared to load correctly according to the utility, but once again, when I removed the device from the computer, it shuts off and cannot be turned back on. I was wondering if you could tell me if there's a way to manually remove the Rockbox FW, by telling me in detail which files to delete, and hopefully then I can reinstall either the original FW, or preferably the Rockbox FW. As I mentioned, I can see all the files on the device in Explorer. Any help regarding this would be greatly appreciated.

Thanks!

[pamaury]

You do not read what I wrote: the bootloader will normally boot the OF if you hold volume down and press longer a few seconds. If you see the bootloader, it means you already missed the step where you could boot the OF. If the device has low battery, just hold volume down and plug the usb cable while holding it.

As for the boot problem: could you at least tell us the bootloader error printed ? That will help us fix the problems if there is one.

[halonachos117]

I do wonder if this is a Rockbox issue. There have been a number of people complaining about this problem on the SanDisk forums, most of whom don't even have Rockbox. It seems to be some weird Fuze+ issue, possibly caused by poor manufacturing or something. It has been suggested numerous times that users test there Fuze+'s in the parking lot to make sure the unit works.
Post Merge: March 07, 2012, 07:46:54 PMAlso, there's been a random freeze problem that's been killing me for some time. Has anyone else had this? FS# 12609.

PS: I'm sorry if this has been reported before, I couldn't find anything.

[Trailblazer7818]

I was able to manually delete everything, and successfully reload the RB firmware, and now all is well. Thanks for all your help.

Cheers!

[buckminster]

Also, there's been a random freeze problem that's been killing me for some time. Has anyone else had this? FS# 12609.

I do get random lock ups (music stops, touchpad unresponsive, screen is black) while listening to music sometimes (less than 5 times in the last few dozen times I've played used it), but I haven't analyzed it since it doesn't happen often enough to determine a pattern.

[pamaury]

After some investigation, it seems that the radio freeze is caused by the chip failing to tune and thus the driver looping over and over trying to tune. I can avoid the freeze by exiting after a few failures but then the chip won't tune until it is stopped and restarted. I'm still looking for a solution... Interestingly, it seems related to the backlight. I suspect that when the backlight shut downs or starts up, there is some intereference which causes the chip to fail.

I have no clue for the playback lock up since it is looks so random.

[megal0maniac]

Interestingly, it seems related to the backlight. I suspect that when the backlight shut downs or starts up, there is some intereference which causes the chip to fail.

Perhaps someone could try and turn off the "fade in" or "fade out" setting on the backlight?
Dimming creates far more electrical interference than straight switching.
I'd try it myself, but strangely, my player isn't freezing at all...
It was freezing last time I used the radio(?)
Running d18a5ca-120304

[buckminster]

Perhaps someone could try and turn off the "fade in" or "fade out" setting on the backlight?
Dimming creates far more electrical interference than straight switching.

Doesn't make a difference for me. Glad that you found something out, pamaury. [wild speculation]If the backlight is causing interference for the radio chip, it might very well be causing the touchpad issue as well.[/wild speculation]

[megal0maniac]

I tried the fade thing, didn't make a difference for me either.

What I did find strange, is that the only time it would freeze was when I let it auto-scan the whole way through without pressing a button (the backlight time-out is slightly shorter than the time it takes to complete a scan)
If I press a button during the scan to keep it awake, then it doesn't freeze no matter what I try.

Does anyone have a reliable way to reproduce the freezing issue?

[alienkid10]

have it in the mode where you can just tune. (not preset mode)
pick a station
leave player alone until backlight goes off
wake player
be stuck.

[megal0maniac]

Okay, that works.
But if you go back to the main menu, then it's fine.
Or if you go back to the main menu and then to the tuner then it doesn't freeze after a BL cycle (sometimes)
Or it does freeze as soon as you go back to tuner (without a BL cycle)
Or it freezes while going through region selections in the tuner settings (as this changes the allowed ranges and shifts the tuned frequency)
The last two scenarios don't require a BL cycle and don't happen every time.

Hate these bugs...

[alienkid10]

Let's stop flooding the thread and make a flyspray (which I always read "flys pray") bug.
Meantime I haven't found any other bugs.

[metaphys]

pamaury just released a new bootloader and I updated the wiki page.
V9 add support for charging the battery in booloader mode (i.e if you plug the device while rockbox isn't running