Database Users

[Q] Unlocking vs rooting

Potential first time Nexus user coming over from Desire Z.
I intend to transfer my old data from my DZ to the nexus4 when I get it via Titanium Backup. My DZ is rooted with S-off, so it's all good.
I've stumbled over instructions on how to unlock the nexus4 via ABD, but if I'm not wrong, that's only to allow flashing of custom bootloaders and ROMs, right?
Which is to say, unlocking != rooting, and in order for Titanium Backup to work properly, the n4 will have to be rooted as well as SU, busybox etc installed.
Am I on the right track?
Cheers.

nexus come unlock.
unlock = to be use with any carrier
rooting = giving beyond standard permissions such as changing how android does things. EG overclocking, changing your sound "quailty" etc and you said. TB (titanium backup)

Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.

Unlawful said:
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
Click to expand...
Click to collapse
Thanks Unlawful. Yes, I meant bootloader unlocking.
Unlawful said:
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Click to expand...
Click to collapse
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.

endlesstrail said:
Thanks Unlawful. Yes, I meant bootloader unlocking.
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
I doubt it. Be cool if it did
Once you have it unlocked you enter the recovery mode and root it there. I'm probably guessing shortly after its release someone is going to make a program so it does it in few steps.
There won't be anything really out that really requires root, other than TB.

endlesstrail said:
Thanks Unlawful. Yes, I meant bootloader unlocking.
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
Nexus 4 does not come rooted. You have to root it.

NeverAlwaysEver said:
Nexus 4 does not come rooted. You have to root it.
Click to expand...
Click to collapse
Thanks guys. I guessed as much.
Yeah, I'll probably have to do without the backup of my apps for a few days until some kind soul manages to root it and posts instructions. Maybe it'll just be a day or a few hours even! :fingers-crossed:

You will be able to unlock the bootloader right away.
Root maybe not. In order to root it you will need either need a custom recovery for the device or a software exploit.
It won't take long but a custom recovery needs to be built and tested first.

It's easy to root a nexus
First you unlock the bootloader=fastboot oem unlock.
Then you use fastboot to flash a recovery. Once recovery is flashed you have to use adb to make it stick(delete the script that overwrite custom recovery with stock) then you flash su. Zip in recovery. Very simple to do
Sent from my SCH-I535 using xda premium

Unlawful said:
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Click to expand...
Click to collapse
Just want to clarify, I have not had a nexus device before, but my understanding is that, even on a Nexus, without unlocking the bootloader, one would still need to exploit and mount system as RW first to install SU.

USSENTERNCC1701E said:
Just want to clarify, I have not had a nexus device before, but my understanding is that, even on a Nexus, without unlocking the bootloader, one would still need to exploit and mount system as RW first to install SU.
Click to expand...
Click to collapse
Without unlocking the bootloader, it's much more difficult to root and as you said, one would need to use an exploit and then do as you have said. However, Nexus devices do come with the luxury of unlockable bootloaders for a multitude of reasons .
endlesstrail said:
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
I think Chainfire meant that in case you wanted to switch from Superuser to SuperSU or if you're just installing the APK (the application). If you do want to root, you should just flash the zip file found here in a custom recovery which does everything for you.

Unlawful said:
Without unlocking the bootloader, it's much more difficult to root and as you said, one would need to use an exploit and then do as you have said. However, Nexus devices do come with the luxury of unlockable bootloaders for a multitude of reasons .
Click to expand...
Click to collapse
Thanks. Bytheby, my only experience in the past with non-hack bootloader unlocking is with HTCunlock. Have past nexus devices had a permanent watermark even after relocking? I'm hoping that's not the case, cause extensive googling does not have anyone explicitly saying one way or the other, so maybe only HTC is that jacked.

