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.
Droid 4 running OTA GB 2.3.6 here in W. San Jose, CA
I get "check for update is not available at this time.". For many days now. LTE and Wifi (LTE is almost instant and Wifi takes 5 seconds or so).
I've looked at a zillion posts about "check for update is not available" and none have a definitive explanation. -- and all of them are from a couple of months ago or earlier. Didn't find anything recent.
I understand that the intended meaning of the message is that you can't connect to the update server.
I've read dozens of "solutions" but each one of them didn't work for somebody else so I've got to assume it was just coincidence -- resetting the phone, factory reset, renaming files, and so on. I *have* network connectivity. Data works great. Apparently I'm not able to connect to the update server? That shouldn't have anything to do with rooted or not, frozen or deleted apps, safestrap, etc. Fail to update once you get the download, sure. But I am expecting to be able to connect to the server.
Anybody know for sure?
I could imagine that the connect request might contain info identifying my particular phone model or ESN (would expect software version checks to be exchanged after connecting though). Something like that.
How does VZW roll out the updates? is it strictly by geographic region? or blocks of ESN? or what?
I have the "official" OTA download from here but figured if I side loaded it I might get out of sync or cut off from future OTAs? Failed to find a definitive answer on that too .
#eliot# from dialer then restart and try again... let us know
Sent from my DROID4 using xda app-developers app
---------- Post added at 01:33 AM ---------- Previous post was at 01:29 AM ----------
dbreezy187 said:
#eliot# from dialer then restart and try again... let us know
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
That will check in with Motorola's server btw kinda busy sorry for no further info
Sent from my DROID4 using xda app-developers app
Nope.
That's one of the myriad ones I read about (didn't recognize it right away though 'cause the post I saw it in had it in numbers instead of letters). One guy said it worked for him and the next guy said it didn't.
If you haven't tried it, as soon as you type in the final '#' you get a popup that says "Log Checkin initiated". So it does *something*but it didn't change my Check for update is not available... maybe whatever it is supposed to do never got into the server either.
lol, reminded me that I used to have a comprehensive list of all those codes for my Treo. Now I got yet another mission
[edit] dahaha, "there's an app for that". https://play.google.com/store/apps/details?id=cx.makaveli.androidsecretcodes&hl=en
Other then that Matt had to push the up date to them.. I believe on one post he actually said to get back to stock 100% wipe cache partition then he pushed the ota to said device... he was really nice about the being rooted over there... the forum is closed now so I can't check for more info.. id post over at Motorola owners forum
Sent from my DROID4 using xda app-developers app
I'll give it a bit more soak time I guess. I will try side loading the update before resetting/wiping. Reset/wipe will be my last resort. First choice is OTA.
Part of what prompted my post is that I'm unclear if the phased rollout is complete.
Is it the case that EVERYONE with a Verizon Droid 4 who is going to get the notification should have gotten it by now? Or is VZW still in the middle of the phased roll out for the Droid 4's? Got to wondering since googling for the Unavailable message only returned results that were at least a couple of months old. I figured it's possible that server access was/is part of the phasing mechanism but, then again, expected to find constant posting about that if it was. It seems that the mechanism of the roll out and the schedule is also a well kept super secret.
are you rooted? I had that same problem for days before I realized unrooting will fix that. Despite what a lot of trusted posters have said here and other forums, having root and no other changes will cause that. I used voodoo ota rootkeeper (free on market) to unroot and I had the OTA installed within 10 minutes (downloaded over wifi). it is recommended you update your binaries in your superuser app before using rootkeeper.
if you're not rooted then this doesn't apply.
---------- Post added at 02:57 PM ---------- Previous post was at 02:50 PM ----------
one more note, the stock recovery on the D4 after ICS update now tracks whether you are or you were rooted. Unrooting your phone no longer hides the fact that you were at some point rooted if a service rep goes into the stock recovery screens. this has been reported on other phones earlier in the year, now also true for D4.
No effect.
I've tried all combinations.
I've used the D4 utility only to root and install safestrap ( and used safestrap only to do a backup. nothing else)
Routine goes like this:
- in safestrap: uninstall recovery
- in settings->applications->manage applications: safestrap -> force close, clear data, uninstall
- in ES File Explorer: delete /system/bin/logwrapper
- in ES File Explorer: rename /system/bin/logwrapper.bin -> /system/bin/logwrapper
- power off, reboot
- in Titanium Backup: clear filters (ALL)
- in Titanium Backup: unfreeze all user and system apps
(the only "system" bloatware I've removed was uninstallable through the normal settings->applications -- I did not use TI for that)
- in OTA Rootkeeper: delete su backup
- in superuser: update su binary
- in OTA Rootkeeper: Protect root
- in OTA Rootkeeper: temp un-root
- power off, reboot
Try to check for updates with 4G LTE (i have great reception) - fails in a second or less
Try to check for updates with WiFi - fails but it takes 5 seconds or a little longer for a response/popup
Since you installed Safestrap you can't install the OTA update anyway, so not much of a bother that you can't get it pushed to you It'd fail trying to install as OTA updates require the stock recovery.
Root does not affect it. My wife's Droid 4 was rooted (by me) and many system apps frozen and the OTA was pushed to her the same day the SOAK testers were scheduled to get it (she was not part of the SOAK test, though I was). My sisters Droid 4 was rooted as well and she got the OTA pushed to her and installed a week or so later,
You'll have to uninstall the recovery Safestrap installs, and uninstall Safestrap. You'll also have to edit some files (logwrapper.bin or something like that).
for the ota
sbf 217 4.0.4 with rsd
SBF
http://sbf.droid-developers.org/cdma_maserati/VRZ_XT894_6.7.2-180_DR4-16_M2-37_1FF.xml.zip
rsd
http://forum.xda-developers.com/showthread.php?t=1348587
dont forget to install the motorola driver first and enable debugging mode in development in your settings
i think they are here https://motorola-global-portal.cust...e-can-i-obtain-the-usb-drivers-for-my-device?
UPDATE: (lengthy with fairy tale ending)
Management summary: I am now on the OTA ICS (acquired over the air). following a wipe/factory reset
Called *611 tech support yesterday afternoon.
Got someone that sounded like they were located on this continent AND proficient. Always a good sign when they ask what the problem is right after getting your name instead of insisting on the 5 minute scripted generic question and answer form. Stated my problem was related to the system update for my Droid 4 and that I had been getting "check for update is not available..." for a few days now. My questions were "is that expected/normal?", "I understand roll outs are phased. What is the date the roll out is expected to be complete? -- last group has been notified or can pull it?", "If the persistent 'check unavailable' message is indicative of a problem then do they have possible fixes/known problem?".
He checked for the dates and said they expect to have completed the roll out by the end of September -- all Droid 4s should have it or have it available to them by the end of September. That the "check unavailable" did not necessarily indicate a problem but that it was not "normally expected" and more likely indicative of a problem on my end since it was persistent over that length of time. I said I felt better knowing they were still in the phased roll out and maybe I should just wait a while. We tried a soft reset (vol- and power) with no effect. He said he was afraid the next step would be to try a factory reset and advised I wait a while to see if the condition cleared. Went on to say that one effect/risk of the factory reset was that, if there was a software/system problem with GB preventing the OTA check it might also effect the factory reset -- if the phone had a problem coming up it might just pull the ICS update in order to come up from the reset. (Nice! he didn't just assume I would be OK with that following a reset). That I decided to wait I should definitely call back if it didn't resolve in 2 weeks. -- OK, that was a pleasantly refreshing encounter with tech support.
So I figured, fine, I haven't really tested a restore/recovery with Titanium backup and I've never gone through a factory reset so maybe now was the time. Had 2 alternatives. I could try using the D4 utility recovery using the official (same as the OTA) zip I have on my sd card or try the wipe/factory reset and see if OTA started working.
My thoughts (due to lack of any knowledge):
- Apparently once you get on ICS there is no reversion to GB (at least the actual kernel).
- Likely they have history at Galactic Headquarters of OTA and/or physical upgrades at factory or service centers for a particular phone.
- Obviously they check the phone's system version when you connect to the OTA server. Have to in order to determine if you even need an update. Additionally they would probably check if the version the phone reports is the version they expect it to be on -- I would, for technical and support reasons.
- So maybe if I went to ICS myself it might remove me from the OTA path for future updates. Not a big deal in my mind but, heh, why eliminate alternatives if you don't have to.
* reinstall safestrap and do a backup
* uninstall safestrap (uninstall recovery, uninstall safestrap apk, delete logwrapper and rename logwrapper.bin to logwrapper)
* unfreeze everything with Ti
* batch backup all user apps with Ti
* batch backup (green and yellow) system data with Ti
* temp un-root with Voodoo
* wipe/factory reset
It comes up in GB
(lot of activity follows which I didn't write down and can't quite remember)
Basically I waited for some market activity and whatnot to die down and tried update. Immediately said update available!
Cancelled that, got Ti (pro) back from the market, batch restored missing apps.
I have eset security (i don't know... I have it on my PCs so I figured I'd stick it on my phone too. Not that I think there is much in the way of virus for android yet). Eset has an urgent notification that it wants to be added as an administrator for the device so it can protect itself from installation of counterfeit Eset. I understand that but I'm wondering if maybe Eset maybe had something to do with my fail to connect to OTA. Probably not but that's the only thing that presented itself after the reset that looked like it could have been related.
OTA again to download the update -- deferred update after download.
Oh wait, forgot to batch restore system data. Did that, checked for sms messages. All good so I triggered the update.
Holy crap!!! I forgot to temp un-root! Figured the worst thing I could do was try to abort anything and just let it run and expect the update to fail.
It didn't fail. It completed just fine?
I go through the new phone screens far enough to sign into my google account.
Bunch of market update activity.
Restore missing apps with Ti
Restore system data with Ti
Then it strikes me that, sure enough, I'm still rooted. I did not restore root anywhere after the update.
I was rooted before the update (by accident) and still rooted after the update... Whats up with that?
So at the moment I'm a happy camper.
All my apps seem to have been effortlessly restored.
All my app settings seem to be intact.
All my system data seems to be intact with no migration issues.
I'm still (magically) rooted without doing anything.
standard101 said:
[/COLOR]one more note, the stock recovery on the D4 after ICS update now tracks whether you are or you were rooted. Unrooting your phone no longer hides the fact that you were at some point rooted if a service rep goes into the stock recovery screens. this has been reported on other phones earlier in the year, now also true for D4.
Click to expand...
Click to collapse
I am going to have to disagree with this. I was rooted and flashed. Ran the download and the install failed. I then did a factory reset (lost my flash and root as expected) and immediately ran the download. Install went off without a hitch. I even had a support rep from verizon and motorola on the phone during the install when i was doing it because i was so mad about the slow download. They were watching the install once it was done because they both stated that everything on my phone "looked good".
YeeP said:
I am going to have to disagree with this. I was rooted and flashed. Ran the download and the install failed. I then did a factory reset (lost my flash and root as expected) and immediately ran the download. Install went off without a hitch. I even had a support rep from verizon and motorola on the phone during the install when i was doing it because i was so mad about the slow download. They were watching the install once it was done because they both stated that everything on my phone "looked good".
Click to expand...
Click to collapse
I don't think that's what he was saying.
After you go to ICS it tracks (displayed in the recovery screen) if you are or were rooted.
Go into recovery and you will see a yellow "qe 0/0" left of the android.
ge 0/0 -- are not rooted/never been rooted
ge 0/1 -- are not rooted/been rooted sometime prior
ge 1/1 -- are rooted/been rooted
No idea if this was tracked before but not displayed in recovery. I suspect it was. On GB they were checking system files on boot and logging differences (I think I read they were comparing system file CRCs?). The list was getting logged to a qer...something log file (I forgot the file name and where it's at). I verified that. On my rooted GB there were mostly /xbin files and a couple of others listed in the log.
Now on ICS my recovery screen shows "qe 1/1".
Oddly enough I did a factory reset, forgot to temp un-root and my root persisted through the OTA update just fine. No idea why.
Since my root persisted through the update I was not able to check before re-rooting to see if it displayed "qe 0/0". My guess is this was always logged/stored and they just added the display to the recovery screen. I would find it almost inconceivable this information (and other) was not written to NVRAM since day one. Basic support/diagnosis information.
Recently my phone received an OTA update that I didn't want to install. I kept pushing remind me later but for two days in a row around the same time (between midnight and 1:30 am) my phone showed me the update with no option to remind me later. It then proceeded to reboot on its own and try to install the update. It failed both times thank GOD! However, my real concern is likely with AT&T because I believe this update will patch the exploit TowelRoot used. Once I calmed down (I was highly pissed) I used Titanium BackUp to freeze the app AT&T software update app, and now I've not been bothered with those irritating update prompts. Has anyone else tried to install the update while rooted? If so, was it successfully done? Has this issue I described happened to anyone else?
So Blu finally released the Marshmallow update for the Vivo XL... and it kind of sucks. It's only 6.0 and not 6.0.1. The Gionee model of this phone has been running 6.0.1 since June. Updating via the OTA was a nightmare. It failed 3 times before it finally worked. Then I performed a factory reset, as always when performing a major update. It seems that you cannot format the memory card to use it as internal storage. It gives you the option but it ALWAYS fails. Also, the battery life blows. I lost 20% battery overnight while the phone was inactive and supposed to be dozing. Very disappointing so far. Anyone else have any problems?
My update failed several times but that was about he only problems I've faced. After a factory reset everything seems to be working fine. I am able to use my micro SD as internal as well. No other problems at all with what you mentioned. Everything seems to run smoother than it did on lollipop (but that could be as a result of the factory reset).
I'd love the upgrade if it didn't break compatibility with one crucial app. Until the issue of false root positives is addressed, I'm sticking to lollipop.
my wife's phone updated first try, didn't even feel the need to factory reset it after it came up, so far buttery smooth and better battery life, i think like 1 % over night sitting there and moderate use she got a few days out of her phone. so far i'm happy
My Vivo XL updated with no problems. However, i have noticed that it runs slower than before when viewing Netflix or listening to music, even though i only have 2 or 3 other apps opened at the same time. I usually have to free up more RAM to get it to work properly but i never had this problem when the phone was running Lollipop. Can be irritating at times because even some websites will lag or typing text messages can be slow because the lag time is ridiculous.
weatherdude35 said:
My Vivo XL updated with no problems. However, i have noticed that it runs slower than before when viewing Netflix or listening to music, even though i only have 2 or 3 other apps opened at the same time. I usually have to free up more RAM to get it to work properly but i never had this problem when the phone was running Lollipop. Can be irritating at times because even some websites will lag or typing text messages can be slow because the lag time is ridiculous.
Click to expand...
Click to collapse
Back up your things and try a factory reset. Had the same problems but this fixed it.
This was a good updated for me
WiddleyScudds said:
This was a good updated for me
Click to expand...
Click to collapse
Yeah. I'm the OP. After a couple days, the update settled in. Battery life went back to normal, which is to say, stellar. So basically, all good here.
xphyle1971 said:
Yeah. I'm the OP. After a couple days, the update settled in. Battery life went back to normal, which is to say, stellar. So basically, all good here.
Click to expand...
Click to collapse
Extreme mode is also impressive don't know if you've seen it. Do you know if there is root yet? I've attempted king root but it fails and I don't want to brick this phone trying to F with other methods
I'm also running 6.0 and it seems to be working great. Much smoother and better battery life. Does anyone know of a method to root the Vivo XL running 6.0 yet?
Good afternoon guys, I have a problem, to update mi Blu vivo XL to Marshmallow the official BLU site says that my version number should be : BLU_V0030UU_V10. I am a little confused about this version number. That is the number in the Wireless update? I have this Current number in Wireless update BLU_V0030UU_V07_GENERIC_5.1_20160126-1033, but when I have tried to check for updates I can't install nothing, this message appears " Your system was damaged, wireless update is disabled". I don't know what to do, I can't install the update via Wireless update, Is there any other method like manually transfer a file? If it is possible, where can I find the file and what is the file name?
adaeda said:
Good afternoon guys, I have a problem, to update mi Blu vivo XL to Marshmallow the official BLU site says that my version number should be : BLU_V0030UU_V10. I am a little confused about this version number. That is the number in the Wireless update? I have this Current number in Wireless update BLU_V0030UU_V07_GENERIC_5.1_20160126-1033, but when I have tried to check for updates I can't install nothing, this message appears " Your system was damaged, wireless update is disabled". I don't know what to do, I can't install the update via Wireless update, Is there any other method like manually transfer a file? If it is possible, where can I find the file and what is the file name?
Click to expand...
Click to collapse
I also have this issue. probably because of being rooted. However even I restored original ROM backup and original recovery, I still got such information and cannot do OTA update.
it works correctly , the system is smooth and everything is fine , maybe You a have a rooted device try reflashing and redownload the update
adaeda said:
Good afternoon guys, I have a problem, to update mi Blu vivo XL to Marshmallow the official BLU site says that my version number should be : BLU_V0030UU_V10. I am a little confused about this version number. That is the number in the Wireless update? I have this Current number in Wireless update BLU_V0030UU_V07_GENERIC_5.1_20160126-1033, but when I have tried to check for updates I can't install nothing, this message appears " Your system was damaged, wireless update is disabled". I don't know what to do, I can't install the update via Wireless update, Is there any other method like manually transfer a file? If it is possible, where can I find the file and what is the file name?
Click to expand...
Click to collapse
Same here, my android 6.0 version was v07. Oddly enough, the first OTA update is v10. But then the next OTA update took the label back to V07. I reverted back to android 5.1 stock rom, since that was the only way I could get TWRP to load.
How can I go back to the lollipop update ???
Pls I need you guys to help me
I'm using BLU vivo XL, I flashed my phone through stock recovery and I wiped cache & format the phone then rebooted the phone, ever since then its been writing invalid imei, I checked the baseband and it's not showing anymore, I've tried to fix this but no way, I later downloaded the stock ROM and reflashed the phone still its showing invalid imei, I wanted to download Gionee S plus stock firmware but dunno if it's gonna fix the problem, pls I need guys to guide me on how best to fix this issue, its been two weeks + now, God bless.
someone share marshmallow for vivo xl (blu vivo xl v0030uu)
**I don't condone anyone using a Note 7 since the recall. **
After spending a lot of time trying to root and failing. I was able to get a slightly different stock rom and now have full battery 100% capability (V2 and previously had update to block at 60%)
What has me excited is when I go to manual update it gets a "Processing Failed" message right away. Tried over wifi and both with a live SIM to make sure.
My questions is, if I can't force update, will I now avoid the OTA coming in couple weeks?
Thanks
Edit - so if I can't get the update to limit charging to 60% again, then I shouldn't receive other OTA's?
I was thinking of rooting mine too but instead of I flushed firmware and rolled back to the green battery and blocked packages with Package Disabler PRO.
PabloMike99 said:
**I don't condone anyone using a Note 7 since the recall. **
After spending a lot of time trying to root and failing. I was able to get a slightly different stock rom and now have full battery 100% capability (V2 and previously had update to block at 60%)
What has me excited is when I go to manual update it gets a "Processing Failed" message right away. Tried over wifi and both with a live SIM to make sure.
My questions is, if I can't force update, will I now avoid the OTA coming in couple weeks?
Thanks
Edit - so if I can't get the update to limit charging to 60% again, then I shouldn't receive other OTA's?
Click to expand...
Click to collapse
exactly package disabler and call it a day
playya said:
exactly package disabler and call it a day
Click to expand...
Click to collapse
It's for a friend so I'll factory reset the device before giving it back. I can advise him to download package disabler once he gets logged on his gmail account etc -
But if the phone gets a "Processing failed" error right away when clicking on check for updates, will it receive push updates still since it can't register and download any of the previous updates at the moment?
Unless your on the orig note 7 firmware rooting isnt going to happen.
Unless you have a paid license of package disabler before it hit version 7 using it to block an OTA also isnt going to happen.
Sent from my Note 7, S7 Edge or S6
Solution here: http://forum.xda-developers.com/showpost.php?p=70283551&postcount=4
Im using Odin3 i currently have the 60% battery i just want to root it to use as a mini tablet or music player. How long does it take for odin to get the firmware to update im using the all variants firmware an it still hasnt move from setup connection am i doing something wrong im just wanting to have 100% back since im past the date to return it what firmware i need an wat other methods i could use to make this faster