[Q] Rooted 4.4.2 with locked bootloader factory reset safe? - Moto X Q&A

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.

Related

[GUIDE][VIDEO] Droid MAXX/Ultra/Mini - Return to stock (RSD Lite OR manual flash)

NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
FYI NOTE - I originally did this for the Moto X back when I still had it. Video below was on a VZW Moto X back in September. I also did the EXACT same process when I received my MAXX two days ago. Exact same hardware, same process.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Devices: VZW Moto X AND Droid MAXX
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
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 vzw
fastboot oem fb_mode_clear
Excellent guide, I'm not bricked but I'm pretty sure it will be useful for someone else!, thanks for your time and effort
Sent from my Nexus 7 using XDA Premium 4 mobile app
Nice guide. Used rsdlite and flashed stock. Just upgraded 4.4. Very satisfied with new version along with nova pro
Sent from my XT1080 using xda app-developers app
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
Yes it does, I'm using a custom radio too, I'm waiting for the kit Kat sbf
Sent from my Nexus 7 using XDA Premium 4 mobile app
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Sent from my XT1080 using xda app-developers app
YoungSkeezy said:
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Click to expand...
Click to collapse
Just the radio that leaked that everyone thought was a test of AWS. The radio worked, but I didn't notice any higher speeds.
No, you don't need S-OFF to flash a custom radio.
will it work if i want to downgrade from 4.4 to 4.2 ?
No
YOU SIR...ARE THE MAN!!!!! worked flawlessly..i thought i had permanently bricked my replacement phone.. but thanks to you and another fellow who directed me to the FXZ files.. the new phone is up and running..and I can send the old one back!!!
Worked great. Not difficult at all.
Sent from my XT1080 using xda app-developers app
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
kanagadeepan said:
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
Click to expand...
Click to collapse
No, this will NOT re-lock your bootloader. It does flash the stock recovery and unroot you so you can receive an OTA.
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
kanagadeepan said:
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
Click to expand...
Click to collapse
yes, just flash twrp and reroot
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Jay_P11 said:
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Click to expand...
Click to collapse
Bootloader
akellar said:
Bootloader
Click to expand...
Click to collapse
Alright thanks for clarifying. My battery life is absolutely horrid, about 8 hours MAX per day before I need a charge, and it was never like this on 4.2.2 :/ 4.4's "Battery Saver" feature in WiFi settings never works anymore either, it just turns itself off the second I turn it on. Definitely some major bugs in this build, and I'm hoping they get fixed in the next update. If they don't, then I'm just going to pony up $300 for early termination and get an LG G2.
One more thing, this should work for restoring back to factory 4.4 on 4.4 then right? Maybe my update is broken and it just needs a clean install for the battery saver to work?
TechSavvy2 said:
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
Click to expand...
Click to collapse
So I just send up sitting at "waiting for device" after executing that line. RSD won't recognize my phone either--tried different cables.
Thoughts?

[Q] please help possible full brick

