I just unlocked my bootloader via the "chinese" unlock code...How to I get back to 100% stock after having been rooted via SlapMyMoto?
As I understand, the slapmymoto method replaces the recovery. Can I just flash the stock recovery back over it? Should I SFB back to 4.2.2 post camera then OTA back to 4.4?
JJHunterx said:
I just unlocked my bootloader via the "chinese" unlock code...How to I get back to 100% stock after having been rooted via SlapMyMoto?
As I understand, the slapmymoto method replaces the recovery. Can I just flash the stock recovery back over it? Should I SFB back to 4.2.2 post camera then OTA back to 4.4?
Click to expand...
Click to collapse
Full restore to stock would be to SBF back to appropriate version.
To just flash a recovery, simply download one, move it to ADB folder then run
Code:
fastboot flash recovery nameofyourfile.zip
asuhoops8628 said:
Full restore to stock would be to SBF back to appropriate version.
To just flash a recovery, simply download one, move it to ADB folder then run
Code:
fastboot flash recovery nameofyourfile.zip
Click to expand...
Click to collapse
If I SBF back to 4.2.2 will that flash the stock recovery and allow me to OTA to 4.4 no problem?
JJHunterx said:
If I SBF back to 4.2.2 will that flash the stock recovery and allow me to OTA to 4.4 no problem?
Click to expand...
Click to collapse
Yes, if you use RSDLite to flash a SBF you are flashing the full stock rom, recovery, boot, etc.
If you want to be on stock 4.4, why not just use RSDLite to flash the 4.4. SBF?
KidJoe said:
Yes, if you use RSDLite to flash a SBF you are flashing the full stock rom, recovery, boot, etc.
If you want to be on stock 4.4, why not just use RSDLite to flash the 4.4. SBF?
Click to expand...
Click to collapse
For some reason, I didn't think 4.4 had a SBF...Found it. Thanks.
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
fury683 said:
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
Click to expand...
Click to collapse
You can unlock your BL regardless of what version of android you are on. I just wanted to get back to stock so slapmymoto was no longer active (which is kinda a workaround for root imho, but it works and does its job.)
To root with an unlocked bootloader, all you have to do is download the TWRP img file and the supersu.zip file. Push the supersu.zip to your SD card. Use fastboot to flash TWRP img file. Boot into the recovery you just flashed and install the supersu.zip file. Bam you're rooted.
fury683 said:
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
Click to expand...
Click to collapse
Well, you can unlock your bootloader at any time once you have the unlock code. The Android version on your phone doesn't matter.
Flashing TWRP, booting to it and installing SuperSU is how you root with an unlocked bootloader. (for full details see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 which makes it seem like a longer process than it is.) That process is as easy as it gets, and works no matter what ROM you are on.
If you want to be on 4.4.2, and going to use RSDLite to flash an SBF anyway, the most straight forward way would be to flash the 4.4.2 SBF, then Root by flashing TWRP, booting to it, and installing SuperSU.
KidJoe said:
Well, you can unlock your bootloader at any time once you have the unlock code. The Android version on your phone doesn't matter.
Flashing TWRP, booting to it and installing SuperSU is how you root with an unlocked bootloader. (for full details see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 which makes it seem like a longer process than it is.) That process is as easy as it gets, and works no matter what ROM you are on.
If you want to be on 4.4.2, and going to use RSDLite to flash an SBF anyway, the most straight forward way would be to flash the 4.4.2 SBF, then Root by flashing TWRP, booting to it, and installing SuperSU.
Click to expand...
Click to collapse
Thanks. Can I SBF with 4.4.2 even thought I'm still on 4.4? Or do I need to do 4.4 SBF, OTA to 4.4.2 then unlock and do TWRP/root?
Thanks again.
fury683 said:
Thanks. Can I SBF with 4.4.2 even thought I'm still on 4.4? Or do I need to do 4.4 SBF, OTA to 4.4.2 then unlock and do TWRP/root?
Thanks again.
Click to expand...
Click to collapse
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
KidJoe said:
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
Click to expand...
Click to collapse
After unlocking though, flashing the system.img from an SBF file and a custom recovery brings you basically back to "stock" (excluding the custom recovery) so you don't have to use RSDLite, correct?
EvanVanVan said:
After unlocking though, flashing the system.img from an SBF file and a custom recovery brings you basically back to "stock" (excluding the custom recovery) so you don't have to use RSDLite, correct?
Click to expand...
Click to collapse
For the most part, you can use mfastboot to flash just system.img and recovery.img, this will get those two parts back to stock, which is often enough to allow you to take an OTA update, however, if you've touched any other part, your phone wont be 100% stock. And then, how long does it take for the OTA to install and reboot? Now, in fury683's case, the phone is on 4.4 and he wants to go to 4.4.2. But if the phone was on say either of the 4.2.2 versions and he wanted to go to 4.4.2, then you'd also have multiple OTA's to install.
Using the full SBF and RSDlite will flash all parts, gets you to 100% stock, and immediately on the version you want. I don't know everything that SlapMyMoto and MotoWpNoMo touch, so I can't say for sure if flashing system and recovery are enough to totally remove them, or just remove enough to allow you to take an OTA.
System.img takes the longest to flash via either mFastboot or RSDLite, the rest are really quick, so the time spent using RSDLite to flash everything isn't that much more than manually flashing just system.img and recovery.img via mfastboot.
So considering that the mfastboot oem unlock does a factory reset anyway (so data is going to be lost), and flashing with RSDlite flashes all parts as 1 batched operation (i.e. you don't have to individually execute mfastboot lines...) using RSDLite can get you to the final destination, and ensure 100% stock, more easily.
I did mine last night from 4.4. I unlocked, got a clean 4.4 , took ota, flash twrp, install su. If you do in the right order shouldn't take more than 30 mins to be up and running again. If you use Titanium backup be sure to pull your files to computer before doing the bootloader unlock.
KidJoe said:
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
Click to expand...
Click to collapse
Thanks for your help. The process was much less painful than I expected. Aside from downloading the SBF file, whole process to SBF, unlock, flash TWRP and root took about 20 minutes.
Working great now!
Thanks again
Related
I have dug around a bit and I can't seem to find a TWRP flashable stock rom for the VZW XT1060. Now that I'm liberated (BL unlocked), I am hoping to have a quick and easy way to recover when I **** up my phone. Can I use stock roms for other Moto X variants or should I just be patient and wait for someone to come out with this?
Just make a backup before you start playing, and you're all set.
If you **** up your phone, use the SBF files and flash them manually.
nhizzat said:
If you **** up your phone, use the SBF files and flash them manually.
Click to expand...
Click to collapse
yea.. thats always the fallback.. but flashing stock rom via twrp or cwm so much faster and able to regain root quickly
grimez said:
I have dug around a bit and I can't seem to find a TWRP flashable stock rom for the VZW XT1060. Now that I'm liberated (BL unlocked), I am hoping to have a quick and easy way to recover when I **** up my phone. Can I use stock roms for other Moto X variants or should I just be patient and wait for someone to come out with this?
Click to expand...
Click to collapse
There is no version of the Stock rom that is flashable via TWRP or CWM.
SBF file is out but you must flash via RSDLite, or manually flash via mfastboot. The only "flashable" via recovery "option" out there would be the OTA UPDATE which is not a full rom, and it isn't flashable via TWRP or CWM either.
I don't expect anyone to come out with anything flashable via TWRP/CWM for the stock rom.
It is not recommended to flash X Roms for other variants like the XT1058/XT1053/etc on the Verizon X XT1060 due to radio, and other components.
Flash with RSD or OTA?
Hi all, am hoping soomeone my know this as I have not come across a detail answer for it yet...I have DE still on the original 4.2.2 pre camera. Is there a best way to upgrade to kit kat , either 4.4 or 4.4.2 and be able to have the most "options" left (ie: I wont be able to re-root or intstal Phils recovery) for my device . Any insight would be apreciated. Thanks.
kerryh420 said:
Hi all, am hoping soomeone my know this as I have not come across a detail answer for it yet...I have DE still on the original 4.2.2 pre camera. Is there a best way to upgrade to kit kat , either 4.4 or 4.4.2 and be able to have the most "options" left (ie: I wont be able to re-root or intstal Phils recovery) for my device . Any insight would be apreciated. Thanks.
Click to expand...
Click to collapse
If you have a DE, you can unlock the bootloader (without voiding warranty) at any time, and install a custom recovery to root.
As far as upgrade path, it depends on if you are stock, or how close to stock if you have modified it. If stock, just take the OTA's, one at a time, to keep your settings, data, apps.
The OTA Update files have a manifest in them containing a list of files, and check sums for those files, which it needs on your phone. If files it wants to be there are missing from your phone or do not match the check sum in the manifest, the OTA will fail (which is why I say depends on if you are stock). If you've removed or replaced any files, you'll need to put them back. You'll also need stock recovery for any OTA to install.
An "easy" way to update is to download the SBF file for the version you want on your phone from -> http://sbf.droid-developers.org/phone.php?device=0 unzip it. Edit the XML file and, if it exists, remove the line for erase partition userdata. Then flash using RSDLite.
With the unlocked bootloader, you can then flash TWRP, CWM or other custom recovery and install SuperSU to root if needed.
grimez said:
I have dug around a bit and I can't seem to find a TWRP flashable stock rom for the VZW XT1060. Now that I'm liberated (BL unlocked), I am hoping to have a quick and easy way to recover when I **** up my phone. Can I use stock roms for other Moto X variants or should I just be patient and wait for someone to come out with this?
Click to expand...
Click to collapse
Recently saw both stock odexed and stock deodexed rooted 4.2.2 for unlocked VZW XT1060 posted over on DroidRzr.com
KidJoe said:
There is no version of the Stock rom that is flashable via TWRP or CWM.
Click to expand...
Click to collapse
For the Verizon XT1060 there is now -> http://forum.xda-developers.com/moto-x/development/rom-stock-vzw-4-4-2-developer-editions-t2693591
I just bought a DE Moto X that's on 4.4.2. The bootloader is unlocked, phone is rooted with TWRP installed. My first question is what do i need to do to update to 4.4.4. If I'm understanding everything correctly I need to flash the stock recovery image..where do I get that??
Once I do that I will need to then reflash TWRP and root again, correct??
mpetruzz said:
I just bought a DE Moto X that's on 4.4.2. The bootloader is unlocked, phone is rooted with TWRP installed. My first question is what do i need to do to update to 4.4.4. If I'm understanding everything correctly I need to flash the stock recovery image..where do I get that??
Once I do that I will need to then reflash TWRP and root again, correct??
Click to expand...
Click to collapse
Yes. Here is the 442 recovery. Extract the img & Flash it with the play app: recovery tools/ Rashr-flash tool.
Once on 444 you do not want to go back.
https://mega.co.nz/#!FQI0zKxR!lS5oSAZiu0Z3dm1OCgkqKE5LqGv9rIT0zAku8juIxPk
---------- Post added at 08:16 PM ---------- Previous post was at 08:07 PM ----------
Good to hide root too with super SU.
mpetruzz said:
I just bought a DE Moto X that's on 4.4.2. The bootloader is unlocked, phone is rooted with TWRP installed. My first question is what do i need to do to update to 4.4.4. If I'm understanding everything correctly I need to flash the stock recovery image..where do I get that??
Once I do that I will need to then reflash TWRP and root again, correct??
Click to expand...
Click to collapse
First, which DEV Edition X do you have? GSM Or VZW? I'm going to Guess VZW, since you say you are on 4.4.2, and the latest for the GSM is 4.4.3.
If GSM, 4.4.4 OTA isn't out yet. So even if you flash back to stock, right now you wont get an update to 4.4.4, but you should get 4.4.3 which will be needed to take 4.4.4.
If Verizon, 4.4.4 OTA and FXZ is out, so you can go either way.
To take any OTA, you need to be aware of several things...
First, the most important, you can't flash an OTA from custom recovery like TWRP. You need STOCK recovery or you will bootloop. (so yes, you can fasboot flash stock recovery on your phone, immediately reboot to booloader and enter recovery to make sure its there). If you are already rooted you can use Rashr (and there is another tool that I can't remember the name of) to put stock recovery back on there.
Next, there is a pre-flash verification check the OTA performs. It makes sure you are on the correct ROM before it installs. It checks files and parts of your phone. It looks to make sure stuff is there, and matches the expected checksum or hash. If you haven't made any mods, and you have stock recovery back on there, you should be OK to take the OTA.. BUT if you've deleted, renamed, modified files or parts and they no longer match close enough to "stock" the OTA will fail to install.
XPosed gets in the way. It must be disabled (there is a zip for that), or uninstalled.
If you manually undo any modifications and take the OTA, you shouldn't have to re-root, and flashing TWRP back on is optional.
You could use mfastboot to re-flash System.img and Recovery.img from 4.4.2 onto your phone, that will usually be enough to allow you to pass the verification checks and take the OTA. But if you do this, you will have to flash TWRP and re-root after you get 4.4.4 on there.
Because many modifications could have been made, and the fact the 4.4.4 FXZ is out for Verizon, if you have a VZW Dev Edition, you can just use RSDLite (or mfasboot) to flash the Verizon 4.4.4 FXZ. Just make sure you remove the ERASE USERDATA line before flashing. This will get you directly to 4.4.4 without you having to manually, one by one, undo any mods you might have made that get in the way of the OTA Verification checks. If you do it this way, you WILL have to flash TWRP and re-root.
Thanks so much for the help!! I flashed the stock recovery image via flashify, accepted the ota and was all set. Then I flased twrp via flashify again and was back and all good!!
So glad I got the DE, this should hold me off til the x+1 drops.
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Anything else I might have missed that is important either from mistakes or just general knowledge I missed would be appreciated. Thanks and Good Night everybody!
Icon000 said:
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
Click to expand...
Click to collapse
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
Click to expand...
Click to collapse
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Click to expand...
Click to collapse
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Great explanation! :good:
tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Why do you recommend flashing 4.4.4 over accepting the OTA? I still want to be able to use the additions originally provided by Motorola. I didn't seen a rom built on Moto Stock. Did I miss it?
Flash the stock 4.4.4 ROM that is for your device.
What's better...4.4.2 with patches to make it 4.4.4 (via an OTA) or just the full 4.4.4 (via the full 4.4.4 install) without the need for patching to make it 4.4.4?
Oh well...it looks like there isn't a FULL 4.4.4 for AT&T Moto X released yet....just 4.4.2. Flash the full 4.4.2 then take the OTA update to 4.4.4 and then flash TWRP to get root.
AT&T 4.4.2
http://sbf.droid-developers.org/download.php?device=0&file=849
You can just flash the system.img from the download with mfastboot to revert any changes you did (root, etc..) so that the OTA can be installed successfully. You'll just want to get fully updated before flashing an alternative recovery like TWRP.
So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance
You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.
PedroAlba said:
So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance
Click to expand...
Click to collapse
This is asked every time an new OTA comes out, and we get many threads started covering it.
To date...
For the Motorola X 2013, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
None of the OTA's will install if you have TWRP recovery on your phone. Instead you get stuck in a bootloop. (mfastboot erase cache will get you out of the bootloop). You need to have stock recovery on your phone. NOTE: I don't recall what happens when using Philz or CWM as recovery.
Each OTA so far has included a "Pre-Install Verification Check", a manifest of files and their checksum/hashes which the update compares against your phone. If expected files are missing, or the wrong hash, the OTA will fail to install. - So any removed or modified "bloat", system files, etc. need to be in place. Any apps like Xposed which change /system need to be disabled/removed. In some cases Freezing apps using Titanium Backup cause the OTA to fail, and the apps need to be unfrozen. However, some have not had to unfreeze. Using the phone's app manager to disable an app (Settings -> Apps -> open app listing -> DISABLE) does not have to be undone.
If you have version mismatch between GPT.BIN or Motoboot.img and the ROM on your phone, taking an OTA WILL brick the phone. - Grab the FULL SBF for the Stock Moto ROM which matches the bootloader version on your phone, or a newer SBF (i.e. if you have the bootloader version that corresponds to 4.4.2, grab the 4.4.2 SBF or 4.4.4 SBF), and flash it via mfastboot. You may need some extra steps to flash GPT.BIN and Motoboot.img.
If you've used hacks to root/disable write protection because you have a locked bootloader, you may lose root, and wont be able to re-root until a new exploit is found. Those hacks might also get in the way of the OTA's pre-install validation checks.
If you have unlocked your bootloader via mfastboot oem unlock UNIQUECODE or Sunshine, the bootloader will not re-lock.
There have been some posts (twitter and G+) about how Lollipop poses new security features which are a challenge to rooting, even with an unlocked bootloader. Since I don't know the technical ins and outs, all I can say is.. Even with an unlocked bootloader, I wont jump on Lollipop as soon as its available, until I know if I can still root my X.
(I have a little bit more detail posted here -> http://mark.cdmaforums.com/MotoX-OTA.html)
lowvolt1 said:
You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.
Click to expand...
Click to collapse
For what it's worth, you don't need to uninstall the modules. Just use the Xposed Disabler zip in your SD card, then install the framework again once you've flashed /system and taken the update.
When I did updated to 4.4.4 I disabled the modules in the Xposed UI (not sure if that was necessary or not), but did not actually uninstall any of the APKs for the modules. When I reinstalled Xposed after updating, all I just turned all my modules back on and rebooted.
Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.
mtpease said:
Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.
Click to expand...
Click to collapse
Not really a bad practice either way, if you clear stuff out now and again. If you try to take an OTA with a modified /system partition, it usually just fails during the hash checks and never installs/modifies anything.
You started your thread title with a [q].... Perhaps the Q&A section would be the section to ask your question? ?
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
bushako said:
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
Click to expand...
Click to collapse
I don't want to go back to complete stock, I want to keep bootloader unlocked and root. Is there a stock rooted rom out there I can flash w/ TWRP without having to do OTA or flashing the recovery back to stock?
Yes there is its in the development section. You'll read the thread something like xt1053 stock flash-able. It contains only the kernel and system files so you should be good.
Here http://forum.xda-developers.com/showthread.php?t=3155843
Sent from my Moto X
-RanZ- said:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
Click to expand...
Click to collapse
First off, there is no Verizon 5.1 yet. So any 5.1 you try will be for a different model, and if you flash a full rom, it will have different radios (which don't work for CDMA that Verizon still uses for voice/3g data. If you keep your stock VZW radio files, keep in mind they will be on a different version than the rest of the rom which could cause some inconsistencies and issues. IF you do flash a FULL SBF, you will be stuck with no SAFE way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature), and you'll have to wait for the Verizon 5.1 SBF to get back to Verizon's rom.
Next, to install an OTA update, when it becomes available, you need STOCK RECOVERY on your phone. The OTA also does a pre-flash check/validation of your phone before it flashes, so if anything it looks for is not what it expects, the OTA will fail. Because of that you need to be 100% stock, or very near to it.
Finally, NO, an OTA will not relock your bootloader, nor will flashing an SBF.
For more on taking an OTA, see the link in my signature on OTA Updates..
That being said, if you TRY a 5.1 rom that is out there for another model you best bet is to find one that is a TWRP back up of 5.1 installed on someone's phone, since it only updates system.img and boot.img. It may not work 100% (because part of your phone will still have the 4.4.4 files), but it will give you a taste and you could later revert back to the stock 4.4.4 which you currently have on your phone. IF you flash a FULL SBF, you might be stuck with no way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature)
Hi Bushako, I've Moto X Verizon XT1060 and it's struck in 4.2.2 android. When I try to update using setting, about phone and system update it show there is no update available but the android version on it is 4.2.2
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
-RanZ- said:
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Click to expand...
Click to collapse
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
KidJoe said:
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
Click to expand...
Click to collapse
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
-RanZ- said:
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
Click to expand...
Click to collapse
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
KidJoe said:
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
Click to expand...
Click to collapse
I will give this a try if I can locate the correct SBF files, your information has helped greatly, Thanks!
nevermind, google fixed me.