FiiO M3K screen is blank

[Njones]

command prompt says jztool not recognized as an internal or external command, operable program or batch file

[7o9]

You would have to download jztool. As you seem to be running Windows, you also need to install Zadig.

Links are at the bottom of this post: https://forums.rockbox.org/index.php/topic,53858.0.html

That post also says which buttons to hold to start the M3K in usb boot mode so jztool works.

[Njones]

Ran the jztool Debug and got the following errors.
libusb_control_transfer: Pipe Error
Bootfailed: -4

[amachronic]

Well, did you see anything happening on the M3K's screen? The bootloader file I gave you will go directly to the Fiio recovery so you should see some activity if it worked.

Sorry not to mention this before, but a successful run should look like this:

Code: [Select]

[  DEBUG] Opened device (0x561aec75d7d0, ID a108:1000)
[ NOTICE] Rockbox bootloader version: a27cf0cd16M-210802
[  DEBUG] Issued SET_DATA_ADDRESS 4093644800
[  DEBUG] Issued SET_DATA_LENGTH 00009896
[  DEBUG] Transferred 9896 bytes to device
[  DEBUG] Issued PROGRAM_START1 4093646848
[  ERROR] libusb_control_transfer: Operation timed out
[  ERROR] Boot failed: -4
[  DEBUG] Closing device (0x561aec75d7d0)
If you do not see "Issued PROGRAM_START1" then it didn't work. The error message after that is expected to happen. This bootloader file is "special" so the 1st stage will run the Fiio recovery directly instead of waiting for jztool to load the 2nd stage. So, when jztool tries to load the 2nd stage it will give an error like the one you got, even if the 1st stage succeeds.

Maybe you want to give it one last try and compare the output carefully. If you can't get the "PROGRAM_START1" message to show up it helps if you can copy and paste the full output from the command line, but I recall it's a bit annoying to do that on Windows (here is some instructions how to do that).

Now if it does boot but you see nothing on the screen, I guess your LCD is just broken and there's probably not much chance of fixing it without taking apart the M3K. (And even then, who knows if it's fixable.)

[Njones]

Tried the debug again.Not getting "Issued program start". I guess it's dead

[amachronic]

Do you get "Opened device"?

[Njones]

I get Opened device & Closing Device

[amachronic]

So it's definitely connected in USB boot mode but it sounds like it isn't able to transfer any data. Are there any SET_DATA_ADDRESS or SET_DATA_LENGTH messages? What about "Transfered XXX bytes to device" messages?

You mentioned a system restore point -- maybe you rolled back to a time before you installed the USB driver? If so then you need to redo the installation with Zadig.

If you're sure the driver is installed and you still have the problem then perhaps try another USB cable in case the one you used happened to be bad.

PS. sorry for the late reply.

[Njones]

I used Zadig to install drivers. X and box symbol appear in the eject safely list. Just to be sure, The file  i"m using to debug is  boot-fiio-recovery.m3k.
Right now besides x and box symbol, It now has a drive letter assigned to it.
Device was finally recognized as Fiiom3K. Did the CMD Debug again. This time it shows[  DEBUG] Opened device (0x561aec75d7d0, ID a108:1000)
[ NOTICE] Rockbox bootloader version: a27cf0cd16M-210802
[  DEBUG] Issued SET_DATA_ADDRESS 4093644800
[  DEBUG] Issued SET_DATA_LENGTH 00009896
[  DEBUG] Transferred 9896 bytes to device
[  DEBUG] Issued PROGRAM_START1 4093646848
[  ERROR] libusb_control_transfer: Operation timed out
[  ERROR] Boot failed: -4
[  DEBUG] Closing device (0x561aec75d7d0
This is your example that I copied the only difference is different Numbers listed

[Njones]

If that looks good, what is the next step? The m3k is still connected to the computer . Slider an buttons are still li up and top of screen is still faint lines.

[amachronic]

Thank you, it's definitely working to load the file so when the screen turns on, it should be in firmware update mode and flashing the original firmware.

If the SD card isn't plugged in or it can't find M3K.fw it will sit there waiting until you put the card in and it finds the update file. If you just copy M3K.fw to the root of an SD card and put it in, it should go through with the update and reboot automatically.

Bad news is that if the LCD is malfunctioning during the update, it will probably not work in the 'normal' player either. If it's still not working after the update & reboot then I'm 99% sure it's not a software problem.

[Njones]

Screen still stays blank or faint vertical lines. The files I have on the SD card are .rockbox, boot-fiio-recoverym3k, fiiom3k-bootbin, m3k.fw. Should I have the dual bootloader too?

[amachronic]

The files on your card are right, it should have flashed. Turn it off and try powering it on normally. But since you are still getting artifacts on the LCD, realistically it's safe to assume this is a hardware problem and will not be fixed by reflashing firmware or bootloaders. I can't totally rule out the possibility it was induced by Rockbox (sorry if it was!) but that is unlikely, and pretty difficult to determine after the fact. Sorry I can't do more to help.

[Njones]

Thanks for your help. I will give it a nice burial