Database Users

Rooting and OTA updates

I am looking into rooting my Nexus S so I can install an ICS ROM. This is my first time rooting so got a question.
How will OTA updates work for me? Will the ICS update just work or will I have to in root to get the official OTA update?
Sry if this has been asked before couldn't find a clear answer.
Sent from my Nexus S using XDA App

Don't do OTAs. Any update released by Google or your manufacturer will be released here, rooted, within hours.
If you take an OTA you will lose root and could even find your phone locked again (as unlikely as that is with the NS, better safe than sorry. Ask the EVO users who took the GB OTA )
Sent from my Nexus S 4G using Tapatalk

Rooting requires flashing custom recovery
OTA requires stock recovery to work properly
So if your phone has custom recovery the OTA will not work.

Alright, thanks alot for the quick responses guys.
Sent from my Nexus S using XDA App

Once the ota is downloaded.....
* Put the zip on sdcard
* Reboot into custom recovery
* Manually flash it
* Directly after that, in the same recovery session, flash latest superuser zip
* Wipe cache
* Reboot

I run stock, so i'll add my two cents into this conversations. A few key points:
OTA's will NOT lock the boot loader
OTA's will work with CWM installed (The OTA will however remove CWM and needs to be manually applied)
OTA's will remove root access (the permissions on the binary get changed)
I have never seen an OTA on XDA that was pre-rooted. i have seen ROM packages that incorporate the OTA that are pre-rooted (installing these usually means a wipe of the device is needed)
if you replace the ROM on the phone, you will not get OTA updated. you must remain mostly stock to obtain them.
Custom kernels or custom google apps on stock roms will cause the OTA update to fail, however you will notified that the update is available.
I hope this answers your questions.

Good points.
What i do in order to maintain the full software (removing system apps, any system changes) is change the permissions of whatever i dont want to "000"
This will allow the verifying of OTA to flash.

snandlal said:
Good points.
What i do in order to maintain the full software (removing system apps, any system changes) is change the permissions of whatever i dont want to "000"
This will allow the verifying of OTA to flash.
Click to expand...
Click to collapse
This does not always work, such as installing the "Black" version of gmail over top the original, the world-wide version of navigation or using market enabler to change the prop.build file. any of these changes will cause the OTA signature to fail.
Though if you are simply removing a system app, then yes, that would work well.
Also to be noted and this just occurred to me, if the OTA is a full ROM version, then the signature won't matter and it will just install. For ICS, this is what i'm expecting.

I'm on the fence about rooting. I know there are advantages like custom ROMs and added features, but I'm somewhat of a newb at this. While the instructions (for the Mac) seem simple enough, I always feel like something inevitably goes wrong or there's some variable I've either overlooked or don't understand that screws things up.
I definitely don't want to brick my phone.
I don't even know what I'm asking in my post, but I guess... what are some advantages of rooting? And if I root, is it fully reversible?
I'm also confused by some of the terminology. What is clockwork recovery? Is that a sort of ROM? I keep seeing that phrase every time I read instructions. Likewise, what's a bootloader? What's fastboot? Also, what's a kernel?
And after I root (as you can see, I am really tempted to), what happens next? How do I choose which ROM works for me? Is it a matter of flashing them and trying each of them out?
I'm afraid of entering the world of root, but I want to. Advice? Does it matter what baseband, or kernel or build number I have?
I'm on Android 2.3.6

Matridom said:
I run stock, so i'll add my two cents into this conversations. A few key points:
OTA's will NOT lock the boot loader
I hope this answers your questions.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1145056
I know it's not likely, particularly with this phone, but it can happen. I maintain that if you're going to go through the process of unlocking your phone and putting a rooted ROM on it that you might as well wait for a modified OTA ROM to get posted by a trusted dev before just installing what the carrier hands out to you.
I guess maybe I should have said "re-lock"?

