Database Develop

OTA 139.15.1 keep root

All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?

First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X

Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...

You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X

The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X

mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.

dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X

mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk

juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.

MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191

will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.

MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!

boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.

will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.

jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.

will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.

jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being

[How-To] Root G870AUCU1ANG3 (GS5 Active)

**Make certain that your reactivation lock in security settings is off before beginning this process**
1. Take the NG3 OTA update.
2. Download and install Towelroot-v3.apk(this version does not require internet access).
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key) and flash the G870A_NE4_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+).
4. Open the Towelroot app from your app drawer and press "Make it Rain" to root your device.
5. Power off then boot into "Download Mode" again and flash the G870A_NG3_Stock_Kernel also in Odin's PDA slot(AP in Odin v3.09+).
6. Download SuperSu to manage root access. Done!
Troubleshooting:
1. If the NG3 OTA update fails consider flashing the G870AUCU1ANE4_Full_Odin.tar to return to stock then take the NG3 OTA update, (or place the G870A_NE4toNG3_OTA.zip onto your ext-sdcard and sideload from stock recovery). Once updated to NG3 continue to Step 2 above.
2. The most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure.
Notes:
1. After flashing the NE4 kernel your phone may run a little wonky and towelroot may not root on the first try. If that happens reboot and try towelroot once again. Once rooted and after flashing the NG3 kernel your phone will once again run like a champ!
2. The above process will not affect your User Data or Knox Warranty Flag.
Credits:
@lordmorphous - Tester

Gonna try this... Thanks! :beer:
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

Yes this worked. Thank you very much.......

Are we going to trip Knox using the method above ???
Just wanna be sure about this. ...g

gregsarg said:
Are we going to trip Knox using the method above ???
Just wanna be sure about this. ...g
Click to expand...
Click to collapse
Nope.

Does anyone have a list of the benefits of updating to NG3?
I just rooted my new phone on NE4 and I want to know whether it's worth taking the time.

Thanks for the How-to! Worked great for me!

Any benefits on ng3 over stock?

Root possible for 'straight out-of-the-box' G870AUCU1ANG3???
I've looked and looked around the forums here and have come to the conclusion that the AT&T S 5 I recently picked up is, sadly, unable to be rooted. Does anyone here know if this is true? As the title suggests, my phone seems to have come loaded with G870AUCU1ANG3. Is it possible that it came with the previous iteration (NE4, I think??) and I didn't avoid an update, thus meaning I can flash the earlier version? Can I even tell whether it's possible to 'revert' to NE4 (or whatever it would be)? Is any of this even possible without having been previously rooted, or am I wasting my time searching this out? Naive but earnest questions... sorry if I'm in the wrong place here. I promise, I poked around the site for a few days in search of clarity before posting.

papayajelly said:
I've looked and looked around the forums here and have come to the conclusion that the AT&T S 5 I recently picked up is, sadly, unable to be rooted. Does anyone here know if this is true? As the title suggests, my phone seems to have come loaded with G870AUCU1ANG3. Is it possible that it came with the previous iteration (NE4, I think??) and I didn't avoid an update, thus meaning I can flash the earlier version? Can I even tell whether it's possible to 'revert' to NE4 (or whatever it would be)? Is any of this even possible without having been previously rooted, or am I wasting my time searching this out? Naive but earnest questions... sorry if I'm in the wrong place here. I promise, I poked around the site for a few days in search of clarity before posting.
Click to expand...
Click to collapse
There shouldn't be any reason why you can't follow the instructions in the 1st post of this thread starting with step 2.

I've been searching for a while and can't find anything about using this root method and then being able to install safestrap. Has anyone been successful in doing this? Do I need to downgrade before and does anybody have the downgrade file? FYI Just bought my phone last night and was successful in rooting.

rescuedad said:
I've been searching for a while and can't find anything about using this root method and then being able to install safestrap. Has anyone been successful in doing this? Do I need to downgrade before and does anybody have the downgrade file? FYI Just bought my phone last night and was successful in rooting.
Click to expand...
Click to collapse
Never mind, I figured it out. If you have the active you need to downgrade the kernel to NE4 like you do if you need root. Then you install Safestrap 3.75. I'm doing a Nandroid backup as I type. I'm going to re-flash the NG3 stock kernel when I'm done and hopefully that will be fine.
If it bricks, I can always take it back since I blocked the knox counter... BTW I'm on At&T

