Database Develop

Incredible OTA Update 1.65.605.2

Has anyone else received this update?

Not here.
Los Angeles, CA

lol figures once i get root an update starts rolling out, it probably enables wifi n like they released for the EVO today.
1.22.605.2 is the software version i have (rooted)

It adds 3G Mobile hotspot and fixes the signal issue, im in a pickle now though lol. cant remove superuser

Not exactly a pickle - just don't do the upgrade, wait for someone else to take the OTA download and make it root-safe.

where did you confirm this info as to what the update offers?

I guess i am confused, what would happen if we did the update with our rooted phones?

Nothing. Because with rooted phones you won't see the OTA Update...but if you were to manually upgrade without it being root proofed....you'd loose root.

Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.

giantcrazy said:
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
Click to expand...
Click to collapse
Incredible OTA Update 1.65.605.2
I'm confused to, so if you are rooted, you won't see this update? or you will see it and if you do it, you lose root? I have the stock rom, which is what I thought disabled your OTA's is this an incorrect thinking?

giantcrazy said:
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
Click to expand...
Click to collapse
The name of this post is Incredible OTA Update 1.65.605.2 so even though we are at 1.22.605.2 that is not 1.65.605.2

Thats the thing, i was rooted and did get the OTA update notifications, hit accept for the update by mistake. And the only reason why i confirmed that info is because i have it on my inc.
P.S sorry lol made a type in the title of the post, its 1.35.605.2

So if you updated as root, did you lose your Root? It is not guaranteed that you would loose it, just likely is all. I feel like they released it to break our Root, and nothing more... but maybe they fixed a few issues too... we have the same screen grounding issue the EVO had, and the recent update fixed theirs... but who knows...
EDIT: Posted an article to an outdated update. Oops...

so i assume you lost root?

Yes i did.

I haven't seen it yet. <-- OHIO

have you tried redoing root? did you loose recovery?

I havent tried redoing the root process again, but how is that going to work? isn't the root process based off of the original software? the baseband is different as well.

Haven't seen it yet either <-- Rhode Island
Didn't find any information on it either. Was their a "more info" link included with yours? as with other OTA updates. Changelog, etc.?
Better question would be, do you have a screen shot of your About Phone page (baseband, software version, etc.)

somebody who gets the update needs to upload the file so a dev can do something with it.

Back to Stock from 5.7.893

Theoretically this might work. Can you use the first backup that was made when you first rooted your phone to go back below 7.893

waffleb051 said:
Theoretically this might work. Can you use the first backup that was made when you first rooted your phone to go back below 7.893
Click to expand...
Click to collapse
You can but there are several partitions that will not be restored (cdt.bin, recovery, boot (where kernel is located), as well as the radios). As long as this is true. You cannot be complete stock or flash any updates. As of now, if you are on 5.7.893, best to stay there and wait for a compatible update maybe in the future.

open1your1eyes0 said:
You can but there are several partitions that will not be restored (cdt.bin, recovery, boot (where kernel is located), as well as the radios). As long as this is true. You cannot be complete stock or flash any updates. As of now, if you are on 5.7.893, best to stay there and wait for a compatible update maybe in the future.
Click to expand...
Click to collapse
Well i was looking around on your cheesecake leak to complete stock forum and on page 5 a person named wingrider1964 used this
http://forum.xda-developers.com/showthread.php?t=1279825
the user chose 5 and and installed cheesecake and he got the ota update to 5.8.894. I am going to pm him and see what he says. At this point i dont mind if I lose root i have a Droid Eris that i can play around with. AGAIN LOSING ROOT IS NOT A BIG DEAL lol

I just posted on another thread about 5.7.893 or any other cheesecake leaked updates. (Not to be confused with "OTA" updates as they aren't). Anyone who has a non-OTA update installed right now, is screwed for the moment. There is no way back. This is the joys of a locked bootloader. The OTA updates out there are patching known versions to the new version. So, for example, the 5.5.886->5.5.893 update patches files from 5.5.886 including the boot image. The 5.5.893->5.9.901 update then patches the 5.5.893 files including the boot image. Those updates can *ONLY* be applied to the version they are meant to update. What we need is a full update installer that doesn't care what version you're on (ideal IMO) or an update made specifically for 5.7.893 (or whatever leak you're on). That's it. Our only options.

On the plus side nothing is wrong with my phone knock on wood i just would like to be on the path for ota
I forgot i also found this http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path-3.html

What IS the scoop on "check for update is not available"?

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.

5.5.886 to OTA ICS

Last November I rooted and installed cheesecake. I don't remember what I used since that was a year ago but the info was from this site. It was done through recovery. Then when the OTA update came out in December I think it was I was never able to install it, it would fail half way through. At that time I did a lot of searching for a solution but never found one that worked. Now that ICS is rolling out I'm searching again, except now links for files are all dead and since nearly a year has passed maybe there's a better solution. When I check for OTA updates it gives me 5.5.893 and it fails half way through. Anyone have any ideas on how I can get this to ICS or at least back on track for OTA updates? It's rooted and has cheesecake and bootstrap.

