[SOLVED] Bootloader unlocking problem. THANKS TO timmaaa - ONE Q&A, Help & Troubleshooting

Hi all,
The bootloader unlocking command "Fastboot oem unlock" did not work for me, because I locked the bootloader when I had installed TWRP recovery. TWRP recovery prevents the command from working. Luckily, timmaaa directed me to a thread which fixed this problem. I flashed a bootloader unlocker zip via TWRP. It worked flawlessly for me.
This is the thread I was directed to:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912

your phone still boots into CM11S and TWRP recovery? if yes, then it is not bricked. Unlocking bootloader is only one time process. you do not need to unlock again as it is already unlocked, if you did re-locked bootloader then unlock it. you can flash oxygen OS straight away on twrp recovery.

Parth2187 said:
your phone still boots into CM11S and TWRP recovery? if yes, then it is not bricked. Unlocking bootloader is only one time process. you do not need to unlock again as it is already unlocked, if you did re-locked bootloader then unlock it. you can flash oxygen OS straight away on twrp recovery.
Click to expand...
Click to collapse
Thanks for your reply.
I relocked the device. After that I tried to unlock it again, but when I type the command and hit enter, the device will boot into TWRP recovery.
So what I have now is CM11S with working TWRP recovery.
But if I had installed cm12 or so, I wouldn't be able to flash CM11S, because the bootloader doesn't get unlocked anymore.
I know it's a very strange problem. I don't understand why it doesn't get unlocked anymore..
Luckily, cm11s still works. And I could install Oxygen OS using TWRP. But if something goes wrong, I will not be able to restore my device to stock CM11S, because the bootloader has not been unlocked..
Thanks anyway, I appreciate your help.

danielsinnema said:
Thanks for your reply.
I relocked the device. After that I tried to unlock it again, but when I type the command and hit enter, the device will boot into TWRP recovery.
So what I have now is CM11S with working TWRP recovery.
But if I had installed cm12 or so, I wouldn't be able to flash CM11S, because the bootloader doesn't get unlocked anymore.
I know it's a very strange problem. I don't understand why it doesn't get unlocked anymore..
Luckily, cm11s still works. And I could install Oxygen OS using TWRP. But if something goes wrong, I will not be able to restore my device to stock CM11S, because the bootloader has not been unlocked..
Thanks anyway, I appreciate your help.
Click to expand...
Click to collapse
Well, you can try @manudroid19's Toolkit it has option to unlock/lock bootloader or flash cm11s everything you want to do with toolkit. http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
if this toolkit doesn't work for you. please let me know or pm me