I downgraded to the NE4 to root. Along with others here I have to ask, what are, if any, benefits to upgrading the kernel?

panthersdzynes said:
I downgraded to the NE4 to root. Along with others here I have to ask, what are, if any, benefits to upgrading the kernel?
Click to expand...
Click to collapse
Not sure I understand the question but I will take a shot......typically the kernel, modules, and non-hlos.bin have to match or else you may experience issues such as no wifi, lag, etc. The NE4 and NG3 kernel and modules may be similar enough that you will not experience issues immediately but they may develop later unless you reflash the NG3 kernel to match your modules and non-hlos.

muniz_ri said:
Not sure I understand the question but I will take a shot......typically the kernel, modules, and non-hlos.bin have to match or else you may experience issues such as no wifi, lag, etc. The NE4 and NG3 kernel and modules may be similar enough that you will not experience issues immediately but they may develop later unless you reflash the NG3 kernel to match your modules and non-hlos.
Click to expand...
Click to collapse
I see. Thank you, that answers my question.

THanks XDA
Been away along time. Had iphones for the last 6 years. Use to go here all the time in the Kaiser days (Att Tilt) if any of you remember. I see XDA has still been kicking ass while I've been gone! Glad to be back and Thank You everyone especially first poster for the guide to root my Att GS5 Active.
THANK YOU

Working perfectly. ..thank you. ..g

There was a small update released today. Can someone that is rooted grab it from their fota/cache folder and send to me so that I can update this guide? Thanks.

WORKED! AWESOME!
Now... I have installed SuperSU. Was that left out of the first post?
Also, if I do not flash the NG3 Stock Kernel back afterwards, will I experience funkiness?
Thanks again!

Stock recovery and upgrading Lollipop with future OTAs after rooting

Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!

LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.

Thank you sir!

obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.

I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6

crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?

I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!

LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.

crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.

obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.

crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1

obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?

crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.

obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?

LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.

obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.

crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.

I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.

Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.

[How-To] Update to I537_OC7 - 5.0.1 and KeepRoot

