Third Party > Unsupported Builds
SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
username_already_taken:
--- Quote from: Bilgus on November 22, 2020, 10:07:13 AM ---I don't think 2020 bootloader was released yet did you build it yourself?
The final thing is to re-make the redirect file rockbox_main.clip+ either completely empty or a single \
--- End quote ---
I should have mentioned my screen is dead, I need to use voice navigation.
I test that I'm not using the SD card by comparing mtimes on files in the internal and SD firmwares (the latter never updates), and by renaming the internal folder (the player stops working).
I also mispoke, I'm not using the 2020 bootloader because the latest one is from 2019, this is what I'm using:
https://download.rockbox.org/bootloader/sandisk-sansa/clipplus/
https://download.rockbox.org/bootloader/sandisk-sansa/mkamsboot/linux-x86-64/
OF 01.02.16
Rockbox dev build with working voice file
Doing a manual installation because my Rockbox utility is outdated and the new binary doesn't run on Debian buster.
I tried both the 0 bytes and 1 byte forward slash variants, not backslash though, I assume that was a typo since everywhere else says /?
I will try the new files and report back soon, thanks for helping!
EDIT: quick update: the rockbox_main.clip+ file uploaded in that link is 2 byte with newline, I will fix it before properly testing
Bilgus:
yes sorry it is a single forward slash, the \n won't matter if there is already a / in the file it just matters for empty ones IIRC
Go ahead and install that new bootloader just copy to the internal drive and reboot into the sansa firmware, it shuts off the device when finished so rather than risk turning it off too early just plug / unplug the USB after 15 mins and see if it boots and connects to USB
(since your screen is out)
username_already_taken:
Still no luck with the downloaded clppa.bin and firmware, exact same behaviour.
Works perfectly from internal flash .rockbox/, not at all when internal flash directory is renamed. The .rockbox/ on the SD card is a straight copy of the one in internal flash, and a 1 byte / rockbox_main.clip+ is present on the SD root.
Not sure if it matters any but after doing manual bootloader installation, the clppa.bin file is left on the root of internal flash after installing.
Don't know if that's supposed to happen, or if it means the bootloader wasn't installed properly and despite all these attempts I'm still running the old bootloader.
Is there an easy way to debug this with voice operation? If not, I'll give up and keep on using the internal flash, no big deal.
username_already_taken:
--- Quote from: Bilgus on November 23, 2020, 12:46:23 PM ---Go ahead and install that new bootloader just copy to the internal drive and reboot into the sansa firmware, it shuts off the device when finished so rather than risk turning it off too early just plug / unplug the USB after 15 mins and see if it boots and connects to USB
(since your screen is out)
--- End quote ---
I've just been copying, ejecting and powering off with gnome-disks, unplugging and waiting a minute.
Do you mean I need to boot holding left to call the OF, then wait?
EDIT: that was definitely it, rebooting into OF, waiting, then plugging in the USB cable and mounting shows a bunch of OF directories on the flash root and no more clppa.bin. And now it works, SD firmware is being used as expected!
Thanks again for the help and for your contributions to Rockbox in general.
Bilgus:
If clppa.bin is still there then it did not update
word of warning you must rename to clppa.bin before copying it to the internal drive
if you do the rename after it will not pick it up
to update it should just be copy the file power off then hold left arrow and power on
edit:
Good to hear glad you got it working
and Thanks :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version