Database Develop

Sprint S4 and Towelroot - Discussion

So Towelroot is working on many S4 variants... But ours. Bummer.... So close. I started this thread in hopes that an authority on the subject might chime in on possible reasons as to why. Also Towelroot has gotten quite a bit of attention as a proof of concept for a major security flaw in Android devices. What are your opinions on that?

Its witchcraft! Burn those responsible at the stake!!
Sent from my SPH-L720 using Tapatalk

This is bad news. I've been wanting to try towelroot for the past 2 days, asking around if it works on our Sprint S4. Do you think it'll ever work on ours? If it works on Sprint Note 3 there's no reason why it shouldn't.

edmund75 said:
This is bad news. I've been wanting to try towelroot for the past 2 days, asking around if it works on our Sprint S4. Do you think it'll ever work on ours? If it works on Sprint Note 3 there's no reason why it shouldn't.
Click to expand...
Click to collapse
I can say first hand it is completely safe to attempt to run towelroot... It will not trip Knox or the flash counter, etc, etc... It just does nothing. If you watch a video if towelroot in action you will see text after you “make it ra1n"... But on our devices it just says black below the button then resets the phone.

There is a list of devices that says the sprint s4 works with towel root.
http://www.droidviews.com/root-att-and-verizon-galaxy-s5-without-voiding-knox-warranty/

Noticed that towelroot has been updated to version 2- no more reboot. May give it a try. However, I just read an article about towelroot saying,
"A flaw in the Android operating system may leave many Android phones and tablets vulnerable to attack, including the Samsung Galaxy S5 and Google's own Nexus 5. It's the same flaw that was recently discovered in the Linux kernel, on which Android is based — and a just-released Android "rooting" tool that uses the flaw could make the problem even worse.
Exploiting the flaw on an Android device yields root permissions, or total control of the system. That's not itself malicious, but the exploit could also let attackers remotely download malware, copy the device owner's files and other personal data, disable the device's security apps and create a backdoor for more attacks, according to San Francisco-based security firm Lacoon Mobile Security."
Any thoughts?

A true double edged sword. Kinda scary the Antivirus gave it an OK... Yet android actually warned me. I've read that in Linux systems the bug has been fixed.. However with so many generations and models of phones and tablets it's trickier.
I'd say the best solution would be an apk that can be ran on a rooted device (or with the bug... Not) that fixes or at least blocks it.

That's a negative on version 2... But nothing tripped. Odd thing... It still resets on its own.

noob with sprint sg4
Syntaxerror999 said:
I can say first hand it is completely safe to attempt to run towelroot... It will not trip Knox or the flash counter, etc, etc... It just does nothing. If you watch a video if towelroot in action you will see text after you “make it ra1n"... But on our devices it just says black below the button then resets the phone.
Click to expand...
Click to collapse
when I say noob I mean noob...I'm new to Android and I have no clue really what I'm doing all I know is that I wanted to be rooted because I used to use iPhone and I'm in jail breaker, which gave me the ability to not be charged out the bottom from Sprint just to tether my unlimited data to my computer. after trying to understand the wholr "rooting" process I gave up ( i suffer with OCD and ADD and that is not a good combination when teaching yourself anything tech...plus if you haven't notice I tend to be long winded and very detailed about very unnecessary information just as this last sentence sorry) Yesterday I came across Towelroot was very skeptical but continued reading as much as I could find and decided after reading "it won harm your device to try" I did..... and it works!!! first try unbelievable... now I just got to try to teach myself what to do now... there is a lot of information in computer language that the typical ex jail breaker doesn't understand....it's going to be a long road ahead of me but from what I've read so far it's going to be great. Thanks!
btw....I read this thread and wanted to reply to let people with the sprint sg4...that it's possible but I wasn't registered .... I guess things happen for a reason! if anyone has some helpful information that they can give me as to bypass the frightening journey me and my OCD andADD have in trying to work through the mass amounts of information in this strange language I sure would love ya for it! lol but what doesn't kill me will only make me smarter. love the site guys!

cwithy74 said:
Yesterday I came across Towelroot was very skeptical but continued reading as much as I could find and decided after reading "it won harm your device to try" I did..... and it works!!!
Click to expand...
Click to collapse
Worked for you? How updated was your device?

Syntaxerror999 said:
Worked for you? How updated was your device?
Click to expand...
Click to collapse
I'm staying away from the kit Kat update..read too much negative
my software: L720VPUEMK2
android version: 4.3
I'm not sure if that is what you wanted to know...I'm not very educated on the computer lango. .
just to let you know though I used towelroot then checked to see if it worked using root checker basic and it was a success then I downloaded superuser couldn't update so u installed it checked my root again it was gone. I opened towelroot again ran it and was rooted again...now I'm just trying to figure out what I need to be safe and secure and get started learning what I am able to do now... hope this info helps

cwithy74 said:
I'm staying away from the kit Kat update..read too much negative
my software: L720VPUEMK2
android version: 4.3
I'm not sure if that is what you wanted to know...I'm not very educated on the computer lango. .
just to let you know though I used towelroot then checked to see if it worked using root checker basic and it was a success then I downloaded superuser couldn't update so u installed it checked my root again it was gone. I opened towelroot again ran it and was rooted again...now I'm just trying to figure out what I need to be safe and secure and get started learning what I am able to do now... hope this info helps
Click to expand...
Click to collapse
so you basically used towelroot on 4.3? enh, I used saferoot, which was released a while back, to root 4.3 without tripping Knox... what we need to know is will towelroot give us root on 4.4 NAE...

