Prepare for bootloader unlock! - Verizon Motorola Droid Turbo General
For those who might not know, great things are about to happen. Get ready!
https://twitter.com/TheRootNinja
EDIT: Alright, ladies and gentlemen, let's get to it: http://theroot.ninja/download.html
They're ready.
Once you have bootloader unlock, you just install TWRP custom recovery. This one works for all Quarks (XT1254, XT1250, XT1225) if you have an unlocked bootloader:
[RECOVERY][OFFICIAL TWRP 2.8.7.0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
http://forum.xda-developers.com/showpost.php?p=63952288&postcount=1550
After that, head on over to the XT1225 Moto Turbo/Moto Maxx and XT1250 U.S. Moto Maxx section. You can install custom animations, remove the bootloader unlock warning, etc.
Themes and applications for the Motorola Moto Maxx
http://forum.xda-developers.com/moto-maxx/themes-apps
Anything that works on the the XT1250 U.S. Moto Maxx which has the same FCC ID as the XT1254 will also work on the Droid Turbo XT1254. The only difference was that until now the XT1254 had locked down bootloader. They are ALL Quarks.
@Skrilax_CZ, the Quark CM dev is also working to make sure you can flash CM12.1 OK.
Skrilax_CZ said:
I need to look again on the XT1250 / XT1254 support so it's not stuck at bootlogo
Click to expand...
Click to collapse
How long will it take us to have a few custom roms like cyanogen? Will moto maxx roms work right away for the turbo?
Sent from my XT1254 using Tapatalk
cadenmiller60 said:
How long will it take us to have a few custom roms like cyanogen? Will moto maxx roms work right away for the turbo?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
@Skrilax_CZ and @baybutcher27 are the ones to ask. They've been working on ROMs/kernels to be compatible with the XT1250 U.S. Moto Maxx, which is identical to the XT1254 Droid Turbo (same FCC ID IHDT56PK1).
FYI:
The "international" XT1225 Moto Turbo/Moto Maxx QUARK has a different FCC ID (IHDT56PK2) as it has no CDMA and slightly different LTE bands, but the exact same hardware as the XT1254/XT1250. LTE bands 2, 3, 4, 5, 7, 17.
However, the XT1250 U.S. Moto Maxx is the SAME device as the XT1254 Droid Turbo, down to the FCC ID (IHDT56PK1). Sold by U.S. regional CDMA/LTE carriers. Runs on Verizon with a Verizon SIM card, just like a non-Verizon Moto Nexus 6. The XT1250 Quark has an unlock-able bootloader and can be rooted. Many people are running them on Verizon.
Stuff like TWRP, boot animations, etc will work on ALL Quarks, but ROMs and kernels will have to be made completely compatible for the XT1254/XT1250 due to the CDMA stuff.
_______
@Skrilax_CZ is part of the CM team. He bought a Quark XT1225 Moto Maxx and developed CM12 and then 12.1 for it. His kernel work is invaluable. All other custom ROMs for the Quarks use CM sources, especially the kernel.
[Moto MAXX XT1225][OFFICIAL] CyanogenMod 12.1
http://forum.xda-developers.com/mot.../moto-maxx-xt1225-cm12-0-pre-release-t3060089
mrkhigh said:
@Skrilax_CZ What is the status of cm12.1 and cm13? I believe I heard with a few minor tweaks cm12 was a daily driver.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Skrilax_CZ said:
It is a daily driver for XT1225 (CM-12.1, CM-12.0 was deprecated early, and CM-13.0 isn't ready yet), it's just I didn't give much attention to XT1250/XT1254 so some tweaks are needed to set it right for CDMA.
Click to expand...
Click to collapse
______
@baybutcher27 took up the Quark TWRP work from @respider and got official status, then went on to adapt two other custom ROMs for the Quark -- Resurrection Remix and Mokee. Thank him for the TWRP you will use with the XT1254 Droid Turbo.
[RECOVERY][OFFICIAL TWRP 2.8.7.0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
[ROM][Moto MAXX][5.1.1]Resurrection Remix 5.5.8 [Optimized / O3 / GRAPHITE / KRAIT]
http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-5-5-5-t3197643
[ROM][5.1.1][OFFICIAL][QUARK] MoKee OpenSource Project
http://forum.xda-developers.com/moto-maxx/development/rom-mokee-opensource-project-t3188936
@baybutcher27 also developed a custom kernel:
[Kernel][Moto Maxx]BHB27-Kernel[5.x.x][CM base][V-1.1.4]
http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526
https://github.com/bhb27/My_works
___________
There's also a 4th custom ROM for Quark by another developer:
[Rom] NEXUS EXPERIENCE 9.8 [MotoMaxx]
http://forum.xda-developers.com/moto-maxx/development/rom-nexus-experience-release-9-5-t3108708
__________
Anyway, I know both those guys -- @Skrilax_CZ and @baybutcher27 -- tried to adapt their work so the XT1250 U.S. Moto Maxx could have Lollipop custom ROMs. As it's identical to the XT1254, CDMA bands, same LTE bands, etc. then that's what you need. However, for awhile they ran into problems as there weren't XT1250 volunteers to help test. I'm sure that won't be a problem with the XT1254 Droid Turbo owners? If a bunch of people are willing to test, the XT1254 compatibility should come very soon....
So, when the XT1254 gets bootloader unlocked THOSE are the two guys you want to make friends with. :good:
NOTE: when you go into the forum, don't just say you have a "Turbo". It's a Droid Turbo. Because there's also the XT1225 Moto Turbo. Yeah, even in the Quark family, Motorola used the same name. It's only the "Droid" name part that is exclusive for Verzion. [emoji14]
Motorola should t know about this...
Inviato dal mio XT1254 utilizzando Tapatalk
danger2u said:
Motorola should t know about this...
Click to expand...
Click to collapse
Why, so they can block the exploit with their next update?
Besides, it's Verizon who made Motorola lock down the bootloader. It's Verizon that will be mad, not Motorola. Because it will finally be YOUR phone, not theirs.
All the other Quarks (XT1225, XT1250) have the same hardware and have unlock-able bootloaders. In fact the XT1250 is IDENTICAL in every way to the XT1254 Droid Turbo -- same CDMA, same LTE bands, same FCC ID, and has unlock-able bootloader. It runs on Verizon with a Verizon SIM card just like a non-Verizon Moto Nexus 6.
maybe. i saw on Twitter that rootninja tags Motorola. if they read it,well i am afraid that it will patch it. so maybe we should move fast.
Inviato dal mio XT1254 utilizzando Tapatalk
danger2u said:
maybe. i saw on Twitter that rootninja tags Motorola. if they read it,well i am afraid that it will patch it. so maybe we should move fast.
Inviato dal mio XT1254 utilizzando Tapatalk
Click to expand...
Click to collapse
Once you unlock the bootloader, I believe that it is impossible to relock it.
Sent from my XT1254 using Tapatalk
cadenmiller60 said:
Once you unlock the bootloader, I believe that it is impossible to relock it.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
this is true. but if Motorola knows,they update and some user will take the update and the unlock for them will go forever maybe.
Inviato dal mio XT1254 utilizzando Tapatalk
danger2u said:
this is true. but if Motorola knows,they update and some user will take the update and the unlock for them will go forever maybe.
Inviato dal mio XT1254 utilizzando Tapatalk
Click to expand...
Click to collapse
I don't think so. It takes months of testing before verizon usually allows for a software update.
Sent from my XT1254 using Tapatalk
Verizon is not fast at releasing anything, that's for sure.
Sent from my XT1254 using Tapatalk
mbarry55 said:
Verizon is not fast at releasing anything, that's for sure.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Maybe the delayed releases is why their phones have the tightest, most secure phones.
Sent from my XT1254 using Tapatalk
richii0207 said:
Maybe the delayed releases is why their phones have the tightest, most secure phones.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
My point was it's not a big deal that either Verizon or Motorola knows about this because their updates are so slow. For whatever reason you want to attribute it to.
Sent from my XT1254 using Tapatalk
Just to be clear it is safe to update to. 44 right?
Sent from my XT1254 using Tapatalk
danger2u said:
maybe. i saw on Twitter that rootninja tags Motorola. if they read it,well i am afraid that it will patch it. so maybe we should move fast.
Inviato dal mio XT1254 utilizzando Tapatalk
Click to expand...
Click to collapse
Knowing we have done it and knowing how it was done are two different things
ChazzMatt said:
Why, so they can block the exploit with their next update?
Besides, it's Verizon who made Motorola lock down the bootloader. It's Verizon that will be mad, not Motorola. Because it will finally be YOUR phone, not theirs.
All the other Quarks (XT1225, XT1250) have the same hardware and have unlock-able bootloaders. In fact the XT1250 is IDENTICAL in every way to the XT1254 Droid Turbo -- same CDMA, same LTE bands, same FCC ID, and has unlock-able bootloader. It runs on Verizon with a Verizon SIM card just like a non-Verizon Moto Nexus 6.
Click to expand...
Click to collapse
Actually it would be bother verizon and moto
So just to be clear we are still waiting on this new version of Sunshine that supports the Turbo to be released, correct?
Ya.
Wynnded said:
Ya.
Click to expand...
Click to collapse
Awesome, I just read through the twitter posts, has anyone else seen any indication as to a timeline or eta? Assuming it would be pretty soon otherwise that is just a little mean to tease us like that
pitchinnate said:
So just to be clear we are still waiting on this new version of Sunshine that supports the Turbo to be released, correct?
Click to expand...
Click to collapse
And this new version of sunshine will unlock 5.1 on the xt1254?
And it is unlikely that the marshmallow update (which moto has promised but is probably months away) will relock the bootloader?
pitchinnate said:
Awesome, I just read through the twitter posts, has anyone else seen any indication as to a timeline or eta? Assuming it would be pretty soon otherwise that is just a little mean to tease us like that
Click to expand...
Click to collapse
I'd say the devs are going to enjoy their holiday, then turn their attention back to this.
Related
Lollipop on Turbo/Maxx - Root, Roadmap and Changes
I just got off the phone with a guy from Motorola Brazil. He clarified a lot of things. Some are good news, others not really. DISCLAIMER: I am not responsible for any actions you take after reading this. If you try anything and it doesn't work, it's you to you to find a way out. You can always post it here and the community will try to help you. It's your phone. Your actions. Release Date He didn't give me a date, rather, he told me the roadmap to it. Motorola is scaling upwards. G > X > G2 > X+1 > Maxx/Turbo Reminder: Verizon says when Turbo gets it after Motorola ships it to Verizon. They are testing the waters on smaller and cheaper devices. Apparently the "under-the-hood" changes are pretty complicated and giving them some headaches. I'd say it makes sense to what @Chainfire has been saying for quite a while now. Many security changes that are affecting how you can interact with the kernel and the init.d process, for example. Bootloader Unlockability Moto Maxx is unlockable. All you need is to go to their website and follow instructions. In KITKAT Apparently, Motorola still hasn't confirmed if they'll allow their customers to unlock the bootloader once Lollipop hits. Like I said, there's no confirmation. Motorola can always just be a good pal and keep on allowing it, it's all just speculations. Recovery Firmware It's the same firmware as the Moto X AND the Moto X 2014. It's up to you to try it out. I might try it next weekend if I got the time. There are no devs working on Maxx/Turbo AFAIK. However, we can apparently use the firmwares from Moto X or the Moto X 2014. This topic is the sole reason I added the disclaimer up there. Read it! The guy told me this, but understand that even though its not a confidential thing, it certainly is extra official. For those who thought a Moto X 2014 TWRP or CWM would brick their devices. Well, apparently, it won't. I'll remove the apparently when I have confirmation on this. Anyone feeling lucky, post your results here or just PM me. Root Root is a complicated matter. In Kitkat. With the previous information, we might be able to root it following Moto X 2014's instructions. More news in the future. In Lollipop. For those who don't know, we should be able to use root, once we patch up the kernel to boot the device allowing root. @Chainfire got it to work without the patch on the Nexus line in SuperSU 2.27, but it's really simple for Google to patch it. Don't expect it to last. Considering the amount of work it takes, we might end up with the shorter stick here. Unless some cool dev decides make it work for us as well, or if the patch for the Nexus 6 somehow work with the Maxx. Someone will have to try it. That's it for now. I'll try to update this as new info comes out. Please, leave a THANKS if you enjoyed it.
Surely these are quite good news. But officially, based on moto website, maxx is not unlockable by now. But these stuff being true is worth of not getting kitkat OTA, to keep the supposed unlockable state, using custom roms, if they someday become available.
ska4fun said: Surely these are quite good news. But officially, based on moto website, maxx is not unlockable by now. But these stuff being true is worth of not getting kitkat OTA, to keep the supposed unlockable state, using custom roms, if they someday become available. Click to expand... Click to collapse I unlocked mine already. It's just as the site says: get the code, send it to them, they reply with the unlock code
Nice! Thanks for the clarification!
alexcreto said: Release Date He didn't give me a date, rather, he told me the roadmap to it. Motorola is scaling upwards. G > X > G2 > X+1 > Maxx/Turbo Reminder: Verizon says when Turbo gets it after Motorola ships it to Verizon. They are testing the waters on smaller and cheaper devices. Apparently the "under-the-hood" changes are pretty complicated and giving them some headaches. I'd say it makes sense to what @Chainfire has been saying for quite a while now. Many security changes that are affecting how you can interact with the kernel and the init.d process, for example. Click to expand... Click to collapse So according to your source, we should be getting Lollipop after all the G's and X's were updated?, if this is the case, I think we should be getting Lollipop really soon, because most of the devices already have Android 5. :highfive:
Galaxo60 said: So according to your source, we should be getting Lollipop after all the G's and X's were updated?, if this is the case, I think we should be getting Lollipop really soon, because most of the devices already have Android 5. :highfive: Click to expand... Click to collapse I don't think that's the case. Both of those devices have a soak test in progress but lollipop has not officially been released to either. Unless I missed a few updates. .
cyberr8der said: I don't think that's the case. Both of those devices have a soak test in progress but lollipop has not officially been released to either. Unless I missed a few updates. . Click to expand... Click to collapse The soak tests were made before Lollipop was officially released (before Nov 13), but Motorola already made an official state about this here: http://motorola-blog.blogspot.mx/2014/11/its-time-to-unwrap-android-5-lollipop.html It seems that Lollipop was already released.
Looks like you're correct. Based on that it seems it is released for certain models. Surprised to see that yet the soak test hasn't started for the turbo. Thanks for sharing.
ska4fun said: Nice! Thanks for the clarification! Click to expand... Click to collapse I've put my oem unlock key in Motorola website and it says my device is unlockable, but I didn't proceed
I will proceed with the release of the first compatible recovery.
Galaxo60 said: The soak tests were made before Lollipop was officially released (before Nov 13), but Motorola already made an official state about this here: http://motorola-blog.blogspot.mx/2014/11/its-time-to-unwrap-android-5-lollipop.html It seems that Lollipop was already released. Click to expand... Click to collapse Just saw this as well. Seems the soak test for the Verizon Moto X is under way. http://m.androidcentral.com/soak-test-invites-going-out-2014-moto-x-verizon
The guy mentioned they were testing an internal build for the G2
Firmware for moto x and Moto x 2014 obviously doesn't work,not even recovery, first of all the devices are different in hardware and have different device trees, it will simple not flash whoever in motorola that told you that, doesn't know how all this works.
Jaocagomez said: Firmware for moto x and Moto x 2014 obviously doesn't work, but even recovery, first of all the devices are different in hardware and have different device trees, it will simple not flash whoever in motorola that told you that, doesn't know how all this works. Click to expand... Click to collapse yeah I think it's just a first line of support or something like that
Jaocagomez said: Firmware for moto x and Moto x 2014 obviously doesn't work, but even recovery, first of all the devices are different in hardware and have different device trees, it will simple not flash whoever in motorola that told you that, doesn't know how all this works. Click to expand... Click to collapse I thought it was weird. I even double checked. "Moto X+1 with the Moto X recovery??" and the guy said that he'd done it himself. Go figure... Sent from my XT1225 using XDA Free mobile app
Nexus 6 have a same hardware, anyone think if works in maxx?
The recovery for the 6 is for LP and is markedly different than a KK recovery. Also be aware that Troy Dees (TWRP) is on record as saying the recoveries for LP are much more involved than KK and to expect a relatively slow roll out for them to a broader range of devices. He did not say it but the impression I have from reading his comments on this are that marginal devices in terms of number of owners may be waiting a long time or never see a TWRP recovery for LP.
matheus_sc said: Nexus 6 have a same hardware, anyone think if works in maxx? Click to expand... Click to collapse if nexus 6 already has twrp recovery check if it works, thats the same hardware. just unlock moto maxx bootloader first. worst case escenario its that TWRP wont work and you'll have to flash stock recovery.img again.
Jaocagomez said: if nexus 6 already has twrp recovery check if it works, thats the same hardware. just unlock moto maxx bootloader first. worst case escenario its that TWRP wont work and you'll have to flash stock recovery.img again. Click to expand... Click to collapse once u flash recovery u will lose all ur data
danger2u said: once u flash recovery u will lose all ur data Click to expand... Click to collapse No... Once u unlock boot loader u loose all your data!
Bottom line on 4.4.4 and 5.1
With all the information and side convo - is it possible to be on 444 rooted, and sideload the 5.1 update and still be rooted? If yes, i'd like to see a thread to describe the process, as search yields to much to read in this lifetime, especially witht he xt1225 and not the 1254, and if no, that's great also, and i'll stick to the Nexus 6.
wrecklesswun said: With all the information and side convo - is it possible to be on 444 rooted, and sideload the 5.1 update and still be rooted? If yes, i'd like to see a thread to describe the process, as search yields to much to read in this lifetime, especially witht he xt1225 and not the 1254, and if no, that's great also, and i'll stick to the Nexus 6. Click to expand... Click to collapse if you are talking about the turbo go check out the development thread there is much written on it. everybody is on rooted LP now i believe. You are still on a mofo rooted turbo running KK?
johnbravado said: if you are talking about the turbo go check out the development thread there is much written on it. Click to expand... Click to collapse The XT1254 he mentions is the Droid Turbo. Whereas you just said "Turbo", which also is one of the model names of the XT1225 (Moto Turbo). The XT1225 was released as both the Moto Turbo and Moto Maxx. To avoid confusion, he stuck to model numbers, not partial model names. But yes, in the Development section are plenty of 5.1 rooted images for the XT1254 Droid Turbo.
ok so let me understand - the xt1254 can be rooted using mofo, which i have - if i sideload the LLPop, it will still be rooted?
wrecklesswun said: ok so let me understand - the xt1254 can be rooted using mofo, which i have - if i sideload the LLPop, it will still be rooted? Click to expand... Click to collapse As long as you didn't take the 5.1 OTA, you are OK. Images and instructions here: http://forum.xda-developers.com/dro...xt1254-21-44-12-quarkrootwifihotspot-t3064908 http://forum.xda-developers.com/showthread.php?p=61636335 http://forum.xda-developers.com/showthread.php?p=61752986
wrecklesswun said: ok so let me understand - the xt1254 can be rooted using mofo, which i have - if i sideload the LLPop, it will still be rooted? Click to expand... Click to collapse If you choose a pre-rooted Lollipop 5.1 image to flash, then yes.
Motorola bootloader unlock via TrustZone exploit - new?
Someone wrote up detailed steps how to unlock the bootloader on the 2014 Moto X, may work with other Motorola devices (gosh I hope) http://bits-please.blogspot.com/2016/02/unlocking-motorola-bootloader.html https://github.com/laginimaineb/Alohamora
It looks like it only works against kitkat.
Aren't all versions of the 2014 Moto X officially bootloader unlockable now? I know the Verizon, AT&T, and Pure editions are all unlockable. Is the international one eligible?
bzeimen said: Aren't all versions of the 2014 Moto X officially bootloader unlockable now? I know the Verizon, AT&T, and Pure editions are all unlockable. Is the international one eligible? Click to expand... Click to collapse Almost correct. All the versions are officially unlockable, except AT&T. The AT&T can be unlocked now, but not officially since it must be done through an exploit. Sent from my XT1095 using Tapatalk
It clearly states that that vulnerability only applies to MSM8974, and that is accurate.
This is probably useful for AT&T users. I wonder if it still works on 5.0
Duo8 said: This is probably useful for AT&T users. I wonder if it still works on 5.0 Click to expand... Click to collapse The vulnerability is valid for all 2014 moto x firmware versions, afaict....the code in git he provided is valid for nothing (requires a custom kernel/unlocked bootloader). fwiw SunShine supports all firmware versions of the 2014x as well. --beaups
beaups said: The vulnerability is valid for all 2014 moto x firmware versions, afaict....the code in git he provided is valid for nothing (requires a custom kernel/unlocked bootloader). fwiw SunShine supports all firmware versions of the 2014x as well. --beaups Click to expand... Click to collapse He said he will provide a version that uses a kernel exploit instead. Let's hope that works on newer fw as well. And since this works on all versions, I guess this bug is 100% a hardware one.
Duo8 said: He said he will provide a version that uses a kernel exploit instead. Let's hope that works on newer fw as well. And since this works on all versions, I guess this bug is 100% a hardware one. Click to expand... Click to collapse Its a tz kernel vuln, not hardware. They are easily patched, but there have been no patches released for the 14x for this bug. Sent from my XT1254 using Tapatalk
I don't know, men. I just rooted my xt1097 at&t two days ago with kingroot as soon as i knew about the good news and I couldn't contain myself and I paid for sunshine. Worked great by the way... Now I installed an xt1095 unbloated marshmallow (Thanks @AGISCI for the .zip). I'm happier than a week ago. =D
droid turbo mm india
https://www.youtube.com/watch?v=xd_iMhjFvA0
gavsi said: https://www.youtube.com/watch?v=xd_iMhjFvA0 Click to expand... Click to collapse Thanks for the video, but actually it's the Moto Turbo XT1225, not the Droid Turbo XT1254 (as you clearly say in the video). It's just your post title is misleading. You'll have Droid Turbo owners thinking somehow you got stock Marshmallow from Motorola on a Droid Turbo in India before them. Some Droid Turbo owners do have stock Marshmallow, but they are using @iiWoodstocK modified Brazil XT1225 image, which doesn't have Verizon VoLTE. Verizon Droid Turbo owners are eagerly awaiting Marshmallow released specifically for the XT1254. The XT1225 has had it since July.
ChazzMatt said: Thanks for the video, but actually it's the Moto Turbo XT1225, not the Droid Turbo XT1254 (as you clearly say in the video). It's just your post title is misleading. You'll have Droid Turbo owners thinking somehow you got stock Marshmallow from Motorola on a Droid Turbo in India before them. Some Droid Turbo owners do have stock Marshmallow, but they are using @iiWoodstocK modified Brazil XT1225 image, which doesn't have Verizon VoLTE. Verizon Droid Turbo owners are eagerly awaiting Marshmallow released specifically for the XT1254. The XT1225 has had it since July. Click to expand... Click to collapse Where can I find that modified image?
ChazzMatt said: Some Droid Turbo owners do have stock Marshmallow, but they are using @iiWoodstocK modified Brazil XT1225 image, which doesn't have Verizon VoLTE. Verizon Droid Turbo owners are eagerly awaiting Marshmallow released specifically for the XT1254. The XT1225 has had it since July. Click to expand... Click to collapse Sparksys said: Where can I find that modified image? Click to expand... Click to collapse In this forum, in Development: [ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable] http://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
XT1585 (Verizon) Root. Android 7.0
How can I root Motorola Turbo 2. XT1585 (Verizon). Running on Android 7.0 Anyone has done yet?
ahmeddrraza said: How can I root Motorola Turbo 2. XT1585 (Verizon). Running on Android 7.0 Anyone has done yet? Click to expand... Click to collapse You can't. You bought the wrong Kinzie. Sibling Moto X Force has bootloader unlock and root. Droid Turbo 2 does not. Sent via open market LG US998 V30/V30+