Sansa Fuze+

[kumy]

Hi,

(I post my message here, as it could be a good source for anyone else having the same trouble)

during my last firmware upgrade, I ran out of battery (shame on me, yet I was warned)...

Now, fuze+ won't boot anymore.

I've been able to boot it in HID_Recovery, and successfully load recovery.sb with imxtools/sbloader (so it's not totally dead).

Now, my question is how can I flash it again ? (with the patched firmware, or original)

could I just "dd" something like seen in posts #105/#106 ? (http://forums.rockbox.org/index.php/topic,26284.msg184559.html#msg184559)

Should It try to load [original]firmware.sb so the flash process will restart ?

What are your advices ?
Thanks

Edit:
Thanks to pamaury, my fuze+ is now recovered !

FTR, this is what we've done.

[sandisk-firmware.sb, is the OF]

$ wget http://download.rockbox.org/bootloader/sandisk-sansa/fuzeplus/bootloader-fuzeplus.sansa
$ ./mkimxboot -i sandisk-firmware.sb -b bootloader-fuzeplus.sansa -o recovery.sb -t recovery

press vol up (keep it down) then plug on USB

$ sudo ./sbloader 1024 recovery.sb
$ ./mkimxboot -i sandisk-firmware.sb -b bootloader-fuzeplus.sansa -o recovery.sb -t recovery

$ fdisk -l
then find which device is has ID 53

My result are:
Disk /dev/sdb: 15.9 GB, 15925772288 bytes
1 heads, 1 sectors/track, 31105024 cylinders, total 31105024 sectors
Units = cylinders of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *      109569    31105024    15497728    1  FAT12
/dev/sdb2            1025      101376       50176   53  OnTrack DM6 Aux3
/dev/sdb3          101377      105472        2048    1  FAT12
/dev/sdb4          105473      109568        2048    1  FAT12


So it's /dev/sdb2

$ sudo dd if=firmware.sb bs=512 seek=4 of=/dev/sdb2

Then unplug USB.
Boot one time onthe OF to end the flash process...

[pamaury]

Yes it is possible. If possible, it would be better to come on IRC. Otherwise I'll write down the procedure.

[megal0maniac]

I'm sorry, but it would probably be best if you wrote it down. I can check if you're on IRC every now and then, but I have no way of staying logged on throughout the day.

[alienkid10]

Pamaury: The CRT effect is GONE for me. I've been using BL V1 since I don't use an SD card and thus saw no need to update bootloader, but just now on a whim I thought I'd give it a shot, after the firmware update I booted to RB some stuff flashed on the top 6-7 lines of the screen then it went white for a fraction of a second then to the normal RB splash screen. I'm running with 7d54ff0 and BL V7 screen 2 with no CRT effect. No idea what in the boot loader would do it but it works!

[Mystos]

I am sorry for my bad English. I use the translator.

I have put today Rockbox on the Fuze +. Has found out the similar problem described in 12458. Internal memory and SD card  are not mounted in Windows simultaneously. If parametre USB Hide Internal Drive = YES - mounted internal memory. If USB Hide Internal Drive = NO - mounted SD card.

[gevaerts]

If parametre USB Hide Internal Drive = YES - mounted internal memory. If USB Hide Internal Drive = NO - mounted SD card.

Are you sure about this? "USB Hide Internal Drive = YES" should show only the SD card, not the internal memory...

[Mystos]

If parametre USB Hide Internal Drive = YES - mounted internal memory. If USB Hide Internal Drive = NO - mounted SD card.

Are you sure about this? "USB Hide Internal Drive = YES" should show only the SD card, not the internal memory...

Excuse me, I was mistaken.
You are right:
If parametre USB Hide Internal Drive = NO - mounted internal memory. If USB Hide Internal Drive = YES - mounted SD card.
Somebody works over the decision of this problem?

[megal0maniac]

If parametre USB Hide Internal Drive = NO - mounted internal memory. If USB Hide Internal Drive = YES - mounted SD card.

I can confirm this issue. Both drives show up fine in Linux, however.
Using Windows 7 SP1 x64

[Mystos]

I am sorry for my bad English. I use the translator.

I do not know where to say of suggestion on development of functional. I will write while here.

Whether it is possible to add such function: when pleer is blocked the buttons of adjusting of volume were executed by the functions of "Play" and "Pause". This possibility must be in options (on/off). It would enable to put pleer on a pause not taking out him. It is not very enough now.

[buckminster]

I noticed that the FFWD and Rewind buttons don't function properly during playback when the backlight is off and "First button press turns on backlight" is set to No. I'll hear a click for the key press and the backlight turns on, but I'll have to press the button again for it to FFWD or Rewind. Other button functions work as expected.

Don't know if this has been posted before and/or if this is a RB issue or specifically Fuze+. I tried to search here and under the bug tracker.

[mysiak]

I noticed that the FFWD and Rewind buttons don't function properly during playback when the backlight is off and "First button press turns on backlight" is set to No. I'll hear a click for the key press and the backlight turns on, but I'll have to press the button again for it to FFWD or Rewind.

Just tried FFWD/REWIND buttons with backlight off and it works fine for me - just one key press needed (version 9acd702M-120214).

However I am observing another issue with charging - if I connect rockbox in MSC/HID mode to the PC, battery is slowly discharging. I have to use USB connection via original firmware or plug in rockbox with some button pressed to charge the battery. Is anyone else observing this?

I would have one more question/request - is it possible to decrease the sensitivity of "ON/OFF" button (the one on top of the player)? It is very easy to accidentally press the button and player turns ON in a pocket. Maybe increasing the required button press time from few miliseconds to 3 seconds for example would help (similar way as with shutdown - we need to keep key pressed for few seconds to power off the player).

[pamaury]

Hello,
no it's not possible to change the sensitivty of the power button unfortunately. I agree it's far to sensitive to me but there no workaround.
I'll have a look at the battery issue in MSC/HID mode, it should not discharge.

[mysiak]

Maybe some dirty workaround could be feasible - first press turns ON the player, but bootloader would wait for another key press, either power button again or some other button to load rockbox FW, otherwise it would power off..?

Regarding the charge/discharge - it seems that with MSC/HID connection it charges the battery to 100%, but does not keep it charged at 100% and it slowly decreases (I noticed that battery was around 80% after connected for 5 hours).

Edit: btw. thanks for a very quick reply

[pamaury]

I prefer to avoid such dirty tricks if possible. But yeah, by changing the bootloader, one could perhaps require that power be pressed for 1 or 2 seconds.
Interesting, so the problem might be that when the charge is finished, I incorrectly configure the power control to use the usb source.

[mysiak]

If it's possible, could you please consider change of bootloader startup behavior for longer button press? It would really help as we don't have hardware lock button. Or maybe you could offer two types of bootloader and user will choose what he prefers?

Small update about battery:
Discharging seems to be also in "player" mode. I had ~90% of battery when I connected player to PC (button pressed) and watched the battery in debug menu. It went to 100% with status "charging", then status changed to "discharging" and it started to slowly decrease (approximately -0.002 V per minute).. After re-connection, player charged to full capacity again.