cwithy74 said:
I'm staying away from the kit Kat update..read too much negative
my software: L720VPUEMK2
android version: 4.3
I'm not sure if that is what you wanted to know...I'm not very educated on the computer lango. .
just to let you know though I used towelroot then checked to see if it worked using root checker basic and it was a success then I downloaded superuser couldn't update so u installed it checked my root again it was gone. I opened towelroot again ran it and was rooted again...now I'm just trying to figure out what I need to be safe and secure and get started learning what I am able to do now... hope this info helps
Click to expand...
Click to collapse
Yes that's exactly what I wanted to know. This would explain why some sites are reporting it as working on our model

Works fine on NAE. Download latest towelroot (v3), click the title 3 times, enter "1337 0 1 7380 4 0". Click "Make it rain".
Enjoy root. No KNOX tripped.

DXtremz said:
Works fine on NAE. Download latest towelroot (v3), click the title 3 times, enter "1337 0 1 7380 4 0". Click "Make it rain".
Enjoy root. No KNOX tripped.
Click to expand...
Click to collapse
What is the reason for entering "1337 0 1 7380 4 0" before making it rain?

Because it doesn't work otherwise. It's a modstring to modify the exploit parameters for our specific device.

DXtremz said:
Because it doesn't work otherwise. It's a modstring to modify the exploit parameters for our specific device.
Click to expand...
Click to collapse
Alrighty, I'll give it a try. Thanks!

DXtremz said:
Works fine on NAE. Download latest towelroot (v3), click the title 3 times, enter "1337 0 1 7380 4 0". Click "Make it rain".
Enjoy root. No KNOX tripped.
Click to expand...
Click to collapse
Aw man...I was just about to post this and you beat me to it.... but yes folks the above offset will make towelroot work on 4.4

Syntaxerror999 said:
Aw man...I was just about to post this and you beat me to it.... but yes folks the above offset will make towelroot work on 4.4
Click to expand...
Click to collapse
I concur the successful rooting of our beloved Sprint S4 (NAE)!! Enjoy everyone!

For sure worked. Just did it on my friends Sprint GS4 that has never been rooted.

Achieving Root on OTA 5.0 G900A using keyboard vuln?

Hey guys, this is my first post on XDA, so I hope I have it in the correct format and place; if not, just politely let me know and I will adjust the post accordingly. This is also just a theory I have on how to achieve root with the OTA 5.0 update, and would like the community's feedback on whether this would work or not.
First, let me start by saying that I don't have much experience with rooting, but I have done a lot of reading and research about how it works and feel like I have a good understanding of how it works. I do however, have a lot of programming and computer security experience, so I like to stay current on active vulnerabilities and such, whether it be on mobile devices or computers.
So I was stupid took the OTA update to 5.0 before checking to see if anyone managed to achieve root, to find out that 5.0 root hasn't been achieved on my model yet so I started to look for a way to do it myself. As I was browsing around for general info on the G900A, the keyboard vulnerability stuck out to me immediately.
To summarize the vuln: "A remote attacker capable of controlling a user’s network traffic can manipulate the keyboard update mechanism on Samsung phones and execute code as a privileged (system) user on the target’s phone. This can be exploited in a manner that requires no user interaction — a user does not have to explicitly choose to download a languagePack update to be exploited." So essentially, if I were to set up my own rogue Wi-Fi access point, I'd be able to execute any code I want in a privileged context.
On NowSecure's website, they go into deep detail on the specific steps of recreating this exploit, but to summarize here are the general steps:
Step 1:
Set a global Wi-Fi proxy and point our device at mitmproxy on our computer
(Essentially creating your own controlled Man-In-The-Middle attack for your phone)
Step 2:
Write a script that feeds the phone a zip containing our payload upon download request from the keyboard
Step 3:
Precompute the SHA1 of our payload and create a custom manifest file containing the SHA1
Add path traversal to the payload and attempt to write to /data/
Now, we have an arbitrary file write as system user. Next, we attempt to turn this file write ability into code execution.
Step 4:
Choose DeviceTest.apk as our target to exploit (this file is owned by a group system and is automatically invoked)
Generate an odex file with code for a BroadcastReceiver named com.sec.factory.entry.FactoryTestBroadcastReceiver
The exploit source will look like this:
Code:
➜cat FactoryTestBroadcastReceiver.java | head
package com.sec.factory.entry;
import java.lang.Class;
import java.io.File;
import android.content.BroadcastReceiver;
import android.content.Context;
import android.content.Intent;
import android.util.Log;
public class FactoryTestBroadcastReceiver extends BroadcastReceiver {
//Exploit code here
}
Step 5:
Once the payload is created, we compile it and run it through the DalvikExchange (dx) tool to get a .jar file which includes our dalvik bytecode
Push our jar to our phone and generate the odex using
Code:
ANDROID_DATA=/data/local/tmp dalvikvm -cp /data/local/tmp/<payload.jar> com.sec.factory.entry.FactoryTestBroadcastReceiver
This will put our cache file in a directory that is readable by the shell user.
Step 6:
Patch our .odex to contain the CRC32 and modification time from the original APK's zip file so it appears to be generated from the original DeviceTest.apk
Step 7:
Trigger the vulnerability to execute the payload
Here is the fully detailed article .
So my question is: would it be feasible to use this vuln to create a payload that injects root into the system?
To check to see if you're vulnerable to this exploit
Download a terminal emulator on your phone and type:
Code:
ls -l /system/app/SamsungIME*
If you see a line that looks like:
Code:
-rw-r--r-- root root 7243414 2008-08-01 07:00 SamsungIME.apk
and the date is older than 2015-03-16 you are vulnerable.
UPDATE: As of July 1, 2015, AT&T appears to have rolled out a small OTA update that updates the bootloader from OC4 to OF2 as well as patches the keyboard vulnerability. As long as you don't take the update and the date modified for SamsungIME.apk is earlier than 2015-03-16, this vulnerability could still be of some potential benefit.

