VZW Moto X dev rooted. go back to stock recovery? - Moto X Q&A

If I go back to the stock recovery from TWRP will I still be rooted? I'd like to go back to stock recovery for the remote-wipe capabilities of android device manager.
Thanks

I don't personally know the method, but yes you can restore the stock recovery and still be rooted. Its on the forum here somewhere.
Just know that feature will put a drain on your battery life. Just a heads up.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

take the recovery image from the fxz plug your phone into your pc with usb cable. Put the phone into fast boot open a command prompt to where you have the recovery.img and type into the command prompt.... fastboot flash recovery recovery.img and you have the stock recovery back.

bigv5150 said:
take the recovery image from the fxz plug your phone into your pc with usb cable. Put the phone into fast boot open a command prompt to where you have the recovery.img and type into the command prompt.... fastboot flash recovery recovery.img and you have the stock recovery back.
Click to expand...
Click to collapse
I know how to restore the stock recovery. Just curious if I will still be rooted after doing so.

Restola said:
I know how to restore the stock recovery. Just curious if I will still be rooted after doing so.
Click to expand...
Click to collapse
Yes you will remain rooted. I'm running mine that way.

Related

[Q] How do I root developer edition?

I just received my moto x developer version. I must be an idiot because I can't find instructions on how to root it. Every post I can find is about rooting the locked version. People talk about the fact that I don't need an exploit because my boot loader is unlocked. I get that but I don't know how to root. Can someone kindly point me to a tutorial on how to root if my boot loader is already unlocked.
Install a recovery from the dev section. Either TWRP or CWM will be fine.
Then download SuperSU
flash supersu in recovery.
Moto x - Developer edition root
gunnyman said:
Install a recovery from the dev section. Either TWRP or CWM will be fine.
Then download SuperSU
flash supersu in recovery.
Click to expand...
Click to collapse
Thanks! I'll give it a shot. Much appreciated!
There are a few threads... but to elborate on what gunnyman has said... If your bootloader is unlocked, either Dev Edition, or you have a phone from a carrier like T-Mobile or Sprint that allow you to unlock via Moto's web site then its pretty easy to flash alternate recovery, and root from there.
Steps see -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP (has links to the files you need too.) and there are threads in the General and Developer sections here too.
Same process works if you have 4.2.2 or 4.4 on your phone.
Is there a way to root the developer edition and keep stock recovery ?
Pete
Flash custom recovery, flash root package in custom recovery, re-flash stock recovery
Sent from my Moto X DE
pasta1234 said:
Is there a way to root the developer edition and keep stock recovery ?
Pete
Click to expand...
Click to collapse
You don't have to flash the custom recovery, just boot into it. Once you have the root .zip on your phone reboot into the bootloader and fastboot boot (recovery) and flash the root zip from there. You will have root and stock recovery.
The reason I'm asking is to retain the ability to recieve OTA updates ?
How does one boot into a custom recovery without loading it?
Pete
3UR0TR45H said:
You don't have to flash the custom recovery, just boot into it. Once you have the root .zip on your phone reboot into the bootloader and fastboot boot (recovery) and flash the root zip from there. You will have root and stock recovery.
Click to expand...
Click to collapse
pasta1234 said:
The reason I'm asking is to retain the ability to recieve OTA updates ?
How does one boot into a custom recovery without loading it?
Pete
Click to expand...
Click to collapse
When you enter the fastboot command, use "boot" instead of "flash" and it will just temporarily boot into the recovery without flashing over the stock partition. You can flash the root zip as normal and when you reboot your phone, the custom recovery will be gone.
As far as receiving OTAs, I'm not sure if you'll get them or not. If you go modifying things like kernel, ROM, or even things like the build.prop, chances are it won't work or will break something. The good thing about having an unlocked bootloader is that it's nearly impossible to hard-brick the device unless you're reckless.
Are you sure this works? When I try 'fastboot boot recovery.img' it gives me a "failed command" error. I kicked off another thread asking how to do this since this is what I typically do with Nexus devices. I know that fastboot now has a -c command that might help but I don't know the magic to put after -c to make it work.
If anyone has been able to 'fastboot boot recovery.img' on a Moto X, please lemme know. This would be my preferred path rather than flashing the custom recovery and then the stock recovery back.
3UR0TR45H said:
When you enter the fastboot command, use "boot" instead of "flash" and it will just temporarily boot into the recovery without flashing over the stock partition. You can flash the root zip as normal and when you reboot your phone, the custom recovery will be gone.
As far as receiving OTAs, I'm not sure if you'll get them or not. If you go modifying things like kernel, ROM, or even things like the build.prop, chances are it won't work or will break something. The good thing about having an unlocked bootloader is that it's nearly impossible to hard-brick the device unless you're reckless.
Click to expand...
Click to collapse
pboggini said:
Are you sure this works? When I try 'fastboot boot recovery.img' it gives me a "failed command" error.
Click to expand...
Click to collapse
What happens when you just type fastboot?
Sent from my XT1060 using Tapatalk
This has been said already but you can just "fastboot flash recovery twrp.img", flash your superuser zip then "fastboot flash recovery recovery.img". You are using the correct image name in the command, correct?
Yes, this was said in the thread I started but then I saw someone suggest what I'd been wanting to do. To answer the questions, if I just type fastboot it gives me the help output like it should, fastboot devices shows my device, fastboot reboot works, fastboot reboot-bootloader works, etc. Essentially, I believe that either there is a command string that I could hand to -c or this just won't work on MotoX's like it does all the Nexus devices that I've played with.
Fortunately I did hit Moto up and they gave me permission to download the 4.4 image so I do have the stock recovery.
Ryno77 said:
This has been said already but you can just "fastboot flash recovery twrp.img", flash your superuser zip then "fastboot flash recovery recovery.img". You are using the correct image name in the command, correct?
Click to expand...
Click to collapse

