Is there a way to stop my Droid from updating OTA to FroYo? I have flashed my Droid over to Cricket and have Bugless Beast v0.4 installed, and now since the 2.2 OTA update has been released I get a constant notification that the update is available. The only options I get are to install now or to install later, but what if I don't want to install it all and just get rid of the pesky notification that keeps popping up every so often after I press install later. I already have 2.2 on my system with Bugless Beast so I'm not really missing out on anything. I don't want to update and have to reroot, reinstall Bugless Beast, and reflash my Droid to Cricket again. I'm happy where my system is at
If you have a custom recovery, then as soon as you reboot into the installation your phone thinks that you've accepted, but the custom recovery blocks the installation and you stay on BB.
What do you mean by reboot into installation?
I've booted into clockwork recovery and then restarted the phone, but nothing seemed to change. Is that what you meant to do?
Flash SPRecovery. Then select "install now". It will send a notification that it has been installed on your phone to the servers that send out the OTA but SPRecovery will block the installation of it onto your phone, thus stopping the notifications of an update and keeping you on BB v.04 w/ Cricket. You can flash back to CW Recovery if you want to afterwards.
Sent from my Droid using XDA App
Im also running BB.04 and got the OTA notification today. Glad I found this thread because I was starting to get worried. I clicked 'install now', rebooted and so far no notification and I am still on BB.04. Woot!
Thank you for this!
Running BB 0.4. I saw the verizon 2.2 Froyo upgrade this morning, and for a second I was psyched verizon finally pushed it out... then I was a little worried about what was going to happen to mine since it was rooted and running a 2.2 Rom I was already happy with. Just like this thread says, I clicked install, and the phone rebooted right back up to my BB 0.4 without any issues.
I'd hate to say I'm a leech, but you guys have so much information here, and I cannot stop reading lol. I commend everyone one of you Devs for all the work you do!
Thank you again,
-Dano
Yup, it worked perfectly! Thank you!
Interesting. I was able to block it the first time but it popped up again. Anyone know why? Maybe there is another update to the 2.2 OTA update?
I was having the same issue with the ota update until I came across this:
http://www.peteralfonso.com/2010/08/how-to-stop-ota-notifications-on.html#more
it says it is for Buggles rom but I am using a different rom and it worked just fine
I had received this notification about four times before it recognized that I'm updated without rebooting the phone for it to be blocked. Nothing else had to be done except for saying yes.
stephen730 said:
whatchoo mean able to block it? You mean you clicked install later? Or you let it run and it goes away?
If you let it run/fail it will just come back again a day later, a week later, next time you reboot, next time you come out of screen off, etc... Its done it to me and it sucks cause it won't go away number 1, and number 2, i hate to keep rebooting to fail and possibly missing calls/texts... especially when you first wake up and the message is there like a nagscreen or advert.
Click to expand...
Click to collapse
I clicked install now and my recovery image blocks the installation when rebooted. It shows the Android guy with the exclamtion point but it doesnt finish the install. Reboot then im back to the way I was. Im running BBv.4 btw. I havent got another prompt yet.
Related
Hey all,
I'm running a T-Mobile G1, rooted with JF's newest 1.5 firmware and running just fine. As of last night I started getting notified that my phone had downloaded the new security fix from Google and would like to install it. There is no "Don't install" option that I can find, just "Install Now", "Install Later...", or "More Info". I just have been going to the "More info" option and backing out from there which seems to delay it for a few hours, but it just keeps coming back. Does anyone know if it will be safe to allow it to install (I don't want to try for fear of losing my precious root)? If I can't let it install, does anyone at least know of a way to get it to stop bugging me about it?
Thanks,
Bob
I thought JF's builds blocked OTA Updates...apparently not JF's ROMS are old flash the cyanogen's cupcake! So many goodies inside
That's what I thought too. After telling it off enough times it seems to have given up, so that should fix it for now, just hope that it doesn't come back.
I haven't heard of anyone loosing root from any OTA updates...think about it, it's the same as flashing a new ROM.
It will never go away as long as there's an update though, only when you actually do update. Google is picky like that!
bregant2 said:
Hey all,
I'm running a T-Mobile G1, rooted with JF's newest 1.5 firmware and running just fine. As of last night I started getting notified that my phone had downloaded the new security fix from Google and would like to install it. There is no "Don't install" option that I can find, just "Install Now", "Install Later...", or "More Info". I just have been going to the "More info" option and backing out from there which seems to delay it for a few hours, but it just keeps coming back. Does anyone know if it will be safe to allow it to install (I don't want to try for fear of losing my precious root)? If I can't let it install, does anyone at least know of a way to get it to stop bugging me about it?
Thanks,
Bob
Click to expand...
Click to collapse
To keep the phone from checking for new updates try:
Go to Settings>Security, then scroll to the bottom, click firmware download and tick never. Should do the trick tho I don't know for sure as I haven't ever been prompted.
Then again, you shouldn't be getting OTA updates at all, haha.
lukekirstein said:
I haven't heard of anyone loosing root from any OTA updates...think about it, it's the same as flashing a new ROM.
It will never go away as long as there's an update though, only when you actually do update. Google is picky like that!
Click to expand...
Click to collapse
You lose root because the update replaces the boot image and other images which are the key thing that is needed for root access on your phone.
Hopefully you guys know there is a software fix out from at&t and samsung that fixes gps problems and etc...
goes without saying you can't just straight update if you're rooted. That's where i'm stuck.
Before i touched anything, it would get to 50% and reboot, says the update was not applied.
Then I tried "unrooting" even though it said it was unrooted, and apps requiring SU backed this up saying my phone was unrooted.
Then during the update, it stops even sooner at "preparing".
So... how do we get around this without doing the master clear with odin3???
I DON'T want to lose all my data. I'm too lazy.
Mine said failed at 100%. I def got the jh7 update though. My phone was unable to reboot into recovery using the three button method. Now I can. My phone was rooted with stock rom.
Mine is rooted with the Voodoo fix and it failed during the update (I was at work so don't know at what step during the update).
Will have to do the voodoo-lag unfix - restore back to factory defaults and try it again..
Unless of course someone pops out a tweaked ROM before then!
check out this thread, http://forum.xda-developers.com/showthread.php?t=789546 so we can get everyone with this issue together in one thread
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!?
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!!!
So I just got a notification from ATT saying that there is a software update available. Has anyone else gotten this and installed it? Is it jelly bean or a minor update? I haven't tried it myself because I am rooted.
Sent from my HTC PH39100 using xda app-developers app
Bigluc said:
So I just got a notification from ATT saying that there is a software update available. Has anyone else gotten this and installed it? Is it jelly bean or a minor update? I haven't tried it myself because I am rooted.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Yes just got it I'm Rooted & S-OFF
it won't be jelly bean since the ONE X series doesn't have it yet haha just a minor I bet
Can someone detail this update?
*Edit* Called AT&T the Update was released October 9th it an 13mb update so yea Minor the girl
on the phone was talking to fast for me to listen what it offers
Got it last night. Android version did not change. Couldn't tell for sure if any other numbers updated. It wouldn't kill AT&T to send out an e-mail or text message telling us what the update was for.
got the same thing i have no idea what is the update
Update has my phone stuck in a darn boot loop..any idea what it is?
Sorry bludiamond.
Since my phone is rooted, I did not want to install this update. It's quite upsetting that AT&T forces the update unconditionally.
Anyway, I had let the download to complete, but did not let it to install. The update did prompt me, whether I want it to install now, or later. I had opted for later.
Then, after some Googling, I had deleted the download (from /sdcard/Download), and had un-installed the following services: com.htc.demoflopackageinstaller and com.smithmicro.dm.
Then, I've rebooted the phone. Afterwards, the phone still had a notification, that there's an update ready to be installed. When, selecting the notification, updater did realize that the downloaded file is gone, and had prompted me whether or not I'd like to download the update again, on which, I had responded no. The notification is gone, and AT&T did not prompt me to download and install the update again, at least not yet.
My phone seems to be OK.
I was hoping for a new Radio/RIL. That's not what this is...
New Kernel & Recovery. If you are rooted and on a custom rom Do Not run the update. I'm sure the developer of the rom you are on will work to add anything useful to future updates.
The dates on these files is 7/27/12 so it took At$t over to months to test & release.
To delete it look in /cache/fota/OTAPkg.zip
Once gone you shouldn't be bothered by it anymore.
Have anyone successfuly downloaded and installed it?
What's new? Bluetooth bugs fixes? Usable Voice Dialer? Better battery life?
Sense 4.0?
Please comment.
Sent from my HTC PH39100 using xda app-developers app
gattech said:
Have anyone successfuly downloaded and installed it?
What's new? Bluetooth bugs fixes? Usable Voice Dialer? Better battery life?
Sense 4.0?
Please comment.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Think the majority of users on here are rooted and running custom roms so they wouldnt' be installing this.
I forgot I was unlocked and rooted. Now I am really stuck. How do I get out of the dead Android loop?
I googled the update, and found this on the ATT Support website.
Beginning on October 9, 2012, AT&T and HTC have released an additional software update for the HTC Vivid that will be available via firmware over-the-air (FOTA). This 13MB software package updates the firmware version to 3.26.502.56_R23 and improves sensor performance.
NOTE: Customers must have a data SOC in order to obtain any FOTA updates. Customers who have a data opt-out SOC are not able to receive FOTA updates.
strose09 said:
Think the majority of users on here are rooted and running custom roms so they wouldnt' be installing this.
Click to expand...
Click to collapse
Hmmm....
Sent from my HTC PH39100 using Tapatalk 2
For the users in boot loop I just recovered from it. Boot into cwm and clear the cache a couple of times and reboot.
Sent from my HTC PH39100 using xda app-developers app
kos26 said:
For the users in boot loop I just recovered from it. Boot into cwm and clear the cache a couple of times and reboot.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
This Fix works. My phone no longer boot loops
3f62011 said:
Sorry bludiamond.
Since my phone is rooted, I did not want to install this update. It's quite upsetting that AT&T forces the update unconditionally.
Anyway, I had let the download to complete, but did not let it to install. The update did prompt me, whether I want it to install now, or later. I had opted for later.
Then, after some Googling, I had deleted the download (from /sdcard/Download), and had un-installed the following services: com.htc.demoflopackageinstaller and com.smithmicro.dm.
Then, I've rebooted the phone. Afterwards, the phone still had a notification, that there's an update ready to be installed. When, selecting the notification, updater did realize that the downloaded file is gone, and had prompted me whether or not I'd like to download the update again, on which, I had responded no. The notification is gone, and AT&T did not prompt me to download and install the update again, at least not yet.
My phone seems to be OK.
Click to expand...
Click to collapse
After getting my phone out of the boot loop I tried this and am no longer prompted to update. Thank you for the help
Apatche69 said:
This Fix works. My phone no longer boot loops
After getting my phone out of the boot loop I tried this and am no longer prompted to update. Thank you for the help
Click to expand...
Click to collapse
I had the looping issue too. I cleared the cache once and rebooted. Received a message that there was a problem with the update and to wait for the next update. Phone seems to be okay since.
I'm unlocked s/on..no custom rom..it was so early, I must have hit the wrong button, so I'm stuck in the loop and can't seem to get into recovery either..ugh
I'm stock - not rooted. I did do the download without any problems, although you do have to manually reboot after the update.
It supposedly improves the sensor. Not sure what that means, but that's what the ATT website says. Other than it changing my default ringtone, I don't see any difference.
Could not get it out of the loop. Took it to the service center and neither could they..they ended up replacing it under warranty..thank goodness. Said that another lady came in with the same issue as well.
AT&T Upgrade to Nowhere
I'm running stock on the HTC Vivid and got this upgrade pushed out by AT&T. This is the second AT&T upgrade I've done on this phone (the first was to ICS not long after I got the phone).
I ran the update yesterday, which force rebooted my phone and I watched as the upgrade downloaded and installed, then came back up.
NOTHING has changed. I don't know what AT&T supposedly upgraded, but it's certainly nothing noticeable.
I didn't even get the "3.26.502.56_R23" software designation that the AT&T help article says I was supposed to see.
It was literally an upgrade to nowhere. Not sure why I wasted time off the grid and battery power on it.
As usual-- AT&T fail.
At least no harm was done.
I was rooted, stock ROM, and got the notification yesterday. I postponed as much as I could but it finally wouldn't let me anymore and I let it try to update.
Of course, went into a boot loop. I did eventually get the boot looping to stop by reflashing the wxc recovery image and CWM-root, but then my wifi wouldn't work. I suspected some difference in the kernel version or some other borking of the update.
Long story short, I had to re-lock, go back to stock, and re-unlock and root again. Then spend the time (ongoing) to get my environment back. Thank goodness for Titanium backup pro and Dropbox. LOL.
Wish I could bill AT&T for the 18 hours I've spent. And if they push it to me again, I'll be irritated.