I have read so much and information seems contradictory. One thing says if you root and take custom recovery you will never be able to update your phone via OTA. But I have been updating with fastboot so is updating like that still possible? And I understand you can get back to stock to take an OTA anyway. Is that correct?
It has been said that you cannot decrypt your N6 after taking 5.xx? (can't remember which) OTA. Is it not possible to decrypt with fastboot or adb after that particular update? If I just take all the OTA's before flashing twrp and rooting will I still be able to decrypt at the 5.1.1 version if I want to? And, there are custom kernels that allow things that the stock one won't allow. Currently using a 2013 Moto X rooted and twrp on 5.1. I've been updating by flashing stock recovery and system.img from sbf files and then taking the OTA successfully. Will the N6 still work that way?
Groid said:
I have read so much and information seems contradictory. One thing says if you root and take custom recovery you will never be able to update your phone via OTA. But I have been updating with fastboot so is updating like that still possible? And I understand you can get back to stock to take an OTA anyway. Is that correct?
It has been said that you cannot decrypt your N6 after taking 5.xx? (can't remember which) OTA. Is it not possible to decrypt with fastboot or adb after that particular update? If I just take all the OTA's before flashing twrp and rooting will I still be able to decrypt at the 5.1.1 version if I want to? And, there are custom kernels that allow things that the stock one won't allow. Currently using a 2013 Moto X rooted and twrp on 5.1. I've been updating by flashing stock recovery and system.img from sbf files and then taking the OTA successfully. Will the N6 still work that way?
Click to expand...
Click to collapse
OTA checks system and kernel and if anything is changed, OTA will fail. That includes root.
Fastboot flashing a system.img, boot.img and recovery.img would be enough to unroot and get back to stock however, you would only want to OTA if the rom you wanted didn't have a factory image.
Decryption is possible on all ROMs. It's just a custom kernel (boot.img) that doesn't force encryption on boot, then format userdata to get rid of existing encryption. Of course you're modified now so no OTA.
People care so pointlessly about OTA. Advice: forget about it and fastboot flash to update, or easier yet, wait for someone to package it up into a recovery flashable zip
Related
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.
Ok, here's the rundown - I have a VZW Moto X (XT1096). I previously ran mofo on it had flashed the 5.1 img files to it and so had 5.1 rooted, but with a locked bootloader. After learning that JCase had gotten sunshine to work on it I unlocked my boot loader. I then decided that because I was worried about having the a kind of mish-mash of systems on it, i.e., 5.0 bootloader (unlocked) with hacked and modded 5.1 system files flashed from mofo, that I wanted to start fresh. I then used the XT1096 flash to stock script and flashed back to 5.0 (there were a bunch of problems and bootloops and force closes, but I am happy to report I am now on a fully stock 5.0 with unlocked BL). Following being stock I have tried to take the OTA but have been unable to do so. When I try it OTA on my device it just sits at 0%. When I tried using MDM it gave me an error message that it failed to install the update - on the device it said getjar: unlocked.
So, now that I am on 5.0 with an unlocked bootloader I am not sure how to proceed with my priorities, Root, WiFi tethering and upgrading to 5.1. My questions are this:
(1) How can I upgrade to 5.1 or does my bootloader unlock preclude that?
(2) How best can I achieve root?
(3) Once I am rooted what do I need to do in order to enable wifi tethering?
Thank you so much!
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot and flash the stock system.img and recovery.img before doing the update.
3. I don't have experience with Verizon network. I use T-Mobile on this Verizon device and I just enable WiFi Hotspot. In the APN settings, in the "APN type" field, I add the value "dun". And set everything to IPv4.
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
eksasol said:
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
Click to expand...
Click to collapse
Thank you for the reply - got the update to take and have gotten the device rooted properly.
Now I just need to enable wifi tether - anyone know what is done in the Mofo images that allows it - can i do the same here?
I am interested in this question as well. I am in the exact same boat as the OP, except I am still on a Mofo 5.1 img that is giving me issues. I'd like to flash back to stock and take the OTA. But wifi tether will be a must.
Thanks to mikeoswego we have the tethering answer.
http://forum.xda-developers.com/showthread.php?p=62379151
eksasol said:
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
Click to expand...
Click to collapse
I tried this but after I flash TWRP I can't boot to recovery. If I choose recovery from the bootloader it just turns off the phone (charging icon). If I send it adb reboot recovery I get error android "No Command."
Flashed it multiple times, tried mfastboot, no luck. Any ideas?
Edit: I feel dumb. I was using power button to try to select, it's volume up. Good to go.
GatorsUF said:
Thanks to mikeoswego we have the tethering answer.
http://forum.xda-developers.com/showthread.php?p=62379151
Click to expand...
Click to collapse
The other method (the one I used) was to install the Xtether xposed module for the 2013 Moto X - worked perfectly for me.
I feel like a complete noob for asking this in regards to my XT1096, but, how would I get rid of the unlocked bootloader warning message?
SargeStryker said:
I feel like a complete noob for asking this in regards to my XT1096, but, how would I get rid of the unlocked bootloader warning message?
Click to expand...
Click to collapse
Flashing this
http://forum.xda-developers.com/showthread.php?t=2871478
juliospinoza said:
Flashing this
http://forum.xda-developers.com/showthread.php?t=2871478
Click to expand...
Click to collapse
Thanks!
I got an OTA update named OTA_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.35-7.18.531.2_release_450302.zip with size about 180MB.
Did anybody else get it?
I can't apply the update though because I have twrp and the phone is rooted. I was wondering if someone else got the update and applied it successfully on a rooted phone.
devsk said:
I got an OTA update named OTA_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.35-7.18.531.2_release_450302.zip with size about 180MB.
Did anybody else get it?
Click to expand...
Click to collapse
Should post this question here: http://forum.xda-developers.com/showthread.php?t=2305490
and the answer is probably yes since I don't see why T-mobile USA would push an ota update only to you
7.18.531.35 is the t-mobile US equivalent of 7.17.1540.35 which is the latest version with the stagefright 1.0 vulnerability fixed.
I can't apply the update though because I have twrp and the phone is rooted. I was wondering if someone else got the update and applied it successfully on a rooted phone.
Click to expand...
Click to collapse
You need to be on 100% stock rom including stock recovery to install ota updates. Better to return to stock using a ruu before applying the update imo since many users soft bricked their phones when attempting to install lollipop ota updates on stock rooted phones. If you need the RUU, look in the RUU collection thread, there is a 7.18.531.2 RUU posted there (link in my signature). Don't forget that questions should be posted in the q&a section, not in general. :good:
Thanks for your help. I found the RUU for my version. So, since I need to go back to RUU flash, I will need to re-setup my phone from scratch again just for getting this OTA....sucks!!
I wish they would make it easier to update modified phones. Just overwrite my root changes to /system and destroy my recovery but keep my /data and /sdcard. I can recover from that much faster than doing RUU and set up from scratch!!
So, on m7, isn't there way to flash stock on /system and stock recovery through fastboot and then take the OTA? I have done that on at least Samsung and Moto phones in the past and it worked fine.
So, if I restore system and boot partitions from my backup to stock, can I sideload the OTA ZIP using TWRP?
I should have made a recovery.img from the original stock recovery partition. Do you know if I can find the stock recovery here somewhere?
devsk said:
I wish they would make it easier to update modified phones. Just overwrite my root changes to /system
Click to expand...
Click to collapse
It is, you'll loose root every time you do an ota update.
and destroy my recovery
Click to expand...
Click to collapse
The ota is flashed using the stock recovery, and the stock recovery is also updated in that process.
So, on m7, isn't there way to flash stock on /system and stock recovery through fastboot and then take the OTA? I have done that on at least Samsung and Moto phones in the past and it worked fine.
Click to expand...
Click to collapse
Yes, either using a RUU, or a combination of a stock rom/backup (/system partition) flashed using twrp and then flashing the stock recovery back.
So, if I restore system and boot partitions from my backup to stock, can I sideload the OTA ZIP using TWRP?
Click to expand...
Click to collapse
No, the updater-script will only work with stock recovery
I should have made a recovery.img from the original stock recovery partition.
Click to expand...
Click to collapse
You can't backup the stock recovery directly from the phone (actually yes you can but it requires s-off and its somewhat complicated.
Do you know if I can find the stock recovery here somewhere?
Click to expand...
Click to collapse
already uploaded here:
https://www.androidfilehost.com/?fid=23991606952604831
or you can extract it from the ota update.
It was possible to update a stock rom + rooted phone simply by flashing the stock recovery back in the past (on kitkat roms and eariler) but it looks like its not possible anymore on lollipop updates. So much ppl posted here with the same problem: "Phone is stuck at HTC splash screen after installing update on stock rooted phone". Example here and here
The biggest problem if the ota install fine but the phone is stuck at the booting screen (like in the link above) is that your firmware will be updated to 7.18.531.35 so you won't be able to use the 7.18.531.2 RUU anymore unless you achieve S-OFF or edit your MISC partition.
alray said:
It is, you'll loose root every time you do an ota update.
The ota is flashed using the stock recovery, and the stock recovery is also updated in that process.
Yes, either using a RUU, or a combination of a stock rom/backup (/system partition) flashed using twrp and then flashing the stock recovery back.
No, the updater-script will only work with stock recovery
You can't backup the stock recovery directly from the phone (actually yes you can but it requires s-off and its somewhat complicated.
already uploaded here:
https://www.androidfilehost.com/?fid=23991606952604831
or you can extract it from the ota update.
It was possible to update a stock rom + rooted phone simply by flashing the stock recovery back in the past (on kitkat roms and eariler) but it looks like its not possible anymore on lollipop updates. So much ppl posted here with the same problem: "Phone is stuck at HTC splash screen after installing update on stock rooted phone". Example here and here
The biggest problem if the ota install fine but the phone is stuck at the booting screen (like in the link above) is that your firmware will be updated to 7.18.531.35 so you won't be able to use the 7.18.531.2 RUU anymore unless you achieve S-OFF or edit your MISC partition.
Click to expand...
Click to collapse
Thanks for the great help! I can't thank you enough.
One question: if I do fail to apply the OTA zip after restoring boot, system and recovery to stock, I will still be able to get TWRP back on the recovery through fastboot and restore my full TWRP backup to get a working system back, right? Is there a gotcha in that route?
devsk said:
Thanks for the great help! I can't thank you enough.
One question: if I do fail to apply the OTA zip after restoring boot, system and recovery to stock, I will still be able to get TWRP back on the recovery through fastboot and restore my full TWRP backup to get a working system back, right? Is there a gotcha in that route?
Click to expand...
Click to collapse
yes, even if the ota installation fails, you''ll be able to access fastboot, flash back twrp and restore your twrp nandroid backup. :good:
alray said:
yes, even if the ota installation fails, you''ll be able to access fastboot, flash back twrp and restore your twrp nandroid backup. :good:
Click to expand...
Click to collapse
Awesome!! :good::good:
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.