Hey Guys,
I used the galaxy nexus root kit to unlock my bootloader and to root my phone (I didn't install a custom rom, I just used what was default on the program after backing up my phone)
Here are my questions:
1) will I receive the official OTA upgrade / be able to install it?
2) If I am able to will that re-lock the bootloader on my phone?
I'm pretty hesitant to install any custom rom of Jellybean since I've had problems with them in the past almost leading up to a bricked phone, so I just wanted to make sure that the OTA will come to my phone, and that it'll work after I being installing it.
Thanks!
~Mike
If I remember right, if you don't have a custom recovery installed, you should still be able to get the OTA.
hmmm well I know that there is clockworksmod on here, but nothing else. I know thats a recovery program... I wonder if I should just flash the google asop direct from google for my verizon nexus :\
My understanding of the matter is that once you are rooted with a custom recovery, you should steer clear of OTA updates. They can definitely break root and have the potential to hard brick the device. This information is from my experiences with an Evo, so things may be different with the Nexus. I've only had mine for a month or so and haven't done enough reading yet to say for certain. If you really want the OTA there is a one-click method to return to stock over in the development section. Haven't been in that thread yet, so I don't know what kind of success/failure rate it's getting. Just read the last couple of pages and you should have a pretty fair idea of how it's going. If it seems doubtful, there are also several excellent guides for doing it manually. efrant has a link to one in his sig I think. Hope this helps!
Sent from my Galaxy Nexus using xda premium
The OTA won't auto-install if you have CWM recovery flashed. You can use CWM to flash the update manually, but it will never work automatically.
Greetings XDA,
Ive recently got me a GN (yakju) (couldn't wait for N4) and wait to get updated to 4.2. Now i run 4.2 and i want to unlock its boot loader & root it.
Not yet interested of having new roms on it, im cool with its stock android BUT i need to get full control of my device and not being restricted on apps that don't need root.
In case you want to ask me WHY i just didn't follow any of the guides for rooting nexuses in the forum, the answer is because im not sure which is the best/easiest/newest/safest
Im not very familiar with such staff i want to make is as simple as it gets and avoid breaking my phone (if thats even possible).
So please can you assist me to take this first android steps ?
Thanks in advance
safest and easiest.
http://forum.xda-developers.com/showthread.php?t=1529058
Hi, welcome to the GNex and the possibilities with it. I have had my GNex since Jan 2012 and it was rooted 2 weeks later. I'm sure if you search in XDA you find lots of help on rooting. However I started out with the www.galaxynexusforum.com forum and followed the unlocking and rooting by Wug.
Assuming you have a verizon GNex here is what you should follow
Wug's Nexus Root Toolkit v1.6.0 [Updated 11/26/12]
It is a nice tool installed on a windows pc or laptop and I have used it to do my GNex and also another one from a friend about 6 month after mine.
Works great and i think if you follow these thread you are rooted in no time.
Good luck
I have the GSM nexus.
Ok its unlocked now, preparing to root.
I just got 1 more final question, considering i will not flash any other rom or such, with my device ONLY unlocked & rooted, will i be able to get OTA updates from now on or i will have to flash myself ? (also do i need Custom Recovery ? what does it do ? )
equilibriumgr said:
Ok its unlocked now, preparing to root.
I just got 1 more final question, considering i will not flash any other rom or such, with my device ONLY unlocked & rooted, will i be able to get OTA updates from now on or i will have to flash myself ? (also do i need Custom Recovery ? what does it do ? )
Click to expand...
Click to collapse
You dont need a tool to unlock...you just need adb and fastboot.
Ensure ADB Debugging is enabled.
adb reboot bootloader
fastboot oem unlock
At this point you can push a custom recovery to your phone - I think there are recoveries now that support 4.2.
After flashing the custom recovery, boot into it and flash your superuser.zip
Lol...thats it.
I think you can still get OTA's but you will lose root. I suppose if the OTA was that important, you can relock the device (you will lose data) and then OTA up to the newest version and unlock again.
If you have a GSM device you are lucky, because the factory images are pretty plentiful. On Verizon CDMA we only have 4.1.1 (and because of this I only use 4.1.1 stock).
I had to relock and unroot on Tuesday because of a SIM card issue - didnt want Verizon knowing it was rooted. Came home and unlocked and rerooted all over again. Took about 10 minutes total.
After OTA 4.2.1 root is lost. Do i need to repeat the process to re-root ?
equilibriumgr said:
After OTA 4.2.1 root is lost. Do i need to repeat the process to re-root ?
Click to expand...
Click to collapse
rooting a nexus will always be the same steps.
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Fakusnamus said:
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Click to expand...
Click to collapse
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
But...
utsmaster18 said:
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
Click to expand...
Click to collapse
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Fakusnamus said:
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Click to expand...
Click to collapse
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
DroidIt! said:
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
Click to expand...
Click to collapse
Ugh...Yeah I was aware of that. If you read my question again, that was not what I was asking for. My queries were about the towelroot application in particular and if I could recieve OTA updates if I left the bootloader alone. I did not ask for alternatives.
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
nhizzat said:
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
Click to expand...
Click to collapse
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Just another thought and I get your question, but if you did unlock the boot loader and then just downloaded the factory image from here https://developers.google.com/android/nexus/images you WOULD be downloading it from Google so you should get the same speeds. Now I know you asked about towelroot and I've not used it, but if you're worried about download speeds the images in that link are directly from Google. I know what you mean though, I have very good download speeds and no matter what I download it does seem like the one's direct from Google are about 25% faster. They've got good networking that's for sure.
Fakusnamus said:
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Click to expand...
Click to collapse
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
nhizzat said:
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
Click to expand...
Click to collapse
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Fakusnamus said:
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Click to expand...
Click to collapse
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) and then back to custom after the OTA. takes 2min extra work before and after the OTA.
esmith13 said:
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) abd then back to custom after the OTA. takes 2min extra work before and after OTA.
Click to expand...
Click to collapse
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Fakusnamus said:
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Click to expand...
Click to collapse
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
The best way is to use towelroot now, and backup your data with titanium backup, then you can unlock your bootloader if you want for lollipop.
esmith13 said:
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
Click to expand...
Click to collapse
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
Question still stands... What Android version and what Kernel date?
Okay...
Okay, this is going on a massive tangent. My question was : If I root the nexus 7 with towelroot, can I still update to lollipop when the update rolls out? What can or can't I do with towelroot? (except not flash custom recovery or roms)
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
esmith13 said:
Question still stands... What Android version and what Kernel date?
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
Just unlock the bootloader now. It'll save you so much time and headache in the future.
I want to root my phone (obviously) and normally I wouldn't hesitate but now I am.
1) is it possible to encrypt my phone back after rooting?
2) do I lose OTA?
3) will things like android pay still work?
I used to know most of it, but it's been such a long time haha.
Yes ou can encrypt after root because when we first got root on 10 there was no data signal if it was not encrypted.
You don't loose ota but you do have a few things do to for ota to apply successfully. Just follow proper thread.
And I might be wrong but I don't think android pay works on any rooted phones.
Sent from my Nexus 5 using XDA-Developers mobile app
all the decryption problems are a thing of the past now when using the latest recovery. twrp-3.0.2-5-pme.img 20.4M and yes android pay will work when using the proper super user to root, Version 2.74-2 with forcedencrypt
as for OTA, its still possible but youll have to install the stock recovery by using the RUU for you phone, or if someone has pulled it. and then taking the OTA with a unmodified system. really though with the amount of support this phone gets, OTA kinda pointless cause a nice dev will probably put the update up and none of those steps are needed, just patient waiting
Hello. I'm pretty terrible at all this rooting stuff (or at least, I only do it once for each android phone I get, and then don't really look into it or stay up to date on all of it afterwards, I just use a few pluses that come along with being rooted).... Anyways, I really do need some help this time, as the confusion has really gotten to me, and I've lacked being able to find some simple answers (probably because they are just THAT simple) on google/reddit/on this forum.
Anyways, I've rooted my phone awhile back, lost it when my verizon pixel auto updated to 7.1.1 (idk how or why, pretty sure I had that disabled with root even, very frustrated) and even attempted to regain root by flashing SU with TWRP, but for some reason SU said I didn't have root still, and eventually just gave up in frustration. But now, my verizon pixel has been shutting off at ~40% battery power, and I read in the google forums that this was patched in the 7.1.2 update for pixels, and it was a software glitch rather than a malfunctioning/bad battery... So now I really want to upgrade to 7.1.2 from 7.1.1 not only to fix the battery/software issue, but also because I really want root.
I have an unlocked bootloader from when i first got my pixel and did this stuff, but now im unrooted on 7.1.1 because of that update awhile back, and want to update to 7.1.2 and root, but I've heard theres issues with rooting on the verizon because of bootloader, but that shoulden't be an issue since I unlocked it already (right? at least, I think? please let me know).
My only question (since i think i'll be able to follow this guide once I get the answer to this) is in the post he says: "Works with 7.1.2 (NJH47F, Aug 2017)".......... but since i have the verizon pixel (small version, not XL), should i be downloading this version: 7.1.2 (NHG47Q, Aug 2017, Verizon).... Or would it just be acceptable to allow my phone to auto download the update i have on it right now? Or must I download the NON verizon version as stated in the post and flash that one? Thanks for the help guys!
Thanks for any help!
-Synk
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
jhs39 said:
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
Click to expand...
Click to collapse
Thank you so much for the explanation. Truly, it's actually crazy how I was unable to find all of this neatly, nicely, and simply stated. Great to hear, I'm going to go on rooting, here's to hoping I don't blow it up.