I just want to clear up some terminology to stop people getting confused...
Bootloader a.k.a HBoot - This is the piece of software that runs before anything else on the phone. It basically packages it all up, tells what to run in what order e.t.c Every computer device has a bootloader in some form or another, be it an Android Phone, iPhone, Windows PC, iMac e.t.c. The HBoot is accessible by switching your phone off, then holding down volume down as you turn it back on. The first line of the HBoot will tell you if you are S-OFF or S-ON.
Recovery - The recovery is the piece of software that allows us to write files to partitions while they aren't being used. It is the portal to allow us to flash custom ROM's and kernels. There are custom recoveries with more options than the stock such as ClockworkMod.
Superuser a.k.a su or Root - This is a user that is present on all linux distros that allows higher permissions than standard users have access to. Certain apps need superuser permissions to function, such as Titanium Backup.
A bootloader is traditionally locked. This means it stops you from writing to any partition on the device other than data. What is always true of Nexus devices, and now true of most consumer devices, there is an offical method for unlocking the bootloader. With HTC, you have to download some software, with Nexus devices, it is as simple as booting into fastboot mode, and typing the command "fastboot oem unlock" (assuming you have fastboot installed on your connected PC / mac).
Although this unlocks the bootloader (which by the way resets your device to factory settings), you still aren't rooted. You now have the ability to flash images to the previously locked partitions. Once you have access to write to partitions, the easiest method of rooting is installing a custom recovery (fastboot flash recovery recovery.img, and then using that to flash a superuser zip.
There are exploits for rooting, which either eman the recovery partition gets written to without the bootloader unlocking OR the su files get pushed to the system partition while the bootloader is locked. These exploits are more tricky and are getting harder to find, but allow you to gain root access without voiding your warranty.
To answer someone else's question, when you unlocked the bootloader on the Nexus One you got a watermark on the bootsplash, I don't know about any Nexus after that.
EDIT - Unlocked Phone: To throw some further clarification, when people talk about "unlocked phones" what they actually means is carrier. This term pre-dates smartphones, and a locked phone just meant that if you bought your phone through a carrier, you could only use it on their network, so no other SIM would work unless you bought a code off them to unlock it. This only applied to GSM phones (not CDMA) and s still practised today. The Nexus 4 will not be carrier locked wherever you buy it.

l0st.prophet said:
I just want to clear up some terminology to stop people getting confused...
Click to expand...
Click to collapse
Thanks for the excellent clarification. It's much clearer now.

USSENTERNCC1701E said:
Thanks. Bytheby, my only experience in the past with non-hack bootloader unlocking is with HTCunlock. Have past nexus devices had a permanent watermark even after relocking? I'm hoping that's not the case, cause extensive googling does not have anyone explicitly saying one way or the other, so maybe only HTC is that jacked.
Click to expand...
Click to collapse
Both the Galaxy Nexus and the Nexus 7 don't have anything changed when you unlock the bootloader (apart from an unlocked lock image on the boot screen beneath the Google logo and then it disappears after going to the boot animation). I would assume this was the same with the Nexus S . Also another good thing about Nexus devices is that you can relock the bootloader after unlocking it and it will be back to a stock configuration (assuming you're on the Google-built ROM).

PlanBSTi said:
There won't be anything really out that really requires root, other than TB.
Click to expand...
Click to collapse
I beg to differ; DroidWall is the one utility I refuse to live without, and that requires root.
Other than that and TitaniumBackup though, you're quite right; the new stock features of JellyBean mean I likely won't even bother with any major third-party modifications. Indeed, I'm thinking this'll be the first 'phone in many a year which I won't be installing a custom ROM on for at least the first six months of use.

PlanBSTi said:
There won't be anything really out that really requires root, other than TB.
Click to expand...
Click to collapse
Lol, the irony is I really only use TB because I'm switching ROMs. I disagree though, I really like the extra customization that comes with a lot of custom ROM's. But I've run phones for a few months with OEM skins, while waiting on an exploit. I agree there won't be a pressing need for root.

I guess you guys like to actually see ads on your phones.

albundy2010 said:
I guess you guys like to actually see ads on your phones.
Click to expand...
Click to collapse
I actually don't find many apps to have very intrusive ads at all. I also feel better knowing I'm not ripping off the devs

