Relocking bootloader of Oneplus 7 pro - OnePlus 7 Pro Questions & Answers

I used a local update to get rid of my root and TWRP. Can i go ahead and lock the bootloader? Thanks

GrubbySalmon said:
I used a local update to get rid of my root and TWRP. Can i go ahead and lock the bootloader? Thanks
Click to expand...
Click to collapse
For me, i just use msmtools for peace of mind. Its simple

If I can remember right. You will have to use the MSM Tool to flash stock after relocking the bootloader.

GrubbySalmon said:
I used a local update to get rid of my root and TWRP. Can i go ahead and lock the bootloader? Thanks
Click to expand...
Click to collapse
Boot to fastboot
then on Adb type Fastboot oem lock. You will get a pop up on your phone screen to confirm re-lock. Confirm this and it will be done. Please note your data and storage will be wipped out

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?

BootUnlocker for Nexus Devices worth it?

Hi guys, I found this program "I'm root" my question is, I'd like to close the boot-loader jut for security reasons, but now I've set up everything as I wanted so I don't want to delete everything again.
Can I use this program it seem to be really good.
"BootUnlocker for Nexus Devices"
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Waiting for answers.
Yes. I use this to lock and unlock my bootloader once rooted. It doesn't wipe anything.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yes. I use this to lock and unlock my bootloader once rooted. It doesn't wipe anything.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
WOW perfect then I'll do it. Like this if I lose my phone no one will be able to steal anything. (Steal I say xD, they can't do that much. but you know what I mean.)
If you have a custom recovery they can. So make sure you have a stock recovery
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yes. I use this to lock and unlock my bootloader once rooted. It doesn't wipe anything.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Can I lock the bootloader using this app with a custom recovery installed so that when I need to install updates to the rom or flash something I wouldn't need to flash/boot Philz again after unlocking?
Or do I need to flash the stock recovery before locking with this app??
vin4yak said:
Can I lock the bootloader using this app with a custom recovery installed so that when I need to install updates to the rom or flash something I wouldn't need to flash/boot Philz again after unlocking?
Or do I need to flash the stock recovery before locking with this app??
Click to expand...
Click to collapse
As long as you're rooted it'll work with a custom recovery or stock. Edit, just be careful if you do a lot of messing around on your phone. You may be locked when you wish you weren't
Sent from my Nexus 5
jd1639 said:
As long as you're rooted it'll work with a custom recovery or stock. Edit, just be careful if you do a lot of messing around on your phone. You may be locked when you wish you weren't
Sent from my Nexus 5
Click to expand...
Click to collapse
Yes, I get that.. If I end up in a bootloop I would need to use fastboot which will erase all my data.. That's what you're warning me about, right?
To tell you the truth, I'm actually worried about this eMMC failure thing as I have a 1 year LG warranty (not google's). I have seen a few threads where they weren't able to relock their bootloaders before sending it in as the eMMC's write function was screwed up. If I send my device in with a unlocked bootloader, warranty will go down the drain for sure. LG is very strict regarding this matter.
May be I'm thinking too much but my friend had faced similar issues with his HTC One and he had to shell out half the price of the phone to get the mobo replaced even though he had warranty
vin4yak said:
Yes, I get that.. If I end up in a bootloop I would need to use fastboot which will erase all my data.. That's what you're warning me about, right?
To tell you the truth, I'm actually worried about this eMMC failure thing as I have a 1 year LG warranty (not google's). I have seen a few threads where they weren't able to relock their bootloaders before sending it in as the eMMC's write function was screwed up. If I send my device in with a unlocked bootloader, warranty will go down the drain for sure. LG is very strict regarding this matter.
May be I'm thinking too much but my friend had faced similar issues with his HTC One and he had to shell out half the price of the phone to get the mobo replaced even though he had warranty
Click to expand...
Click to collapse
I'm guessing that if your emmc failed you wouldn't be able to lock using this app. Boot it is an easy way to keep it locked until you need to unlock. It is a good app and it's been on my phone for months. But I usually keep it unlocked
Sent from my Nexus 5
rootSU said:
If you have a custom recovery they can. So make sure you have a stock recovery
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So if I have a custom recovery I can!!!! and then you said make sure you have a stock recovery...
What I have to have, stock or custom?
When you say custom you mean, -hammerhead or clockwork- right?
Thanks.
you can have a custom recovery and use that app to lock and unlock your bootloader, just as you can have a custom recovery and lock/unlock your bootloader with the fastboot command.. fastboot oem lock(fastboot oem unlock).
jd1639 said:
I'm guessing that if your emmc failed you wouldn't be able to lock using this app. Boot it is an easy way to keep it locked until you need to unlock. It is a good app and it's been on my phone for months. But I usually keep it unlocked
Sent from my Nexus 5
Click to expand...
Click to collapse
That's why I was thinking to after flashing what I want to, I would lock the bootloader with the app so suppose one fine day my eMMC gets fried, I wouldn't be in trouble as it will be locked.
If I want to flash anything, unlock with the app, flash via recovery, reboot and then lock the bootloader again! Does sound good, right??
LOL, now I'm surely thinking too much
ivan333 said:
So if I have a custom recovery I can!!!! and then you said make sure you have a stock recovery...
What I have to have, stock or custom?
When you say custom you mean, -hammerhead or clockwork- right?
Thanks.
Click to expand...
Click to collapse
Rootsu was referring to the ability to hack onto your phone not the bootunlocker app. Bootunlocker will work if you're rooted and it doesn't matter if you have stock or a custom recovery
Sent from my Nexus 5
vin4yak said:
That's why I was thinking to after flashing what I want to, I would lock the bootloader with the app so suppose one fine day my eMMC gets fried, I wouldn't be in trouble as it will be locked.
If I want to flash anything, unlock with the app, flash via recovery, reboot and then lock the bootloader again! Does sound good, right??
LOL, now I'm sure thinking too much
Click to expand...
Click to collapse
then you dont need the app. after you unlock your bootloader and root it, just boot into your bootloader after and lock it.
simms22 said:
then you dont need the app. after you unlock your bootloader and root it, just boot into your bootloader after and lock it.
Click to expand...
Click to collapse
But then, when I need to flash a nightly or any mod, I would need to unlock the bootloader via fastboot to access the custom recovery which will wipe everyhting, right? If I have the app, I can simply unlock it without wiping.
Or should I just use fastboot boot on a locked bootloader to flash any mod/nightly??
vin4yak said:
That's why I was thinking to after flashing what I want to, I would lock the bootloader with the app so suppose one fine day my eMMC gets fried, I wouldn't be in trouble as it will be locked.
If I want to flash anything, unlock with the app, flash via recovery, reboot and then lock the bootloader again! Does sound good, right??
LOL, now I'm surely thinking too much
Click to expand...
Click to collapse
Yep, that would work
Sent from my Nexus 5
simms22 said:
then you dont need the app. after you unlock your bootloader and root it, just boot into your bootloader after and lock it.
Click to expand...
Click to collapse
But that will swap (WIPE sorry) all your phone... that's what I don't want. (Sorry maybe I misunderstood something but later I'll read it again and carefully.)
vin4yak said:
But then, when I need to flash a nightly or any mod, I would need to unlock the bootloader via fastboot to access the custom recovery which will wipe everyhting, right? If I have the app, I can simply unlock it without wiping.
Or should I just use fastboot boot on a locked bootloader to flash any mod/nightly??
Click to expand...
Click to collapse
no, wont wipe everything. just that first time.
simms22 said:
no, wont wipe everything. just that first time.
Click to expand...
Click to collapse
Are you sure? If you oem lock and then oem unlock I think it wipes it each time.
Sent from my Nexus 5
simms22 said:
no, wont wipe everything. just that first time.
Click to expand...
Click to collapse
Wooaaahh?! Thanks for the clarification... Just curious though, why does it not wipe everything when I unlock it the 2nd time? is it because the tamper flag is set to "true"? How does the bootloader determine that it's being unlocked the second time?
Thanks a lot!
vin4yak said:
Wooaaahh?! Thanks for the clarification... Just curious though, why does it not wipe everything when I unlock it the 2nd time? is it because the tamper flag is set to "true"? How does the bootloader determine that it's being unlocked the second time?
Thanks a lot!
Click to expand...
Click to collapse
As an fyi, I locked with bootunlocker once and then messed up by device where I had to use fastboot commands. It does wipe if you have to fastboot unlock the device again
Sent from my Nexus 5

[SOLVED] Bootloader unlocking problem. THANKS TO timmaaa

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

Factory images are up....

Factory images are up... https://developers.google.com/android/images#coral
Thanks, gonna try to root now!
Are the images only useful if you have your bootloader unlocked or can they help unlock bootloader?
Who-Lep said:
Are the images only useful if you have your bootloader unlocked or can they help unlock bootloader?
Click to expand...
Click to collapse
You should be able to flash it, regardless, but I am not sure why you would. This is mainly for getting root and you have to be unlocked for that
ZeroKool76 said:
You should be able to flash it, regardless, but I am not sure why you would. This is mainly for getting root and you have to be unlocked for that
Click to expand...
Click to collapse
I see, thanks!
Seems firmware's are universal now. Don't see a Verizon one.
Who-Lep said:
Are the images only useful if you have your bootloader unlocked or can they help unlock bootloader?
Click to expand...
Click to collapse
Factory images can ONLY be flashed if you have an unlocked bootloader.
They on their own cannot help unlock the bootloader.
You can sideload the factory OTA zips with a locked bootloader.
uicnren said:
Factory images can ONLY be flashed if you have an unlocked bootloader.
They on their own cannot help unlock the bootloader.
You can sideload the factory OTA zips with a locked bootloader.
Click to expand...
Click to collapse
Thanks for the explanation!
If I sideload the factory image over the AT&T variant; will it finally let me enable oem unlocking? Currently, it's grayed out.
KillerBytes said:
If I sideload the factory image over the AT&T variant; will it finally let me enable oem unlocking? Currently, it's grayed out.
Click to expand...
Click to collapse
1. You don't sideload a factory image.
2. No
Moderator, you can close this thread since it has served it's purpose. Thank you

Bootloader relock breaking my boot

I wanted to switch to Lineage with MicroG so I unlocked my bootloader(was on Open beta 3), flashed Lineage recovery and tried out Lineage. Somehow being unsatisfied, I wanted to move back to stock and found the Android 10 fastboot rom and instructions from this thread I am back on stock now. However my bootloader is still unlocked. I tried to lock it using fastboot OEM lock but then I ended up not able to boot at all. Has anyone managed to relock bootloader and can you share the way to do it?
yeshwanthvshenoy said:
I wanted to switch to Lineage with MicroG so I unlocked my bootloader(was on Open beta 3), flashed Lineage recovery and tried out Lineage. Somehow being unsatisfied, I wanted to move back to stock and found the Android 10 fastboot rom and instructions from this thread I am back on stock now. However my bootloader is still unlocked. I tried to lock it using fastboot OEM lock but then I ended up not able to boot at all. Has anyone managed to relock bootloader and can you share the way to do it?
Click to expand...
Click to collapse
Why do you want to lock your bootloader?
There are many reasons for unlocking but I do not see any for "re-locking" the bootloader
You sure you have no modifications applied at all? As soon as the boot / system partition is being detected as tampered the device won't boot. I can imagine there is some information on persist whichmight be used for comparison and as you are using a file to go back to Android 10 from XDA it might throw this error? Just guessing though
TheSSJ said:
You sure you have no modifications applied at all? As soon as the boot / system partition is being detected as tampered the device won't boot. I can imagine there is some information on persist whichmight be used for comparison and as you are using a file to go back to Android 10 from XDA it might throw this error? Just guessing though
Click to expand...
Click to collapse
I am not sure what exactly is causing this. This is why I created this thread to see if someone who has locked it again can reply or something or I can get some hints from someone.
It_ler said:
Why do you want to lock your bootloader?
There are many reasons for unlocking but I do not see any for "re-locking" the bootloader
Click to expand...
Click to collapse
People have preferences. Whilst for you it may not seem valid or no reasons, I do have bro.

Categories

Resources