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.
Related
Why can't those of us who have locked phones just flash the developer's edition OS? By the time I learned of the Developer's edition phone, I had already passed my 14 business days return of my phone. The long root process is a bit much for me... If there is no other way, I'll give it a try though...
I'm not exactly sure how Motorola's bootloader works, but I'm pretty sure the Developer Edition is signed with different keys and will possibly be a different size. Motorola's bootloader I'm sure checks these things and will deny it.
The bootloader is not part of the OS, it's a different thing all on its own.
It really does seem as simple as you said OP but there's been plenty of phones with locked bootloaders, if it was as simple as that, there wouldn't need to be SafeStrap and other bypasses / exploits.
If you haven't looked at JCase's new SlapMyMoto 1.0 root method, it is more simple than the previous versions. It still requires going back to 4.2.2 camera OTA and losing all your data, but some of the ADB/Fastboot steps were removed and simplified, from what I've seen.
OK after a lot of sweat, I was able to get back to 4.2.2. How do I know if I have the camera patch?
jideay said:
OK after a lot of sweat, I was able to get back to 4.2.2. How do I know if I have the camera patch?
Click to expand...
Click to collapse
If you followed the instructions in the root guide and used the proper SBF to get back to 4.2.2, you should have the update. It links directly to the correct SBF for the root process.
http://forum.xda-developers.com/showthread.php?t=2538896
jideay said:
Why can't those of us who have locked phones just flash the developer's edition OS? By the time I learned of the Developer's edition phone, I had already passed my 14 business days return of my phone. The long root process is a bit much for me... If there is no other way, I'll give it a try though...
Click to expand...
Click to collapse
Depending on the model of you phone you can flash the developer edition rom,
XT1060, Verizon Retail, Moto Maker or Developer edition can flash the same Developer Edition recovery images direct from Moto's web site.
XT1053, GSM Developer or T-Mobile USA can use the GSM Developer recovery images direct from Moto's web site.
BUT this won't impact your ability to unlock your phone's bootloader.
(If you don't believe me that the rom is the same, Do a FC /B of all files contained inside the developer edition recovery images requested from Moto's web site with those inside the roms/images downloaded from http://sbf.droid-developers.org/phone.php?device=0 and you will see other than the XML, all files are identical. And the XML just tells RSDLite what to flash. Also when you request the GSM Developer Edition recovery files, you get a file named.. TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip )
Well, after a day and half of sweating, and a few hours there where I thought I bricked it, it's rooted on 4.4. I have rooted every android phone I've ever had, and this was by far the hardest... But i'm really happy with it. Got the wifi tether going and life is good. Thanks everyone for your replies...
jideay said:
Well, after a day and half of sweating, and a few hours there where I thought I bricked it, it's rooted on 4.4. I have rooted every android phone I've ever had, and this was by far the hardest... But i'm really happy with it. Got the wifi tether going and life is good. Thanks everyone for your replies...
Click to expand...
Click to collapse
This was surely the most involved root I've done. I think it's partially because I got this phone much close to launch than my previous devices. They all had one click root methods available by the time I tried.
fury683 said:
This was surely the most involved root I've done. I think it's partially because I got this phone much close to launch than my previous devices. They all had one click root methods available by the time I tried.
Click to expand...
Click to collapse
True the X hasn't been out long, and to complicate that more, 3 roms have been there for it... release, first OTA with camera fix, and Kit Kat...
Combine that with newer phones being harder to root... and yeah, one click root method isn't a reality at this point.
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.
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.
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
So I was just curious if there were any devs who were trying to crack this device and get some open development on this.
If there is, and you need us who have the phone in our hands to help, let us know!
none of them as far as i know
I haven't seen anything on the internet about this device or development that sucks I wish there was root available for this device and developers support hopefully someone comes out with something soon maybe is because some developers don't even have the device that's why they don't come out with anything yet or maybe it will stay that way :/
Mrblunt92 said:
I haven't seen anything on the internet about this device or development that sucks I wish there was root available for this device and developers support hopefully someone comes out with something soon maybe is because some developers don't even have the device that's why they don't come out with anything yet or maybe it will stay that way :/
Click to expand...
Click to collapse
I have some hope. I mean the Idol 3 got rooted and custom ROMs after all.
Mountainmohawk said:
I have some hope. I mean the Idol 3 got rooted and custom ROMs after all.
Click to expand...
Click to collapse
I think we might have to wait till probably early next year. Android 7.0 is about a month away, I think devs may wait till 7.0 is out there for the Idol 4S before they'd go tinkering.
atrain2324 said:
I think we might have to wait till probably early next year. Android 7.0 is about a month away, I think devs may wait till 7.0 is out there for the Idol 4S before they'd go tinkering.
Click to expand...
Click to collapse
we wont be getting 7.0 until the end of 2017..it is sad to say that there are already developers working on root for the note 7, and the phone hasnt even been in the market for more than a week
Sucks there is no developers working on this device , we need root , two or cwm , roms that's the only way to get maybe to get Android 7 earlier hopefully some developer takes action for us that would be awesome
Can anyone check to see if there is any validity to this method described on this site?
rootoreviews.com/root-Alcatel-Idol-4s-install-twrp-custom-recovery
deaniebaby said:
Can anyone check to see if there is any validity to this method described on this site?
rootoreviews.com/root-Alcatel-Idol-4s-install-twrp-custom-recovery
Click to expand...
Click to collapse
That's the way on carrier-branded handsets (unless you got HTC) I think. It's missing the whole part about the bootloader unlock part. While Marshmallow has an OEM Unlock switch, it's useless if the manufacturer won't release it (yet?).
atrain2324 said:
That's the way on carrier-branded handsets (unless you got HTC) I think. It's missing the whole part about the bootloader unlock part. While Marshmallow has an OEM Unlock switch, it's useless if the manufacturer won't release it (yet?).
Click to expand...
Click to collapse
Yeah seemed too good to be true haha. Guess we'll just keep waiting then.
I was just curious if anyone has an idea about root for the idol 4? I remember reading about the idol 3 and all I used was the Alcatel idol upgrade tool, flashed back to 5.1, rooted with recovery and installed stock rim zip. Is this a possibility to bypass the latest 6.0 bootloader? When I did the idol 3 I never had to unlock bootloader for root and custom Roms.
Weren't fastboot binarys removed?
If yes there will probably never be a chance to see custom ROMs for this device.
y
I so want this device to be rooted.. What are your opinions on this device with root? Will it be beast?
celoxocis said:
Weren't fastboot binarys removed?
If yes there will probably never be a chance to see custom ROMs for this device.
Click to expand...
Click to collapse
Fast boot was removed even with idol 3 but devs are developing. Only thing I noticed is with Alcatel idol 3 you were able to install 5.1, root, and install zip update through twrp. I'm trying to find 5.1 for this phone so I can do the same. I did however find some rooting links from others working on the possibilities.
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
mcarden2006 said:
Fast boot was removed even with idol 3 but devs are developing. Only thing I noticed is with Alcatel idol 3 you were able to install 5.1, root, and install zip update through twrp. I'm trying to find 5.1 for this phone so I can do the same. I did however find some rooting links from others working on the possibilities.
Click to expand...
Click to collapse
Honestly the only thing I ever do is root because the coolest software is for rooted phones.
I wouldn't consider myself a dev, but more of a tinkerer. Once I get my post count up, i'll be compiling some information i've collected about the device / similar devices. Hopefully we can get this ball rolling.
mcarden2006 said:
Fast boot was removed even with idol 3 but devs are developing. Only thing I noticed is with Alcatel idol 3 you were able to install 5.1, root, and install zip update through twrp. I'm trying to find 5.1 for this phone so I can do the same. I did however find some rooting links from others working on the possibilities.
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
Honestly the only thing I ever do is root because the coolest software is for rooted phones.
Click to expand...
Click to collapse
I think that only worked because the 3S had initially fastboot commands and those were later removed to "secure the phone" (big BS if u ask me).
But don't quote me on that. I don't own the device I had only looked into it its "fastboot command returning method" half a year ago because Oppo (my phones brand) had done the same thing with its fastboot commands. I was building up that method when I crossed the mind of a genius Interpreter hacker who was faster and used a way better method. I can't elaborate on the method used but he would be the only one I know, who could do something about the fastboot commands returning to the 4S.
I can't reveal his name because I promised not to but I could send him the "aboot" partition which contains the Little Kernel and let him check if he would be able to.
That is however only possible if someone could gain root access to the 4S and "DD" the aboot partition.
On a side note. Does Alcatel release kernel sources?
i think we have to make a custom kernel for root
Under developer options, the OEM can be unlocked (thus the boot loader). So it seems like Alcatel intended to allow devs to tweak with the phone. But at this point, it isn't much to go on.
deaniebaby said:
Under developer options, the OEM can be unlocked (thus the boot loader). So it seems like Alcatel intended to allow devs to tweak with the phone. But at this point, it isn't much to go on.
Click to expand...
Click to collapse
That option does literally nothing for unlocking the bootloader without fastboot.
If fastboot binarys were available it would just set a permission flag to allow "fastboot OEM unlock".
Alcatel removed the fastboot binarys intentionally to prevent users from rooting/flashing custom ROMs/ getting rid of crappy pre-installed vendor apps that only are their to use their services because they profit from data-mining.
The oem unlock toggle is included in all android google code. The vendors just don't bother to remove it. They simply remove the fastboot binarys.
Contacted alcatel support telling them to release a bootloader unlock or to release kernel source and fastboot binaries their answer is not clear since they didn't answer everything i asked but maybe we have some hope i did this for us who own the idol 4s and wants this thing rooted and developed support we should all email alcatel support and ask for a release tool to unlock bootloader https://photos.google.com/u/1/photo/AF1QipNi-GuS-c9DhHSqB-y0CQPwQdDPQETpvLd-rvV5