Database Develop

[Q] OTA Update with custom recovery?

Hello! I received the 1.29.1540.16 update today. I have the Team Win's recovery flashed on my Dev Edition. When I try to update, TWRP starts and no update happens.
How should the OTA updates be addressed with custom recoveries?

Same here... I have a rooted Dev Edition with CWM Touch recovery. Got prompted to update to 1.29.1540.16 (currently on 1.29.1540.3). Tried to install a couple of times, but, it just reboots without installing the update.

mrcobain said:
Hello! I received the 1.29.1540.16 update today. I have the Team Win's recovery flashed on my Dev Edition. When I try to update, TWRP starts and no update happens.
How should the OTA updates be addressed with custom recoveries?
Click to expand...
Click to collapse
Flash stock recovery first.

MediocreFred said:
Same here... I have a rooted Dev Edition with CWM Touch recovery. Got prompted to update to 1.29.1540.16 (currently on 1.29.1540.3). Tried to install a couple of times, but, it just reboots without installing the update.
Click to expand...
Click to collapse
i think you have to install stock recovery and maybe relock bootloader

skinsfanbdh said:
i think you have to install stock recovery and maybe relock bootloader
Click to expand...
Click to collapse
%$($*&%(@%... I was too hasty. Rebooted to recovery, wiped cache and tried to flash the downloaded OTA update zip (named OTA_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16_R-1.29.1540.3_release_318620_signednimix5ealszkrygs.zip) which I found in the downloads folder.
It started the installation, and is now hung at the "Running bug-fix1 tool..." step.
Not sure how long I should wait before aborting it. Am concerned that aborting (forcing a reboot) will cause more damage.

MediocreFred said:
%$($*&%(@%... I was too hasty. Rebooted to recovery, wiped cache and tried to flash the downloaded OTA update zip (named OTA_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16_R-1.29.1540.3_release_318620_signednimix5ealszkrygs.zip) which I found in the downloads folder.
It started the installation, and is now hung at the "Running bug-fix1 tool..." step.
Not sure how long I should wait before aborting it. Am concerned that aborting (forcing a reboot) will cause more damage.
Click to expand...
Click to collapse
abort and restore you backup

Aborted... rebooted... looks OK. Still on 1.29.1540.3. Still prompted to update. So, basically, status quo.
Looked around for stock recovery - the only ones I find are the 401 (instead of 1540) - which, if I understand, is from the international version and NOT the Dev Edition. Can anybody please help me get the stock recovery for the Dev Edition. (My first nandroid backup was *after* installing CWM and rooting.)

MediocreFred said:
Aborted... rebooted... looks OK. Still on 1.29.1540.3. Still prompted to update. So, basically, status quo.
Looked around for stock recovery - the only ones I find are the 401 (instead of 1540) - which, if I understand, is from the international version and NOT the Dev Edition. Can anybody please help me get the stock recovery for the Dev Edition. (My first nandroid backup was *after* installing CWM and rooting.)
Click to expand...
Click to collapse
you may be able to get it to install if your on a stock rom but im not sure about it

Yeah, I have stock ROM. Looks like I have to do what this person has done here.
Has to wait until I get home this evening.

MediocreFred said:
Yeah, I have stock ROM. Looks like I have to do what this person has done here.
Has to wait until I get home this evening.
Click to expand...
Click to collapse
or just flash the ruu for your phone

But, doesn't flashing the RUU wipe apps/data? I'd like to do this in the least destructive way possible. If I can get away with just flashing original recovery, installing the OTA update and flashing CWM back, I'll be happy.

yes it will. if you can get away with that then go for it

I have cwm installed on my htc one and I couldn't ruu my one back to a stock image. It would freeze up during the flash image process in the beginning.

No harm in trying the 401 or 707 recoveries ... if OTA doesnt work, just hard reboot and flash another
AND REMEMBER - NO NEED TO RELOCK FOR OTA UPDATES !

Ok got this to work and here's how, it goes without saying that this was my experience and the steps I used and I by no means accept any responsibility for any of these steps functioning on any other device...
I was using TWRP 2.5 and was rooted but otherwise was still on the stock rom that my developer edition shipped with.
I went here and downloaded the stock recovery for .16.
I opened the rar file which included other bat files to push the recovery but I didn't use that. I went to the fastboot folder and pulled the recovery.img file and dropped it in my M7 all in one tool kit folder under data and recoveries.
I then plugged in the phone and opened the toolkit and flashed my own recovery and followed the directions in the toolkit. After reboot the device came up and wanted to load the update which I let it do.
It went through and loaded and the scroll bar went all the way to the end and stuck. I waiting ten minutes and when it didn't restart I held the power button for about 15 seconds (until buttons stopped flashing) and the device screen went blank and I let go of the power button.
At this point it went through a couple screens where it appeared to be loading the update. Scroll bar went to the end and the device restarted and did that again. On the third restart it did a full boot and was good.
I then went back to the toolkit and flashed the TWRP recovery and then after reboot I went into recovery and flashed supersu to get root back.
Not sure if this helps anyone but wanted to share my experience...
MG

[Q] need some serious help with return to stock

hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19

Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..

Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.

Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA

still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.

1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.

[Q] PLEASE POST full STOCK HTC ONE ROM exe for AT&T new kitkat Vers: 4.18.502.7

ISSUE RESOLVED: keeping post since active since I still need the rom exe. But boot looping fixed.
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!

more info
by the way, when it crashed i had installed the ota update and then restarted play around with it, then rebooted in bootloader and unlocked, reinstalled twrp and AndRev HD 51. I've noticed two problems there. The first is that the Xposed module's latest update totally defeats my internet wifi and especially crashes vpn sevice. prior versions did not and I could not down-install to prior version (is preinstalled in HD 51). The other problem is that in looking around for this boot loop probably, turns out that TWRP apparently doesn't get along well with the encryption. don't know why. this stuff may or may not be part of the problem, but at this point i have no OS, an erased cache and can't even get into recovery (tried flashing twrp, older twrps and CWM. thanks.

You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device

randomOne1111 said:
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
Click to expand...
Click to collapse
This RUU does not exist yet, only the FOTA version - I've been in talks with HTC about this very thing. They do not have an ETA for the RUU, unfortunately.

SaHiLzZ said:
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
Click to expand...
Click to collapse
Hm. I did flash the firmware from an OTA. But couldn't actually boot into recovery after that. I can flash custom recoveries but can sideload without the intall stalling about a third of the way through (just hangs, no error messages). Then after that if I restart it loops. I can maybe fix the "tampered" warning and swap it out somewhere. I think it's the encryption while using twrp maybe resulted in some hiccup. But I thought the firmware flash would fix that. And I'm not sure how you can actually tell whether the flashed firmware is successful. (it says it is in the command prompt, but the phone doesn't really do anything all that different and i already updated with the OTA so the numbers won't change).
Looking at the board today and reading through the posts I see many people reporting basically being in the same boot loop boat after the OTA update, though with diff versions maybe there's some FW problem. weird so many posts of similar boot looping.
Thanks for responding.
This issue is temporarily resolved, was able to push ARHD in TWRP (would not sideload without erroring out during install, but was able to push zip to sdcard and then install from there) after much wiping using both twrp and cwm. Did notice when using CWM recovery would not install ARHD off sdcard push, and would flag unknown files .... android..security during wipes, so i am guessing that encrypting a custom ROM at least with TWRP as recovery was a bad idea. hopefully this will stay stable until the KK OEM RUU EXE is available. Thanks for the help.

[Closed] How to Return to Stock Recovery for OTA Updates

Hello all again. It's been almost year since last here, and clearly I have learnt nothing in the meanwhile.
First, specifications:
I have an HTC One M7 (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remains S-On.
Now, for the detailed inquiry:
I've been in the Stone Ages (see, Jelly Bean) for a while and have been planning on updating my phone for some time. However, the easy way, i.e. OTA, requires that I return to stock recovery. Now, as far as I know, this would require the use of an RUU (I'm not quite sure which one - perhaps "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe" from AndroidRUU?) which would require that I lock my bootloader (correct?) which would also happen to wipe my device. I was hoping that I might be able to flash the stock recovery image (which I have been unsuccessful thus far in finding on my friend Google, since I assume it was deleted from my phone when I flashed CWM?) without having to go through an RUU. Is such a thing feasible? Where would I find the appropriate stock recovery image file to do so? And is there a way, once I (hopefully) receive the OTA update, to copy that new stock recovery image to my PC before I switch back to custom recovery to avoid bothering all you fine folks about this again?
Thank you all for taking a look, and I appreciate any direction you may provide. (Seriously, though, I'm suspecting that the reason I haven't gotten an LTE signal the past couple months is because my radio is so outdated.)

You can install stock recovery using fastboot command.
However to apply OTA, if your phone is S-On, you must lock the bootloader.
You don't have to lock bootloader if your phone is Soff, for OTA, just stock recovery is good enough.

lyciansarpedon said:
Hello all again. It's been almost year since last here, and clearly I have learnt nothing in the meanwhile.
First, specifications:
I have an HTC One M7 (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remains S-On.
Now, for the detailed inquiry:
I've been in the Stone Ages (see, Jelly Bean) for a while and have been planning on updating my phone for some time. However, the easy way, i.e. OTA, requires that I return to stock recovery. Now, as far as I know, this would require the use of an RUU (I'm not quite sure which one - perhaps "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe" from AndroidRUU?) which would require that I lock my bootloader (correct?) which would also happen to wipe my device. I was hoping that I might be able to flash the stock recovery image (which I have been unsuccessful thus far in finding on my friend Google, since I assume it was deleted from my phone when I flashed CWM?) without having to go through an RUU. Is such a thing feasible? Where would I find the appropriate stock recovery image file to do so? And is there a way, once I (hopefully) receive the OTA update, to copy that new stock recovery image to my PC before I switch back to custom recovery to avoid bothering all you fine folks about this again?
Thank you all for taking a look, and I appreciate any direction you may provide. (Seriously, though, I'm suspecting that the reason I haven't gotten an LTE signal the past couple months is because my radio is so outdated.)
Click to expand...
Click to collapse
Just flashing the stock recovery will probably not allow you to successfully install OTAs. You have to have stock rom, stock recovery and possibly some /preload/ files that were deleted when you unlocked your bootloader. The quickest way to stock for OTA would be to flash a RUU. I would propose this route:
Option A
Lock your bootloader
Flash RUU 3.17.502.3
Receive OTA updates if they are still available
Option B
Lock your bootloader
Flash in bootloader: firmware 4.18.502.7
Flash RUU 4.18.502.7
Flash in bootloader: firmware 5.12.502.2
Flash TWRP 2.6.3.3
Download Guru Reset 5.12.502.2 and place on your sdcard
Boot into TWRP and install GURU Reset
For complete stock Say no to installing Root when exiting TWRP and Flash the Stock Recovery

Thanks for the feedback. I was a bit surprised to find out about needing to re-lock the bootloader even with stock recovery since a bunch of other places I looked said that I could use an unlocked bootloader as long as everything else was stock (just couldn't find a way to return to stock recovery without an RUU - which would require re-locking the bootloader - at the time). Used this (http://forum.xda-developers.com/showthread.php?t=2545227) from Majmoz's signature and got the relevant recovery.img from it. Since I had it, I figured I might as well try it before going through the process of re-locking the bootloader since being bounced out of the OTA and then going through the full process of relock-RUU-OTA anyhow was the worst that could happen. Turns out it worked.
So, for posterity's sake in case anyone else should come across a similar issue, everything I did (most of it probably unnecessary, but who knows):
-Made CWM backup (in case I happened to need to re-lock the bootloader which would wipe the device data to factory)
-Pulled that backup to my PC in case flashing to stock recovery wiped it (adb pull [backup directory, e.g. /mnt/shell/emulated/clockworkmod/backup/[folder]])
-Went into recovery from the bootloader, fastboot, plugged in the usb, and flashed the stock recovery (fastboot flash recovery [the downloaded stock recovery .img file in the platform-tools directory])
-Went back to the bootloader menu and entered the stock recovery and rebooted the device from there (I recall having to do that when I flashed CWM for the recovery to "stick", not sure if it was necessary here)
-Went into AT&T Software Update, let it download off the Wi-Fi, and let it apply. Did its thing with the image of the green downward arrow within the circulating arrows followed by reboot a few times, the "Android Update" screen where it runs through your applications, and voila, I am now on 4.4.2.
Updates:
-Have downloaded the updated stock recovery image.
-Flashed CWM Recovery back onto device
-Re-rooted via CWM (confirmed root)
-Made a new backup through CWM.
Now, if only I could figure out what the issue with the LTE signal is since I've never fiddled with that - guess I can heckle AT&T tech support for that.

lyciansarpedon said:
-Pulled that backup to my PC in case flashing to stock recovery wiped it (adb pull [backup directory, e.g. /mnt/shell/emulated/clockworkmod/backup/[folder]])
Click to expand...
Click to collapse
Flashing a recovery will not wipe anything but its a good call to backup on your computer :good:
-Went back to the bootloader menu and entered the stock recovery and rebooted the device from there (I recall having to do that when I flashed CWM for the recovery to "stick", not sure if it was necessary here)
Click to expand...
Click to collapse
no but again its a good practice to check if the recovery is working correctly.
Now, if only I could figure out what the issue with the LTE signal is since I've never fiddled with that - guess I can heckle AT&T tech support for that.
Click to expand...
Click to collapse
Have you checked you preferred network setting (GSM/CMDA/LTE AUTO)?
Is your apn correctly configured?

alray said:
Flashing a recovery will not wipe anything but its a good call to backup on your computer :good:
Click to expand...
Click to collapse
Good to know: the backup directory actually showed as empty while I still had stock, and then each backup's folder reappeared when I put CWM back on - was patting myself on the back for a few minutes there.
alray said:
Have you checked you preferred network setting (GSM/CMDA/LTE AUTO)?
Click to expand...
Click to collapse
It worked! Used *#*#4636#*# to pull that up (didn't know one could do that!) and, sure enough, it was on "WCDMA Preferred" for some reason. Switched it back to "GSM/CDMA/LTE AUTO" and my long-lost signal has returned.
Thanks a ton!

lyciansarpedon said:
Good to know: the backup directory actually showed as empty while I still had stock, and then each backup's folder reappeared when I put CWM back on - was patting myself on the back for a few minutes there.
It worked! Used *#*#4636#*# to pull that up (didn't know one could do that!) and, sure enough, it was on "WCDMA Preferred" for some reason. Switched it back to "GSM/CDMA/LTE AUTO" and my long-lost signal has returned.
Thanks a ton!
Click to expand...
Click to collapse
youre welcome glad it worked!

did anyone get a security update on their m7 this morning?

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: