Related
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.
So I know being rooted and receiving OTAs isn't a problem, but I've read that having frozen apps can be. What happens if I/we get an OTA and an app is frozen? Does it fail gracefully or will I have a nice shiny paperweight as a result?Could we freeze/disable the update app/service until they push one out and we're ready for it?
Most likely the phone will reboot to do the update but will fail during the file system check. Your phone will then boot again and a message will pop up telling you the update has failed.
This is what happened with my D2. I would expect the same to apply to the D3.
Yes, your phone will refuse to take the update.
Nice. Sounds like it fails pretty gracefully.
Let's say your rooted but did not freeze or do anything at all will you still get a update. I've herd yes you can and no you can't. I can understand if you have froze or deleted things that you wont but if you didn't do a single thing except root that you might be able to get an update?
Sent from my DROID3 using XDA App
If you're rooted but have not frozen / deleted anything you will get the update and likely lose your root.
Getting the update to install successfully depends on what you have frozen vs. What the update tries to update. If you freeze something it wants to update, it will fail.
Root itself doesn't play a part in this.
Sent from my DROID3 using XDA App
So having the update fail because of required frozen apps may be a good thing! It will prevent unroot and prevent a fix to the root exploit on your phone.. giving you time to come back to the forum and check for other users experience.. i love XDA...
I definitely want an update when one comes out to fix the camera a the cell standby. I have froze stuff but I will unfreeze them when an update comes out. But nice to know that I don't have to do any weird stuff to take an update. Now will we be able to root again.
mkultramega said:
If you're rooted but have not frozen / deleted anything you will get the update and likely lose your root.
Getting the update to install successfully depends on what you have frozen vs. What the update tries to update. If you freeze something it wants to update, it will fail.
Root itself doesn't play a part in this.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Sent from my DROID3 using XDA App
Honestly, it's best to just wait. The update might patch root exploits and be very hard to root. If you wait just a little bit, then the devs will release a rooted and flashable update. Well, when we have recovery, that is. But recovery shouldn't be too far off.
If fixing the camera and cell standby is more important than root, then you should proceed with the update. If you want to keep your root, do not update quite yet, as GoogleAndroid said. It just might patch the exploit.
I would like to have non blue pics that would be nice. My phone ran really good before I froze stuff its a bit faster now so I would take the update and im sure someone will root that if not im still a happy droid 3 owner.
Sent from my DROID3 using XDA App
Here's a quick guide to get to the latest OTA Jelly Bean. Looks like its Official: http://www.droid-life.com/2012/11/3...or-droid-razr-hd-and-maxx-hd-as-build-9-1-41/
and, yes, you CAN fastboot back to 0.7.2 after applying this update: http://www.droidrzr.com/index.php/t...erizon-new-leak-and-atrix-hd-att-firmwarefxz/
This guide will take you from any current version, back to original factory release, root, and then update to 0.7.2, and then new Jelly Bean.
If you are ALREADY rooted on 0.7.2, then simply do Step 0-1 and 12-22.
Requirements:
1. You have a PC and have the Motorola Drivers installed for your Phone when its plugged in as USB.
2. You have an SD Card for your Phone (yes, you can do this without an SD card, but its not covered in this guide.)
Issues
1. You dont have an SD Card? -- OK, you can do it without, but its not covered here. hint, you need to use adb a little and push the update to the proper location when you dont have an SD card.
2. You dont have the Motorola drivers installed for your Phone? Step 4, or Step 6 failed? --- OK, in that folder, open 'Drivers[REQUIRED]' and run either the 32bit or 64bit version depending on your OS.
Downloads:
Jelly Bean OTA 9.1.41 (Android 4.1.1): http://sbf.droid-developers.org/vanquish/delta-ota-Blur_Version.0.7.2-9.1.41.XT926.Verizon.en.US.zip
MD5: 0aebd88f7e975bdc4323002215cad727
DROID RAZR HD Utility 1.10: http://forum.xda-developers.com/showthread.php?t=1970267 download: http://www.batakang.com/ftp/DROID_RAZR_HD/DROID_RAZR_HD_Utility1.10.zip
0. Backup anything you want to keep on your phone (Camera pics, etc)
1. Put "delta-ota-Blur_Version.0.7.2-9.1.41.XT926.Verizon.en.US.zip" on your Phone SD card
2. Unplug USB and Power off your Phone
2. Boot into bootloader mode by holding down Volume up, Volume down and Power
3. Once in Boot Mode Selection Mode screen, select “AP Fastboot” using the Volume Down Key then press the Volume Up Key to select it.
4. Plug in Phone to USB and use the DROID RAZR HD Utility 1.00 to Fastboot Restore 0.6.25 (ICS 4.0.4 Official Software)
5. a. Boot Phone b. turn on USB Debugging (Settings | Developers) c. unplug and plugin Phone
6. install Root exploit using DROID RAZR HD Utility 1.00 (make sure you read the note about pressing Vol Up and Power on your phone when asked to do so). Also NOTE: Wiping 'Data' will erase all your Camera pics that are NOT stored on 'SDCard' by default.
7. Sign-in to Google Play and Update Superuser
8. Open Superuser and update binaries
9. Open OTA Keeper: click 'protect root' and then 'temp unroot'
10. Open System and check for Updates, download and then install the 0.7.2 update
11. Once phone is booted, Open OTA Keeper: click 'restore root'
12. Open Superuser and make sure you are rooted, check for 'Updates'
13. Open OTA Keeper: click 'protect root' and then 'temp unroot'
14. Unplug USB and Power off your Phone
15. Boot into bootloader mode by holding down Volume up, Volume down and Power
16. Once in Boot Mode Selection Mode screen, select “Recovery” using the Volume Down Key then press the Volume Up Key to select it.
17. Once the Android with the belly open logo shows, press both Volume Up and Volume Down
18. use Volume Down to navigate 'Update from External Data' and press 'Power' to select it
19. use Volume Down to navigate 'delta-ota-Blur_Version.0.7.2-9.1.41.XT926.Verizon.en.US.zip' and press 'Power' to select it
20. the update will take 5-10 minutes. Do not worry when its at 50% and takes a long time. Once done, hit 'Power' to reboot into Jelly Bean
21. Once phone is booted, Open OTA Keeper: click 'restore root'
22. Enjoy Jelly Bean and Root!
Bout the same process I used
Works!!!!
Just make sure to root and protect before going to jelly bean
NO WAY to root jelly bean right now!!! I tried
Sent from my DROID RAZR HD using xda app-developers app
I originally liked the idea of rooting, then I found out that I don't need root to reliably freeze apps, and messing with verizon stuff makes it hard to flash updates in the future, so I'm on the fence... so I guess are there any downsides to rooting? If not then i'd do it for the heck of it.
BinarySauce said:
I originally liked the idea of rooting, then I found out that I don't need root to reliably freeze apps, and messing with verizon stuff makes it hard to flash updates in the future, so I'm on the fence... so I guess are there any downsides to rooting? If not then i'd do it for the heck of it.
Click to expand...
Click to collapse
U have to have been rooted to properly freeze or remove some of the bloat. .as its in the systems
I use titanium backup for that
Sent from my DROID RAZR HD using xda app-developers app
Update to .41 went flawlessly after downgrading from .39, removing safestrap and starting anew. That said, I found it odd that when I updated to .41, my phone s running painfully slow. Upon examination, I found that the CPU frequency was being restricted to 384mhz for both min and max. Using setcpu I changed this of course, but I am curious to know of anyone else experienced this? I still feel like the .41 update runs more slowly than the vitreous rom with safestrap.
I'm am having a hard time believing this is going to be the official release. HDMI output is still wonky. There is no way to change the resolution and even the overscan option that was present in ICS is missing. Why would Motorola remove such a useful feature?
I thought the version match the one that Verizon said was official on their website
shaddix2 said:
I thought the version match the one that Verizon said was official on their website
Click to expand...
Click to collapse
That's what I read
Super smooth for me
Sent from my DROID RAZR HD using xda app-developers app
Lol you guys cant just wait less than a week to take the official OTA???
Also just wanted to point out that if anyone else here has the developer edition you don't need to go through this. You can just simply root the JB OTA.
GoClifGo05 said:
Lol you guys cant just wait less than a week to take the official OTA???
Also just wanted to point out that if anyone else here has the developer edition you don't need to go through this. You can just simply root the JB OTA.
Click to expand...
Click to collapse
Hell no man 2 days is essentially an eternity when it comes to jelly bean!!
lucidvtec said:
U have to have been rooted to properly freeze or remove some of the bloat. .as its in the systems
I use titanium backup for that
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
In Jellybean you can disable apps so they never run, don't need root for that. And I ain't removing any bloat(just disabling), because I've heard the bloat needs to be intact to get future updates.
So again, any downsides to rooting? If I root and don't remove bloat will my phone still be upgradable and not too 'tweaked'?
Its trivially simplistic to remove root, in fact once you are more comfortable with it, you will not want to take updates ota anymore. There is more risk in getting bricked that way(ota) because you don't have custom recoveries and backups etc.
BinarySauce said:
In Jellybean you can disable apps so they never run, don't need root for that. And I ain't removing any bloat(just disabling), because I've heard the bloat needs to be intact to get future updates.
So again, any downsides to rooting? If I root and don't remove bloat will my phone still be upgradable and not too 'tweaked'?
Click to expand...
Click to collapse
If you just freeze bloat you can unfreeze it before the update. And yes if you only root you can still get updates.
Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2
I'm trying to go through the last few steps to get Jelly Bean but not root. When I boot into recovery and select update from sd card, recovery gives me an error that it failed to mount sd card. Any idea why?
Sent from my DROID RAZR Maxx HD
gtownie said:
I'm trying to go through the last few steps to get Jelly Bean but not root. When I boot into recovery and select update from sd card, recovery gives me an error that it failed to mount sd card. Any idea why?
Sent from my DROID RAZR Maxx HD
Click to expand...
Click to collapse
Do you have a SD card installed in the phone? Is it formatted fat32 or something else? Formatting the card within the phone is the best way to ensure compatibility.
Man I feel pretty dumb. Didn't have an sd card in the phone.
Sent from my DROID RAZR Maxx HD
Updated with this leak! Everything went well... got impatient, but it seems like it will be the same version as the official update coming this week.
So far so good, everything seems to be working well, but volumes (ringtones, notifications, etc) seem to be a bit lower than they were in ICS... anyone else notice that?
Everything Worked just as described.
Curious though if this will be the same as the OTA.
sammyboy405 said:
Everything Worked just as described.
Curious though if this will be the same as the OTA.
Click to expand...
Click to collapse
Lots of people are saying they have heard/read that this is the official OTA.
big ach said:
Updated with this leak! Everything went well... got impatient, but it seems like it will be the same version as the official update coming this week.
So far so good, everything seems to be working well, but volumes (ringtones, notifications, etc) seem to be a bit lower than they were in ICS... anyone else notice that?
Click to expand...
Click to collapse
They were too loud in ICS on the lowest settings. Minimum volume for ringer settings is now quiet how it should be!
I took the JB OTA update. Which works great except the phone wont allow me to access my dialpad mid-call sometimes...weird. Anyway, I used Voodoo OTA Root keeper and took the update and restored...all check marks there, but no root. So i decided to wait for an exploit for a lil while and then i got my wish! Which using ubuntu and the terminal and not windows seemed easier to me so i set it up.
Did all the steps and it worked! or so i thought...phone vibrated and came back on with the superuser apk etc. Check with root checker...no root. Not sure where my conflict is coming from now? Not sure if I should Fxz JB 4.1.2 or what, I've been reading some things on that thread, different problems people have had seemingly with the firmware. I didn't think it should matter as far as rooting the phone goes, but one person was saying that using it would stop the exploit from working? Never thought that would be the case, am i missing something?
Also, my phone after i tried both of these keeps asking me to update my superuser binary. First with one superuser app and now with the one that was with the exploit package and i can't seem to do it. Feel like i'm missing something simple here but i'm not sure what it is?
Did you wait for the vibrations and then press a hardware button, like vol up or dn? Others have reported having to go through the exploit more than once to get it rooted. Give it another try. I was able to get root on the second try, but I royally messed up the process the first time.
Embarrassing, but no I forgot the hardware button. Worked like a champ second time lol my advice don't do this late when your not awake, follow all the steps!
Sent from my XT875 using xda premium
Well I am surprised I received the 5.0.1 update notification but after agreeing and letting device restart, it didn't happen and device claims that is up to date and still on 5.0
Did Google retired the OTA?
Your not alone im having the same issue. My 6 is on verizon and the same issue has happened that you described. Cleared data in the frame service. Phone claims up to date...still 5.0
Darn it....
At least AT&T and Verizon respect the "direct updates form Google" advantage of the Nexus brand.
Anyone able to help?
If you've flashed a custom recovery and/or are rooted, the OTA will fail. It will just reboot without doing anything, then the OTA disappears when back in Android and autoupdate says you're up to date.
You can download the image from the Nexus factory images site, extract the system and radio images, and flash them yourself with either fastboot or Nexus Root Toolkit.
This post gave me the idea:
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
And here's the link to the latest N6 image from Google:
https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz
You'll need WinRAR or similar to extract the download from Google.
It failed for me too, bone stock. Connect your phone to a charger . it reappear and I was able to update
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Same here.... Verizon/Stock Nexus 6. Mine didn't even reboot. After I chose to accept the update, screen just flashed to up-to-date. Now claiming up-to-date each time.
Strange I'm in the UK and have the exact same problem. Got a notification thru last night for the 5.0.1 update, decided to leave it until this morning and it's gone. Must be something to do with Google.....
I am bone stock and have the same issue . Last night it said there was a new update and I said ok lets do it.. It said it was going to restart and then it never restarted or nothing and says its up to date even though its on 5.0 . I am on verizon !!!
StrangeTimes said:
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Click to expand...
Click to collapse
Immediately. I guess I was lucky
I did not root/installed custom ROM neither, which boost the upset. But again, I am glad that I should not worry for update delays due the device being from a carrier's branded, and evidently I am not the only one, I will give Google the opportunity before opting for manually flash the update which that means dealing with an 20+ GB backup first.
Sent from my Nexus 6 using XDA Free mobile app
Question
Hey i was wondering, I got my OTA update last night and of course my phone is unlocked and rooted but i still attempted to download and install it. I was successful in downloading the update and my device rebooted. I shortly got the error message so i rebooted the device and when i logged back on i was still on 5.0 and the OTA notification is now gone.
My question is, since i downloaded 5.0.1 and the device rebooted in the attempt to complete the install will this now cause my phone to no longer get the 5.0.1 update notification? I plan on unrooting once i get the notification so i can go ahead and OTA and when that is completed root the phone again. Or am I now forced to flash a factory reset in order to get that OTA update again?
ideally i would prefer to wait for the OTA so i dont have to factory reset.
ATT Stock
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
gleonard3 said:
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
Click to expand...
Click to collapse
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
You are correct! Thanks. Reading elsewhere had it backwards. This worked. Off to update now. Thanks again.
No worries bud
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Do I need to be rooted to flash update? On my one plus I could download update and the go to recovery and flash it.
Tia,
Ian B
Slorks said:
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just for literally a second or so..