Related
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.
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
I have vzw dev ed, rooted with twrp recovery, stock everything else, I want to take the OTA and know i cant as is, i plan on using moto x toolkit to flash back to stock, here are my questions, once im back to stock and take the OTA, will i still be rooted, if not can i re root 4.4.2, do they have twrp custom recovery for 4.4.2, or should i just freeze the update and leave my phone as is?
jaysdroid2 said:
I have vzw dev ed, rooted with twrp recovery, stock everything else, I want to take the OTA and know i cant as is, i plan on using moto x toolkit to flash back to stock, here are my questions, once im back to stock and take the OTA, will i still be rooted, if not can i re root 4.4.2, do they have twrp custom recovery for 4.4.2, or should i just freeze the update and leave my phone as is?
Click to expand...
Click to collapse
you have a unlocked bootloader so you can root any version of android just grab the SBF file for 4.4 and flash it with RSD Lite and then take the OTA update
after the update reflash your custom recovery via the command promote command then install the SuperSU flashable zip in your recovery and enjoy your rooted 4.4.2
dray_jr said:
you have a unlocked bootloader so you can root any version of android just grab the SBF file for 4.4 and flash it with RSD Lite and then take the OTA update
after the update reflash your custom recovery via the command promote command then install the SuperSU flashable zip in your recovery and enjoy your rooted 4.4.2
Click to expand...
Click to collapse
awesome, thank you, so the twrp version i used while on 4.4 will work with 4.4.2, there is not a different version for the new OS? basically once i revert back to stock and accept the OTA i just do exactly what i did the first time with the same files and i'll be where i was prior?
Yes, you can use the same TWRP version on 4.4.2, and you reinstall it the same way. However, you don't need to use RSD lite to flash an entire SBF file in order to return to stock to accept the update - you can, but it will wipe all of your apps and settings. You can fastboot the stock recovery.img and system.img to return to stock, accept the OTA, re-flash TWRP, reboot directly into TWRP, let TWRP install SU, and you're good to go.
Sent from my XT1060 Dev Edition
Interesting, where would i find just those two img. files and how would i go about flashing just those two files, sorry if i need it dumbed down, fist moto phone and first time having to use a cmd prompt screen to do anyhting, had a galaxy nexus prior and everyhting was completely.....different/simpler.
pkomarnicki said:
Yes, you can use the same TWRP version on 4.4.2, and you reinstall it the same way. However, you don't need to use RSD lite to flash an entire SBF file in order to return to stock to accept the update - you can, but it will wipe all of your apps and settings. You can fastboot the stock recovery.img and system.img to return to stock, accept the OTA, re-flash TWRP, reboot directly into TWRP, let TWRP install SU, and you're good to go.
Sent from my XT1060 Dev Edition
Click to expand...
Click to collapse
this is tru but i rather just have them use the whole file instead of flashing just parts of it because there is less chance of messing there phone up.
so it is your call either way you have to download the SBF file. then you can either flash the whole file via RSD Lite or you can unzip the recover or system images and flash them via CMD and fastboot and mfastboot.
you can find the SBF files at the link below just make sure you download the correct file for your phone
http://sbf.droid-developers.org/phone.php?device=0
here is a link to my guide should give you all the info you need to get back to stock to take the OTA
http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358
Thank you all for the input, im prolly just going to revert completely to stock, i have no problem letting my apps re download and its less of a chance i fubar something, although if i do rest assured my next post will be how to un-fubar my phone
pkomarnicki said:
Yes, you can use the same TWRP version on 4.4.2, and you reinstall it the same way. However, you don't need to use RSD lite to flash an entire SBF file in order to return to stock to accept the update - you can, but it will wipe all of your apps and settings. You can fastboot the stock recovery.img and system.img to return to stock, accept the OTA, re-flash TWRP, reboot directly into TWRP, let TWRP install SU, and you're good to go.
Sent from my XT1060 Dev Edition
Click to expand...
Click to collapse
This. No reason to flash back to completely stock.
jaysdroid2 said:
Interesting, where would i find just those two img. files and how would i go about flashing just those two files, sorry if i need it dumbed down, fist moto phone and first time having to use a cmd prompt screen to do anyhting, had a galaxy nexus prior and everyhting was completely.....different/simpler.
Click to expand...
Click to collapse
The 2 files can be found inside the sbf file.
To flash them:
fastboot flash recovery recovery.img
fastboot flash system system.img
jaysdroid2 said:
Thank you all for the input, im prolly just going to revert completely to stock, i have no problem letting my apps re download and its less of a chance i fubar something, although if i do rest assured my next post will be how to un-fubar my phone
Click to expand...
Click to collapse
Take this opportunity to learn something. If flashing back to stock isn't an issue for you, what's the worst that can happen? You own a dev edition, learn to take full advantage of it. It's not difficult at all..
And please, don't use a toolkit until you've learned the basics of fastboot and adb. If the toolkit fails, you'll end up having to learn it all anyways.
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.
Ok, here's the rundown - I have a VZW Moto X (XT1096). I previously ran mofo on it had flashed the 5.1 img files to it and so had 5.1 rooted, but with a locked bootloader. After learning that JCase had gotten sunshine to work on it I unlocked my boot loader. I then decided that because I was worried about having the a kind of mish-mash of systems on it, i.e., 5.0 bootloader (unlocked) with hacked and modded 5.1 system files flashed from mofo, that I wanted to start fresh. I then used the XT1096 flash to stock script and flashed back to 5.0 (there were a bunch of problems and bootloops and force closes, but I am happy to report I am now on a fully stock 5.0 with unlocked BL). Following being stock I have tried to take the OTA but have been unable to do so. When I try it OTA on my device it just sits at 0%. When I tried using MDM it gave me an error message that it failed to install the update - on the device it said getjar: unlocked.
So, now that I am on 5.0 with an unlocked bootloader I am not sure how to proceed with my priorities, Root, WiFi tethering and upgrading to 5.1. My questions are this:
(1) How can I upgrade to 5.1 or does my bootloader unlock preclude that?
(2) How best can I achieve root?
(3) Once I am rooted what do I need to do in order to enable wifi tethering?
Thank you so much!
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot and flash the stock system.img and recovery.img before doing the update.
3. I don't have experience with Verizon network. I use T-Mobile on this Verizon device and I just enable WiFi Hotspot. In the APN settings, in the "APN type" field, I add the value "dun". And set everything to IPv4.
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
eksasol said:
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
Click to expand...
Click to collapse
Thank you for the reply - got the update to take and have gotten the device rooted properly.
Now I just need to enable wifi tether - anyone know what is done in the Mofo images that allows it - can i do the same here?
I am interested in this question as well. I am in the exact same boat as the OP, except I am still on a Mofo 5.1 img that is giving me issues. I'd like to flash back to stock and take the OTA. But wifi tether will be a must.
Thanks to mikeoswego we have the tethering answer.
http://forum.xda-developers.com/showthread.php?p=62379151
eksasol said:
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
Click to expand...
Click to collapse
I tried this but after I flash TWRP I can't boot to recovery. If I choose recovery from the bootloader it just turns off the phone (charging icon). If I send it adb reboot recovery I get error android "No Command."
Flashed it multiple times, tried mfastboot, no luck. Any ideas?
Edit: I feel dumb. I was using power button to try to select, it's volume up. Good to go.
GatorsUF said:
Thanks to mikeoswego we have the tethering answer.
http://forum.xda-developers.com/showthread.php?p=62379151
Click to expand...
Click to collapse
The other method (the one I used) was to install the Xtether xposed module for the 2013 Moto X - worked perfectly for me.
I feel like a complete noob for asking this in regards to my XT1096, but, how would I get rid of the unlocked bootloader warning message?
SargeStryker said:
I feel like a complete noob for asking this in regards to my XT1096, but, how would I get rid of the unlocked bootloader warning message?
Click to expand...
Click to collapse
Flashing this
http://forum.xda-developers.com/showthread.php?t=2871478
juliospinoza said:
Flashing this
http://forum.xda-developers.com/showthread.php?t=2871478
Click to expand...
Click to collapse
Thanks!