Here is the link your wanting to post.
https://www.nowsecure.com/blog/2015/06/16/remote-code-execution-as-system-user-on-samsung-phones/
I really hope you are on to something.
I used terminal emulator and it looks like this (attached)
Looks like I'm vulnerable.
You seem to know your stuff and I hope some people can work with you to make some things happen
I just read the full article your source.. in theory root should be possible. I'm not sure how but maybe using the exploit to install cf as a system app. Then it could run with higher privileges I suppose. Or maybe just a custom zip to obtain the root.
Damn this makes me happy! I only wish I was smart enough to make it work lol
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

adam_ky said:
I really hope you are on to something.
I used terminal emulator and it looks like this (attached)
Looks like I'm vulnerable.
Click to expand...
Click to collapse
Thank you!
I'd really love to collaborate with some devs or something. I would be able to test most of those steps out myself, but would need help with the scripting of the actual payload. Then if it actually works, I ultimately would want to automate it and turn it into a redistributable application that anyone could use by just clicking a few buttons (seeing as how literally every non-rooted S5 should be vulnerable, I would want anyone to be able to use it). But I would need some help on that as well.
Also, until I (or anyone else) can confirm that this method either succeeds or fails, I'd hold off on taking any security updates that may patch this, just in case this method does end up working.
adam_ky said:
I just read the full article your source.. in theory root should be possible. I'm not sure how but maybe using the exploit to install cf as a system app. Then it could run with higher privileges I suppose. Or maybe just a custom zip to obtain the root.
Click to expand...
Click to collapse
That's exactly what I was thinking. If this exploit works the way I think it will, there should be no real constraints on the code you can execute and privilege escalation should be a breeze whether it's with something like cf, or a custom zip.
adam_ky said:
Damn this makes me happy! I only wish I was smart enough to make it work lol
Click to expand...
Click to collapse
Haha I was pretty ecstatic when I happened upon this and I couldn't really believe that no one else had put these two ideas together before I did. I tend to be more of a lurker on forums, so I was kind of iffy about posting this, but I'm really glad it's being well-received so far!
I'm really excited for this exploit's potential and can't wait to see where this leads!

https://www.nowsecure.com/blog/2015/06/16/remote-code-execution-as-system-user-on-samsung-phones/
I'm not sure it would be possible for an automated means of execution via an app or something. The one step in the process mentions that what has to be entered is device unique. But with the exploit it is kind enough to give you that bit of info needed.
The best we might be able to hope for here is connecting to your own personal wifi network with capabilities of injecting code exploit. Which shouldn't be to hard really.
We just need someone to create a payload for us and have a good step by step howto.
I'd be willing to volunteer both my time and device for testing this. I like you, just need a but of help.
However if no help comes I may try it myself lol
I'm pretty sure I can work out the steps . And set up a connection that's capable of injecting the code threw the keyboard exploit. I just need help with the scripts.
This exploit could do so much really... besides root. You could use it to delete preload bloat system apps. You could use it to edit the build.prop. you could use it to manually edit the host file. Should be able to run the script that allows read/write permissions over whole device for user.
I'm glad I have had my security updates set to off since the beginning as this has supposedly been fixed and pushed by samsung threw the policy updates
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

adam_ky said:
I'm not sure it would be possible for an automated means of execution via an app or something. The one step in the process mentions that what has to be entered is device unique. But with the exploit it is kind enough to give you that bit of info needed.
The best we might be able to hope for here is connecting to your own personal wifi network with capabilities of injecting code exploit. Which shouldn't be to hard really.
We just need someone to create a payload for us and have a good step by step howto.
I'd be willing to volunteer both my time and device for testing this. I like you, just need a but of help.
However if no help comes I may try it myself lol
I'm pretty sure I can work out the steps . And set up a connection that's capable of injecting the code threw the keyboard exploit. I just need help with the scripts.
This exploit could do so much really... besides root. You could use it to delete preload bloat system apps. You could use it to edit the build.prop. you could use it to manually edit the host file. Should be able to run the script that allows read/write permissions over whole device for user.
I'm glad I have had my security updates set to off since the beginning as this has supposedly been fixed and pushed by samsung threw the policy updates
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, by automating it, I was thinking more along the lines of building an executable to be run on a computer that contains the necessary MITMproxy program, script for feeding the phone a zip, the actual payload, etc.
And the unique identifiers should only change based on the current version of android and which variant of the phone it is. So if I'm reading it right, the identifiers should all be the same for every G900A running 5.0. Either way, this exploit should be easy enough for most everyone to use, but it'd still be nice to make a program with a nice interface to it.
Yeah, I think with this exploit you could basically have control over just about anything you want, the only hard part would be making a payload for each thing you want to do.
As far as the exploit being fixed by Samsung, I think they have acknowledged the exploit and have "fixed" it, but the patches either haven't been pushed from Samsung to the carriers for distribution or the carriers haven't pushed out the update to fix it yet. According to NowSecure's website,
"As of June 16 2015, this is the known (but not all-inclusive) list of impacted devices by carrier with patch status:
Device | Carrier* | Patch Status
Galaxy S6 | Verizon | Unpatched
Galaxy S6 | AT&T | Unknown
Galaxy S6 | Sprint | Unpatched
Galaxy S6 | T-Mobile | Unknown
Galaxy S5 | Verizon | Unknown
Galaxy S5 | AT&T | Unknown
Galaxy S5 | Sprint | Unknown
Galaxy S5 | T-Mobile | Unpatched
Galaxy S4 | Verizon | Unknown
Galaxy S4 | AT&T | Unknown
Galaxy S4 | Sprint | Unknown
Galaxy S4 | T-Mobile | Unknown
Galaxy S4 Mini | Verizon | Unknown
Galaxy S4 Mini | AT&T | Unpatched
Galaxy S4 Mini | Sprint | Unknown
Galaxy S4 Mini | T-Mobile | Unknown
"
So I'm fairly certain that there won't be many phones that have the exploit patched (yet), which is definitely a good thing for all of us right now.