Hopefully someone is able to help...
I had my tmo moto x unlocked with twrp and root and I tried a factory reset through the twrp recovery and it erased all the software. It booted to the setup screen where I proceeded to log in with Google but it didn't work I think and when it got the home screen it just showed a loading circle and that's it and stupid me I didn't make a backup before
I've tried using the tool in the android development thread to flash back to stock but now my phone doesn't even boot at all I can get to the bootloadwr and I can successfully flash files through the Motorola tool by removing the proper line in the XML file but my phone still don't boot
It just flashes the little android laying down and says error every 5 seconds I don't know what to do anymore I've searched all over and no matter what I can't get the phone to boot
Thanks for the help if any
1. With an unlocked bootloader, you're not fully bricked if you can get to the bootloader.
2. Download the SBF file for your variant here http://sbf.droid-developers.org/phone.php?device=0. If you're already on the 4.4.2 bootloader, download only the 4.4.2 SBF file.
3. Learn how to use fastboot/mfastboot and adb. Follow the steps in the "return to stock" section here http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358.
4. Extract the SBF file, boot into the bootloader, type what's in the "return to stock" section verbatim. Skip the fastboot oem lock step though and don't copy/paste.
5. Stop using toolboxes and scripts until you understand how fastboot and adb work. They'll save your ass each and every time.
nhizzat said:
1. With an unlocked bootloader, you're not fully bricked if you can get to the bootloader.
2. Download the SBF file for your variant here http://sbf.droid-developers.org/phone.php?device=0. If you're already on the 4.4.2 bootloader, download only the 4.4.2 SBF file.
3. Learn how to use fastboot/mfastboot and adb. Follow the steps in the "return to stock" section here http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358.
4. Extract the SBF file, boot into the bootloader, type what's in the "return to stock" section verbatim. Skip the fastboot oem lock step though and don't copy/paste.
5. Stop using toolboxes and scripts until you understand how fastboot and adb work. They'll save your ass each and every time.
Click to expand...
Click to collapse
thank you so much for the help but for some reason when i flash the files to my device they run the process perfectly fine but when the phone boots its still doing the same thing where it just flashes the android on his back for like a second every five seconds or so. I did the 4.4.2 update first then i tried 4.2.2 just to give it a shot but i dont think that flashed right since its says an error about downgrading the security in the bootloader
please if there are any other suggestions im open ears ive searched everywhere and tried everything but i still cant get the phone to actually boot up at all
thanks for the help
genaro12543 said:
thank you so much for the help but for some reason when i flash the files to my device they run the process perfectly fine but when the phone boots its still doing the same thing where it just flashes the android on his back for like a second every five seconds or so. I did the 4.4.2 update first then i tried 4.2.2 just to give it a shot but i dont think that flashed right since its says an error about downgrading the security in the bootloader
please if there are any other suggestions im open ears ive searched everywhere and tried everything but i still cant get the phone to actually boot up at all
thanks for the help
Click to expand...
Click to collapse
once you've upgraded to 4.4.2, you can't go back to 4.2.2.
as mentioned, download the 4.4.2 fastboot files and flash each partition.
make sure to wipe data and cache once all partitions are flashed.
here are some more notes regarding flashing:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682

Need help upgrading to 5.1, Tired of flashing all the things.

My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.
Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.
I tried using tge NRT to flash it back to stock but it didn't work.
I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1
When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...
celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.
prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.

[MoFo IMG] 5.1 Rooted AT&T XT1097 with Tether