[Q] Can you just boot twrp recovery?

All,
I'm coming from a nexus environment where I've been able to do fastboot boot twrp-2.6.3.1-ghost-4.4.img rather than fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img since I'm hoping to keep the stock recovery while installing supersu. It complains about "(bootloader) Command restricted" with the MotoX even though my bootloader is unlocked. Is this typical of Moto devices? Do I actually need to flash twrp, then supersu and then the stock recovery if that's the final result I want? FWIW, I want SU on it but I'd like to also receive future OTA updates w/o too much dorking around of at all possible.
thanks peterb
Are you using mfastboot or just regular fastboot?
I fastboot twrp no problem. I did however mfastboot the system.img . But to answer your question twrp will ask you if you want to root when you go to reboot.
Fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img is the command, when you flash do not reboot the device to the system but boot into recovery instead, you should be good to go and twrp should ask if you wish to root, if not just download the flashable supersu zip
Sent on my Moto X
I understand that you should flash if you want to have TWRP installed on your phone but that's not what I want. I'd like to just boot into TWRP, install the SuperSU.zip and then boot back up as normal leaving the stock recovery in place so that I will continue to get OTA updates. I get that this is likely not the norm but it's what I did with my N4 to get SuperSu so that I could update boot.prop for flashing a hybrid radio. Doing this made it easier to get the phone back to OTA ready w/o having to flash the stock recovery back.
I found a couple of posts in the N4 where the fastboot command failed and you needed to start using the "-c" command. I was wondering if this was the problem I was running into. The argument for -c is a bit cryptic so I worry that the one I found is likely N4 specific:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Basically what I'm wondering is if anyone has been able to just boot into TWRP w/o actually flashing it to the recovery partition.
If this is not possible then I'll flash TWRP, root and then flash the stock recovery back on since I did get the stock 4.4 image from Motorola.
thanks peterb
flashallthetime said:
Fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img is the command, when you flash do not reboot the device to the system but boot into recovery instead, you should be good to go and twrp should ask if you wish to root, if not just download the flashable supersu zip
Sent on my Moto X
Click to expand...
Click to collapse
Interested in this as well, for booting kernels. Device support has been hit-or-miss for me in the past.
And folks, he's asking about fastboot's ability to launch an image _without_ flashing. This is a somewhat esoteric/advanced use.
I'm interested in this too even though I have a locked Moto X.
I didn't know this was possible, huh. As for our device, it'll probably help if we can figure out what that -c command means.
Sent from my Moto-X (GSM DE) using the xda-developers app
thehockeydude44 said:
I didn't know this was possible, huh. As for our device, it'll probably help if we can figure out what that -c command means.
Sent from my Moto-X (GSM DE) using the xda-developers app
Click to expand...
Click to collapse
If I'm remembering right, google took the ability to boot a recovery without loading one away in 4.2. We tried to do this on the HTC 1 Google edition when we pulled its partitions to make a system dump. It failed.
OTA fails when the device is rooted, even if you have the stock recovery.
The OTA zip checks the system partition. If there is any single modification, it fails.
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Yea, this is the other way to do it. It's just a bummer if one can't use the flexibility to just boot into recovery. Note that I still seem to be able to boot into custom recovery on my Nexus 4 that's running KitKat. I'm curious about the comment about not getting an OTA with su installed. I know that with a modified build.prop and radio, the N4 wouldn't update but I could adb sideload successfully once I put build.prop back and the stock radio on. I figured the OTA would just unroot and then I'd have to do the process again.
Anyway, this was my plan B, just would have preferred to boot recovery.
peterb
waiflih said:
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Click to expand...
Click to collapse
if u want to "unroot" to take otas, u can just flash stock system
waiflih said:
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Click to expand...
Click to collapse
I am interested in this as well. How do we get a copy of the stock recovery to reflash?
Also, I have had rooted stock and custom recoveries and have received OTA's before (but they were on Nexus devices).
droiddog said:
I am interested in this as well. How do we get a copy of the stock recovery to reflash?
Also, I have had rooted stock and custom recoveries and have received OTA's before (but they were on Nexus devices).
Click to expand...
Click to collapse
you can take it from the the file used in rsdlite, according to you fw version
The only reason I want the stock recovery is because I think you can't remotely lock or erase your device on a custom recovery. Does anyone know anything to the contrary? Thanks.