onthecouchagain said:
I'm on the fence about rooting. I know there are advantages like custom ROMs and added features, but I'm somewhat of a newb at this. While the instructions (for the Mac) seem simple enough, I always feel like something inevitably goes wrong or there's some variable I've either overlooked or don't understand that screws things up.
I definitely don't want to brick my phone.
I don't even know what I'm asking in my post, but I guess... what are some advantages of rooting? And if I root, is it fully reversible?
I'm also confused by some of the terminology. What is clockwork recovery? Is that a sort of ROM? I keep seeing that phrase every time I read instructions. Likewise, what's a bootloader? What's fastboot? Also, what's a kernel?
And after I root (as you can see, I am really tempted to), what happens next? How do I choose which ROM works for me? Is it a matter of flashing them and trying each of them out?
I'm afraid of entering the world of root, but I want to. Advice? Does it matter what baseband, or kernel or build number I have?
I'm on Android 2.3.6
Click to expand...
Click to collapse
OK, let's clear a few things up here.
CWM or ClockWorkMod is a custom recover that can be installed on the phones. This step is needed because the default recovery on the nexus does not allow for updates to be installed that are unsigned. CWM does, so it's a necessary step to installing the SU binary (aka root your phone) or installing custom ROMs
The bootloader is the basic system on your phone that reacts to the power on and hands over operations to Android. The equivalent in the PC world would be a BIOS.
fastboot is a utility that is provided by google that allows you to send commands to the bootloader and direct it's operations. It's needed to unlock the bootloader (so you can replace parts of it.. like recovery with CWM)
Interestingly enough, you can boot your phone to a custom recovery WITHOUT replacing your existing stock recovery by using fastboot.
Rooting your phone is simply installing and providing the proper rights to the SU binary to allow you to have full administrative rights to the phone, the superuser application is almost always bundled with it as it allows for a form of control as to what applications can use root access. Rooting your phone allows you to install some very interesting application, most popular are titanium backup (let's you back up app data and restore them after a reset) and removing advertising (adfree/adaway or it's like) Root can also be used by some applications that allow you to "cheat" at games.
rooting your phone is reversable, though not always the easiest to do. With the stock ROMS, it's fairly easy, you just re-apply the latest OTA and it will kill Root access on your device.
When it comes to custom ROMs the vast majority come pre-rooted to save you the hassel of doing it yourself.
On other phones where the bootloader remains locked, you have to use an exploit to gain root access, this then allows you to modify the OS and install custom roms and CWM while keeping the bootloader locked. Since the Nexus line can be unlocked, it's not needed.
Please note, root access is NOT required to install a custom ROM.
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
MaxCarnage said:
http://forum.xda-developers.com/showthread.php?t=1145056
I know it's not likely, particularly with this phone, but it can happen. I maintain that if you're going to go through the process of unlocking your phone and putting a rooted ROM on it that you might as well wait for a modified OTA ROM to get posted by a trusted dev before just installing what the carrier hands out to you.
I guess maybe I should have said "re-lock"?
Click to expand...
Click to collapse
That's a link to a non-nexus phone. The question here is in regards to the nexus device and i believe my statement stands 100% true. Since it's a self proclaimed "newby" asking questions, i don't want to confuse the post with un-needed and non-relevant information.

Matridom, wow thanks. That clarifies a few things.
So, you say root access isn't required to flash custom ROMs? Let's say for example, I want to flash an ICS ROM, or even a ROM that allows me to have Backlight Notifications?
I don't need root? If I don't need root, how do I flash those ROMs?

Matridom said:
That's a link to a non-nexus phone. The question here is in regards to the nexus device and i believe my statement stands 100% true. Since it's a self proclaimed "newby" asking questions, i don't want to confuse the post with un-needed and non-relevant information.
Click to expand...
Click to collapse
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least one OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.

MaxCarnage said:
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least one OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
Click to expand...
Click to collapse
The key here is that SPRINT released an OTA for a SPRINT branded device. This has zero relevance to updates provided by Google for Nexus devices.

