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.
Hi folks,
Just got my TF701T from Amazon on the $279 deal. I've connected it to my wifi but have not even set up a google account for it yet. It's doing an initial charge.
Is there any compelling reason not to let the update happen? The main short term use for the tablet will be that my 7 year old son will play games on it. Eventually, I'd still like to unlock it and maybe to a custom OS, but for now it's plain Jane use.
The only special thing I might want to do is get Helium/Carbon going so I can backup / restore game positions for him... I've got his status on several games saved from another tablet that had root and I backed them up. Would like to restore if possible. Does this require root?
Thanks. Looking forward to advice.
Marc
Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!
royredman said:
Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!
Click to expand...
Click to collapse
Thanks. I've used Carbon and believed it requires root, too. I'm a bit surprised that Towelroot wouldn't work on 4.4.2, as it was originally designed for 4.4.2 on Samsung and similar related kernel units. I've used it on my Samsung S4, and it required being on a pretty up to date 4.4.2 build. Wouldn't work on 4.3. But it may be different on the Asus.
I saw a mention off battery drain on 4.4.2 but without details. I'll continue looking. For now I've charged then powered off the tablet. No time to set it up tonight anyway. Seems like a very nice unit though.
Thanks for your reply!
Marc
Frankenscript said:
Thanks. I've used Carbon and believed it requires root, too. I'm a bit surprised that Towelroot wouldn't work on 4.4.2, as it was originally designed for 4.4.2 on Samsung and similar related kernel units. I've used it on my Samsung S4, and it required being on a pretty up to date 4.4.2 build. Wouldn't work on 4.3. But it may be different on the Asus.
I saw a mention off battery drain on 4.4.2 but without details. I'll continue looking. For now I've charged then powered off the tablet. No time to set it up tonight anyway. Seems like a very nice unit though.
Thanks for your reply!
Marc
Click to expand...
Click to collapse
Yeah, from what I understand, towelroot worked on the galaxy s4 (my current awesome phone) because the exploit wasn't patched at that time for the phone, but sadly Asus patched it as for the 4.4.2 drain, Netflix seems to be one of the couple of apps that is really draining power. Not really sure about it, but I'm probably not going to update until the next update is released.
royredman said:
Yeah, from what I understand, towelroot worked on the galaxy s4 (my current awesome phone) because the exploit wasn't patched at that time for the phone, but sadly Asus patched it as for the 4.4.2 drain, Netflix seems to be one of the couple of apps that is really draining power. Not really sure about it, but I'm probably not going to update until the next update is released.
Click to expand...
Click to collapse
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?
Frankenscript said:
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?
Click to expand...
Click to collapse
You can use any on. I just used the one that was on my tablets before (which was US). 10.26.1.18 is the 4.3 file to grab. Yup, unzip once and put it on the sd root file. For me, when I rebooted it, it let me know that there was a downloaded update detected (NOT the normal "click this button to download the system update")(be really careful about that one). Once I tapped the detected update file, it showed me it was the 10.26.1.18 file and I told it to install it.
If you want to see what to freeze, go into the towelroot thread in the Q&A section and look for my posts on the last page or so. I was asking exactly the same thing and they answered it all for me. Good luck and let me know if it goes well!!
Frankenscript said:
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?
Click to expand...
Click to collapse
You got it.
The .18 firmware is the JB 4.3. But stick to your SKU (US, WW - whatever it is now).
Once rooted freeze DMClient and CMClient and you won't be bothered with OTA updates.
Thanks! It's all done.
For anyone who reads this and needs to do the same thing, it was super easy. Just plugged the new Tab into the PC via USB, opened up to "Internal Storage", copied the UL-K00C-US-10.26.1.18-user.zip file over there, and rebooted. It auto-applied, rebooted again. Eventually I had to delete the .zip file from the internal storage, because on each reboot it would notice it and spend time figuring out if it had new updates or not.
Then Towelroot, SuperSU, and used App Quarantine-Root to freeze DMClient and CMClient. Rebooted again and no more update waiting for download messages.
I'm good to go!
royredman said:
Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!
Click to expand...
Click to collapse
First, i can confirm battery issues with 4.4.2. Android sometimes does not go to deepsleep (even if there are no addition apps installed, it seems a general problem). If i charge the tablet to 100% and go to bed, on the next morning i can be glad, if i have 30% battery left. Not always, but every 2.nd or 3rd night.
Second, a little question. Becauce of this "bug" i'd like to root my tablet and use a custom rom. I would like to use this method "http://forum.xda-developers.com/showthread.php?t=2604462 <- [MOD] JB 4.3+ | TF701T | Flashable Root Method v2 | Asus Stock 10.26.1.7/18
My first problem is the unlock app from asus. On the support site a text says: "1. Only suitable for Android4.2 Jelly Bean OS version" . But, according to most of the threads here, i should also work with 4.4.2??
The second question is, if the root method i just linked, works without any problems with the last asus update 4.4.2?
Using the tablet with this battery issue is horrible.
Thanks!
Hypothetix said:
First, i can confirm battery issues with 4.4.2. Android sometimes does not go to deepsleep (even if there are no addition apps installed, it seems a general problem). If i charge the tablet to 100% and go to bed, on the next morning i can be glad, if i have 30% battery left. Not always, but every 2.nd or 3rd night.
Second, a little question. Becauce of this "bug" i'd like to root my tablet and use a custom rom. I would like to use this method "http://forum.xda-developers.com/showthread.php?t=2604462 <- [MOD] JB 4.3+ | TF701T | Flashable Root Method v2 | Asus Stock 10.26.1.7/18
My first problem is the unlock app from asus. On the support site a text says: "1. Only suitable for Android4.2 Jelly Bean OS version" . But, according to most of the threads here, i should also work with 4.4.2??
The second question is, if the root method i just linked, works without any problems with the last asus update 4.4.2?
Using the tablet with this battery issue is horrible.
Thanks!
Click to expand...
Click to collapse
Reg. Battery drain: Did you run Netflix on those nights you had that severe battery drain?
Reg. Unlock: The tool should work on any fimware version. Just run it. Worst case scenario: It won't work.
Reg. Root: Why would you root the stock rom if you want to replace it with a custom rom anyway?
To install a custom rom you need to:
A) unlock the bootloader
B) flash a custom recovery in fastboot
C) create a nandroid of your stock rom in recovery
D) wipe cache, Dalvik and data using your custom recovery
E) flash the custom rom (which is rooted anyway).
For general reference on flashing custom roms to the Transformer, check out my guide here:
http://forum.xda-developers.com/showthread.php?t=2688891
NOTE: This is a guide for the TF700!! The general instructions on flashing, fastboot commands etc still apply. The specifics like recovery and version, bootloader and version etc DO NOT.
For TF701 specific instructions check out the OP of the CROMi-X thread in the Development section for the TF701 here on XDA.
berndblb said:
Reg. Battery drain: Did you run Netflix on those nights you had that severe battery drain?
Reg. Unlock: The tool should work on any fimware version. Just run it. Worst case scenario: It won't work.
Reg. Root: Why would you root the stock rom if you want to replace it with a custom rom anyway?
Click to expand...
Click to collapse
Thanks. Yes i know. I like the look the stock rom has. Therefore i first wanted to test, if i can stop the battery drain, if i use apps like greenify to send a few apps to deepsleep.
I rooted yesterday and tested it. Unfortunately, even with greenify i have the same problem. Every time i use the keydock, the tablet does not go into deepsleep mode. I checked with wakeup detector if i can find out which app is bad, but there are no apps which wake up the tablet more that 5 or 6 times.... If i use the tablet without the dock i dont have this problem (or just when i use netflix and dont reboot after usage)
Now i will try a custom rom....maybe it helps.
Thanks !
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.
I bought this phone today, and it was on 4.1 or something - some rom. I came back to XDA the wonderful fairy land to make my dreams come true.
Alas, and as always (6th phone in a row) I am lost. I rooted successfully the 4.1 (I forget what it *actually* was) and that was fine. It worked. I used a DooMLoRD special secret package that he made specifically for us Canadians, I don't know how I found it either as it was buried deep in a different thread. As far as I know the 'perf'(..?) exploit has been patched by Sony.
Seeing how I haven't been around here in about 10 to 16 months, I forgot how everything works. I upgraded my device to the official 5.1.1 expecting to retain my root, and then intended on getting my hands a little dirty in the coming weeks (or at least get a Kernel that seeks to improve battery life)
my bootloader is still locked. I will note, however, that Kingroot, the APK succesfully got me rooted. But that app is weird, and I don't know if I trust it... I also don't know what would happen if I tried to flash a new kernel.
ANYWAY THANKS FOR READING THIS
Search tool is a gift, I have been and will continue to be searching probably way too intensely for a fix or some help.
Cheers to all
k.
I have seen talk of ppl trying things out as to how to roll back from 6.6 to 6.5 in order to unlock the bootloader, install yerp, etc. Has anybody on this forum heard of anything I could try? I obviously didn't do my research on the phone before updating it but I do have average experience with rooting, using Android SDK and spft so any suggestions are welcome!
it has been mentioned that the only downgradable (or workable) v6.6 is when it is installed using the SAFE method.
http://forum.xda-developers.com/r1-hd/how-to/safe-v6-6-prime-update-via-twrp-t3459257
but if not, as ColtonDRG himself said : "The V6.6 update brought a new preloader that breaks our ability to use SPFT. I am currently working on ways to reverse the damage, but as of right now, there is no way to convert (or downgrade) from software V6.6."
I have not yet rooted it so everything is still stock so upgrading via the safe method doesn't really apply for me. Thanks anyways, guess I'll be waiting for a new root method to come about. Hopefully ppl haven't already forgotten about this phone lol.