Below are the instructions for using MoFo to flash the AT&T XT1097 to 5.1. The rooted image has a modified build.prop file for free tether. Thanks go to @Slack3r for making the ext4 image and @btdownloads7 for developing the root method.
Since this is a 5.1 image, in order to get it to boot, you need to do the following BEFORE flashing the 5.1 system image:
1) Download the stock 5.1 files and extract them:
https://mega.co.nz/#!bN0BjKbI!zzq5b9wZBo-XFGNkcWtgw7mnXZgC5BWrEC-GZcGLELo
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /cache - YOU MUST DO THIS!
3) Reboot into bootloader mode and run the commands below to flash the following stock 5.1 files for the XT1097:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
Do NOT flash the 5.1 bootloader (motoboot.img) or partition table (gpt.bin) - if you do, you will not be able to use MoFo ever again!!!!!
4) Download the rooted 5.1 image from here, extract it and flash it using MoFo.
https://mega.co.nz/#!ct8DlQxQ!DRMC_TvCcUk7V-FjCBfjsmIoOvw_f0WEdM7gx2waqzM
MD5 of the unzipped file = 146B6A65D925B985857A2F28D4294765
Note that with the XT1096 we had issues if we tried to boot into recovery after initially flashing the 5.1 system image so instead of booting into recovery and wiping cache where you might get weird flashing dead androids, we had to boot into system first.
Obviously if you want Xposed or anything else in the image, someone will need to add it in.
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Casyis said:
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Click to expand...
Click to collapse
No, the instructions as written in the OP are complete. Like the instructions say, you need to do step 2:
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /data/cache - YOU MUST DO THIS!
Then you can flash the rest of the 5.1 stock files for your device EXCEPT for the bootloader (motoboot.img) and partition table (gpt.bin). Then use MoFo to flash the rooted 5.1 image for your device.
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Casyis said:
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Click to expand...
Click to collapse
This was happening with the XT1096 - you have to get it into system before recovery. You likely hit the wrong button and ended up in recovery instead of system. But once you get it into system, then it is fine.
Thanks again @JulesJam I am downloading now! Do you notice a big performance difference in 5.1? Will be nice to finally kill these memory bugs, so major thanks for that!
The OS is much snappier than 5.0.2. You can tell by going into multitasking and seeing how quickly the tiles load. Very, very nice. No re-draws at all yet since I flashed.
Step 2 implies that I'm already rooted. If I'm not, I assume I need to start with Step 0: Root the device with a 5.0 IMG?
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
bamachevrolet said:
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
Click to expand...
Click to collapse
FYI - like it says in the MoFo Noob Guide - MoFo trips the root checker and it is not able to be undone by flashing back to stock. I don't know how AirWatch works, but if it looks at the qe, then it will see you as rooted even if you aren't.
First thing I would do is flash back to 5.0.2 by flashing the stock 5.0.2 firware (link is in the MoFo Noob Guide)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1 (repeat this for all of the sparsechunks)
then boot into recovery and wipe the cache. Then boot into system. I believe it will need to downgrade the sensor firmware so allow that to happen.
Then boot into bootloader mode and see if your software status still says modified or not. Then boot into recovery and see what your qe status is. If after that your software status is still modified and your qe is still 1/1, I would do a factory reset and see if that corrects it. It probably won't though.
You will then have to decide whether or not you want to take the 5.1 OTA because your phone is going to want to upgrade. Instead of taking the 5.1 OTA which will upgrade your bootloader and partition table, you have the option of flashing stock 5.1 everything but the motoboot.img and gpt.bin. That would keep you stock 5.1 but still keep your bootloader and partition table on 5.0.2 so that if you wanted to sell the phone later, you could sell it with a copy of MoFo that still works. I put this out there because idk how AirWatch works and if flashing back to stock doesn't change your software status from modified or your qe from 1/1, you may not be able to use AirWatch, idk.
Thank you so much for the detailed explanation @JulesJam . Unfortunately I followed the instructions to the T and didn't run into any issues until I tried to boot into recovery. I got the dead android with a line under saying "no command". So I tried running system first. I got through the boot animation and then a black screen. I let the black screen sit for 30 min and nothing happened. I had the exact issue when installing 5.1, I was able to get it to boot using BT tools. Unfortunately this is not working now. I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
bamachevrolet said:
I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
Click to expand...
Click to collapse
For sure you flashed the 5.0.2 logo.bin, boot.img and all of the 5.0.2 system sparsechunks? That sounds like the system partition was not flashed properly.
Perhaps the 5.0.2 system files you have are corrupted? Are you sure the files you have are the stock 5.0.2 files for the AT&T XT1097?
bamachevrolet said:
I got the dead android with a line under saying "no command". !
Click to expand...
Click to collapse
That's OK as long as he is not flashing. When you have the dead android, go ahead and press and hold power then tap volume up to get into recovery and wipe the cache.
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
bamachevrolet said:
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
Click to expand...
Click to collapse
How long do you let the blank screen sit before you try to get into bootloader mode? I remember sometimes it takes awhile for it to boot.
Also, the dalvik-cache may need to be wiped too. That would require a factory reset to do it so you could boot into recovery and do a factory reset. Unless there is some way to wipe the dalvik-cache from bootloader mode.
bamachevrolet said:
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
Click to expand...
Click to collapse
That's fine. I wasn't sure what number they started with.
bamachevrolet said:
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Click to expand...
Click to collapse
And after you do, let it sit at the blank screen for awhile to make sure that it isn't an issue of needing time to boot up. If it still won't boot, try the factory reset.
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!!
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
[/COLOR @JulesJam do you have a donation link?
bamachevrolet said:
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!![
Click to expand...
Click to collapse
Glad it worked out, sucks about the tasker profiles though. So it seems like the dalvik-cache has to be wiped, too. I will note that in the future people should delete the contents of the dalvik-cache folder before flashing back to the earlier version of the software.
Does your software status still say modified in bootloader mode? What is your qe when you boot into recovery?
bamachevrolet said:
@JulesJam do you have a donation link?
Click to expand...
Click to collapse
No but thanks for the offer. If you want to donate, please donate to the ASPCA.

[A2017U][TWRP System Image] Stock System Image of B20 for full stock restore and OTAs

THIS APPLIES ONLY TO THE A2017U VARIANT, DO NOT USE THIS FILE ON OTHER VERSIONS
Disclaimer - don't blame me if something goes wrong
As title says, this is a full stock unmodified B20 TWRP system image. It kan be used in addition to stock boot and recovery images to restore the US A7 to conditions which will be like stock and allow to flash upcoming OTA. This was tested by @jkuczera here http://forum.xda-developers.com/showthread.php?t=3459107
Link to system image
https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy
If you are BL unlocked, you will need to lock it before flashing old recovery and boot (this may not be necessary to get MR2 to flash, depending on what it checks, but the phone might not boot, unknown). This will make your phone verify boot, recovery and /system again, so flash TWRP from tenfar's thread to be able boot after relocking since his is signed
To restore, unzip the file above to TWRP folder on the SD Card, then in TWRP under mount points unmount /system and put check mark on mount system as read-only. The read-only part is important so that TWRP does not modify the /system apon exit. You can then restore boot, recovery and system image.
Another partition, fastboot, was altered if you applied B20_boot, but so far no OTA has check it so it should be fine as is. Chance is it will be just overwritten by next OTA, but in case that changes, info will be added. This step is more risky since it involves using dd command and has to be applied carefully.
EDIT: looks like @Unjustified Dev posted new build that will flash fastboot image http://forum.xda-developers.com/showpost.php?p=68677272&postcount=133
You should then boot to stock recovery and factory wipe
In case you did not dump your boot and recovery, they can be found in @rczrider's post here
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Thanks to @swehes for providing the space on his cloud for this file, @rczrider for rest of the files and @jkuczera for trying this all out
So you need TWRP for this, but will this overwrite the TWRP recovery and make it truly stock?
imp3r10 said:
So you need TWRP for this, but will this overwrite the TWRP recovery and make it truly stock?
Click to expand...
Click to collapse
Indeed and before rebooting , you MUST Wipe Data + Internal Storage, cuz you are flashing new boot and system and will get in conflicts if there no wipe.
Just for clarity sake these are the steps I need to take to get back to B20 from B20_Boot?
1. fastboot oem lock
2. put system image from OP's post AND stock_boot_backup.img AND stock_recovery_backup.img from rczrider's post into TWRP folder.
3. in TWRP unmount /system and check mark on mount system as read only.
4. Flash boot, recovery, and system image.
5. Wipe Data and Internal Storage.
6. Profit?
runderekrun said:
Just for clarity sake these are the steps I need to take to get back to B20 from B20_Boot?
1. fastboot oem lock
2. put system image from OP's post AND stock_boot_backup.img AND stock_recovery_backup.img from rczrider's post into TWRP folder.
3. in TWRP unmount /system and check mark on mount system as read only.
4. Flash boot, recovery, and system image.
5. Wipe Data and Internal Storage.
6. Profit?
Click to expand...
Click to collapse
Pretty much. I would reboot to stock recovery after and factory wipe from there. you might wan't to flash fastboot from B20 OTA for extra profit but seems like it's a moot point so far if you have seen the Unjustified Devs trick for BL unlock via TWRP
peramikic said:
Pretty much. I would reboot to stock recovery after and factory wipe from there. you might wan't to flash fastboot from B20 OTA for extra profit but seems like it's a moot point so far if you have seen the Unjustified Devs trick for BL unlock via TWRP
Click to expand...
Click to collapse
Thanks.
I'm having to do a warranty replacement on my device so i'll probably want to do the fastboot flash. Any idea where to get a fastboot image?
runderekrun said:
I'm having to do a warranty replacement on my device so i'll probably want to do the fastboot flash. Any idea where to get a fastboot image?
Click to expand...
Click to collapse
Step 6 to pull your own: http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Or you can download the one I pulled from my device (it can be found in the Mega folder linked in the OP): http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
And as option 3 it's inside the B18toB20 OTA file floating somewhere around here
Alright I tried this and something went wrong.
First thing I did was copy all the files where they needed to be. Then I booted into fastboot and did a "fastboot oem lock".
Then my device would do nothing. I would boot up to the ZTE logo then go black a second later. I tried to force into recovery by selecting recovery in fastboot but same thing, ZTE logo then blackness.
I got it back by getting into fastboot and performing a "fastboot oem unlock" again. All it did was wipe data.
What did I do wrong? I thought I am supposed to lock bootloader first before I restore system and flash recover and boot????
runderekrun said:
Alright I tried this and something went wrong.
First thing I did was copy all the files where they needed to be. Then I booted into fastboot and did a "fastboot oem lock".
Then my device would do nothing. I would boot up to the ZTE logo then go black a second later. I tried to force into recovery by selecting recovery in fastboot but same thing, ZTE logo then blackness.
I got it back by getting into fastboot and performing a "fastboot oem unlock" again. All it did was wipe data.
What did I do wrong? I thought I am supposed to lock bootloader first before I restore system and flash recover and boot????
Click to expand...
Click to collapse
Ok so if you modified boot, system or recovery in anyway then after BL lock it will not boot since it will fail secure boot, so you need to load the signed TWRP from tenfar's thread via EDL after locking. That will let you run TWRP with locked BL. Although ig you just want stock for upcoming OTA, then you might be good staying unlocked. If for return, then you should lock it
peramikic said:
Ok so if you modified boot, system or recovery in anyway then after BL lock it will not boot since it will fail secure boot, so you need to load the signed TWRP from tenfar's thread via EDL after locking. That will let you run TWRP with locked BL. Although ig you just want stock for upcoming OTA, then you might be good staying unlocked. If for return, then you should lock it
Click to expand...
Click to collapse
I apologize if I am fundamentaly not understanding this but wouldn't it be easier to flash system, boot, recovery, and fastboot back to stock via my current twrp THEN relock bootloader?
runderekrun said:
I apologize if I am fundamentaly not understanding this but wouldn't it be easier to flash system, boot, recovery, and fastboot back to stock via my current twrp THEN relock bootloader?
Click to expand...
Click to collapse
Yeah, now that we know fastboot will work even on stock boot that will work as well. The only thing you won't be able to do is flash back the B20 fastboot image that way, but enough to pass OTA most likely. The long way you can revert the fastboot image as well. I only wanted to post the image to begin with, but then wrote out instruction as they rolled around in my head. This will change soon anyways so a proper write-up will happen, just not by me, Documentation was never my forte
My BL is unlocked from ZTE right now, If I want to get CM for future but also want upcoming update from ZTE? What are the exact steps that I need to follow to get future OTA but also keep the BL unlocked for future CM? Please help as I'm confused with all these instructions.
peramikic said:
THIS APPLIES ONLY TO THE A2017U VARIANT, DO NOT USE THIS FILE ON OTHER VERSIONS
Disclaimer - don't blame me if something goes wrong
As title says, this is a full stock unmodified B20 TWRP system image. It kan be used in addition to stock boot and recovery images to restore the US A7 to conditions which will be like stock and allow to flash upcoming OTA. This was tested by @jkuczera here http://forum.xda-developers.com/showthread.php?t=3459107
Link to system image
https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy
If you are BL unlocked, you will need to lock it before flashing old recovery and boot (this may not be necessary to get MR2 to flash, depending on what it checks, but the phone might not boot, unknown). This will make your phone verify boot, recovery and /system again, so flash TWRP from tenfar's thread to be able boot after relocking since his is signed
To restore, unzip the file above to TWRP folder on the SD Card, then in TWRP under mount points unmount /system and put check mark on mount system as read-only. The read-only part is important so that TWRP does not modify the /system apon exit. You can then restore boot, recovery and system image.
Another partition, fastboot, was altered if you applied B20_boot, but so far no OTA has check it so it should be fine as is. Chance is it will be just overwritten by next OTA, but in case that changes, info will be added. This step is more risky since it involves using dd command and has to be applied carefully.
EDIT: looks like @Unjustified Dev posted new build that will flash fastboot image http://forum.xda-developers.com/showpost.php?p=68677272&postcount=133
You should then boot to stock recovery and factory wipe
In case you did not dump your boot and recovery, they can be found in @rczrider's post here
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Thanks to @swehes for providing the space on his cloud for this file, @rczrider for rest of the files and @jkuczera for trying this all out
Click to expand...
Click to collapse
Can someone please explain exactly how to do this. I have an unofficial twrp on my phone and the bootloader is unlocked but after i tried to flash super su it got stuck on bootloop so I wiped every thing and I also accidentally wiped my os too. So now I don't have an os and I want to go back to stock. Can someone please explain step by step on how to fix this? I just got the phone.
seby1234 said:
Can someone please explain exactly how to do this. I have an unofficial twrp on my phone and the bootloader is unlocked but after i tried to flash super su it got stuck on bootloop so I wiped every thing and I also accidentally wiped my os too. So now I don't have an os and I want to go back to stock. Can someone please explain step by step on how to fix this? I just got the phone.
Click to expand...
Click to collapse
All right I'm no expert either but I'll try to make this as straightforward as possible.
1) Format your SD card as exFAT. This is important as otherwise you will not be able to transfer the system image to your SD card since it is 6GB. To do this you can just plug it in to your PC, right click, Format and then select exFAT from the dropdown.
2) Download tenfar's tool for B20, rczrider's boot and recovery backup, and the system image backup from the link in the OP.
3) Create a new folder in /external_sd/TWRP/BACKUPS/serial_number/.Move the stock_boot_backup and stock_recovery backup into the folder.
4) Using a program such as 7zip, extract the 6GB system image file and move it to the same folder.
6) Go to into fastboot mode. Before you do anything you have to relock the bootloader otherwise the system will be modified and you want to be 100? stock. Execute 'fastboot oem lock'. You should then boot to a black screen.
7) Unzip tenfar's tool. Go to the unzipped folder, then hold down shift+right click and select 'Open command window here'. Execute 'axon7root.exe -p [COMPORT #] -r. To figure out your com port #, go to Device Manager, then go to down to where it says "Qualcomm Loader..." and your com port number is the number at the end. So for example if your com port number is 5, you should execute axon7root.exe -p 5 -r. Allow the program to do its thing.
5) Boot into TWRP. Do not swipe to allow modifications. Once in TWRP, go to "Install", "Install Image" at the bottom right hand corner, and then navigate to the stock_recovery_backup in the folder that you moved it to to. Select it and then choose the Recovery partition to flash it to. Do the same thing for stock_boot_backup.
6) Once you have flashed boot and recovery, go to the main menu, then "Restore" and then Restore the system image backup.
7) Go to wipe and then slide to factory reset. Finally, reboot system.
Hope that helps! If you have any questions, feel free to ask me.
rczrider's stock boot and recovery thread
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818/page7
tenfar's tool thread: http://forum.xda-developers.com/axo...xon-7-root-bootloader-unlokced-t3441204/page1
Has anyone who requested the bootloader unlock from ZTE (and mistakenly installed it) returned to stock and been able to get OTA's? I followed this guide and seemed to have returned to stock fine but the only OTA I can get now is the bootloader unlock OTA. I've downloaded and discarded it several times but that is the only one I can get. Anyone know of a way to bypass this OTA and get the new MR2 that was just released? I want to get OTA's until the custom roms start flowing.
Thanks!
shifuharris said:
Has anyone who requested the bootloader unlock from ZTE (and mistakenly installed it) returned to stock and been able to get OTA's? I followed this guide and seemed to have returned to stock fine but the only OTA I can get now is the bootloader unlock OTA. I've downloaded and discarded it several times but that is the only one I can get. Anyone know of a way to bypass this OTA and get the new MR2 that was just released? I want to get OTA's until the custom roms start flowing.
Thanks!
Click to expand...
Click to collapse
From what I can tell, once you apply for official bootloader unlock, your IMEI is placed on a list that will not get any future OTA updates set to it.
However, the OTA for B20 to B27 has been uploaded here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ
Try flashing that via stock recovery.
Quick question for anyone who might know.
The Link to system image which is : https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy has the following;
1. system_image.emmc.win
2. system_image.emmc.win.md5
Am I suppose to rename system_image.emmc.win to system_image.emmc.img and load?
it's not as clear that's why I ask but I ended up downloading rczrider system.img and reflashed via TWRP since I was a bit confused.
Thanks!
***************
I simply just went into TWRP backed up by boot so it would create a directory that contains the info I needed copied the system_image.emmc.win and system_image.emmc.win.md5 and restored.
xtermmin said:
From what I can tell, once you apply for official bootloader unlock, your IMEI is placed on a list that will not get any future OTA updates set to it.
However, the OTA for B20 to B27 has been uploaded here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ
Try flashing that via stock recovery.
Click to expand...
Click to collapse
I suspected as much. I downloaded the update and tried to flash it via the stock recovery using the update for ADB option but it fails saying that the package is not a ks package. Booooo. I really wanted this MR becasue they addressed the weak cell signal which I think contributes significantly to my battery drain. Not sure if there are any alternatives to get the update installed. Not very a happy about the ceased OTA's due to the bootloader unlock. Thinking the new Nexus (or whatever they are going to call them) is looking pretty good at the moment.
shifuharris said:
I suspected as much. I downloaded the update and tried to flash it via the stock recovery using the update for ADB option but it fails saying that the package is not a ks package. Booooo. I really wanted this MR becasue they addressed the weak cell signal which I think contributes significantly to my battery drain. Not sure if there are any alternatives to get the update installed. Not very a happy about the ceased OTA's due to the bootloader unlock. Thinking the new Nexus (or whatever they are going to call them) is looking pretty good at the moment.
Click to expand...
Click to collapse
Try the microSD card method instead.
First, make sure OEM Unlocking is checked in developer settings, rename the OTA to "update.zip", put on microSD, boot into stock recovery, and choose update from microSD.

Categories

Resources