I wish some other people would chime in... surely this intrests more ppl than just you and I.
I'm sure this community can make something workable out of this exploit.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

I really do too. I thought people would be all over this, and this is really the best place to post it

Today I had a talk with Samsung IT crew. General reason was wifi leakage on boc3 firmware on Sm-n910c. Also had a talk about keyboard vulnerability. Samsung's IT leading engineer told they know about it and it's on final stage of fixing. So in very short time it's gonna be fixed and no more hacking over keyboard will be available. So this door is finally to close soon(bad part is that also rooting over it will be impossible, but it's nice that Samsung very soon rolls out a fix for it so no more remote injections and rahcking will be possible). So hurry up, doors are closing soon finally. You should contact chainfire, maybe he will help you in rooting that phone.
Sent from my Galaxy Note SM-910C running SweetROM v14 using XDA free app

Sapphire999 said:
Today I had a talk with Samsung IT crew. General reason was wifi leakage on boc3 firmware on Sm-n910c. Also had a talk about keyboard vulnerability. Samsung's IT leading engineer told they know about it and it's on final stage of fixing. So in very short time it's gonna be fixed and no more hacking over keyboard will be available. So this door is finally to close soon(bad part is that also rooting over it will be impossible, but it's nice that Samsung very soon rolls out a fix for it so no more remote injections and rahcking will be possible). So hurry up, doors are closing soon finally. You should contact chainfire, maybe he will help you in rooting that phone.
Sent from my Galaxy Note SM-910C running SweetROM v14 using XDA free app
Click to expand...
Click to collapse
Oh interesting. Did they happen to mention any kind of time frame or just that they were in the final stages?
And I'll try to contact chainfire, but it seems like he hasn't been active on his G+ for a few months.

They told it's on final tasting stage. But that about Galaxy Note 4 talk, that we had. Not sure about other models. I simply asked of it since it bad when over wifi my phone can be hacked by some man in a middle. So if you plan still use that keyboard hack, you probably should ban updates to avoid that door closed.
And as they told roll out can happen from day to day. Meant very soon.
I also searched the web, your device should be rootable. If last ota update hack fails, use sammobile and downgrade os to root it and then search rooted custom roms
Sent from my Galaxy Note SM-910C running SweetROM v14 using XDA free app

Sapphire999 said:
They told it's on final tasting stage. But that about Galaxy Note 4 talk, that we had. Not sure about other models. I simply asked of it since it bad when over wifi my phone can be hacked by some man in a middle. So if you plan still use that keyboard hack, you probably should ban updates to avoid that door closed.
And as they told roll out can happen from day to day. Meant very soon.
I also searched the web, your device should be rootable. If last ota update hack fails, use sammobile and downgrade os to root it and then search rooted custom roms
Sent from my Galaxy Note SM-910C running SweetROM v14 using XDA free app
Click to expand...
Click to collapse
Ah, ok. Thank you for sharing and I'll definitely keep any updates disabled.
And I think there's a problem with downgrading due to the bootloader being locked by AT&T.

You're welcome. My device is unlocked likely. Any way guess you can search sammobile. Maybe you will sucess somehow to downgrade.
Loool. I have an idea. If you success hacking keyboard etc, probably you could somehow face ota to downgrade firmware. Hmmm... you know what. There is an option. Not sure if it will work, but still. Try getting custom rom. And boot your phone even with original firmware into recovery mode. Usually volume up + home + power. If it works, you can make restore from zip deploying custom rom.
Maybe it will not work, but you can try. If a bit lucky, you wouldn't need root on current rom. No warranties and it just in theory. Try at your own risk.
Sent from my Galaxy Note SM-910C running SweetROM v14 using XDA free app
---------- Post added at 04:42 AM ---------- Previous post was at 04:22 AM ----------
http://hexamob.com/how-to-root/android-rooting-method-samsung-galaxy-s5/
Doesn't this one work for you?

No, that way doesn't work and is for a previous version of android, not 5.0. When the G900A is updated to 5.0, the bootloader firmware is updated to patch the exploit that that method uses.