[Q] VZW moto x- Bootloader variable not supported

I have a developer edition VZW moto x, bootloader is unlocked, i have the white warning screen upon boot telling me its unlocked, it has not yet been rooted, stock 4.4 kitkat and currently trying to install custom recovery, ive tried both twrp and the unofficial cwm recovery, i can get into bootloader through the cmd window, i get a response with adb devices showing its communicating, ive renamed the recovery files with a ".img" and no matter what i do i get the message "bootloader variable not supported" can someone please help me figure out what im doing wrong.
jaysdroid2 said:
I have a developer edition VZW moto x, bootloader is unlocked, i have the white warning screen upon boot telling me its unlocked, it has not yet been rooted, stock 4.4 kitkat and currently trying to install custom recovery, ive tried both twrp and the unofficial cwm recovery, i can get into bootloader through the cmd window, i get a response with adb devices showing its communicating, ive renamed the recovery files with a ".img" and no matter what i do i get the message "bootloader variable not supported" can someone please help me figure out what im doing wrong.
Click to expand...
Click to collapse
I believe you do not have to put the .IMG at the back of the files as they are already .IMG. Files
Are you using mfastboot?
The IMG file is in the same folder as mfastboot?
What are you typing in the cmd window
Sent on my Gummy running Lenoto X
well i installed the minimal ADB and fastboot installer with the adb and fastboot files in the zip, i extracted and installed, plug phone in USB debugging active, i type in command adb devices, get confirmation of device then type adb reboot bootloader, phone boots into bootloader, once in bootloader i type, fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img after which i get the error message, also when the file is saved, the .img is not there, ive done it as is and adding the .img to the end with the same result
jaysdroid2 said:
well i installed the minimal ADB and fastboot installer with the adb and fastboot files in the zip, i extracted and installed, plug phone in USB debugging active, i type in command adb devices, get confirmation of device then type adb reboot bootloader, phone boots into bootloader, once in bootloader i type, fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img after which i get the error message, also when the file is saved, the .img is not there, ive done it as is and adding the .img to the end with the same result
Click to expand...
Click to collapse
go here
http://forum.xda-developers.com/showthread.php?t=2603358
and look at the guide for unlocked bootloaders it should walk you though how to get it done correctly because you are spouse to use
MFastboot not fastboot.
alright, i got twrp installed, use mfastboot and had to add the .img to the end of the file, so i now have twrp installed, backups made and saved to my computer for the just in case, i hace access to twrp through rom manager, i am wondering if i can flash cwm using rom manager, the reason i ask is ive always used cwm with all my other phones and i just like using what i know and am comfortable with it, will i fudge everything up trying to use rom manager to flash cwm rather than the fastboot method.
p.s. thank you for the link and advise
jaysdroid2 said:
alright, i got twrp installed, use mfastboot and had to add the .img to the end of the file, so i now have twrp installed, backups made and saved to my computer for the just in case, i hace access to twrp through rom manager, i am wondering if i can flash cwm using rom manager, the reason i ask is ive always used cwm with all my other phones and i just like using what i know and am comfortable with it, will i fudge everything up trying to use rom manager to flash cwm rather than the fastboot method.
p.s. thank you for the link and advise
Click to expand...
Click to collapse
I have had issues with cwm restoring nandroids but I believe you need to flash it in the same manor
Sent on my Gummy running Lenoto X
so in other words i should just go ahead and keep twrp? at least until an official cwm is out?
jaysdroid2 said:
so in other words i should just go ahead and keep twrp? at least until an official cwm is out?
Click to expand...
Click to collapse
Haven't had one hiccup with twrp, actually prefer it over cwm
Sent on my Lenoto A2109 tablet
jaysdroid2 said:
so in other words i should just go ahead and keep twrp? at least until an official cwm is out?
Click to expand...
Click to collapse
you can try it if you every have to restore a nandroid backup and CWM fails all you have to do is flash TWRP and restore
here is a link to a CWM
Moto x thread
http://forum.xda-developers.com/showthread.php?t=2612149
dray_jr said:
you can try it if you every have to restore a nandroid backup and CWM fails all you have to do is flash TWRP and restore
here is a link to a CWM
Moto x thread
http://forum.xda-developers.com/showthread.php?t=2612149
Click to expand...
Click to collapse
May not work but I haven't tried it , cwm leaves the back up in the emulated sector in the sdcard
Sent on my Lenoto A2109 tablet

