I had lollipop running without real issues for a while. After a complete battery drain, I put it on the charger. Upon trying to turn the device on, it hung on the Google screen showing an unlocked padlock at the bottom.
I tried to see how far I could go, and can boot into fastboot but no further.
I thought I would start the usual flashing process from the start by bringing it back to stock and then back to root. Initially the device was unlocked. I locked it with "fastboot oem lock" the rebooted to bootloader. Now when I run "fastboot oem unlock", the unit freezes up when I select Yes to confirm unlocking the bootloader.
Code:
C:\Android>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 898.264s
Previously, before I locked it, when I tried to flash recovery & bootloader, I received "FAILED (remote: flash write failure)" and "fastboot FAILED (remote: Partition table doesn't exist)" errors. Now, I cannot try to reflash because I can't get unlocked ("FAILED (remote: Bootloader is locked.)")
Current status:
Code:
C:\Android>fastboot-toolkit oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) SB=Y
OKAY [ 0.016s]
finished. total time: 0.016s
integramodder said:
I had lollipop running without real issues for a while. After a complete battery drain, I put it on the charger. Upon trying to turn the device on, it hung on the Google screen showing an unlocked padlock at the bottom.
I tried to see how far I could go, and can boot into fastboot but no further.
I thought I would start the usual flashing process from the start by bringing it back to stock and then back to root. Initially the device was unlocked. I locked it with "fastboot oem lock" the rebooted to bootloader. Now when I run "fastboot oem unlock", the unit freezes up when I select Yes to confirm unlocking the bootloader.
Code:
C:\Android>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 898.264s
Previously, before I locked it, when I tried to flash recovery & bootloader, I received "FAILED (remote: flash write failure)" and "fastboot FAILED (remote: Partition table doesn't exist)" errors. Now, I cannot try to reflash because I can't get unlocked ("FAILED (remote: Bootloader is locked.)")
Current status:
Code:
C:\Android>fastboot-toolkit oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) SB=Y
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
Same exact thing happened to mine last week. I've followed the exact same steps as you with no luck..Maybe some has recovered from this?????
zerocool00 said:
Same exact thing happened to mine last week. I've followed the exact same steps as you with no luck..Maybe some has recovered from this?????
Click to expand...
Click to collapse
So was this a Google OTA update that caused this?
integramodder said:
So was this a Google OTA update that caused this?
Click to expand...
Click to collapse
Anyone else have any suggestions?
I've got a Moto G4 Play and with LineageOS I can't make any calls. So I wanted to downgrade the firmware to the stock-firmware which I downloaded here: bit.ly/2lvXpgC. There are instructions how to downgrade the firmware here: bit.ly/2kPAuNS.
The first command - "fastboot oem fb_mode_set" - is accepted.
But the second command - "fastboot flash partition gpt.bin" - produces the following:
"target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.442s"
Can anyone tell me what I'm doing wrong here?
[EDIT]:
I simply run the other commands and ignored those that failed. Now my Phone boots into the bootloader and if I press start, I get into an endless boot-loop. If I start the TWRP recovery-image with "fastboot boot twrpxyz.img", the device restarts and stops in the bootloader, i.e. the recovery-mode isn't started.
Can anyone help me from here?
[EDIT2]:
I've got the problem: I tried to boot the bootloader without a battery in the phone and just the USB-cable attached. So I suspected this was also the problem when flashing the stock-image and I run through tge commands to install it. I simply ignored that "fastboot flash partition gpt.bin" didn't work (according to someone who had the same problem here in this boadd) and every other command was successful. The phone booted the stock firmware and everything is fine now.
Thanks you so much
Work fine for me, only i found the solution here, seriously, thanks!!
GOD BLESS YOU
Hi guys!
I hope you can help me, since I've looked everywhere but can only find people with similar but not the exact same problem.
I tried flashing TWRP in order to migrate to a custom ROM. I am currently running official 7.1.1.
When I try to flash twrp (tried several versions) the command window shows me this:
c:\adb>fastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (14522 KB)...
OKAY [ 0.049s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.068s
I tried using Moto fastboot as well but with the same result. I'd really appreciate your help. Please note, that I am not a pro like most you guys so I might have follow-up questions
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Code:
fastboot boot twrp.img
?
Artim_96 said:
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Code:
fastboot boot twrp.img
?
Click to expand...
Click to collapse
Yes, I am sure that I am using the right image. I tried several, always checked that they were for addison.
I also unlocked the bootloader in developer options - although now that you mention it: in the fastboot screen it still says oem_locked. So maybe that is the problem?
c:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.054s
Okay, I managed to unlock the bootloader with the unlock key I got from Motorola.
Now when I try to flash it says:
c:\adb>fastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (14522 KB)...
OKAY [ 0.049s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.280s]
finished. total time: 0.330s
Come ooooon
ischariot_pasadelski said:
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Yes, I am sure that I am using the right image. I tried several, always checked that they were for addison.
I also unlocked the bootloader in developer options - although now that you mention it: in the fastboot screen it still says oem_locked. So maybe that is the problem?
c:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.054s
Click to expand...
Click to collapse
Oh Jesus... Bootloader unlock is not just the option in Dev settings. Google it, you'll find a website from Motorola that guides you through the process and provides you with everything necessary
Yes, I did that by now as I said in the post before. Sorry, but I'm a beginner
Now it says that the image is not signed or corrupt. IDK what to do anymore.
Booting in TWRP works but when flashing Lineage from SD card I get the error:
recv error on unevent
and
failed to mount data.
I wiped everything using TWRP and I also tried to use another version of TWRP, so a corrupted file can't be the problem.
I figured it out.
I had to restore the file system by only checking the "System" box when wiping with TPWR - just in case anybody else has the same problems.
So a factory data reset solve the problem? Having your first issue with moto e5 cricket and you can't unlock three bootloader
Artim_96 said:
Oh Jesus... Bootloader unlock is not just the option in Dev settings. Google it, you'll find a website from Motorola that guides you through the process and provides you with everything necessary
Click to expand...
Click to collapse
well, i had it unlocked via the settingsbutton and after read this here , via the website where you can get the 20 bits code, but it is the same result with a code that is the same as the adb devices code, just as before! Only thing that is changed is a warning when you starts the phone up.
ischariot_pasadelski said:
Yes, I did that by now as I said in the post before. Sorry, but I'm a beginner
Now it says that the image is not signed or corrupt. IDK what to do anymore.
Booting in TWRP works but when flashing Lineage from SD card I get the error:
recv error on unevent
and
failed to mount data.
I wiped everything using TWRP and I also tried to use another version of TWRP, so a corrupted file can't be the problem.
Click to expand...
Click to collapse
Can you tell me how you got the phone twrped, pls?
Hi!
I've been following this thread and everything gone fine. I converted to global, then did OTA and after that I've relocked my bootloader. Everything is okay but I would like to root my phone now. Hence I need to unlock bootloader again but old unlock code seems not working and I cannot get new unlock code via fastboot.
After trying with old unlock code (which I get when I was on Tmobile) I got this output:
Code:
fastboot flash cust-unlock unlock_code.bin
Sending 'cust-unlock' (0 KB) OKAY [ 0.013s]
Writing 'cust-unlock' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
After this failed attempt I thought that I will try to get a new unlock_code.bin from OnePlus but I've met another problemwhen I was trying to get unlock code which we need then paste on OnePlus site:
Code:
fastboot.exe oem get_unlock_code
FAILED (remote: 'Unknow command')
fastboot: error: Command failed
Any ideas what can I do right now to unlock bootloader once again ?
EDIT:
SOLUTION:
If someone will be in the same situation. You don't need to flash unlock_code.bin for another time. You just simply do:
Code:
fastboot oem unlock
and it's working as champ. Remember it will wipe your phone.
Hello, I am trying to unlock the bootloader of my moto g60 but I have a problem to get the bootloader data with the fastboot oem get_unlock_data command, every time I try it returns the following error
c:\platform-tools>fastboot oem get_unlock_data (bootloader) Failed to get unlock data. OK [0.008s] Finished. Total time: 0.008s
I have tried to restore the firmware with RSA, but it is still the same no matter how many times I try, I always get the same error, if anyone knows of a solution, or has had the same problem and has solved it, please explain to me what I can do.