MetalAZ said:
Last November I rooted and installed cheesecake. I don't remember what I used since that was a year ago but the info was from this site. It was done through recovery. Then when the OTA update came out in December I think it was I was never able to install it, it would fail half way through. At that time I did a lot of searching for a solution but never found one that worked. Now that ICS is rolling out I'm searching again, except now links for files are all dead and since nearly a year has passed maybe there's a better solution. When I check for OTA updates it gives me 5.5.893 and it fails half way through. Anyone have any ideas on how I can get this to ICS or at least back on track for OTA updates? It's rooted and has cheesecake and bootstrap.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=33256361
Follow the directions in this post. Install 905 then 246. This will put you back on the OTA path.
From my EVOLVED bionic

Obsidian_soul said:
http://forum.xda-developers.com/showthread.php?p=33256361
Follow the directions in this post. Install 905 then 246. This will put you back on the OTA path.
From my EVOLVED bionic
Click to expand...
Click to collapse
Thanks. After I made my post I kept on searching and came across http://www.droidforums.net/forum/dr...install-246-ics-fxz-updated-10-24-2012-a.html which ended up working for me. It used RSDLite to install 246.

I'm just curious if you had bootstrap or safestrap installed? OTAs won't install if those, or any other mods, are on your phone. You also can't have any of the bloat removed or frozen.
Sent from my DROID BIONIC using Tapatalk 2

VS910ZVB: "LG Revolution gets bloat-removing OTA update"

From Android Central: "Updates, patches, and bug fixes are included in version VS910ZVB."
I don't have enough posts yet to link, so replace the " [dot] ":
androidcentral [dot] com/lg-revolution-gets-bloat-removing-ota-update

I have remove clock work so I can get the update. Been so long since I connected my phone to my pc to this, I will have to start from scratch. Time to search for all the how to's in here.

Haxcid said:
I have remove clock work so I can get the update. Been so long since I connected my phone to my pc to this, I will have to start from scratch. Time to search for all the how to's in here.
Click to expand...
Click to collapse
I'm rooted but without CWM (still have stock recovery). Can I simply defrost (freezing is all I've done) and get the update? Or do I have to do a hard reset to get back to full stock?
If hard reset to stock is required, any tips or techniques that you use to save time to get back to where you were? Thx.

Well I am updated and while I notice that all the extra Verizon apps are gone here is what I see...
1. Kindle, bing, slacker, tunewiki, and Verizon tones are all still installed and no option to remove them.
2, After I installed a dozen apps of my own, I still have 1gig of app space available.
3. The phone is remarkable faster and smoother.
I am going to see if they fixed the Exchange email client issue I was having...

Haxcid said:
Well I am updated and while I notice that all the extra Verizon apps are gone here is what I see...
1. Kindle, bing, slacker, tunewiki, and Verizon tones are all still installed and no option to remove them.
2, After I installed a dozen apps of my own, I still have 1gig of app space available.
3. The phone is remarkable faster and smoother.
I am going to see if they fixed the Exchange email client issue I was having...
Click to expand...
Click to collapse
Did you need to unroot? If yes how did you do it?
Thx
Mendel

mmp17 said:
Did you need to unroot? If yes how did you do it?
Thx
Mendel
Click to expand...
Click to collapse
Rooted should be ok, you may likely lose your root. It does not install with clockwork. I used lgnpst and imaged my phone, I then did a factory reset, felt like starting from scratch.
Verizon only removed a handful of apps. I am not sure it was worth the trouble. I have to root again so I can go back in and freeze or uninstall all the crap they left.
Id say in the de-bloat department they were a epic fail.

Haxcid said:
Rooted should be ok, you may likely lose your root. It does not install with clockwork. I used lgnpst and imaged my phone, I then did a factory reset, felt like starting from scratch.
Verizon only removed a handful of apps. I am not sure it was worth the trouble. I have to root again so I can go back in and freeze or uninstall all the crap they left.
Id say in the de-bloat department they were a epic fail.
Click to expand...
Click to collapse
I tried to do the update and it fails. I unrooted and it still failed if it is not worth it I'll leave it as it is. let us know if this update can be rooted.
Thx
Mendel

mmp17 said:
I tried to do the update and it fails. I unrooted and it still failed if it is not worth it I'll leave it as it is. let us know if this update can be rooted.
Thx
Mendel
Click to expand...
Click to collapse
yeah I returned my phone to stock with the lg tool and tot file, then did a factory reset, updated, rooted again, used titanium back up to uninstall the rest of the bloat Verizon missed.

While I do not know if the update breaks root or not, you can use the root tool in the dev section (esteem root v2) to root your phone. It works like a charm.

So was anything else updated? Trying to decide if it's worth my time to bother with. I am already running a zv9 that I seriously debloated and tweaked to where it's useable.
Sent from my VS910 4G using xda app-developers app

me too. I am running zv9 with root. And uninstalled lots of useless apps for me. I tried update, but failed.
wslguy said:
So was anything else updated? Trying to decide if it's worth my time to bother with. I am already running a zv9 that I seriously debloated and tweaked to where it's useable.
Sent from my VS910 4G using xda app-developers app
Click to expand...
Click to collapse

