Went thru other problems in here but none of them worked.
I'm using Nexus Root Toolkit 1.8.2.
Everything seems to work except when Unlock finishes, it does not go back to "new" state. Everything is still there: all my apps, settings, everything.
I tried another USB port, another USB cable, and then used a different computer and went thru it all again. Same problem.
I made sure I set it to v2 and 4.4.2 KOT49H. Went thru the drivers setup. Everything passed after I followed all the instruction.
I even tried to Root it and still nothing. It reboots, it does everything it's supposed to do. I even watched the video on their webpage about my Nexus. It does exactly as it should, except when it comes out of unlock, apparently it's not unlocked.
Maybe try a different root program?
goofy173 said:
Went thru other problems in here but none of them worked.
I'm using Nexus Root Toolkit 1.8.2.
Everything seems to work except when Unlock finishes, it does not go back to "new" state. Everything is still there: all my apps, settings, everything.
I tried another USB port, another USB cable, and then used a different computer and went thru it all again. Same problem.
I made sure I set it to v2 and 4.4.2 KOT49H. Went thru the drivers setup. Everything passed after I followed all the instruction.
I even tried to Root it and still nothing. It reboots, it does everything it's supposed to do. I even watched the video on their webpage about my Nexus. It does exactly as it should, except when it comes out of unlock, apparently it's not unlocked.
Maybe try a different root program?
Click to expand...
Click to collapse
Did you try unlocking manually by using the fastboot drivers? See if that works.
How do I do that? Its that something within Nexus Root Toolkit?
I tried manually putting it into bootloader and then running the toolkit with no luck
I have these options on the bootloader:
Restart Bootloader
Recovery Mode
Power Off
Start
At the bottom I have:
FASTBOOT MODE
PRODUCT NAME - flo
VARIANT - flo 32G
HW VERSION - rev_e
BOOTLOADER VERSION - FLO-04.02
CARRIER INFO - None
SERIAL NUMBER - 05858bae
SIGNING - yes
SECURE BOOT - enabled
LOCK STATE - unlocked
Does that last one mean it's already unlocked?
Here's what I did:
I tried another method. I got the clockwork recovery image, SuperSU and Fastboot.
I opened a command prompt to get it into bootloader but it never worked so I did it manually.
I typed fastboot oem unlock and that worked. It looks like its already unlocked.
Rebooted but all my data was still there.
Then I typed fastboot flash recovery recovery-clockwork-6.0.4.3-flo.img (Now I see WiFi only I was supposed to use 6.0.4.4, oh well)
and it said it was successful. When I rebooted it was back the way it always is, with my data.
I sent ahead with the root by copying SuperSU.zip over to the root directory.
Rebooted to recovery mode
and install teh zip file
It all said it worked but I rebooted and it's still all the same.
Now this would have normally told me it was already rooted, but I tried to install an adblocker the other day that required a rooted tablet, and it said it could perform the install because it wasn't rooted.
So???
Unlocking the bootloader destroys your data. If they're still there, I doubt you successfully unlocked the bootloader. Check by powering down. Boot back up. You should see the word Google followed by an icon of an open lock if you successfully unlocked the bootloader.
Sent from my Nexus 7 using Tapatalk
exglynco said:
Unlocking the bootloader destroys your data. If they're still there, I doubt you successfully unlocked the bootloader. Check by powering down. Boot back up. You should see the word Google followed by an icon of an open lock if you successfully unlocked the bootloader.
Click to expand...
Click to collapse
I've had that open lock icon from when I first got the tablet.
I don't think i can post images.
https://www.dropbox.com/s/is51bsgh11zxkcu/100_1690[1].JPG
I tried 2 other root required apps, one which is for checking if it rooted, and it said it wasn't, and a root-required app also said it wasn't.
Dude you are already unlocked. If it says in bootloader mode that you are unlocked and you have the unlock symbol when you boot you are unlocked. You just need to root. Rooting is is not the same as unlocking your bootloader. To root you can either use a toolkit. Or get the LATEST Supersu flashable zip file. Then download the Supersu app from the play store and update your binaries
Sent from my SCH-I535 using Tapatalk
And I've done both of those and neither has rooted it. Says it did it, but when I check it with 2 apps that require a rooted tablet, it says it's not rooted. I dl'ed a root check app and it also says its not rooted. Gonna go thru it again right now.
And it worked with Nexus Root Toolkit and just clicking root and following everything from then on out.
not sure where I messed up. Not even sure that mine came already unlocked now. Maybe I unlocked it the first time I tried?
Anyway, the root checker app said its rooted! Thanks for your help as this is my first root of anything.
I guess since I never lost my data and apps since I first started trying to root this Nexus yesterday, it must have already been unlocked, since from my understanding, unlocking it would have lost the apps and data and took it back to as-new setup.
goofy173 said:
I guess since I never lost my data and apps since I first started trying to root this Nexus yesterday, it must have already been unlocked, since from my understanding, unlocking it would have lost the apps and data and took it back to as-new setup.
Click to expand...
Click to collapse
Unlocking doesn't delete your apps. But it does delete everything on the internal SD card
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
Unlocking doesn't delete your apps. But it does delete everything on the internal SD card
Click to expand...
Click to collapse
oh. I figured that was everything. I do remember at one point I had to put my password in manually to connect to my router. Must have been when it unlocked.
Now when I just did my daughter's Nexus 7 (2012) it did erase everything and took it back to original, but she's only had a for a week so she can reinstall everything.
Related
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Dynesh said:
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Click to expand...
Click to collapse
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
xIC-MACIx said:
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
Click to expand...
Click to collapse
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Well, I tried to run that program from the link, and it said some files were missing, so I stopped it. I tried to flash clockwork mod recovery and when it booted back into Android to rename the files, it got stuck on waiting on ADB. Frustrating.
Dynesh said:
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Click to expand...
Click to collapse
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
xIC-MACIx said:
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
Click to expand...
Click to collapse
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Glad it's working, Android can be temperamental at times & the issue is typically caused by the small things!
Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
kane1513 said:
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
Click to expand...
Click to collapse
I rooted using this method.
http://forum.xda-developers.com/showthread.php?t=2001868
I did have to unlock the bootloader so I did lose everything, but it wasn't that hard and I did it early enough that I didn't lose too much of what I had on there.
So i'm new to android but i continued to root my device. I did it the "legit" way. No tool kit. I installed drivers. ADB and used bootloader. I unlocked the bootloader when the dialog popped on my phone. I navigated and selected "unlock the bootloader" sideloaded clockworkmod touch. Installed supersu from sdcard. Booted up and i still have my pictures and i even found a folder on the phone from the gosms app I had. I know im properly rooted because i was able to flash paranoid rom 3 successfully. Everywhere i've been reading states unlocking the bootloader wipes everything! My question is this normal?
Its standard protocol made by Google. Yes its normal. Just remember if you have stuff on your storage to make sure you back up your storage before unlocking
Jsparta26 said:
Its standard protocol made by Google. Yes its normal. Just remember if you have stuff on your storage to make sure you back up your storage before unlocking
Click to expand...
Click to collapse
standard protocol but it didn't wipe...lol
BugJuice said:
standard protocol but it didn't wipe...lol
Click to expand...
Click to collapse
All you had to do is setup fast boot and use fast boot command fastboot oem unlock to unlock your bootloader. A message always comes up letting you knlw that unlocking bootloader erases your data. You didn't necessarily had to adb not to mention you went and side loaded a custom recovery. Guess you beat the system. Lol
Jsparta26 said:
All you had to do is setup fast boot and use fast boot command fastboot oem unlock to unlock your bootloader. A message always comes up letting you knlw that unlocking bootloader erases your data. You didn't necessarily had to adb not to mention you went and side loaded a custom recovery. Guess you beat the system. Lol
Click to expand...
Click to collapse
I unlocked my bootloader but it didn't wipe my data. But i didn't unlock it correctly and rooted.
BugJuice said:
I unlocked my bootloader but it didn't wipe my data. But i didn't unlock it correctly and rooted.
Click to expand...
Click to collapse
The same thing happened to me. Apparently this happens if you flash the recovery right after unlocking the bootloader. Rather than unlocking, rebooting into android, then flashing the recovery.
Read this for more info.
chromium96 said:
The same thing happened to me. Apparently this happens if you flash the recovery right after unlocking the bootloader. Rather than unlocking, rebooting into android, then flashing the recovery.
Read this for more info.
Click to expand...
Click to collapse
ahhh gotcha! Thats my exact situation. I did not load into android either. Just flashed the recovery immediately afterwards. Is there any negative effects of this?
BugJuice said:
ahhh gotcha! Thats my exact situation. I did not load into android either. Just flashed the recovery immediately afterwards. Is there any negative effects of this?
Click to expand...
Click to collapse
Yep. I was pretty confused too.
So far I havent had any issues and everything seems fine. I flashed superuser on stock rom, flashed CM10.1, and flashed PA and everything has gone smoothly. Its only been about a week though, so im not sure if anything will happen. But i highly doubt that it will cause anything negative to occur.
First I have been to and searched every post and site I can find to turn this thing around, with no success. Sent several emails.
Took a rooted New Nexus 7 that had been restored back because it froze/did not respond. Got a new N7, unlocked bootloader and installed TWRP using Terminal (Mac) booted into recovery (TWRP) it said you are not rooted, install SU by swiping below. I swiped and tried to reboot and it stops at X. I have wiped, reinstalled TWRP and used a One Click Toolkit to Root. no success. Not really sure what I did wrong.....given I have always trusted TWRP.
Anyway... have unlocked bootloader, TWRP installed and cannot get Android File Transfer to recognize device. Welcome help or suggestions.
Thank you in advance.
David
Same thing happened to me. Don't listen to TWRP about SU. You'll need to do it manually for it to be successful. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2381582. This won't relock your bootloader. You just need to root it by flashing the SU zip found on one if the "How to root" threads.
natezire71 said:
Same thing happened to me. Don't listen to TWRP about SU. You'll need to do it manually for it to be successful. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2381582. This won't relock your bootloader. You just need to root it by flashing the SU zip found on one if the "How to root" threads.
Click to expand...
Click to collapse
Yeah, youre correct, you have to manually flash twrp. I would suggest running the utility to make youre device boot again, then make sure you have the LATEST twrp, then reboot and flash COMPATIBLE SU and you should be golden. Im not sure about macs though but you should deff be goin the right way.
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
dschaap said:
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
Click to expand...
Click to collapse
Give this a try: http://forum.xda-developers.com/showthread.php?t=2395003
I don't have a Mac, so I don't know if this will help. Only thing I could find.
dschaap said:
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
Click to expand...
Click to collapse
If you were able to install using a Mac, then you should have no troubles setting things up again. Avoid toolkits if you can, especially during the early days where things are buggy.
If you put your tablet into fastboot though, you can get started by going ahead and running fastboot -w and then flashing the stock recovery images back on. Sure, you won't have root, but I've found that 1) root doesn't take super nicely unless you're already signed into the tablet anyway, and 2) regardless of 1), once your bootloader is unlocked you might as well get set up and then root afterwards.
Mine did the same thing. What I did to fix was:
1. Go into recovery and format data in the wipe menu.
2. Then factory reset.
3. Restart os.
This was posted by decksy post #11 in tutorial for unlock, recovery, and root thread so if it works thank him.
Sent from my Nexus 7 using xda app-developers app
Just got the notice. Updating now!
About damn time.
Sent from my XT1058 using XDA Free mobile app
Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.
Yay, now do I unroot and try the OTA or do I wait for the full image.
ChrisAG said:
Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.
Click to expand...
Click to collapse
You can? How? I didn't save the link to the release notes, and can't find them now.
thedosbox said:
You can? How? I didn't save the link to the release notes, and can't find them now.
Click to expand...
Click to collapse
Removing provider name from the Status bar:
Settings > Wireless & Networks > More > Mobile Networks > Show Mobile Network (check on or off)
I completely forgot about the carrier being removed. Really cool.
Sent from my XT1058 using XDA Free mobile app
Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.
Steve-x said:
Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.
Click to expand...
Click to collapse
Ugh... I have TWRP on mine. Can I just unroot, or I need to remove TWRP? (read: flash stock 4.4.2...)
OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?
R3dbeaver said:
OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?
Click to expand...
Click to collapse
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.
R3dbeaver said:
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.
Click to expand...
Click to collapse
If your bootloader is unlocked then it is very simple. Just go to fastboot and flash the TWRP recovery, once flashed you can access it from fastboot. TWRP will load, then you can just select to restart the phone from it and it will ask if you want to root the phone, swipe to confirm and it will do it and restart the phone for you. Once the phone is booted you will need to finish the process - it should prompt you to update SuperSU, I selected the play store option, it downloaded and installed and was done. From there do yourself a favor and install AdAway
waiting for the firmware image..... anybody knows where to get it?
It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.
Steve-x said:
It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.
Click to expand...
Click to collapse
Would you please send the download link when you are convinient? I searched and find this http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25, but looks something wrong with the system.img.
Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Thanks, works a charm, went from rooted 4.4.2 to 4.4.4.
PS- I grew up in Langley.
I don't know if it's dumb luck or not, but I didn't even unroot and was able to accept OTA to 4.4.4.
This is what I did to prepare the phone:
- Uninstall Xposed Framework from within the Xposed installer itself. Left the installer app in place.
- Changed recovery from TWRP back to factory.
- Enabled all apps previously disabled.
At this point my phone was still rooted. I accepted the OTA and everything worked fine.
Afterwards, I re-installed Xposed from the installer app, and re-disabled the apps I don't use. But left the factory recovery in place since I don't have a need to go into TWRP for now.
Everything is working fine.
No Rogers Update?
I just picked up a Moto X (Brand New) It came with 4.2.2 Im with Rogers, It is a Rogers phone , its been 2 hours now still no software update notification. When I try to check manually in about phone, system update. Keeps telling me my device is up to date??
Any one experienced this before? Or am I being to impatient
Now, a dummy question: what is Rogers?
Rogers is the Canadian phone company that's selling the original Moto X
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