albundy2010 said:
I guess you guys like to actually see ads on your phones.
Click to expand...
Click to collapse
I've never actually ended up with an air push app, and the rest of the ads really don't bother me, sometimes I'll go on a clicking spree to support devs. If it really bothers me I buy the full version or uninstall it.

How to Root with Minimum Impact

Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?

You'll need adb/fastboot + the appropriate drivers.
-unlock BL via fastboot,
-flash recovery via fastboot,
-flash SU zip via recovery,
-leave BL unlocked, no reason to relock it.
That's it. Don't remove, or rename any system apps if you want the OTA to apply. You can even flash OTA's via a custom recovery, this will likely be available here prior to you getting a notification.
Good info here: http://forum.xda-developers.com/showthread.php?t=2010312

So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.

mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You know when you are on other phones, you are actually unlocking the bootloader via a exploit or through the manufacturers developer center.
You need a custom recovery in order to obtain root. It is a must need, without it you cannot be rooted.
Only way to change your recovery is to unlock the bootloader. Having a locked bootloader locks it so your recovery can't be changed. So.... You get the idea
Sent from my Nexus 4 using xda premium

mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You can do it via adb with an insecure boot image, outlined here below the CWM method: http://forum.xda-developers.com/showthread.php?t=1993331&highlight=insecure
If you do it the CWM, or TWRP way you can flash the stock recovery again. You absolutely have to unlock the bootloader however, no way around that.
CF Root is another option: http://forum.xda-developers.com/showthread.php?t=2025274

i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.

phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.

threeclaws said:
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
Click to expand...
Click to collapse
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.

phermey said:
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
Click to expand...
Click to collapse
I also could drop it into dropbox but that is all more work than just hitting "install" on my phone, it isn't like updates are released with enough frequency that the amount of work matters but like I said OTA is more convenient for me and CWM made it even more convenient. The OP may have completely different reasons for wanting OTA.

phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.

ORStoner said:
Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
Click to expand...
Click to collapse
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688

phermey said:
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
Click to expand...
Click to collapse
I wasn't being a smart ass nor was I unaware of other ways to get an OTA update, you said there was no reason for OTA on a nexus device and I responded why someone would want it.

clockcycle said:
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
Don't use toolkits take the time and learn how to do it yourself so if you get into situations where you messed something up you know how to fix it as you know how adb and fast boot will work.
Toolkits are not worth the short cut
Sent from my Nexus 4 using xda premium

Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium

ORStoner said:
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is the best way to do it. Yes you can fastboot boot cwm so it'll be temp and just install supersu zip. Regarding warranty for bootloader, it originally came locked so should you need to return it, warranty will be voided if you unlock it. However, it would really be just fastboot oem lock if you need to relock it. The state won't show relocked if you do it. It'll be plain locked
Sent from my Nexus 7 using Tapatalk 2

[Q] Another Rooting Question

The majority of my phones have been HTC so not really sure if unlocking the bootloader is normal procedure for a Motorola phone to obtain root. So i have a couple of questions on rooting this device, I'm happy to stay on a rooted stock so don't really see the point/need of unlocking the bootloader at this time.
1) Do you have to unlock the bootloader to root? or is there a method to root without unlocking the bootloader.
2) If the bootloader does get unlocked can it be relocked at a later date and would it show it had been unlocked?
Thanks in advance.

rnscotch said:
1) Do you have to unlock the bootloader to root? or is there a method to root without unlocking the bootloader.
Click to expand...
Click to collapse
Yes, at this time there's no way to obtain root without unlocking the bootloader.
rnscotch said:
2) If the bootloader does get unlocked can it be relocked at a later date and would it show it had been unlocked?
Click to expand...
Click to collapse
It can be relocked but then it'll be just "re-locked" not "locked", that means it'll have a different status.

Also note that you void the warranty just by obtaining the unlock code from Motorola; it doesn't matter if you've actually applied it to your device