https://www.youtube.com/watch?v=1dYoDX07Cks
Told any S5 lolipopp running. Unfortunally or likely, I don't know what locked bootloader mean. Never had such. Does it mean that recovery mode and odin mode are unavailable(not launchable)?

As of this moment, if a att s5 sm g900a took the ota update to lolipop, there is no means to gain root access.
If you achieve root on kitkat, you can update to lolipop and keep root.. but that's it.
This keyboard exploit is our only possible ray of hope at this moment.
Root may not even be possible with it as it runs with system privilages.. which is actually not the same as root privilages.. however system privilages can do a lot and I got hope for it.
Even if root can't be obtained.. this exploit could be used to do things to the device that we currently cant. Could possibly remove system and preinstalled bloat. It can defiantly install an app as a system app... that should be able to a compliance quite a bit.
The possibilities are endless really.
I am thankful the exploit is there and hope we can acompliwb something with it before everyone gets patched.
I have my security policy updates disabled and I suggest you do the same for the time being if anyone out there is in the same boat as us.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Couldn't have said it better myself.
Also, I have attempted to contact Chainfire on both of his G+ accounts, so hopefully something can come of that too.

Hmm if so, just keep it mind not only to disable updates, but to keep away from wifis with internet access. On some conditions auto update setting are ignored, if connected to wifi. Surely depends on exact system and model. But keep it in mind. Well. If you gain system app privilegies, then possibly you get partitions access. That a hope to deploy something like twrp recovery and flash custom rom. Info about soon coming keyboard breach fix I got for GN4 model SEB (Baltic) region. Cann't say anything exact about other models and regions. But generally if Samsung is one step away from rolling it out in Baltic, quite possible other regions coming also soon.
Sent from my Galaxy Note SM-910C running SweetROM v14 using XDA free app

I just got an update and it's a bootloader upgrade from oc4 to I forgot and I suspended the update till I can get some more info . Check and see if you have it .
Sent from my SAMSUNG-SM-G900A using Tapatalk

superp32 said:
I just got an update and it's a bootloader upgrade from oc4 to I forgot and I suspended the update till I can get some more info . Check and see if you have it .
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
From all the information I've gathered, this update does appear to patch the keyboard.
EDIT: I do have an available update too and attached a screenshot.
EDIT 2: I've seen the "Date modified" of the SamsungIME.apk change to one of two dated after taking the small OTA, either 2014-03-25 or 2015-03-16. If the date is the one from 2014, the vulnerability should still be active, but if it's the newer one, it appears to have been patched.

FYI... I posted the screen shot showing the 2015 update but my phone was already loaded with 5.0/OC4 when I received it from at&t last week and I have not updated to the new bl. Hope some can still benefit from the keyboard vulnerability even if I can't.

AT&T Software update as of 7/9/15 - 146.75MB

Not sure what this is yet. Non rooted, stock image.
5.1.1?? Will report back...

Not 5.1.1
No idea as they haven't posted changelog, but hopefully a fix for MicroCell issues everyone is experiencing.
Let us know if you see any changes.

Update downloaded.
Real upgrade from OE2 to OF3. Thats all it says.

@Globalrebel where are you looking for change logs?
Update just finished. Yeah Android version is still 5.0.2. Baseband G925AUCU2AOF3 now.

Getting it now.

http://www.att.com/esupport/softwar...are&siteId=JAF5WzpxbKM-uxPru.0S4qk9EABb6wNW3Q
Change Log

Ssj237 said:
http://www.att.com/esupport/softwar...support/sharedSegments/supportViewService.jsp
Change Log
Click to expand...
Click to collapse
Session timed out. Please use the back button, reload and try again.

That build date of june 18th piss anyone else off lol

veener79 said:
Session timed out. Please use the back button, reload and try again.
Click to expand...
Click to collapse
Should be fix now

msfguard said:
That build date of june 18th piss anyone else off lol
Click to expand...
Click to collapse
You mean since 5.1.1 was supposed to hit the S6's "in June?"
This is getting ridiculous, we need an update from 5.0.2, the memory issues I'm dealing with even on XtreStoLite are almost unbearable

Exactly and as updates for 5.1 come out for other carriers we get updates for random att crap that are almost a month old

It's sad to say that the latest AT&T OTA patches the export for ping pong root, don't take the OTA, because you cannot downgrade the Odin fails

dnp77 said:
It's sad to say that the latest AT&T OTA patches the export for ping pong root, don't take the OTA, because you cannot downgrade the Odin fails
Click to expand...
Click to collapse
how you know? you ota it ?
i was "downloading" then saw your post. so i reboot my phone to cancel it.

netnerd said:
how you know? you ota it ?
i was "downloading" then saw your post. so i reboot my phone to cancel it.
Click to expand...
Click to collapse
They know because it says on the Ping Pong Root thread not to update for anything past May 15th as the method for root has been patched

I'm curious if there are any other undocumented changes besides the 2 official changes listed earlier. It feels like a fairly big patch for a fix to an phone location and a kernel security fix.

Is there any hope, luck or signs of achieving root on this new firmware
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app

Wow, what a crappy push out by AT&T.
In any case, what process do i need to freeze in TB to stop my phone from trying to download and/or annoying me with that pop-up when it does happen?

