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?
Related
Hi All.
I just bought the leeco pro 3 and want to unlock the bootloader. I followed the steps outlined in "X727 (US Model) Persistent bootloader unlock from 5.8.019s". I turned on USB debugging, permanently added USB device, and turned on the "allow oem unlocking option". Then, i rebooted to fast boot and tried the following commands and received an error.
Code:
:~$[B] fastboot oem device-info[/B]
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
:~$ [B]fastboot oem unlock-go[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.008s
:~$ [B]fastboot oem unlock[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.007s
My phone came with 5.8.020S (I think) and I tried the above steps with that version. Then i updated to 5.8.021S and tried again and received the same issue. I checked for more updates but none were found.
I am sure this issue has been solved somewhere but I just want to make sure I do not brick this device. Please help.
Developer Options ---> usb debug ---> open ..
Developer Options ---> Oem unlock ---> open ..
Have you enabled them?
lazye53 said:
Developer Options ---> usb debug ---> open ..
Developer Options ---> Oem unlock ---> open ..
Have you enabled them?
Click to expand...
Click to collapse
Thanks for the reply.. Yes. Both of those options are on. I have tried multiple times to turn them off and on and redo the unlock at fast boot, but i get the same error
sagarc88 said:
Hi All.
I just bought the leeco pro 3 and want to unlock the bootloader. I followed the steps outlined in "X727 (US Model) Persistent bootloader unlock from 5.8.019s". I turned on USB debugging, permanently added USB device, and turned on the "allow oem unlocking option". Then, i rebooted to fast boot and tried the following commands and received an error.
Code:
:~$[B] fastboot oem device-info[/B]
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
:~$ [B]fastboot oem unlock-go[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.008s
:~$ [B]fastboot oem unlock[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.007s
My phone came with 5.8.020S (I think) and I tried the above steps with that version. Then i updated to 5.8.021S and tried again and received the same issue. I checked for more updates but none were found.
I am sure this issue has been solved somewhere but I just want to make sure I do not brick this device. Please help.
Click to expand...
Click to collapse
For 5.8.021S, go to page 26 ....
sagarc88 said:
Thanks for the reply.. Yes. Both of those options are on. I have tried multiple times to turn them off and on and redo the unlock at fast boot, but i get the same error
Click to expand...
Click to collapse
I had this issue also this I solved it.
Undo the OEM allow to unlock reboot then enable OEM to unlock bootloader.
Still had the problem.
I ended up flash the bootloader then then ran the bootloader unlock commander and it worked.
Sent from my LEX727 using xda premium
mchlbenner said:
I had this issue also this I solved it.
Undo the OEM allow to unlock reboot then enable OEM to unlock bootloader.
Still had the problem.
I ended up flash the bootloader then then ran the bootloader unlock commander and it worked.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
You need to flash 2 files via adb first, then run the unlock command.
I did it successfully for 021s
Sent from my LEX727 using Tapatalk
kukuteku said:
For 5.8.021S, go to page 26 ....
Click to expand...
Click to collapse
This worked perfectly!! Thank you very much.
Flashing Critical Locked
I'm just a dabbler in this stuff, but I think I understand everything required to get LineageOS on my LEX727. The problem is, in the process of learning, I think I locked the ability to flash aboot, and now I can't get the twrp recovery onto my phone. Does anyone have any ideas or know what to do? If I can do anything from here?
Thanks for any help!
MAHawbs said:
I'm just a dabbler in this stuff, but I think I understand everything required to get LineageOS on my LEX727. The problem is, in the process of learning, I think I locked the ability to flash aboot, and now I can't get the twrp recovery onto my phone. Does anyone have any ideas or know what to do? If I can do anything from here?
Thanks for any help!
Click to expand...
Click to collapse
What did locked ability flash abootd it d relock bootloader.
What did you ?
Sent from my SM-A730F using xda premium
Hey guys, i have to send my Pixel C to repair so i want to lock my bootloader. My Problem is, that i cant enable OEM unlocking in the developer options because its grayed out saying that my bootloader is already unlocked. "fastboot flashing lock" and "fastboot oem lock" both give me the error "FAILED (remote: Enable OEM unlock is not set)".
Is there a workaround for this?
Thanks for your help!
I also have this issue.
Same thing here. I loaded LineageOS and have decided to go back to factory. I can't figure it out either. Here are my results.
fastboot flashing lock
FAILED (remote: Enable OEM unlock is not set)
finished. total time: 0.022s
fastboot flashing unlock
FAILED (remote: Device already unlocked)
finished. total time: 0.003s
fastboot flashing get_unlock_ability
(bootloader) 0
OKAY [ 0.020s]
finished. total time: 0.020s
Ok all, I finally figured it out.
I had to download factory image 6.0.1 (MXB48J) go thru the instructions to flash this image.
Started up in android went thru the min setup to get into Settings and Developer Options. Turn on USB debugging and the OEM Unocking.
adb reboot bootloader
flashboot flashing lock
Prompted me about wiping the device.
Everything is good.
If I remember correctly, on the P2XL, we were able to do both unlock and unlock_critical from fastboot. And them lock them both separately. However, since the last two clean flashes for me, I'm unable to lock or unlock both the partitions. I can only unlock or lock either one of them. When I try to do the other, it fails stating that the device is already unlocked! Another thing I noticed is that when I run sudo fastboot oem device-info, I get the below:
Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
Finished. Total time: 0.000s
If you notice,
Code:
(bootloader) Device critical unlocked: false/true
is completely missing!
Due to this, my device remains uncertified and always fails safety net.
Any idea how to fix this?
Hey so I have a razer phone and I am stuck in the bootloader "download" mode Oem Unlock is disabled and cant enable because I am in a boot loop and I can't install stock because I can't unlock bootloader. Can anyone help me?
did you ever fix
have the same problem right now any help would be appreciated
does fastboot recognize the device?
same problem
Hi, I have the exact same problem,
fastboot is working, but cannot unlock
Code:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.008s]
Finished. Total time: 0.009s
Code:
fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.004s
I cannot go into the android system, screen stay black, I need to wait for the battery to run out to test again from powered off phone (if I boot normally)
any help ?
I had been using 8 for a while successfully with Google Pay functioning and recently updated to the latest 9 because... updates are great right (https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/)
Even after relocking the bootloader and OEM unlock, Gpay says it cannot be used on this phone as it's been modified. I tried downgrading back to 8 but WIFI and Mobile Data didn't work, lucky bluetooth tehtered to OEM unlock (I relocked the bootloader for Gpay before noticing access did not work) so I'm back on 9 with the retail FlashAll but ideally am after Google Pay working as it's my access to the wifes credit card when mine hits the limit (renos.... joy)
So, team, geniuses... is it possible to run Stock Pie Retail (1789-05 retcn) with a locked bootloader and all functionality working? If so... how?! Many thanks :cyclops:
Does your phone pass safetynet check?
SafetyNetResponse
ctsProfileMatch=false, basicIntegrity=true, advice=LOCK_BOOTLOADER,RESTORE_TO_FACTORY_ROM}
I'll relock bootloader tonight ... Reloading apps and messages is tiresome!
On the last instance with a locked bootloader Google Pay would not allow my card to be added
Just my luck...
fastboot.exe oem lock
(bootloader) s: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: -0.000s
fastboot flashing lock
(bootloader) s: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: -0.000s
fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\adb\Z2FORCE9.0>fastboot oem lock
(bootloader) slo: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.016s
The only type of firmware you can relock have 4 letter characters that end in an S. For instance, the latest RETAIL Pie update has PPX29. You would only be able to relock on Pie using PPXS29.
Your best bet is flashing the latest OPXS firmware and getting an OTA update to 9. Also, I recommend using this utility to generate the template of fastboot commands: https://github.com/dlenski/motoflash2sh.
And as far as relocking goes, you can use guides for older moto z phones, they all work about the same, like this one: https://forum.xda-developers.com/showpost.php?p=74222803&postcount=26
ben0551 said:
Just my luck...
fastboot.exe oem lock
(bootloader) s: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: -0.000s
fastboot flashing lock
(bootloader) s: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: -0.000s
fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\adb\Z2FORCE9.0>fastboot oem lock
(bootloader) slo: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
If you noticed, your commands are cut off and not properly formatted. This is usually because of outdated adb/fastboot files, bad or no oem cable, or incompatible usb port. Update your adb/fastboot files and make sure you're using the oem cable and 2.0 usb ports for reliability.
As for relocking, I don't recommend it. If you look around the forum you'll see a few that are basically up a creek because they relocked the bootloader and something went wrong. Now they can't flash anything because their bootloader is locked. You should reflash retail 9 and take an ota if you can. Try and clear up any mismatches or discrepancies. Try Gpay afterwards. Many have no issues using Gpay, even with unlocked rooted devices.
With retail 9 and unlocked bootloader I cant access settings > updates or gpay
"As your system device integrity is compromised you are no longer eligible for updates"
ben0551 said:
"As your system device integrity is compromised you are no longer eligible for updates"
Click to expand...
Click to collapse
Download your firmware from lolinet and manual flash it.
41rw4lk said:
Download your firmware from lolinet and manual flash it.
Click to expand...
Click to collapse
If I flash 9 from lolinet, I can't lock bootloader / use gpay
If I flash 8 from lolinet, baseband is gone
Suggesting flash 8, lock and OTA via bluetooth tether?
ben0551 said:
If I flash 9 from lolinet, I can't lock bootloader / use gpay
If I flash 8 from lolinet, baseband is gone
Suggesting flash 8, lock and OTA via bluetooth tether?
Click to expand...
Click to collapse
Why don't u try flashing stock 8 but with modem from 9?