If I unlock the bootloader and root, will I lose OTA updates, right? So, if I do this, how will I update to Marshmallow, when it's available?

LuizHenrique91 said:
If I unlock the bootloader and root, will I lose OTA updates, right? So, if I do this, how will I update to Marshmallow, when it's available?
Click to expand...
Click to collapse
With root you'll lose ota updates if I'm not wrong, but you can always flash the updated full firmware through fastboot or rsd.

If you're rooted, you're free to install any ROM you like. The Devs here at XDA got your back when it comes to updates. Every time the latest Android version came out for my past 2 devices I got it through ROMs from here way quicker than the carriers delivered it. That's not certain for every device, especially older ones, but it's up to you.
I will say since Motorola has kept the Android OS "pure," there may be a chance that this device gets Android M fairly quickly. However in my experience, developers on XDA seem to be able to squash the bugs so much quicker than the carriers.
Good luck in whatever you decide. Myself, I haven't unlocked or rooted since I just got this phone a few days ago. I'm keeping an eye on the forums to see some more ROMs come into play and the tweaking to be more common place with solid procedures. Though, I am itching to root just to get a working LED light. I'm not crazy about this Moto Display that blinks once with a notification and if I missed the blink, I never know something is waiting for me.

eskamhl said:
With root you'll lose ota updates if I'm not wrong, but you can always flash the updated full firmware through fastboot or rsd.
Click to expand...
Click to collapse
But if I flash the full firmware with the new version, I'll need to install the recovery and root again or will the phone stay rooted?
---------- Post added at 04:30 PM ---------- Previous post was at 04:28 PM ----------
ooklathemok said:
If you're rooted, you're free to install any ROM you like. The Devs here at XDA got your back when it comes to updates. Every time the latest Android version came out for my past 2 devices I got it through ROMs from here way quicker than the carriers delivered it. That's not certain for every device, especially older ones, but it's up to you.
I will say since Motorola has kept the Android OS "pure," there may be a chance that this device gets Android M fairly quickly. However in my experience, developers on XDA seem to be able to squash the bugs so much quicker than the carriers.
Good luck in whatever you decide. Myself, I haven't unlocked or rooted since I just got this phone a few days ago. I'm keeping an eye on the forums to see some more ROMs come into play and the tweaking to be more common place with solid procedures. Though, I am itching to root just to get a working LED light. I'm not crazy about this Moto Display that blinks once with a notification and if I missed the blink, I never know something is waiting for me.
Click to expand...
Click to collapse
Yes.. I'm considering to root mine X Play for be able to change the kernel and get the LED working (and maybe some optimizations). It's not prioritary, but I want. I won't install a custom ROM, because I like Moto Voice to much and I know we lost it.

LuizHenrique91 said:
But if I flash the full firmware with the new version, I'll need to install the recovery and root again or will the phone stay rooted?
Click to expand...
Click to collapse
Of course in that case you'll need to install the recovery and root, but as ooklathemok said you'll be able to update through a stock rooted rom simply from recovery

How do I fix this problem
So I fastboot stock firmware for my xt1563 from a rooted rim 6.0 to 5.1
And it all went good until I seen I lost root and recovery
So I re booted to bootloader and flashed
Fastboot flash recovery recovery img
Said okay and installed
I rebooted os
Then rebooted bootloader
Tried to go to recovery mode and the little android dude was there and below him says no command
What am I going wrong

deaksfrost said:
How do I fix this problem
So I fastboot stock firmware for my xt1563 from a rooted rim 6.0 to 5.1
And it all went good until I seen I lost root and recovery
So I re booted to bootloader and flashed
Fastboot flash recovery recovery img
Said okay and installed
I rebooted os
Then rebooted bootloader
Tried to go to recovery mode and the little android dude was there and below him says no command
What am I going wrong
Click to expand...
Click to collapse
Do not reboot to OS after flashing recovery, just reboot to recovery. If you reboot to OS after flashing twrp the stock Rom will over write recovery

