Related
I'm going to look around with Radiocomm to see what kind of information this can provide about the Droid 3. Any information I find (version numbers, etc) will be posted here to help get root going.
Haven't used this particular tool, but should be able to just check things out.
http://forum.xda-developers.com/showthread.php?t=1138072
(thread with latest Radiocomm, if you wish to explore as well)
Deafdan02 said:
I'm going to look around with Radiocomm to see what kind of information this can provide about the Droid 3. Any information I find (version numbers, etc) will be posted here to help get root going.
Haven't used this particular tool, but should be able to just check things out.
http://forum.xda-developers.com/showthread.php?t=1138072
(thread with latest Radiocomm, if you wish to explore as well)
Click to expand...
Click to collapse
would this help it talks about getting to the bootloader if not i will delete this.
http://modmymobile.com/forums/71-razr-v8/72211-getting-information-radiocomm-well-tricks.html
RadioComm is a very powerful tool but it will not help to "unlock" the bootloader.
There are a great many useful things to explore with RadioComm, but you need to be VERY CAREFUL when using it and I do NOT recommend randomly hitting any buttons in the GUI and never write or execute ANYTHING unless you are absolutely certain you understand both what you are doing and how to recover or restore default values!!!
This is really important if you want to avoid damaging your phone.
I will be posting a lot more about RadioComm and how to use it safely to read and write the NVM and other functions.
I've worked in a production environment with testing and programming software similar to this, so I can translate some of the commands used (but please feel free to share!). I am just using read or get commands at the moment, to get the information out to the community. On the plus side, I have another upgrade coming up in a few months, so if I do brick this one, I can get another
After looking around some, the P2K tabs are the only sections I find that communicate with the droid 3 so far.
The SW version reported:
Tcdma_solana-user 2.3.4 5.5.1_84_D3G-20_TA-9 110613 release-keysMDM6600BP_N_03.18.16P
And I believe the eFuse is on the D3 as well, since the section communicates and verifies it.
For about phone (kernel, build, etc):
http://www.mediafire.com/imgbnc.php/0898e7caaacf11060a68f7af37e593956ad00729f8c56800cd560e8c116a00866g.jpg
New MotoX from sprint.
android version 4.2.2
baseband msm8960pro_bp_2323.020.90.00r
kernel 3.4.42.-xline.
system version 139.14.1
build 13.9.0q2.x-116-mx-17-57-1
i did a fair amount of searching but could not find the proper instructions for obtaining root access for the moto x. Need root access or this device would be a deal breaker.
Can someone point me to a link? I would be much appreciated. Thanks Listers!!!
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
BrokenWall said:
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
Click to expand...
Click to collapse
I did search the web and the forums; I'm sorry. it was a long day, i had just purchased the phone and wanted to make sure i didn't brick it. I have rooted/jailbroken several other devices but wanted to know if the latest ota update would cause a problem for that.
Again, I'm sorry for for the excess forum baggage.
I'll try again.
BrokenWall said:
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
Click to expand...
Click to collapse
that simple? i have the tmobile version with an unlocked bootloader but i been looking for ways to root it and i have not been able to do it, so you saying that if i install TWRP that would obtain root automatically?
moises1204 said:
that simple? i have the tmobile version with an unlocked bootloader but i been looking for ways to root it and i have not been able to do it, so you saying that if i install TWRP that would obtain root automatically?
Click to expand...
Click to collapse
I read where a previous method of rooting (pwnmoto or whatever) was shut off by the latest ota.
Please help a new guy out.
http://forum.xda-developers.com/showthread.php?t=2487635
this thread is what I found. Please advise if this is the correct method. Thank you all, and sorry if I'm wanting to be sure I'm doing the right thing.
Thanks listers...I do very much appreciate any help.
bullpen7979 said:
I read where a previous method of rooting (pwnmoto or whatever) was shut off by the latest ota.
Please help a new guy out.
http://forum.xda-developers.com/showthread.php?t=2487635
this thread is what I found. Please advise if this is the correct method. Thank you all, and sorry if I'm wanting to be sure I'm doing the right thing.
Thanks listers...I do very much appreciate any help.
Click to expand...
Click to collapse
ownmoto or whatever?? um... ok... I can tell you haven't browsed the different sections for the Moto X here or you would have seen in the "Moto X Original Android Development" section that its called "PwnMyMoto"
Brokenwall gave you a way to root your sprint device, no matter what stock rom you're running... OTA updates or not. Granted unlocking your bootloader voids your warranty... and he didn't give you a 100% newbie step by step guide which it now seems you were really looking for.
Also in the Moto X Original Android Development is a thread titiled... "[Root] RockMyMoto (Yes, even the first OTA)" which is pretty obvious as to what it is for. If you took a few minutes to read it, you'd know it is what you want if you don't want to unlock your bootloader. Its not a very long thead (141 posts currently) so it wont take long to read. The original post contains everything you need, except how to make sure you have Telnet as part of your Windows install (there are posts in that thread later that say what to do to enable/install Telnet as a Windows Feature inside Add/Remove Programs).
Sorry, if I come across as harsh. I know you just want to root without screwing up your phone, and I get that. But I'm afraid if you haven't been able to look around and find this stuff, you'll likely not be able to properly follow and understand the instructions and will therefore stand a good chance of messing up your phone!!!
OK. I am sorry about the post. I know I'm at the mercy of the forum here.
I was up till 2 am getting this phone unlocked, but when I installed wireless tether it said I was not rooted.
Had to install sdk, get a long unlock code, etc.
Evidently I have yet to attain root access, but its not as though I"m not trying.
I have done rooted/jailbroken a couple times before with my htc evo/iphone, and am fairly computer literate, but I just can't hash this out.
I read this thread, but could not quite make out the steps. http://forum.xda-developers.com/showthread.php?t=2509590., The video has no sound, which makes it a little more difficult.
I have also read about an OTA on 10/7 or so that patched some of the root methods, so, at the risk of getting put in my place, I'm humbly coming to ask for assistance in helping get my phone rooted.
Again, I'm sorry for being stuck here and having to ask the question. I would greatly appreciate the assistance of someone who can speak to my specific situation.
Thank you and regards to those who can help.
Bull
bullpen7979 said:
OK. I am sorry about the post. I know I'm at the mercy of the forum here.
I was up till 2 am getting this phone unlocked, but when I installed wireless tether it said I was not rooted.
Had to install sdk, get a long unlock code, etc.
Evidently I have yet to attain root access, but its not as though I"m not trying.
I have done rooted/jailbroken a couple times before with my htc evo/iphone, and am fairly computer literate, but I just can't hash this out.
I read this thread, but could not quite make out the steps. http://forum.xda-developers.com/showthread.php?t=2509590., The video has no sound, which makes it a little more difficult.
Click to expand...
Click to collapse
The steps taken in the video are exactly explained in the post.
There are a few assumptions.. 1. Your PC has telnet on it, or you know how to install it. (there is a link further in that thread which Windows users can follow. 2. You have ADB Driver and Platform tools from the AndroidSDK installed correctly on your PC, and Moto drivers installed. Again, there are threads on this already, so you'll have to find/follow them.
You could also try to follow this post -> http://forum.xda-developers.com/showthread.php?p=47067076 however, it uses puttytel.exe instead of Telnet so it will look a little different. It too assumes you've properly installed ADB Driver and Platform Toos from the Android SDK along with the Moto drivers.
Another option is the "Tool Kit" -> http://forum.xda-developers.com/showthread.php?t=2477132 which is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. Only thing would be if you want to use "Flash back to stock" you need to download the ROM file separately.
bullpen7979 said:
I have also read about an OTA on 10/7 or so that patched some of the root methods, so, at the risk of getting put in my place, I'm humbly coming to ask for assistance in helping get my phone rooted.
Click to expand...
Click to collapse
Right now, there is the rom the phone shipped with. If you have that, you use PwnMyMoto process to root it. The "camera update" that was pushed over the air. If you have that, you use RockMyMoto. And as of yesterday, if you have Verizon X, there is KitKat which can not be rooted (unless your carrier allows you to unlock your phone's boot loader)
I tried the puttytel thread, but I kept getting a timeout like this guy did:
"After running cydia impactor I see a popup for a second that says payload and then it disappears. I then try to run puttytel but it just keeps failing with "network error: connection timed out"." That was the error I kept getting.
The other problem I am currently having is not being able to push files to my device because it doesnt show up as a drive letter. I have usb debugging enabled.
I would about paypal someone for some help at this point. Bummed. I just want my device rooted so I can send my daughter the one I promised here.
I tried the puttytel thread, but I kept getting a timeout like this guy did:
"After running cydia impactor I see a popup for a second that says payload and then it disappears. I then try to run puttytel but it just keeps failing with "network error: connection timed out"." That was the error I kept getting.
The other problem I am currently having is not being able to push files to my device because it doesnt show up as a drive letter. I have usb debugging enabled.
I would about paypal someone for some help at this point. I'd even accept remote assistance via logmein. Pretty bummed. I just want my device rooted so I can send my daughter the one I promised her.
I have no idea why this process has been so difficult this time around. I have rooted, downloaded & installed custom roms, etc.
http://forum.xda-developers.com/showthread.php?t=2536200
Please help. I am out of ideas.
jayboyyyy said:
http://forum.xda-developers.com/showthread.php?t=2536200
Click to expand...
Click to collapse
Isn't this just for the verizon model?
Guys/Gals/Developers.... I'm really stuck, and would greatly appreciate some help.
I have read thru the threads.
I can't get my phone to be recognized as a drive. Only a camera. Yes, I installed usb mass storage from play store. No luck.
I can't push files to the root of the device.
I have to believe it can be done, I'm just not getting it for some reason.
I'm really sorry, as I have said in multiple posts. Like I said, I would paypal you a reasonable sum if one of the more experienced people out there want to remote in via logmein and help. I know that sounds lame. I'm normally a guy who likes to research it all himself and do this.
I'm normally the guy who helps other people with this stuff, but I just can't hash this out. I've spent the last three days of my free time reading, researching, trying to get the thing to connect as a drive so I can push files to it and run them via adb.. Even went so far as considering buying a wireless adapter to put the files there wirelessly. I'd try now but I'm exhausted. If you can help, please PM me and we can work out something if you are willing. Thanks to those who have suggested methods. I do appreciate your help. I have tried them all except the last kit kat method which I thought was just for Verizon. I'm with sprint. As tired as I am, I'm afraid to brick the thing. I'm very close to asking for a method to restore the phone and take it back. I really wanted wireless tether. I need it for work and to run the ipad on occasion. Sorry this was a long post/thread.
Sorry I'm not as quick as the rest of you. Just want a rooted phone and can't seem to get it done this time on my own.
Any suggestions?
bullpen7979 said:
Isn't this just for the verizon model?
Click to expand...
Click to collapse
No. That will work for any Moto X Developer Edition or Carrier edition with an unlocked boot loader. So T-Mobile, Sprint, etc.. If you can unlock your boot loader via -> https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth then you can root via this process.
bullpen7979 said:
Guys/Gals/Developers.... I'm really stuck, and would greatly appreciate some help.
I have read thru the threads.
I can't get my phone to be recognized as a drive. Only a camera. Yes, I installed usb mass storage from play store. No luck.
I can't push files to the root of the device.
Click to expand...
Click to collapse
To get your phone to show up in windows as Drive Letter, needs USB Mass Storage mode. Ok, You've installed an app for that, fine... but 1. I'm not aware of that app working, and more importantly, 2. I am not aware of any root method in these forums that requires your phone to show as a "drive letter" to work. So I couldn't even begin to suggest what you are doing wrong.
What instructions are you actually trying to follow? Why not post questions on it in that particular thread, including exact details of what you've done, what you see on your phone, any/all errors or messages, etc.???
And if what you really want to do is tether with sprint, I hope you have checked out threads with suggestions on hacks/ways that work to tether on Sprint Moto X before you worry about rooting.
For example, if you want to remain non-rooted, FoxFi could possibly be an option. As I am a Verizon user and haven't used it, I can't say how well it works for Spint, and I can't say how well it works for Verizon, just that Verizon KK users say it doesn't work, but it did with the JB/4.2.2 roms..
KidJoe;
Thanks for your patience. I'm sorry about all of this. I have tried to be as clear as I can be, but I will redouble my efforts. Let me read clearly that last link and I will post back. I do want root access for all the other cool things it enables too, so I'm determined to get it right. I just want to be careful not to miss something and turn a decent phone into a paperweight.
That link you referenced is exactly what I used to unlock. When I reboot the phone, I get a white screen with a red exclamation point that says bootloader unlocked.
Fox Fi is a no go
Update. Just tried Foxfi. Does not work with current status of unlock but not rooted. I need root, but how does one copy files to the device via usb? I remember there being a setting.
I opened a new thread on this subject. http://forum.xda-developers.com/showthread.php?p=47740046#post47740046
Hope that's not against the rules. I really thing the failure is related to my inability (or ignorance of how to ) push files to the device.
Good gravy. This has eaten up WAY too much time.
Apparently its a mixed bag over at sprint. Some can some can't.
http://www.sprintusers.com/forum/showthread.php?t=234246
I see it mentioned a few times but what on the phone prevents say 4.4.2 from being installed after the upgrade to 4.4.3?
Because the partion table and bootloader are different and can't be downgraded at all.
Or, you can downgrade... But brick your device after, even later.
Anyone who knows anything about the moto x will tell you just don't. ?
I find that odd. I wonder what the purpose is for doing that.
There is no way to just re-write those sections? Even on a Dev Edition?
knitler said:
I find that odd. I wonder what the purpose is for doing that.
There is no way to just re-write those sections? Even on a Dev Edition?
Click to expand...
Click to collapse
Security!
Look at the whole Windows/AntiVirus industry.
All because Microsoft wanted unsecure compatibility with the old OS.
Saving software dev time making things work.
knitler said:
I find that odd. I wonder what the purpose is for doing that.
There is no way to just re-write those sections? Even on a Dev Edition?
Click to expand...
Click to collapse
No, the Dev edition is no different. All the same "rules" apply.
The Dev edition is the same as any other.... It just keeps is warranty if you unlock it.
aviwdoowks said:
Security!
Look at the whole Windows/AntiVirus industry.
All because Microsoft wanted unsecure compatibility with the old OS.
Saving software dev time making things work.
Click to expand...
Click to collapse
I'm kind of not buying this for a second?
How about linux, which is often pointed to for its security... And you can upgrade, down grade, switch out every component for newer/older/different, switch kernels, upgrade kernels, downgrade kernels... hell change out kernels with out even rebooting.
Really not buying it has anything with security.
KJ said:
Or, you can downgrade... But brick your device after, even later.
Anyone who knows anything about the moto x will tell you just don't. ?
Click to expand...
Click to collapse
I think we understand that, I mean if the OP didn't he wouldn't have the question of "why not?". Its not I think it might be a good idea... We are just trying to understand the situation because it seems unique, and so we were hoping someone who knows a lot about
AGISCI said:
Because the partion table and bootloader are different and can't be downgraded at all.
Click to expand...
Click to collapse
This is the most I have heard so far, and I have heard it once or twice... But can't the recovery image include information on the partition table?
I realize the way it is, but was curious on some more technical information explaining it...
scryan said:
I'm kind of not buying this for a second?
How about linux, which is often pointed to for its security... And you can upgrade, down grade, switch out every component for newer/older/different, switch kernels, upgrade kernels, downgrade kernels... hell change out kernels with out even rebooting.
Really not buying it has anything with security.
I think we understand that, I mean if the OP didn't he wouldn't have the question of "why not?". Its not I think it might be a good idea... We are just trying to understand the situation because it seems unique, and so we were hoping someone who knows a lot about
This is the most I have heard so far, and I have heard it once or twice... But can't the recovery image include information on the partition table?
I realize the way it is, but was curious on some more technical information explaining it...
Click to expand...
Click to collapse
It is security. Specifically the SECURED BOOTLOADER. Don't confuse secured with locked. Yes, you can unlock your bootloader, but it is still secured.
Read up on "TrustZone" and see why it is important, and why the OEMs would not want you to be able to downgrade. You can "buy" or "not buy" whatever you want....
I really don't get the linux reference. We are talking about a bootloader, not linux in general. That's beyond the fact that any smart linux user would almost never have any reason at all to downgrade. Think about the heartbleed vuln that was discovered recently. Why on god's green earth would you want to downgrade openssl back to a version that is vulnerable??
The early (4.2.2 & 4.4) bootloader (motoboot.img) was vulnerable to an exploit that allowed us to disable write protection. The updated bootloader (4.4.2+) is patched. You *CAN NOT* downgrade back to the vulnerable version.
^Does that not have *everything* to do with security??
scryan said:
I'm kind of not buying this for a second?
How about linux, which is often pointed to for its security... And you can upgrade, down grade, switch out every component for newer/older/different, switch kernels, upgrade kernels, downgrade kernels... hell change out kernels with out even rebooting.
Really not buying it has anything with security.
I think we understand that, I mean if the OP didn't he wouldn't have the question of "why not?". Its not I think it might be a good idea... We are just trying to understand the situation because it seems unique, and so we were hoping someone who knows a lot about
This is the most I have heard so far, and I have heard it once or twice... But can't the recovery image include information on the partition table?
I realize the way it is, but was curious on some more technical information explaining it...
Click to expand...
Click to collapse
Because even though the patition file and bootloader are included in the archive, they fail to flash because they have a lower version than what is installed.
AGISCI said:
Because even though the patition file and bootloader are included in the archive, they fail to flash because they have a lower version than what is installed.
Click to expand...
Click to collapse
Can't just fake the version number?
No, it's not possible.
samwathegreat said:
I really don't get the linux reference. We are talking about a bootloader, not linux in general. That's beyond the fact that any smart linux user would almost never have any reason at all to downgrade. Think about the heartbleed vuln that was discovered recently. Why on god's green earth would you want to downgrade openssl back to a version that is vulnerable??
Click to expand...
Click to collapse
The linux reference was in direct reply to the quote above it that was making the argument that the PC anti-virus industry as well as the proliferation of malware and viruses is an example of the insecurity that is a result of a computers administrator having the technical ability to downgrade his OS software.
I mention linux because he was using PC OS's as an example, and Linux allows you not only to downgrade... but rewrite the bootloader. Or use a different bootloader. You bootloader can boot securely with UEFI, or you can just use BIOS. All this insecurity, but virtually no viruses, and very few security issues.
Why would you want to downgrade openssl? I wouldn't. I probably wouldn't flash back to an earlier version of android either... I keep my system pretty damn up to date. The point is more that his assertion that MS and Windows proves that being able to downgrade creates inherent security issues doesn't really hold up when you look at other systems that provide even more freedom.
samwathegreat said:
You can "buy" or "not buy" whatever you want....
Click to expand...
Click to collapse
I know, and that is why I want to understand what it is I would be buying.
AGISCI said:
Because even though the patition file and bootloader are included in the archive, they fail to flash because they have a lower version than what is installed.
Click to expand...
Click to collapse
I guess this is the part that we are not understanding. Perhaps because I don't understand enough and have not looked through decompressed recovery images enough... but basically the issue is that Motorola is bricking the device, rather then letting it be downgraded to an potentially insecure image. I am guessing then this is a soft brick?
Does recovery not have the ability to re-write the partition table though? Is there no partition table information in this recovery image? I get that the stock recovery would not allow it, but wouldn't a developer edition user be able to flash a custom recovery that wouldn't have issues flashing the partition table. Don't TWRP or CWM, ect do this?
I guess then that is where the trust zone comes in...
scryan said:
The linux reference was in direct reply to the quote above it that was making the argument that the PC anti-virus industry as well as the proliferation of malware and viruses is an example of the insecurity that is a result of a computers administrator having the technical ability to downgrade his OS software.
I mention linux because he was using PC OS's as an example, and Linux allows you not only to downgrade... but rewrite the bootloader. Or use a different bootloader. You bootloader can boot securely with UEFI, or you can just use BIOS. All this insecurity, but virtually no viruses, and very few security issues.
Why would you want to downgrade openssl? I wouldn't. I probably wouldn't flash back to an earlier version of android either... I keep my system pretty damn up to date. The point is more that his assertion that MS and Windows proves that being able to downgrade creates inherent security issues doesn't really hold up when you look at other systems that provide even more freedom.
I know, and that is why I want to understand what it is I would be buying.
I guess this is the part that we are not understanding. Perhaps because I don't understand enough and have not looked through decompressed recovery images enough... but basically the issue is that Motorola is bricking the device, rather then letting it be downgraded to an potentially insecure image. I am guessing then this is a soft brick?
Does recovery not have the ability to re-write the partition table though? Is there no partition table information in this recovery image? I get that the stock recovery would not allow it, but wouldn't a developer edition user be able to flash a custom recovery that wouldn't have issues flashing the partition table. Don't TWRP or CWM, ect do this?
I guess then that is where the trust zone comes in...
Click to expand...
Click to collapse
The custom recoveries don't flash gpt.bin nor motoboot.img so using a custom recovery it's impossible to correctly flash a Moto X. You MUST use stock recovery with a Moto X. The problem isn't that it causes a brick by flashing an old version. The problem is that a brick happens the next time you do an OTA update. When the OTA update occurs there is a mismatched partion table and bootloader, so it ends up causing a brick.
The developer edition and the standard moto x are 100% identical. They only difference is that you don't void the warranty when you unlock the bootloader on the dev edition, however with the non dev edition your warranty is voided. So the same problem with the partition table and the bootloader ALSO apply to the developer edition as well.
AGISCI said:
The custom recoveries don't flash gpt.bin nor motoboot.img so using a custom recovery it's impossible to correctly flash a Moto X. You MUST use stock recovery with a Moto X. The problem isn't that it causes a brick by flashing an old version. The problem is that a brick happens the next time you do an OTA update. When the OTA update occurs there is a mismatched partion table and bootloader, so it ends up causing a brick.
The developer edition and the standard moto x are 100% identical. They only difference is that you don't void the warranty when you unlock the bootloader on the dev edition, however with the non dev edition your warranty is voided. So the same problem with the partition table and the bootloader ALSO apply to the developer edition as well.
Click to expand...
Click to collapse
Well said :good:
Still the answer is security.
So upgrade as Moto intended & do not downgrade!
---------- Post added at 07:37 PM ---------- Previous post was at 07:30 PM ----------
scryan said:
Is there no partition table information in this recovery image? I get that the stock recovery would not allow it, but wouldn't a developer edition user be able to flash a custom recovery that wouldn't have issues flashing the partition table. Don't TWRP or CWM, ect do this?
Click to expand...
Click to collapse
Our recovery devs never restore such partitions or boot loader elements.
scryan said:
The linux reference was in direct reply to the quote above it that was making the argument that the PC anti-virus industry as well as the proliferation of malware and viruses is an example of the insecurity that is a result of a computers administrator having the technical ability to downgrade his OS software.
I mention linux because he was using PC OS's as an example, and Linux allows you not only to downgrade... but rewrite the bootloader. Or use a different bootloader. You bootloader can boot securely with UEFI, or you can just use BIOS. All this insecurity, but virtually no viruses, and very few security issues.
Why would you want to downgrade openssl? I wouldn't. I probably wouldn't flash back to an earlier version of android either... I keep my system pretty damn up to date. The point is more that his assertion that MS and Windows proves that being able to downgrade creates inherent security issues doesn't really hold up when you look at other systems that provide even more freedom.
I know, and that is why I want to understand what it is I would be buying.
I guess this is the part that we are not understanding. Perhaps because I don't understand enough and have not looked through decompressed recovery images enough... but basically the issue is that Motorola is bricking the device, rather then letting it be downgraded to an potentially insecure image. I am guessing then this is a soft brick?
Does recovery not have the ability to re-write the partition table though? Is there no partition table information in this recovery image? I get that the stock recovery would not allow it, but wouldn't a developer edition user be able to flash a custom recovery that wouldn't have issues flashing the partition table. Don't TWRP or CWM, ect do this?
I guess then that is where the trust zone comes in...
Click to expand...
Click to collapse
Smh I normally don't chime into these threads but I had to, you can't downgrade the bootloader because of security/compatibility plan and simple. It's the same concept as why you can't downgrade most PC's bios, if there is a flaw found in the system as a whole, then they don't want you to downgrade to that version. A lot of the times when people brick their device trying to downgrade is because it will flash, but because an efuse was blown when it was upgraded the downgraded version will not boot. Yes the recovery can technically rewrite those partitions but again because the efuse was blown it will not boot. Also yes being able to downgrade on any system Windows, Linux, Unix, IOS, Xbox, PS, etc are causes to security issues. If you can downgrade a system to a vulnerable version, it is then by definition less secure, no matter how you try to spin it. Take the futex vulnerability which affected most linux kernels from the past 5 years, so why would any desktop linux user ever want to downgrade to a vulnerable kernel? They wouldn't but if the end user isn't knowledgeable of the vulnerability they wouldn't know that downgrading makes them vulnerable. So since phones are used by so many people who are not knowledgeable of vulnerabilities, why would you want to give them the opportunity to downgrade themselves to a vulnerable OS?
Appreciate the info given... I don't want to downgrade, I am not trying to downgrade, I understand why its a bad idea, ect...
My view point was more questioning the insistence that it being technically possible to downgrade creates a security flaw on a machine that is kept up to date by a responsible individual. Unless we are trying to speak more abstractly about that fact that given someone the opportunity to make a mistake makes it more likely for one to occur, I don't think that security threat exists until you actually use that ability to downgrade to something with a flaw.
I guess then it comes down to personal viewpoint of do I want my phone to brick it self to protect me from myself and like sam said, you choose to go elsewhere... But then that is somewhat what I am trying to figure out. Even though its not something I would probably ever have to deal with, I don't like the idea... But "bricking" can be such a vague term with manufacturer specific recovery tools and "different levels of bricking".
Just trying to understand how what and when actually happens. I probably need to read some more of the recovery threads, and I have been looking through old threads here while considering VZ dev moto X and waiting for the x + 1 announcement, but I figured I would jump on the thread while it was here.
I understand keeping it simple because its generally a bad idea all around, and its just best not to confuse things... but its been hard to find deeper discussion or information then the general warnings. A bit of a better picture from this thread though.
aviwdoowks said:
Still the answer is security.
So upgrade as Moto intended & do not downgrade!
---------- Post added at 07:37 PM ---------- Previous post was at 07:30 PM ----------
Our recovery devs never restore such partitions or boot loader elements.
Click to expand...
Click to collapse
By "Our recovery devs" do you mean the ones doing the moto specific stuff? Do you know if this Is typical of the custom recoveries for other devices?
@scryan
I know far less then other posters, but yes android recoveries are all very similar in that regard.
scryan said:
Appreciate the info given... I don't want to downgrade, I am not trying to downgrade, I understand why its a bad idea, ect...
My view point was more questioning the insistence that it being technically possible to downgrade creates a security flaw on a machine that is kept up to date by a responsible individual. Unless we are trying to speak more abstractly about that fact that given someone the opportunity to make a mistake makes it more likely for one to occur, I don't think that security threat exists until you actually use that ability to downgrade to something with a flaw.
I guess then it comes down to personal viewpoint of do I want my phone to brick it self to protect me from myself and like sam said, you choose to go elsewhere... But then that is somewhat what I am trying to figure out. Even though its not something I would probably ever have to deal with, I don't like the idea... But "bricking" can be such a vague term with manufacturer specific recovery tools and "different levels of bricking".
Just trying to understand how what and when actually happens. I probably need to read some more of the recovery threads, and I have been looking through old threads here while considering VZ dev moto X and waiting for the x + 1 announcement, but I figured I would jump on the thread while it was here.
I understand keeping it simple because its generally a bad idea all around, and its just best not to confuse things... but its been hard to find deeper discussion or information then the general warnings. A bit of a better picture from this thread though.
Click to expand...
Click to collapse
The thing is you keep looking at it from a PC point of view, where you basically have full control over the software and hardware. Phones have much tighter restrictions on them from carriers, fcc, etc they're not personal computers. So the reason they make it where you can't downgrade the bootloader is because that's what controls the restriction on downgrading any other partition on the device.
So with the Moto X's 4.4.4 update they probably blew an efuse, so users with a locked device can't downgrade. This is done because with locked devices they can only flash signed kernels, so by blowing the efuse they can't downgrade to the vulnerable 4.4.2 and below kernel even though it is signed correctly. This is because lets say a malicious app was able to get on a device that had the ability to downgrade say back to 4.2.2. That app could flash the older vulnerable signed kernel to the recovery partition, to disable write protection gain more control over the phone etc, without the users knowledge. Now that is a stretch and probably will never happen but that doesn't mean the threat isn't there, and hackers are very creative at deploying malicious attacks. So by updating the bootloader and blowing an efuse the older vulnerable kernels can't be flashed. Now this is all negated if you're unlocked of course, but if you don't want to ever worry about this issue don't update your bootloader. This is not recommended but I've mentioned it several times on this forum I haven't updated my X's bootloader since I bought it, it's still running the factory 4.2.2 bootloader, running 4.4.4 with no problem.
The other thing you're missing is we're technically not supposed to have the ability to restore our phones, except for the developer edition of course. The fastboot restore files are leaked not released to the public, they are designed for use when phones are returned to be refurbished. So they don't want the phones that are being refurbished to be flashed back to an older version, they want it to be refurbished and the latest software version flashed to it.
iKrYpToNiTe said:
The other thing you're missing is we're technically not supposed to have the ability to restore our phones, except for the developer edition of course. The fastboot restore files are leaked not released to the public, they are designed for use when phones are returned to be refurbished. So they don't want the phones that are being refurbished to be flashed back to an older version, they want it to be refurbished and the latest software version flashed to it.
Click to expand...
Click to collapse
A bit selfish, and perhaps lazy of me but I am only really here talking about the developer version, I just haven't bothered to write the full "verizon developer edition " every time (most of this is research for next phone, which will be developer handset)... To me, obviously a locked phone is going to have weird restrictions and hacked together paths to getting things done, your not supposed to have admin rights...(yeah, maybe I do look at it too much as a computer. Mostly because I am annoyed the differences seem intentionally imposed). But when I pay outright for a device so that I can own it and have full administrative control... anyways, thats a different more philosophical discussion. The point is I have been talking about an unlocked device using third party software where possible.
Either way, appreciate the reply. I have a better understanding of the issue... Though coming from an S4 it still seems weird that MDK*/developer phones don't seem to have the same issues/warnings. It would seem however that the difference may be that MDK/dev owners only use kernels/roms prepared for their devices and do not update the bootloader. I suppose if more people in the Moto X community were worried about maintaining the ability to downgrade an unlocked device it would be technically possible to upgrade in a way that could be easily reversed, similar to the S4.
(*MDK was the first VZ S4 firmware, and the only one that has a released exploit to allow for a full custom recover. Later locked firmwares must rely on safestrap)
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.
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
jsmithfms said:
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
Click to expand...
Click to collapse
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
KennyG123 said:
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
Click to expand...
Click to collapse
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Honestly for the time being I wouldn't bother with ROMS for that Device and carrier at the moment. Especially being that its someone elses device. Towelroot should be a good start. If Im not mistaken I don't think its supposed to trip knox.
Sent from my HTCEVODesign4G using XDA Free mobile app
jsmithfms said:
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Click to expand...
Click to collapse
This is the riddle of the Sphinx my friend. I am sure the super devs have tried their best so far to crack it. It has been an ongoing effort to make phones more and more secure, not against the amateur developers and rooters, but against the hackers. These smartphones are now our personal computers, diaries, personal assistants, financial operator, and more. They basically are a person's (and business's) life. AT&T and Verizon have taken the big steps to appeal to the Exchange clients, corporate, government and military contracts. Even the general public want to know their phone is secure. This is what keeps me stuck on the Sprint network.
Have you tried Kingroot?
I successfully rooted my wife's AT&T S4 on OC3 lollipop (supposedly unrootable) with the desktop version. Mobile version didn't work but desktop did without a hiccup. Maybe it'll work on the S5.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
S5 on lollipop has a new nasty boot loader.... it was a miracle on its own that they ever came up with safestrap to duck the boot loader on earlier versions of android