Fastboot Boot Recovery.IMG not Working after Update

I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
ReproOne said:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
Click to expand...
Click to collapse
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
Thank you for the reply. I thought about taking that approach, but I was really hoping someone would have an answer on why the procedure wasn't working now. My bootloader is still unlocked.
I found this as an approach someone did on the Nexus 4 for a similar issue:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Thoughts?
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
ReproOne said:
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
Click to expand...
Click to collapse
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Thank you for those steps. I do not have an external SD card installed, so I modified it to store the recovery.img on sdcard instead.
Now I can always fastboot flash twrp and then back to stock recovery.
Thank you again!
nfinitefx45 said:
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Click to expand...
Click to collapse
You would need root to do this. Not being able to use "fastboot boot" you would just be backing up the flashed recovery. Possibly towel root temp root, but I would assume it has been patched in newest update.
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
xPhantom said:
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
Click to expand...
Click to collapse
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
neudof said:
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
Click to expand...
Click to collapse
Yes, after the OTA, just flash TWRP back through fastboot and then re-flash SuperSU to get root back.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
I just applied the update released today, and I tried to save the recovery.img file before flashing TWRP. However, it kept giving me permission denied. Do you have the recovery.img file from the update released today so I can use it for the next update?
fastboot not working
please any help on how to access fastboot on HTC one m8.
its showing black screen n fastboot mode...
wot can I do 2 annul d problem
rooting problem
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
jinal shah said:
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
Click to expand...
Click to collapse
What's the output in the terminal when you fastboot flash recovery?
rooting problem
It doesn't show any error as such.
In the command window it shows successful.
But when I click on recovery it reboots back to fast boot.
Like for a second it shows the screen which reads 'this build is only for developers'
But then instead of opening Twrp it reboots back to fast boot.

Recovery issues

So Im at a total loss on this phone. I had a moto e unlocked that everything worked fine on and Im not totally new to working on phones. But this phone has me stumped. I have a unlocked XT1095, that is rooted. I tried to install TWRP on it, I can flash the .img file okay but everytime I reboot the phone to go into the recovery menu option, the phone just goes black and shuts off. I can't get into the recovery at all or any of the other fastboot options. My specs are as follows, Moto X 2nd gen, 5.1, system version is 23.16.3.victara_tmo.tmo.en.US tmo build number, LPE23.32-21.3
Don't reboot the phone after you flash TWRP. Select recovery from fastboot as soon as you flash it.
Sent from my XT1095 using Tapatalk
AGISCI said:
Don't reboot the phone after you flash TWRP. Select recovery from fastboot as soon as you flash it.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I just tried that today and it still shuts the phone off. The other odd thing is I tried to do this OTA update that was only a few MB. Once I tried that, it booted into TWRP just fine but into a boot loop. I had to delete the cached update file in order to get it to boot up properly.

Categories

Resources