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.
Related
I feel kinda screwed here, I purchase phones without contract on purpose so that I do not have locked bootloader restrictions, though i cannot with this Xperia T, It's a lovely phone and I'd prefer to not return it for this restriction.
I'd love to get my hands drity on the Xperia T' s kernel source
What would you guys recommend me?
FYI, I only rooted the phone and updated to Jelly Bean.
djpbx said:
I feel kinda screwed here, I purchase phones without contract on purpose so that I do not have locked bootloader restrictions, though i cannot with this Xperia T, It's a lovely phone and I'd prefer to not return it for this restriction.
I'd love to get my hands drity on the Xperia T' s kernel source
What would you guys recommend me?
FYI, I only rooted the phone and updated to Jelly Bean.
Click to expand...
Click to collapse
Currently there is no way to unlock your botloader if it says its not allowed.
I would return it and get ask for one that can be unlocked.
gregbradley said:
Currently there is no way to unlock your botloader if it says its not allowed.
I would return it and get ask for one that can be unlocked.
Click to expand...
Click to collapse
Yeah i was thinking to to trade it in if this cant be fixed, though i feel its a shame if i need to.
djpbx said:
Yeah i was thinking to to trade it in if this cant be fixed, though i feel its a shame if i need to.
Click to expand...
Click to collapse
well maybe as a dev it may push you into finding a way to unlock it
Yeah, you need to change it, having a T with a locked bootloader is like having a gorgeous girlfriend who wants to be celibate
djpbx said:
I feel kinda screwed here, I purchase phones without contract on purpose so that I do not have locked bootloader restrictions, though i cannot with this Xperia T, It's a lovely phone and I'd prefer to not return it for this restriction.
I'd love to get my hands drity on the Xperia T' s kernel source
What would you guys recommend me?
FYI, I only rooted the phone and updated to Jelly Bean.
Click to expand...
Click to collapse
This is probably a stupid question, as I guess you are well aware of this issue, but are you sure that the bootloader was unlockable when you purchased the phone? What I have in mind is that if you've used Goroh_kun's rooting method (or option "3" from Bin4ry's script), then the service menu incorrectly shows that bootloader unlocking is not allowed. I haven't bothered to check whether this actually does prevent the unlocking or it's simply a bug in the service menu itself, caused by the hooked library, but in any case it can be easily fixed. From what I've heard, it would be rather unusual to have an unbranded Xperia T that has the bootloader unlockable.
Edit: Ah, sorry, just noticed in your signature that my comment was also not relevant anymore, in addition to being unlikely helpful in your case.
Re: [Q] Bought an Xperia T without contract, though i'm not allowed to unlock bootloa
kerberizer said:
This is probably a stupid question, as I guess you are well aware of this issue, but are you sure that the bootloader was unlockable when you purchased the phone? What I have in mind is that if you've used Goroh_kun's rooting method (or option "3" from Bin4ry's script), then the service menu incorrectly shows that bootloader unlocking is not allowed. I haven't bothered to check whether this actually does prevent the unlocking or it's simply a bug in the service menu itself, caused by the hooked library, but in any case it can be easily fixed. From what I've heard, it would be rather unusual to have an unbranded Xperia T that has the bootloader unlockable.
Edit: Ah, sorry, just noticed in your signature that my comment was also not relevant anymore, in addition to being unlikely helpful in your case.
Click to expand...
Click to collapse
Hmm, didnt root it on jb yet but this is helpful information anyways. I didnt see it around the forums yet
Sent from my Nexus 7 using xda app-developers app
djpbx said:
Hmm, didnt root it yet but this is helpful information anyways. I didnt see it around the forums yet
Click to expand...
Click to collapse
This has actually been fixed in the latest version (22+) of the Bin4ry's script. If you do the rooting manually, using the Goroh_kun's method, I'd suggest that you make a copy of /data/data/com.sonyericsson.android.servicemenu/lib/libservicemenu.so, noting also the ownership (should be system:system) and permissions (most likely 644). I went so far as to restore the file's timestamp, but that seems to be unnecessary. In case you forget to do this, just take a look at Bin4ry's script and use the library he provides in the archive.
BTW, could you please tell which ROM version have you rooted successfully? I got a phone with 7.0.A.3.226 preinstalled, and neither method seems to work. There's simply no /data/local.prop for Bin4ry's original method to work (it seems to either be completely ignored if created, or at least its ownership is checked to confirm it's owned by root and not by, e.g. system), and Goroh_kun's method fails to switch the ownership of /sys/kernel/uevent_helper to system (if I understand correctly how it's supposed to work). Judging from other reports, this ROM version (and .223, perhaps) has indeed been patched against Bin4ry's method, and Goroh_kun's is likely working only on JB, so no surprise, but I really hoped I could make a full 1:1 backup of the phone.
Cheers,
Luchesar
P.S. Here's an article* that mentions the problem with the bootloader, but the solution is indeed much simpler. (Sorry, being a newbie here, I'm not allowed to post the link more conveniently. )
*) w w w .itechpost.com/articles/6550/20130314/sony-xperia-z-jelly-bean-4-1-2-root-upgrade-kit-guide-goroh-kun-leak-android-xda.htm
Re: [Q] Bought an Xperia T without contract, though i'm not allowed to unlock bootloa
kerberizer said:
BTW, could you please tell which ROM version have you rooted successfully? I got a phone with 7.0.A.3.226 preinstalled, and neither method seems to work. There's simply no /data/local.prop for Bin4ry's original method to work (it seems to either be completely ignored if created, or at least its ownership is checked to confirm it's owned by root and not by, e.g. system), and Goroh_kun's method fails to switch the ownership of /sys/kernel/uevent_helper to system (if I understand correctly how it's supposed to work). Judging from other reports, this ROM version (and .223, perhaps) has indeed been patched against Bin4ry's method, and Goroh_kun's is likely working only on JB, so no surprise, but I really hoped I could make a full 1:1 backup of the phone.
Cheers,
Luchesar
Click to expand...
Click to collapse
I did a good root on ICS wit the standard method from bin4ry. Later i updated to jb but didnt Root that one yet
Sent from my Nexus 7 using xda app-developers app
djpbx said:
I did a good root on ICS wit the standard method from bin4ry. Later i updated to jb but didnt Root that one yet
Click to expand...
Click to collapse
I guess it must have been an earlier version than mine. Do you by chance remember what was the exact ROM version number?
Re: [Q] Bought an Xperia T without contract, though i'm not allowed to unlock bootloa
Nop. Unfortunately not
Sent from my HTC Desire S using xda app-developers app
gregbradley said:
well maybe as a dev it may push you into finding a way to unlock it
Yeah, you need to change it, having a T with a locked bootloader is like having a gorgeous girlfriend who wants to be celibate
Click to expand...
Click to collapse
I like the way you put it!
djpbx said:
Nop. Unfortunately not
Click to expand...
Click to collapse
Never mind. Thanks and good luck with the new phone!
kerberizer said:
Never mind. Thanks and good luck with the new phone!
Click to expand...
Click to collapse
Thanks, hope the store sends it quickly but the mail service isnt terribly fast
With that said, the thread is closed. I got all the advices i needed and this can be a helpful resource for others.
Cheers!
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 was just Google searching hoping for some good news... And came across this posted yesterday...
http://www.youmobile.org/blogs/entry/Root-Moto-X-KitKat
... Any truth to that? And is it for any carrier, i.e att?
Sent from my XT1058 using Tapatalk
Links to a thread on here.
Yea I saw that, but they are not the same...
Sent from my XT1058 using Tapatalk
They want you to dl this http://www.cydiaimpactor.com/
Anyone know what it is?
Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?
jbaumert said:
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?
Click to expand...
Click to collapse
There's other threads where this stuff gets talked about, but im pretty sure for things like that it would probably work. But any actual changes to anything would get reversed.
I've always been unlocked....so I don't have firsthand experience though.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.
KidJoe said:
I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.
Click to expand...
Click to collapse
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
Please see my response to you in the 4.2.2 to 4.4.2 thread.
kj2112 said:
Please see my response to you in the 4.2.2 to 4.4.2 thread.
Click to expand...
Click to collapse
Thanks, didn't realize until afterward it was the same voice in both threads.
Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.
Jumnhy said:
Thanks, didn't realize until afterward it was the same voice in both threads.
Click to expand...
Click to collapse
Where you found another same threads ?
DANIEL AMBRUSO said:
Where you found another same threads ?
Click to expand...
Click to collapse
It was just kj2112 explaining a similar issue to me. Check it out, but essentially my understanding is that there's no root for 4.4.2 if the phone never had root previously (ie, if you naively took the OTA like me without thnking about implications for root.
---------- Post added at 10:01 PM ---------- Previous post was at 09:56 PM ----------
KidJoe said:
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.
Click to expand...
Click to collapse
Solid, thanks for the concise summary. I'd read jcase's posts a while back about a potential exploit--something about using it in a teaching session at BlackHat? He even says though, that the exploit he has will probably never be useful for the average user insofar as it would be too hard to implement and n00bz like myself would end up bricking our phones. So I'm not holding my breath on that one. Ugh. Sad I missed the window for the Chinese connection. Should have jumped on it.
The Tallest said:
Links to a thread on here.
Click to expand...
Click to collapse
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.
glarepate said:
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.
Click to expand...
Click to collapse
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).
KidJoe said:
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).
Click to expand...
Click to collapse
Yes, if you have already gone to 4.4.2 you are out of luck.
I'm using the T-Mobile SafeStrap Recovery with my RW Moto X. This was done by a Franken-ROM process that uses the 4.4.2 ROM without using the 4.4.2 bootloader and using the SS recovery to flash a zip file with some components of the 4.4.2 ROM and then flashing SuperSU. Whether or not it should be working, it is. Nothing I can, or want to, do about that.
But I am sure you are right that this resultant ROM would not work on phones from other carriers. Versions for other carriers are being developed though. It may simply be a matter of time and interest by motivated individuals until this is available for just about everyone.
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.
Hi I have a DROID Turbo that currently has the MOFO Rooted ROM installed. I have to send my in for the screen replacement, but need to remove the Root as this voids the warranty. I have went to the SU app and clicked on the remove root, but am unsure if that is all I need to do besides wiping my cell.
raxhunter said:
Hi I have a DROID Turbo that currently has the MOFO Rooted ROM installed. I have to send my in for the screen replacement, but need to remove the Root as this voids the warranty. I have went to the SU app and clicked on the remove root, but am unsure if that is all I need to do besides wiping my cell.
Click to expand...
Click to collapse
I had to use the screen replacement last summer for my first Turbo, which was purchased from Verizon around Thanksgiving 2014. I never took an OTA update and got MOFO root as soon as it came out. I'm not sure if this works for everyone, but the only way I was able to have the "Modified" Software status on bootloader changed to Unmodified before I sent it back for replacement was to plug it into a windows computer with Verizon's Upgrade Assistant installed, wipe everything and reset to factory (backup anything you want to save first), and let it update. I couldn't read the screen but after letting the busted phone update, I do remember somewhere within the Verizon application it stated the software status was Unmodified (or what ever else it's supposed to say).
Not sure if it will work for you but it's something to try.
Thank you for the info... I'll give it a try
raxhunter said:
Thank you for the info... I'll give it a try
Click to expand...
Click to collapse
If that doesn't work, you might have to purchase moforoot or Sunshine in order to flash an unrooted image, and to get rid of the Modified line.
I tried the rootjunky unroot, but still see the modified line in boot. I also tried the VZW update tool, but the communications seem to stop around 17 of 20 packets... I've been stumped all day... Can you post a link for the MOFO unmodified image? Or the sunshine rout... I've paid for the MOFO root, so maybe I don't need to buy it...
Thanks in advance
raxhunter said:
I tried the rootjunky unroot, but still see the modified line in boot. I also tried the VZW update tool, but the communications seem to stop around 17 of 20 packets... I've been stumped all day... Can you post a link for the MOFO unmodified image? Or the sunshine rout... I've paid for the MOFO root, so maybe I don't need to buy it...
Thanks in advance
Click to expand...
Click to collapse
I'm not sure about this article's reliability, but it looked like it could help you.
Or you can download these files for the appropriate firmware version and flash them after unlocking with Sunshine.
Your best bet would be to flash the stock system image with mofo. Unfortunately, I was unable to find the flashable moforoot unrooted image.
I'm unsure if this would change the Modified line to Unmodified; if it doesn't than I have no idea.
Additionally, Motorola offers a repair service where you can send in a device to be repaired either for a small fee or for free. With the paid option, they don't inspect the actual device, and they send you a new phone. This could be used as a last resort.
I tried the article... The downgrade didn't work... I'll see if sunshine will work...
The sunshine one is the same one I tried earlier from rootjunky... The software line in the boot still sez modified, but the software in the about phone area sez official.. Dunno...
You might have to just use the Motorola service. Why do you want to get rid of the Modified line, again?
raxhunter said:
I tried the rootjunky unroot, but still see the modified line in boot. I also tried the VZW update tool, but the communications seem to stop around 17 of 20 packets... I've been stumped all day... Can you post a link for the MOFO unmodified image? Or the sunshine rout... I've paid for the MOFO root, so maybe I don't need to buy it...
Thanks in advance
Click to expand...
Click to collapse
Factory reset, then use the Verizon update tool? Wait for it to actually finish? It probably takes a long time.
Sent from my XT1254 using Tapatalk
Latiken said:
You might have to just use the Motorola service. Why do you want to get rid of the Modified line, again?
Click to expand...
Click to collapse
The screen is cracked, VZW will replace the screen for free if phone is less then 1yr old, but in the return box there is a clause for modified software that won't cover the broken screen.
SpyderPride said:
Factory reset, then use the Verizon update tool? Wait for it to actually finish? It probably takes a long time.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
That's what I tried... It gets to about packet 17 of 20 then the screen sez lost communication... It's weird because onbthe cell is sez USB connected...
raxhunter said:
The screen is cracked, VZW will replace the screen for free if phone is less then 1yr old, but in the return box there is a clause for modified software that won't cover the broken screen.
Click to expand...
Click to collapse
You don't have to use Verizon's service. There's two options you can use, both from Motorola: a paid one and a free one. The link is in one of my previous posts.
Someone on the forum said that with the paid option, they send you a new (or very well refurbished) Turbo without looking at your current device (so they wouldn't penalize you for it being modded.)
The free option is a bit more iffy. The same someone said that they check the device, but Motorola didn't specify if they check the software, or just the hardware.
The paid option would be your best bet, but you can opt for the free option if you feel a bit risky.