Database Develop

root for vzw moto x 4.4.2?

While we wait for real root for 4.4.2...in the meantime, I wouldn't mind having root with write protection upon reboot. Could someone walk me through the process for that? I'm more than happy to reapply any changes when the phone is rebooted (which won't be too often, hopefully)

If you're already on 4.4.2....you can't root. Can't downgrade to do the safe strap method.
If you are on 4.2.2 or 4.4....then read the safe strap thread. Also there's a couple ROMs now that apparently root and disable write protection. But again, if you are already on 4.4.2....you can't do it.

I saw it mentioned in a thread that root could exist but with write protection. Is that not true?

terrorist96 said:
I saw it mentioned in a thread that root could exist but with write protection. Is that not true?
Click to expand...
Click to collapse
You can't root on 4.4.2 period. There's no way. Simple as that.
Sent from my XT1060 using Tapatalk

DroidOnRoids said:
You can't root on 4.4.2 period. There's no way. Simple as that.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Guess I'll just wait

terrorist96 said:
Guess I'll just wait
Click to expand...
Click to collapse
That's the only thing to do. It sucks because I'm stuck too.
Sent from my XT1060 using Tapatalk

terrorist96 said:
I saw it mentioned in a thread that root could exist but with write protection. Is that not true?
Click to expand...
Click to collapse
The only way was to have it on 4.4 before taking ota. I guess root survived with write protection enabled tho.
But already being on 4.4.2.....can't root now.

This is kinda weird. I was talking to Motorola via the help app and the representative was adamant in telling me that I am able to unlock my bootloader on the Verizon version. I even said that xda developers say it cannot be unlocked but he told me it was possible and to try it. He linked me here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Has anyone tried this?

terrorist96 said:
This is kinda weird. I was talking to Motorola via the help app and the representative was adamant in telling me that I am able to unlock my bootloader on the Verizon version. I even said that xda developers say it cannot be unlocked but he told me it was possible and to try it. He linked me here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Has anyone tried this?
Click to expand...
Click to collapse
I think the rep told you wrong. According to this link (found on the page that you linked under the "Find Your Device" section) https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215, it only works with the Verizon Dev Edition. You can give it a go, but it will probably reject the attempt. If Verizon has changed their policy (highly doubtful) a lot of people would be extremely happy. Anyway, give it a shot. The worst that can happen is that it tells you that your device doesn't qualify.

Yeah, I even sent him that page saying that only the sprint, t-mobile and US Cellular versions can be unlocked. But I'll try this tomorrow. Anyone else can feel free to do so as well in the meantime.

kj2112 said:
The only way was to have it on 4.4 before taking ota. I guess root survived with write protection enabled tho.
But already being on 4.4.2.....can't root now.
Click to expand...
Click to collapse
Correct.
If you were on 4.4, you could root and disable write protection. When you took the 4.4.2 OTA, write protection became re-enabled, but you kept root. Of course this meant any changes/installs/etc made to /system and the like since taking 4.4.2 would be lost at power off/on.
Once 4.4.2 is on your phone, you can't root, and you can't disable write protection, unless you have a developer edition, or a carrier edition like Sprint, T-Mobile, etc that Moto gives out the bootloader unlock codes on their web site for. Once you unlock the bootloader you can root and write protection is disabled, and this can be done no matter what rom is on the phone.
The bounty to unlock the bootloader for VZW/ATT (who can't get codes from moto's web site), has continued to grow. No one has found a way. Same with some older Moto's too. Same with the updated GS4 and GS5, and so on.... So the chances of seeing a bootloader unlock hack are fading. Root exploits seem to get patched with each new ROM update (to root 4.4, you had to downgrade and root 4.2.2), so that is getting harder.
To be realistic, the only way to ensure you can have root and write protection disabled is to buy a Developer Edition, or from a carrier that allows you to unlock the bootloader. Yup it can cost more, and you can't customize its look, but its a small trade off if you *NEED* working root no matter what rom comes on your phone. Its a trade off I had to make, but it was easier when I did it as I was paying full price (to keep my unlimited data), and the Dev Edition was the only 32gig option for Verizon at the time.
---------- Post added at 09:46 PM ---------- Previous post was at 09:44 PM ----------
terrorist96 said:
This is kinda weird. I was talking to Motorola via the help app and the representative was adamant in telling me that I am able to unlock my bootloader on the Verizon version. I even said that xda developers say it cannot be unlocked but he told me it was possible and to try it. He linked me here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Has anyone tried this?
Click to expand...
Click to collapse
As @HeroOfTime has said, unless Moto has reversed their course of action, Verizon and ATT non-developer phones can not receive an unlock code via Moto's web site.
That is why there was such a big "to do" about the Chinese site that was selling codes not too long ago. (which has been shut down).
Once you try it. Please let us know. There are MANY who would be very happy if Moto has changed things!!

Well, I tried and got the expected error telling me that my device wasn't eligible. Guess that Motorola rep didn't know what she was talking about. I talked to someone else and they basically confirmed it, saying you can only do it on the Dev Edition on Verizon. :\

I'll just leave this right here.... PLEASE be smart and do not start spamming him with "ETA?" and other b.s. that will make him not want to share it. We are NOT entitled to his work. If he decides to share, he will. Leave it at that.

jimmiet said:
I'll just leave this right here.... PLEASE be smart and do not start spamming him with "ETA?" and other b.s. that will make him not want to share it. We are NOT entitled to his work. If he decides to share, he will. Leave it at that.
Click to expand...
Click to collapse
He's already said that he's not going to release it. Jcase is a lost cause.

Jump on this while you can !! -> http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177

terrorist96 said:
He's already said that he's not going to release it. Jcase is a lost cause.
Click to expand...
Click to collapse
He said on Twitter that it would more than likely be released just not by him.
Sent from my XT1060 using XDA Premium HD app

Well let's hope so.

And then 4.4.3 will come out. Lol

kj2112 said:
And then 4.4.3 will come out. Lol
Click to expand...
Click to collapse
His tweet did say "Don't OTA"

I've been searching for an answer to my problem and this is the best thread I have seen but....I'm a little confused. Here is what I did:
Bought a BOOST Mobile MOTO-G.
I unlocked the bootloader. I can be done on this device.
I flashed CWM from recovery. It worked fine.
From recovery, I flashed the VERIZON 4.4.2 image.
Booted the phone, activated it on PagePlus.
Went back to recovery, flashed SUPERSU. It worked....no errors.
Root checkers say I have root. I cannot use anything that needs root such as Titanium.
I connected the phone and did :
adb shell
getprop ro.boot.write_protect
It returned a 0 (zero)
Does this make sense? I just would like someone to confirm it does. Reading this thread has helped but it is the ZERO write protect thing that is throwing me.
Thanks in advance.

[Q] Unable to update, Software status:Modified

So i keep being prompted to get the new OTA update and whenever i try to download and install it, it reboots goes to the install screen, gets about 1/4 of the way through, says error and then reboots to an update unsuccessful page
After digging around my phone i also noticed it says my software was modified on the status page
But obviously ive never rooted this phone as its pretty much impossible at the moment
Has anyone experienced something similar and found a way to fix it?

did you disable any of the bloat? that might be your issue.....

xbxjunkie said:
did you disable any of the bloat? that might be your issue.....
Click to expand...
Click to collapse
I did! I'll re enable it all and see if it fixes the issue

jaideng123 said:
So i keep being prompted to get the new OTA update and whenever i try to download and install it, it reboots goes to the install screen, gets about 1/4 of the way through, says error and then reboots to an update unsuccessful page
After digging around my phone i also noticed it says my software was modified on the status page
But obviously ive never rooted this phone as its pretty much impossible at the moment
Has anyone experienced something similar and found a way to fix it?
Click to expand...
Click to collapse
Try a factory data reset but you will wipe your phone and lose all data and apps.
xbxjunkie said:
did you disable any of the bloat? that might be your issue.....
Click to expand...
Click to collapse
That's odd, I even blocked the OTA via adb and mine says official.

OK i tried both, neither worked, also when i boot into recovery i get qe 1/1 at the bottom left side of my screen

Decided to just get a replacement from motorola since I'm still under warranty, but thank you for the suggestions!

jaideng123 said:
Decided to just get a replacement from motorola since I'm still under warranty, but thank you for the suggestions!
Click to expand...
Click to collapse
You could just flash the stock ROM again!

Gundabolu SC said:
You could just flash the stock ROM again!
Click to expand...
Click to collapse
I am unable to obtain the moforoot util to do this. When I put in my ID on the moforoot page, it says my device is not supported. I know for a fact the model and current OS on it. Its 5.1 updated already which is probably why the website is rejecting my request to obtain the util.
I do not think the bootloader will allow me to downgrade. If anybody has a solution, please let me know.
Note: Using XT1254 w/ latest 5.1 update from Aug-Sept.

LatencyXXX said:
I am unable to obtain the moforoot util to do this. When I put in my ID on the moforoot page, it says my device is not supported. I know for a fact the model and current OS on it. Its 5.1 updated already which is probably why the website is rejecting my request to obtain the util.
I do not think the bootloader will allow me to downgrade. If anybody has a solution, please let me know.
Note: Using XT1254 w/ latest 5.1 update from Aug-Sept.
Click to expand...
Click to collapse
If you want to flash an official update that is greater than or equal to the version you're on now, you don't need mofo. You could use fastboot, rsdlite, Motorola device manager or the Verizon upgrade assistant. The upgrade assistant is probably the easiest way to go. That's the annoying pop up software you get whenever you plug your phone into your computer.

TheSt33v said:
If you want to flash an official update that is greater than or equal to the version you're on now, you don't need mofo. You could use fastboot, rsdlite, Motorola device manager or the Verizon upgrade assistant. The upgrade assistant is probably the easiest way to go. That's the annoying pop up software you get whenever you plug your phone into your computer.
Click to expand...
Click to collapse
I tried all 3 different options and none of them work. Then I went into Verizon store and asked them to do it and they told me that they don't do that anymore. Only contacts, photos, etc.
The store told me to send it to Motorola for them to do it. I'm sure there is an ISP somewhere or some trick button internally for them to unlock the bootloader, but nobody is saying.
I am out of options, and I am ready to send it to whomever can fix it for me. PM me if you can guarantee to do it and send it back.
-Thanks

LatencyXXX said:
I tried all 3 different options and none of them work. Then I went into Verizon store and asked them to do it and they told me that they don't do that anymore. Only contacts, photos, etc.
The store told me to send it to Motorola for them to do it. I'm sure there is an ISP somewhere or some trick button internally for them to unlock the bootloader, but nobody is saying.
I am out of options, and I am ready to send it to whomever can fix it for me. PM me if you can guarantee to do it and send it back.
-Thanks
Click to expand...
Click to collapse
Send it to Motorola then. If your phone is less than a year old, they will send you a new one for free.

Is there any possibilities for rooting turbo's lollipop?

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.

Update about OTA & FOTA from autoprime

http://forum.xda-developers.com/showpost.php?p=61672737&postcount=622
By autoprime
DON'T OTA
going to post this once... please spread the word into the other G4 subforums and any related posts anywhere.
I'm not sure if this is cause for alarm... but just putting the warning out there... based on viewing the latest USCC and T-Mobile files... these recent OTAs for USA carriers seem to be implementing "antirollback" which means you can never "go back" to a lesser version. To simplify things... fresh out of the box all of your phones were at "0" and now after the OTA they're at "1". Both the TMO and USCC KDZ file's are based on the OTA which is a "1" so there's no concern of flashing an older KDZ by mistake... at least for now. Not sure what will happen with future updates.
Can only confirm this on the TMO H811 and USCC US991... Still waiting on Sprint users to grab the OTA URL or zip name for me so I can inspect that... but I suspect all of the recent OTAs from AT&T, Sprint and Verizon also used the "1" update. The European/Asian/Etc variants still seem to be using the "0" version.. even after the recent updates. [Not every OTA will bump up the "version"]
I can't say what this means as a whole just yet... Maybe nothing at all. But perhaps for those who wish to stay at that fresh "0" for now... try your best to avoid the OTA update. I know the intl phones can disable updates but this option has been removed in USA variants. There are talks of an app that allows you to disable apks on your phone... I haven't used it myself but perhaps for those who want to maybe block the OTA app (LGDMSClient.apk)... worth checking out. This is said app: http://forum.xda-developers.com/andr...bloat-t2998294
apks to attempt to disable:
/system/priv-app/LGDMSClient/LGDMSClient.apk (not in all phones)
/system/priv-apps/LGUpdateCenter/LGUpdateCenter.apk
Again.. I don't really know what any of this means just yet... just reporting what I do know. Spread the word.
And for those who were forced to OTA.. or saying this post has come too late.. everyone knows to never ever OTA.. and the app to disable OTA has been around for a bit now. I'm sorry but..
Cross fingers and hope I'm wrong
Phones with "v1" status confirmed:
H811 10H
US991 10C

Seems to work
Thanks for the heads-up. Tried this on my H811 and it seemed to work. It is not able to block the apps, but it can disable them. Hopefully that is enough to stop an OTA.
I did get a message from ES File Explorer that the LG World app had been removed and asked me if I wanted to delete it's folder. So that is a good sign.
After reboot the Update Center in app settings has all options, including force stop, grayed out. So that leads me to believe that it is no longer running. Also, all changes stuck per the debloater program after reboot. :good:
Quick question: How do we tell if the phone has taken an OTA update? This generation has been pretty sneaky about running updates without asking thus far. I am currently on build LMY47D, but I am not sure if that is any different than what originally came on the phone.

funkbuqet said:
Thanks for the heads-up. Tried this on my H811 and it seemed to work. It is not able to block the apps, but it can disable them. Hopefully that is enough to stop an OTA.
I did get a message from ES File Explorer that the LG World app had been removed and asked me if I wanted to delete it's folder. So that is a good sign.
After reboot the Update Center in app settings has all options, including force stop, grayed out. So that leads me to believe that it is no longer running. Also, all changes stuck per the debloater program after reboot. :good:
Quick question: How do we tell if the phone has taken an OTA update? This generation has been pretty sneaky about running updates without asking thus far. I am currently on build LMY47D, but I am not sure if that is any different than what originally came on the phone.
Click to expand...
Click to collapse
For T-Mobile the software version of the latest update is H81110h. Find this under software, in About Phone. If you have that you took the FOTA/OTA from T-Mobile.
Sent from my LG-H811 using Tapatalk

That's the one that updated itself by force. H81110H

jnclocker said:
That's the one that updated itself by force. H81110H
Click to expand...
Click to collapse
Well damn, looks like I was a bit too late. At least I can avoid the next one.

I have the latest software. It didnt ask me just installed it, before I even got phone setup.
Sent from my LG-H811 using Tapatalk

I purchased my g4 the evening before the pre-order for tmobile started .... So may 27th ish early. The girl on The phone said i was The first one to order it. Got it 3days later. When i first powered it on i was careful to not let it update, Which it didn't. Since I've had the phone it has never updated. When i checked software version I'm on h811 10h of lmy47d. I think it came installed with 10h.

<Deleted>

Youssarian said:
Confirmed. I just received one that shipped with 10h and know of one other.
Click to expand...
Click to collapse
But my point was that I received one of the first ones that were commercially available in the United States. I was three first person to get one thru t mo pre-order. Right the second they became available, and it was 10h

<Deleted>

Those greedy bastards just dont want us to experience happiness. (i.e. root, unlock boot). They want us to just be calm in their regime, so they can 'monitor' what we 'do'. Lg......jeez Its just a damn phone, gimme the unlock bin.

got mine on the 8th, before i walked out of the store it was updating to 10h (didnt know about this till now). i think the sales girl did the update while she had it in her grubby little hands
so if i understand, once you get to 10h you cant go back a version, is that right? didnt this same thing happen with the g2?

It auto updates during the setup process unfortunately. I'm sure she didn't care much about it. I'm a rep and I'm pretty sure nobody that is a rep besides me (out of everyone is talked to) knows much about stuff like this. I'm annoyed that we don't have the unlocked bootloader like the g3. :/
Sent from my LG-H811 using XDA Free mobile app

What app was at this link? http://forum.xda-developers.com/andr...bloat-t2998294 I just ask cause the link is dead and I'm getting my phone soon.

TekGadgt said:
What app was at this link? http://forum.xda-developers.com/andr...bloat-t2998294 I just ask cause the link is dead and I'm getting my phone soon.
Click to expand...
Click to collapse
you mean this link?
http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
its the debloater tool you can use without root

Just purchased a G4 myself and saw it updating at the counter. Pretty sure it updates during the setup process and we have no choice. Current software version in my hands is H81110h. Is this not the original version? Do we have a KDZ in which is older that we can attempt to use to go backwards? Thanks!

thenewbigmack said:
Just purchased a G4 myself and saw it updating at the counter. Pretty sure it updates during the setup process and we have no choice. Current software version in my hands is H81110h. Is this not the original version? Do we have a KDZ in which is older that we can attempt to use to go backwards? Thanks!
Click to expand...
Click to collapse
Original was whatever it says on the box label next to "S/W:". Most phones shipped with 10d.

Midnight_Rider said:
you mean this link?
http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
its the debloater tool you can use without root
Click to expand...
Click to collapse
Funny. Your link worked, but the one the OP used gives me a 404 error. Weird.

I'm getting a g4 this week most likely does this mean I can no longer root my device
Sent from my SM-G386T using Tapatalk

[email protected] said:
I'm getting a g4 this week most likely does this mean I can no longer root my device
Sent from my SM-G386T using Tapatalk
Click to expand...
Click to collapse
This thread is old... You can root with the current update.
Sent from my LG-H811 using Tapatalk

Vulnerability to open S5 (Verizon) bootloader released

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