aidanipod said:
Is there any hope, luck or signs of achieving root on this new firmware
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
Please see just ONE post above yours........ we have just been talking about the exploit being patched
Globalrebel said:
Wow, what a crappy push out by AT&T.
In any case, what process do i need to freeze in TB to stop my phone from trying to download and/or annoying me with that pop-up when it does happen?
Click to expand...
Click to collapse
AT&T Software Update is the main one, but there are a few others - I don't have an AT&T ROM on mine right now to help out, but it's been posted a few times already (I think I even posted those once)

Just freeze att software update. Then it can't even run so no downloads. I got lucky I clicked on update after reading it in Android central but didn't want to install it. Postponed couple of times but somehow it automatically loaded the update process. I was like sh#t. When it booted up it said a problem updating. And then I blocked the updater. My root almost gone lol
Sent from my SAMSUNG-SM-T337A using Tapatalk

saketkutta said:
Just freeze att software update. Then it can't even run so no downloads. I got lucky I clicked on update after reading it in Android central but didn't want to install it. Postponed couple of times but somehow it automatically loaded the update process. I was like sh#t. When it booted up it said a problem updating. And then I blocked the updater. My root almost gone lol
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
Same thing happened to me being rooted. It just tried to install automatically. Woke up to my phone restarting but then I got the error "problem updating". I was pretty relieved on that error lol... :victory:

New 08/05/15 update

AT&T software updater just downloaded a new update.
The file is 301.08mb
What's the word?
Going to try and upload the file soon.

DOWNLOAD LINK:
https://mega.co.nz/#!SUoTFIJR!zhmzM7DUyN_4MWhdUbI-9JHask3l_PJQG9FHTX5flNk

File info:
Android version: 5.0
Baseband version: G900AUCU4BOF3
Kernel version: 3.4.0-4432708
Build number: LRX21T.G900AUCU4BOF3
Upgrade file size: 301MB
Software update includes
Device security enhancements
Patch Info:
AT&T Patching Devices Against Stagefright Vulnerability
I am assuming this update would break root?

Any chance you collected an url for the source? (if possible)

Upgrade Device Software for the Samsung Galaxy S5 (G900A)

No, I mean is there a way on an S5 to collect the actual OTA url used to download that file. On Nexus phones it is often used to help validate the OTA someone hosts. No offense, but I'm not trusting a random stranger that posts an "ota". I'd like to know if there is a way to confirm via a direct url from the vendor.
EDIT: As in this article - http://www.droid-life.com/2014/06/05/download-nexus-ota-url-file/

davidalindsey said:
File info:
Android version: 5.0
Baseband version: G900AUCU4BOF3
Kernel version: 3.4.0-4432708
Build number: LRX21T.G900AUCU4BOF3
Upgrade file size: 301MB
Software update includes
Device security enhancements
Patch Info:
AT&T Patching Devices Against Stagefright Vulnerability
I am assuming this update would break root?
Click to expand...
Click to collapse
Not necessarily but it will definately update your bootloader leaving you with no way to unbrick should something go wrong other than BestBuy or an ATT store. I am checking it out to see if there is a safe way to update and keep root. Stand by...

@muniz_ri
Sounds good.
@zenrage
I have no ideal how to pull up the OTA File URL.
I assure you the one I uploaded is a direct copy and paste from my / cache/ fota folder on my phone.

muniz_ri said:
Not necessarily but it will definately update your bootloader leaving you with no way to unbrick should something go wrong other than BestBuy or an ATT store. I am checking it out to see if there is a safe way to update and keep root. Stand by...
Click to expand...
Click to collapse
This is another 5.0 version and it is rootable. I will upload a new ROM to update and keeproot.

I just tried to collect the url, and failed. the logcat was dumping tons of data. And since it was my first attempt at logcat for this new device, I connected it only after the start of the download was flushed from the log. . I dare not interrupt the ongoing download, as I have no clue how Samsung/AT&T would handle an incomplete download.
Protip: if you gonna try to logcat the url - be frickin fast!

Not sure if this is the right place to ask this question, but how would I update from OC4 to this new build? I'm using my att s5 with T-Mobile so I can't get ota's. Thanks!

Its_Tim said:
Not sure if this is the right place to ask this question, but how would I update from OC4 to this new build? I'm using my att s5 with T-Mobile so I can't get ota's. Thanks!
Click to expand...
Click to collapse
I have rooted att s5 on t-mobile and I use this to update . just make sure to backup apps and data.
http://forum.xda-developers.com/att...w-to-update-to-g900aof2-5-0-keeproot-t3149146

Did this update last night on my wife's S5 and it still has root.
I also did it on my G870A and my root is still working.

jackinct said:
Did this update last night on my wife's S5 and it still has root.
I also did it on my G870A and my root is still working.
Click to expand...
Click to collapse
Is your bootloader still OA1, or it got updated as well?

Bad juju
Stock, unrooted AT&T S5 on 5.0.
Just did the update and now all of my apps on the SD card show grayed and uninstalled.
All else looks OK. Any pearls of wisdom?
EDIT - rebooted on its own about 5 minutes later and hung at the "globe". Had to pull the battery to restart. Still no SD apps.

My wife just installed this (stock, unrooted) and she is having an issue with the phone waking up. Massive lag for it to do so. I'm think I'm gonna hold off for my rooted phone.

davidalindsey said:
DOWNLOAD LINK:
https://mega.co.nz/#!SUoTFIJR!zhmzM7DUyN_4MWhdUbI-9JHask3l_PJQG9FHTX5flNk
Click to expand...
Click to collapse
Taking that how can i update my phone?
Im stock and unrooted of2
How i zip that file?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

