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.
Related
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.
good friends after an update my google pixel stays in boot loop I have tried several ways to unlock the bootloader to install a stock rom from flashboot but every time i try to unlock the bootloader it tells me that i have to activate or unlock the oem option
I tried to do it with the adb flashtool but it gives me error
c:\adb>fastboot oem unlock
FAILED <remote: oem unlock is not allowed>
finished. total time: 0.044s
c:\adb>
I can not enter the Android system either from my Google Pixel since it is damaged the same to activate the option of OEM
I need someone to help me with this problem because the phone does not let me do anything for the fastboot because the bootloader and the OEM are blocked
I think I've screwed up big time, but as I list ditch effort I'm hoping somebody can save the day. And I'd be more than happy to send a little money toward anyone who can help me solve this.
I don't remember the exact commands, but I locked my bootloader before going stock, and as a result the phone is now bootlooping (flashing the boot logo for less than a second and restarting) from normal boot AND recovery. Pretty much all fastboot commands result in the following:
$ fastboot boot twrp-3.3.1-2-marlin.img
Sending 'boot.img' (31101 KB) OKAY [ 0.763s]
Booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
fastboot: error: Command failed
Trying to unlock the bootloader results in FAILED (remote: 'oem unlock is not allowed')
Anything else I should try before giving up on it?
Yup looks like you bricked it. Should probably buy an iPhone.
uPaymeiFixit said:
I think I've screwed up big time, but as I list ditch effort I'm hoping somebody can save the day. And I'd be more than happy to send a little money toward anyone who can help me solve this.
I don't remember the exact commands, but I locked my bootloader before going stock, and as a result the phone is now bootlooping (flashing the boot logo for less than a second and restarting) from normal boot AND recovery. Pretty much all fastboot commands result in the following:
$ fastboot boot twrp-3.3.1-2-marlin.img
Sending 'boot.img' (31101 KB) OKAY [ 0.763s]
Booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
fastboot: error: Command failed
Trying to unlock the bootloader results in FAILED (remote: 'oem unlock is not allowed')
Anything else I should try before giving up on it?
Click to expand...
Click to collapse
I got a ROG phone 6 few days ago. But I found that after I used the official unlocker app, I cannot find OEM unlock option in Developer settings.
I tried 2 commands in bootloader:
Code:
(bootloader)
fastboot flashing unlock
FAILED (remote: 'permission denied')
fastboot: error: Command failed
get_unlock_ability: 0
OKAY [ 0.003s]
Finished. Total time: 0.004s
How can I enable it?
To unlock the bootloader, you have to use unlock app from the Asus homepage. That's the best way to do it. Relock could be done by CMD command.
I also cannot unlock my bootloader. When i use unlocking tool app my device just reboot