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?
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.
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?
Hi, I need some help with unlocking the bootloader of my phone [Huawei Y5 (DRA-LX3)] Please!
So, I am using the adb7fastboot method to unlock the bootloader, there are very limited options to do this process, but I've managed to find what might be the unlocker code for the command:
Code:
fastboot oem unlock xxxxxxxxxx (the unlock code)
Naturally, the warning screen appears on my phone (the one that tells you about erasing all of the data by unlocking the phone), and when I select "Yes" the phone displays an error:
unlock failed... return to fastboot in 3s
And the adb/fastboot window goes something like this:
Code:
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0x7
)
finished. total time: 6.137s
What do you think? Is there a solution that can save my life? Thanks by the way!
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.