UPDATED GUIDE: How to unlock your MOTO MAXX/MOTO TURBO bootloader/install TWRP/root

[ChazzMatt]

JimChazz,
I have also tried

---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------

Chazz,
I have also tried my activated SIM card into the xt1250 but didn't get onto the network. I can work with that further to see what the problem is. That gives me a solid direction to work in.
So okay I'm stuck with Google Play. I'll have to figure out how to re install, it (Google Play) has record of being on both devices but it's not too be found on the new phone, and the PlayStore blocks a new download encounter.
When I check the phone this morning, maybe the GApps sideload I started will let me re flash it and then I'm off to the races.
Cheers

You can dirty flash the ROM and reflash Gapps in TWRP.

 

[[email protected]]

Moto Maxx xt1250 image size exceeded partition limits + pre flash validation failed

Chazz,
I was able to establish Resurrection 7.0 on the Moto Maxx and used my already authorized xt1254 SIM card. When I added my account, I allowed Google to take control of my phone (inadvertently) and Google cloned my Droid Turbo settings and apps and data to the new XT1250.
So then I had a working XT1250 on the Verizon network LTE, with Resurrection Remix as my OS.
But I didn't think I had root because I couldn't get SuperSU icon to populate my apps folder, no matter how many times I flashed it and re booted. I didn't see the SU icon in my apps folder, therefore didn't think I had root.
I did not use Rootcheck to verify, I just assumed I didn't have root.
So, I decided to try something different. I did a fresh wipe of everything except internal storage and re flashed TWRP, GApps, and RR, and this time I pre installed the SIM card in the XT1250 to see if the process progressed more easily.
The OS was operational, but device couldn't connect to Verizon network this time. Not SMS nor Voice.
So I never got the device on the Verizon network and had to take the SIM card out and put back in my Droid Turbo, so I would have an operational device to use.
So it's Saturday now and let's try it all again.
Getting nowhere fast.
Did an advanced wipe again, everything except internal storage, but now cannot re flash anything.
Get error image size exceeded partition limits + pre flash validation failed. Tried newly downloaded files but still same error, image size exceeded partition limits + pre flash validation failed.
Sideloading R R results in invalid zip signature error.
So I've gone backwards this day, but stuff happens !
Cheers

 

[ChazzMatt]

Chazz,
I was able to establish Resurrection 7.0 on the Moto Maxx and used my already authorized xt1254 SIM card. When I added my account, I allowed Google to take control of my phone (inadvertently) and Google cloned my Droid Turbo settings and apps and data to the new XT1250.
So then I had a working XT1250 on the Verizon network LTE, with Resurrection Remix as my OS.

You were on the right track here. Yes, let Google "restore" from recently used phone. It will often give you a choice of which recently used phone/device.

Chazz,
But I didn't think I had root because I couldn't get SuperSU icon to populate my apps folder, no matter how many times I flashed it and re booted. I didn't see the SU icon in my apps folder, therefore didn't think I had root.
I did not use Rootcheck to verify, I just assumed I didn't have root.

If you flashed SuperSu, you had probably had root. Sometimes you have to download the "user" SuperSu version from Google Play, in addition to flashing in TWRP, to have SuperSu icon in your apps folder. Also, in some versions of the ROM, SuperSu will appear as a Settings category. Most recently, I had to download SuperSu from Google Play. When you then open SuperSu in app drawer (and you can put a shortcut on one of the desktop screens), you can see which apps have root or not. Especially if you open up Titanium Backup it should ask for root. When the SuperSU prompt appears to grant or deny root, you also know it's installed. The default prompt is 15 seconds, I believe, but in SuperSu settings I change that to 30 seconds to give me more time.

