I rooted my Nexus One with the 1-click androot and today I've received the 2.2.1 update (FRG83) OTA. I don't want to install it because it'll unroot, but the notification is really persistent and irritating, and I'm afraid I'm going to accidentally hit the install button.
How can I make it go away?
Install a custom recovery, make sure it works, try to flash the rom, it will fail because it needs to stock recovery to install, delete the update from /cache/.
That will at least leave you with a little time before it tries to notify you again. Best thing to do is load a rooted custom rom with a build.prop mod to make it think it's a version better/same so it won't try and update you.
I thought I had to have an unlocked bootloader in order to install a custom recovery or flash custom roms. Is this not the case?
I also have rooted with the one click but have clockworkmod recovery with stock rom. I just received the update ota and I am confused as to what would happen if I attempt to install it. Will it just abort or will it brick the device? Would just a battery pull and reboot be all thats necessary? Has any new roots come out for this update? I really dont want to lose my root. Any and all help is appreciated.
tenbeau said:
I also have rooted with the one click but have clockworkmod recovery with stock rom. I just received the update ota and I am confused as to what would happen if I attempt to install it. Will it just abort or will it brick the device? Would just a battery pull and reboot be all thats necessary? Has any new roots come out for this update? I really dont want to lose my root. Any and all help is appreciated.
Click to expand...
Click to collapse
I was in the same boat as you yesterday. I didn't think of the recovery so I hit update because I was tired of the notification. The phone applied the update successfully and I don't have root anymore. I have no idea how that impacts the recovery since ClockworkMod says the ClockworkMod recovery is installed.
Would like to know as well. Do not want to lose one-click root and would love to get rid of that stupid notification.
check out post #102 here:
http://forum.xda-developers.com/showthread.php?t=791124&page=11
this user says he has gotten it to stop via this method. I cannot verify yet as I have not received the OTA
For me that seems to have stopped the OTA nagg screen.
Using quickboot to reboot then clearing the notification, I have not got another OTA nagg screen. I like the 1 click root, turn on when needed off when not.
tinymiata said:
For me that seems to have stopped the OTA nagg screen.
Using quickboot to reboot then clearing the notification, I have not got another OTA nagg screen. I like the 1 click root, turn on when needed off when not.
Click to expand...
Click to collapse
I'm willing to try anything after 100+ "install later" replies Quickboot here I come
Thank you! I don't know why Quick Boot worked, but it seems that it has. It's now been a couple of hours without a notification message when they were coming back every few minutes. Thanks!
wouldn't it be cool if we got around Google's grand plan to force us to update by driving us crazy!?
Related
I figured, I would get the best response here... If you ROOT an Android phone, will downloading OTA updates through your phone brick it? I read an article about the new OTA for the EVO and it will brick rooted devices.
Misinformation. It would brick it if you applied it twice in sequence, not if you were rooted. You need the stock recovery to apply updates anyway, if you do get one it will not harm the phone because it can't be applied.
In the thread when the final OTA was coming out, lots of people that were rooted, said they installed it, it worked fine, but they lost root. So then they have to obtain root again.
So, I'd assume it would work fine if everything else was stock... you just might loose root.
So your saying, that if I were to install an OTA update through a rooted Android device running stock firmware, it would go through successfully without bricking it. But, if I ran the update a second time it would brick it. Correct?
If you're on a rooted stock rom, assuming you haven't flashed a custom recovery, the phone's recovery utility will not allow you to flash an OTA update because of a signature mismatch. I'm not sure what happened with the evo, but I don't believe it can happen with the nexus.
Okay, thanks? But I would still like some more input on this situation.
Pay attention
PurpleLlamaLover said:
Okay, thanks? But I would still like some more input on this situation.
Click to expand...
Click to collapse
If your not rooted you can still flash OTA update leaks, there are plenty out there. If you want custom roms then you have to root. The stock recovery only flashes stock updates, not rooted updates. If your not getting it by reading the forums, then I suggest you stay on stock, and wait for OTA update.
efishta said:
If you're on a rooted stock rom, assuming you haven't flashed a custom recovery, the phone's recovery utility will not allow you to flash an OTA update because of a signature mismatch. I'm not sure what happened with the evo, but I don't believe it can happen with the nexus.
Click to expand...
Click to collapse
No, this only happens with this specific update with the EVO.
Alright, great! Thanks guys. So since I believe the nexus one already got the offical OTA, did any of you lose ROOT access?
You WILL loose root when you update from an OTA update.
I had a rooted FRF50 and went to the FRF83 update and lost root/custom recovery, everything else was fine though.
I ask that you all forgiveth the newb nature of my question in advance, but if my phone has been rooted, and is currently running FRF50, is there anything I can do to the phone to have it automatically update using OTA? I ask because I received the notice for the OTA update the other day, but being rooted, got a signature mismatch error. (The only reason my phone is rooted is bc I bought it used that way-I wish I could've had it bone stock instead!) I know I can somehow do a manual update, but I'm trying to figure out for further future OTA updates if there's a way that I can have my phone simply automatically apply them.
Well, first off, thanks for hijacking.... AND, I have been doing a bunch of research. You should find the official build of froyo (FRF85B correct?) and manually update it. Just use it unrooted and it'll be easier when an OTA update comes along
I'm running decrap 1.1...My phone automatically attempts to install the vzw update every day, usually around 5 AM. With CWM installed, it seems that when the phone reboots after the install, it prevents the upgrade from actually being put in place. In theory this is a good thing and prevents unwanted downloads. The problem is that it is preventing my alarm from working and I wake up every day with my phone in CWM recovery mode. Plus I was late to work today. So, I would actually like to try the vzw update and replace it with the revolt rom if I don't like it. Does anyone know where the VZW update gets stored so that I can flash it out of cwm? Any thoughts on this would be appreciated.
You will need to flash back to stock and remove root to have the update install, and then if you change your mind, you will need to downgrade to the old software before being able to root again.
Nooben said:
I'm running decrap 1.1...My phone automatically attempts to install the vzw update every day, usually around 5 AM. With CWM installed, it seems that when the phone reboots after the install, it prevents the upgrade from actually being put in place. In theory this is a good thing and prevents unwanted downloads. The problem is that it is preventing my alarm from working and I wake up every day with my phone in CWM recovery mode. Plus I was late to work today. So, I would actually like to try the vzw update and replace it with the revolt rom if I don't like it. Does anyone know where the VZW update gets stored so that I can flash it out of cwm? Any thoughts on this would be appreciated.
Click to expand...
Click to collapse
Do NOT install the update if you want root and Revolt. Just flash Revolt or Home-Less as instructed in their threads, and you will be good to go!!!
Have the VZW G2 rooted on the previous OTA update, now starting to see the nag screen to update again.
Last time, I reverted to stock and had to set up everything again from scratch. I needed root so did that but now at the same point again.
Is there an easier way to update, without having to wipe everything and start over again?
TIA
I was rooted and just installed the update. Went through fine and kept root. All my had to do was install/update xposed framework and reboot to get my modules working again. Aside from xposed I had no modified system files and stock recovery. I had not uninstalled any pre-installed apps, just have a few frozen with titanium.
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
wujuyamakin said:
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
Click to expand...
Click to collapse
If you find a solution would you kind enough to share? Ive been delaying my install and when i finally decided to do it, it errors.
wujuyamakin said:
Have the VZW G2 rooted on the previous OTA update, now starting to see the nag screen to update again.
Last time, I reverted to stock and had to set up everything again from scratch. I needed root so did that but now at the same point again.
Is there an easier way to update, without having to wipe everything and start over again?
TIA
Click to expand...
Click to collapse
Other than root, are you stock? If so, should be able to take ota with non issue. If you modded wifi hotspot, need to change it back for ota. Did you also install custom recovery?
wujuyamakin said:
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
Click to expand...
Click to collapse
I didn't have any errors but I have no system files modded.
Thanks mhirsh, you nailed it. I had to restore the stock wifi hotspot app, do OTA update, then do the steps for wifi hotspot again.
It's actually the only root feature I've used for quite a while now. The root uninstallers I've tried have all failed to remove bloatware. I'll be looking at other root benefits to get more use out of it.
And to think I spent days restoring my phone from scratch last update ... lol.
wujuyamakin said:
Thanks mhirsh, you nailed it. I had to restore the stock wifi hotspot app, do OTA update, then do the steps for wifi hotspot again.
It's actually the only root feature I've used for quite a while now. The root uninstallers I've tried have all failed to remove bloatware. I'll be looking at other root benefits to get more use out of it.
And to think I spent days restoring my phone from scratch last update ... lol.
Click to expand...
Click to collapse
I tired this with no success. So i didnt delete my stock wifi hotspots (apk and odex) just renamed them. I removed my modded one and switched back to original names, rebooted, downloaded ota and it errored when it tried to install. Am i missing a step? Thanks in advance
lg g2 Verizon ota update with twrp
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
wrayzor71 said:
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
Click to expand...
Click to collapse
I couldn't get the OTA update to work until I went back to stock and unrooted. I was rooted with stock except I had performed the audio mod and the tethering mod which modified system files. Once I unrooted and factory reset to stock everything updated fine. haven't rooted again yet kind of waiting for stock lollipop OTA update to show up soon.
wrayzor71 said:
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
Click to expand...
Click to collapse
TheJuicer said:
I couldn't get the OTA update to work until I went back to stock and unrooted. I was rooted with stock except I had performed the audio mod and the tethering mod which modified system files. Once I unrooted and factory reset to stock everything updated fine. haven't rooted again yet kind of waiting for stock lollipop OTA update to show up soon.
Click to expand...
Click to collapse
You should never attempt OTA unless you are stock (having only root will be ok).
Yeah i had forgotten i had performed those mods after i rooted. Initially i thought i was just stock and rooted. Thankfully pretty easy to go back to stock.
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
aeb401 said:
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
Click to expand...
Click to collapse
Try using your favorite applications manager for root and freeze MotorolaOTA. This will prevent the update from being downloaded and you won't get messages about installing the OTA update.