Related
This is my first Android phone i have owned for a few years now and i made the mistake of doing the OTA update to 4.3. I would love to root this phone because that was a big reason why i got it. I hated waiting for a jailbreak for my iPhone and i want a phone that i have control over. is it possible to "downgrade" from the OTA update to the leaked update? or even downgrade back to 4.2.2? I have looked around but cant find anything to helpful for the galaxy s4 active. also reading around multiple people say they end up having issues after downgrading or the KNOX counter going from 0x0 to 0x1, therefore voiding warranty.
RobbieHag said:
This is my first Android phone i have owned for a few years now and i made the mistake of doing the OTA update to 4.3. I would love to root this phone because that was a big reason why i got it. I hated waiting for a jailbreak for my iPhone and i want a phone that i have control over. is it possible to "downgrade" from the OTA update to the leaked update? or even downgrade back to 4.2.2? I have looked around but cant find anything to helpful for the galaxy s4 active. also reading around multiple people say they end up having issues after downgrading or the KNOX counter going from 0x0 to 0x1, therefore voiding warranty.
Click to expand...
Click to collapse
While the OTA upgraded Android to 4.3 it also included a new bootloader. The new bootloader prohibits "downgrading" to a firmware version below ML2. Currently there is no way to downgrade with the locked bootloader. However there is a new thread just started by @TransformixS4 that is looking at injecting root into the ML2 Odin files, so it may be possible in the future to root ML2. There are a couple threads in the regular S4 forums exploring ways to exploit the bootloader and flash custom kernels.
Back to your situation: you're completely stuck. Next time you see there is an update or OTA check XDA before you install it. There are a couple threads that explain the pros and cons of any updates. There is also a thread summarizing all the AT&T i537 firmwares which will be updated in the future and you may find useful.
Devo7v said:
While the OTA upgraded Android to 4.3 it also included a new bootloader. The new bootloader prohibits "downgrading" to a firmware version below ML2. Currently there is no way to downgrade with the locked bootloader. However there is a new thread just started by @TransformixS4 that is looking at injecting root into the ML2 Odin files, so it may be possible in the future to root ML2. There are a couple threads in the regular S4 forums exploring ways to exploit the bootloader and flash custom kernels.
Back to your situation: you're completely stuck. Next time you see there is an update or OTA check XDA before you install it. There are a couple threads that explain the pros and cons of any updates. There is also a thread summarizing all the AT&T i537 firmwares which will be updated in the future and you may find useful.
Click to expand...
Click to collapse
My issue was I kept telling it not to upgrade, and then it went ahead and did it anyway! On 4G, not wifi even. I was so mad when I got home and started reading that all the stuff I downloaded to root it *that day* would no longer work.
Caboose27 said:
My issue was I kept telling it not to upgrade, and then it went ahead and did it anyway! On 4G, not wifi even. I was so mad when I got home and started reading that all the stuff I downloaded to root it *that day* would no longer work.
Click to expand...
Click to collapse
You're only allowed to delay the update 4 or 5 times before it installed automatically. You can prevent it from upgrading in the future by freezing some system apps with Titanium Backup. I don't remember which ones right now, but if you search it's pretty easy to find.
Caboose27 said:
My issue was I kept telling it not to upgrade, and then it went ahead and did it anyway! On 4G, not wifi even. I was so mad when I got home and started reading that all the stuff I downloaded to root it *that day* would no longer work.
Click to expand...
Click to collapse
Just checking, you do have the i537 not i9295, right?
Hey guys, im stuck on deciding whether i should root my note 4 or not. What's really bugging me is that i will trip knox and will it devalue the phone?
Any benefits of rooting it right now? vs nonroot
i've seen some threads of rooting problems with some apps and such and im not sure if i should wait or not. Im coming from a rooted s4 and i kinda miss being rooted. Come on guys post what you think here!
Belongs in the Q&A section
bipoler said:
Belongs in the Q&A section
Click to expand...
Click to collapse
You're right im sorry guys
Any possbility of a mod moving it?
marcustdu said:
Hey guys, im stuck on deciding whether i should root my note 4 or not. What's really bugging me is that i will trip knox and will it devalue the phone?
Any benefits of rooting it right now? vs nonroot
i've seen some threads of rooting problems with some apps and such and im not sure if i should wait or not. Im coming from a rooted s4 and i kinda miss being rooted. Come on guys post what you think here!
Click to expand...
Click to collapse
Root if something you want needs it, otherwise there's not any need. Do you need tomatoes? I dunno.
marcustdu said:
Hey guys, im stuck on deciding whether i should root my note 4 or not. What's really bugging me is that i will trip knox and will it devalue the phone?
Any benefits of rooting it right now? vs nonroot
i've seen some threads of rooting problems with some apps and such and im not sure if i should wait or not. Im coming from a rooted s4 and i kinda miss being rooted. Come on guys post what you think here!
Click to expand...
Click to collapse
As stated above, root if you have the NEED to root. For me, I got plenty. Smoothness, debloating, batterylife, awesome rooted apps out there (I know..only three reasons.) For others, they need a specific app they need to run on their phones and it will need root.
If non of these are an issue to you, do not root. If you cannot think of a reason to root without having the benefit of root vs non root listed out to you, I will advice you do not root because that tells me you actually do not have the need to root. Make sense?
As far as knox is concern...I will say only trip if if you have no need to send it straight to Samsung while your phone is still functioning. I say this because they will send it right back to you. Now if your phone is fried, how will they check exactly if knox is tripped? The carriers do not care, tmobile do not care. Most of the workers think nova is a rooted app. Thats how much they know about root.
You go to a carrier, simply do not give them a reason to think you are rooted. People like to take a phone with custom roms and custom kernels on there...thats not smart. They boot your phone, a message at the top most left of the phone will tell them you are rooted. Always go to the store with stock ^.^
Hope that helps!
I have the Note 4. I root it about 2 weeks later after I got it. My reason: get ride of all the bloat junk that I dont need; now I can write to my SD card; unlimited hotspot; lean machine and good battery life. Its good to have su access.
mgbotoe said:
As stated above, root if you have the NEED to root. For me, I got plenty. Smoothness, debloating, batterylife, awesome rooted apps out there (I know..only three reasons.) For others, they need a specific app they need to run on their phones and it will need root.
If non of these are an issue to you, do not root. If you cannot think of a reason to root without having the benefit of root vs non root listed out to you, I will advice you do not root because that tells me you actually do not have the need to root. Make sense?
As far as knox is concern...I will say only trip if if you have no need to send it straight to Samsung while your phone is still functioning. I say this because they will send it right back to you. Now if your phone is fried, how will they check exactly if knox is tripped? The carriers do not care, tmobile do not care. Most of the workers think nova is a rooted app. Thats how much they know about root.
You go to a carrier, simply do not give them a reason to think you are rooted. People like to take a phone with custom roms and custom kernels on there...thats not smart. They boot your phone, a message at the top most left of the phone will tell them you are rooted. Always go to the store with stock ^.^
Hope that helps!
Click to expand...
Click to collapse
Thank you for your input, yes I do have things such as you listed for rooting! Merry Christmas!
chong67 said:
I have the Note 4. I root it about 2 weeks later after I got it. My reason: get ride of all the bloat junk that I dont need; now I can write to my SD card; unlimited hotspot; lean machine and good battery life. Its good to have su access.
Click to expand...
Click to collapse
Thanks for the response! I think I know what I'm doing now [emoji14]
Merry Christmas!
Im in the same boat, sorta. Ive always rooted. Everything i had, even the old windows phones. This is the longest ive lasted non rooted. Im getting the itch. My question, if i root, flash twrp, does it erase my data? Not a big deal really, but im on level 110 on ea sports king of the course. Would suck to start over.
Sent from my SM-N910T using XDA Free mobile app
donnyp1 said:
Im in the same boat, sorta. Ive always rooted. Everything i had, even the old windows phones. This is the longest ive lasted non rooted. Im getting the itch. My question, if i root, flash twrp, does it erase my data? Not a big deal really, but im on level 110 on ea sports king of the course. Would suck to start over.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Neither rooting nor flashing a recovery will wipe your data. Some phones ship with the unlockable bootloaders and the unlocking process wipes the data (for example, on Google Nexus devices). But the bootloaders on T-Mobile Samsung phones are unlocked by default, so flash away
chenxiaolong said:
Neither rooting nor flashing a recovery will wipe your data. Some phones ship with the unlockable bootloaders and the unlocking process wipes the data (for example, on Google Nexus devices). But the bootloaders on T-Mobile Samsung phones are unlocked by default, so flash away
Click to expand...
Click to collapse
Thanks dude, im on tmobile. Root then backup!
Sent from my SM-N910T using XDA Free mobile app
Its done. I voided it!
Sent from my SM-N910T using XDA Free mobile app
Rooted is the way to go! Only reason I haven't rooted yet is because I'm waiting for Android 5.0 to drop next month hopefully ! Then I will gladly root. Phone is much better when it is under your control.
ROLL THAT SHT, LIGHT THAT SHT. SMOKKKKE THAT SHT
Those of you who rooted the Note 4, can you confirm if root disables:
Private mode - Possible fix (old fix)
S-Health (maybe only if using Xposed) - Possible fix?
Screen Mirroring (wireless) - Possible fix?
Recording calls (?)
I would want to root mainly to gain access to the external SD card, possibility to enable/disable flight mode using profiles and wouldn't mind about OTA ora Knox 0x01.
But it's annoying to lose those functions for me.
Updated previous post with some links to possible fixes.
virtualdj said:
Those of you who rooted the Note 4, can you confirm if root disables:
Private mode - Possible fix?
S-Health (maybe only if using Xposed) - Possible fix?
Screen Mirroring (wireless) - Possible fix?
Recording calls (?)
I would want to root mainly to gain access to the external SD card, possibility to enable/disable flight mode using profiles and wouldn't mind about OTA ora Knox 0x01.
But it's annoying to lose those functions for me.
Click to expand...
Click to collapse
I rooted but on a custom ROM and I have zero issues with private mode or S-health. I guess the issue is when you're only rooted on stock ROM. But apparently there's walkarounds for those issues.
shook187 said:
I rooted but on a custom ROM and I have zero issues with private mode or S-health.
Click to expand...
Click to collapse
Thanks, but actually I was interested on (possible) issues on stock ROM and, most importantly, if the walkarounds really work.
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
How does this affect our device when it gets the lollipop update?
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Since I am running dynamic Kat on stock slot right now, I should be safe from updates for now right?
Waiting to see what happens with all this. I did back up my stock rom to an SD card, so I can restore and unroot etc... to get an update if I choose to later.
muniz_ri said:
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Click to expand...
Click to collapse
was looking for a post like this. well maybe we might get 5.1 in the next few weeks or sooner so i am sure you will give it a try and a good look and hopefully you will have success in attaining root and a good SS. seems like u da man for this...:good::good:
as for 5.1 or a custom rom...well whose to say what that will bring...
will be waiting to see what happens. will check back here when it comes out. i watch for it everyday and as usual, thank you for all your great work!
miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Not necessarily, just because (if) the S5 gets 5.0 does not mean the ability to root will be lost just go check out the Verizon S5 forums you'll see they have a method for rooting with 5.0 that in theory should work for us as well. again it is recomended to remain on a 4.4.x rom until this has been fully evaluated.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
My suggestion would be not to take any updates until the root capabilities have been evaluated.
As always, research goes a long way towards alleviating fears and stopping panic attacks before they happen. be patient there are great devs here give them time to work
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
the att gs5 doesn't seem like it's getting any updates..
wmunn said:
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
Click to expand...
Click to collapse
How are you liking it? I'm seriously thinking about doing the same thing.
I have a coworker that just got the Lollipop update for his Note 3 so that means it will be coming to the S5 very soon!
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
silentscreamz said:
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
Click to expand...
Click to collapse
I used that method as well. Sure, it worked for me, but I came from Dynamic Kat, a well debloated stock rom. Due to this, after installing the update using this method, the built-in apps restore function could not complete due to having all of the useless bloatware back, taking up the extra space I was free to use in Dynamic Kat. Even removing the apps that are safe to remove via Titanium Backup doesn't help because the space is reserved for them. I've also already moved every app that it will allow to move to SD card. I've removed unneeded apps. I've gone through my internal storage to remove any unneeded files.
I've removed most of the apps listed here
This doesn't give me the Bluetooth tether that I used to us for my Gear 1(Running Null Rom). I'd look for an app to cover this but... I can't install anything because I've got no space to do so... I hope a good debloat method comes along soon. I still have root, so I'm hopeful.
Yea, bloatware is ridiculous for this phone. Have you tried the Alliance rom, that is what I run and it's not to bad for bloatware but I have only managed to get 5.6 running. Going to try version 8 today sometime. If you like to customize that is an awesome rom.
Hi folks, new to the S5 forums on here as I just upgraded from my trusty S3 on AT&T. I'm still on the stock 4.4.2 firmware, NG3 build, and I'm wondering if I should just root from here using TowelRoot method or take the 4.4.4 OTA and root from there.
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
SoCalHTCFuze said:
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
Click to expand...
Click to collapse
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
MetalHead66 said:
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
Click to expand...
Click to collapse
You gotta downgrade theres a post on here just type it in the search bar. Pretty easy process
Yes. Follow the 4.4.2 how to root thread, it says that bit still works.
OK thanks a bunch. Getting ready to do that now.
---------- Post added at 03:27 AM ---------- Previous post was at 02:53 AM ----------
Well that was quite easy and I'm a happy camper now! Just had to flash nd3 kernel with odin in order for TR to work then flash my ng3 kernel. So nice to be able to use TiBu. Helium wouldnt install all my apps. Now I can start freezing and uninstalling all the bloatware!
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.
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