Related
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
timour79 said:
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
Click to expand...
Click to collapse
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Billchen0014 said:
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Click to expand...
Click to collapse
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
Alright, thanks
Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
What's your reason for wanting it relocked?
Sent from my HTC Vision using xda app-developers app
noneabove said:
What's your reason for wanting it relocked?
Click to expand...
Click to collapse
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Nate2 said:
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Click to expand...
Click to collapse
Well I dont want to completely void the warranty, unless rooting already does that. If it was mine then i would've unlocked and rooted. I'd probably already have a rom and kernel on it. But it's actually my dad's, and he said I can root it if I don't do anything too serious(like I said, I just want Superuser so I can use things like the sixaxis controller app.)
comminus said:
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
Click to expand...
Click to collapse
Would that be manual rooting?
NRT questions
hey there
have some newb questions about rooting along the same lines of the OP. hope you can help me
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
sorry for the newb questions but there are so many different guides out there and some of them refer to older versions of the NRT so just want to clarify these points.
timour79 said:
Would that be manual rooting?
Click to expand...
Click to collapse
No. All you are doing there is unlocking the bootloader. Unlocking the bootloader is the equivalent of pre-heating your oven. You haven't messed with any ingredients or cooked anything yet.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
Lemegeton300 said:
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
Click to expand...
Click to collapse
1. The chances are pretty slim for permanently bricking. That is the beauty of Nexus devices - the entire factory image is available to be flashed back on if you screw things up. That is the equivalent of reformatting your harddrive & reinstalling your OS on your desktop.
2. mkskip's toolkit will install it for you. I am sure wug's will too.
3. You don't have to install CWM, especially if you are thinking that you will pretty much always stay stock. But, the bug might hit you in a month or two to start playing around, and then CWM or TWRP is your friend. I installed CWM & made a backup pretty quickly in case I do something I shouldn't, such as accidentally deleting a vital system app. That way you do not have to do the factory reinstall route. Every few weeks you can make yourself a fresh backup just for fun.
4. You should be fine - the drivers must be working if the toolkit is doing backups for you. I am assuming you are using mkskips toolkit based on this question - his instructions say that sometimes in 1 step it says drivers didn't install correctly when they actually do - Windows is...Windows. If you want to be sure, ask away on mkskip's thread. He is quite helpful.
5. If you reflash the factory image & the bootloader is relocked, there is nothing for them to see...not that they'd really care since the point of a Nexus is to develop on it. You would only be returning it for a hardware issue, and the software unlocking has no impact on the hardware problem, since your hardware issue would've happened no matter what software you had on it. The only way a software thing could cause a hardware issue would be if you over-overclocked it & cooked some parts. You'd really have to work at doing that since these things usually shut down when the temperature gets too high.
In short: root it & enjoy it!
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Lemegeton300 said:
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes. When you restore a backup it will be just as it was when you made it. Have fun!
Ultra Noob here
So I had my first android-TF700 for about 10 days. Played around with it, read around this site and realized it was a tablet for someone with experience.
So I now have an N10. Charged, not even turned on yet. What should be my next steps? I see a couple toolkits,an auto root, and ASOP-
What would you suggest a noob start with?
I know, I know, turn it on
Thanks!
Depends on what you want to accomplish with the device. If you want to try or at least gain some understanding as to the different features you might be interested in, read the first post of the different ROMs available and see if anything sounds enticing.
I personally use me for taking media with me on the go, be it news or videos, so I don't have to carry a laptop around. I'm on CM10.1 right now but cycle through every rom to see how everything works. Good luck!
Sent from my Nexus 10 using XDA Premium HD app
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
rauschkugl said:
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
Click to expand...
Click to collapse
And how do you unlock the bootloader and install root?
What do you mean a custom recovery?
Are there other ways to root the device with out wiping it? Seems like most android smartphone you can load up an exe or something to shift the su app around or something.
Thanks.. (still waiting for my N10 to arrive.. meanwhile.. still playing with my ICS Bionic)
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
rauschkugl said:
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
Click to expand...
Click to collapse
Found the threads. Look easy enough to follow. Something I'm not understanding . What does it mean to install a recovery? whats the purpose of that. I've search and (at least not yet) found a good description of what/why that it. I'm sensing that devices are different (duh!) and I didnt need to install a "recovery" on my Droid Bionic when I rooted it, but this N10 must be different.
With the custom recovery you're able to install zip files, make a backup of your Rom,... You can't do that with the recovery that comes with the nexus 10.
Recovery is like a separate system that you can boot to, if you want to mess with the main Android OS. Like rauschkugl said, you can boot to a custom recovery to flash different ROMs that are distributed in flashable ZIP files. You can also make (or if anything goes wrong, revert to) a complete backup of the device's internal memory.
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
Great questions. You are one step ahead of me on my new N10. I've not turned it on yet, really wanting to, but I dont want to do much to it, until after I unlock/root/ and learn how to make backups. Though since i've got a TBpro license, I'll probably use that. I dont want to tweak the OS. so I think I need root just to be able to run TBpro. I just want to be sure I'll still get OFA updates, and I want to learn more about if and how backup work for a multi-user N10.
EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
I would suggest straight away that you perform a backup with TWRP, so that if you decide to delve deeper into ROMs and playing with your system files, you'll have a completely stock backup to rely on. Simply boot into recovery and select 'Backup', then you can rename the backup file if you want, then swipe the slider across and wait, then you're done!
When it comes to system updates, you'll most likely have to use your root toolkit to unroot the device, else the update will fail. You can however continue to update all your apps as you normally would. Hope this helped
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
EraVulgaris said:
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
Click to expand...
Click to collapse
Sounds like a great success then so are you saying that you performed the system update while you were rooted and you retained the root access?
Nope. Got the OTA system update and it knocked me off root. But I got it back easily with the toolkit.
So I am going to be getting a N7 for Christmas, and I was wondering, should I root and unlock the tab before even setting it up? And should I accept the 4.2.1 update before or after doing all this?
Outdated yet young Motorola Photon 4G
I just did mine today on nexus 4 and 7. I had to read everything carefully to find out this was the method that I find it was easy. Make sure you read everything first. Look at the video for 4 and it should be similar to 7 and instructions are provided in link as well. btw I rooted it on 4.2.1.
As rooting will factory reset your device, it will delete all your data. Make sure you backup first.
http://forum.xda-developers.com/showthread.php?t=1766475
Do yourself a favor and learn to do it manually first before using toolkits. There is a lot of tutorials on doing so.http://forum.xda-developers.com/showthread.php?t=1741395 Use fastboot to unlock device:
Command= fastboot OEM unlock
Select yes on your device to unlock boooader.
Install a custom recovery( I would reccomend twrp) and flash supersu zip and you are now rooted.
Need to go back to stock then this is great http://forum.xda-developers.com/showthread.php?t=1907796
Yes toolkits do work but if things go wrong its good to know what to do.
Travisdroidx2 said:
Do yourself a favor and learn to do it manually first before using toolkits. There is a lot of tutorials on doing so. Use adb to unlock device:
Command= adb OEM unlock
Select yes on your device to unlock boooader.
Install a custom recovery and flash supersu zip and you are now rooted.
Need to go back to stock then this is great http://forum.xda-developers.com/showthread.php?t=1907796
Yes toolkits do work but if things go wrong its good to know what to do.
Click to expand...
Click to collapse
I had no intention of using a toolkit lol. Link to the best method to root/unlock?
Outdated yet young Motorola Photon 4G
Lol good deal added another link that you are looking for.
http://forum.xda-developers.com/showthread.php?t=1741395
Travisdroidx2 said:
Lol good deal added another link that you are looking for.
http://forum.xda-developers.com/showthread.php?t=1741395
Click to expand...
Click to collapse
Answered my edit before I could post it. You read my mind!
Outdated yet young Motorola Photon 4G
Nexus 7 root and unlock.
Slender Troll said:
So I am going to be getting a N7 for Christmas, and I was wondering, should I root and unlock the tab before even setting it up? And should I accept the 4.2.1 update before or after doing all this?
Outdated yet young Motorola Photon 4G
Click to expand...
Click to collapse
I bought my Nexus 7 about 2 weeks ago. I set it up then downloaded the jb 4.2.1 update. You will have to unlock before you root. I then downloaded Wugfresh Nexus 7 Tool kit to my computer. Very easy to follow instructions. The kit will take you through the steps on unlocking and rooting. There are videos on this procedure. I did not flash CWM and opted to flash TWRP. Excellent recovery system. I downloaded Goo manager app and you can install TWRP within the app. Very easy. You can then make nandroid backups and install custom roms. I am currently on Cyanogenmod 10.1 nightly.Cyanogenmod now has an updater within and it will search for new nightlys and also install them. Very easy. Hope this helps.
I do prefer twrp over cwm. And I was a long time cwm user before. You can fastboot the twrp.IMG file. And if you Fastboot twrp you will not have to rename .bak the stock recovery.
And yes you will want to unlock it and root it first thing since the unlock wipes the entire device.
What's the difference between CWM and TWRP?
Edit: Swipe was acting up.
Outdated yet young Motorola Photon 4G
In my opinion twrp gets more support and updates. Is way faster than cwm and you will never look back. Twrp is a great recovery.
Ok. So if/when I root the 7, I will be using a computer running windows xp, and I don't know how to install the correct files and where.
Outdated yet young Motorola Photon 4G
Hey, I'd like you to help me decide whether I should root my Nexus 7 or not. This is my first android device and I'm a complete 'noob.' Since then I've been reading about rooting continuously and I would've done it already but I'm a bit concerned. I don't want to lose my warranty and I'm aware that I can unroot the device to get my warranty back but what if something happens to the screen or the power button, or what if it bricks after losing battery power? (I read somewhere that this happened to him during night, the device ran out of juice and he couldn't turn it on ever again) Would I still be able to unroot it so I could return it for repair?
My other concern is about the rooting process itself. I've read that it's 99% safe with a toolkit but anything can go wrong. Is this 1% a big risk? Would I be able to unbrick it if something happened? Since I'm a noob my only reason to root my device is to be able to run memory editors like gamecih or something like that. Are the risks worth it?
Thank you for your answers.
BenFuF said:
Hey, I'd like you to help me decide whether I should root my Nexus 7 or not. This is my first android device and I'm a complete 'noob.' Since then I've been reading about rooting continuously and I would've done it already but I'm a bit concerned. I don't want to lose my warranty and I'm aware that I can unroot the device to get my warranty back but what if something happens to the screen or the power button, or what if it bricks after losing battery power? (I read somewhere that this happened to him during night, the device ran out of juice and he couldn't turn it on ever again) Would I still be able to unroot it so I could return it for repair?
My other concern is about the rooting process itself. I've read that it's 99% safe with a toolkit but anything can go wrong. Is this 1% a big risk? Would I be able to unbrick it if something happened? Since I'm a noob my only reason to root my device is to be able to run memory editors like gamecih or something like that. Are the risks worth it?
Thank you for your answers.
Click to expand...
Click to collapse
In all honesty, a toolkit is almost completely unnecessary for the Nexus 7. You can do everything yourself in about 5 minutes. The thing about the Nexus 7 is that Google knew that people would try and do things with it, so they made it easy (How it should be with every device). One thing you should take into consideration when unlocking/rooting any device is "Why am I doing this?" If the answer is "Cuz I can!", you probably shouldn't. If you want to be able to use advanced apps that require root, go right ahead. Even if you are having performance problems, and just want to fix them by installing a new ROM after you unlock, go for it. If not, don't worry about it.
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
I'm getting a 6p for Christmas and I have a question.
Say the 6p is on Marshmallow, and I decide to unlock the bootloader (just that, no root or anything) on MM. Will I be able to update to 7.1.1 via ota (no I don't want to sideload or flash) without issues? Or is there a process to it like updating bootloader, vendor, radio or whatever else. Or does the Ota file contain the updated boot.img and vendor etc.
ricbaez said:
I'm getting a 6p for Christmas and I have a question.
Say the 6p is on Marshmallow, and I decide to unlock the bootloader (just that, no root or anything) on MM. Will I be able to update to 7.1.1 via ota (no I don't want to sideload or flash) without issues? Or is there a process to it like updating bootloader, vendor, radio or whatever else. Or does the Ota file contain the updated boot.img and vendor etc.
Click to expand...
Click to collapse
Yes, you can unlock then update via OTA. OTAs patch every partition permitted there are no modifications done to system and boot.
Sent from my Nexus 5X using Tapatalk
ricbaez said:
I'm getting a 6p for Christmas and I have a question.
Say the 6p is on Marshmallow, and I decide to unlock the bootloader (just that, no root or anything) on MM. Will I be able to update to 7.1.1 via ota (no I don't want to sideload or flash) without issues? Or is there a process to it like updating bootloader, vendor, radio or whatever else. Or does the Ota file contain the updated boot.img and vendor etc.
Click to expand...
Click to collapse
Why would you want to unlock the bootloader if you don't intend to root or install a custom recovery? I don't understand what the benefit is.
jhs39 said:
Why would you want to unlock the bootloader if you don't intend to root or install a custom recovery? I don't understand what the benefit is.
Click to expand...
Click to collapse
I actually intend to install megapixel rom
jhs39 said:
Why would you want to unlock the bootloader if you don't intend to root or install a custom recovery? I don't understand what the benefit is.
Click to expand...
Click to collapse
@ricbaez
No disrespect, but I would say why would you NOT unlock the bootloader on a Nexus? Especially when you first get the phone because unlocking wipes it. Unlocking the bootloader allows you to use MANY more tools in the event your phone boot loops or becomes unresponsive. There are dozens of threads where people are completely screwed because they did NOT unlock the bootloader and so cannot salvage their device with ADB/Fastboot. If you bought a Nexus, one of the selling points is that Google ALLOWS the owner to unlock the bootloader right in the Dev Options! Even if the OP is not going to root or install a custom recovery, if he/she does not unlock the bootloader, they are going to be S.O.L. if the phone won't boot. There are many examples of this since Google has gone to the monthly security OTA's and updates. Or... simply put, if you are unlocked you can flash full Google images and use ADB/Fastboot. If you are locked, you can only sideload an OTA with the stock recovery and that hasn't been working out well for so many people here on XDA.
To the OP. Recommend you unlock your bootloader first thing which will wipe the phone and start you out fresh. Unlocking the bootloader will not prevent you from receiving OTA's. Make sure your Google login works properly. Login. Logout. Login. Then do whatever the F you want with your phone, knowing you will have serious options to recover in the event things go south for any reason. Next would be installing TWRP. Good luck!
v12xke said:
@ricbaez
No disrespect, but I would say why would you NOT unlock the bootloader on a Nexus? Especially when you first get the phone because unlocking wipes it. Unlocking the bootloader allows you to use MANY more tools in the event your phone boot loops or becomes unresponsive. There are dozens of threads where people are completely screwed because they did NOT unlock the bootloader and so cannot salvage their device with ADB/Fastboot. If you bought a Nexus, one of the selling points is that Google ALLOWS the owner to unlock the bootloader right in the Dev Options! Even if the OP is not going to root or install a custom recovery, if he/she does not unlock the bootloader, they are going to be S.O.L. if the phone won't boot. There are many examples of this since Google has gone to the monthly security OTA's and updates. Or... simply put, if you are unlocked you can flash full Google images and use ADB/Fastboot. If you are locked, you can only sideload an OTA with the stock recovery and that hasn't been working out well for so many people here on XDA.
To the OP. Recommend you unlock your bootloader first thing which will wipe the phone and start you out fresh. Unlocking the bootloader will not prevent you from receiving OTA's. Make sure your Google login works properly. Login. Logout. Login. Then do whatever the F you want with your phone, knowing you will have serious options to recover in the event things go south for any reason. Next would be installing TWRP. Good luck!
Click to expand...
Click to collapse
You are right. I wasn't aware that people were having boot loop issues on phones running stock Android but that apparently is the case. But as long as USB Debugging and Allow OEM Unlock are ticked in the developer options you should be able to unlock the bootloader later through ADB if you need to. I assumed the warning about my phone being insecure since my bootloader is unlocked that pops up every time I boot was there for a reason. There is no security issue created by unlocking your bootloader?
jhs39 said:
You are right. I wasn't aware that people were having boot loop issues on phones running stock Android but that apparently is the case. But as long as USB Debugging and Allow OEM Unlock are ticked in the developer options you should be able to unlock the bootloader later through ADB if you need to. I assumed the warning about my phone being insecure since my bootloader is unlocked that pops up every time I boot was there for a reason. There is no security issue created by unlocking your bootloader?
Click to expand...
Click to collapse
It's cool, and I respect your decision to stay locked if you decide that is best for you. I suppose you could set Allow OEM unlock in Dev settings AND USB debugging in USB just in case, but if for some reason you could not boot, unlocking bootloader would then wipe userdata and your backups would be gone before you could transfer them off. In the end it's up to the individual to choose security vs, recoverability. Many ppl are getting locked out of their phones in the interest of security (or just the default settings). As it turns out, they were just trying to perform a monthly security update and hosed their phone. Stock rom, stock recovery, unrooted. Every Nexus phone I've owned (Galaxy?) has been unlocked so that I could use all the tools available to get myself out of a bind if needed. I don't give a sh!t about the boot up warning, because I know that my nandroid and FF backups can get me back home in the event of a lockup. Unlocking will not stop you from receiving OTA's if you are stock. Even if you are not, unlocking will allow you to use ADB, custom recoveries, toolkits, etc. If you end up in a bootloop and your bootloader is locked you are S.O.L. plain and simple. Each to their own though... if you need encryption and value high security of your data over recoverability then you may want to stay bootloader locked. As owners of a Nexus phone we have that option. Many others do not. Cheers my friend!
Thank you guys everything was successful, unlocked it in no time, downloaded 7.1.1 and it's perfect. NOw time to flash twrp and MegaPixel Rom