Hello all,
I think I messed my Nexus 6 badly.
I stupidly re locked the bootloader, then did a factory wipe in TWRP.
So there is no more way the phone boot to configure 'Allow OEM Unlock' in Developer Options
So I'm stuck:
C:\SDK\android-sdk-windows\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.003s
C:\SDK\android-sdk-windows\platform-tools>
Any Idea ???
Please help
Thanks
Pas
Can you still boot to TWRP?
Deleted
runekock said:
Can you still boot to TWRP?
Click to expand...
Click to collapse
Thanks for replying.
It's on Stock recovery now.
But in TWRP flashing always fails because the bootloader is locked.
now I need to unlock the bootloader but how if "fastboot oem unlock" does not work
it give the FAILED (remote failure)
When the phone reboot it's stuck with a white Google display and nothing happen.
If you're on the stock recovery, installing the final OTA update (N8I11F) should get your device up and running so you can then enable OEM Unlocking in Android.
Strephon Alkhalikoi said:
If you're on the stock recovery, installing the final OTA update (N8I11F) should get your device up and running so you can then enable OEM Unlocking in Android.
Click to expand...
Click to collapse
Yes, the OTA update did it.
Installed fine with the ADB sideload option in stock recovery .
It finally boot up to enable OEM Unlocking
Thanks a lot
Best
Pas
Related
I have non-dev Verizon Moto X 4.4.2 unlocked using the chinese method.
I'm in fastboot right now and it says "Device is UNLOCKED. Status Code: 3" if that means anything.
Every time I tried to flash TWRP and I reboot to recovery...it's still the stock android recovery.
I also tried to erase the stock recovery but i get this message:
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.094s
My motox is unlocked..so why doesn't it say permission denied and why can't i flash a custom recovery??
please help.
I'm not root btw.
Did you go into TWRP after flashing it?
You have to boot straight to recovery or it gets written over by the stock recovery
bigv5150 said:
You have to boot straight to recovery or it gets written over by the stock recovery
Click to expand...
Click to collapse
i thought i did but it boot straight into the OS instead of recovery...let me try again...
*edit*
ok wow i guess i didn't do it when i thought i did but i'm in TWRP now.
Thank you guys!
You probably hit the power button instead of volume+ the first time around.
nexus 6 can not run the system, only the logo on the screen does not move
I tried to brush oem unlock firmware but failed.
I guess I broke the Recovery partition.
How can I do it? Help me!:angel::angel:
Please give a bit more detail about your setup and what happened before this
rootSU said:
Please give a bit more detail about your setup and what happened before this
Click to expand...
Click to collapse
I installed android 5.1.
root
Installed TWRP Recovery
Then I run "fastboot oem lock" this time we can not normally enter the system.
I found that running fastboot -w can enter the system, so I entered the "TWRP Recovery" to restore the backup method used to restore a backup Recovery partition.
So, let me get it straight...
You unlocked the bootloader
You then rooted
Installed recovery
THEN relocked the boot loader?
...why?
You won't be able to do anything to any partition until the boot loader is unlocked again - try that. Unlock the boot loader (make sure to enable it in Dev settings) and then it should all work again.
Good job, I think you bricked yourself.
Not sure if anyone found a work around for this.
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
Leo D said:
nexus 6 can not run the system, only the logo on the screen does not move
I tried to brush oem unlock firmware but failed.
I guess I broke the Recovery partition.
How can I do it? Help me!:angel::angel:
Click to expand...
Click to collapse
If you have TWRP recovery installed and ONLY if you have TWRP installed, boot into bootloader. Issue the fastboot commands:
fastboot format userdata
fastboot format cache
If you do have TWRP installed, this should allow you to boot to TWRP recovery.
See if you can accomplish this and let us know.
Evolution_Freak said:
If you have TWRP recovery installed and ONLY if you have TWRP installed, boot into bootloader. Issue the fastboot commands:
fastboot format userdata
fastboot format cache
If you do have TWRP installed, this should allow you to boot to TWRP recovery.
See if you can accomplish this and let us know.
Click to expand...
Click to collapse
I went into recovery mode, nothing happens.
View Bootloader logs
Invalid boot image size!
failed to validate recovery image
Boot up failed
iRub1Out said:
So, let me get it straight...
You unlocked the bootloader
You then rooted
Installed recovery
THEN relocked the boot loader?
...why?
You won't be able to do anything to any partition until the boot loader is unlocked again - try that. Unlock the boot loader (make sure to enable it in Dev settings) and then it should all work again.
Click to expand...
Click to collapse
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
Options appear before acceptance and rejection does not appear on the phone screen.
You probably bricked it.
It's been known to happen after 5.1 if you're not careful (or, in this case, relock the BL after modifying)
Why did you relock it? I still can't wrap my head around any reason for doing that?
Sent from my Nexus 6
Leo D said:
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
Options appear before acceptance and rejection does not appear on the phone screen.
Click to expand...
Click to collapse
The phone is bricked. RMA to Motorola
Or if you're feeling adventurous: http://forum.xda-developers.com/showthread.php?t=3059518
brando56894 said:
Or if you're feeling adventurous: http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
Thanks for your help. But there are some questions I still do not understand.
Now the phone connected to the computer and did not see QHSUSB_BULK in Device Manager. In the Device Manager to see BootLoader interface or adb interfaces.
How can I make the phone run QHSUSB_BULK state?
Hi all,
I have debranded my EVA-L09 from Three UK, so that I can get faster OTA updates (and also to try to participate in future betas) - I'm now successfully on C432B166
However, I'd like to now re-lock my bootloader, but am struggling.
Whenever I boot to fastboot and run "fastboot oem relock ****************", I get the following response:
Code:
...
FAILED (remote: root type is risk)
finished. total time: 0.006s
If I try "fastboot oem lock ****************", I get the following:
Code:
...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
I have tried with "Enable OEM unlock" both enabled and disabled in Developer Options.
Can anyone give me any pointers on how to re-lock the bootloader?
Many thanks!
Sorry to bump an old thread. I'm currently having the same problems @ConfusedTA . Unfortunately I think it's difficult to re-lock bootloader without being on the same firmware that you were on when you unlocked it.
If anybody knows a way of forcing the bootloader to lock it'd be much appreciated!
Hello, i want to lock my bootloader but i can't. I tried with some fastboot commands but i get this error:
FAILED (remote: unknown command)
finished. total time: 0.004s
I have ZUI 11.1.021 ST Chinese ROM
Thanks in advance
jc9495 said:
Hello, i want to lock my bootloader but i can't. I tried with some fastboot commands but i get this error:
FAILED (remote: unknown command)
finished. total time: 0.004s
I have ZUI 11.1.021 ST Chinese ROM
Thanks in advance
Click to expand...
Click to collapse
hello can you tell me what commands you used?
i used "fastboot flashing lock"
then it pops up a confirmation dialog on the phone and once you accept it the boot loader locks.
metalspider said:
i used "fastboot flashing lock"
then it pops up a confirmation dialog on the phone and once you accept it the boot loader locks.
Click to expand...
Click to collapse
thanks:good::fingers-crossed:
I tried to lock my bootloader i download adb and fastboot and lenovo usb driver but no device found plsss help
I did this guide to lock the bootloader and install CN Rom zui10. then download and update to zui11 from there.
"forum.xda-developers.com/z5-pro-gt/how-to/guide-how-to-install-gsi-rom-treble-t3950283"
---------- Post added at 07:01 AM ---------- Previous post was at 06:53 AM ----------
pauloalbura said:
I did this guide to lock the bootloader and install CN Rom zui10. then download and update to zui11 from there.
"forum.xda-developers.com/z5-pro-gt/how-to/guide-how-to-install-gsi-rom-treble-t3950283"
Click to expand...
Click to collapse
wrong link. here's the correct one.
"forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945?spm=a2o4l.home.icms-5000630-1511774168247.1.239e6db4Kzq2Ou&fbclid=IwAR3kKJw0i3fcYqhmYem3Gf-zReG6qpXoAAUehm6au0RC1zAULuqQ222fFnY"
i only got to the stage of unlocking the phone. didnt know how to isntall the rom for oxygenos with magisk.
now my phone is unlock i want to lock it because i want to use gpay.
i tried to use the command fastboot oem lock. it said: failed (remote: unknown command)
finished. total time: 0.001s
any help please?
don't unless you want to roll the dice on bricking.
just install safetynet fix
grand_deluxe said:
i only got to the stage of unlocking the phone. didnt know how to isntall the rom for oxygenos with magisk.
now my phone is unlock i want to lock it because i want to use gpay.
i tried to use the command fastboot oem lock. it said: failed (remote: unknown command)
finished. total time: 0.001s
any help please?
Click to expand...
Click to collapse
you have to use this adb command: fastboot flashing lock
Good luck
g96818 said:
don't unless you want to roll the dice on bricking.
just install safetynet fix
Click to expand...
Click to collapse
U won't brick relocking if nothing was altered in the system or the phone is back to factory state.
the_rooter said:
U won't brick relocking if nothing was altered in the system or the phone is back to factory state.
Click to expand...
Click to collapse
Tell that to those who have bricked with everything back to a factory state.
g96818 said:
Tell that to those who have bricked with everything back to a factory state.
Click to expand...
Click to collapse
And I will obviously they didn't take the time to make sure everything was back to stock and the system was unchanged... if u relocate your bootloader and it bricked...that's the cause of user error.