I just got a Moto X (non-developer edition) and I'm looking to root to take advantage of Xposed and Gravitybox. I'm a little confused as to what path to take however. I'd like to be able to get to 4.4 and still retain OTA updates without losing root, if possible.
Here's my details:
VZW Moto X
Android 4.2.2
Baseband MSM8960PRO_BP2323.020.90.00R
System: 139.15.1.ghost_verizon.verizon.en.us
Build Number: 13.9.0Q2.X-116-MX-17-57-X-1
You will need to look at using the SlapMyMoto method.
But you will not be able to take the future OTAs until someone figures out how to root them (if it even can be done).
I thought that the Slapmymoto method was from the 4.4 OTA already? Should I take the OTA and follow from step 1 of the guide? Or can I just skip downgrading and follow all the way through?
pan2thada said:
I thought that the Slapmymoto method was from the 4.4 OTA already? Should I take the OTA and follow from step 1 of the guide? Or can I just skip downgrading and follow all the way through?
Click to expand...
Click to collapse
If you are on 4.2.2 currently, just start the slapmymoto process as if you have just freshly flashed back to 4.2.2.
The Slapmymoto process will take you up to 4.4 and be rooted.
What mjphillips1981 was saying is once you use Slapmymoto, you will not be able to take any future OTA updates. If Slapmymoto works anything like the previous generation roots, it replaces your stock recovery, and some other things that will make OTA updates fail, lose root, and possibly cause you to be stuck in a boot loop (which should be repairable).
Just like other phones, when future ROM updates come out, unless you have an unlocked bootloader, you need to wait for someone to find an exploit, take advantage of it, and bring out a repeatable root process. So once you root, if you want to keep root, do NOT take an OTA until a root exploit and process have been posted.
KidJoe said:
If you are on 4.2.2 currently, just start the slapmymoto process as if you have just freshly flashed back to 4.2.2.
The Slapmymoto process will take you up to 4.4 and be rooted.
What mjphillips1981 was saying is once you use Slapmymoto, you will not be able to take any future OTA updates. If Slapmymoto works anything like the previous generation roots, it replaces your stock recovery, and some other things that will make OTA updates fail, lose root, and possibly cause you to be stuck in a boot loop (which should be repairable).
Just like other phones, when future ROM updates come out, unless you have an unlocked bootloader, you need to wait for someone to find an exploit, take advantage of it, and bring out a repeatable root process. So once you root, if you want to keep root, do NOT take an OTA until a root exploit and process have been posted.
Click to expand...
Click to collapse
Thanks! I'm coming from first a HTC Incredible and then a GNex so I'm not used to not being able to unlock the bootloader... I'm a little confused about these steps however:
Wait for the bootlaoder screen to appear
Code:
fastboot flash recovery recovery.img
fastboot reboot
Once the device has rebooted, go ahead and take the OTA, once 4.4 is up and running continue.
Step 5)
Now we need to downgrade the bootloader using the 4.2.2 bootloaders and flash the normal kernel to the recovery partition:
Code:
adb reboot bootloader
Wait for the bootlaoder screen to appear
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot reboot
Step 6)
Once booted into 4.4,
Code:
adb push su /data/local/tmp/su
adb push install.sh /data/local/tmp/install.sh
adb push rec.sh /data/local/tmp/rec.sh
adb push install-recovery.sh /data/local/tmp/install-recovery.sh
adb push setup.sh /data/local/tmp/setup.sh
adb reboot
Click to expand...
Click to collapse
First, does the fastboot flash command make a backup of my bootloader? If not, where do I get the bootloader I'm re-downgrading to from? Also where do the recovery.img or motoboot.img files come from? I just want to make sure I fully understand the process before I accidentally brick my phone.
KidJoe said:
If you are on 4.2.2 currently, just start the slapmymoto process as if you have just freshly flashed back to 4.2.2.
The Slapmymoto process will take you up to 4.4 and be rooted.
What mjphillips1981 was saying is once you use Slapmymoto, you will not be able to take any future OTA updates. If Slapmymoto works anything like the previous generation roots, it replaces your stock recovery, and some other things that will make OTA updates fail, lose root, and possibly cause you to be stuck in a boot loop (which should be repairable).
Just like other phones, when future ROM updates come out, unless you have an unlocked bootloader, you need to wait for someone to find an exploit, take advantage of it, and bring out a repeatable root process. So once you root, if you want to keep root, do NOT take an OTA until a root exploit and process have been posted.
Click to expand...
Click to collapse
But you can always SBF back to factory stock to be able to get OTA's again, right? Without root anymore of course.
detonation said:
But you can always SBF back to factory stock to be able to get OTA's again, right? Without root anymore of course.
Click to expand...
Click to collapse
Yes.
detonation said:
But you can always SBF back to factory stock to be able to get OTA's again, right? Without root anymore of course.
Click to expand...
Click to collapse
In the current state. Yes. That is one way to fix the "boot loop" issue I mentioned, and get back to stock.
i.e. if you are on KK and root, you can re-flash the same KK rom and get back to stock and take a future OTA, without root.
---------- Post added at 03:07 PM ---------- Previous post was at 02:58 PM ----------
pan2thada said:
First, does the fastboot flash command make a backup of my bootloader? If not, where do I get the bootloader I'm re-downgrading to from? Also where do the recovery.img or motoboot.img files come from? I just want to make sure I fully understand the process before I accidentally brick my phone.
Click to expand...
Click to collapse
These questions are answered in the Slapmymoto thread but..
No, the fastboot flash command does NOT backup anything... it FLASHES the files stored on your PC onto your phone. For example: Fastboot flash recovery recover.img would flash the recovery.img on your PC to your phone's recovery "partition"
and looking at the steps, Step 1 tells you to flash back to 4.2.2, which you are on. BUT you still need to download and unzip the 4.2.2 rom for your phone (step 1 has links to the Verizon and ATT versions), as that is where you'll get the .IMG files, logo.bin and other files you'll need in step 4 and 5.
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools
KidJoe said:
In the current state. Yes. That is one way to fix the "boot loop" issue I mentioned, and get back to stock.
i.e. if you are on KK and root, you can re-flash the same KK rom and get back to stock and take a future OTA, without root.
---------- Post added at 03:07 PM ---------- Previous post was at 02:58 PM ----------
These questions are answered in the Slapmymoto thread but..
No, the fastboot flash command does NOT backup anything... it FLASHES the files stored on your PC onto your phone. For example: Fastboot flash recovery recover.img would flash the recovery.img on your PC to your phone's recovery "partition"
and looking at the steps, Step 1 tells you to flash back to 4.2.2, which you are on. BUT you still need to download and unzip the 4.2.2 rom for your phone (step 1 has links to the Verizon and ATT versions), as that is where you'll get the .IMG files, logo.bin and other files you'll need in step 4 and 5.
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools
Click to expand...
Click to collapse
can i use this fastboot installer?
http://forum.xda-developers.com/showthread.php?p=42407269
pan2thada said:
can i use this fastboot installer?
http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
that is a minimal install of Android SDK/Platform tools. Yes you can start with that... BUT you still need to use the special motorola fastboot.exe that I linked to instead of the stock fastboot.exe part of the package in this thread you are linking to.
KidJoe said:
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools
Click to expand...
Click to collapse
KidJoe said:
that is a minimal install of Android SDK/Platform tools. Yes you can start with that... BUT you still need to use the special motorola fastboot.exe that I linked to instead of the stock fastboot.exe part of the package in this thread you are linking to.
Click to expand...
Click to collapse
I used the Android SDK/Platform tools fastboot.exe without issue to root my VZW Moto X using SlapMyMoto. Knowing what I know now, I wouldn't recommend it. Just saying it can be done.
KidJoe said:
In the current state. Yes. That is one way to fix the "boot loop" issue I mentioned, and get back to stock.
i.e. if you are on KK and root, you can re-flash the same KK rom and get back to stock and take a future OTA, without root.
---------- Post added at 03:07 PM ---------- Previous post was at 02:58 PM ----------
These questions are answered in the Slapmymoto thread but..
No, the fastboot flash command does NOT backup anything... it FLASHES the files stored on your PC onto your phone. For example: Fastboot flash recovery recover.img would flash the recovery.img on your PC to your phone's recovery "partition"
and looking at the steps, Step 1 tells you to flash back to 4.2.2, which you are on. BUT you still need to download and unzip the 4.2.2 rom for your phone (step 1 has links to the Verizon and ATT versions), as that is where you'll get the .IMG files, logo.bin and other files you'll need in step 4 and 5.
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools
Click to expand...
Click to collapse
Thanks, unfortunately the Slapmymoto thread is 80 pages long and growing, so it's hard to get anything useful out of it. This is what I thought I was supposed to do but I wasn't certain.
Related
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
dray_jr said:
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
Click to expand...
Click to collapse
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Cozume said:
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Click to expand...
Click to collapse
as for the logo i am not sure i think you should be ok .
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go,
and anytime i flash something i always wipe the cache/davlik
dray_jr said:
and anytime i flash something i always wipe the cache/davlik
Click to expand...
Click to collapse
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Cozume said:
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Click to expand...
Click to collapse
you dont have too but it is recommended
dray_jr said:
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go
Click to expand...
Click to collapse
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Melarsa said:
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Click to expand...
Click to collapse
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Got it, that's what I'll do when the time comes. Thanks!
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
piccit said:
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
Click to expand...
Click to collapse
I thought it might be different because I'm rooted, and encrypted.
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
flashallthetime said:
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'm not using a custom ROM though.
fbiryujin said:
I'm not using a custom ROM though.
Click to expand...
Click to collapse
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
flashallthetime said:
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
So far no official update available to me even after flashing the stock image from Moto. My biggest goal here is to find a way to backup and restore nandroids from the encrypted phone.
Flash and relock Moto X manually
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
_slam said:
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
Click to expand...
Click to collapse
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
_slam said:
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
Click to expand...
Click to collapse
1) You don't need to do much. Revert the Entitlement hack you did, you need the one that came on the device, not a hacked one.
2) Flash the stock recovery back to your phone. You'll need the stock recovery to install the OTA. Just do it the same way you flashed TWRP to your phone but use the stock recovery.img file from the 4.4 .sbf ( http://sbf.droid-developers.org/download.php?device=0&file=5 )
You will NOT lose root flashing the stock recovery, you will NOT lose root taking the OTA.
After updating, use Xposed and the Moto Tether module for tethering instead of using a hacked version of the app.
shadowmonk36 said:
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
Click to expand...
Click to collapse
If you have the Dev edition from VZW, it's simple to install the OTA.
This is what I did as I had root and xposed installed.
1. Download 4.4.2 file from XDA and cut and paste it from download folder to root of sdcard
2. Flash stock 4.4 recovery image via fastboot.
3. Flash 4.4 system image using mfastboot (must use mfastboot)
4. Boot into recovery
5. Apply update and selected the OTA zip.
6. Reboot
7. Power down and boot back into fastboot.
8. Flash TWRP, allow it to root, reboot.
9. Reinstall Xposed framework.
All my data and settings were still there. Even my xposed modules reactivated. No additional setup and my phone was exactly the same but had 4.4.2.
Only caveat is only do this if you've never installed other OS's and have only taken official OTAs from VZW. You need to be on the right bootloader. Don't brick your phone.
Sent from my Dev Edition Moto X
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
As far as I can figure, the only way would to use an app to backup the data, flash back to factory, re-root and restore the data. The OTA update will remove root access. I would do a backup with CWM first if possible.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
if you know what you actually changed with root permissions then you can just flash stock recovery onto the phone then remove all things root and put everything back to normal stock (like unfreezing things out of tibu or whatever) then take the ota. if you are not sure what you changed, you can flash recovery and system then take the ota (assuming you didn't flash new kernals or anything else major).
And if you just want to keep data then you can flash stock ota with rsdlite and remove the two entries that erase data and cache in the xml file. Then take the ota. or flash the fxz and remove the same data erasing entries in the xml
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Schaweet said:
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Click to expand...
Click to collapse
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
robwege said:
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Schaweet said:
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Click to expand...
Click to collapse
I kept the old boot animation file so I can just move it back.
Sent from my XT1060 using XDA Premium 4 mobile app
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Schaweet said:
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
OK. I think I will do your method instead. I will unfreeze the apps, install old boot logo and disable xposed just to be safe. Then I will do your method. Wish me luck.
Sent from my XT1060 using XDA Premium 4 mobile app
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
You don't even need an unlocked bootloader, you can still flash stock images on a locked bootloader. Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
eksasol said:
Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
Click to expand...
Click to collapse
You are correct. You can only flash a custom recovery if your bootloader is unlocked. That is what unlocking your bootloader allows you to do - flash unsigned recovery files (i.e., custom recoveries) and obviously, TWRP is not signed by motorola. Then once you have a custom recovery, the custom recovery allows you to flash unsigned operating systems.
If your bootloader is locked, you cannot flash an unsigned recovery.
Schaweet said:
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I meant step 7.
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Click to expand...
Click to collapse
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
NightThyme said:
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
Click to expand...
Click to collapse
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Sent from my Dev Edition Moto X
Schaweet said:
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Click to expand...
Click to collapse
This.
If I wanted to go back to stock from an aosp based ROM could I use the mfastboot recovery and system method or do I ha e to rsd.... I'm unlocked btw
Sent from my Moto X using Tapatalk
Hi, I have a republic wireless moto x I just successfully rooted and updated to 4.4.2 from 4.2.2 with a locked bootloader with no write protection (wp)
Since I updated it to 4.4.2 I have this error that pops up that I can not resolve
"Unfortunately, the process com.motorola.process.system has stopped"
I googled several pages of several website results and several pages of google but can not find the solution.
Solutions found was to:
Safe Mode (I tried this first with no apps installed on non safemode and non system apps updated, didn't work and popped up even on safe mode)
Change date & time method (didn't work)
Wipe Cache (didn't work)
Wipe Cache & dalvik cache (didn't work)
I am debating about factory reset but unsure if it will make me lose my root because I have a locked bootloader (if that matters in anyway I am still new to this, and that my moto x is from republic wireless not like other carriers with unlocked bootloaders).
Please help me and discuss with me how I can get rid of that error.
androiddoglover6969 said:
Hi, I have a republic wireless moto x I just successfully rooted and updated to 4.4.2 from 4.2.2 with a locked bootloader with no write protection (wp)
Since I updated it to 4.4.2 I have this error that pops up that I can not resolve
"Unfortunately, the process com.motorola.process.system has stopped"
I googled several pages of several website results and several pages of google but can not find the solution.
Solutions found was to:
Safe Mode (I tried this first with no apps installed on non safemode and non system apps updated, didn't work and popped up even on safe mode)
Change date & time method (didn't work)
Wipe Cache (didn't work)
Wipe Cache & dalvik cache (didn't work)
I am debating about factory reset but unsure if it will make me lose my root because I have a locked bootloader (if that matters in anyway I am still new to this, and that my moto x is from republic wireless not like other carriers with unlocked bootloaders).
Please help me and discuss with me how I can get rid of that error.
Click to expand...
Click to collapse
You shouldn't have done it. You obviously didn't read or follow any of the guides here or you would have known better.
There was ONE (very tricky and convoluted) way of retaining root and it involves SafeStrap.
Sorry to say - there will likely be no root in your future.
A factory reset will most likely not help. You will have to download the 4.4.2 SBF and re-flash the entire stock rom.
There's a guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
^ This is the only way to get your phone back to being usable again. MAKE SURE you do NOT try to flash anything but 4.4.2. Flashing a prior version will likely permanently brick your phone.
After this process, the ONLY way you're going to obtain ROOT is to unlock your BL.
I hate to hear this happened to you, but its posted -all over- this forum that you cannot take the 4.4.2 OTA if you are rooted on a previous version. If you had followed the guide, and used Safestrap, you would be OK.....but now its too late. Once you've flashed the 4.4.2 OTA, it updates the bootloader, patching all of the exploits we used previously. Game Over.
Good Luck
samwathegreat said:
You shouldn't have done it. You obviously didn't read or follow any of the guides here or you would have known better.
There was ONE (very tricky and convoluted) way of retaining root and it involves SafeStrap.
Sorry to say - there will likely be no root in your future.
A factory reset will most likely not help. You will have to download the 4.4.2 SBF and re-flash the entire stock rom.
There's a guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
^ This is the only way to get your phone back to being usable again. MAKE SURE you do NOT try to flash anything but 4.4.2. Flashing a prior version will likely permanently brick your phone.
After this process, the ONLY way you're going to obtain ROOT is to unlock your BL.
I hate to hear this happened to you, but its posted -all over- this forum that you cannot take the 4.4.2 OTA if you are rooted on a previous version. If you had followed the guide, and used Safestrap, you would be OK.....but now its too late. Once you've flashed the 4.4.2 OTA, it updates the bootloader, patching all of the exploits we used previously. Game Over.
Good Luck
Click to expand...
Click to collapse
I did not have a root before 4.4.2. And I did not take the 4.4.2 OTA. I did follow the guide and have used Safestrap and still have it. What do you mean flash the 4.4.2 OTA? You mean installing it through the update notification? Well I didn't do that if that is what you meant. I flashed through the using the guide to get me no WP, root, and 4.4.2. So am I still doing it wrong?
androiddoglover6969 said:
I did not have a root before 4.4.2. And I did not take the 4.4.2 OTA. I did follow the guide and have used Safestrap and still have it. What do you mean flash the 4.4.2 OTA? You mean installing it through the update notification? Well I didn't do that if that is what you meant. I flashed through the using the guide to get me no WP, root, and 4.4.2. So am I still doing it wrong?
Click to expand...
Click to collapse
Sorry for the confusion...
Hmm...you didn't mention safestrap in OP - just that you "successfully rooted and updated to 4.4.2 from 4.2.2"
OK so if you followed the guide exactly your bootloader should still be on the JellyBean bootloader.
Assuming you followed the guide, you can start over. If you're ABSOLUTELY SURE you didn't update to the 4.4.2 bootloader, then I suggest starting from scratch.
Use RSD Lite to restore the 4.2.2 (JellyBean) rom (Again, you've been warned. If theres any possibility you flashed the 4.4.2 bootloader last time, this WILL brick your phone) Also, be careful to NOT flash the 4.4.2 ROM, or you will NOT be able to root as this patches the exploit.
Just follow the guide step-by-step: http://forum.xda-developers.com/moto-x/general/guide-republic-wireless-moto-x-kitkat-4-t2738233
The first step is to restore back the 4.2.2 stock rom, so this is where you should start. Don't forget to re-install safestrap and MotoWpNoMo as described.
Please let us know how it works out.
samwathegreat
samwathegreat said:
Sorry for the confusion...
Hmm...you didn't mention safestrap in OP - just that you "successfully rooted and updated to 4.4.2 from 4.2.2"
OK so if you followed the guide exactly your bootloader should still be on the JellyBean bootloader.
Assuming you followed the guide, you can start over. If you're ABSOLUTELY SURE you didn't update to the 4.4.2 bootloader, then I suggest starting from scratch.
Use RSD Lite to restore the 4.2.2 (JellyBean) rom (Again, you've been warned. If theres any possibility you flashed the 4.4.2 bootloader last time, this WILL brick your phone) Also, be careful to NOT flash the 4.4.2 ROM, or you will NOT be able to root as this patches the exploit.
Just follow the guide step-by-step: http://forum.xda-developers.com/moto-x/general/guide-republic-wireless-moto-x-kitkat-4-t2738233
The first step is to restore back the 4.2.2 stock rom, so this is where you should start. Don't forget to re-install safestrap and MotoWpNoMo as described.
Please let us know how it works out.
samwathegreat
Click to expand...
Click to collapse
Aslo, before I start to do the RSD Lite to restore the 4.2.2. Is there any other way how I can identify what is causing that error "com.motorola.process.system"? And isolate and get rid of that problem somehow or finding that stock app and preventing it from doing that?
androiddoglover6969 said:
Aslo, before I start to do the RSD Lite to restore the 4.2.2. Is there any other way how I can identify what is causing that error "com.motorola.process.system"? And isolate and get rid of that problem somehow or finding that stock app and preventing it from doing that?
Click to expand...
Click to collapse
Its extremely difficult to know why you are getting the error, but if you RSD Lite and start over, it will fix this issue.
Far too many people are running safestrap and not receiving the error. Likely there is a file on your device corrupted somewhere. RSD Lite will fix it as it completely restores the all of the partitions.
Just go -slow- step-by-step, and post here if you get confused or have questions. We will get your phone back to normal...
On another note....if you have $45 laying around, I highly suggest you email the gentleman from China. Once unlocked, you won't have to go through this long drawn-out process. You simply SBF back to stock, fastboot flash TWRP, and you're done. TWRP will install su-installer for you.
Your choice. The BL unlock method is best because you have permanent access and can never lose root.
Safestrap method will work as well, but you have to be very careful to not accept any new OTAs until the devs find a solution and post it here.
Good Luck.
samwathegreat said:
Its extremely difficult to know why you are getting the error, but if you RSD Lite and start over, it will fix this issue.
Far too many people are running safestrap and not receiving the error. Likely there is a file on your device corrupted somewhere. RSD Lite will fix it as it completely restores the all of the partitions.
Just go -slow- step-by-step, and post here if you get confused or have questions. We will get your phone back to normal...
On another note....if you have $45 laying around, I highly suggest you email the gentleman from China. Once unlocked, you won't have to go through this long drawn-out process. You simply SBF back to stock, fastboot flash TWRP, and you're done. TWRP will install su-installer for you.
Your choice. The BL unlock method is best because you have permanent access and can never lose root.
Safestrap method will work as well, but you have to be very careful to not accept any new OTAs until the devs find a solution and post it here.
Good Luck.
Click to expand...
Click to collapse
Woops I responded to another post but I am going to expect my bootloader code.
What is the first step from all of this that I should do?
1. SBF = what exactly? Hitting the factory reset button?
2. Fastboot Flash TWRP ? So after SBF. Fastboot Flash TWRP is done in AP Fastboot screen? Stock Recovery Screen? Or what screen exactly?
3. Did the guide I do didn't safestrap (twrp?) installed the su-installer for me as well right? Just wondering.
androiddoglover6969 said:
Woops I responded to another post but I am going to expect my bootloader code.
What is the first step from all of this that I should do?
1. SBF = what exactly? Hitting the factory reset button?
2. Fastboot Flash TWRP ? So after SBF. Fastboot Flash TWRP is done in AP Fastboot screen? Stock Recovery Screen? Or what screen exactly?
3. Did the guide I do didn't safestrap (twrp?) installed the su-installer for me as well right? Just wondering.
Click to expand...
Click to collapse
1.)
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
Download the correct file for your carrier and try to flash with RSD lite.
You can find a great guide here: http://forum.xda-developers.com/moto...using-t2446515
PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Basically, an SBF is a complete STOCK image of the original filesystem (all partitions). By SBFing, you will be 100% back to factory stock. This method (SBFing) will actually fix a corrupted filesystem.
A "factory reset" does NOT do this. I highly suggest you do the SBF back to stock, and not try just reseting. If there is corruption, reset won't fix it.
Don't bother setting up any apps yet or setting up the phone. Wait until you complete the entire process.
2.
Yes! You'll flash TWRP from the "AP Fastboot" screen (bootloader).
UNLOCK YOUR BOOTLOADER FIRST. Otherwise you won't be able to flash TWRP custom recovery.
Now unplug the USB cord, and power off your device. Hold down the VOL DOWN button, and power back on. You will now be in bootloader (fastboot) mode. Plug the USB back into the phone now.
You must have "mfastboot" downloaded. You'll type:
mfastboot flash recovery twrp_file_you_downloaded.img (obviously replace with the actual filename)
You can find complete instructions here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
P.S. If the download link for TWRP in the original post does not work, look near the end of the thread. Someone else re-uploaded it.
3.
Its entirely possible that something went afoul during your flashing process. I doubt the guide is to blame, because nearly everyone reported success. Sometimes things just go wrong...?
Good Luck.
samwathegreat said:
1.)
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
Download the correct file for your carrier and try to flash with RSD lite.
You can find a great guide here: http://forum.xda-developers.com/moto...using-t2446515
PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Basically, an SBF is a complete STOCK image of the original filesystem (all partitions). By SBFing, you will be 100% back to factory stock. This method (SBFing) will actually fix a corrupted filesystem.
A "factory reset" does NOT do this. I highly suggest you do the SBF back to stock, and not try just reseting. If there is corruption, reset won't fix it.
2.
Yes! You'll flash TWRP from the "AP Fastboot" screen (bootloader). You must have "mfastboot" downloaded. You'll type:
mfastboot flash recovery twrp_file_you_downloaded.img (obviously replace with the actual filename)
You can find complete instructions here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
P.S. If the download link for TWRP in the original post does not work, look near the end of the thread. Someone else re-uploaded it.
3.
Its entirely possible that something went afoul during your flashing process. I doubt the guide is to blame, because nearly everyone reported success. Sometimes things just go wrong...?
Good Luck.
Click to expand...
Click to collapse
On step 1. It is republic wireless 4.4.2 that I should download right. Correct me if I'm wrong.
Also is there RSDlite for mac or similar software? I tried to google it and xda'd it but I don't think there is. Or any other way to flash it into it.
androiddoglover6969 said:
On step 1. It is republic wireless 4.4.2 that I should download right. Correct me if I'm wrong.
Also is there RSDlite for mac or similar software? I tried to google it and xda'd it but I don't think there is. Or any other way to flash it into it.
Click to expand...
Click to collapse
If you have already received your code, yes, you should flash republic 4.4.2
If you haven't...just wait until you have it for sure. Once you flash 4.4.2 theres no going back. As long as you get unlock code, this is no problem....you'll be able to root regardless.
But, if for any reason he doesn't have your code (unlikely), you'll never be able to root once on 4.4.2....
As of right now (If I understand you completely), since you followed the safestrap guide, you SHOULD be on the jellybean bootloader, so the steps would be different if you didn't have an unlock code (and wanted to retain root).
Don't worry about any of this until we know for sure if you can get unlocked. In the unlikely event you don't get a code, post back here and I will step you through it.
Otherwise (if you get code), yes, start by using RSD Lite to flash the Republic Wireless 4.4.2 SFB per my previous instructions.
EDIT:
Just read the part about being on a MAC. AFAIK, there is no RSD Lite for Mac. We will have to go another route, unless you want to install windows inside a virtual machine....The dev that created the Mac Tooklit sold his X, and its no longer supported.
We will just do manual flashing...make sure you downloaded the "mfastboot" and followed all instructions on the RSD Lite thread I linked, EXCEPT follow the "Manual Flashing" instructions instead.
Extract the Republic Wireless SBF zip file Put the contents in to the same folder where fastboot and mfastboot are located. Here are the commands you will type after booting your X Into bootloader (Fastboot mode):
***Notice that mfastboot is used to flash the system.img. DONT try to use regular fastboot. Just type these commands one at a time.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier sprint ***be sure to type sprint. RW is a sprint MVNO, and I checked the xml file and this is the correct command for the Republic Wireless rom.
fastboot oem fb_mode_clear
Now reboot. Expect it to take a little longer than normal for the first boot-up. Congrats! You're now on 4.4.2 and your corruption issue will be a thing of the past.
Now Complete steps 2 & 3
samwathegreat said:
If you have already received your code, yes, you should flash republic 4.4.2
If you haven't...just wait until you have it for sure. Once you flash 4.4.2 theres no going back. As long as you get unlock code, this is no problem....you'll be able to root regardless.
But, if for any reason he doesn't have your code (unlikely), you'll never be able to root once on 4.4.2....
As of right now (If I understand you completely), since you followed the safestrap guide, you SHOULD be on the jellybean bootloader, so the steps would be different if you didn't have an unlock code (and wanted to retain root).
Don't worry about any of this until we know for sure if you can get unlocked. In the unlikely event you don't get a code, post back here and I will step you through it.
Otherwise (if you get code), yes, start by using RSD Lite to flash the Republic Wireless 4.4.2 SFB per my previous instructions.
EDIT:
Just read the part about being on a MAC. AFAIK, there is no RSD Lite for Mac. We will have to go another route, unless you want to install windows inside a virtual machine....The dev that created the Mac Tooklit sold his X, and its no longer supported.
We will just do manual flashing...make sure you downloaded the "mfastboot" and followed all instructions on the RSD Lite thread I linked, EXCEPT follow the "Manual Flashing" instructions instead.
Extract the Republic Wireless SBF zip file Put the contents in to the same folder where fastboot and mfastboot are located. Here are the commands you will type after booting your X Into bootloader (Fastboot mode):
***Notice that mfastboot is used to flash the system.img. DONT try to use regular fastboot. Just type these commands one at a time.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier sprint ***be sure to type sprint. RW is a sprint MVNO, and I checked the xml file and this is the correct command for the Republic Wireless rom.
fastboot oem fb_mode_clear
Now reboot. Expect it to take a little longer than normal for the first boot-up. Congrats! You're now on 4.4.2 and your corruption issue will be a thing of the past.
Now Complete steps 2 & 3
Click to expand...
Click to collapse
So what you showed me on manual way was if I was to install virtual windows right? Also that link showed it was 4.4 not 4.4.2... so am I still good or I shouldn't do that method? Thanks again for your effort.
androiddoglover6969 said:
So what you showed me on manual way was if I was to install virtual windows right? Also that link showed it was 4.4 not 4.4.2... so am I still good or I shouldn't do that method? Thanks again for your effort.
Click to expand...
Click to collapse
No. What I showed you was the manual fastboot method. This will run on Mac natively. You'll have to download the android SDK for mac, and install, then download the mfastboot binary (either 32 or 64 bit) here: https://gist.github.com/crazed/7670423 *** after you download the file (moto-fastboot-osx64), RENAME it to mfastboot.
Although the link on how to SBF back to stock shows android 4.4, it doesn't matter. The SBF process is the same no matter which version you are on. You just need to download the right carrier/version from here http://sbf.droid-developers.org/phone.php?device=0
Not to confuse you but if you were to install virtual windows, you could probably use the rsd lite method.
Do one but not both. The native (manual) version should be simpler for you. I had assumed you already had the necessary android SDK since you said you went through the whole safestrap process and everything. Were you on a different computer when you did that?
Have you received your code yet? Hold off on SBFing until you have it in hand.
samwathegreat said:
No. What I showed you was the manual fastboot method. This will run on Mac natively. You'll have to download the android SDK for mac, and install, then download the mfastboot binary (either 32 or 64 bit) here: https://gist.github.com/crazed/7670423 *** after you download the file (moto-fastboot-osx64), RENAME it to mfastboot.
Although the link on how to SBF back to stock shows android 4.4, it doesn't matter. The SBF process is the same no matter which version you are on. You just need to download the right carrier/version from here http://sbf.droid-developers.org/phone.php?device=0
Not to confuse you but if you were to install virtual windows, you could probably use the rsd lite method.
Do one but not both. The native (manual) version should be simpler for you. I had assumed you already had the necessary android SDK since you said you went through the whole safestrap process and everything. Were you on a different computer when you did that?
Have you received your code yet? Hold off on SBFing until you have it in hand.
Click to expand...
Click to collapse
Havn't got the code yet. And I did the motowpnomo on windows 8. Everything else did on mac.
Just got my code at 23hrs.
I just wanted to do add onto the process and make minor adjustments to make it clear.
Did Step 1.
and then at the end
He will say reboot, but don't go waiting to install your apps or update it or setting it up. Just start it up normal power up. Then when it says select language (not sure if needs debugging or not but I did) go to developer options by clicking on settings. go all the way down to "about phone" tap on "build number" a couple times you will see developer options pop up. Go back and go down to developer options and go find usb debugging. Then hit accept on phone pop up when usb debugging is enabled so your phone trust your computer. then do ./adb reboot bootloader
It should get you into ap fastboot mode then do my step 2.
Step 2 - Unlock bootloader before doing mfastboot-ing the twrp so you don't get the
invalid image size on your phone
or
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure) on your terminal
So by doing this to unlock bootloader
fastboot getvar all
then
fastboot oem unlock CODEHERE
Should give you a "unlock" blue text with black screen.
Then the step 2 mentioned by samwathegreat for TWRP which will download the file without the invalidity error message on both computer or moto x on ap fastboot screen.
Then step 3. I used the Down arrow to select "recovery" which gave me the TWRP screen.
Step 4. I went into the TWRP screen and hit reboot and a pop up for SuperSU popped up notifying me to install SuperSU. Swipe next and it'll install and then voila!
Step 5. Click on SuperSu app and it should reboot and try to install.
Step 6. Hit the thanks button to samwathegreat
androiddoglover6969 said:
Havn't got the code yet. And I did the motowpnomo on windows 8. Everything else did on mac.
Just got my code at 23hrs.
I just wanted to do add onto the process and make minor adjustments to make it clear.
Did Step 1.
and then at the end
He will say reboot, but don't go waiting to install your apps or update it or setting it up. Just start it up normal power up. Then when it says select language (not sure if needs debugging or not but I did) go to developer options by clicking on settings. go all the way down to "about phone" tap on "build number" a couple times you will see developer options pop up. Go back and go down to developer options and go find usb debugging. Then hit accept on phone pop up when usb debugging is enabled so your phone trust your computer. then do ./adb reboot bootloader
It should get you into ap fastboot mode then do my step 2.
Step 2 - Unlock bootloader before doing mfastboot-ing the twrp so you don't get the
invalid image size on your phone
or
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure) on your terminal
So by doing this to unlock bootloader
fastboot getvar all
then
fastboot oem unlock CODEHERE
Should give you a "unlock" blue text with black screen.
Then the step 2 mentioned by samwathegreat for TWRP which will download the file without the invalidity error message on both computer or moto x on ap fastboot screen.
Then step 3. I used the Down arrow to select "recovery" which gave me the TWRP screen.
Step 4. I went into the TWRP screen and hit reboot and a pop up for SuperSU popped up notifying me to install SuperSU. Swipe next and it'll install and then voila!
Step 5. Click on SuperSu app and it should reboot and try to install.
Step 6. Hit the thanks button to samwathegreat
Click to expand...
Click to collapse
Excellent! Thanks for pointing that the instructions didn't specify that you must unlock your BL before flashing TWRP. Edited Post # 8 to include the step. You can also unlock BL before you start any of the steps, but must do it before flashing custom recovery as you have pointed out.
I did suggest a slightly different method, however, that doesn't require enabling developer options or usb debugging. If you unplug the phone and power it off, you can get straight into fastboot mode without 'adb reboot bootloader'. You just hold down VOL DOWN, and power it on. Then you plug the USB cord back in. It only works if you unplug the phone first....for some reason if you leave it plugged in, you can't power off the phone...it just immediately reboots.
So, to wrap this all up, just a couple more questions:
Did you complete the entire process on your Mac? And can you confirm that the error you were originally receiving (in Original Post) is no longer popping up?
And finally, check out xposed framework installer and "gravity box" mod. You can do some really cool mods with gravity box. I suggest you boot into TWRP and make a nandroid backup -just in case- before you go playing around with xposed.
Have fun.
samwathegreat said:
Excellent! Thanks for pointing that the instructions didn't specify that you must unlock your BL before flashing TWRP. Edited Post # 8 to include the step. You can also unlock BL before you start any of the steps, but must do it before flashing custom recovery as you have pointed out.
I did suggest a slightly different method, however, that doesn't require enabling developer options or usb debugging. If you unplug the phone and power it off, you can get straight into fastboot mode without 'adb reboot bootloader'. You just hold down VOL DOWN, and power it on. Then you plug the USB cord back in. It only works if you unplug the phone first....for some reason if you leave it plugged in, you can't power off the phone...it just immediately reboots.
So, to wrap this all up, just a couple more questions:
Did you complete the entire process on your Mac? And can you confirm that the error you were originally receiving (in Original Post) is no longer popping up?
And finally, check out xposed framework installer and "gravity box" mod. You can do some really cool mods with gravity box. I suggest you boot into TWRP and make a nandroid backup -just in case- before you go playing around with xposed.
Have fun.
Click to expand...
Click to collapse
Yes I complete the whole process on the Mac. Yes the original error is no longer popping up. What is a nandroid back up? I did a back up after I installed all my apps and updated it and dragged that copy to my desktop and uploaded it to my cloud.
I hear about xposed framework and gravity box but I have no clue what it looks like and also forgot what nandroid is but I'll look it up.
And yes android reboots can't stay on shut down when cord is connected. Which is funny.
androiddoglover6969 said:
Yes I complete the whole process on the Mac. Yes the original error is no longer popping up. What is a nandroid back up? I did a back up after I installed all my apps and updated it and dragged that copy to my desktop and uploaded it to my cloud.
I hear about xposed framework and gravity box but I have no clue what it looks like and also forgot what nandroid is but I'll look it up.
And yes android reboots can't stay on shut down when cord is connected. Which is funny.
Click to expand...
Click to collapse
If you backed up from within custom recovery (TWRP), thats the same thing. Some recoveries call them ''backup', some 'nandroid'....same thing.
Thanks for the final follow-up. Take care...
samwathegreat said:
If you backed up from within custom recovery (TWRP), thats the same thing. Some recoveries call them ''backup', some 'nandroid'....same thing.
Thanks for the final follow-up. Take care...
Click to expand...
Click to collapse
Also I installed everything I needed to from gravitybox and well framework xposed too. Which is very similar to jailbreak tweaks on the iPhone.
Thanks again.
This does work to upgrade from 4.4.2 to 4.4.4 and there was no data/setting loss. I am running Verizon, developer phone, rooted, with xposed. Here are the directions I used:
1. disable Xposed - I just went to the app and uninstalled it
2. boot into bootloader/fastboot - connect your computer to the phone via USB. Then push the down volume and power at the same time. This will take you to the bootloader/fastboot
3. flash stock recovery (fastboot flash recovery yourfilename.img) - to do this (and to flash stock system) you need the motorola fastboot files and you will need to use the command prompt on the PC. for directions and download for the fastboot files check out this link - http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ To actually download the stock recovery and stock system files you can download them here (look for 4.4.2 verizon - http://sbf.droid-developers.org/phone.php?device=0. I actually pasted the recovery.img/stock.img files into the windows fastboot folder and accessed CMD prompt from there to flash them. I flashed recovery then moved onto stock. I did not reboot until both were done.
4. flash stock system (fastboot flash system yourfilename.img)
5. reboot (stay in the CMD prompt and type - fastboot reboot)
6. update via OTA
7. reboot
You are now stock unrooted 4.4.4, so just re-apply root the same way you did the first time:
1. boot into bootloader/fastboot - you should be able to follow the directions from above to do this now
2. flash custom recovery - you should be able to follow the directions from above to do this now. Note that I tried CWM and it didnt work until I used TWRP. - download the latest version here and stick in the same fastboot folder you were using above - http://teamw.in/project/twrp2
3. boot to recovery - make sure you do this from the bootloader/fastboot screen. To do it, press down until you get to recovery then up to actually select it. I kept pressing power to select which doesnt actually select it.
4. flash SuperSU - this should be on your phone from the first time you rooted. If doing a new root you will need to get it first.
5. reboot
6. re-enable Xposed - i just reinstalled it and all of my settings were back
7. reboot
- BAM you are done!
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
Multiple reports all over the forum say YES. (must flash stock recovery back, FIRST -- OR just use the FXZ and don't worry about having to flash stock recovery...)
Also, to the OP: questions belong in Q&A, not General. See the 2nd Sticky post at the top of the General forum....please post in the correct forums in the future...
I have a vzw DE
I took the 4.4.4 FXZ file from the other thread and just flashed it, no prep, didn't disable xposed.I was flashing in fastboot, not recovery, so its not checking for intact files. Then had to twrp/root and re-enable xposed.
But if you want to take the OTA then your procedure would be good.
Ryphez said:
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
Click to expand...
Click to collapse
There is no difference whatsoever between an unlocked dev edition and any other unlocked X. The ONLY difference is the dev edition keeps its warranty when you unlock.
Whats the best twrp for root on 4.4.4
Mickoou said:
Whats the best twrp for root on 4.4.4
Click to expand...
Click to collapse
How about the latest version from the official source? Here: http://techerrata.com/browse/twrp2/ghost
It will root for you. Just flash w/fastboot, then "fastboot reboot-bootloader", then VOL DOWN to RECOVERY, and VOL UP to select it. When you go to exit, it will offer to install SuperSU Installer. Once booted, launch SuperSU Installer, and select Play Store method.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
No, you should be the guinea pig for all of us.
I can confirm that this works. I did it. I did not lose any data. It took about 20 minutes total. I already had everything installed otherwise you are looking at about 45 minutes.
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
KidJoe said:
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
Click to expand...
Click to collapse
Thanks for the tip. I believe I did it the way I mentioned because last time gravity box didnt have a wifi tether available so I had to modify the system files. this time I didnt touch them.
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
+1 :good:
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
zoid_99 said:
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
Click to expand...
Click to collapse
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Schaweet said:
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thank you Thank you.... That was it.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
1.6 SU was the only issue I had, I got the latest and had no issue
http://download.chainfire.eu/supersu
KidJoe said:
[*]Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Click to expand...
Click to collapse
Where do I get the stock recovery.img file?
Thank you!
fede_arg said:
Where do I get the stock recovery.img file?
Thank you!
Click to expand...
Click to collapse
The OP tells you in the very first post...
Maybe I'm just super bad at finding things in this forum but I can't find any discussion on how to guard root when going up to 5.1. It looks like the only app for that (OTA Rootkeeper) is no longer working. Do I have to unroot my n6 before I upgrade to 5.1?
Simple answer, yes.
Longer answer, you'll need to be 100% stock for an OTA to work.
Bootloader unlocked is okay...but everything else... System, kernel and recovery must be 100% stock firmware or else OTA will fail.
carlz28 said:
Simple answer, yes.
Longer answer, you'll need to be 100% stock for an OTA to work.
Bootloader unlocked is okay...but everything else... System, kernel and recovery must be 100% stock firmware or else OTA will fail.
Click to expand...
Click to collapse
Ok, so I have unlocked bootloader and I'm rooted. The OTA update just became available to me today. What are my next steps?
Sauveur said:
Maybe I'm just super bad at finding things in this forum but I can't find any discussion on how to guard root when going up to 5.1. It looks like the only app for that (OTA Rootkeeper) is no longer working. Do I have to unroot my n6 before I upgrade to 5.1?
Click to expand...
Click to collapse
Dude I had these same questions you can use the WugFresh Tool-Kit it works like a charm you do have to un-root but you can do so by keeping your data without a wipe just go to his website.
defyiant said:
Dude I had these same questions you can use the WugFresh Tool-Kit it works like a charm you do have to un-root but you can do so by keeping your data without a wipe just go to his website.
Click to expand...
Click to collapse
carlz28 said:
Simple answer, yes.
Longer answer, you'll need to be 100% stock for an OTA to work.
Bootloader unlocked is okay...but everything else... System, kernel and recovery must be 100% stock firmware or else OTA will fail.
Click to expand...
Click to collapse
Thank you both! I just need to find the Mac version of Wug's toolkit....
Sauveur said:
Maybe I'm just super bad at finding things in this forum but I can't find any discussion on how to guard root when going up to 5.1. It looks like the only app for that (OTA Rootkeeper) is no longer working. Do I have to unroot my n6 before I upgrade to 5.1?
Click to expand...
Click to collapse
Just use fastboot flash.
Go to Google and download the factory image for the one you want to flash. Unzip Factory image until you see system.img, recovery.img, boot.img, radio.img, and bootloader.img and copy them into your adb folder. On mine it is C/Androidsdk/sdk/platform-tools. Delete anything else unless you just want to keep it. DO NOT FLASH userdata.img as it will wipe data.
If any of the above have names that are different, change them to what is above.
Connect the phone to your computer and open a command prompt and get to your adb folder.
adb reboot bootloader
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
You are now updated with unlocked bootloader. You will have to re root the device. I suggest just putting TWRP on it and when you open twrp and select reboot it will ask if you want to root the device.
I found this info in another comment section on another site and can't remember the name to give credit. He's a boss though.