Do Custom OS support Active/Moto Display and Moto voice?

yekollu said:
Do Custom OS support Active/Moto Display and Moto voice?
Click to expand...
Click to collapse
No, custom Roms do not support moto voice nor will they ever. Active display is all custom Roms provide.
This is my second moto x, I had the original moto x from 2013 and hated moto display.

Android 6.0 Marshmallow

Dumb question, but I'll ask anyway if I root will I not be able to receive OTA updates? Because I know whenever I did that with my Note 4 that if I tried it would give a message saying operating system is modified or something in that nature.

joe1blue said:
Dumb question, but I'll ask anyway if I root will I not be able to receive OTA updates? Because I know whenever I did that with my Note 4 that if I tried it would give a message saying operating system is modified or something in that nature.
Click to expand...
Click to collapse
You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool and take the ota them reroot
2) Wait for a flash able zip to become available.

TrenchKato said:
2) Wait for a flash able zip to become available.
Click to expand...
Click to collapse
Which will most likely be faster available than waiting for the OTA.

I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work. Remember that on the Note 4, et al, unlocking the bootloader wasn't supported by the OEM or carrier. Since Moto is supplying the unlock codes, I suspect that OTA updates will not be disabled on the MXPE as long as no other OS changes are made. I could be wrong, but we'll find out when the time comes.

Tanker Bob said:
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work. Remember that on the Note 4, et al, unlocking the bootloader wasn't supported by the OEM or carrier. Since Moto is supplying the unlock codes, I suspect that OTA updates will not be disabled on the MXPE as long as no other OS changes are made. I could be wrong, but we'll find out when the time comes.
Click to expand...
Click to collapse
Chances are, if you unlocked your bootloader, you flashed a custom recovery. You can't take an OTA through a custom recovery -- not because it's "blocked," but because the OTA tool is not written to work with that recovery.

Could be. Easy enough to fix if so. Just tell TWRP to allow the OS to overwrite it, the reflash TWRP after the update.

Can't you just flash the stock recovery to take the OTA? Sure, you'll lose root, but you could still take the OTA, then flash your custom recovery again. Is there anything, other than a stock recovery, that prevents OTA updates?
I wish we had a release date. Getting excited for the new features. Should have kept my Nexus 5!

jonathanbailie said:
Can't you just flash the stock recovery to take the OTA? Sure, you'll lose root, but you could still take the OTA, then flash your custom recovery again. Is there anything, other than a stock recovery, that prevents OTA updates?
I wish we had a release date. Getting excited for the new features. Should have kept my Nexus 5!
Click to expand...
Click to collapse
A modified system will prevent the install. You would need to flash the system image as well.
Sent from my XT1575 using Tapatalk

I know some owners rooted their device for different reasons other than roms, but imo better to wait for 6.0 for OTA first. This phone comes with pure Android rom. Not like you need to remove bloat apps. Just need custom roms and kernels which is slow developing. Maybe the devs don't want to waste time with lp and their also waiting for marshmallow. I'm surprised how slow this device is moving under development. Oneplus one didn't have mass sale but their development was quick. Being so similar with nexus 6, hopefully we can get some love with MXP.
Sent from my XT1575 using XDA Free mobile app

I have been holding out on unlocking for this reason. I'm lazy and don't want to set everything up again so I will use Marsh to back everything up first then I will go to town

Tanker Bob said:
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work.
Click to expand...
Click to collapse
OTA will not work for rooted MXPE's.
1) Rooting the MXPE requires you to load an alternative recovery (TWRP), which doesn't work with the OTA installation scripts.
2) Rooting the MXPE modified /system files. And OTA updates check /system integrity before it runs the update. Rooted phones will fail that integrity check, and will fail to OTA for that reason.
You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA. I'm sure that most people will do that, and then re-install TWRP and re-root after that is done. However, I'd recommend you wait a bit for other people to try this first, just in case there are any issues and to verify that root is still available in Android Marshmallow 6.0