It will rebloat your phone. While they did patch some things, my phone did actually run smoother. I did have to root it again and un-install all the bloat they left, vzw tones, navigator, city id, kindle, slacker, etc...
No better battery life and not much of a performance increase. Id wait if you are happy.

keeps trying to update
I was planning on rooting & putting BrokenOut ROM on my revo when my contract ended. Then this OTA update came out, and I was worried that it would prevent that. So, I rooted the phone and put CWM recovery on and did a backup. As expected, the OTA update failed.
But, it hasn't given up. It tries and tries, about once a day. I hear my phone chirp, and it has rebooted and drained the battery, and shows at various times either the "update failed" screen, or the "updating in 2 minutes" screen, or recovery. When I get prompted to run the update, I defer it - but the deferal time doesn't correspond to when the reboot happens.
It's possible that the rooting and recovery are behind the problem, and not the update - but I suspect the update has something to do with it.
So, what I'd like to know is:
1) if I get the update, can I still use ROM Manager to change the recovery back to CWM, and still be able to flash BO on it?
2) to get the update, is it safe to just use ROM Manager to put the stock recovery on it, then run the update? I haven't done any debloating or other rooty stuff not mentioned above. I'd rather not lose data by reset, tot, etc.
3) can I fix my problem without getting the update? Maybe one of the options on the "update failed" screen? I'm not sure if I've selected only "OK" or only "Cancel" so far - or what those are supposed to mean.
4) do the security updates make zvb better than BO? (Does anyone here no what the security updates are?)
Thanks...

Broken out is based off of V9, so unless there are updates to the radio, you will most likely over-write most, if not all, of the updates.
As posted earlier, someone has rooted and installed cwm. But, someone wants to post up the update (you can rip it from the /data/local/tmp directory, iirc) I will try my best to update BO. Also, if someone can do a backup of the new update and post it up, (not the blob crap, the other one ) I'll rip the kernel and post a flashable zip. Maybe they did fix something. We will see.

I.M.famous XMAN said:
Broken out is based off of V9, so unless there are updates to the radio, you will most likely over-write most, if not all, of the updates.
As posted earlier, someone has rooted and installed cwm. But, someone wants to post up the update (you can rip it from the /data/local/tmp directory, iirc) I will try my best to update BO. Also, if someone can do a backup of the new update and post it up, (not the blob crap, the other one ) I'll rip the kernel and post a flashable zip. Maybe they did fix something. We will see.
Click to expand...
Click to collapse
Yeah, I figured current BO would undo zvb, that's why I was wondering which I should go with. The update downloaded several times, but I don't see anything in /data/local/tmp. Don't know if the download failed or just didn't persist. It hasn't tried to update for the last 30 hours or so. I'm not eager to encourage it at the moment.
I see that haxcid re-rooted, but nothing about re-cwm-ing.

can't find update file(s)
I.M.famous XMAN said:
...someone wants to post up the update (you can rip it from the /data/local/tmp directory, iirc) ...
Click to expand...
Click to collapse
I rebooted my phone, and once again it prompted me to install the update. I selected "defer" and then checked settings / about phone / software update / status which says "Package downloaded successfully".
However, /data/local/tmp is still an empty directory, according to ES File Explorer.

That's where the file was stored for v7, v8, and v9. Maybe they changed it for this update. IDK. I'll look into it. No worries. It's all good.

I think it gets downloaded to /cache/fota, but deleted once the process finishes failing. I will try to trigger it again and copy it before the phone reboots. I was not given the defer option this time.
---------- Post added at 01:31 PM ---------- Previous post was at 01:09 PM ----------
OrangeJoe said:
I think it gets downloaded to /cache/fota, but deleted once the process finishes failing. I will try to trigger it again and copy it before the phone reboots. I was not given the defer option this time.
Click to expand...
Click to collapse
Ok, I got it, I think. It's called ipth_package.bin
For now, I'm going to skip trying to attach it, and just give the link from which it seems to download:
https : / / pvzwmdmcdn.vzw.motive.com/firmware/LG_VS910_ZV9_TO_ZVB.bin
~47 MB

OrangeJoe said:
I think it gets downloaded to /cache/fota, but deleted once the process finishes failing. I will try to trigger it again and copy it before the phone reboots. I was not given the defer option this time.
---------- Post added at 01:31 PM ---------- Previous post was at 01:09 PM ----------
Ok, I got it, I think. It's called ipth_package.bin
For now, I'm going to skip trying to attach it, and just give the link from which it seems to download:
https : / / pvzwmdmcdn.vzw.motive.com/firmware/LG_VS910_ZV9_TO_ZVB.bin
~47 MB
Click to expand...
Click to collapse
Is it weird that my phone never prompted me for the OTA? I am on BO 2.0.1 with ZV9

dbeauch said:
Is it weird that my phone never prompted me for the OTA? I am on BO 2.0.1 with ZV9
Click to expand...
Click to collapse
Not really. I believe MT disabled the update feature from BO; hence the 'super fast' FC's at boot.