I used PwnMyMoto to get root. Never flashed another recovery.
However, since pwnmymoto removes stock recovery...how can I flash it back so I can get OTA?
Thanks for your help.
Related
So I updated to all stock 4.3 GE but can't flash the needed superuser zip. Do I need to flash a custom recovery than root and after that flash stock recovery back? Is there any way to root with stock recovery directly?
Thanks.
pr0x2 said:
So I updated to all stock 4.3 GE but can't flash the needed superuser zip. Do I need to flash a custom recovery than root and after that flash stock recovery back? Is there any way to root with stock recovery directly?
Thanks.
Click to expand...
Click to collapse
Yes, you need custom recovery for root. No need to change recovery back until the next update is due at which time I believe you will have to unroot and go back to completely stock which can be done by running the RUU again.
pr0x2 said:
So I updated to all stock 4.3 GE but can't flash the needed superuser zip. Do I need to flash a custom recovery than root and after that flash stock recovery back? Is there any way to root with stock recovery directly?
Thanks.
Click to expand...
Click to collapse
I believe you would need to flash CWM or TWRP then flash the superuser.zip then flash back the stock recovery afterwards.
can someone post the superuser.zip?
http://bit.ly/13F784c
gunnyman said:
http://bit.ly/13F784c
Click to expand...
Click to collapse
thanks. confirmed latest TWRP working on 4.3 and flashed supersu. had to install an update from the play store. it was without drama.
hi, i have Rooted original rom,. unlocked with clockwork mod recovery.
tonight my phone got a OTA 20B,
i tried to install in but my phone is now only rebooting to recovery, is there a way to bypass?
makkie88 said:
hi, i have Rooted original rom,. unlocked with clockwork mod recovery.
tonight my phone got a OTA 20B,
i tried to install in but my phone is now only rebooting to recovery, is there a way to bypass?
Click to expand...
Click to collapse
How many different threads are we going to get from people asking this same question?
Don't accept an OTA update on a modified phone! If you want it then flash the original .kdz then OTA update then redo root and recovery.
I have a Dev edition on VZW with an unlocked bootloader, rooted, and CW recovery. Stock ROM, running Xposed.
What should I do so I don't get stuck in a bootloop again?
I've heard all I need to do is flash the stock recovery through ADB. Is this correct?
9kracing said:
I have a Dev edition on VZW with an unlocked bootloader, rooted, and CW recovery. Stock ROM, running Xposed.
What should I do so I don't get stuck in a bootloop again?
I've heard all I need to do is flash the stock recovery through ADB. Is this correct?
Click to expand...
Click to collapse
if the only thing you used root for was the xposed stuff, then uninstall all of that stuff, and flash the recovery and you should be good to go.
So, just to be clear we will lose root after the OTA right? Do we also need to do any other stuff like restoring hosts file changed by adblock for instance? Or just flashing stock recovery is fine?
Sent from my XT1060 using Tapatalk
tejaskary said:
So, just to be clear we will lose root after the OTA right? Do we also need to do any other stuff like restoring hosts file changed by adblock for instance? Or just flashing stock recovery is fine?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
if all you did was run rooted apps, then uninstalling those apps (assuming they uninstall correctly and clean up whatever mess they created) then just flashing stock is fine. If you want to be 100% sure, then flash system.img as well and you will most certainly be good to go.
I'm having trouble locating a stock recovery img.
And is it just fasboot flash recovery.img?
Edit: Nvm, found it.
Hi guys!
I've finally received 4.4.4 notification to update my German Moto x!!
I'd like to know one thing before I proceed.. If I update, will I have to root again the phone?
My phone has unlocked bootloader so there is no problem, but right now I'm on holiday and I don't have a pc to root it again..
Thanks a lot!
I have not upgrade to 4.4.4 yet.
I don't think you need to root again
Thanks!
I've read some other user just flashed the stock recovery, installed the ota and flashed back twrp recovery..
Others instead use fwz method
I think I'll wait until I'm home just to be sure I need my phone during the holidays!
daede86 said:
Thanks!
I've read some other user just flashed the stock recovery, installed the ota and flashed back twrp recovery..
Others instead use fwz method
I think I'll wait until I'm home just to be sure I need my phone during the holidays!
Click to expand...
Click to collapse
Hi, i was wondering the same thing. Is there a method for someone to create an update for rooted phones?
Also can you link me to the threads for flashing back to stock and what this fwz is?
thank you
Here you can find some info about FXZ (sorry for my typo)
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In the same thread you can find the stock recovery, a user posted it. Just search stock recovery in the thread and you'll find it!
I'm not the right person to help you in detail.
I'm not an expert user
In the meantime I froze motorola OTA app to hide the update notification..
Guys, before anyone gets in trouble....there is no FXZ for the german (or any asia/european) Moto X's yet.
The only one released is the Verizon one....so DON'T flash the verizon FXZ.
You need to flash stock recovery back, and if the phone STILL won't take the OTA, also use "mfastboot" to flash system.img from the 4.4.2 FXZ (which IS released for the european/asia models). Afterwards, the OTA should install without fail.
You WILL need to re-flash TWRP no matter which method you use. You will also need to re-root IF you flash the system.img from the 4.4.2 SBF in order to be able to accept the OTA (you only flash system.img from 4.4.2 if the OTA fails after you have flashed stock recovery - it normally means you have modified /system in some way, and restoring the full system.img fixes this issue).
Good Luck - Remember: Don't flash the Verizon 4.4.4 FXZ to your non-Verizon phone. Not a good idea...
If your phone doesn't vary from Stock but rooted, you can get away with flashing stock recovery back on there and taking the OTA. (OTA wont install via custom recovery like TWRP, CWM, etc). And if that is the case, you will retain root. You can optionally flash TWRP back on there.
If you have Xposed installed, it will need to be disabled or removed for the OTA install to work.
It is when you mess with stock files in /System or other folders on the phone.. i.e. remove, rename, etc. files from them, that you may also need to flash system.img and possibly other parts. This is due to verification checks in the OTA zip itself. If you have to flash those parts, you will have to re-root. Not an issue if you have an unlocked bootloader.
Thanks a lot for your help and clarification!!
I knew I wasn't the right person
Guys just to be sure of the right process..
-download the actual sbf of my phone
-extract recovery.img from the sbf
-remove xposed
-flash the recovery with flashify
-take the ota
-flash back twrp recovery
Am I right?!
Thanks a lot
daede86 said:
Guys just to be sure of the right process..
-download the actual sbf of my phone
-extract recovery.img from the sbf
-remove xposed
-flash the recovery with flashify
-take the ota
-flash back twrp recovery
Am I right?!
Thanks a lot
Click to expand...
Click to collapse
IF you do not vary too much from Stock (i.e. didn't remove, rename or replace any "stock" files on your phone), then yes.
Oh, for Xposed, there is a disabler ZIP you can flash from custom recovery located in /storage/emulated/0/Android/data/de.robv.android.xposed.installer (or /SdCard/Android/data/de.robv.android.xposed.installer ) instead of removing it, as sometimes removing it doesn't undo all the changes.
I have a moto x 2013 with an unlocked bootloader. I was on 4.4.2 and I decided to take the OTA. After flashing stock 4.4.2 and updating I flashed TWRP and my custom boot animation. It would no longer turn wifi on which I had solved in the past by reflashing stock. I stupidly tried to do this, and realize now that I have the 4.4.4 bootloader with 4.4.2 images. Is there anything I can do? Is there any way to flash 4.4.4?
Edit: I flashed TWRP and copied the ota to the sd card from a otg drive. I then flashed back the stock 4.4.2 recovery and used it to install the ota zip. I do not recommend others try this as I have no idea how safe it is. Avoid getting in this situation to begin with.
Now I need to know if I can try flashing TWRP again and what I did wrong with that last time? Or was it the boot logo/animation?
numanair said:
I have a moto x 2013 with an unlocked bootloader. I was on 4.4.2 and I decided to take the OTA. After flashing stock 4.4.2 and updating I flashed TWRP and my custom boot animation. It would no longer turn wifi on which I had solved in the past by reflashing stock. I stupidly tried to do this, and realize now that I have the 4.4.4 bootloader with 4.4.2 images. Is there anything I can do? Is there any way to flash 4.4.4?
Edit: I flashed TWRP and copied the ota to the sd card from a otg drive. I then flashed back the stock 4.4.2 recovery and used it to install the ota zip. I do not recommend others try this as I have no idea how safe it is. Avoid getting in this situation to begin with.
Now I need to know if I can try flashing TWRP again and what I did wrong with that last time? Or was it the boot logo/animation?
Click to expand...
Click to collapse
You're fine to flash TWRP. The issues was you re-flashed it before taking the update last time. To update to 4.4.4 you have to do a stock restore to 4.4.2 first then install the update.
coles427 said:
You're fine to flash TWRP. The issues was you re-flashed it before taking the update last time. To update to 4.4.4 you have to do a stock restore to 4.4.2 first then install the update.
Click to expand...
Click to collapse
I am almost certain that I flashed it after taking the update. The update won't flash with anything other than the stock recovery. It was probably user error of some sort when flashing.