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

[TheSt33v]

Yes. I did fail to mention that on a few of the file download occasions it gave me a 'file corrupt' msg when trying to open...but not the majority.

You were trying to open the image file? Why?

 

[ChazzMatt]

That's the error message given when the image you're trying to flash cannot be found by fastboot. Did you remember to put your image in c:\Program Files (x86)\Minimal ADB and Fastboot?

Yes. I did fail to mention that on a few of the file download occasions it gave me a 'file corrupt' msg when trying to open...but not the majority.

You were trying to open the image file? Why?

Yeah, @mtor9477, seems somewhere you are confused about the procedure.
Download TWRP IMG file from this @baybutcher27 link. It's the latest TWRP for Quark (August 8, 2016).

twrp-3.0.2-0-Mod_03-quark.img
DOWNLOAD:
https://www.androidfilehost.com/?fid=24665509702140399

It's an IMG file. There's NOTHING TO OPEN. That is the file you flash! Of course, you will need to re-name that img file to just TWRP.img -- but there's nothing to "open".

Move it to your ADB folder and flash it using the instructions.

"fastboot flash recovery TWRP.img"

 

[mtor9477]

You were trying to open the image file? Why?

I was trying to view it in my downloads folder to rename it to TWRP.img per the instructions when it gave me 'file corrupt' on a few occasions. All steps previous went without a hitch. Installed Sunshine with temproot and continued to step 2 (TWRP). I'm hung up here and unable to install the file. Gives me the error msg I showed earlier. ???

---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------

Yeah, @mtor9477, seems somewhere you are confused about the procedure.
Download TWRP IMG file from this @baybutcher27 link. It's the latest TWRP for Quark (August 8, 2016).

twrp-3.0.2-0-Mod_03-quark.img
DOWNLOAD:
https://www.androidfilehost.com/?fid=24665509702140399

It's an IMG file. There's NOTHING TO OPEN. That is the file you flash! Of course, you will need to re-name that img file to just TWRP.img -- but there's nothing to "open".

Move it to your ADB folder and flash it using the instructions.

"fastboot flash recovery TWRP.img"

So, I shouldn't be using the TWRP download link in the instructions? Are these one of the same that you referenced?

 

[ChazzMatt]

SUTL-49 or SUTL-44?

I was trying to view it in my downloads folder to rename it to TWRP.img per the instructions when it gave me 'file corrupt' on a few occasions. All steps previous went without a hitch. Installed Sunshine with temproot and continued to step 2 (TWRP). I'm hung up here and unable to install the file. Gives me the error msg I showed earlier. ???

But you kept saying you were trying to "open" it, which implies you were trying to unzip or something... You just need to re-name it. And the only reason you need to re-name it is to keep from having to type the LONG file name. You can actually re-name it ANYTHING, as long as you use that name in the fastboot command...

"fastboot flash recovery TWRP.img"

You can re-name it "X" in which case it would be

"fastboot flash recovery X.img"

__________

To be clear, you have unlocked your bootloader?

You said you installed Sunshine with temp root, but I would like to hear you say you actually unlocked your bootloader.

From the OP:

8. If, when your phone reboots, you see a "Warning: The bootloader is unlocked" message, you have successfully unlocked your bootloader. If you do not see this message, open Sunshine again and follow the directions again.

Are you using a DIFFERENT PHONE than this one you posted about just 5 days ago?

How can you edit the build.prop script without a rooted phone. I tried using Root Explorer with the -49 SU with no luck.

This is also the single most important use for my being rooted.... unfortunately, Verizon sent my warranty replacement yesterday with the new -49 SU. Have my fingers crossed that someone's willing enough to crack this.

You cannot unlock the bootloader of an SUTL-49 phone.
If you can't unlock the bootloader, you also can't install TWRP and root.
So, I trust you are using a different phone for this? A Droid Turbo XT1254 with SUTL-44? That's the only firmware that works with Sunshine to unlock the Droid Turbo bootloader.

________________

So, I shouldn't be using the TWRP download link in the instructions? Are these one of the same that you referenced?

The link I provided is the most up-to-date version of TWRP from our Quark TWRP developer. I have not checked what links are in this thread. If the most recent is not yet posted here, older versions will work also... But why not use the most up-to-date?

 

[mtor9477]

Thanks, I'll try the latest TWRP link you provided this evening. Not sure why I encountered problems with the TWRP files on from the link in Step 2 of the instructions.

Yes, my bootloader IS unlocked on a different new phone. Found an older version STL-39 on eBay.

 

[ChazzMatt]

And the only reason you need to re-name it is to keep from having to type the LONG file name. You can actually re-name it ANYTHING, as long as you use that name in the fastboot command...

