[GUIDE] How to unlock your bootloader, install TWRP and gain root access

[ChazzMatt]

Ok umm..
Droid turbo 64 gb verison is for 150$ while the 32 gb version which i bought was for 120$ with ballastic nylon back

However the Moto Maxx 64gb verison is for 260$
I knew it's the better version for unlocking the bootloader but it was 2x the price of the droid turbo

You keep saying just "Moto Maxx" . There's two - XT1250 and XT1225. I assume you mean only the XT1225. The U.S.Moto Maxx XT1250 is 32GB only. The "international" Moto Maxx XT1225 (also called Moto Turbo XT1225 in India) is 64GB only.

You were very lucky to get firmware not updated yet to SUTL-49 on your XT1254. Otherwise you would have permanent locked down phone.

Many in this forum would gladly trade phones with you to get the chance to unlock their XT1254 bootloader.

---

I'm just pointing out you knew the $25 fee before you bought the phone, because I did tell you.

If other Quark phones are even more expensive (with free bootloader unlock), then you still got a good deal!

 

[Sparksys]

You keep saying just "Moto Maxx" . There's two - XT1250 and XT1225. I assume you mean only the XT1225. The U.S.Moto Maxx XT1250 is 32GB only. The "international" Moto Maxx XT1225 (also called Moto Turbo XT1225 in India) is 64GB only.

You were very lucky to get firmware not updated yet to SUTL-49 on your XT1254. Otherwise you would have permanent locked down phone.

Many in this forum would gladly trade phones with you to get the chance to unlock their XT1254 bootloader.

---

I'm just pointing out you knew the $25 fee before you bought the phone, because I did tell you.

If other Quark phones are even more expensive (with free bootloader unlock), then you still got a good deal!

Yup you did tell me about the 25$ fee haha
And about the Moto Maxx both models have same price which is 250-270$

That's why I didn't buy any of them..because the droid turbo was waaay much cheaper..like a smartphone with these specs for 120$!! That's a steal haha

 

[ChazzMatt]

Yup you did tell me about the 25$ fee haha
And about the Moto Maxx both models have same price which is 250-270$

That's why I didn't buy any of them..because the droid turbo was waaay much cheaper..like a smartphone with these specs for 120$!! That's a steal haha

See, even with $25 you still got a good deal. Now change your XDA sig file to your new phone. "Sony Xperia Z3 Compact" needs to go. It's only 720p and you now have a 1440p AMOLED phone!

 

[TheSt33v]

Hey @ChazzMatt, out of pure curiosity, how do you unlock the bootloader of a Moto Maxx? I looked at the bootloader unlock eligibility list on Moto's website, and I couldn't find the Maxx there.

 

[ChazzMatt]

Hey @ChazzMatt, out of pure curiosity, how do you unlock the bootloader of a Moto Maxx? I looked at the bootloader unlock eligibility list on Moto's website, and I couldn't find the Maxx there.

I'm not sure why it's not currently listed. Even U.S. Moto Maxx XT1250 is eligible, so it's not because the international Moto Maxx XT1225 wasn't sold in the U.S. (It was sold in Puerto Rico, which is a U.S. territory -- which is one reason it had to undergo FCC testing.)

Go to this website.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

sign in and then provide Motorola with your device ID and receive a code.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b

You may not be able to see that page unless signed in. They tell you to download install Android SDK.

UNLOCK YOUR BOOTLOADER

STEP 2 - GET YOUR DEVICE ID & UNLOCK CODE

First ensure your device has the latest tools.

Install the Android SDK. Download here.
Install the latest Motorola USB Drivers on your desktop. Download here.

You paste the number in and it tells you whether your device can be unlocked or not. First time I missed typing a number or something and it said NO. :crying: I knew that couldn't be right, so I figured out how to copy and paste from Windows command window so I wasn't manually typing like 72 characters.

Then, got YES. I unlocked my XT1225. About a month later I got my 2nd one, which my wife now uses and unlocked it also. 3rd one is still in the box, but I may soon fire it up again and unlock it.

 

[TheSt33v]

I'm not sure why it's not currently listed. Even U.S. Moto Maxx XT1250 is eligible, so it's not because the international Moto Maxx XT1225 wasn't sold in the U.S. (It was sold in Puerto Rico, which is a U.S. territory -- which is one reason it had to undergo FCC testing.)

