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!
Related
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.
This is my first Android phone i have owned for a few years now and i made the mistake of doing the OTA update to 4.3. I would love to root this phone because that was a big reason why i got it. I hated waiting for a jailbreak for my iPhone and i want a phone that i have control over. is it possible to "downgrade" from the OTA update to the leaked update? or even downgrade back to 4.2.2? I have looked around but cant find anything to helpful for the galaxy s4 active. also reading around multiple people say they end up having issues after downgrading or the KNOX counter going from 0x0 to 0x1, therefore voiding warranty.
RobbieHag said:
This is my first Android phone i have owned for a few years now and i made the mistake of doing the OTA update to 4.3. I would love to root this phone because that was a big reason why i got it. I hated waiting for a jailbreak for my iPhone and i want a phone that i have control over. is it possible to "downgrade" from the OTA update to the leaked update? or even downgrade back to 4.2.2? I have looked around but cant find anything to helpful for the galaxy s4 active. also reading around multiple people say they end up having issues after downgrading or the KNOX counter going from 0x0 to 0x1, therefore voiding warranty.
Click to expand...
Click to collapse
While the OTA upgraded Android to 4.3 it also included a new bootloader. The new bootloader prohibits "downgrading" to a firmware version below ML2. Currently there is no way to downgrade with the locked bootloader. However there is a new thread just started by @TransformixS4 that is looking at injecting root into the ML2 Odin files, so it may be possible in the future to root ML2. There are a couple threads in the regular S4 forums exploring ways to exploit the bootloader and flash custom kernels.
Back to your situation: you're completely stuck. Next time you see there is an update or OTA check XDA before you install it. There are a couple threads that explain the pros and cons of any updates. There is also a thread summarizing all the AT&T i537 firmwares which will be updated in the future and you may find useful.
Devo7v said:
While the OTA upgraded Android to 4.3 it also included a new bootloader. The new bootloader prohibits "downgrading" to a firmware version below ML2. Currently there is no way to downgrade with the locked bootloader. However there is a new thread just started by @TransformixS4 that is looking at injecting root into the ML2 Odin files, so it may be possible in the future to root ML2. There are a couple threads in the regular S4 forums exploring ways to exploit the bootloader and flash custom kernels.
Back to your situation: you're completely stuck. Next time you see there is an update or OTA check XDA before you install it. There are a couple threads that explain the pros and cons of any updates. There is also a thread summarizing all the AT&T i537 firmwares which will be updated in the future and you may find useful.
Click to expand...
Click to collapse
My issue was I kept telling it not to upgrade, and then it went ahead and did it anyway! On 4G, not wifi even. I was so mad when I got home and started reading that all the stuff I downloaded to root it *that day* would no longer work.
Caboose27 said:
My issue was I kept telling it not to upgrade, and then it went ahead and did it anyway! On 4G, not wifi even. I was so mad when I got home and started reading that all the stuff I downloaded to root it *that day* would no longer work.
Click to expand...
Click to collapse
You're only allowed to delay the update 4 or 5 times before it installed automatically. You can prevent it from upgrading in the future by freezing some system apps with Titanium Backup. I don't remember which ones right now, but if you search it's pretty easy to find.
Caboose27 said:
My issue was I kept telling it not to upgrade, and then it went ahead and did it anyway! On 4G, not wifi even. I was so mad when I got home and started reading that all the stuff I downloaded to root it *that day* would no longer work.
Click to expand...
Click to collapse
Just checking, you do have the i537 not i9295, right?
My setup: 4.4 ATT Moto X, Rooted (by way of latest jcase method), Locked bootloader, and I'm pretty sure write protection is off (though I don't remember how to check)
What I am wanting to know is how would and should I be able to get to 4.4.2, and get my root back (as I'm not confident any method will be able to "keep" my root safely without screwing something else up)? What's the best way based on my setup, and what files or tools would I need(stock 4.4 or 4.4.2 ROM, a new recovery image, etc)?
Since the root method I used hijacks the recovery, I suppose I technically don't have a functional one (other than it maintaining my root). Do I even need a custom recovery? I don't ever plan to flash anything other than basic stock firmware, though I may toy around with Xposed in the future. Also as a sidenote, im currently using ART instead of Dalvik. If any method or technique might conflict with that (other than Xposed), then let me know to the best of your knowledge.
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
...
Sent from my XT1058 using XDA Premium 4 mobile app
kj2112 said:
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Honestly i dont even care to have an unlocked bootloader. I just realy need root after I update. Write protection, so far i think, i've only needed for AdAway to work on my phone, though Im sure I have used or applied it else on my device. And thanks for the thread, but I was already subscribed .
Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
Click to expand...
Click to collapse
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
NameLessThugZero said:
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
Click to expand...
Click to collapse
The only ways to use 4.4.2 Rooted with Write Protection DISABLED is the Safestrap way, or to unlock your bootloader.
Since you have AT&T, Moto doesn't give out the code to unlock your bootloader (Non-Developer Edition Verizon phones are the same way.) so if you really want to unlock your bootloader, see -> http://forum.xda-developers.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651 I know the thread title says VERIZON but it works for ATT users too.
I see, thanks for the explanation, because I certainly wouldn't have know it was for AT&T users too! I'll check them out.
Sent from my XT1058 using XDA Premium 4 mobile app
Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)[/QUOTE
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
NameLessThugZero said:
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
Right. You want a modified version of the OTA that does not modify your bootloader and will patch /system from 4.4 to 4.4.2. I also manually patched the kernel up to 4.4.2.
And, my experience is that you also have to downgrade to 4.2.2. I don't quite understand why, but I have never been able to upgrade to 4.4.x (neither from the 4.4 leak or the official 4.4 version) without going back to 4.2.2 first. The eclipse ROM instructions, on the other hand, suggest that a safestrap:twrp factory wipe might be enough, but I remember trying that once, and it didn't work. YMMV
I already made a zip to flash a full copy of 4.4.2 (not a patch) that I made from my system dump, but it hasn't been tested. (I'm waiting for the SBF.)
Alright. Well I guess I'll have to wait a bit for someone to come out or prove there's a safer, surer method to update. Moto always did like to make thing like this difficult, heh.
Sent from my XT1058 using XDA Premium 4 mobile app
I've searched high and low for a root for my new galaxy note 3. I've seen somethings say the las vegas one or whatever but it couldn't be done on 4.4.2 kitkat. I've seen something about kingo. Which is the best method to root and unlock my boot loader so that i can flash roms.
Samsung galaxy note 3
Android version 4.4.2 kitkat
model- SM-n900a
Thank you in advance for your help! :good::laugh:
No rooting yet and there hasn't been unlocked bootloaders on the AT&T Note 3 yet.
Sent from my SAMSUNG-SM-N900A using Tapatalk
really???? bummer
A root method for 4.4.2 will be found eventually, so try to tough it out until its found. Not having root sucks, but it will hopefully come soon. An unlocked bootloader will most likely never happen unless someone holds the CEO of AT&T hostage (any volunteers?), so no custom kernels or AOSP for us unless someone gets Loki working.
Face_Plant said:
A root method for 4.4.2 will be found eventually, so try to tough it out until its found. Not having root sucks, but it will hopefully come soon. An unlocked bootloader will most likely never happen unless someone holds the CEO of AT&T hostage (any volunteers?), so no custom kernels or AOSP for us unless someone gets Loki working.
Click to expand...
Click to collapse
I'm glad your that positive that a root method for 4.4.2 will be found, however (not to be a negative nelly) KK has some security features that Google has added, that would make it even harder to achieve root. That, with the added AT&T "updated" locked bootloader, would make it almost impossible to obtain root. Then, adding salt to the wound, the new S5 has just been released, so every DEV that's worth their salt would want to hop on the new tech bandwagon and tackle something new.
I personally don't care about root. I never rooted my Note 3 until the OTA update, which kept getting stuck at 27%. I followed the instructions to obtain root, installed the OTA update, but FORGOT TO UNROOT my phone!!! That stupid SU app is in the way, and I can't uninstall it! When it comes time for me to upgrade my Note3 to a Note4, anyone can simply look in my app draw and see SU app. Even ISIS wont work because it thinks my phone is rooted. I want to simply root my phone, delete that SU app, and un-root. It's that simple. If I can do this using ADB, i'll try it in a heartbeat.
awe that sucks..hopefully someone comes up with some thing soon. Thanks for your replies. When they do come up with a root method would we still be able to flash roms being that our bootloader is locked?
dunn816 said:
I've searched high and low for a root for my new galaxy note 3. I've seen somethings say the las vegas one or whatever but it couldn't be done on 4.4.2 kitkat. I've seen something about kingo. Which is the best method to root and unlock my boot loader so that i can flash roms.
Samsung galaxy note 3
Android version 4.4.2 kitkat
model- SM-n900a
Thank you in advance for your help! :good::laugh:
Click to expand...
Click to collapse
At this time there is no way to root KitKat, period, either with De La Vega, or Kingo. In addition, the bootloaders are totally locked down. There currently is a petition here, to see if we can get AT&T to unlock them
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
dunn816 said:
awe that sucks..hopefully someone comes up with some thing soon. Thanks for your replies. When they do come up with a root method would we still be able to flash roms being that our bootloader is locked?
Click to expand...
Click to collapse
Search through the forum, there is a way to flash custom ROMS, just not in the typical way
lawalty said:
I'm glad your that positive that a root method for 4.4.2 will be found, however (not to be a negative nelly) KK has some security features that Google has added, that would make it even harder to achieve root. That, with the added AT&T "updated" locked bootloader, would make it almost impossible to obtain root. Then, adding salt to the wound, the new S5 has just been released, so every DEV that's worth their salt would want to hop on the new tech bandwagon and tackle something new.
Click to expand...
Click to collapse
It still doesn't hurt to look up. The S5 is locked down tight just like the Note 3 so I don't see why devs would dump the Note 3 just to work on another locked device. The Note 3 is still relatively new and pretty popular so I doubt it's going to be given up on just yet.
Ok so many of us have successfully rooted our devices and frozen update and renamed security files to avoid losing our root.
What are the proper steps for Dummies like me to accept the Lollipop OTA in December without losing my data?
Also now 4.4.4 is anounced with Bluetooth fixes that I have noticed while streaming
(My gut tells me keep update frozen until a flashable rooted 5.0.)
It was said in another thread NOT to take the 5.0 update until a root method for it has been established. If you wanna keep root, I'd wait. I'm still running stock rooted AND3 firmware/kernel. I'm looking to get the newest update up to today (I think ANG3 or something of that nature.) I'm just not taking updates yet so I can keep my root. I'm having problems with the phone freezing and restarting though so I'd like an update.
Sent from my "ROOTED" SAMSUNG-SM-G900A using XDA Premium 4 mobile app
NG3 is smooth
PS4AndroidHacker said:
It was said in another thread NOT to take the 5.0 update until a root method for it has been established. If you wanna keep root, I'd wait. I'm still running stock rooted AND3 firmware/kernel. I'm looking to get the newest update up to today (I think ANG3 or something of that nature.) I'm just not taking updates yet so I can keep my root. I'm having problems with the phone freezing and restarting though so I'd like an update.
Sent from my "ROOTED" SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am stock rooted with ANG3 pre-installed on my purchased S5. It runs smooth as silk if you use the method posted by muniz_ri in general. All I've done is turned off or frozen some bloatware and installed Chainfire SU 2.16.
My question was more geared towards the person who might want to go from rooted to the lastest OTA without losing data etc. I have been diving in pretty deep to the AT&T side of XDA since leaving sprint a week ago and I think the answer might have been posted by shortydoggg with the soft-bricked thread.
I was hoping someone might be able to tell me a non odin 3.09+ way to remove the freeze on my apps in the correct order to take the OTA without tripping KNOX if I wanted to do that knowing I might loose root.
I thought we might be able to follow muniz_ri and odin the one file back towelroot again after.
Basically I like stock always have, but I want root also for AdAway Titanium Backup Etc. and being a truck driver I wanted the 4.4.4 Bluetooth fix for Iheart radio.
UltraCon79 said:
I am stock rooted with ANG3 pre-installed on my purchased S5. It runs smooth as silk if you use the method posted by muniz_ri in general. All I've done is turned off or frozen some bloatware and installed Chainfire SU 2.16.
My question was more geared towards the person who might want to go from rooted to the lastest OTA without losing data etc. I have been diving in pretty deep to the AT&T side of XDA since leaving sprint a week ago and I think the answer might have been posted by shortydoggg with the soft-bricked thread.
I was hoping someone might be able to tell me a non odin 3.09+ way to remove the freeze on my apps in the correct order to take the OTA without tripping KNOX if I wanted to do that knowing I might loose root.
I thought we might be able to follow muniz_ri and odin the one file back towelroot again after.
Basically I like stock always have, but I want root also for AdAway Titanium Backup Etc. and being a truck driver I wanted the 4.4.4 Bluetooth fix for Iheart radio.
Click to expand...
Click to collapse
It's hard to say what the best approach will be until the update arrives. In the case of 4.4.4, I'm rather confident that a somewhat simple method can be developed to take the update while keeping root. As for 5.0, I have some ideas none ideal but we'll see.
Is Android 4.4.4 for the AT&T version of the Galaxy S5 out? I have a Galaxy S5 AT&T phone but I don't have AT&T service. I am running Android 4.4.2 with build version ND3 is there something newer than this?
Updating to NG3
Het guys, so today I got ahold of Odin 3.09 and the NG3 update, I applied it through Odin in the AP slot and it DID NOT update my phone to NG3. My Baseband still says AND3 and kernel is 3.4.0-2178781
Tue Jul 22 13:58:46 KST 2014. Anybody have any options i can use without having to downgrade to NCE just to upgrade? LOL...Im kinda at a loss,Ive tried it in download mode twice now and no fu go.
Plz disregard my message. I'm good now and running rooted NG3.