Makes sense. Somebody has to be first. I will do a nandroid backup before attempting to update by any means.

Prior comments in this thread:
"You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool..."
and
"You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA..."
I just wanted to clarify that the Return to Stock tool does not currently remove TWRP...
Factory image will appear here once available: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
(Must log in with Motorola registered ID or gmail address)
Keep in mind you will see a Moto X (2nd Gen) Pure Edition already there...that is not ours.

hijax2001 said:
Prior comments in this thread:
"You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool..."
and
"You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA..."
I just wanted to clarify that the Return to Stock tool does not currently remove TWRP...
Factory image will appear here once available: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
(Must log in with Motorola registered ID or gmail address)
Keep in mind you will see a Moto X (2nd Gen) Pure Edition already there...that is not ours.
Click to expand...
Click to collapse
More clarification: Restore-To-Stock-Tool does replace TWRP. Have a gander inside the zip. I spy recovery.img within. What do you see?

PiousInquisitor said:
More clarification: Restore-To-Stock-Tool does replace TWRP. Have a gander inside the zip. I spy recovery.img within. What do you see?
Click to expand...
Click to collapse
Yup, you're correct ... I just used the tool earlier today and I do indeed have stock recovery.
Sent from my XT1575 using Tapatalk

Sharing my experience... good it's supposed to. Didn't for me, for some reason, until 2nd power cycle. It is stock recovery now though. Sorry for the confusion.

[Root && Unlock] Droid Turbo 6.0.1 mcg24.251-5-5

@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
fastboot oem config fsg-id " "
Click to expand...
Click to collapse
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.

jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
@jcase, please clarify...
Do you mean mcg24.251-5 or mcg24.251-5-5 (with extra -5 at the end?) The one with the extra -5 at the end (mcg24.251-5-5) is the most current Verizon Droid Turbo firmware (released March 2017) which did NOT work with Sunshine. Whereas mcg24.251-5 (with only one -5) already does work with Sunshine.

ChazzMatt said:
@jcase, please clarify...
Do you mean mcg24.251-5 or mcg24.251-5-5 (with extra -5 at the end?) The one with the extra -5 at the end (mcg24.251-5-5) is the most current Verizon Droid Turbo firmware (released March 2017) which did NOT work with Sunshine. Whereas mcg24.251-5 (with only one -5) already does work with Sunshine.
Click to expand...
Click to collapse
mcg24.251-5-5

Fantastic. Yeah, I figured that had to be typo.
Will make a lot of people happy.

I will try now

KARIM9377 said:
I will try now
Click to expand...
Click to collapse
Yes, great news, right?

jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
So just to be clear, the correct method would be to install sunshine, install temproot per the instructions that you linked to, sunshine it up, and uninstall the temproot by performing fastboot oem config fsg-id "" ?

TheSt33v said:
So just to be clear, the correct method would be to install sunshine, install temproot per the instructions that you linked to, sunshine it up, and uninstall the temproot by performing fastboot oem config fsg-id "" ?
Click to expand...
Click to collapse
i would assume you could install sunshine apk before or after temproot. does not matter which.
boot using temproot.
sunshine it up.
fastboot oem config fsg-id ""
if you dont run fastboot oem config fsg-id "" afterwards the phone will boot loop.
for those not planning on using sunshine and just want root there are alternative methods in post #2 of the temproot thread for avoiding the boot loop without needing to be near a computer.

Oh My Lord. @jcase and @autoprime do it again! Even though mine is unlocked my replacement 32gb isnt and this may make me buy a new screen for it to use! Looks like i know what im doing on my day off tomorrow. Transplanting this screen back onto its orginal donor and unlocking that sucker

autoprime said:
i would assume you could install sunshine apk before or after temproot. does not matter which.
boot using temproot.
sunshine it up.
fastboot oem config fsg-id ""
if you dont run fastboot oem config fsg-id "" afterwards the phone will boot loop.
for those not planning on using sunshine and just want root there are alternative methods in post #2 of the temproot thread for avoiding the boot loop without needing to be near a computer.
Click to expand...
Click to collapse
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?