"fastboot flash recovery TWRP.img"

You can re-name it "X" in which case it would be

"fastboot flash recovery X.img"

Thanks, I'll try the latest TWRP link you provided this evening. Not sure why I encountered problems with the TWRP files on from the link in Step 2 of the instructions.

Yes, my bootloader IS unlocked on a different new phone. Found an older version STL-39 on eBay.

OK, good.

The other thing is to make sure you type the entire command. One time I re-named the TWRP file as recovery.img and when I went to type the command

"fastboot flash recovery recovery.img"

I had a brain glitch and didn't type the word recovery twice.

 

[TheSt33v]

Thanks, I'll try the latest TWRP link you provided this evening. Not sure why I encountered problems with the TWRP files on from the link in Step 2 of the instructions.

Yes, my bootloader IS unlocked on a different new phone. Found an older version STL-39 on eBay.

The link in the guide is to the official TWRP website. It should work fine. The link that ChazzMatt provided is to the most recent version made by our TWRP maintainer. For reasons I don't understand, he can't incorporate his modifications into the official build. Either one should be good. That error message basically means fastboot either can't find the image you're talking about, or it checked it out and there's something wrong with it. My money is on corrupted download, which could mean an internet or browser issue.

 

[ChazzMatt]

OK, good.

The other thing is to make sure you type the entire command. One time I re-named the TWRP file as recovery.img and when I went to type the command

"fastboot flash recovery recovery.img"

I had a brain glitch and didn't type the word recovery twice.

Here's something else...

On Windows PCs the default Microsoft setting -- which is STUPID BEYOND BELIEF -- is to NOT show file extensions. First thing I do it enable showing file extensions: .jpg, .gif, .exe, .pdf, .bat, .img, etc.

It let a lot of virus writers sneak through files to teenage boys labelled "naked.jpg" -- but it was REALLY "naked.jpg".exe or "naked.jpg".bat . The virus writers included the ".jpg" part of the file name to fool people. That's NOT the extension! The REAL extension ".exe" or ".bat" was not visible, because most people don't know they should change Windows default settings. They think they are opening a picture file when they are really opening a malware executable file.

So, first thing I do on a Windows PC is enable view of file extensions.

OK, so what does that have to do with flashing recovery in fastboot?

For someone who has NOT enabled extensions view in Windows, if they rename the TWRP file as "TWRP.img", then they are REALLY re-naming it as TWRP.img.img -- because the file extension is already there (just hidden). And when you go to flash that file, TWRP.img file is not found -- because you've named it TWRP.IMG.img?

That may not be your problem, but just a thought...

 

[mtor9477]

Here's something else...

On Windows PCs the default Microsoft setting -- which is STUPID BEYOND BELIEF -- is to NOT show file extensions. First thing I do it enable showing file extensions: .jpg, .gif, .exe, .pdf, .bat, .img, etc.

It let a lot of virus writers sneak through files to teenage boys labelled "naked.jpg" -- but it was REALLY "naked.jpg".exe or "naked.jpg".bat . The virus writers included the ".jpg" part of the file name to fool people. That's NOT the extension! The REAL extension ".exe" or ".bat" was not visible, because most people don't know they should change Windows default settings. They think they are opening a picture file when they are really opening a malware executable file.

So, first thing I do on a Windows PC is enable view of file extensions.

OK, so what does that have to do with flashing recovery in fastboot?

For someone who has NOT enabled extensions view in Windows, if they rename the TWRP file as "TWRP.img", then they are REALLY re-naming it as TWRP.img.img -- because the file extension is already there (just hidden). And when you go to flash that file, "TWRP.img" is not found -- because you've named it TWRP.IMG.img?

That may not be your problem, but just a thought...

