the guy who unlocked the bootloader on Verizon's s5 variant has released a document detailing what I believe is the procedure. Could this open the door for ATT's variant to be unlocked?
https://twitter.com/firewaterdevs/status/713906161834192896
http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf
sensei22 said:
the guy who unlocked the bootloader on Verizon's s5 variant has released a document detailing what I believe is the procedure. Could this open the door for ATT's variant to be unlocked?
https://twitter.com/firewaterdevs/status/713906161834192896
http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf
Click to expand...
Click to collapse
Possibly, based on what I read from it though it needs the string from the dev-edition device, they have that with the Verizon version so it's easy to get, we only have the one, so I think(speculation) it would be trivial at best to repeat this in our model since we don't even know what to set the CID to to make it reflect that of the 'dev edition', I don't think we're getting a towelroot from this at least[emoji14]
Sent from my SAMSUNG-SM-G900A using Tapatalk
I'm going to take a guess that the Verizon and AT&T phones are both unlockable via the same method. I don't even know how to run Samdunk.. Phone or PC? (Can't be Phone if we have no root access :/)
this really seems promising, i still love my s5 and would like to have the bootloader unlocked at some point.
I wouldn't get your hopes up. That unlock requires root which means anyone on 5.0 or above already is SOL, even IF that method worked on AT&T.
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Guicrith said:
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Click to expand...
Click to collapse
My att s5 has 15 for the first 2 digits of the Cid.
Guicrith said:
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Click to expand...
Click to collapse
Mine is 15, I may be willing to be the guinea pig for this as long as it's not a 100% brick. I'm not entirely sure about the tmo s5 simply having the same hardware will make it work, if something like that was the case why did Verizon folks have to wait for someone with the dev Verizon s5 to upload their aboot?
Sent from my SAMSUNG-SM-G900A using Tapatalk
Anyone here willing to risk bricking their device with a 15 series chip pm me!
I saw on a thread maybe the Verizon s5 bootloader unlocking thread a post about copying your original boot chain to an SD card so incase you brick you can still boot the original boot chain off of your SD. Apparently your SD has to be class 10. Just more food for thought.
How do I check my cid? I'm tempted to test as I have the S7 now. But if this works, I may very well return the S7 due to locked bootloader.
TehPirate_ said:
How do I check my cid? I'm tempted to test as I have the S7 now. But if this works, I may very well return the S7 due to locked bootloader.
Click to expand...
Click to collapse
Brickbug emmc from play store. Still not clear if we can make it work, it should and can, but I think we're missing the att 'dev edition'(maybe factory has it with this?) aboot as just using the Verizon one doesn't seem to work.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
Brickbug emmc from play store. Still not clear if we can make it work, it should and can, but I think we're missing the att 'dev edition'(maybe factory has it with this?) aboot as just using the Verizon one doesn't seem to work.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Shame, mines Toshiba (11)
I just want to let everyone know that I've been involved with the thread over at Verizon and guinea pigged for us. I do have an active, however that shouldn't matter. At the moment, you can run both methods and it will appear to be successful, even changing the Cid, but it doesn't unlock the bootloader.
So for now, we're out of luck.
N4styN1ghtm4r3 said:
I just want to let everyone know that I've been involved with the thread over at Verizon and guinea pigged for us. I do have an active, however that shouldn't matter. At the moment, you can run both methods and it will appear to be successful, even changing the Cid, but it doesn't unlock the bootloader.
So for now, we're out of luck.
Click to expand...
Click to collapse
Damn, I was hoping this would pan out as I have a CID that starts with 15. Checked yesterday when advised in the TMS5 3.0 thread. I got this s5 from Samsung insights so I was hoping that'd help but it's At&t branded with locked bootloader. Waiting patiently for an option to unlock bootloader as I don't plan to get a new phone anytime soon.
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
joshua14 said:
Damn, I was hoping this would pan out as I have a CID that starts with 15. Checked yesterday when advised in the TMS5 3.0 thread. I got this s5 from Samsung insights so I was hoping that'd help but it's At&t branded with locked bootloader. Waiting patiently for an option to unlock bootloader as I don't plan to get a new phone anytime soon.
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
Click to expand...
Click to collapse
If you're comfortable doing this kind of stuff, then you can try without risking anything. Nobody with an original s5 has tried it, only me, but again, mine is an active. That may or may not be the reason it didn't work for me, but if somebody with an original s5 wants to try, that would give us a definitive answer.
I did both methods and everything went fine, with no errors. It simply didn't unlock. So feel free to give it a shot, you'll just have to restore your old Cid if it fails, which is no big deal. The only thing I'd give a heads up on, is both methods erase your SD card, so use a spare SD card or back up your files from it somewhere else.
Good luck if you try!!
N4styN1ghtm4r3 said:
If you're comfortable doing this kind of stuff, then you can try without risking anything. Nobody with an original s5 has tried it, only me, but again, mine is an active. That may or may not be the reason it didn't work for me, but if somebody with an original s5 wants to try, that would give us a definitive answer.
I did both methods and everything went fine, with no errors. It simply didn't unlock. So feel free to give it a shot, you'll just have to restore your old Cid if it fails, which is no big deal. The only thing I'd give a heads up on, is both methods erase your SD card, so use a spare SD card or back up your files from it somewhere else.
Good luck if you try!!
Click to expand...
Click to collapse
This will be something to try for the weekend. I have backups for both SS and FF so as long as I don't risk full bricking then I'm game. I have a few spare sd cards too. I never took any OTA updates, the first one that tried getting pushed on me while still within the 6 month insights program I rooted with TowelRoot and froze with TB. Other than that I didn't do much else until more recently to go to Muniz_ri 5.0 keeproot and then to TMS5-3.0-TMBUILD. I was hoping of convincing At&t to unlock the bootloader along with the sim unlock since they don't have any rights to this phone. I still have my Next plan s5 thru them so I can toy with this one, just don't want to end up completely bricking either. I have 2 S3 that I put full custom CM builds on for the kids to play with, just turned off root. Lol
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
joshua14 said:
This will be something to try for the weekend. I have backups for both SS and FF so as long as I don't risk full bricking then I'm game. I have a few spare sd cards too. I never took any OTA updates, the first one that tried getting pushed on me while still within the 6 month insights program I rooted with TowelRoot and froze with TB. Other than that I didn't do much else until more recently to go to Muniz_ri 5.0 keeproot and then to TMS5-3.0-TMBUILD. I was hoping of convincing At&t to unlock the bootloader along with the sim unlock since they don't have any rights to this phone. I still have my Next plan s5 thru them so I can toy with this one, just don't want to end up completely bricking either. I have 2 S3 that I put full custom CM builds on for the kids to play with, just turned off root. Lol
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
Click to expand...
Click to collapse
Yea like I said, as long as you follow the steps closely, there isn't a chance of bricking, it just won't unlock. Let us know when you give it a shot!
Still don't work as of yet...maybe never. The main thread on this is here:
http://forum.xda-developers.com/ver...locking-galaxys-s5-bootloader-t3337909/page77
samccfl99 said:
Still don't work as of yet...maybe never. The main thread on this is here:
http://forum.xda-developers.com/ver...locking-galaxys-s5-bootloader-t3337909/page77
Click to expand...
Click to collapse
It's likely to be never unless we get the proper CID, which as about a needle in a haystack to guess as the bootloader key.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Related
I've searched high and low for a root for my new galaxy note 3. I've seen somethings say the las vegas one or whatever but it couldn't be done on 4.4.2 kitkat. I've seen something about kingo. Which is the best method to root and unlock my boot loader so that i can flash roms.
Samsung galaxy note 3
Android version 4.4.2 kitkat
model- SM-n900a
Thank you in advance for your help! :good::laugh:
No rooting yet and there hasn't been unlocked bootloaders on the AT&T Note 3 yet.
Sent from my SAMSUNG-SM-N900A using Tapatalk
really???? bummer
A root method for 4.4.2 will be found eventually, so try to tough it out until its found. Not having root sucks, but it will hopefully come soon. An unlocked bootloader will most likely never happen unless someone holds the CEO of AT&T hostage (any volunteers?), so no custom kernels or AOSP for us unless someone gets Loki working.
Face_Plant said:
A root method for 4.4.2 will be found eventually, so try to tough it out until its found. Not having root sucks, but it will hopefully come soon. An unlocked bootloader will most likely never happen unless someone holds the CEO of AT&T hostage (any volunteers?), so no custom kernels or AOSP for us unless someone gets Loki working.
Click to expand...
Click to collapse
I'm glad your that positive that a root method for 4.4.2 will be found, however (not to be a negative nelly) KK has some security features that Google has added, that would make it even harder to achieve root. That, with the added AT&T "updated" locked bootloader, would make it almost impossible to obtain root. Then, adding salt to the wound, the new S5 has just been released, so every DEV that's worth their salt would want to hop on the new tech bandwagon and tackle something new.
I personally don't care about root. I never rooted my Note 3 until the OTA update, which kept getting stuck at 27%. I followed the instructions to obtain root, installed the OTA update, but FORGOT TO UNROOT my phone!!! That stupid SU app is in the way, and I can't uninstall it! When it comes time for me to upgrade my Note3 to a Note4, anyone can simply look in my app draw and see SU app. Even ISIS wont work because it thinks my phone is rooted. I want to simply root my phone, delete that SU app, and un-root. It's that simple. If I can do this using ADB, i'll try it in a heartbeat.
awe that sucks..hopefully someone comes up with some thing soon. Thanks for your replies. When they do come up with a root method would we still be able to flash roms being that our bootloader is locked?
dunn816 said:
I've searched high and low for a root for my new galaxy note 3. I've seen somethings say the las vegas one or whatever but it couldn't be done on 4.4.2 kitkat. I've seen something about kingo. Which is the best method to root and unlock my boot loader so that i can flash roms.
Samsung galaxy note 3
Android version 4.4.2 kitkat
model- SM-n900a
Thank you in advance for your help! :good::laugh:
Click to expand...
Click to collapse
At this time there is no way to root KitKat, period, either with De La Vega, or Kingo. In addition, the bootloaders are totally locked down. There currently is a petition here, to see if we can get AT&T to unlock them
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
dunn816 said:
awe that sucks..hopefully someone comes up with some thing soon. Thanks for your replies. When they do come up with a root method would we still be able to flash roms being that our bootloader is locked?
Click to expand...
Click to collapse
Search through the forum, there is a way to flash custom ROMS, just not in the typical way
lawalty said:
I'm glad your that positive that a root method for 4.4.2 will be found, however (not to be a negative nelly) KK has some security features that Google has added, that would make it even harder to achieve root. That, with the added AT&T "updated" locked bootloader, would make it almost impossible to obtain root. Then, adding salt to the wound, the new S5 has just been released, so every DEV that's worth their salt would want to hop on the new tech bandwagon and tackle something new.
Click to expand...
Click to collapse
It still doesn't hurt to look up. The S5 is locked down tight just like the Note 3 so I don't see why devs would dump the Note 3 just to work on another locked device. The Note 3 is still relatively new and pretty popular so I doubt it's going to be given up on just yet.
Im just wondering because I have not seen or heard anything in a while.
note crazy said:
Im just wondering because I have not seen or heard anything in a while.
Click to expand...
Click to collapse
May be there is no point any more to do this. Samsung will issue a new update with a patched bootloader and the custom one won't work again. I read on "General Note 3" forum even "towelroot" doesn't work after official update to 4.4.3.
jondoe27 said:
May be there is no point any more to do this. Samsung will issue a new update with a patched bootloader and the custom one won't work again. I read on "General Note 3" forum even "towelroot" doesn't work after official update to 4.4.3.
Click to expand...
Click to collapse
Yes true but if you do not take the update you will be fine I would think most people that have got root will not give it up without a fight I feel as if there is a point to unlock the bootloader because its not there phone its are phone and I want to do whatever I want with a phone I bought I froze the ota updater with titanium back up i will no long allow att to tell me what I can do with my phone . They cant patch something I dont allow and thats that
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
dont mess with itttt leave it until someone replies we need to extract your firmware, hold onto it if you not messing around, im not experinced enough but someone will pm you im sure
MGArcher007 said:
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
Click to expand...
Click to collapse
MGArcher007 said:
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=54642044
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
Apparently there are many different circumstances under which the splash screen says custom, which have nothing to do with the bootloader being locked or unlocked. I seem to recall it showing up for people when they just switched to ART runtime, and in some cases it didn't even go back when they switched back to Dalvik. Many of the methods for making this not appear just involve cosmetically hiding it, not actually cleaning up whatever it is that is being detected.
What I wouldn't give to have this bootloader unlocked
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
If there is a dev that wants a s5 to experiment with to get the bootloader unlocked I'll be happy to donate my s5 if I can get it back after finding an exploit . But the dev needs to come with unanimous recommendation by the devs. Let me know I can still use my s3.
Sent from my SAMSUNG-SM-T537A using XDA Free mobile app
Aw man, I was really hoping that the bootloader just somehow magically unlocked itself. Wishful thinking, I suppose. I love my S5 Active, I just wish I had a little more freedom with customizing it in ways like I could my S3.
I wonder if this is a result of Knox being disabled during the root... Either way, I hope I'll still receive OTA updates for things like 4.4.4 if they ever decide to release it, and eventually Android L.
For now, I can't complain -- surprisingly enough, even without root, my Xposed Framework still functions very well and I can still make backend and UI changes in GravityBox.
Regardless, thanks for all the replies, guys! I probably won't mess with trying to fix it unless they come out with an OTA update that I can't get as a result of this.
MGArcher007 said:
Aw man, I was really hoping that the bootloader just somehow magically unlocked itself. Wishful thinking, I suppose. I love my S5 Active, I just wish I had a little more freedom with customizing it in ways like I could my S3.
I wonder if this is a result of Knox being disabled during the root... Either way, I hope I'll still receive OTA updates for things like 4.4.4 if they ever decide to release it, and eventually Android L.
For now, I can't complain -- surprisingly enough, even without root, my Xposed Framework still functions very well and I can still make backend and UI changes in GravityBox.
Regardless, thanks for all the replies, guys! I probably won't mess with trying to fix it unless they come out with an OTA update that I can't get as a result of this.
Click to expand...
Click to collapse
Sadly. ...We may never see the bootloader unlocked without a factory method...
It's encryption prevents us from even being able to open it into a usable state...
We need either an encryption key....or a new bootloader entirely...
Not happening any time soon....g
Someone says that mofo cannot be used under android 5.1, because verizon added patch against mofo in the update package. Is this true?
If this be true, seems that versizon has little willingness to open the bootloader.
when the upgrading of lollipop was delayed on June 10, there was rumor saying that verizon might open the bootloader. Now I will say "wholy ****"
computerfreek274 says he's working to get a rooted image of version 5.1. Bless him!
manofwind said:
Someone says that mofo cannot be used under android 5.1, because verizon added patch against mofo in the update package. Is this true?
If this be true, seems that versizon has little willingness to open the bootloader.
when the upgrading of lollipop was delayed on June 10, there was rumor saying that verizon might open the bootloader. Now I will say "wholy ****"
computerfreek274 says he's working to get a rooted image of version 5.1. Bless him!
Click to expand...
Click to collapse
1: Yes mofo, in its current state will not get you root on LP, and yes, AFAIK, the mofo exploit was patched.
2: Yes verizon has no desire to give you bootloader access.. I cant source that but if you find me something opposing it... I will be grateful.
3: The rumors were false. There was no verizon unlock in any capacity.
4. (this is more my opinion) Compfreak was building customized images that can be flashed via MOFO based on what people wanted.. tethering/xposed. I hope he/she has the ability to find a crack through 5.1 but ultimately it was @maiko1 effort. Root on LP will be a wholly different story.
So no root yet or ever for LP on turbo?
raze5115 said:
So no root yet or ever for LP on turbo?
Click to expand...
Click to collapse
No for yet; no one can be absolutely certain if root will be achieved before most of us move on to another phone in a year or two.
raze5115 said:
So no root yet or ever for LP on turbo?
Click to expand...
Click to collapse
Only time will tell
ntxct said:
1: Yes mofo, in its current state will not get you root on LP, and yes, AFAIK, the mofo exploit was patched.
2: Yes verizon has no desire to give you bootloader access.. I cant source that but if you find me something opposing it... I will be grateful.
3: The rumors were false. There was no verizon unlock in any capacity.
4. (this is more my opinion) Compfreak was building customized images that can be flashed via MOFO based on what people wanted.. tethering/xposed. I hope he/she has the ability to find a crack through 5.1 but ultimately it was @maiko1 effort. Root on LP will be a wholly different story.
Click to expand...
Click to collapse
just upgraded yesterday. i have the option to unlock the bootloader in 5.1. when you enable it it throws all kinds of warnings about your system not being protected.
maybe it is really unlocked with this option. is there any way i can test this?
LP is rooted if you did not take the OTA update look for my lollipop forum. As I had told everyone not to update OTA or you will be locked and no mofo. If you Are still on 4.4.4 head on over to forum and flash a nice rooted copy of lollipop.
If you did take the OTA update well you know you are not going to be getting root or unlocked. I do not think you will ever get it. Sorry.
computerfreek274 said:
LP is rooted if you did not take the OTA update look for my lollipop forum. As I had told everyone not to update OTA or you will be locked and no mofo. If you Are still on 4.4.4 head on over to forum and flash a nice rooted copy of lollipop.
If you did take the OTA update well you know you are not going to be getting root or unlocked. I do not think you will ever get it. Sorry.
Click to expand...
Click to collapse
You have to think there is some internal memo with the execs at Verizon...
"You know, Google added this 'Unlock Bootloader' option to the menu's in 5.1 Should we have our engineers remove it?
Remove it?! Are you kidding, you know how many people will take the upgrade thinking they can actually use that feature?! Find that hole in mofo and patch it.
Sir, finding the hole in mofo is taking us a while, its only April and our guys say to patch it will push back 5.1 to July.
Yes. Do it."
Lets be happy none of them got the idea that every time someone tries the unlock button it adds $10 to their bill in "network security."
Your best bet is probably trading your Turbo for someone else's who is still on 4.4.4.
I don't know why people take OTAs if they want root.
cgreen36352 said:
just upgraded yesterday. i have the option to unlock the bootloader in 5.1. when you enable it it throws all kinds of warnings about your system not being protected.
maybe it is really unlocked with this option. is there any way i can test this?
Click to expand...
Click to collapse
All that does is enable the OEM unlock command to be used IF you have the unlock code for your phone. You have no way of getting the unlock code for your phone.
If the Enable OEM unlock is not turned on, even if you have the unlock code for your device, you can't unlock it. You have to enable OEM unlock to unlock your phone but simply enabling it won't unlock it - you need the unlock code.
So that's it then.... Turbo development is dead. KK was rooted, and screw LP? That's unfortunate...
irish_711 said:
So that's it then.... Turbo development is dead. KK was rooted, and screw LP? That's unfortunate...
Click to expand...
Click to collapse
... No, that's not what anyone said. WTF is wrong with you people that if it's not 'done right now' that it's never going to be done. Team Ninja is working on unlocking the Turbo's bootloader, but absolutely no one knows how long it will be even team ninja. It's not like they just sit down and go "Lets apply the 'super secret' root method to this phone." It takes a good amount of work and luck to find a method that works to root the new devices because of how far android has come in security. Saying stuff like "development is dead" it's an insult to the people that are spending time working on it.
I think, root droid turbo is very difficult work. Maybe we never root it successfully. I will sell my droid turbo and by Samsung galaxy S6 in next month if i can't root it.
bahuy2003 said:
I think, root droid turbo is very difficult work. Maybe we never root it successfully. I will sell my droid turbo and by Samsung galaxy S6 in next month if i can't root it.
Click to expand...
Click to collapse
People are dumb...
Sent from my XT1254 using Tapatalk
guys ive done a lil looking into this update sadly i was one to update it to 5.1 shame on me but the whole non-downgrading function mite be a joke ive heard rumors of a guy downgrading from 5.1 to 4.4.4 using root junkys unbricking method now at first youll get a soft brick (as to be expected) but the XT1254 originally comes with 4.4.4 and i dont see why after this soft brick why you couldnt just run the flash thru fastboot again and have it work if anyone wants to try it heres the source of the info last comment on the page if it works then were good also idk if needed but it mite help to unlock the BL thru ADB
ps all i did was google droid turbo 5.1 downgrade to 4.4.4 wont let me post links so message me for screenshots
let me know what you find out good luck -Shifty
You can't downgrade the kernel.
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
You can't downgrade the kernel.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
ok so whats the next step there has to be away to get root ive been able to get superuser and everything needed pushed to the phone or should i say what would i have to play with to possibly get root i have linux so i could get it if anyone knows where i should start looking the thing is im not very familiar with the lollipop update :/
---------- Post added at 08:20 PM ---------- Previous post was at 08:10 PM ----------
bahuy2003 said:
I think, root droid turbo is very difficult work. Maybe we never root it successfully. I will sell my droid turbo and by Samsung galaxy S6 in next month if i can't root it.
Click to expand...
Click to collapse
the thing is that its not the phone its self its the firmware the S6 also doesnt have root for 5.1 plus youll have the KNOX counter plus motorola is more rooting friendly than samsung so stick with your droid trust me there are enough people working on the root access someone will get it just give it time
Shiftydogit said:
ok so whats the next step there has to be away to get root ive been able to get superuser and everything needed pushed to the phone...
Click to expand...
Click to collapse
So it may be late and I may be pessimistic about it but the next step here... search ebay or those swappa sites for a 4.4.4 Turbo., those can still be rooted with MoFo and then upgraded to 5.1. It appears replacements Turbos are being shipped with 5.1 now, and while there was hype at the end of August about a group unlocking the bootloader...it still hasn't come (not to say it won't but......) the fact that a Turbo 2 is coming soon means that at this point, it's a game of just seeing if that bootloader unlock will happen before the drop of the Turbo 2.... Once that happens the game basically starts over, new crews will work on unlocking/rooting that and who's to say that won't take 1-36 months? Who knows if those people working on the Turbo 2 were the ones working on the Turbo 1.. and since they don't tend to announce progress, we'll never really know how close they might have gotten before giving up and moving on to the latest flagship.
The best advice I can give is that on your next phone, whatever manufacturer or carrier or inkling you have to update.. before you do anything.. hell, if possible, before you buy, check out that phone's xda forum and see how development is being done. Taking an upgrade all willy-nilly is the first step in being screwed having root.
well with us having fastboot and the OEM unlockbootloader in dev options we can unlock our BLs thru ADB with Fastboot OEM unlock i know it works i got it to work so i dont see why we cant get root
The turbo does not have BL unlock, if it was so simple as using OEM unlock we wouldn't have a bounty out for unlocking the bootloader. If you managed to unlock the bootloader you may have one of the other quark devices not a Droid Turbo.
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