New OTA Update for Incredible 4g LTE 1/6/14
- Thread starter pmcall
- Start date
pretty interesting ... so next will be: 2.19.605.2 710RD ... which is of course newer than our previous 2.17.605.2, but it doesn't give much hope for the expected JB release (3.16.605.1)
main changes (as per changelog dec-2013): ISIS support, Software Update and Software Repair Tools are now compatible (?? whatever that means!!), reduced power cycling, improved bluetooth clarity and ... security patches added
that's about it. will be interesting if ANY new custom roms are going to be based on the new release (a new Viper?
) ... but i suppose we still won't get any newer kernel, any JB love and/or updated Sense(4.5) ... as nothing of that is listed in the update announcementEDIT: checked http://support.verizonwireless.com/support/system_update/droidincredible4glte.html for "benefits" (which is already updated to 2.19.605.2) and "instructions" for a hint on the size of the (this time for _real_ new OTA 2013/2014!) ... but as instructions are still based on our prev 2.17.605.2 update with its 155mb size, there isn't _any_ info yet on the size of the upcoming OTA. ........... and it seems that it was just less than 24hrs ago, when the news about the 2.19.605.2 update started to make its round in the net (and on the verizon page).
Last edited:
The viper OTA (about the faked illegal rom) has nothing to do with this
This info above is finally some news about an official OTA from Verizon! (albeit not the bigger JB update we are all still waiting for, but rather only a smaller Bugfix for our current ICS)
This info above is finally some news about an official OTA from Verizon! (albeit not the bigger JB update we are all still waiting for, but rather only a smaller Bugfix for our current ICS)
update size
according to my phone, the update is only 43.8MB.
I have now lost faith in seeing any real updates for this phone. I am ready to root and try a new ROM. What I'd like to know is if this update will break any of the methods for rooting this phone.
I know this phone isn't much, but for HTC to totally forget it like they have is rotten. I guess I'll have to follow the bandwagon to Samsung or Motorola.
according to my phone, the update is only 43.8MB.
I have now lost faith in seeing any real updates for this phone. I am ready to root and try a new ROM. What I'd like to know is if this update will break any of the methods for rooting this phone.
I know this phone isn't much, but for HTC to totally forget it like they have is rotten. I guess I'll have to follow the bandwagon to Samsung or Motorola.
it's HIGHLY LIKELY that ANY previous rooting method will not be working any more AFTER you agree to the new OTA.
@DanPFW: as for HTC, they had prepared a JB update and send it to Verizon ... it's just that Verizon didn't approve it (for some unknown to us reason!!!) ... even the release-number is known, just the actual ROM has not surfaced (yet?!) to the community.
as for rooting and a new custom-ROM ... it's a great and fun device and fairly easy to root & unlock. just that the fully working custom-roms _with_ HTC Sense are ALL only ICS4.0.4 with Sense4.1. Overclocking is easy and stable and a sweet kernel (from user: jose) is available. the newer JB-based custom-roms with Sense5 or Sense4.5 are all ported from different devices and are only partially working, as camera and bluetooth are _completely broken_ due to non-existing (Sense-kernel) drivers for JB. most ppl here are running either ViperLTE2.2.0 (best ICS with Sense4.1 imho) or some AOSP-based custom roms like CM, PacMan, Avatar etc, which are upto at least JB4.3.1 available and nicely working)
EDIT: I hope someone can capture this new OTA for 2.19.605.2 and provide the file here on xda ... for further "analysis"
Last edited:
new OTA package on my drop box
https://dl.dropboxusercontent.com/u/5271399/OTAPkg.zip
https://dl.dropboxusercontent.com/u/5271399/OTAPkg.zip
thanks for the upload ... i just checked its content, but as it's mainly patchfiles (which i dun know how to apply manually to see what's changed) i can only confirm a couple of things for now:
* according to the updater script, it's still ICS4.0.4 ... but now "fireball:4.0.4/IMM76D/278117.2" (prev was: "fireball:4.0.4/IMM76D/111397.2")
* the actual patch-content size is only 15MB!
* whole new firmware package (32MB) ... incl a slightly newer radio: 1.53.06.1009 (was: 1.53.06.0919)
waiting for some more details about the actual OTA changes from others for now :fingers-crossed:
yah I looked the update script
so the hfirware includes the radio. that mihgt make it worhthteh update IF WE CAN ROOT.
yeah and additionally one needs the (previous) 2.17.605.2 installed ... and unmodified stock-rom to apply the patches (or is there a "offline" way, like on linux or so to apply them safely w/o needing to run it on a Dinc4G). but plz correct me if i'm wrong ^^
we just shouldn't execute/load the whole firmware.zip at once as it is (right now) ... as it might re-lock the bootloader and/or in the worst case even bricks _currently_ rooted/unlocked Dinc4Gs
... that's why I said, let's wait for "the specialists" to decompose the OTA and tell the "common ppl" what can be safely applied and what better shouldn't yeah and additionally one needs the (previous) 2.17.605.2 installed ... and unmodified stock-rom to apply the patches (or is there a "offline" way, like on linux or so to apply them safely w/o needing to run it on a Dinc4G). but plz correct me if i'm wrong ^^
we just shouldn't execute/load the whole firmware.zip at once as it is (right now) ... as it might re-lock the bootloader and/or in the worst case even bricks _currently_ rooted/unlocked Dinc4Gs
i know I cant do it. that's why i posted it.
i know that the asserts nt eh script check each file (and odex) for the right hash before applying the patch.
The viper OTA (about the faked illegal rom) has nothing to do with this
This info above is finally some news about an official OTA from Verizon! (albeit not the bigger JB update we are all still waiting for, but rather only a smaller Bugfix for our current ICS)
I'm not that stupid. I run the Viper run and keep getting the download for the Verzion OTA. I thought the Viper rom was suppose to stop Vertizon OTA's, but I guess it hasn't. I just deferred it for now. Wait to see what happens with it, and if its worth while.
afaik only ViperLTE2.2.0 removed the real Verizon OTA stuff ... it still is present in Viper2.1.1
Can we install it if running viper 211? I just got the message and deferred it for now... How can I cancel it if running viper 211?
I'm pretty certain it will mess up the ROM if you run the OTA. Viper 2.2 lets you turn off the check/reminder.
you probably wont be able to install it anyway. im pretty sure it needs a stock recovery to install it. if youre running viper youre more than likely running custom recovery.
Correct... I didn't think ota updates would actually install on phones running custom rom / recoveries
to get rid of the notifications... does the old trick of changing your build.prop work? i can just use this...
also looks like viper rom has a section in build.prop...
"ro.config.venum.enableCOTA=1"... if i change that to zero i wonder if it will stop the viper illegal rom nag (that thread got closed) (and yes i'm still on viper 211 so i don't have the option in settings to disable ota updates).
also looks like viper rom has a section in build.prop...
"ro.config.venum.enableCOTA=1"... if i change that to zero i wonder if it will stop the viper illegal rom nag (that thread got closed) (and yes i'm still on viper 211 so i don't have the option in settings to disable ota updates).
Last edited:
I decided to just take this as an opportunity to finally upgrade to Viper 2.2.0. I wasn't looking forward to the full ROM install and the PITA that goes with it. Hooray for Nandroid backups and TiB!
If anyone else it thinking of doing the same, make sure you're using TWRP recovery. (Full Nandroid and full TiB backup first before doing anything!). The Aroma installer appeared to work when installing with a CWM-based recovery, but the phone hung up good upon reboot. I looked at the nice white HTC screen for quite a while :laugh:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3new OTA package on my drop box
https://dl.dropboxusercontent.com/u/5271399/OTAPkg.zip2
I just took my time today to extract all files from the previous RUU (2.17.605.2) and applied the OTA-patch (2.19.605.2) manually ... on my linux system and not on my Dinc4G ... when the upload is finished, I can provide the full new apps and changed framework (albeit not deodexed or zipaligned yet). so you guys will have a chance to at least compare the apps to the previous ones directly w/o needing to fiddle on how to apply the patches from the OTA
but as the amount of 2.17.605.2 based SENSE roms is rather limited, these files cannot be installed directly ... at least not on custom roms.
not sure about the new radio.img and/or boot.img ... if those could be updated and flashed via fastboot w/o breaking the s-off'ed & rooted system, but i assume it should be fine and otherwise restoreable via custom-recovery (for the boot.img) or adb (for both).
EDIT: link to our development section where I just posted my full patch-applied set of files, based on this 2.19.605.2 OTA:
http://xdaforums.com/showpost.php?p=49472442&postcount=5 ... all other details over there
(I hope it will simplify and help to initiate some new dev'ing for our fireball)2i modified my build.prop yesterday to try to stop the ota update... i'll post results in a few days. this method has always worked in the past. if you search you'll find plenty of info about it.
i agree with kimba99 above - i'd be really surprised if anyone start dev again on this phone i doubt this small update is worth it anyway.
if you guys want to stop it it checks for the cid and for the ro.build.fingerprint, if you change build fingerprint to anything you like youll be fine
i also noticed they added a few lines in ramsdisk for mtp, also just to confirm yes it is another kernel not depending on dxoaf stuff2
As of 01-09-2014. If you are running any nightly past that, you should already have the new firmware.