TheSt33v said:
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
Click to expand...
Click to collapse
no, pressing volume down or vol dwn + pwr should not interfere with sunshine.
whichever method people find easier.. i'd assume not everyone will be able to catch it on the initial reboot after sunshine completes.
i'd just avoid pressing buttons while sunshine is still running.. but once the screen shuts off have at it.
also, not sure how it is with the turbo but on my g4 play i do not have to force a 'power down' while phone is in bootloop. i just wait for bootloop cycle to turn screen off and then quickly press the button combo to go into fastboot (volume down + power for g4 play).

Great was to slow and now I have a bootloop. Restarted to fastboot but ADB can not find the device. Can anybody help me with the next steps. Bootloader is unlocked so all that is left now is getting the device to boot.
Figured it out myself!
Once you have a bootloop restart into fastboot and open up the the fastboot folder in "auto-initroot_xt1254_quark_vzw_mcg24.251-5-5".
Then open up a command promp and issue the => fastboot.exe oem config fsg-id "" command. That's all!
Thanks a lot to JCase and his team for developing this hack!
BRB installing lots of ****

FYI @TheSt33v...
Haven't read your updated instructions, but this may be something worth mentioning if you haven't already.
killer520 said:
Great was to slow and now I have a bootloop. Restarted to fastboot but ADB can not find the device. Can anybody help me with the next steps. Bootloader is unlocked so all that is left now is getting the device to boot.
Figured it out myself!
Once you have a bootloop restart into fastboot and open up the the fastboot folder in "auto-initroot_xt1254_quark_vzw_mcg24.251-5-5".
Then open up a command promp and issue the => fastboot.exe oem config fsg-id "" command. That's all!
Thanks a lot to JCase and his team for developing this hack!
BRB installing lots of ****
Click to expand...
Click to collapse

ChazzMatt said:
FYI @TheSt33v...
Haven't read your updated instructions, but this may be something worth mentioning if you haven't already.
Click to expand...
Click to collapse
Those instructions were in autoprime's OP, so they did make it into my guide.

need more help
TheSt33v said:
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
Click to expand...
Click to collapse
what to do step by step to get my droid xt1254 unlock with sunshine
if i put the sunshine code and the unlock fail is the code still working for the next try or i have to buy another one

KARIM9377 said:
what to do step by step to get my droid xt1254 unlock with sunshine
if i put the sunshine code and the unlock fail is the code still working for the next try or i have to buy another one
Click to expand...
Click to collapse
See updated guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
As for the code not working after a failure, I don't think you'll need another code if yours fails, but that would be a better question for Sunshine customer support if you want to be sure before trying it.

TheSt33v said:
See updated guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
As for the code not working after a failure, I don't think you'll need another code if yours fails, but that would be a better question for Sunshine customer support if you want to be sure before trying it.
Click to expand...
Click to collapse
thanks for your help
can you please update the TWRP

KARIM9377 said:
thanks for your help
can you please update the TWRP
Click to expand...
Click to collapse
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.

KARIM9377 said:
thanks for your help
can you please update the TWRP
Click to expand...
Click to collapse
TheSt33v said:
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
Click to expand...
Click to collapse
What @TheSt33v said.
This link is to the most recent TWRP with @bhb27 mods for our Quark phones. @bhb27 is our official TWRP maintainer. He's why our TWRP has official status. But he also builds personalized versions which include some features/mods for our phones that other TWRP versions do not have, mods specifically for our Quarks. His modded versions are always better than the versions on the TWRP website (which again are only there due to his efforts).
On that page below you want the modded TWRP with the most recent date -- will always be the one listed at the bottom.
https://www.androidfilehost.com/?w=files&flid=39562

need help
TheSt33v said:
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
Click to expand...
Click to collapse
i need stack firmware to flash it with my locked droid turbo xt1254 MCG24.251-5-5 with tool to falsh it