MaxCarnage said:
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
Click to expand...
Click to collapse
The issue at heart here is that fact that the OTA for the nexus line of phones comes straight from google and are not "tweaked" in any way by the carriers. (exception nexus 4g has additional applications required for CDMA support)
One of the selling features of the nexus phones is the fact that unlocking the bootloader is officially supported.
In regards to other phones getting their bootloader locked, I've experienced first hand the pains of that, having a galaxy S and the 2.3 installing a new bootloader and really screwing things up for me. In those cases, i agree with you whole heartily and to wait for pre-cracked roms that can be installed.
My question to you would be to please show an example of a nexus S getting it's booloader locked due to an OTA update as that is the phone we are discussing.
---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------
onthecouchagain said:
Matridom, wow thanks. That clarifies a few things.
So, you say root access isn't required to flash custom ROMs? Let's say for example, I want to flash an ICS ROM, or even a ROM that allows me to have Backlight Notifications?
I don't need root? If I don't need root, how do I flash those ROMs?
Click to expand...
Click to collapse
All you would need to do is to unlock the bootloader, install CWM, then apply the .zip associated with the ROM you wish to install. I would however carefully read the installation instructions for the rom as in some cases, it might be a multi-step process (such as going from a 2.2 rom to a 2.3).
Many ROMS also do not come with the google apps and secondary zip file needs to be applied to get those running (cyanogenMod does this)
I wanted to add, that the process of unlocking your bootloader will erase EVERYTHING on the phone, including the SDcard partition. So make sure you back up anything of importance.

Matridom said:
My question to you would be to please show an example of a nexus S getting it's booloader locked due to an OTA update as that is the phone we are discussing.
Click to expand...
Click to collapse
I can't provide an example because, as I have already stated, this was a precautionary suggestion only.
I'm not going to get into a debate with you over this; I've made my point and you've made yours. Thanks.

Matridom said:
This does not always work, such as installing the "Black" version of gmail over top the original, the world-wide version of navigation or using market enabler to change the prop.build file. any of these changes will cause the OTA signature to fail.
Though if you are simply removing a system app, then yes, that would work well.
Also to be noted and this just occurred to me, if the OTA is a full ROM version, then the signature won't matter and it will just install. For ICS, this is what i'm expecting.
Click to expand...
Click to collapse
Good point again but the trick is to put your apps in /system/framework
Along with framework-res.apk.
This will add a dex file to /data/dalvik-cache, which is needed for saving upon reboot

Does flashing another radio that's different from your original radio impact the ability to apply an OTA?

suksit said:
Rooting requires flashing custom recovery
OTA requires stock recovery to work properly
So if your phone has custom recovery the OTA will not work.
Click to expand...
Click to collapse
Rooting doesn't require flashing custom recovery.

iboj007 said:
Does flashing another radio that's different from your original radio impact the ability to apply an OTA?
Click to expand...
Click to collapse
No. It doesnt

Titanium Backup, Recovery apps, and the noob

Noob for tablets. Got the nexus 10 for the family for christmas. Want to get it all setup before I turn it over to the wolves.
I love using TBpro on my Droid Bionic. I thought it would be good to have a solid backup program on the tablet, and since I have it on my smartphone I thought I would hang with what I've sorta know already.
Dont really understand what unlocked/locked means for a bootloader, and why the N10 needs that why many smartphone can be rooted without being unlocked.
I would love to hear some views on the purposes of apps like ClockWorkMod and TWRP and what they do and provide. Seems like they do perform backups and more. Why TBpro is likely just a backup app. What functions do these recovery apps have the make them "must have".
thanks for the time answering the tablet noob

TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227

bg1906 said:
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
Click to expand...
Click to collapse
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?

jetguat said:
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
Click to expand...
Click to collapse
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467

bg1906 said:
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
Click to expand...
Click to collapse
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)

The wugfresh version automates what the zedomax version does by hand. I did mine via the zedomax way.
Sent from my Nexus 10 using xda app-developers app

jetguat said:
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
Click to expand...
Click to collapse
I would suggest using the Wugfresh method, definitely the simplest to use. And a great recovery is TWRP, it is very clear and easy to understand what it is that each menu contains.
Also with the OTA updates, it really depends on the size and type of update. If it is a fairly major one, like JB 4.1 to JB 4.2 then you will have to use the option in Wugfresh toolkit to 'unroot', then update. After the update you can simply reuse the toolkit to root again. Sometimes if the OTA is small it will simply install over the rooted device, but I wouldn't count on it. It definitely shouldn't discourage you from rooting though, its relatively simple to fix

