Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.
I have rooted Kit Kat using the original method, and today while on wifi I saw the dreaded Software Update Downloading in my tasks. I quickly disabled my wifi and have had it off all day and it has kept the software update from downloading, since I'm paranoid to lose root. I have two Galaxy S4 Actives, both running the same exact Kit Kat exploit and they both had the same software update come up today. I've tried to disable the OTA but FOTA.apk isn't on the phone when I used a root file explorer to look in the System/App folder.
I can't seem to find anything on this update, it just came up on 7/2/14 around 1:00pm EST.
Is there a way to block OTA's on Kit Kat? I imagine it's different as no method I've found has worked.
I did find an APK to kill KNOX, which was popping up at least a dozen times a day to tell me about the "new security policies".
The phones work great as they are, I love having Kit Kat & Root, and don't want to lose it. Anyone have any ideas or anyone know anything about this update?
SebringTech said:
I have rooted Kit Kat using the original method, and today while on wifi I saw the dreaded Software Update Downloading in my tasks. I quickly disabled my wifi and have had it off all day and it has kept the software update from downloading, since I'm paranoid to lose root. I have two Galaxy S4 Actives, both running the same exact Kit Kat exploit and they both had the same software update come up today. I've tried to disable the OTA but FOTA.apk isn't on the phone when I used a root file explorer to look in the System/App folder.
I can't seem to find anything on this update, it just came up on 7/2/14 around 1:00pm EST.
Is there a way to block OTA's on Kit Kat? I imagine it's different as no method I've found has worked.
I did find an APK to kill KNOX, which was popping up at least a dozen times a day to tell me about the "new security policies".
The phones work great as they are, I love having Kit Kat & Root, and don't want to lose it. Anyone have any ideas or anyone know anything about this update?
Click to expand...
Click to collapse
What firmware are you on? If you're on NC9, then it's probably the NE3 update which fixes the bugs in NC9. You can root NE3 very easily with towelroot. I suggest trying to take the update with one of your phones. Odds are that the update will fail to install anyways because you're rooted.
If you're already on NE3 and receiving an update, then I have no idea what it is. Either way the update will fail to install because you've modified system files, so you have nothing to worry about.
Okay I am on NC9. Would there be a noticeable benefit to go stock, take the NE3 update, then acquire root with towel root? I don't have any problems with my phone but my wife seems to have some issues with hers. Not sure what all the update addressed.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
SebringTech said:
Okay I am on NC9. Would there be a noticeable benefit to go stock, take the NE3 update, then acquire root with towel root? I don't have any problems with my phone but my wife seems to have some issues with hers. Not sure what all the update addressed.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Click to expand...
Click to collapse
Unfortunately you can't just unroot and take the update. You have to go all the way back to stock by flashing the ML2 Odin package and then flash the OTA update. Flashing the Odin package will completely wipe the phone so I suggest backing up anything you want to save with Titanium Backup.
As for benefits, the NE3 update will probably fix some of the issues with your wife's phone and put her on the latest version, but functionally it should be the same as NC9. Samsung didn't add any additional features or functionality to the NE3 update, they just fixed all the bugs they created with the NC9 OTA. Rooting is super simple now with towelroot so you shouldn't consider that a deterrent.
If you want to try to fix some bugs then update to NE3, if you're perfectly happy with the way your phone is running now then you're not missing out on anything.
If you ever have questions about firmware and updates again, check the Firmware Thread first. I try to keep that updated as soon as I hear about new firmware.
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
How does this affect our device when it gets the lollipop update?
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Since I am running dynamic Kat on stock slot right now, I should be safe from updates for now right?
Waiting to see what happens with all this. I did back up my stock rom to an SD card, so I can restore and unroot etc... to get an update if I choose to later.
muniz_ri said:
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Click to expand...
Click to collapse
was looking for a post like this. well maybe we might get 5.1 in the next few weeks or sooner so i am sure you will give it a try and a good look and hopefully you will have success in attaining root and a good SS. seems like u da man for this...:good::good:
as for 5.1 or a custom rom...well whose to say what that will bring...
will be waiting to see what happens. will check back here when it comes out. i watch for it everyday and as usual, thank you for all your great work!
miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Not necessarily, just because (if) the S5 gets 5.0 does not mean the ability to root will be lost just go check out the Verizon S5 forums you'll see they have a method for rooting with 5.0 that in theory should work for us as well. again it is recomended to remain on a 4.4.x rom until this has been fully evaluated.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
My suggestion would be not to take any updates until the root capabilities have been evaluated.
As always, research goes a long way towards alleviating fears and stopping panic attacks before they happen. be patient there are great devs here give them time to work
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
the att gs5 doesn't seem like it's getting any updates..
wmunn said:
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
Click to expand...
Click to collapse
How are you liking it? I'm seriously thinking about doing the same thing.
I have a coworker that just got the Lollipop update for his Note 3 so that means it will be coming to the S5 very soon!
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
silentscreamz said:
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
Click to expand...
Click to collapse
I used that method as well. Sure, it worked for me, but I came from Dynamic Kat, a well debloated stock rom. Due to this, after installing the update using this method, the built-in apps restore function could not complete due to having all of the useless bloatware back, taking up the extra space I was free to use in Dynamic Kat. Even removing the apps that are safe to remove via Titanium Backup doesn't help because the space is reserved for them. I've also already moved every app that it will allow to move to SD card. I've removed unneeded apps. I've gone through my internal storage to remove any unneeded files.
I've removed most of the apps listed here
This doesn't give me the Bluetooth tether that I used to us for my Gear 1(Running Null Rom). I'd look for an app to cover this but... I can't install anything because I've got no space to do so... I hope a good debloat method comes along soon. I still have root, so I'm hopeful.
Yea, bloatware is ridiculous for this phone. Have you tried the Alliance rom, that is what I run and it's not to bad for bloatware but I have only managed to get 5.6 running. Going to try version 8 today sometime. If you like to customize that is an awesome rom.
Hi folks, new to the S5 forums on here as I just upgraded from my trusty S3 on AT&T. I'm still on the stock 4.4.2 firmware, NG3 build, and I'm wondering if I should just root from here using TowelRoot method or take the 4.4.4 OTA and root from there.
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
SoCalHTCFuze said:
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
Click to expand...
Click to collapse
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
MetalHead66 said:
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
Click to expand...
Click to collapse
You gotta downgrade theres a post on here just type it in the search bar. Pretty easy process
Yes. Follow the 4.4.2 how to root thread, it says that bit still works.
OK thanks a bunch. Getting ready to do that now.
---------- Post added at 03:27 AM ---------- Previous post was at 02:53 AM ----------
Well that was quite easy and I'm a happy camper now! Just had to flash nd3 kernel with odin in order for TR to work then flash my ng3 kernel. So nice to be able to use TiBu. Helium wouldnt install all my apps. Now I can start freezing and uninstalling all the bloatware!
I’m guessing this has already been asked but I didn’t find a good answer for it, so I will ask here. I recently got my Verizon S6 Edge (SM-G925V) and was able to root it using Ping Pong and had no problems at all (with Super SU installed) – kudos to Keen Team. I’m on G925VVRU1AOC3 now (stock) but maybe a week ago, I started receiving a notice to install an OTA update. Should I install the OTA and if so, should I unroot my phone prior to installing the update? Sorry if I seem cautious but I've not seen this discussed about the S6 Edge and I definitely don't want to trip KNOW or brick my phone.
Thanks in advance,
UCG
UnderCoverGuy said:
I’m guessing this has already been asked but I didn’t find a good answer for it, so I will ask here. I recently got my Verizon S6 Edge (SM-G925V) and was able to root it using Ping Pong and had no problems at all (with Super SU installed) – kudos to Keen Team. I’m on G925VVRU1AOC3 now (stock) but maybe a week ago, I started receiving a notice to install an OTA update. Should I install the OTA and if so, should I unroot my phone prior to installing the update? Sorry if I seem cautious but I've not seen this discussed about the S6 Edge and I definitely don't want to trip KNOW or brick my phone.
Thanks in advance,
UCG
Click to expand...
Click to collapse
If you read the q&a section on the ping pong root sub forum you will learn that thee ota cannot be installed after you have achieved root. Perhaps the best thing to do is unroot using odin then install the ota
sent
Download smart switch onto your PC and update thru that way. It will update and you will loose root but all your data is not touched. Then you use pingpong to reroot.
dansto82 said:
Download smart switch onto your PC and update thru that way. It will update and you will loose root but all your data is not touched. Then you use pingpong to reroot.
Click to expand...
Click to collapse
Thanks @dansto82 and @Snowby123, I actually did those things. I did the ODIN thing, it didn't work (the reason I posted this thread was because I saw what to do for AT&T, Sprint, T-Mobile, but no Verizon steps). So when ODIN and factory resets didn't work, I ran the Verizon utility that comes with the phone and I did the "repair" (which downloads and installs a fresh copy of the stock ROM) and then I updated from OC3 to OE2 and that toasted my phone (and I can't downgrade either). The device actually works until it finishes booting up, then the touch screen has issues and performance is slower than my big wheel in a blizzard, but at least root is gone because I have to send it back now. The setup process runs without issue until it completes (so it isn't the physical screen). Either way, my S6 Edge 128GB OC3 phone ended up not liking the OE2 update. and I just got off the phone with Verizon and they are sending me another one. Let's hope that works.
Got my replacement phone (came with OC3). Updated to OE2 and rooted, works great. I guess caution when unrooting the Verizon S6 Edge to do an OTA.
It appears that once you install the OF1 update you can't flash back to OE2
Sent from my SM-G925V
Hello everyone. I did the root on my Galaxy S6 edge, and everything's been working great. The only thing I really use it for right now is so that I can run my app radio unchained reloaded app. Otherwise I haven't changed anything. Recently I've been getting carrier updates coming in that I have not been able to accept. They continue to fail. Is there a way I can update my phone yet still keep root? Or is there something else going on?
Chemdawg said:
Hello everyone. I did the root on my Galaxy S6 edge, and everything's been working great. The only thing I really use it for right now is so that I can run my app radio unchained reloaded app. Otherwise I haven't changed anything. Recently I've been getting carrier updates coming in that I have not been able to accept. They continue to fail. Is there a way I can update my phone yet still keep root? Or is there something else going on?
Click to expand...
Click to collapse
You can Odin back to stock (oc3), take update, then root using latest ping pong root. Or, flash a custom oe2 rom using flashfire, then use Odin to update firmware to OE2, such as is explained here: http://forum.xda-developers.com/showthread.php?p=61198002. Or use smart switch to update, which will remove root.
This question was asked a few days ago:
http://forum.xda-developers.com/showthread.php?p=61365924
Sent from my SM-G925V