**You can begin the following process from 4.4.x Build/ROM or higher but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
**Caution!** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Download:
- I537_OC7_Stock_Rooted_ROM
- I537_OC7_Stock_Rooted_Deodexed_ROM
Pevious Builds:
- I537_OC6_Stock_Rooted_ROM
- I537_OC6_Stock_DeOdexed_ROM
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" setting to "Download."
6. Press the lightning bolt then "Ok" to begin the flash.
7. Once the flash is complete and the device reboots into "Download" mode, flash the I537_OC7_Bootloader using Odin's PDA/AP slot.
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the AT&T splash screen for 1 - 2 minutes (15 - 20mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Optional - Enable Native Tethering:
- I537_OC7_TetherAddOn
- I537_OC6_TetherAddOn (Flash using FF's "Flash zip or ota" option.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits:
@thisisapoorusernamechoice - for capturing the ota update and for his system dump.
@Chainfire

muniz_ri said:
**You can begin the following process from any Build/ROM but you must already have Root Access**
**Attention** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Instructions:
Click to expand...
Click to collapse
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix

thisisapoorusernamechoice said:
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix
Click to expand...
Click to collapse
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon

Joe-Tech said:
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon
Click to expand...
Click to collapse
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option

thisisapoorusernamechoice said:
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option
Click to expand...
Click to collapse
Only way im thinking to boot the new LP ROM, is to use @muniz_ri method so we can upgrade and keep root. So now we going to be on the OC6 kernel and baseband, since the gpe can boot without flashing the kernel. Then we can flash the GPE 5.x ROM, either with safestrap or FlashFire, and we can also use Odin to flash the stock kernel/partitions. But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.

Joe-Tech said:
But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.
Click to expand...
Click to collapse
Were other rooted apps able to get root permission?

thisisapoorusernamechoice said:
Were other rooted apps able to get root permission?
Click to expand...
Click to collapse
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.

delete
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app

Joe-Tech said:
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.
Click to expand...
Click to collapse
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question

thisisapoorusernamechoice said:
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question
Click to expand...
Click to collapse
I don't think it will make any difference.

@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.

Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?

mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
Extract the tar from the rar. Leave the zip as is. Copy the tar and the zip to your phone's internal memory or external SD card, somewhere it'll be easy for you to find

Devo7v said:
@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.
Click to expand...
Click to collapse
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.

mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
If all of the above is beyond your level of understanding I strongly suggest you reconsider attempting to modify your phone.

muniz_ri said:
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.
Click to expand...
Click to collapse
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.

Devo7v said:
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.
Click to expand...
Click to collapse
Did not bother to try since it has not worked on any 5.0 release so far.

muniz_ri said:
Did not bother to try since it has not worked on any 5.0 release so far.
Click to expand...
Click to collapse
Any chance I can implore you to try it since there will inevitably be a bunch of people already on the OC6 firmware asking how to root it and will get pissed when they find they have to wipe their phone? Or maybe you could just provide the stock OC6 kernel and I can convince @thisisapoorusernamechoice to give it a shot?

For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.

bobbylx said:
For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.
Click to expand...
Click to collapse
A couple questions:
What firmware were you coming from?
How long did you wait?
Did you have Xposed enabled?

[q] [may 29]sgs5 at&t is rooting possible? Answer i am about to explode.

It is about time I get some straight-forward answers. I'm tired of Googling everything I can and it not being what I think it is.
It is about time I get some straight-forward answers. I'm tired of Googling everything I can and it not being what I think it is.
What I have come to you for, XDA, is some light in the cave.
WILL THERE BE A WAY TO ROOT THE AT&T SAMSUNG GALAXY S5 VARIANT?!
Towelroot doesn't work. And if quite frankly tired ****less of all the posts that still exist talking about it.
Is there anything in development? All I can see now is SafeStrap and Multi-Tool but if you aren't rooted these do nothing. I just want some information for God's sake. Will ANYONE tell me what is being done about the development of the device's rooting? Is anyone even trying anymore? And if so, tell me! More importantly, if there are people, why aren't they being talked about? With as many S5's as there are out there (at least to me since I know about 10 people who use them regularly) why wouldn't anyone be trying?
PLEASE people get it together!
I have come from only 3 devices, but I was able to root and mod all of them. Rooting and Modding is love and life to me and is pretty much all I sincerely love about Android. The fact that I can't afford a new phone at this stage is sad, and I have grown tired of the bloating of TouchWiz, especially with the Lollipop update. I know that a rooted S5 would be extremely awesome, but since there is nothing about it being worked on I suppose I'll just have to live with the rubbish they call TouchWiz.
And if by some chance someone who can develop something like this reads this thread, please, respond, PM me, do SOMETHING. TELL THE XDA WORLD, because I GUARANTEE there are more of me out there who have longed for this but have just lived with it. BE A GAME CHANGER A DO SOMETHING ABOUT IT.
Don't give me the, "Knox and bootloaders are hard to pass by, especially with the new more secure versions." Because guess what, geohot did it once. Not like it lasted, but the fact is is that it worked at one point. It may be harder now, but it's still possible. PLEASE DO SOMETHING. PLEASE TRY.
Anyway, best of luck to all of the users. And anyone who has read this please leave a comment and tell me what you know. Many days I'm left alone, commentless with my threads. This is one I truly need to be acknowledged.
THANK YOU FOR YOUR TIME

Well that's a big thread revealing nothing about your device other than its an s5. There are ways to root with towel root unless you have the 5.0 ota.

dirtydodge said:
Well that's a big thread revealing nothing about your device other than its an s5. There are ways to root with towel root unless you have the 5.0 ota.
Click to expand...
Click to collapse
Well it's pretty obvious that it's AT&T. 5.0 L and Towelroot has never worked before.

ElectricBiskitz said:
Well it's pretty obvious that it's AT&T. 5.0 L and Towelroot has never worked before.
Click to expand...
Click to collapse
Towel root has worked and still does on nce. If you were on OA1 towel root wouldn't work unless you downgraded to use it then go back to OA1. And no it don't work on 5.0. There are multiple kernels and builds that att has put out that it didn't work on without downgrading. But just for future reference is always helpful if you include your build, version, etc. Like i said there are multiple builds that it didn't work on unless you downgraded is only the 5.0 that you can't downgrade.

dirtydodge said:
Towel root has worked and still does on nce. If you were on OA1 towel root wouldn't work unless you downgraded to use it then go back to OA1. And no it don't work on 5.0. There are multiple kernels and builds that att has put out that it didn't work on without downgrading. But just for future reference is always helpful if you include your build, version, etc. Like i said there are multiple builds that it didn't work on unless you downgraded is only the 5.0 that you can't downgrade.
Click to expand...
Click to collapse
I said that I have Lollipop so everything you're saying won't help. Plus I know you wouldn't have known anyway but I have tried all of this way before Lollipop. I tried downgrading from OA1 at the time to NCE and I ended up in a bootloop. The kernel was faulty. I had to reset my phone in a very long, aggravating process to get it back. I NEVER want to go down that road again. And like I said in the entire post, I'm just looking for a pioneer to try again and make a geohot move on Lollipop. And no offense to you, you wouldn't have known this about me anyway, but your kind of information was exactly what I was trying to steer away from. And here it comes, right back at me. I'm just tired and sick of all the people who just do, essentially, a copy/paste of common information. When in my circumstance, am looking for something difference. Again, no harm to you, but anyone and everyone that has ever responded to my threads because it's all the same.

As someone who used to reverse engineer software, updates to said software usually patch those exploits. It's not usually easy to regain a new exploit and can take massive amounts of time. I can't speak for other devs but (at the time I did this stuff and still currently) I have a demanding full time job and a family, which come first over a hobby. I can guarantee I will never buy another Samsung phone again because of this. I know it's not always feasible, but maybe look into getting an HTC phone with developer options that is unlocked from the factory. Venting on here will get your cause nowhere.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

Forum is trying to help you!
ElectricBiskitz said:
Well it's pretty obvious that it's AT&T. 5.0 L and Towelroot has never worked before.
Click to expand...
Click to collapse
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.

Besides the fact there are already a metric ass ton of threads in this phone's forum discussing rooting the 900A.
I've been reading them for weeks now after I was overzealous and took the OTA to OC4 figuring there was a root solution already..... There wasn't, and oh well... My fault for not researching first, but it's making me keep my Note 2 until something comes up.
Hell something may already be out, but with rants like yours..... Feel free to enjoy the great advice in the links in my signature.

wwit said:
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
So wait... You have a method to get him from ota 5.0 to a muniz method 5.0? I was under the impression that was not possible once you took the ota ( i didn't, but I'm still curious)

ota 5.0 root?
wwit said:
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
Ok, so I'm sorry if i've got this wrong, but as the user above stated, I too have been scouring the web and FDA searching for a way to root an at&t galaxy s5 with an OTA u5.0 lollipop update. From all the research i have done, I have found no resolution to the locked bootloader. Are you saying that you can root the stock, unrooted, locked bootloader, sm-g900a running lollipop 5.0? If so, I will gladly donate to your Paypal for detailed instructions on how to do this! I am no noob at rooting, having rooted every galaxy since the skyrocket,. But this lollipop crap is driving me crazy. Any help is greatly appreciate!!

wwit said:
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
I need this please! I have an at&t Samsung S5 lollipop 5.0 please guide me

I have not seen any solutions for people who took Ota update. Did you make the exploit yourself? If not can you point out the source?
Thanks!

lowspeed said:
I have not seen any solutions for people who took Ota update. Did you make the exploit yourself? If not can you point out the source?
Thanks!
Click to expand...
Click to collapse
My phone just automatically downloaded the 5.0 update a few weeks ago. I attached a screenshot of my phones specs

I replied to the person who said he has instructions. ..

wwit said:
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
if you're able to root OC4 on a G900A, i'm all ears.
so far i'm unable to install TWRP (fail auth) using odin and it seems it only works for 900F or other models, not 900A specifically that has never been previously rooted. all posts on the topic suggests you cannot downgrade from OC4 and any attempt is futile at the moment.

Rooted 5.0
tmac200913 said:
My phone just automatically downloaded the 5.0 update a few weeks ago. I attached a screenshot of my phones specs
Click to expand...
Click to collapse
Hi, I'm trying to make time to create the document to show how I did it. I intend to recreate the process again on my handset and include screenshots as I go through.
Basically the only way I could get my handset to 5.0 root was to take the handset back to NCE stock firmware (by the way I have all the files on my laptop to do this) using ODIN v3.09. This took my back to G900AUCU1ANCE (4.4.2) April 2014 release. I installed Towelroot, busybox and Safestrap. Did a backup of the device (when I went back to 4.4.2 I then configured my device to look and feel how I wanted it to be because I wanted to restore the data partition once on Lollipop - but this is a required part of the upgrade). You need to use Safestrap to create a backup folder structure on the SD card so you can dump the 5.0 (OC4) rooted backup on to restore later in the upgrade process. I then installed G900AUCU2ANG3 (4.4.2) September 2014 release using Safestrap. I then installed the G900AUCU2AOA1 (4.4.4) February 2015 release and then used Safestrap to take another backup. Then I did an advanced wipe in Safestrap (excluding the SD card) and restored the OC4 rooted backup (I found online I also have this file). Once that restored I then within Safestrap selected the reboot > download mode (don't restart the handset into Lollipop before doing this process - the whole process will fail). Once the handset rebooted into Download mode I connected the handset to ODIN v.3.10.6 and installed the G900A_OC4_Stock_Partitions_wOA1_BL.tar.md5 (using the AP option in ODIN). Once that completed the handset rebooted and after 5-10 mins started to upgrade files. Once that finished the handset was on 5.0 - the same as the screenshot you've posted and it's rooted. I have SuperSU installed working fine and I used Root Checker Basic to confirm the device is rooted. More so I then went on to sideload the G900A_OC4_TetherAddOn so I could get native wifi tethering because AT&T still had this locked down in the root 5.0 I installed above.

anyone verify this?

Not sure they started out on 5.0...I don't know of anyone who has successfully downgraded once on OC4.

wwit said:
Hi, I'm trying to make time to create the document to show how I did it. I intend to recreate the process again on my handset and include screenshots as I go through.
Basically the only way I could get my handset to 5.0 root was to take the handset back to NCE stock firmware (by the way I have all the files on my laptop to do this) using ODIN v3.09. This took my back to G900AUCU1ANCE (4.4.2) April 2014 release. I installed Towelroot, busybox and Safestrap. Did a backup of the device (when I went back to 4.4.2 I then configured my device to look and feel how I wanted it to be because I wanted to restore the data partition once on Lollipop - but this is a required part of the upgrade). You need to use Safestrap to create a backup folder structure on the SD card so you can dump the 5.0 (OC4) rooted backup on to restore later in the upgrade process. I then installed G900AUCU2ANG3 (4.4.2) September 2014 release using Safestrap. I then installed the G900AUCU2AOA1 (4.4.4) February 2015 release and then used Safestrap to take another backup. Then I did an advanced wipe in Safestrap (excluding the SD card) and restored the OC4 rooted backup (I found online I also have this file). Once that restored I then within Safestrap selected the reboot > download mode (don't restart the handset into Lollipop before doing this process - the whole process will fail). Once the handset rebooted into Download mode I connected the handset to ODIN v.3.10.6 and installed the G900A_OC4_Stock_Partitions_wOA1_BL.tar.md5 (using the AP option in ODIN). Once that completed the handset rebooted and after 5-10 mins started to upgrade files. Once that finished the handset was on 5.0 - the same as the screenshot you've posted and it's rooted. I have SuperSU installed working fine and I used Root Checker Basic to confirm the device is rooted. More so I then went on to sideload the G900A_OC4_TetherAddOn so I could get native wifi tethering because AT&T still had this locked down in the root 5.0 I installed above.
Click to expand...
Click to collapse
This is funny.......there seems to be a huge disconnect between this and the actual issue in the OP which is someone that took the 5.0 OTA and wants root access. There currently is no way for him to gain root access. Instead you quoted, almost verbatim, my origina KeepRoot method and files: http://forum.xda-developers.com/showpost.php?p=59996087&postcount=4

muniz_ri said:
This is funny.......there seems to be a huge disconnect between this and the actual issue in the OP which is someone that took the 5.0 OTA and wants root access. There currently is no way for him to gain root access. Instead you quoted, almost verbatim, my origina KeepRoot method and files: http://forum.xda-developers.com/showpost.php?p=59996087&postcount=4
Click to expand...
Click to collapse
Morning, first of all if you take a look at my first post you will see I have clearly stated your name and I have not tried to take credit for your process. Secondly I have only been replying to questions from members who have read my results and have then from my post asked how I did it. I have then simply explained again in the post you have replied to how I got to a rooted version of Lollipop.
Are ypu saying that if a handset takes the ota it is not possible to go back to NCE and then forward right through to rooted Lollipop or are just annoyed thinking I am trying to take credit for your work. I'm happy to guide a member step by step through a process if they want me to but I have already said it's not my discovery.