I'm trying to unbrick my 11 LE, but whenever I try to do anything with it, it gives me an error like:
FAILED (Write to device failed (Too many links))
FAILED (remote: 'Token Verify Failed, Reboot the device
')
FAILED (Write to device failed (no link))
All drivers are installed, don't know what to do...
Already tried to use USB 2.0 port, 2 different PC's (all Intel) and 2 different USB cables from Xiaomi.
Bootloader is unlocked, I use Windows 11 x64.
Closed! Fixed with using rear USB 2.0 port of my PC.
Related
Hello everyone.
I am having this error while trying to flash the latest factory image.
Adb and fastboot seem propoerly configured as I have adb devices and fastboot devices working.
sending 'bootloader' (3911 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time 5.011s
rebooting into bootloader...
FAILED (status read failed ( Too many links))
finished. Total time: 117.384s
Any help would be appreciated, because I am lost on this one.
SDK is fully updated and doing everything as I did to flash 5.0.1
Thanks in advance.
Can't help with ADB or Fastboot but I can suggest dirty flashing this stock, rooted rom by scrosler found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Worked great for me. Good luck!
Mine failed the first couple of times too, but on the third attempt it went through. However, it turns out that I had failed to turn on the ADB bridge on the first one, and I guess it was still coming up on the second.
Adb has nothing to do with this. Fastboot is what's used when you're in the bootloader.
Have you tried a different cable/USB port?
yosmokinman said:
Adb has nothing to do with this. Fastboot is what's used when you're in the bootloader.
Have you tried a different cable/USB port?
Click to expand...
Click to collapse
Very true, except that it uses adb to initially reboot the tablet into fastboot mode.
It would probably skip that step if you were already in fastboot mode, but if the OS is running, the flash-all script will attempt to restart the device by running adb reboot bootloader.
That said, if ADB isn't working, checking the cable and drivers is the next step.
Getting into the bootloader doesn't require adb. Use the hardware buttons.
So through a series of attempts to root the latest MM software ive found myself with nothing but fastboot to boot into, but whenever i try to use a command such as boot for example i get:
C:\android>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.560s]
booting...
And it just hangs at booting forever. It does this every command. If i unplug the phone i get:
FAILED (status read failed (Too many links))
Any idea why it's doing this?
I'm on windows 7 with the drivers for my device along with google drivers installed. I've tried two different computers with the same results.
boho555 said:
So through a series of attempts to root the latest MM software ive found myself with nothing but fastboot to boot into, but whenever i try to use a command such as boot for example i get:
C:\android>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.560s]
booting...
And it just hangs at booting forever. It does this every command. If i unplug the phone i get:
FAILED (status read failed (Too many links))
Any idea why it's doing this?
I'm on windows 7 with the drivers for my device along with google drivers installed. I've tried two different computers with the same results.
Click to expand...
Click to collapse
Do you have access to download mode?if yes, flash back to kit Kat.bit If you are stuck at this Fastboot,you are left with only option of getting to Qualcomm 9008 mode.and flash from that.because this Fastboot fail has no solution.
Jahanzaibawan said:
Do you have access to download mode?if yes, flash back to kit Kat.bit If you are stuck at this Fastboot,you are left with only option of getting to Qualcomm 9008 mode.and flash from that.because this Fastboot fail has no solution.
Click to expand...
Click to collapse
Thanks, I'll try the qualcom fix.
Hey, im trying to unlock the bootloader on a LMG710EM but everytime i try to flash the unlock.bin file it gives me the error FAILED (status read failed (Too many links)) and then the phone just reboots to os.
I've tried getting the unlock.bin again, and it doesnt work, tried all usb ports and different cables, no luck.
This is the error and command i use:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlock unlock.bin
target didn't report max-download-size
sending 'unlock' (1 KB)...
FAILED (status read failed (Too many links))
finished. total time: 5.925s
So I got unlock code from motorola, all good. But, when I go to do the unlock I get this error
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
This is on Win 10, Mac 11, and Ubuntu 20.
I enabled developer options, usb debugging, and oem bootloder unlock....
No clue What I am missing here....
3evils said:
So I got unlock code from motorola, all good. But, when I go to do the unlock I get this error
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
This is on Win 10, Mac 11, and Ubuntu 20.
I enabled developer options, usb debugging, and oem bootloder unlock....
No clue What I am missing here....
Click to expand...
Click to collapse
have you ever tried to reinstall the Stock Rom with Rescue and Smart Assistant (LMSA) from Lenovo and then try again to unlock the Bootloader?
make sure you use the latest adb/fastboot binaries
in my case I couldnt execute `fastboot reboot fastboot` because my adb/fastboot binaries were to old. I followed wiki.lineageos.org/adb_fastboot_guide.html to get the latest versions.
also have this problem, still can't figure it out
3evils said:
So I got unlock code from motorola, all good. But, when I go to do the unlock I get this error
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
This is on Win 10, Mac 11, and Ubuntu 20.
I enabled developer options, usb debugging, and oem bootloder unlock....
No clue What I am missing here....
Click to expand...
Click to collapse
Some distros will need you to run fastboot with a priviliged user. Try "sudo fastboot".
Hi. iv'e been trying to unlock the bootloader on my device in order to install custom rom but i get this error everytime i use fastboot flashing unlock:
FAILED (remote: 'Command not support: the display is not enabled')
fastboot: error: Command failed
And yes i checked that OEM Unlock is enabled and USB Debugging aswell. I also tried typing fastboot oem unlock but it says:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
any ideas why unlocking doesn't work? thanks.
I have the same problem
Is there anyone who can help??
I refresh, is there anyone who can help?
I refresh, is there anyone who can help?
I refresh, is there anyone who can help?