So the official OTA Jellybean update has been out for awhile now, but I'm just now trying to get to the bottom of my issue. My issue being that my OTA update downloaded but didn't install. Please note that, 1. I am an amateur with roms and such, and 2. My phone is rooted.
I have opened the OTA zip file with the Rom Manager's Rom Pre-installation, but I am lost on what to do from there. I figure there is a way I can install this update on my phone manually.
One more thing, I have tried flashing a rom before, but there was an error and I had to restore to my stock rom.
Attachment is a screenshot of the Rom Pre-installation screen.
Sent from my HTC One X using xda app-developers app
I would suggest not using Rom Manager for anything. Flash it in recovery. Plus that looks like an old version.
Sent from my Evita
If you have custom recovery installed, OTA will fail. OTA is looking for stock recovery to perform the install. If it doesn't find it, it stops.
Unlocked bootloader may also cause OTA to fail, can't remember.
timmaaa said:
I would suggest not using Rom Manager for anything. Flash it in recovery. Plus that looks like an old version.
Sent from my Evita
Click to expand...
Click to collapse
As I said, previously, I have had issues with flashing roms. But according to Rom Manager, it says the zip I have is a "Rom addon". Should that give me a different result than flashing a rom?
redpoint73 said:
If you have custom recovery installed, OTA will fail. OTA is looking for stock recovery to perform the install. If it doesn't find it, it stops.
Unlocked bootloader may also cause OTA to fail, can't remember.
Click to expand...
Click to collapse
Well, that's the cause of the issue. I have TWRP installed, and I have an unlocked bootloader.
caskla said:
As I said, previously, I have had issues with flashing roms. But according to Rom Manager, it says the zip I have is a "Rom addon". Should that give me a different result than flashing a rom?
Click to expand...
Click to collapse
ROM Manager is for flashing custom ROMs, and in the case of the "addons" for custom mods packaged as flashable zips. I would not expect it to install official OTAs.
What "issues" have you had with flashing ROMs? If you are rooted and bootloader unlocked, I wouldn't typically recommend to install OTAs at all. Install a custom ROM or stock rooted (if you want a stock type ROM), otherwise, why did you unlock in the first place?
Also, if you are SuperCID (probably the case since you are rooted) and S-on, you are lucky the OTA didn't install. It would have bricked the phone. Same thing if you try to RUU. If you really want to return to stock, you either need to change back to the proper AT&T CID, or S-off, then run the RUU.
Related
I want to be sure my DS can receive and install the imminent (?) ota ICS from HTC. Still a bit of a noob so read a lot of stuff on here and other forums (mainly non DS) but haven't really found definitive answers for the 'half rooted' device i.e. bootloader unlocked via htcdev, cwm flashed, s-on.
Main concerns are:
losing root
ota will not install because of /system/app and framework mismatch (after a few UOT mods) - boot animation and sound have also been changed in /system/customise/resource, also bloatware removed
ota issues with cwm installed
Originally first thing I did immediately after flashing cwm was a nandroid backup so that's available to me, which really only leaves the cwm and ota compatability question.
Is Rootkeeper an option or should I root from scratch again after ota?
If I receive notification of the ota availability, then restore from original backup (and maybe relock bootloader with htcdev?) will I then have lost the chance to install the ota?
A lot of questions and ifs, I know, I just don't want to screw up the chance to try the official ICS before going for a custom rom. Thanks in advance.
Hboot 2.00.0002
Android 2.3.5
Sense 3.0
Stock rom/kernel/radio
Sorry, I'm pretty sure HTC Dev unlocked devices can't get OTA updates. I'm completely sure devices with CWM can't (you need stock HTC recovery). Since you already have a custom recovery, it would be better to get a custom ROM, much fastr and tweaked
As shrome99 said..
To get the OTA update you will need to have STOCK recovery, and a relocked bootloader to get the OTA.
__________________
This assumes you are 100% stock on the operating side.
foX2delta said:
As shrome99 said..
To get the OTA update you will need to have STOCK recovery, and a relocked bootloader to get the OTA.
__________________
This assumes you are 100% stock on the operating side.
Click to expand...
Click to collapse
I got OTA updates with both an unlocked bootloader and custom recovery. It's true the update won't install till you're back on stock recovery but the locked bootloader isn't necessary. I was however updating from Stock Sense 2.1
Warning: do not install it if you get a OTA message if rooted!
It will lead to the dreaded red triangle screen. Your best bet is to just install CWM/4EXT then when the new update comes, install the ICS prerooted ROM by Adidas.
Sent from my HTC Desire S using xda premium
The "dreaded" triangle screen is just the stock recovery.
Jack_R1 said:
The "dreaded" triangle screen is just the stock recovery.
Click to expand...
Click to collapse
That won't boot back to your ROM therefore you are stuck.
No root/s-off, therefore you can't do much about it. (Unless you get the RUU to run)
And for the average user, this is difficult for them to understand. Hence it has picked up its name as the 'dreaded triangle screen' over several different HTC device threads.
Sent from my HTC Desire S using xda premium
Cheers for the input.. did a bit more snooping and (if and when I get the ota shout).. I think I can go back with original nandroid to pre-root, before superuser went in. Then I'll give Android Recovery Manager (Sensation Android Development forum) a lash, just to see if I can flash back the stock recovery img.
If any nice ota comes my way which won't take then I'll try htcdev to relock the bootloader and give it another lash!
Think (hope) it'll work.. couldn't find a stock img anywhere yet so I'm hoping it's included in the above manager.. was going to try tonight but, typical, my connection went..
'Your best bet is to just install CWM/4EXT then when the new update comes, install the ICS prerooted ROM by Adidas.'
I have cwm, not sure why I would wait for the update then install a custom ics rom..
You must install stock recovery to install OTA update.OTA won't install, if you have custom recovery or S-off.But I recommend to install ROM, using zip or RUU.
From htcdev:
(after unlocking bootloader) Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable.
That answers the question re the bootloader but I'm struggling to find the stock recovery img to flash.
I suppose I can extract and then flash it, possibly from this: RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.exe, even though my device is 2.10.161.3 (161 is Vodafone). The radio is the same as mine which is irrelevant anyway, right?
I know it would be easier to install the RUU but after hours of research I would really like to be able to nail this so I have the option of reverting back to VF stock, as I still have 18 months warranty left.
Can anyone can confirm if I'm on the right track pls?
I suppose, if you haven't GoldCard or SuperCID recovery won't flash(signature verify failed).Download Zip/exe of your ROM , and flash that recovery.After that you might be able to install FOTA.No guarantee it will work.
scandron said:
I suppose, if you haven't GoldCard or SuperCID recovery won't flash(signature verify failed).Download Zip/exe of your ROM , and flash that recovery.After that you might be able to install FOTA.No guarantee it will work.
Click to expand...
Click to collapse
It will flash, because his bootloader is unlocked.
He won't need a goldcard cause he is flashing a voda RUU recover, future I don't think it will even come into play when using fastboot to flash it.
However I suggest EVERYONE who is a little unsure make a goldcard.
Thanks all, trying to get a gold card now just to be sure.. however just intend to extract and flash the recovery img from the ruu, once I can be sure I have the right one.. the stock recovery in HTC devices is generic, no?
i also have a doubt.
what i wanted to know is that will i still be able to update my device OTA if i have unlocked the bootloader, rooted my device but havent installed a custom recovery?my device is rooted nothing more than that. and after relocking my bootloader (i dont mind loosing root) will i be able to update OTA?
sorry for being irrelevant but i didnt want to start a new thread for a doubt of this magnitude.
See post #10
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
iwearthebelt said:
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
Click to expand...
Click to collapse
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
darkhawk3383 said:
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I did, had it unlocked and rooted. I guess there was some sort of issue with Rom Manager on the S3. I use it on my Galaxy Nexus and have no issues. I ended up abandoning what I was doing, uninstalling Rom Manager and going a different route. I have no prior experience with Odin but figured out how to install CWM . Downloaded I535vrblk1, flashed CWM, unlocked & rooted again. . Thanks anyway for the reply.
You can reinstall ROM Manager. It is something to do with some of the newer OTA's and the leaks. I have read a few posts in the forums about this in the GS3 and I really can't remember the fix but your recovery not sticking had nothing to do with ROM Manager. I think the fix was when you rebooted to recovery to flash a kernel right away, whether it be KT747, LK, or any of the other. Now that I typed this I'm about 99% sure that was the fix. Like I said above though, it has nothing to do.with ROM Manager, so if you're like me and find a lot of the tools in it handy you should be able to reinstall it. If you have a problem again just flash a kernel.
Sent from one of the many Anthropomorphic Personalities on the Disc
Hi,
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
Or, can I flash OTA update as update.zip in TWRP recovery?
sorry, for my bad english.
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
JohnKoeMan said:
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
Click to expand...
Click to collapse
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
Haha no problems friend!
I've found a link to a custom ROM using JB 4.1.1, you can look into that?
http://forum.xda-developers.com/showthread.php?t=1871866
Also you can instead remove TWRP (if you know how) and instead install CWM (clockworkmod).
I found CWM to work better than TWRP.
I myself am using CyanogenMod 10.1, very nice and clean, works perfectly ad has Android 4.2.1
That might also be an option if you want a clean ROM. ^^
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
orenfl said:
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
Click to expand...
Click to collapse
Since I'm facing the same problem, and there is no RUU for now, how and where to get a JB OTA nandroid... Haven't seen any around.
Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
tominozh said:
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
bo6o said:
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
Click to expand...
Click to collapse
Yes, you should be. Download zenrom, reboot recovery, wipe everything a few times, flash zenrom, set it up, then recovery, flash STOCK RECOVERY ( very important), prompt for update, download, install, set up, ( you may get a few errors here and there so just do factory reset in setting-->factory reset). Then flash twrp, flash superuser, backup.
Sent from my HTC One S using xda app-developers app
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
JustinBieber said:
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
Click to expand...
Click to collapse
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
robbham78 said:
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
Click to expand...
Click to collapse
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
charesa39 said:
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
Click to expand...
Click to collapse
Thanks guys, I didn't know everything had to be stock! plus I found out that xposed will also break the ota
There's an OTA help desk sticky thread in general that tells you everything you need to know
Sent from my Nexus 5 using Tapatalk
Hi all,
I apologize if this has been answered before, but I had trouble finding it here. I am currently rooted on a stock backup, but I am running a custom recovery. I am not sure where to find the stock recovery image for my device. I am using the HTC One M8 through Verizon, and I know that the new firmware update is coming out soon, and I'd like to be able to just OTA update my phone so that I can reflash a custom recovery and install the newest VenomROM. I have flashed a custom recovery before (obviously), but I didn't know if it mattered which firmware base you are running. I read somewhere that the recovery is totally separate from the OS, and it is meant to be an alternative to booting into the OS in case of a problem, but I want to be sure. If there is a specific recovery I need to use and someone here knows where I can find it, that'd be great. I found the collection of stock recoveries, but I'm having trouble figuring out which one I need to use. Any and all help is appreciated, thanks.
EDIT: My CID is VZW__001
My VERSION-MAIN is nothing. There's is just nothing next to this label.
I tried locating it on the collection of stock recoveries, but couldn't find it. I'm not sure why this is.
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
hgoldner said:
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Hi there,
I actually just used the psuedo RUU tool (I assume this is the one you are talking about? http://forum.xda-developers.com/showthread.php?t=2727831)
I just finished using this tool, but when I went to check the recovery, all I get is a big red triangle with an exclamation point in the middle. Nothing else. So, I'm guessing that recovery didn't flash properly? But I'm honestly not completely sure. I would screenshot it, but I can't do that. Any help is appreciated.
EDIT: I found out that pressing volume up and power gives more options. I assume I am all good to go now? I am still rooted, and I'm not sure if that is a problem. I am stock, s-off and rooted, but I don't have any mods installed.
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
hgoldner said:
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
ChuckFinley1992 said:
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
Click to expand...
Click to collapse
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
hgoldner said:
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
ChuckFinley1992 said:
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
Click to expand...
Click to collapse
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
hgoldner said:
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
Click to expand...
Click to collapse
Okay, I may look into that. I've only seen an RUU flashed via hboot, so I'd have to look into it. At the very least though, I'd imagine someone will post the instructions on how to flash the firmware when it comes out.
Thanks so much for your help!
hgoldner said:
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
+100 for this!
I am reading dozens of posts in all kinds of threads of people just dying to take that OTA...
Why???
I would not touch that new firmware with a 100 foot pole until the devs have figured out what it breaks!!!
I predict a flood of posts in the line of:
"I flashed back to stock to take the OTA and now weaksauce is not working - how do I get root back?"
What's the hurry?????