xBlue_ said:
Taking that how can i update my phone?
Im stock and unrooted of2
How i zip that file?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
If you're stock unrooted why not just update normally?

geicogecko said:
If you're stock unrooted why not just update normally?
Click to expand...
Click to collapse
Bcuz im outside from USA and i need zip file i cant get ota
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

davidalindsey said:
DOWNLOAD LINK:
https://mega.co.nz/#!SUoTFIJR!zhmzM7DUyN_4MWhdUbI-9JHask3l_PJQG9FHTX5flNk
Click to expand...
Click to collapse
If I download this, I can sideload it thru adb to do the update? I'm not on wifi so I can't take the OTA.
Sent from my SAMSUNG-SM-G900A using Tapatalk

G900A with no AT&T apps, logos or bootscreen.

I have spent 2 days looking for info on this phone and can't find a thing. It is possible I have been looking in the wrong place but here is what I have. I purchased what was supposed to be a brand new g900a. While the phone is in new condition it has no att apps, no att logo on the back and no att boot logo. The phone also has many features missing from the att version like the ability to turn of lte, native call recording and additional controls in the quick access bar.
The bootloader shows official firmware and Knox has not been tripped but the baseband version shows the exact version of the fully bloated att version.
Is it possible I have come up with a g900a that came directly from the factory and never made it to att? If so is it possible the bootloader never got locked?
I have done a factory reset. I haven't dared try updating. I refuse to turn on wifi until I know more to avoid any possible att updates.
Anyone have any ideas on what I have? I have thought about trying to install some of the klte roms but I want a recovery image and more information before I try.
Just to add a bit more information the build number is "dongchao.a725"
I have found other references to dongchao stating they are fakes but I do not think that is the case here but it may not be a us release.
Any help would be greatly appreciated.
Sent from my SAMSUNG-SM-G900A using Tapatalk

This is what I did. http://forum.xda-developers.com/showthread.php?p=64251984
Sent from my SAMSUNG-SM-G870A using Tapatalk
Edit: oops wrong thread

jpruett79 said:
I have spent 2 days looking for info on this phone and can't find a thing. It is possible I have been looking in the wrong place but here is what I have. I purchased what was supposed to be a brand new g900a. While the phone is in new condition it has no att apps, no att logo on the back and no att boot logo. The phone also has many features missing from the att version like the ability to turn of lte, native call recording and additional controls in the quick access bar.
The bootloader shows official firmware and Knox has not been tripped but the baseband version shows the exact version of the fully bloated att version.
Is it possible I have come up with a g900a that came directly from the factory and never made it to att? If so is it possible the bootloader never got locked?
I have done a factory reset. I haven't dared try updating. I refuse to turn on wifi until I know more to avoid any possible att updates.
Anyone have any ideas on what I have? I have thought about trying to install some of the klte roms but I want a recovery image and more information before I try.
Just to add a bit more information the build number is "dongchao.a725"
I have found other references to dongchao stating they are fakes but I do not think that is the case here but it may not be a us release.
Any help would be greatly appreciated.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Whatever model it says in Odin mode is the actual model.

Rakuu said:
Whatever model it says in Odin mode is the actual model.
Click to expand...
Click to collapse
Odin does show this
Product Name: SM-G900A
Current Binary: Samsung Official
System Status: Official
Reactivation lock(kk): Off
Knox Warranty Void: 0X0
Qualcomm SecureBoot: Enable (CSB)
RP SWREV: S1, T2, R1, A4, P1
Secure Download: Enable
Based on my limited knowledge it was what i expected to see.
I have since determined that it must be a refub. I didnt catch this till about an hour ago but the S/N: on the back does not match the S/N: under phone info. I dont know how since the IMEI match in both places.
I did try the phone info app and it said the phone is not a refub?
I do have the opportunity to get my money back but I love not having all the att bloat on my phone. Plus this phone has features enabled that are not normally available.
I guess my big question now is How safe and secure are the DONGCHAO builds from a privacy standpoint? I have been unable to confirm the bootloader status. The phone is not currently rooted.

jpruett79 said:
Odin does show this
Product Name: SM-G900A
Current Binary: Samsung Official
System Status: Official
Reactivation lock(kk): Off
Knox Warranty Void: 0X0
Qualcomm SecureBoot: Enable (CSB)
RP SWREV: S1, T2, R1, A4, P1
Secure Download: Enable
Based on my limited knowledge it was what i expected to see.
I have since determined that it must be a refub. I didnt catch this till about an hour ago but the S/N: on the back does not match the S/N: under phone info. I dont know how since the IMEI match in both places.
I did try the phone info app and it said the phone is not a refub?
I do have the opportunity to get my money back but I love not having all the att bloat on my phone. Plus this phone has features enabled that are not normally available.
I guess my big question now is How safe and secure are the DONGCHAO builds from a privacy standpoint? I have been unable to confirm the bootloader status. The phone is not currently rooted.
Click to expand...
Click to collapse
Can you post a screenshot of the about phone page from settings.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Rakuu said:
Can you post a screenshot of the about phone page from settings.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
First of all THANK YOU for your help and input on this.
Is this the info you are after? I can provide more if needed.

jpruett79 said:
First of all THANK YOU for your help and input on this.
Is this the info you are after? I can provide more if needed.
Click to expand...
Click to collapse
Well you're on lollipop, so I think you're screwed for root or anything, that's the att firmware so I'd assume bootloader is locked also, I don't really know for sure so don't quote me on this , I personally say wait for a second opinion on this.

Rakuu said:
Well you're on lollipop, so I think you're screwed for root or anything, that's the att firmware so I'd assume bootloader is locked also, I don't really know for sure so don't quote me on this , I personally say wait for a second opinion on this.
Click to expand...
Click to collapse
I figured root and the bootloader being unlocked are a long shot.
I think I could live without root considering this phone doesn't have much bloatware to remove. And I love the extra features that are not normally enabled.
What I can't figure out is how it has the att rom but no other trace of att. I am hoping to learn the difference in the build numbers as they relate to the baseband version.
The seller has sent me a return label to send it back but they will provide no information regarding the phone or its origins. I have a few more days to decide and ship it back.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Here are some screenshots from phoneinfo. Hopefully they will help clear up this puzzle. I don't know why the build number in phone info would disagree with the number in the about setting but they do.
Phone info also shows I have root but SU and root checker seem to disagree.
I would be happy to share this Rom if we can figure out how to extract it. I really love the having a phone with no AT&T crap on it.
Edit:
Phone does appear to be rooted after all. After a reset SU is not installed. Before installing SU i checked root with two separate apps and both said i had root. Once installing SU i checked again and access was denied but SU was not promoting me for access. I changed the default access to allow and once again root checker showed root access.
There may be hope for this phone yet but i really want to get to the bottom of the DONGCHAO build if anyone can help.

jpruett79 said:
Here are some screenshots from phoneinfo. Hopefully they will help clear up this puzzle. I don't know why the build number in phone info would disagree with the number in the about setting but they do.
Phone info also shows I have root but SU and root checker seem to disagree.
I would be happy to share this Rom if we can figure out how to extract it. I really love the having a phone with no AT&T crap on it.
Edit:
Phone does appear to be rooted after all. After a reset SU is not installed. Before installing SU i checked root with two separate apps and both said i had root. Once installing SU i checked again and access was denied but SU was not promoting me for access. I changed the default access to allow and once again root checker showed root access.
There may be hope for this phone yet but i really want to get to the bottom of the DONGCHAO build if anyone can help.
Click to expand...
Click to collapse
As for the dongchao deal I have no clue. You do have root though if its saying you do with no su manager installed or with the default access set to allow which is extremely interesting because you don't have the KK bootloader which is how it's usually done, so either the previous owner rooted it and updated the bootloader or you have a weird version, I do agree you should get a dump of it though. Like I said though, id wait for a second opinion first and in this case so it can be determined if what you have maybe opens an opportunity to get root while on lollipop.
Sent from my SAMSUNG-SM-G900A using Tapatalk

I'm working on trying to get a rom dump but i'm not sure how to do that without custom recovery. I have not tried to install that yet based on fear of loosing official status and making it harder to return the phone if need be. I have no issue giving up official status if i can figure out what i have because i will keep it.
I have been thru kies and smart switch both show this as a Chinese build. They show OF2 (CHN) Unfortunately this is still vulnerable to stagefright and there are no available updates. I have checked the build for malicious software and all 5 apps i have tried give it a clean bill of health.

jpruett79 said:
I'm working on trying to get a rom dump but i'm not sure how to do that without custom recovery. I have not tried to install that yet based on fear of loosing official status and making it harder to return the phone if need be. I have no issue giving up official status if i can figure out what i have because i will keep it.
I have been thru kies and smart switch both show this as a Chinese build. They show OF2 (CHN) Unfortunately this is still vulnerable to stagefright and there are no available updates. I have checked the build for malicious software and all 5 apps i have tried give it a clean bill of health.
Click to expand...
Click to collapse
It's possible someone modified the build.prop to make it look like the AT&T version through about device. It's really, really easy to do.
Sent from my SM-T520 using XDA Premium HD app

shakatu said:
It's possible someone modified the build.prop to make it look like the AT&T version through about device. It's really, really easy to do.
Sent from my SM-T520 using XDA Premium HD app
Click to expand...
Click to collapse
If that's the case is it possible the bootloader may be unlocked. If so would it be worth trying to load another rom if I could find one for a g900a.
Sent from my SAMSUNG-SM-G900A using Tapatalk

shakatu said:
It's possible someone modified the build.prop to make it look like the AT&T version through about device. It's really, really easy to do.
Sent from my SM-T520 using XDA Premium HD app
Click to expand...
Click to collapse
Modifying the build.prop doesn't change what it says in download mode, that will always say what the actual model number is.
Sent from my SAMSUNG-SM-G900A using Tapatalk

I didn't realize how far behind I was until I started looking into this phone. I may be way off base with this but if we assume this is a Chinese refurbished and I'm sure it is at this point. Wouldn't it still show a g900a in download mode but the software could be different. Could they have take their rom and changed the build.prop to look like the art version. That would explain why I have att numbers but no trace of anything AT&T.
If that's all the case should I consider it a blessing to have a debloated/rooted lollipop. Or should I run from it like the plague.
I'm trying to install twrp now and I'm having trouble getting twrp manager to download the image so the bootloader may still be locked. I may still try installing with Odin in the morning.
Sent from my SAMSUNG-SM-G900A using Tapatalk