Installation / Removal > Other - Installation/Removal
Surfans F20 v3.4 - jztool doesn't seem to activate the screen
jdharper:
Hello!
Over the weekend I tried to install Rockbox on a new Surfans F20. It shipped with firmware update 3.4, which is newer than what's available here. I've emailed Surfans support to see if they'll give me the stock 3.4 firmware, but in the meantime I tried to get into the bootloader menu with jztool and had no success. I tried this on two computers, one Windows and one Linux, and I tried it from both the chrome tool and the command line. In all cases, it would LOOK like it was working--no error messages from jztool, and the device would show up in device manager/lsusb as expected. But the screen stayed dark on the device.
I think that this version of the hardware may have a different LCD screen than previous models, maybe one that requires a different command to turn on? It looks to me like it's connecting but the screen isn't lighting up for me to actually do any commands.
I'm not sure how to fix that, but figured this is the right place to report the issue.
dconrad:
Ok, thanks for the heads up. Once we get a 3.4 update file we can figure out what may be different. So you put it in usbboot mode (the blue led is on, screen is off), plug it in and run jztool to send the bootloader and... nothing happens?
jdharper:
Correct. I load it in USB mode, the light is blue and the screen is off. Then I try to load the bootloader, the blue light goes off, but the menu never appears.
I have to push the power button for several seconds, wait, then push the power button again for several seconds again to make it turn back on in regular mode. Between that and the lack of errors, I'm assuming that it's loading the menu but never actually displaying it.
Here's the log from the jztools.js website:
Downloading: 'files/bootloader/aigo/native/221029-b4e7c60c6d/bootloader.erosq'
File downloaded, 92160 bytes
Extracting bootloader-info.txt...
Extracting spl.erosq...
Extracting bootloader image...
Found bootloader.ucl (v1 format)
Validated bootloader package.
Bootloader version: b4e7c60c6d-221029
Saving bootloader...
Asking for device...
Opening device...
Claiming device interface...
Loading stage1 (SPL)...
Pausing for SPL to come up...
Loading stage2 (bootloader)...
Closing device...
Done!
speachy:
--- Quote from: jdharper on October 08, 2024, 09:06:18 AM ---Here's the log from the jztools.js website:
Downloading: 'files/bootloader/aigo/native/221029-b4e7c60c6d/bootloader.erosq'
--- End quote ---
It appears that this jztools website is out of date.
It should be using the 20240908-a7cfee640d build, and there's also a different bootloader for different HW generations.
Strictly speaking it shouldn't be using a specific version at all; there are symlinks in place that will always point at the latest bootloader release.
dconrad:
--- Quote from: jdharper on October 08, 2024, 09:06:18 AM ---Correct. I load it in USB mode, the light is blue and the screen is off. Then I try to load the bootloader, the blue light goes off, but the menu never appears.
I have to push the power button for several seconds, wait, then push the power button again for several seconds again to make it turn back on in regular mode. Between that and the lack of errors, I'm assuming that it's loading the menu but never actually displaying it.
Here's the log from the jztools.js website:
Downloading: 'files/bootloader/aigo/native/221029-b4e7c60c6d/bootloader.erosq'
File downloaded, 92160 bytes
Extracting bootloader-info.txt...
Extracting spl.erosq...
Extracting bootloader image...
Found bootloader.ucl (v1 format)
Validated bootloader package.
Bootloader version: b4e7c60c6d-221029
Saving bootloader...
Asking for device...
Opening device...
Claiming device interface...
Loading stage1 (SPL)...
Pausing for SPL to come up...
Loading stage2 (bootloader)...
Closing device...
Done!
--- End quote ---
Speachy got to it before me, but:
Ah, I see. It looks like the web jztool is automatically pulling the old bootloader from an old url which appears to not exist anymore... Although you would think it should throw an error in that case. It's also curious that the blue light goes out though, that should stay on. Any chance you could use the desktop command line jztool? There's a chance that something is going sideways with the web jztool, and the hardware might not be changed (fingers crossed!). I would try loading this bootloader file.
BTW, thanks for noticing the version changed and being proactive about it 8)
Edit: Just saw that you already said you had tried the command line jztool
Navigation
[0] Message Index
[#] Next page
Go to full version