Go to this website.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

sign in and then provide Motorola with your device ID and receive a code.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b

You may not be able to see that page unless signed in. They tell you to download install Android SDK.



You paste the number in and it tells you whether your device can be unlocked or not. First time I missed typing a number or something and it said NO. :crying: I knew that couldn't be right, so I figured out how to copy and paste from Windows command window so I wasn't manually typing like 72 characters.

Then, got YES. I unlocked my XT1225. About a month later I got my 2nd one, which my wife now uses and unlocked it also. 3rd one is still in the box, but I may soon fire it up again and unlock it.

Hmm. So I guess the short answer is even though it isn't listed, it's still eligible, and you unlock it the same was as any other phone on that list.

 

[Claps1775]

I followed your section 2 instruction. I am getting this.
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
XXXXXXXXX fastboot

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
(bootloader) has-slot:recovery: not found
error: cannot load 'TWRP.img'

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
(bootloader) has-slot:recovery: not found
error: cannot load 'TWRP.img'

C:\Program Files (x86)\Minimal ADB and Fastboot>

 

[TheSt33v]

I followed your section 2 instruction. I am getting this.
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
XXXXXXXXX fastboot

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
(bootloader) has-slot:recovery: not found
error: cannot load 'TWRP.img'

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
(bootloader) has-slot:recovery: not found
error: cannot load 'TWRP.img'

C:\Program Files (x86)\Minimal ADB and Fastboot>

This error indicates that Fastboot cannot find the file. So either you didn't move the file into the correct folder, or you don't have the windows option checked to show you file extensions, which caused you to name the file "twrp.img.img" without you realizing it. A few posts ago in this thread, someone else had the same problem. Perhaps his solution may work for you as well.

 

[ChazzMatt]

I followed your section 2 instruction. I am getting this.
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
XXXXXXXXX fastboot

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
(bootloader) has-slot:recovery: not found
error: cannot load 'TWRP.img'

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
(bootloader) has-slot:recovery: not found
error: cannot load 'TWRP.img'

C:\Program Files (x86)\Minimal ADB and Fastboot>

Read posts 308 and 309 and verify you can see all file extensions.

 

[Claps1775]

I open a folder and enabled file extensions. That was my problem. Now, I am getting this.
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
XXXXXXXXX fastboot

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14208 KB)...
OKAY [ 0.456s]
writing 'recovery'...
OKAY [ 0.207s]
finished. total time: 0.668s

C:\Program Files (x86)\Minimal ADB and Fastboot>
I reboot phone and after I shut down and rebooted into recovery. I am still on stock recovery. I have not activated my phone with Verizon yet as I need a phone till I can use my Turbo. I have set up my phone. I am not sure what is wrong now. I have also tried it again and same outcome. Stock recovery. I must be over looking something.

 

[Claps1775]

I do have the developer option and usb debugging checked.

 

[TheSt33v]

I open a folder and enabled file extensions. That was my problem. Now, I am getting this.
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
XXXXXXXXX fastboot

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14208 KB)...
OKAY [ 0.456s]
writing 'recovery'...
OKAY [ 0.207s]
finished. total time: 0.668s

C:\Program Files (x86)\Minimal ADB and Fastboot>
I reboot phone and after I shut down and rebooted into recovery. I am still on stock recovery. I have not activated my phone with Verizon yet as I need a phone till I can use my Turbo. I have set up my phone. I am not sure what is wrong now. I have also tried it again and same outcome. Stock recovery. I must be over looking something.

Do not reboot normally after flashing twrp. Reboot directly to recovery by selecting recovery from the bootloader menu on the phone. After the first TWRP boot, it will be there permanently.

 

[Claps1775]

Do not reboot normally after flashing twrp. Reboot directly to recovery by selecting recovery from the bootloader menu on the phone. After the first TWRP boot, it will be there permanently.

When using the restart bootloader on the phone. It reboots into stock recovery. I do not get no TWRP anything. On the stock recovery. Says, AB Fastboot Flash Mode (Secure) Does that mean anything?

---------- Post added at 11:33 AM ---------- Previous post was at 11:17 AM ----------