Parth2187 said:
Well, you can try @manudroid19's Toolkit it has option to unlock/lock bootloader or flash cm11s everything you want to do with toolkit. http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
if this toolkit doesn't work for you. please let me know or pm me
Click to expand...
Click to collapse
It did not work ;( It tried to unlock my bootloader. But after I clicked on "unlock bootloader" button, the device rebooted once again in TWRP recovery.
I think the problem is that I have a locked bootloader with a custom recovery. I think stock recovery is used to unlock the bootloader, isn't it?

You should never relock the.bootloader
Its not necessary
Sent from my A0001

There was no point to locking the bootloader again. Go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
That will allow you to unlock again via TWRP. Don't lock your bootloader again.
Transmitted via Bacon

IT WORKED!
timmaaa said:
There was no point to locking the bootloader again. Go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
That will allow you to unlock again via TWRP. Don't lock your bootloader again.
Transmitted via Bacon
Click to expand...
Click to collapse
You are absolutely amazing.
Thank you so much for directing me to that thread.
It unlocked the bootloader via TWRP. I didn't know that was possible.
Again man.. thanks.
Have a great day
Best regards,
Daniel

danielsinnema said:
You are absolutely amazing.
Thank you so much for directing me to that thread.
It unlocked the bootloader via TWRP. I didn't know that was possible.
Again man.. thanks.
Have a great day
Best regards,
Daniel
Click to expand...
Click to collapse
No worries man, glad to be able to help. You have a good day too.
Transmitted via Bacon

Related

Possible Brick after attempting to install Xposed

Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
jimburke57 said:
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
Click to expand...
Click to collapse
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Zepius said:
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Click to expand...
Click to collapse
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
jimburke57 said:
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
Click to expand...
Click to collapse
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Zepius said:
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Click to expand...
Click to collapse
I have followed it already. The images on the first post are my result.
It is showing as unlocked at the booloader and on fastboot oem device-info.
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Zepius said:
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Same thing as before. All of the erase commands get processed, but when it gets the the system.img it fails to write it.
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
jd1639 said:
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
Click to expand...
Click to collapse
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
jimburke57 said:
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
Click to expand...
Click to collapse
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
orangekid said:
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
Click to expand...
Click to collapse
Are you talking about these drivers?
jimburke57 said:
Are you talking about these drivers?
Click to expand...
Click to collapse
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
orangekid said:
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
Click to expand...
Click to collapse
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
jimburke57 said:
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
Click to expand...
Click to collapse
Have you tried flashing stock kitkat (from google) via fastboot?
orangekid said:
Have you tried flashing stock kitkat (from google) via fastboot?
Click to expand...
Click to collapse
yes, many times
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
pantlessjim said:
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
Click to expand...
Click to collapse
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Here is some additional information. When I perform a factory reset in recovery it freezes while formatting /data. And when flashing the stock images, I am able to flash everything successfully except for the system.img
jimburke57 said:
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Click to expand...
Click to collapse
Have you tried just dirty flashing stock / rooted thru recovery?
edit: or restoring a backup?

how to boot into recovery with moto G?

I have managed to root, unlock booloader but it cant find the way to boot to cwm 6... i try from fastboot but doesnt work.
I would like to know this too. I can't seem to boot into recovery even though I know I flashed TWRP correctly with a recovery.img.
Go to this post and click on the 3rd video. It worked for me
http://forum.xda-developers.com/showthread.php?t=2577043
Sent from my XT1032 using xda app-developers app
Once rooted, you may want to use the "Quick boot" application. It allows you to reboot to bootloader and recovery easily.
Thanks!
Also, a side note, if you update to Android 4.4, you have to downgrade the bootloader to 4.3s or recovery will not flash
defectiveleader said:
Thanks!
Also, a side note, if you update to Android 4.4, you have to downgrade the bootloader to 4.3s or recovery will not flash
Click to expand...
Click to collapse
oh, this is the problem... im in 4.4, how to downgrande bootloader? i dont find any guide.
yunior597 said:
oh, this is the problem... im in 4.4, how to downgrande bootloader? i dont find any guide.
Click to expand...
Click to collapse
I hope you were able to figure it out. There was a thread on here for it and I would post a link if I had time. It was super easy. You just needed to do an adb push recovery.img. There was a download someone posted for people needing it.
You don't have to downgrade to 4.3 bootloader any more just flash cwm 6.0.4.6 v3 from the link below
http://forum.xda-developers.com/showthread.php?t=2563599
yunior597 said:
I have managed to root, unlock booloader but it cant find the way to boot to cwm 6... i try from fastboot but doesnt work.
Click to expand...
Click to collapse
best way is to enable debugging mode and then in the terminal with adb
adb reboot recovery
or you press the volume down and power button and select the recovery

[Q] Serious Help Needed!!! NEED A GURU!

I recently flashed MIUI, however I have been trying to get back to CM. I seemed to have tried everything and dove and read all aspects of this forum.
Here is my situation:
Bootloader is now locked.
Custom recovery disappeared, hence I just have stock.
Tamper flag true, false, false
Can access fastboot
I tried to manually boot TWRP to wipe and sideload with no success, continues to say failed then takes me to stock recovery.
I have no freaking idea what to do. Long time reader, enthusiast, rom flashing user, however...this is the first time I am stuck! PLEASE HELP!
http://forum.xda-developers.com/showthread.php?t=2788632
C13v3r0n3 said:
http://forum.xda-developers.com/showthread.php?t=2788632
Click to expand...
Click to collapse
I have been to this thread. I fastboot oem unlock. I have read it from start to finish.
You fastboot oem unlock. What does that mean? You unlocked it? It failed? You need to be more detailed and specific.
Transmitted via Bacon

[Q] Root without Wipe

Hello together,
I read recently a article about a Nexus, which may be rooted without wipe (Source: I cannot attach a link because it is the first post, so: "Root without Wiping - Android Forums at AndroidCentral" in google), so I wondered, if it is possible to do the same on the OPO.
Thanks for your replies.
Regards,
elchico
oh ,flash supersu in recovery?don't tell me your phone is locked~~
loridoo said:
oh ,flash supersu in recovery?don't tell me your phone is locked~~
Click to expand...
Click to collapse
it is locked
I unlocked it when I bought it but then there occured some problems and as a result I flashed the stock kernel/ rom. But today I wanted to install an anti-theft-protection and for that I need the root
Why did you relock the bootloader when you went back to stock? You didn't need to do that. Now you're stuck, you can't get root without unlocking the bootloader, and you can't unlock the bootloader without it wiping your phone.
Transmitted via Bacon
timmaaa said:
Why did you relock the bootloader when you went back to stock? You didn't need to do that. Now you're stuck, you can't get root without unlocking the bootloader, and you can't unlock the bootloader without it wiping your phone.
Transmitted via Bacon
Click to expand...
Click to collapse
hmm ok uncool it was a bat file from oneplus personally ...
okay so: thank you all

Can't boot :/

If you're asking if we have Marshmallow, yes we do, in the form of Resurrection Remix 6 (WIP) and CM13 (WIP).
You said with locked bootloader it doesn't boot. Did you mean UNLocked bootloader? When you unlocked your bootloader, did you install TWRP?
When you installed TWRP did you wipe EVERYTHING?
If wiped everything then you have no ROM to boot. (You should have done a factory re-set instead.)
You have to go back into TWRP and drag over a ROM from your computer... install that in TWRP and then it will boot.
I'm only guessing at what you did, so that's my best answer.
_______
Oh, wait, looking at your other posts, you're the guy who re-locked his Droid Turbo bootloader and bricked it:
http://forum.xda-developers.com/droid-turbo/help/relocked-bootloader-bricked-t3306081
So, that's your issue. Still not sure why you did that. You paid for Sunshine, it was a one-time deal, can't be done again, and you still re-locked your bootloader. An unlocked bootloader is FREEDOM. You can screw up and still recover from mistakes. A locked bootloader is slavery, and if you mess up, much harder -- sometimes impossible -- to recover from mistakes...
IF that's still your issue, the only thing you can try to do is re-install stock 5.1 Droid Turbo Lollipop image via fastboot. Good luck.
This post by @TheSt33v in the other thread where you posted gave you the only possible answer. If you have TWRP still installed you have to overwrite everything, including the recovery partition. But you have to follow the steps exactly.
http://forum.xda-developers.com/showpost.php?p=65095391&postcount=5
TheSt33v said:
With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to flash all of the stock images with a locked bootloader.
See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse

Categories

Resources