I need to relock the bootloader, but the fastboot oem lock command doesn't work saying
C:\G5>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.003s
But that option is greyed out. I'm on POTTER_NPN25.137-92 Stock ROM with unlocked bootloader (XT1686).
Please help!
SD008 said:
I need to relock the bootloader, but the fastboot oem lock command doesn't work saying
C:\G5>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.003s
But that option is greyed out. I'm on POTTER_NPN25.137-92 Stock ROM with unlocked bootloader (XT1686).
Please help!
Click to expand...
Click to collapse
Because that isn't how you lock the bootloader on Moto devices... you can't just lock your bootloader on the fly, it can only be down with a full factory image flash. In your case, it is something like this:
'fastboot oem lock ' <get prompted to make sure you want to this and enter command again>
'fastboot oem lock'
Then fastboot flash the full factory image of NPN25.137-92 or newer ROM for your device, including all wipes, and end it with
`fastboot oem lock` - but this will only work if you used oem lock at the beginning and in conjunction with a complete image flash.
There are tutorials on here how to do it, a little research in the forums here will yield a couple different tutorials.
BTW, it is well known that relocking the bootloader on the Moto G5 series is problematic... Sometimes it doesn't work, and sometimes it bricks.
Remember that regardless of if you relock or not, the bootloader unlock warning screen will always be there, and the bootloader will never go back to Status 0 - Locked, it will become Status 2 - Relocked so it is still a clear indication the phone was modified at one point.
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
acejavelin said:
Because that isn't how you lock the bootloader on Moto devices... you can't just lock your bootloader on the fly, it can only be down with a full factory image flash. In your case, it is something like this:
'fastboot oem lock ' <get prompted to make sure you want to this and enter command again>
'fastboot oem lock'
Then fastboot flash the full factory image of NPN25.137-92 or newer ROM for your device, including all wipes, and end it with
`fastboot oem lock` - but this will only work if you used oem lock at the beginning and in conjunction with a complete image flash.
There are tutorials on here how to do it, a little research in the forums here will yield a couple different tutorials.
BTW, it is well known that relocking the bootloader on the Moto G5 series is problematic... Sometimes it doesn't work, and sometimes it bricks.
Remember that regardless of if you relock or not, the bootloader unlock warning screen will always be there, and the bootloader will never go back to Status 0 - Locked, it will become Status 2 - Relocked so it is still a clear indication the phone was modified at one point.
Click to expand...
Click to collapse
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
Click to expand...
Click to collapse
Hi I want to ask a question I restored my nandroid stock backup VoLTE , LTE everything is working fine. I have Moto stock recovery but on device bootup it shows bootloader unlocked sign.
Can I install updates when update come without any issue or will it brick my device I have stock moto recovery
sinchan_nohara said:
Hi I want to ask a question I restored my nandroid stock backup VoLTE , LTE everything is working fine. I have Moto stock recovery but on device bootup it shows bootloader unlocked sign.
Can I install updates when update come without any issue or will it brick my device I have stock moto recovery
Click to expand...
Click to collapse
If you haven't changed anything in /system or /vendor and your device is stock unrooted there's no problem with OTA updates. If you flashed the stock logo.bin everything is ok even when it shows BL is unlocked.
Sent from my Moto G5 Plus using XDA Labs
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
Click to expand...
Click to collapse
I've been here a long time, didn't mean to offend... All I had to go by was your limited information of the first post, I assumed nothing that wasn't included in your post. You didn't state anything that you had tried, so of course I assumed you didn't look because you didn't state anything.
Sorry. I will just bow out and wish you luck.
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
Click to expand...
Click to collapse
Man, I was having the same issue on my Moto G6 (Ali) and was like you, looking here and there with no solution, and your solution was the only one that worked!! Thank you so much!
Related
I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
1. Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
2. Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.
All this info is all ready on the forums in various threads already but I wanted to put in one place since I noticed quite a few users botch up the devices trying to update to 3.1 The last thing we need are a bunch of people bricking the devices and sending them in moto. I suspect if enough people do it they will end up changing their minds on the entire encrypted bootloader situation.
I know you have to unlock to flash "non-stock" images, but do you have to unlock if you are only going to flash the "stock" motodev images?
If I am currently just unlocked, not rooted do I need to lock in order to get the 3.1 update?
ccogan said:
If I am currently just unlocked, not rooted do I need to lock in order to get the 3.1 update?
Click to expand...
Click to collapse
NO. the update only checks for stock files, not lock or unlock.
Blaisun said:
I know you have to unlock to flash "non-stock" images, but do you have to unlock if you are only going to flash the "stock" motodev images?
Click to expand...
Click to collapse
before you can flash anything you will need to unlock the bootloader.
how to lock the bootloader????
albundy2010 said:
I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
1. Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
2. Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.
All this info is all ready on the forums in various threads already but I wanted to put in one place since I noticed quite a few users botch up the devices trying to update to 3.1 The last thing we need are a bunch of people bricking the devices and sending them in moto. I suspect if enough people do it they will end up changing their minds on the entire encrypted bootloader situation.
Click to expand...
Click to collapse
Question for you, how do I go about entering this command? My knowledge is basic. I have unrooted, restocked a Nexus 7. Trying to do oem lock without being able to use the screen. Cannot enable USB debugging because the screen is nonoperational. Any advice?
The new Device Protection features of Android 5.1 on the Nexus 9 and Nexus 6 can, in certain cases, cause you to have a bootloader which can not be unlocked.
Please have a read of the following links:
https://support.google.com/nexus/answer/6172890?hl=en
http://forum.xda-developers.com/nexus-6/help/update-to-5-1-lock-bootloader-t3058480
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
What a pita
Sent from my Nexus 5 using XDA Free mobile app
i would never relock my bootloader
people unlock there bootloader for a reason
but to relock it after thats just wrong...
thats one of the things i hate about CM
they recommend you to relock your bootloader...
Agreed, why would you lock your bootloader unless sending in for repairs maybe?
But Google is really messing up the flow. The nexus 6 5.1 OTA is a mess right now but I will leave that for another thread.
Android 5.1 for Nexus 9? You must be joking.
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
No no you can still unlock it
But if you relock it that's the problem
disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
efrant said:
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
Considering this is a tablet, hopefully I won't lose or misplace it
Thanks, guys! Glad I stumbled across this thread before the thing arrived.
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
doitright said:
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
Click to expand...
Click to collapse
Example: I have a device running a stock ROM with no encryption, the stock recovery and a lock screen password. I happen to lose my phone. What happens to the photos of me dancing to Old Time Rock & Roll in my underwear that are stored on the device? If the bootloader is unlocked, someone just plugs it into a PC, boots TWRP and pulls them off. If the bootloader is locked, there is no easy way to see or get the photos off the device.
That is all I was saying about security. Nothing to do with you leaving your device somewhere or losing it, and then finding it again. Strictly about the personal content on the device.
efrant said:
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
bailyc said:
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
Click to expand...
Click to collapse
If you have never booted into Android, then you don't need to check that setting. As I said, that's the way I did it on my N6: take out of box -> charge -> boot directly into bootloader -> "fastboot oem unlock". No other steps required if you don't boot into Android first.
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
lilliput222 said:
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Click to expand...
Click to collapse
Yes, that should work for the N9 as well.
The bootloader on my Nexus 9 Android 5.1.1 is locked forever due to my mistake
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to check "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
quekl84 said:
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
Not possible. You will have to return it to HTC for repair or replacement.
quekl84 said:
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to uncheck "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
cobyman7035 said:
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
Click to expand...
Click to collapse
Yes, I forgot to check the box to allow oem UNLOCK. And now my device is locked forever.
A quick question: A lot of N9 ROMs require flashing an updated bootloader from the factory image. Aren't these bootloaders locked by default? Can we flash a factory bootloader over a custom ROM?
It seems that we might bork our Nexus 9s if we flash a locked bootloader in.
This guide is for the safe procedure for re-locking your bootloader with the new security features of Android 5.1 on the Nexus 6
The purpose of re-locking your bootloader should solely be used for RMA or resale of your device. Also if you have flashed a factory image and want the added security of a locked bootloader. Or possibly it is required by your employer. If you're required by your employer, then I suggest you reconsider unlocking in the first place. If you're returning to stock, to simply fix problems on your device, then I also strongly suggest leaving the bootloader unlocked. To put it in simple terms, if you want to keep a custom recovery and ROM, mod, root, etc, then leave your bootloader unlocked. Re-locking the bootloader on the Nexus 6 will cause your device to be wiped.
Please read this post by @efrant for more clarification:
http://forum.xda-developers.com/showthread.php?p=60128929
Thanks @efrant @cam30era @rootSU @clairez for collaboration and advice.
This is based on a 100% stock, encrypted, un-modded Nexus 6
Due to significant security changes in Android 5.1, there are some specific steps that must be taken in order to safely re-lock your bootloader during and after installing a factory image.
WARNING! These steps are confirmed working but there is still risk involved. If you do not ABSOLUTELY need to re-lock then I strongly suggest leaving the bootloader unlocked.
FOLLOWING THESE STEPS WILL WIPE YOUR DEVICE SO BACKUP YOUR DATA!
This is based on you (the user) having already read and followed instructions on downloading the factory image and having it ready to install.
STEP 1
Disable all security locks on your phone.
On your phone, go into your settings, click Security. In Screen security, click on Screen lock, enter your passcode/pin/pattern then select none.
You will get a prompt that Device protection features will no longer work. Click OK.
STEP 2
**OPTIONAL**
Thanks @gee2012
This step is optional because successful installation of the factory image will remove this info anyway.
Remove your Google account.
In settings, click Accounts, click Google then click on your account name. (your gmail address)
Click the 3 dot menu button in top right of screen and select Remove account. You will get a prompt That this will delete all messages, contacts and other data from your phone. Click REMOVE ACCOUNT.
STEP 3
This step is optional and may or may not be needed but I recommend doing this.
Preform a factory reset from your phone settings.
Open settings and click on Backup & reset. Click Factory data reset.
You will receive a prompt stating that this will erase all data from your phone's internal storage, click RESET PHONE.
The reset takes quite a while to complete, approximately 10 to 15 or more minutes for a 32gb model and 20 minutes or more for a 64gb model, so BE PATIENT!
Your phone will reboot when completed.
STEP 4
IMPORTANT!!
When your phone reboots, you will have to skip all account set up and ABSOLUTELY do not set any security features up. Skip EVERYTHING!
Go to settings and enable Developer options. (About phone>tap build number 7 times)
Once you have developer options enabled, enable USB Debugging and tick the box to allow OEM unlock.
I suggest preforming a reboot here to verify that OEM unlock sticks. After the reboot enter developer options to verify OEM unlock is still ticked.
If it is, we will proceed. If not, ensure you have followed the previous steps correctly. If you have and for some reason the setting won't stick, DO NOT PROCEED OR YOU MAY END UP STUCK IN A BOOT LOOP WITH NO CURRENT WAY TO FIX!
STEP 5
If setting has stuck, you are ready to unlock your bootloader and install the factory image using one of the ways outlined elsewhere in this forum.
After installation is complete, reboot to recovery and again preform a factory reset. Reboot to Android.
STEP 6
IMPORTANT!
Upon completion of factory reset from recovery and reboot to Android, it is important to follow this procedure so you may now safely lock your bootloader.
SKIP ALL ACCOUNT AND SECURITY SET UP AGAIN! Go to settings and enable developer options again. Enable USB debugging and tick allow OEM unlock.
Again, I recommend a reboot at this point to verify the settings stick.
Use the button combo or ADB to reboot to bootloader.
Use the command fastboot oem lock
Your device will wipe again and reboot.
CONGRATULATIONS! You now have a locked bootloader and you may proceed to restore your phone.
See here for info from Google about the new security features:
https://support.google.com/nexus/answer/6172890?hl=en
Thanks @efrant for finding this link.
Thanks also to all of those who helped to confirm this process works consistently.
Thanks to @clairez for this thread: http://forum.xda-developers.com/nexus-6/help/update-to-5-1-lock-bootloader-t3058480
*Disclamer*
I am not responsible if your device bricks, loops or causes mass world hysteria.
*How to prepare your Nexus 6 for resale*
Since the onset of Android 5.1, there are some specific steps needed to ensure you can sell your device and not have the seller need your Google password when they receive your device. Please read this guide provided by @PatimusXPrime
http://forum.xda-developers.com/showpost.php?p=60455167&postcount=43
TWRP RECOVERY INSTALLED ONLY
The following info is for users who have TWRP installed and are stuck in bootloop (soft brick) after wiping OS with a locked bootloader.
Credit to this thread:
Thanks @ixa20
http://forum.xda-developers.com/showthread.php?t=3053783
STEP 1
Boot into bootloader.
STEP 2
Use fastboot and issue the commands:
fastboot format userdata
fastboot format cache
This should allow you to boot back into TWRP.
Flash a ROM and get up and running.
Unlock your bootloader and leave it that way.
Thanks also to @rootSU for posting this solution many, MANY times.
I hear a lot about locking the boot loader, but what exactly am I missing out on in terms of security with an unlocked boot loader, and rooted
productofusa said:
I hear a lot about locking the boot loader, but what exactly am I missing out on in terms of security with an unlocked boot loader, and rooted
Click to expand...
Click to collapse
I think, primarily, if you are unencrypted you run the risk of your data being compromised if your phone is lost or stolen. Plus, the new security features are not proven to work 100% when bootloader is unlocked. Simply by rooting, you've opened your device to be more vulnerable to malicious attacks. I'm sure you already know that.
Evolution_Freak said:
I think, primarily, if you are unencrypted you run the risk of your data being compromised if your phone is lost or stolen. Plus, the new security features are not proven to work 100% when bootloader is unlocked. Simply by rooting, you've opened your device to be more vulnerable to malicious attacks. I'm sure you already know that.
Click to expand...
Click to collapse
I see, nothing I wasn't already aware of! It seems that a significant amount of people that are used to an unlocked rooted handset are quick to jump on the relock the bootloader omg security bandwagon regardless of the consequences. Having said that thanks to folks such as yourself most of the kinks seem to be worked out at this point.
Thanks
Okay, so I'm new to the whole unlocking/flashing thing.... I bought a nexus 6 from Verizon which obviously came with 5.1 out of the box. I was using stock with my google account attached and a pin lock. I successfully unlocked by bootloader and rooted with twrp and the nexus toolkit. I have also since flashed chroma. Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Cannibal Oxen said:
Okay, so I'm new to the whole unlocking/flashing thing.... I bought a nexus 6 from Verizon which obviously came with 5.1 out of the box. I was using stock with my google account attached and a pin lock. I successfully unlocked by bootloader and rooted with twrp and the nexus toolkit. I have also since flashed chroma. Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Click to expand...
Click to collapse
The first post explains how to lock the bootloader safely. If you're going g back to stock, simply follow the steps
Cannibal Oxen said:
Okay, so I'm new to the whole unlocking/flashing thing.... I bought a nexus 6 from Verizon which obviously came with 5.1 out of the box. I was using stock with my google account attached and a pin lock. I successfully unlocked by bootloader and rooted with twrp and the nexus toolkit. I have also since flashed chroma. Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Click to expand...
Click to collapse
No, not at all. You can flash a factory image and return to stock at anytime. However, if you plan on flashing ROMs again, there's no need to relock the bootloader. For instance, if you wanted to return to stock to say, get an OTA, the bootloader being unlocked wouldn't affect that negatively.
If you did desire to relock, following this guide, as far as disabling the security and Google account, you should be able to relock. The important thing is making sure that pesky "allow OEM unlock" option remains checked after a reboot.
Cannibal Oxen said:
Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Click to expand...
Click to collapse
You can go back to stock. And then, subsequently relock the bootloader.
And the question is not "stupid". Noob questions are encouraged here. That's how you learn.
rootSU said:
The first post explains how to lock the bootloader safely. If you're going g back to stock, simply follow the steps
Click to expand...
Click to collapse
Fair enough. The part that confused me was the first five steps appear to address steps required to unlock the bootloader. I was afraid since I already unlocked mine without first disabling security and removing my account that it would somehow preclude me from ever being able to relock the bootloader should that need ever arise in the future.
I really appreciate the help!
Yeah, I learned my lesson, DON'T PLAY WITH LOCKED BOOTLOADERS ON THIS DEVICE, EVER!
I had a locked bootloader, and no System (I had wiped it accidentally).
Luckily though I had the sense to keep TWRP installed, but I couldn't boot to it, it was just bootlooping to the TWRP splash screen.
I thought I had just lost a $650 investment, but here's what I did:
Boot to bootloader, then
Code:
fastboot erase cache
fastboot erase userdata
Then I could boot to TWRP! So I
Code:
adb push (ChromaOS zip here) /sdcard/
But when I tried to flash the Data and Cache partitions kept giving me errors, I couldn't flash anything!
I went to sleep (or tried to sleep, but couldn't) I was panicking!
When I woke up I tried one more thing:
From bootloader I did
Code:
fastboot format cache
fastboot format userdata
(Notice FORMAT instead of erase!)
I booted into TWRP and was able to flash ChromaOS, I was able to enable OEM Unlock, and flashed the full Factory Image, completely back to stock.
I booted once with unlocked bootloader to verify it was working, then locked it.
If I had the stock recovery, I would've had a $650 paperweight.
DO NOT MESS AROUND WITH LOCKED BOOTLOADERS! DON'T RISK IT!
gorei23 said:
Yeah, I learned my lesson, DON'T PLAY WITH LOCKED BOOTLOADERS ON THIS DEVICE, EVER!
I had a locked bootloader, and no System (I had wiped it accidentally).
Luckily though I had the sense to keep TWRP installed, but I couldn't boot to it, it was just bootlooping to the TWRP splash screen.
I thought I had just lost a $650 investment, but here's what I did:
Boot to bootloader, then
Code:
fastboot erase cache
fastboot erase userdata
Then I could boot to TWRP! So I
Code:
adb push (ChromaOS zip here) /sdcard/
But when I tried to flash the Data and Cache partitions kept giving me errors, I couldn't flash anything!
I went to sleep (or tried to sleep, but couldn't) I was panicking!
When I woke up I tried one more thing:
From bootloader I did
Code:
fastboot format cache
fastboot format userdata
(Notice FORMAT instead of erase!)
I booted into TWRP and was able to flash ChromaOS, I was able to enable OEM Unlock, and flashed the full Factory Image, completely back to stock.
I booted once with unlocked bootloader to verify it was working, then locked it.
If I had the stock recovery, I would've had a $650 paperweight.
DO NOT MESS AROUND WITH LOCKED BOOTLOADERS! DON'T RISK IT!
Click to expand...
Click to collapse
With the method I've outlined and personally tried, it can be safely done. The security settings are the issue and a safe way around that has been found.
Evolution_Freak said:
With the method I've outlined and personally tried, it can be safely done. The security settings are the issue and a safe way around that has been found.
Click to expand...
Click to collapse
I know, I'm just saying don't play around with it, if you're going to relock make sure that you KNOW it will work.
Can confirm that the outlined info here works flawlessly
I used this process to re-lock my phone after unlocking in the fastboot-enabled upgrade from OTA 5.1 "D" to stock 5.1 "E" an hour ago.
The easy part was unlocking/locking/rebooting in the correct order - the harrowing part was when my fastboot update of the radio failed, after which I figured out it was a transient USB issue with my system, so rebooted Windows and then everything went reasonably close to plan.
So, now I'm on "E" and with a locked bootloader (i.e., stock for Verizon). I'll be experimenting with custom ROMs after settling in with this for a bit, but wanted to test out VoLTE and other things before going the custom route.
Thanks again for this guide.
- ooofest
ooofest said:
I used this process to re-lock my phone after unlocking in the fastboot-enabled upgrade from OTA 5.1 "D" to stock 5.1 "E" an hour ago.
The easy part was unlocking/locking/rebooting in the correct order - the harrowing part was when my fastboot update of the radio failed, after which I figured out it was a transient USB issue with my system, so rebooted Windows and then everything went reasonably close to plan.
So, now I'm on "E" and with a locked bootloader (i.e., stock for Verizon). I'll be experimenting with custom ROMs after settling in with this for a bit, but wanted to test out VoLTE and other things before going the custom route.
Thanks again for this guide.
- ooofest
Click to expand...
Click to collapse
Word of caution, don't flash stuff with a locked bootloader. If you get a bad flash and you can't boot, you'll be screwed.
Doesn't the setting in developer optionsto allow OEM unlock of the bootloader reset every boot on the new firmware? I know mine does on meanpop and chroma both 5.1 roms
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
pwned3 said:
Doesn't the setting in developer optionsto allow OEM unlock of the bootloader reset every boot on the new firmware? I know mine does on meanpop and chroma both 5.1 roms
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yes
pwned3 said:
Doesn't the setting in developer optionsto allow OEM unlock of the bootloader reset every boot on the new firmware? I know mine does on meanpop and chroma both 5.1 roms
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
It does if you have "Device protection" enabled. If you do a factory reset and, while you are running through the set up wizard, do not enable "Device protection", then the " Allow OEM unlock" setting should stick.
Sent from my Nexus 6 using Tapatalk
rootSU said:
Word of caution, don't flash stuff with a locked bootloader. If you get a bad flash and you can't boot, you'll be screwed.
Click to expand...
Click to collapse
Before attempting to upgrade the stock level or going custom, I was planning to run through at least steps 1-4 again to enable me to safely unlock.
Or, do I only need to tick OEM Unlock, adb into stock recovery and then fastboot oem unlock without going through the suggested factory data reset step?
- ooofest
Guys,
I have some very noob questions about flashing that I would like to solve :
1) is normal that fastboot connection works only after setting the device for "allow own unlock" and "USB debugging"?
2) I might flashing my devices without unlocking the bootloader? And what about flashing original firmwares from Motorola?
(I ask because my bootloader is locked under status "2")
2) I tried to flash my device and, despite of several "preflashing" errors, my device still showing status 2 on bootloader, but it started showing that "unlocked bootloader warning" when it starts, is that normal? How to solve it?
3) I might flashing an older firmware (update September ) than I already have in my device (December)?
4) what is the function of recovery mode on bootloader ? I
Sent from my XT1575 using Tapatalk
Belotto said:
Guys,
I have some very noob questions about flashing that I would like to solve :
1) is normal that fastboot connection works only after setting the device for "allow own unlock" and "USB debugging"?
2) I might flashing my devices without unlocking the bootloader? And what about flashing original firmwares from Motorola?
(I ask because my bootloader is locked under status "2")
2) I tried to flash my device and, despite of several "preflashing" errors, my device still showing status 2 on bootloader, but it started showing that "unlocked bootloader warning" when it starts, is that normal? How to solve it?
3) I might flashing an older firmware (update September ) than I already have in my device (December)?
4) what is the function of recovery mode on bootloader ? I
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
OK...My first and main recommendation is DO NOT start trying to flash, mod, or do anything outside of using the phone as intended yet. These questions show that you have very limited knowledge on these subjects and if you continue as is, you will most likely get yourself into a bind you can't get out of, such as hard bricking your device.
Questions 1 and 4 are Bootloader/Fastboot/Rooting 101 topics. Until you have read up thoroughly on these, please don't think about proceeding. The rest of your questions have been answered here in the forums. I can't stress this enough: RESEARCH, READING, AND READ SOME MORE!!! No one here is obligated to help you fix any mess you get into so you need to be able to help yourself first. If you have attempted to fix an issue, and can give some details on what has been tried, you will find that most likely, there will be some who will step forward to assist, but most will not rehash a full step by step of everything.
Please do not think I am trying to blow you off. I am merely trying to prevent you from creating a problem that cannot be fixed. Having at least a basic working knowledge of how FastBoot, Bootloader, and flashing ROMs work on this device is a must. But I will answer your question 3: Do not under any circumstances try to "downgrade" your stock rom on the phone to a previous security update. This does create major issues.
@Belotto
2. Only upper/the same version of stock rom.
Status code 2 - locked by user. Did you buy used phone?
4. Recovery mode(stock, 3e) is for factory reset f.e.
dzidexx said:
@Belotto
2. Only upper/the same version of stock rom.
Status code 2 - locked by user. Did you buy used phone?
4. Recovery mode(stock, 3e) is for factory reset f.e.
Click to expand...
Click to collapse
I haven't. I have unlocked , used custom roms for a time and flashed stock and locked again before. Did it just following to guides available here.
In that time I did not have any trouble doing that lol
Sent from my XT1575 using Tapatalk
Belotto said:
I haven't. I have unlocked , used custom roms for a time and flashed stock and locked again before. Did it just following to guides available here.
In that time I did not have any trouble doing that lol
Click to expand...
Click to collapse
Just in case you are not aware, having an unlocked bootloader does not prevent you from taking OTA updates. You can just leave it unlocked. The unlocked bootloader warning doesn't bother me so I just ignore it.
If you just wanna get rid of bootloader warning then look at
https://forum.xda-developers.com/mo...o-remove-unlocked-bootloader-warning-t3201141
Make sure you are on stock(software status: offical)
You will recieve the ota
Thanks all you guys.
Despite of some strange things, I could take out the warning logo.
Now, its "oficial", status "2" and no warning. So I can sell it without discussion.
hello all,
im currently working on a samsung S4 (GT-I9515) and i ran into a small problem.
i have rooted phones more then ones and i know the drill more or less.
but when i tried to sellect the unlock oem option in the dev options it was not there.
normally it is located under bluetooth HCI-snooplog and above Process stats but the oem unlock option seems to be non existing on this phone
can someone tell me whats wrong or is it not needed ? Because i did get a message when i tried to install something trough the default recovery menu that the system was still locked. (also it runs android 5.0.1(lolipop))
Best regards,
Darkdevel
You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.
Pwnycorn said:
You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.
Click to expand...
Click to collapse
true i also tried using twrp but when in boot twrp i cant swipe/select anything of the first screen do you have another idea what i can use ?
What are you trying to unlock with "unlock OEM option"?
audit13 said:
What are you trying to unlock with "unlock OEM option"?
Click to expand...
Click to collapse
well as far as i know i need it so i can try to flash a new android version on it im trying force 6.0 on it and yes i know there is no S4 (i9515) android 6.0 version but i still want to try and do it its a old phone anyway
ppl you can forget about this post i found the problem more or less first off i had the wrong twrp version that caused the bug on twrp afterward it was all smooth sailing
for all the other ppl who want a non official android 6.0
go to youtube and look for:
install Android 6.0.1 Marshmallow Galaxy S4 GT-I9515
posted by ما لا تعلم ?
all the files you need are in the discription
Best regards,
Darkdevel
Pwnycorn said:
You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.
Click to expand...
Click to collapse
But you can't install a CR without OEM unlocked.
I am having the same problem right now (same device, gt-i9515), no OEM unlock option in developer options.
I kinda need it to install TWRP, it won't let me do it otherwise. I openned a new thread about it and explained the issue I have in more details.
FurySh0ck said:
But you can't install a CR without OEM unlocked.
I am having the same problem right now (same device, gt-i9515), no OEM unlock option in developer options.
I kinda need it to install TWRP, it won't let me do it otherwise. I openned a new thread about it and explained the issue I have in more details.
Click to expand...
Click to collapse
Dude, all S4 models, except for the Verizon and AT&T models, have an UNLOCKED BOOTLOADER.
An OEM Unlock option is, therefore, redundant because there is absolutely nothing to unlock. And the ones that do have a locked bootloader CAN'T BE UNLOCKED.
If you want TWRP follow a guide on how to install it. They even have one on the TWRP website and nowhere does it say that you need to OEM unlock. In fact, no S4 rooting/twrp flashing guide will mention any OEM unlock option.
If it does, it's garbage.
Pwnycorn said:
Dude, all S4 models, except for the Verizon and AT&T models, have an UNLOCKED BOOTLOADER.
An OEM Unlock option is, therefore, redundant because there is absolutely nothing to unlock. And the ones that do have a locked bootloader CAN'T BE UNLOCKED.
If you want TWRP follow a guide on how to install it. They even have one on the TWRP website and nowhere does it say that you need to OEM unlock. In fact, no S4 rooting/twrp flashing guide will mention any OEM unlock option.
If it does, it's garbage.
Click to expand...
Click to collapse
It's very strange then. When I had a root (same device gt-i9515 for SURE), I managed to flash TWRP on my first try, no mistakes.
I recently flashed a firmware (from sammobile. I9515XXU1BOE3_I9515DBT1BOE1_DBT, because my PDA is i9515xxu1boe3) and wiped everything. It's like a new device now.
In it's current state (non-root) I couldn't install TWRP via the same method I did before (ODIN + TWRP.tar).
About the comment on the other thread, yes, I am sure it's gt-i9515 and I know that if the USB is getting disconnected, ODIN writes it on screen, so I could see it.
Here's the guide that told me about OEM: http://www.theandroidsoul.com/how-to...ry-using-odin/ (I understand that it's a trash guide lol)
Update:
I finally did it, explained here: https://forum.xda-developers.com/ga...p-cr-galaxy-s4-gt-i9515-t3668461#post73680660
Thanks for your help!