Related
I have vzw dev ed, rooted with twrp recovery, stock everything else, I want to take the OTA and know i cant as is, i plan on using moto x toolkit to flash back to stock, here are my questions, once im back to stock and take the OTA, will i still be rooted, if not can i re root 4.4.2, do they have twrp custom recovery for 4.4.2, or should i just freeze the update and leave my phone as is?
jaysdroid2 said:
I have vzw dev ed, rooted with twrp recovery, stock everything else, I want to take the OTA and know i cant as is, i plan on using moto x toolkit to flash back to stock, here are my questions, once im back to stock and take the OTA, will i still be rooted, if not can i re root 4.4.2, do they have twrp custom recovery for 4.4.2, or should i just freeze the update and leave my phone as is?
Click to expand...
Click to collapse
you have a unlocked bootloader so you can root any version of android just grab the SBF file for 4.4 and flash it with RSD Lite and then take the OTA update
after the update reflash your custom recovery via the command promote command then install the SuperSU flashable zip in your recovery and enjoy your rooted 4.4.2
dray_jr said:
you have a unlocked bootloader so you can root any version of android just grab the SBF file for 4.4 and flash it with RSD Lite and then take the OTA update
after the update reflash your custom recovery via the command promote command then install the SuperSU flashable zip in your recovery and enjoy your rooted 4.4.2
Click to expand...
Click to collapse
awesome, thank you, so the twrp version i used while on 4.4 will work with 4.4.2, there is not a different version for the new OS? basically once i revert back to stock and accept the OTA i just do exactly what i did the first time with the same files and i'll be where i was prior?
Yes, you can use the same TWRP version on 4.4.2, and you reinstall it the same way. However, you don't need to use RSD lite to flash an entire SBF file in order to return to stock to accept the update - you can, but it will wipe all of your apps and settings. You can fastboot the stock recovery.img and system.img to return to stock, accept the OTA, re-flash TWRP, reboot directly into TWRP, let TWRP install SU, and you're good to go.
Sent from my XT1060 Dev Edition
Interesting, where would i find just those two img. files and how would i go about flashing just those two files, sorry if i need it dumbed down, fist moto phone and first time having to use a cmd prompt screen to do anyhting, had a galaxy nexus prior and everyhting was completely.....different/simpler.
pkomarnicki said:
Yes, you can use the same TWRP version on 4.4.2, and you reinstall it the same way. However, you don't need to use RSD lite to flash an entire SBF file in order to return to stock to accept the update - you can, but it will wipe all of your apps and settings. You can fastboot the stock recovery.img and system.img to return to stock, accept the OTA, re-flash TWRP, reboot directly into TWRP, let TWRP install SU, and you're good to go.
Sent from my XT1060 Dev Edition
Click to expand...
Click to collapse
this is tru but i rather just have them use the whole file instead of flashing just parts of it because there is less chance of messing there phone up.
so it is your call either way you have to download the SBF file. then you can either flash the whole file via RSD Lite or you can unzip the recover or system images and flash them via CMD and fastboot and mfastboot.
you can find the SBF files at the link below just make sure you download the correct file for your phone
http://sbf.droid-developers.org/phone.php?device=0
here is a link to my guide should give you all the info you need to get back to stock to take the OTA
http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358
Thank you all for the input, im prolly just going to revert completely to stock, i have no problem letting my apps re download and its less of a chance i fubar something, although if i do rest assured my next post will be how to un-fubar my phone
pkomarnicki said:
Yes, you can use the same TWRP version on 4.4.2, and you reinstall it the same way. However, you don't need to use RSD lite to flash an entire SBF file in order to return to stock to accept the update - you can, but it will wipe all of your apps and settings. You can fastboot the stock recovery.img and system.img to return to stock, accept the OTA, re-flash TWRP, reboot directly into TWRP, let TWRP install SU, and you're good to go.
Sent from my XT1060 Dev Edition
Click to expand...
Click to collapse
This. No reason to flash back to completely stock.
jaysdroid2 said:
Interesting, where would i find just those two img. files and how would i go about flashing just those two files, sorry if i need it dumbed down, fist moto phone and first time having to use a cmd prompt screen to do anyhting, had a galaxy nexus prior and everyhting was completely.....different/simpler.
Click to expand...
Click to collapse
The 2 files can be found inside the sbf file.
To flash them:
fastboot flash recovery recovery.img
fastboot flash system system.img
jaysdroid2 said:
Thank you all for the input, im prolly just going to revert completely to stock, i have no problem letting my apps re download and its less of a chance i fubar something, although if i do rest assured my next post will be how to un-fubar my phone
Click to expand...
Click to collapse
Take this opportunity to learn something. If flashing back to stock isn't an issue for you, what's the worst that can happen? You own a dev edition, learn to take full advantage of it. It's not difficult at all..
And please, don't use a toolkit until you've learned the basics of fastboot and adb. If the toolkit fails, you'll end up having to learn it all anyways.
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
pairustwo said:
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
Click to expand...
Click to collapse
1. - You do not need to unfreeze apps. The apps are still there untouched in the file system, and in recovery the OS hasn't booted enough to know that the apps are "frozen". By the way, frozen apps are basically just tagged in the OS as not available....so with the OS not running (just recovery is), they aren't "frozen" in recovery.
2. - Yes, fastboot to flash stock recovery. Boot to bootloader mode, fastboot flash recovery recovery.img (you don't need mfastboot for recovery, though you can still use it.)
3. - Accept the OTA. Since yours is trying to install, you should be able to boot to bootloader, flash stock recovery and on reboot it will start the install of the OTA. When done and booted.....reflash TWRP if you like.
That would be the way to go, yes.
Flash stock recovery and try to upgrade. If you cannot, try to unfreeze all sys apps. That should do it. ?
OK. So maybe not such a huge PIA as I had thought. I will track down the recovery file and read the instructions for flashing.
Thanks
@pairustwo
Every time another OTA comes out, people who modify their phones ask the same question. I've written up a FAQ based on the past OTA's.. -> http://mark.cdmaforums.com/MotoX-OTA.html if you want to read it to get more info.
Part of the issues you are talking about when taking an OTA is that the OTAs want to patch and replace only SOME files on your phone, so it checks to make sure the update is for your phone and its android version by evaluating certain files on the phone, that they exist and that their check sums match what the update expects.
i.e. change/modify/delete files the OTA update checks before installing, and the OTA will refuse to install.
If it didn't do this, the wrong update could possibly flash to your phone, replacing files with incompatible versions and making a big mess.
So yeah, "getting back to stock" (or as close to it as you can) is always recommended before taking an OTA so the "check" doesn't fail and prevent the OTA from applying.
In the past, freezing apps with Ti Backup was enough of a modification to cause the OTA's to fail. So often it is still suggested to un-freeze those done with TiBackup.
The OTA zip file (as downloaded) will only flash from Stock Recovery. TWRP and CWM for example don't properly process and flash them, so if you try to install when stock recovery is NOT on your phone, you get stuck in a bootloop. Using mFastboot to flash stock recovery back on is fine for those with unlocked bootloaders. Locked Bootloader users, is another matter.
There is a way "side load" the OTA, IF you have stock recovery, your phone hasn't received the push from Moto or your Carrier yet, and the OTA Zip file has leaked. But it still requires you get back to stock, etc. just as if you were getting it OTA.
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
pairustwo said:
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
Click to expand...
Click to collapse
Answered here -> http://forum.xda-developers.com/moto-x/moto-x-qa/dead-android-red-exclamation-t2778189
and I made this -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
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.
It's been a while since I meddled with my phone and I fear some of the adb basics are failing me. I had rooted my XT1092 a while ago and changed the DPI via a build.prop edit. Now since my device was rooted, I could not update to the subsequent 5.0.2 and later 5.1 via an OTA. As the damned "Update device" message keeps popping up and annoying the bejeezus outta me, I decided to take the 5.0.2 update via a zip (which again failed, since it needed stock unrooted 5.0 (Status 7 error, if I remember correctly).
I managed to unroot my phone, but the edited build.prop still stops me from an OTA/zipped stock update. I'd rather not do a full wipe of my device to get back to stock 5.0 (LXE22.46-19). So my question is this: can I get back to complete stock unrooted 5.0 by merely flashing the system.img files via mfastboot? Or would that cause an issue? Or flash all the files from logo.bin to fsg.mbn and stop there without wiping data? Or any other suggestion to get to 5.1 on a once-rooted phone with an edited build.prop? TIA!
You can always flash the same version of Android without a data wipe. Just download a stock firmware for same or higher Android version, follow all steps for flashing in the flashfile.xml, just don't use the command fastboot erase userdata at last. And you must flash from system image, the OTA won't work.
Okay, I haven't been able to update since LMY48I. Back then I was on stock recovery. Re-locking bootloader and all but still was not able to take OTA (always came up with dead android guy with "Error"). I'll skip the (probably) irrelevant stuff since then and give you the current situation:
Currently unlocked, rooted, with custom recovery. Still on LMY48I. I can't take OTAs obviously, and have tried flashing OTA updates manually with no luck and have tried flashing the entire Marshmallow image and that will not work either (sideload or flashing from internal storage in recovery). Sideload comes up with Closed error (device DOES show up in device list and I can do other things). Flashing from within recovery just says "Failed".
Please help me get to Marshamallow!
Edit: On Project Fi by the way.
Edit 2: Also, I've tried the flash-all script.
Now it says the device is corrupted when I boot up. I can still access recovery. Any help walking me through getting all of the correct firmware and latest build on would be much appreciated.
Thank you.
Edit: Looks like i'm good. I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
altvisionx said:
......./I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
Click to expand...
Click to collapse
Flashall.bat stops; only m-bootloader and m-radio are flash. Google's fault. You did the right thing by extracting the images and fasbiot flash them.
You cannot sideload the full factory image or flash from storage. Only fastboot
And just to clarify, you can't take an OTA (sideloading or otherwise) if your phone is rooted, have a custom recovery or a custom kernel (or any other modification to the system). The state of the bootloader (locked or unlocked) does not affect the ability to take an OTA update.