I got it. Wow, I just needed to reread and try again. I selected recovery and I am in TWRP right now. I really am not sure why I selected Restart Bootloader. Thank you for your help @TheSt33v and @ChazzMatt.
File extensions enable check
Rename file to TWRP.img check
Flash recovery check
Select Recovery Mode on phone check
Booted into TWRP check
Ahhh check

---------- Post added at 11:34 AM ---------- Previous post was at 11:33 AM ----------

I got it. Wow, I just needed to reread and try again. I selected recovery and I am in TWRP right now. I really am not sure why I selected Restart Bootloader. Thank you for your help @TheSt33v and @ChazzMatt.
File extensions enable check
Rename file to TWRP.img check
Flash recovery check
Select Recovery Mode on phone check
Booted into TWRP check
Ahhh check

 

[doubledragon5]

Ok can't flash twrp.img I get this error

<bootloader> has-slot:recovery: not found

error: can not load twrp.img

 

[ChazzMatt]

Ok can't flash twrp.img I get this error

has-slot:recovery: not found

error: can not load twrp.img

Please make sure you have viewing extensions enabled in Windows. That's the common mistake everyone keeps making, keeping Windows silly default settings.

Go back and read post 309.
http://forum.xda-developers.com/showpost.php?p=68222204&postcount=309

You probably named it TWRP.IMG.img because you couldn't see the extension already on the file name. And ADB can't find it because it's looking for TWRP.img.

 

[doubledragon5]

Please make sure you have viewing extensions enabled in Windows. Everyone keeps screwing that up.

Go back and read like post 309.

You probably named it TWRP.IMG.img because you couldn't see the extension already on the file name. And ADB can't find it because it's looking for TWRP.img.

Thank you that did the trick.. Never new that about windows.. Last time I used Flashy to install twrp...

 

[ChazzMatt]

Thank you that did the trick.. Never new that about windows.. Last time I used Flashy to install twrp...

First time I mentioned it, it was just a guess. But you are the third person in this thread less than two weeks to not have extensions view enabled in Windows. I understand that's Microsoft's silly default setting -- but I've never understand why it's the default setting, as it only hurts Microsoft and hurts customers if people click on malware disguised as something else. If you can't see the complete file name, it could be anything. And there's ways malware writers can use to disguise the associated "icon" -- but if you see the complete file name, there's no way to disguise that extension -- oh, except if Microsoft HIDES it from you!

First thing I do on a new computer (or even a friend's computer I sit down to use) is enable file extensions view. I NEED to see .pdf, .doc, .exe, .xls, .jpg, .png, .php, etc. I don't understand why Microsoft wants to hide that from their customers. Give me 15 minutes with Microsoft's Windows Master copy in a locked room and there's several stupid Windows "default" settings I would change.

 

[dwh2o13]

So when I fastboot flash twrp should the command be "fastboot flash recovery TWRP.img.img" if I have renamed the file to TWRP.img as recommended in the guide? Or, could I just type in "fastboot flash recovery" then just drag the original downloaded twrp file w/o renaming into the command prompt

Sent from my XT1254 using Tapatalk

 

[Claps1775]

So when I fastboot flash twrp should the command be "fastboot flash recovery TWRP.img.img" if I have renamed the file to TWRP.img as recommended in the guide? Or, could I just type in "fastboot flash recovery" then just drag the original downloaded twrp file w/o renaming into the command prompt

Sent from my XT1254 using Tapatalk

You need to enable the file extensions. Happen to me. Do not put .IMG after the when you rename it. Yes, it will me .IMG.img. I went through it all. Hehe.

 

[ChazzMatt]

So when I fastboot flash twrp should the command be "fastboot flash recovery TWRP.img.img" if I have renamed the file to TWRP.img as recommended in the guide? Or, could I just type in "fastboot flash recovery" then just drag the original downloaded twrp file w/o renaming into the command prompt

Sent from my XT1254 using Tapatalk

You need to enable the file extensions. Happen to me. Do not put .IMG after the when you rename it. Yes, it will me .IMG.img. I went through it all. Hehe.

Yes, just follow the guide. That's why we have it. It works.

And make file extensions visible so you know what the real file name is!