Easy 2 click root: How I got to 4.2.2 Camera Update/Rooted and WP permanently Off

Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.

It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk

Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.

So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app

No nothing roots 4.4 at this point.

vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.

akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.

mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???

-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck

mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.

-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it

mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh:

Rooting?

I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.

What version are you running? B20/B27/B29

If you are not tech savvy, do not attempt the root method. It's for advance user and too many people have bricked their phone already. Just read the threads and you will know what I mean.

S8ntsHaz3 said:
What version are you running? B20/B27/B29
Click to expand...
Click to collapse
I'm running B29.
And yes I can probably guess the amount of people who bricked their phones. But what if everything were to be laid out simple and I follow the directions in every respect? I'm not going to start rooting until I know what I'm doing. So don't worry. I'm stupid but I'm not THAT stupid.

No your fine lmao I started with this phone so we're pretty much same level. As to my understanding it is possible but I would wait just a bit for the b29 stuff to come out.

Don't worry, you're not the only one. I've been reading these tutorials and it's all gibberish, lol.... Every phone I have has been rooted within the first day, this phone I've had over 2 months, and I still can't get it. So you're not alone, lol...

There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice

Bolandk said:
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Click to expand...
Click to collapse
I'm looking closely at this phone now myself...
I've seen the bootloader thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
I'm only interest in this if I can successfully unlock the bootloader and stock root is possible...from what I've read, BOTH can be done. According to the root thread, the model I need (A2017G) is listed as unlockable, correct? What's the difference between a2017g B02 and B03??
RoOSTA

totalFX said:
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
Click to expand...
Click to collapse
OK I have read far too many of these questions here about root on B29 - so here goes.
1. Go to the ZTE website, download the stock B20, and install it.
2. http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 use this to get TWRP installed on your phone - don't worry about root.
3. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 UNLOCK the bootloader
4. http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2 flash boot file, system file, and SuperSU 2.65
Now please relax - anyone here with any dev skills whatsoever are neck deep in other projects (like CM13). B29 hasn't been out long and the only stock image we have from ZTE is B20, which doesn't give us a ton to work with

I also very new to android smartphone and I also feel so so out of place too.
I wish someone make a video how to root this axon 7 phone.
search around youtube jailbrake iPhone is so easy root samsung phone is so easy.... but root axon 7 nothing
I love axon 7 so much now but if I know it's so hard to root i'm just gonna buy samsung phone .
so F..... tired of this youtube ads
ads block is the only reason why I want to root
and that is the only reason why I jailbrake all my ideviese

For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?

tasar said:
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
Click to expand...
Click to collapse
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.

So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Sent from my ZTE A2017U using Tapatalk

polar2792 said:
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Click to expand...
Click to collapse
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.

rczrider said:
[*] *Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
Click to expand...
Click to collapse
Thanks, reboot disemmcwp fixed my write access to /system

rczrider said:
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
Click to expand...
Click to collapse
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk

polar2792 said:
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I think ZTE will eventually put out a bootloader unlock without killing the warranty. But, yeah, either way it's easy enough to do it on your own now.

rczrider said:
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
Click to expand...
Click to collapse
Thank you; thank you, THANK YOU!!!!! I tried for an hour or two, using both ADB and Terminal Emulator to apply this "reboot disemmcwp" fix, and I just couldn't get it to work (I'm on B29). Then, I saw your instructions to use TWRP and followed them, and it worked first time, like a charm!
Thanks again - I'm a very happy camper. You da' man, LOL!
Dennis

Shortcut to being rooted on N910VVRU2CQI2

Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE

I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks

My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839

RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.

Thanks doc. Is that a folder that gets overwritten when you flash a new room?

This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?

lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works

RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.

does this require the developer version? btw how do i backup

I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.

RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.

kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.

Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.

In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.

Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.

Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.

Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?

lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.

kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.

Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.