ChazzMatt, (*&^%$#@!!!!!...so, guess what my problem was? Yep, exactly what you mentioned...STUPID EXTENSION naming. I kicked my self in the arse for his one. You're right about not being used to the new Windows (guess I'm a dinosaur). Anyway, phone seems to have rooted fine now and I'm once again a happy camper.

Thank you ChazMatt, TheSt33v, and JCase!

---------- Post added at 12:45 AM ---------- Previous post was at 12:10 AM ----------

Guys, I just rooted a replaced Turbo and I'm noticing a problem I had with my previous where when trying to backup all my apps and data (or even one app, for that matter), TB is failing and giving me an error msg 'Backup Failed: Insufficient free storage space'. I checked my storage and it shows around 17GB, what gives?

Any idea what's goin on? TB is kind of a big deal to have workin correctly.

 

[TheSt33v]

ChazzMatt, (*&^%$#@!!!!!...so, guess what my problem was? Yep, exactly what you mentioned...STUPID EXTENSION naming. I kicked my self in the arse for his one. You're right about not being used to the new Windows (guess I'm a dinosaur). Anyway, phone seems to have rooted fine now and I'm once again a happy camper.

Thank you ChazMatt, TheSt33v, and JCase!

---------- Post added at 12:45 AM ---------- Previous post was at 12:10 AM ----------

Guys, I just rooted a replaced Turbo and I'm noticing a problem I had with my previous where when trying to backup all my apps and data (or even one app, for that matter), TB is failing and giving me an error msg 'Backup Failed: Insufficient free storage space'. I checked my storage and it shows around 17GB, what gives?

Any idea what's goin on? TB is kind of a big deal to have workin correctly.

That's a TiBu bug. I remember I had to deal with that a while back, but I don't remember how I fixed it. Just google what the error message says and you should be able to find the solution.

 

[sd_shadow]

ChazzMatt, (*&^%$#@!!!!!...so, guess what my problem was? Yep, exactly what you mentioned...STUPID EXTENSION naming. I kicked my self in the arse for his one. You're right about not being used to the new Windows (guess I'm a dinosaur). Anyway, phone seems to have rooted fine now and I'm once again a happy camper.

Thank you ChazMatt, TheSt33v, and JCase!

---------- Post added at 12:45 AM ---------- Previous post was at 12:10 AM ----------

Guys, I just rooted a replaced Turbo and I'm noticing a problem I had with my previous where when trying to backup all my apps and data (or even one app, for that matter), TB is failing and giving me an error msg 'Backup Failed: Insufficient free storage space'. I checked my storage and it shows around 17GB, what gives?

Any idea what's goin on? TB is kind of a big deal to have workin correctly.

try unchecking something like 'mount spaces' in supersu

Sent from my KFFOWI using XDA Labs

---------- Post added at 05:14 AM ---------- Previous post was at 05:09 AM ----------

This is due to the 'Mount namespace separation' setting in SuperSU being turned on (by default). Uncheck that, reboot and try Titanium Backup again.

This happens because of permissions to app-created folders being restricted in newer Android versions



Sent from my KFFOWI using XDA Labs

 

[Sparksys]

Is this method for free or do I need to pay 25$?

---------- Post added at 12:50 PM ---------- Previous post was at 12:45 PM ----------

I mean..is there another free method?

 

[mtor9477]

try unchecking something like 'mount spaces' in supersu

Sent from my KFFOWI using XDA Labs

---------- Post added at 05:14 AM ---------- Previous post was at 05:09 AM ----------

This is due to the 'Mount namespace separation' setting in SuperSU being turned on (by default). Uncheck that, reboot and try Titanium Backup again.

This happens because of permissions to app-created folders being restricted in newer Android versions



Sent from my KFFOWI using XDA Labs

Thanks, that worked! Un-check 'Mount namespace separation' in SU and reboot.

 

[TheSt33v]

Is this method for free or do I need to pay 25$?

---------- Post added at 12:50 PM ---------- Previous post was at 12:45 PM ----------

I mean..is there another free method?

The answer to your first question appears under the READ THIS FIRST section of the OP. The answer to your second question is no.

 

[ChazzMatt]

Is this method for free or do I need to pay 25$?
I mean..is there another free method?

The answer to your first question appears under the READ THIS FIRST section of the OP. The answer to your second question is no.

@Sparksys, blame Verizon for demanding Motorola lock down the bootloader for their Quark, the Droid Turbo XT1254. The XT1250 (clone, identical to the XT1254) and XT1225 (twin sibling to the XT1254, but different radio bands) can be unlocked via free code from Motorola website. Only Verizon's Moto Quark is locked down like this.

A year after Droid Turbo XT1254 release the Sunshine team found a Snapdragon 805-specific exploit which unlocked the bootloader on a certain version of Verizon firmware. They invested a lot of time and effort into finding this. Sunshine team deserves thanks for finding this. I mean, a whole year!

They also PUBLISHED the exploit, so anyone with good coding skills could replicate their work -- if anyone wanted. So, if anyone really wanted, they COULD do it for free. But the time and effort it would take, it's probably easier to just pay the $25.

Or you can buy the XT1250 U.S. Moto Maxx. Same phone, same FCC ID, same radio bands --unlock it for free, via Motorola.

 

[TheSt33v]

@Sparksys, blame Verizon for demanding Motorola lock down the bootloader for their Quark, the Droid Turbo XT1254. The XT1250 (identical to the XT1254) and XT1225 (sibling to the XT1254 but different radio bands) can be unlocked via free code from Motorola website.

A year after Droid Turbo XT1254 release the Sunshine team found a Snapdragon 805-specific exploit which unlocked the bootloader on a certain version of Verizon firmware. They invested a lot of time and effort into finding this. Sunshine team deserves thanks for finding this. I mean, a whole year!

They also PUBLISHED the exploit, so anyone with good coding skills could replicate their work -- if anyone wanted too.
So, if anyone really wanted they COULD do it for free. But the time and effort it would take, it's probably easier to just pay the $25.

Or you can buy the XT1250. Same phone, same FCC ID, same radio bands --unlock it for free, via Motorola.

I actually read team ninja's release detailing the bug and I thought to myself "this might be a fun excuse to go full dev and learn how to code and actually implement this." But then I didn't because I realized I don't want it to be free. I want sunshine to get all of the money because they deserve it. And also I'm lazy. But mostly the first reason.

 

[Sparksys]

@Sparksys, blame Verizon for demanding Motorola lock down the bootloader for their Quark, the Droid Turbo XT1254. The XT1250 (clone, identical to the XT1254) and XT1225 (twin sibling to the XT1254, but different radio bands) can be unlocked via free code from Motorola website. Only Verizon's Moto Quark is locked down like this.

A year after Droid Turbo XT1254 release the Sunshine team found a Snapdragon 805-specific exploit which unlocked the bootloader on a certain version of Verizon firmware. They invested a lot of time and effort into finding this. Sunshine team deserves thanks for finding this. I mean, a whole year!

They also PUBLISHED the exploit, so anyone with good coding skills could replicate their work -- if anyone wanted. So, if anyone really wanted, they COULD do it for free. But the time and effort it would take, it's probably easier to just pay the $25.

Or you can buy the XT1250 U.S. Moto Maxx. Same phone, same FCC ID, same radio bands --unlock it for free, via Motorola.

But I mean..25$ is so expensive for rooting
It should be 10$ or 15$ especially the Droid Turbo is now out for 2 whole years!
I agree that we should pay for the developers but that price is just too high!!
I guess I have to pay after all..I can't live without Root

and about the Moto Maxx..It's 130$ more expensive than the Droid Turbo on eBay for some reason..

 

[sd_shadow]

But I mean..25$ is so expensive for rooting
It should be 10$ or 15$ especially the Droid Turbo is now out for 2 whole years!
I agree that we should pay for the developers but that price is just too high!!
I guess I have to pay after all..I can't live without Root

They buy several devices, brick some of them, and spend countless hours/weeks trying different ways to unlock the bootloader.
It not rooting, it unlocking the bootloader

Sent from my XT1254 using XDA Labs

 

[ChazzMatt]

But I mean..25$ is so expensive for rooting
It should be 10$ or 15$ especially the Droid Turbo is now out for 2 whole years!
I agree that we should pay for the developers but that price is just too high!!
I guess I have to pay after all..I can't live without Root

Well, it's well known Verizon locks down their Droid phones. I even warned you about it before you bought it, when you were asking questions:

If you care about development, see if the the XT1254 bootloader is already unlocked. On the Droid Turbo XT1254 it can only be unlocked if it's on Verizon SUTL-44 firmware via $25 Sunshine exploit. If it's already on SUTL-49 and still locked, you are out of luck. The other Quarks have easily unlocked bootloaders via Motorola.

Can't say you didn't know.

Basically anyone who buys a Droid phone doesn't really care about unlocked bootloaders, and they are VERY lucky if a solution like Sunshine comes around. I'm not saying they don't want an unlocked bootloader -- I'm saying they buy it anyway, knowing it's locked down. This is why the Sunshine exploit was such a miracle, a year after release. By that time the Quark forums had already been split into the "active" forum (XT1225) and the "dead" forum (XT1254), with XT1250 sort of caught in between. THEN the bootloader exploit was released and the XT1254 could join the dev party!

There were people who complained and procrastinated for SIX MONTHS and took the SUTL-49 OTA. Now they can't unlock their bootloaders if they wanted to!

and about the Moto Maxx..It's 130$ more expensive than the Droid Turbo on eBay for some reason..

WHICH Moto Maxx -- the XT1250 or the XT1225?

The XT1225 is more expensive because not only does it have easily unlocked bootloader (like the XT1250), but it comes withy 64GB internal memorey AND ballistic nylon over kevlar back. It's top of the line in every regard -- memory storage and back cover, and dev potential.

I own three XT1225.

 

[Sparksys]

WHICH Moto Maxx -- the XT1250 or the XT1225?

The XT1225 is more expensive because not only does it have easily unlocked bootloader (like the XT1250), but it comes withy 64GB internal memorey AND ballistic nylon over kevlar back. It's top of the line in every regard -- memory storage and back cover, and dev potential.

I own three XT1225.

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