Develop Bugs

will Verizon Galaxy Nexus OTA come to my phone?

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.

[Q] GNEX Verizon Root Question

Hey everyone. It has been a while since I have been around the rooting world... Since my D1 and DX days to be exact. So my question is this.. I have a GNEX Verizon That has the OTA to 4.1.1 JRO03O. I have downloaded Wugs Kit and the GNEX kit 7.8 . Neither one has an option to match my version of software. Sorry if this has been discussed before but can someone point me in the right direction. I would like to root and unlock the bootloader and then install CNA 3.6.6 . Thank you very much in advance for the help and direction.

the problem is the rootkit. dont use it. do it the right way, use fastboot or adb. its quicker/easier and youll learn how its done. or eventually youll be starting a thread titles "i bricked my gnex, help?". the basic steps via fastboot.. fastboot oem unlock, fastboot a custom recovery of choice, flash a custom rom or the su binaries in your new recovery, then reboot and profit. easy.

Here, have a look at this...
http://forum.xda-developers.com/showthread.php?p=23229558
ADB/Fastboot is the way to go.

[Q] Towelroot - Should I use it on Nexus 7 (2013)?

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.

Rooting & Rom'ing

Okay, I think I know the answer to this question, so forgive me. Just want to be sure before I go blow $500.
For the Nexus devices, regardless of the carrier, we'll be able to root them and ROM them as well as install new Kernel's because the bootloaders will be unlocked?
If that's correct please say so. If it's only partially correct, please explain it all to me.
Disgruntled Verizon User with a S6 Edge
THANK YOU IN ADVANCE!!!

Yes, its easy as pie.

nexuses are always devs favorites...

@mrbigdrawsz As a fellow Verizon user, I know exactly were your coming from. And yes since this is a nexus device coming directly from Google and not being sold or touched by Verizon, it will be good to go for all your rooting, ROM'ing, Bootloader unlocking, and custom kernel needs.

Yes! Though I am not sure about the Pixel C. I am wondering if Google giving products the Pixel name means they lock them down? Sorry, little off topic.

I'm only curious how/if Google has the fingerprint security locked down when it comes to root

shimp208 said:
@mrbigdrawsz As a fellow Verizon user, I know exactly were your coming from. And yes since this is a nexus device coming directly from Google and not being sold or touched by Verizon, it will be good to go for all your rooting, ROM'ing, Bootloader unlocking, and custom kernel needs.
Click to expand...
Click to collapse
Thank the sweet, tiny, infant squishy baby Jesus! I have yet to own a nexus phone (fed up with my GS5) and am about to pre order the 5X. I miss getting to try out different roms and such, so i'm really pumped about the 5X. the 6P is just too big of a phone for me i think.
Forgive me if this has been covered elsewhere, is there any word on xposed for android M?

owenrg said:
Forgive me if this has been covered elsewhere, is there any word on xposed for android M?
Click to expand...
Click to collapse
They are still working out the bugs on getting it to run on 5.x completely as they want and those devs on the Xposed team do a phenomenal job. Support for 6.0 marshmallow will eventually come but it will be a little bit yet.

If I unlock bootload, will I have problem with OTA?

shimp208 said:
They are still working out the bugs on getting it to run on 5.x completely as they want and those devs on the Xposed team do a phenomenal job. Support for 6.0 marshmallow will eventually come but it will be a little bit yet.
Click to expand...
Click to collapse
Awesome thanks!
Sent from my iPad using Tapatalk

menaceinc said:
If I unlock bootload, will I have problem with OTA?
Click to expand...
Click to collapse
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.

Thanks, I will just do that, unlocking bootloader. I really missed OTA as my current N5 is rooted.
shimp208 said:
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Click to expand...
Click to collapse

shimp208 said:
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Click to expand...
Click to collapse
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?

Tank87 said:
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Click to expand...
Click to collapse
In my experience, installing an OTA over a rooted phone would just kill root and you'd have to root it again, however, installing a custom ROM, the developer usually kills OTA so that all the custom stuff doesn't get jacked up.

Tank87 said:
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Click to expand...
Click to collapse
Rooting will effect the built in method of OTA updates. This is not a problem though. 99% of the time you will have access to the updated via the nexus factory image site before you receive notification of an OTA update on your device. Download the update and extract the boot, bootloader, radio, and system images. Flash via fastboot in bootloader mode and you will update your device without losing data/settings. I believe that you can flash img files with recent TWRP builds also.
To root after update just reboot to TWRP recovery and reboot. You will be prompted to install root before system reboots.
May seem a little overwhelming if its your first nexus device but a lot easier than updating a non nexus rooted Android device.
For more info check out any one of the recent nexus routing guides sticky threads

I know many people rooted etc their Nexus 5s using the Wugfresh Nexus Root ToolKit. Undoubtably a version will be introduced for the 5X,
If you root your device then flash a custom rom, you will be notified of the update via OTA or otherwise (eg Pushbullet) for that specific rom that you have flashed.

SlyUK said:
I know many people rooted etc their Nexus 5s using the Wugfresh Nexus Root ToolKit. Undoubtably a version will be introduced for the 5X,
If you root your device then flash a custom rom, you will be notified of the update via OTA or otherwise (eg Pushbullet) for that specific rom that you have flashed.
Click to expand...
Click to collapse
Why use a Toolkit to root? Just using ADB and Fastboot is better/easier since you can actually see what is happening during the process. Using a toolkit removes that element and if it hangs you don't where in the process it failed on.

metpage said:
Why use a Toolkit to root? Just using ADB and Fastboot is better/easier since you can actually see what is happening during the process. Using a toolkit removes that element and if it hangs you don't where in the process it failed on.
Click to expand...
Click to collapse
Yes thats true, but I haven't heard of many people who have had problems with Wugfresh and it is a popular method. Everyone is different

I always rooted my Nexus (N4, N5 & N7), but I am not going to root my new upcoming Nexus 5X. Why? It just too much to flash/root since Google will release monthly security updates. Yes, I did use "fastboot flash xxx xxx.img" method. However, I will unlock the bootloader in case I change my mind in the future. With unlocked bootloader, I can always fix phone via flash factory images.

Cant seem to fidn the proper root guide

Its been forever sicne ive done this so i feel a bit embarrased.. but i just got a fresh nexus 7 wifi only 2013 model from amazon and looking to root it unlock and whatever i need to do else. Its has 5.0 installed and asking to update to 5.1. Can someone point me to a guide to root and install the newest twrp and unlock the bootloader? Ive seen a few but nothing new so i dont know if they would soft brick my device. Thanks for your help! I appreciate it all.

First decide if you want OTA updates because they will end if you root it.
Next, consider the already-rooted alternative.
Then we can answer your questions...

No updates, i like to do it on my own

Will One Click Bootloader Unlock, Root, Recovery Install With Wugfresh Nexus Toolkit: @ http://forum.xda-developers.com/showthread.php?t=2381698 suffice for this 2013 nexus 7 with 5.0 installed work for all that?

Nevermind, that link is still down. So im still open to any ideas or leads lol.

unlock bootloader (#4, section "To flash a system image")
install TWRP and accept its rooting offer
install SuperSU app
Done.

Thank you. However im getting bootloop. flashed razor-lrx22g and twrp-3.00-0-flo.img when i reboot to fastboot and then to recovery it simply hangs at twrp, or if i just go for a restart it hangs at the boot screen with the multicolor balls. any suggestions?

No worries at all - it is easy to fix, but why did you flash razor-lrx22g? Didn't you want root/twrp only?
Anyway, now you have to flash the image yet again and let it boot completely to Android user interface. Then do the 3(-1) steps I posted earlier.