Related
Is there a way I can root with 4.4? I have an unlocked bootloader but the SlapMyMoto method fails me everytime at the impactor 2222 step & even when I try to troubleshoot by using the small windows guide method provided by Jcase. I might be wrong entirely and there isn't yet a root for 4.4, if so let me know that way I don't sound too ignorant. :good:
Demorthus said:
Is there a way I can root with 4.4? I have an unlocked bootloader but the SlapMyMoto method fails me everytime at the impactor 2222 step & even when I try to troubleshoot by using the small windows guide method provided by Jcase. I might be wrong entirely and there isn't yet a root for 4.4, if so let me know that way I don't sound too ignorant. :good:
Click to expand...
Click to collapse
Flash twrp recovery by hashcode and flash supersu zip and you're all done
Sent on my Moto X
Is there any possibility there's a way I can root it without a custom recovery though? I understand that it is the easiest way to root, but I'd like to try and keep it stock, that's been my main difficulty thus far.
Demorthus said:
Is there any possibility there's a way I can root it without a custom recovery though? I understand that it is the easiest way to root, but I'd like to try and keep it stock, that's been my main difficulty thus far.
Click to expand...
Click to collapse
No, you already unlocked your boot loader , so you're already swimming in the swallow end so you may as well swim over to the deep end
Sent on my Moto X
flashallthetime said:
No, you already unlocked your boot loader , so you're already swimming in the swallow end so you may as well swim over to the deep end
Sent on my Moto X
Click to expand...
Click to collapse
Alright I'll get right on it then! Thanks x2 . Just as a side question since I've only had my Moto X for about a week and a half, will I still be able to continue to use touchless control and updates for it just as so long as I dont flash a custom rom? I want this puppy as stock as possible
Demorthus said:
Alright I'll get right on it then! Thanks x2 . Just as a side question since I've only had my Moto X for about a week and a half, will I still be able to continue to use touchless control and updates for it just as so long as I dont flash a custom rom? I want this puppy as stock as possible
Click to expand...
Click to collapse
As long as you run the stock ROM you'll have all the great features , if you use xposed framework and gravity box you'll have all the features that cyanogenmod has plus all moto's great features too, win win
Sent on my Moto X
Demorthus said:
I want this puppy as stock as possible
Click to expand...
Click to collapse
Why did you unlock your bootloader then?
http://forum.xda-developers.com/showthread.php?t=2573212
From what I was following it appeared to be as though it was necessary, but I misinterpreted it. But, it's too late now for any changes, sadly and unfortunately.
get TWRP, xposed framework, with gravitybox and google search api. learn to use tasker and all of its major plugins, you will have a blast with the moto x. the possibilities are endless.
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.
Hi guys,
I recently purchased the Developer Edition of Moto X. To be honest, I am not a developer for Android, and I am very new all together to Android, coming from iOS. All of my iPhones have always been jailbroken, and I would like to root my new Android as well. My Moto X has an unlocked boot loader. If I understand it correctly, this should allow me to root the phone in a permanent way. I would like to stick with the stock Moto X room, but I want to have root for some of the apps that need it.
I have googled it and found a bunch of different guides on how to do this, but is there a better way to do it on a device with an unlocked boot loader? Something what works with 4.4.2. If you point me in the right direction, I would really appreciate it.
Thanks,
- Bogdan
x0054 said:
Hi guys,
I recently purchased the Developer Edition of Moto X. To be honest, I am not a developer for Android, and I am very new all together to Android, coming from iOS. All of my iPhones have always been jailbroken, and I would like to root my new Android as well. My Moto X has an unlocked boot loader. If I understand it correctly, this should allow me to root the phone in a permanent way. I would like to stick with the stock Moto X room, but I want to have root for some of the apps that need it.
I have googled it and found a bunch of different guides on how to do this, but is there a better way to do it on a device with an unlocked boot loader? Something what works with 4.4.2. If you point me in the right direction, I would really appreciate it.
Thanks,
- Bogdan
Click to expand...
Click to collapse
This Guy has all these kind of tips
http://mark.cdmaforums.com/MotoX.htm
My opinion, if you can't figure out how to root a device with an unlocked bootloader when non-stock recovery is available, you should just leave your phone stock. It doesn't get any easier unless it would come pre-rooted.
Sent from my Moto X
Thanks for the tip. The procedure looks relatively simple. Is the mfastboot the utility that Motorola includes with their SDK, or is it a 3rd party utility? I have a mac, and I would like to do all of this without having to boot into Windows.
Thanks!
x0054 said:
Thanks for the tip. The procedure looks relatively simple. Is the mfastboot the utility that Motorola includes with their SDK, or is it a 3rd party utility? I have a mac, and I would like to do all of this without having to boot into Windows.
Thanks!
Click to expand...
Click to collapse
There is a Mac toolkit in our dev section. I think all you need is fastboot not m....
I don't understand why you need to over complicate unlocking and rooting a Developer Edition. Just go here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Request the unlock code. Follow the instructions to unlock it. You can then install TWRP and root it.
Here's a complete guide here on XDA. Tho, with Mac, you may need that toolkit.
Personally, if you can use windows, I'd use it.
http://forum.xda-developers.com/showthread.php?t=2603358
Thanks for all the links, I think I figured it out. The mfastboot should come with the Motorola Development bundle, and the rest I have ready. Looks like the process is pretty straight foreword. I'll post a little writeup for doing this on Mac if I am successful.
- Bogdan
kj2112 said:
Here's a complete guide here on XDA. Tho, with Mac, you may need that toolkit.
Personally, if you can use windows, I'd use it.
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
I used a mac without any issues. Uses fastboot instead of mfastboot. And I think I used the SDK. Don't remember now.
krsmit0 said:
I used a mac without any issues. Uses fastboot instead of mfastboot. And I think I used the SDK. Don't remember now.
Click to expand...
Click to collapse
I'm sure Mac is fine. Just if there's any problems, it'll be harder to find help here with Mac stuff.
kj2112 said:
I'm sure Mac is fine. Just if there's any problems, it'll be harder to find help here with Mac stuff.
Click to expand...
Click to collapse
Its pretty much the same as Linux. Windows might actually be the odd ball in the process.
x0054 said:
Hi guys,
I recently purchased the Developer Edition of Moto X. To be honest, I am not a developer for Android, and I am very new all together to Android, coming from iOS. All of my iPhones have always been jailbroken, and I would like to root my new Android as well. My Moto X has an unlocked boot loader. If I understand it correctly, this should allow me to root the phone in a permanent way. I would like to stick with the stock Moto X room, but I want to have root for some of the apps that need it.
I have googled it and found a bunch of different guides on how to do this, but is there a better way to do it on a device with an unlocked boot loader? Something what works with 4.4.2. If you point me in the right direction, I would really appreciate it.
Thanks,
- Bogdan
Click to expand...
Click to collapse
You can unlock though Motorola. Then install super su from the play store. If you're not interested in flashing a custom ROM you should be good to go, however I'd advise flashing a custom recovery and making a back up. Not needed but makes things a lot easier.
Sent from my XT1060 using XDA Premium 4 mobile app
aviwdoowks said:
There is a Mac toolkit in our dev section. I think all you need is fastboot not m....
Click to expand...
Click to collapse
FYI: I used the Mac toolkit to get my new DE going.
Also be aware the up code goes to the email Moto has tied to the phone not the user account (email) you need to create the unlock.
Ever since I've rooted my Moto G 2nd Gen (Consumer Cellular) with Kingroot it has been starting to take a full 5-7 minutes just to boot up. The weird part of it is that the device reboots itself automatically 3 times just to finally boot to the OS. I have no clue of what's going on at the moment, but this is an incredibly irritating issue. Any thoughts? Any help will obviously be appreciated.
Who did you tell to use some rooting tool like Kingroot or whatever?
To root your Moto G you have to unlock your bootloader on Motorola page,flash or boot into custom recovery (TWRP) and then flash latest super SU from there.
Or after unlocking use chainfires autoroot.
All this you can read here:
http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243
Never use some rooting tool when it´s not recommended...
Wolfcity said:
Who did you tell to use some rooting tool like Kingroot or whatever?
To root your Moto G you have to unlock your bootloader on Motorola page,flash or boot into custom recovery (TWRP) and then flash latest super SU from there.
Or after unlocking use chainfires autoroot.
All this you can read here:
http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243
Never use some rooting tool when it´s not recommended...
Click to expand...
Click to collapse
Thanks.
I have the same problem anyone know what causes this long boot time? The kingroot works great in every other way and no need for unlocking boot loader or even the need for a pc making it a very easy option. Any experience of this root method from anyone here?
xs1m0nx said:
I have the same problem anyone know what causes this long boot time? The kingroot works great in every other way and no need for unlocking boot loader or even the need for a pc making it a very easy option. Any experience of this root method from anyone here?
Click to expand...
Click to collapse
That's an awful way to root and frankly almost if not impossible to do. This phone needs to be unlocked to root and anything other than that way is bound to fail.
Well that's not the case it does not fail it works great with just a small issue of longer boot time. Far from being an awful way it's actually a brilliant way as it makes it so easy for people with minimum fuss. What I'm really looking for is some constructive information from someone who has good knowledge of this root method. The boot time is not really a big deal I'm just interested to know why it does this.
xs1m0nx said:
Well that's not the case it does not fail it works great with just a small issue of longer boot time. Far from being an awful way it's actually a brilliant way as it makes it so easy for people with minimum fuss. What I'm really looking for is some constructive information from someone who has good knowledge of this root method. The boot time is not really a big deal I'm just interested to know why it does this.
Click to expand...
Click to collapse
Well have at it. It's obviously a poor choice as you'll eventually discover. Some people just look for ways to fail.
I think it's more people look for new ways and that's not a bad thing. Everything moves on and what was not possible to do becomes possible. Yes it maybe true that there can be problems but there are few that can't be overcome. Every method was unknown and risky as some point but that's just how it will always be. You got to admit kingroot have done what everyone said was impossible so that's pretty clever of them. Hopefully someone a lot more clever than me will work out about the little side effect in time.
Update: Tel864 is quite right although this does root your phone it causes problems with boot that just get worse over time. I've flashed stock back on mine I'll probably re root but with the recommended method so yes I retract all the above!
What scares me about Kingroot is the fact that it's just a collection of exploits that forces changes to the bootloader. It sort of goes against the very thing that makes Android safer.
Sent from my GT-P5210 using Tapatalk
Yes your right and I imagine eventually may brick the phone. I have rooted the proper way now and installed a custom ROM so ended up with a much better situation.
Sent from my Moto G 2014 using Tapatalk
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.