Chazz,
So, I decided to try something different. I did a fresh wipe of everything except internal storage and re flashed TWRP, GApps, and RR, and this time I pre installed the SIM card in the XT1250 to see if the process progressed more easily.
The OS was operational, but device couldn't connect to Verizon network this time. Not SMS nor Voice.
So I never got the device on the Verizon network and had to take the SIM card out and put back in my Droid Turbo, so I would have an operational device to use.
So it's Saturday now and let's try it all again.
Getting nowhere fast.
Did an advanced wipe again, everything except internal storage, but now cannot re flash anything.
Get error image size exceeded partition limits + pre flash validation failed. Tried newly downloaded files but still same error, image size exceeded partition limits + pre flash validation failed.
Sideloading R R results in invalid zip signature error.
So I've gone backwards this day, but stuff happens !
Cheers

I'm not quite sure why this part didn't work out right.

If you boot into TWRP, connect to PC, drag over a zipped file -- like SuperSu -- and can see it.... (VERIFY you can see it and know it's what you dragged over) then you could even wipe internal storage and have a really clean slate.

Some people do this on purpose so that everything on the phone is "new", no legacy issues. But it's scary because from completely wiped phone, you cannot boot back to anything since nothing is installed. You then have to drag over ROM, GAPPS, and SuperSu from PC connection to then install.

I am not telling you to do that, that's up to you, but something about your phone sounds really confused at this point. I hope you get back to the stages you were at the beginning of this post. You were almost there!

 

[[email protected]]

Chazz,
Thanks again ! I'm up and running on Verizon rooted with RR ROM by bhb27. Everything functional. While I was not able to use fastboot to flash files, I was able to drag and drop to system file with my PC after doing another clean wpe of everything except internal storage.
Then booted into TWRP recovery and installed the GApps, SuperSU,RR 7.0, and reflashed TWRP for good measure.
Added my Google account, got WiFi.
Installed the activated 1254 SIM card, and it took maybe 15 minutes for me to gain access to network, but all working now.
Wondering what I can freeze in titanium so I don't get any forced OTA updates.
Cheers!

 

[ChazzMatt]

Chazz,
Thanks again ! I'm up and running on Verizon rooted with RR ROM by bhb27. Everything functional. While I was not able to use fastboot to flash files, I was able to drag and drop to system file with my PC after doing another clean wpe of everything except internal storage.
Then booted into TWRP recovery and installed the GApps, SuperSU,RR 7.0, and reflashed TWRP for good measure.
Added my Google account, got WiFi.
Installed the activated 1254 SIM card, and it took maybe 15 minutes for me to gain access to network, but all working now.
Wondering what I can freeze in titanium so I don't get any forced OTA updates.
Cheers!

Since RR doesn't have the stock firmware OTA framework, you won't receive any Motorola or Verizon OTA prompts.

With Nougat custom ROM, you are well past anything the XT1250, XT1254, XT1225 got from Motorola. XT1250 never got past Lollipop 5.0.2 and XT1225 /XT1254 never got past Marshmallow.

Sent from my LG-US998 using Tapatalk

 

[[email protected]]

MOTO MAXX

Quoted post by ChazzMatt,

Since RR doesn't have the stock firmware OTA framework, you won't receive any Motorola or Verizon OTA prompts.

With Nougat custom ROM, you are well past anything the XT1250, XT1254, XT1225 got from Motorola. XT1250 never got past Lollipop 5.0.2 and XT1225 /XT1254 never got past Marshmallow.

That's welcomed news indeed. No OTA to set things awry !
Yes you're right, my 1254 has MM, so I am past that.

Thanks for pointing that out !

 

[ChazzMatt]

MOTO CAMERA 6.0.91.19

We now have 6.0.91.19.


APK

I've followed another signing method: if you want to give it a try

MotoCamera_Mod_6.0.91.19V1: https://mega.nz/#!HJRHHQCY!WiaBjo6HlPjt4J2Xbch09eHbv7EwcLGjD1PMq6PO76g

VirusTotal (0/60): https://www.virustotal.com/#/file/d...f2daccf08bc31f7cbd3ca1bcbeabf1643b1/detection

TWRP FLASHABLE

Thanks.. the version seems to be working fine for me.
Also i made a Flashable Zip which have Sdcard save option,
Please test & let me know if it's working fine..

https://drive.google.com/open?id=1hgtTdoLlfYlMxH3T5vWz8Nyl2GgDapsq

 

[isnerdd]

i have a brazillian Moto Maxx (XT1225) and after trying everything to unlock bootloader i just dont stop recieving the "you does not qualify for bootloader unlocking" message. i already used data scrub to format my data but still gets the error. theres anything else i can do? maybe its because this phone is from TIM (Telecom Italia Mobile)? i have checked my CID and it is 0x000c, so it should be unlockable, right?

 

[ChazzMatt]

i have a brazillian Moto Maxx (XT1225) and after trying everything to unlock bootloader i just dont stop recieving the "you does not qualify for bootloader unlocking" message. i already used data scrub to format my data but still gets the error. theres anything else i can do? maybe its because this phone is from TIM (Telecom Italia Mobile)? i have checked my CID and it is 0x000c, so it should be unlockable, right?

Yes, should be able to unlock bootloader if it's XT1225.

If you get an error message at this step that your phone is not eligible, then you have typed in something wrong (or you have a Verizon Droid phone). Helps if you Google how to copy and paste from Windows command window. There's a LOT of alphanumeric characters you have to type. First time I tried to unlock my bootloader I mis-typed something. :crying: Copying and pasting from the Windows command window fixed that problem! :good:

You'll get an email with the bootloader unlock code. The email will also have a link back to the instructions. But the code is what's important.

You will receive this fairly instantly. If you don't get it, make sure you checkmarked you agree to all the conditions. Also check your spam folder.


Of the Quark series, only Verizon's Droid Turbo XT1254 is exempt from this free Motorola bootloader unlock and this guide is NOT for the Droid Turbo XT1254.

 

[isnerdd]

Yes, should be able to unlock bootloader if it's XT1225.

As i said, i already tried everything suggested here. I was looking up on Motorola's official list of suportes devices, and It seems that moto maxx/droid turbo are no longer supported on their unlock bootloader program since It isnt on the list, plus this statement on top of the website. I dont know why they wouldnt allow a device to be unlocked just for being old, but thats the only explanation.

 

[ChazzMatt]

As i said, i already tried everything suggested here. I was looking up on Motorola's official list of suportes devices, and It seems that moto maxx/droid turbo are no longer supported on their unlock bootloader program since It isnt on the list, plus this statement on top of the website. I dont know why they wouldnt allow a device to be unlocked just for being old, but thats the only explanation.

You need to forget about "official list of supported devices" -- Moto Maxx/Moto Turbo was never on any such list but still bootloader unlock worked just fine and probably still works. From the very first time I unlocked my two XT1225, it was never on any "list" and never has been. Just follow my instructions and it will work.

2 or 3 years ago someone complained it wasn't on the "supported list" and I laughed (about the list) just like I'm doing now. Then -- just as I cautioned in post #1 -- he hadn't typed the numbers correctly. Once he did it again, it worked. Like I said, I messed up the very first time myself.

 

[ChazzMatt]

Posting this here also as it's relevant...

iv gone to the service center and gotten the latest update installed but it is kindoff bugged and freezes a lot when I launch some apps
also i enabled the oem unlocking and am trying to unlock the bootloader but it says failed to get unlock data when i do fastboot get unlock data

Read my bootloader unlock guide (this thread here, see post #1). OEM bootloader unlock in Settings by itself does nothing, unless the OEM wants it to do something. This has always been true. In this case, Motorola is one of the OEMS who make you get a bootloader unlock code to actually unlock your bootloader; LG is another one that requires this. You request a bootloader unlock code and follow the steps in my guide.

 

[ChazzMatt]

Recovery Reboot app

Just added this to post #1:

STRONG SUGGESTION: After successfully unlocking bootloader, installing TWRP and rooting, when you finally boot back to stock firmware, install THIS app (needs root permission) to easily facilitate rebooting to TWRP recovery in the future. Recovery Reboot

While all the non-stock custom ROMs have reboot to (custom) recovery options in the the power menu, stock firmware does not. This is a great app to have to easily reboot to TWRP on a rooted phone.