I received the OTA update to software version 4.28.502.2 yesterday and it installed with zero problems. (The hardest part was dealing with the slow transfer of files as I backed up my phone before installing said update.) My phone is completely stock (running Android 5.0.2), and no root. That being said, I checked tonight to see if I was still vulnerable... and apparently I still am. The impression I got yesterday (I received the notification that an update had been downloaded, but I looked it up before I applied it to see what it was about) was that the update was to fix the vulnerabilities of my phone. I have looked, and verified, on AT&T's webpage about the update that everything matches. Two separate apps, one by Zimperium, say that I'm still vulnerable. The Zimperium app says its due to CVE-2015-3864.
Trying to find information about CVE-2015-3864 has been a pain. All I've been able to locate is this:
It is important to note all Common Vulnerabilities and Exposures (CVEs) were patched, and Google has assigned the Exodus discovery with CVE-2015-3864, so it is well aware of the problem.
Click to expand...
Click to collapse
(source)
and:
"The issue is still exploitable, despite the patches currently being shipped to Android devices," Exodus Intelligence wrote in a blog post on Aug. 13. "As of this morning, Google has notified us they have allocated the CVE [Common Vulnerabilities and Exposures] identifier CVE-2015-3864 to our report."
Click to expand...
Click to collapse
(source)
Has anyone else downloaded the OTA update, and then checked to see if they are still vulnerable and found out they were?
Attached are screenshots of the results, and my phone's software (as well as other) information that matches up to what AT&T says it should be after the update.
I have not been able to update yet due to me not being able to find the stock recovery for 4.28.502.1 (the 5.0.2 update). However I do remember reading an article recently that reported the same vulnerability that you are seeing.
ZehelSitchel said:
I have not been able to update yet due to me not being able to find the stock recovery for 4.28.502.1 (the 5.0.2 update). However I do remember reading an article recently that reported the same vulnerability that you are seeing.
Click to expand...
Click to collapse
+1
indiana99 said:
+1
Click to expand...
Click to collapse
+2
I went back to stock and got the update. Running a few of those programs it say's I'm still vulnerable as well.
.
jpeepers said:
I went back to stock and got the update. Running a few of those programs it say's I'm still vulnerable as well.
.
Click to expand...
Click to collapse
Do you have a link to the stock recovery?
GrandAdmiral said:
Do you have a link to the stock recovery?
Click to expand...
Click to collapse
No, never could find it. I RUU'd back to stock (complete start over)
.
jpeepers said:
No, never could find it. I RUU'd back to stock (complete start over)
.
Click to expand...
Click to collapse
The ruu has the Stagefright patch in it. Dated 08/26/2015
http://www.htc.com/us/support/htc-one-m8-att/news/
I installed the OTA and the Lookout Stagefright Detector says I am no longer vulnerable.
Related
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
redpoint13 said:
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
Click to expand...
Click to collapse
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Don't you love those Asus emails telling you to flash things without any indication of consequences? That's why I didn't flash the one I was pmed.
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Seems to be a firmware update today just got it
Commodore 64
buxtahuda said:
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Click to expand...
Click to collapse
So it sounds like we are guaranteed to lose root then?
GreginNH said:
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Click to expand...
Click to collapse
The biggest thing for rooting to me was being able to install/use an ad-block program.
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Does it not work downloading and flashing 9.4.2.11 from asus' site and aquiring the .13 OTA that way?
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
*EDIT: Also, sorry, didn't meant to sound like a d'bag lol just trying to make sure some poor soul doesn't do a manual update thinking rootkeeper will work for them
buxtahuda said:
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
Click to expand...
Click to collapse
Good point..lmfao wasn't really thinkn of that. Exit stage right. Lol
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
AFAIK when you manually install "OTA" root keeper does not work, and seems like others are confirming this.
I just hope someone is able to quickly find another root exploit as fast as they did for .11.
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
I noticed that as well. 1st few times I hit it twice due to the delay which would end up turning it on and then back to standby/sleep
Moothead2 said:
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
Click to expand...
Click to collapse
Yes, also noticed it. We'll see if the .13 goes back to the quicker.
Duh!
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
What are the risks of this? I want to do this myself but I'm worried.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Trying now.
*RETARDED found both
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Even if this seems to work, I would be very worried about messing up the system. The OTAs are basically a patch file, and they only contain the changed bits of system files, not the whole files. (It's using bsdiff, if anyone cares.)
What this means is, if it's patching the wrong file because you lied about your version, it will very likely mess up your system - maybe even make it unbootable until you fix it with a full update.
Now, it's possible this update doesn't touch any files which changed between .11 and. 11.1, so it would be safe. But I wouldn't assume that.
buxtahuda said:
Trying now.
Click to expand...
Click to collapse
Any news? I.e. does it work or not?
I have a rooted ATT M8 running the stock ROM. They recently released new firmware and my phone wants me to install. I can tell when they release one because I get a notice saying that "google services are running in the background."
I do NOT want the new firmware, but I can find no way to turn off the update service and it's causing my phone to reboot. I assume that installing this update will break my root. Anybody got any solutions?
I've been wrestling with this the last 2 nights as well. I also didn't want the firmware update. I also had the google services annoying me.
Here's my advice:
1. Take the firmware update
2. Reboot
3. Update SuperSU immediately (use the app itself, it will boot into TWRP and update as necessary, if you don't follow this step, your root WILL be broken, and your phone will likely get locked into a ~3minute reboot cycle).
You shouldn't be affected beyond this point, unless you're like me and your phone automatically reinstalls all the AT&T bloatware on every reboot.
Install Titanium backup and kill the update service. I think it is "Software Updates"
Then you won't have this problem. At least I don't.
lostangelintx said:
Install Titanium backup and kill the update service. I think it is "Software Updates"
Then you won't have this problem. At least I don't.
Click to expand...
Click to collapse
I use titanium backup and have looked for the service but the only one I see is called updater. And from what I can tell that's not the right one.
Hmm I haven't gotten any updates
Sent from my HTC One_M8 using Tapatalk
Alaris said:
Hmm I haven't gotten any updates
Click to expand...
Click to collapse
1.54 was the software version at release (April), then the started rolling out 1.58 in May. I haven't heard of any other updates rolling out yet, although an update to 4.4.3 or 4.4.4 is supposedly upcoming.
What version is your phone currently?
---------- Post added at 10:51 AM ---------- Previous post was at 10:44 AM ----------
jbwitt said:
I use titanium backup and have looked for the service but the only one I see is called updater. And from what I can tell that's not the right one.
Click to expand...
Click to collapse
Try what is stated in Post #7 here: http://forum.xda-developers.com/showthread.php?t=2752718
You can just "freeze" (instead of uninstall) the service if you're afraid of breaking anything.
Never mind. The poster above me answered it for you.
Ok I froze HTC dm. We will see what happens. I am running 4.4.2. Thanks everybody.
jbwitt said:
Thanks everybody.
Click to expand...
Click to collapse
There's a button for that.
redpoint73 said:
There's a button for that.
Click to expand...
Click to collapse
Mind telling me where? Nowhere do I see a thanks button. I'm not a forum expert, obviously.
Also, none of the above suggestions worked. Today, when I got home, the phone rebooted again. I believe getting on my wifi is what triggered it (like it was trying to download the new firmware again). I also tried accepting the update but that didn't solve it either. All it did was reboot the phone again when told it to install...and I'm still at 4.4.2.
EDIT: Err, never mind. I reloaded the page and the thanks buttons showed up.
jbwitt said:
none of the above suggestions worked. Today, when I got home, the phone rebooted again. I believe getting on my wifi is what triggered it (like it was trying to download the new firmware again). I also tried accepting the update but that didn't solve it either. All it did was reboot the phone again when told it to install...and I'm still at 4.4.2.
Click to expand...
Click to collapse
Interesting, it seemed to work for others. Try freezing updater, FOTA, and/or HTCdrm.
Freeze these
Updater.apk
HtcOMADM_SettingsPlugin_ATT.apk
HtcOMADM_ATT.apk
Now Available!! 5.0.1!!!
Go get your lollipop ON!!!
Hopefully this will result in some bugs squashed with CM12. I am hoping for a better modem and better Bluetooth.
Queuing up downloads now, I have two of them pending for my device
are you able to capture the updates
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
you could try taking it, then flashing the nc5 kernel through odin, and then (if someone's able to do this) get the kernel from nk4 and flash that
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
How many updates are there? What does it mean 1st update? are there more updates?
meazz1 said:
How many updates are there? What does it mean 1st update? are there more updates?
Click to expand...
Click to collapse
apparently this is a 2-part update
part 1 is a build where the last three characters are NK4. this is a kitkat ROM that was likely used to prepare for lollipop
part 2 is the actual lollipop build, OC1. i think it's 5.0.1 but i'm seeing conflicting things from the internet
for some reason verizon likes doing major updates this way (i dont think they did it for jelly bean to kitkat though). but i've had a few of their phones, they've been doing two-part updates since the original galaxy s in 2010 lol
Hey everyone! Has anyone solved the mystery of the lollipop update fail? Seems alot of us are getting the first update without any issues, but the lollipop update is failing. It gives error 402, which one person at Vz told me was an error thrown due to having root. ( I don't have root ) Any suggestions appreciated!
gsmitchell said:
Hey everyone! Has anyone solved the mystery of the lollipop update fail? Seems alot of us are getting the first update without any issues, but the lollipop update is failing. It gives error 402, which one person at Vz told me was an error thrown due to having root. ( I don't have root ) Any suggestions appreciated!
Click to expand...
Click to collapse
My update is failing as well.
I've wiped cache in recovery, wiped data and cache in download manager...
Still fails.
I was rooted at one time - not rooted anymore.
I do still get the "custom" boot screen with the padlock though...
Can someone that has taken the OC1 ota update test to see if the 4.4.2 kernel has been blacklisted by:
1. Flash the I545_NK4_Stock_Kernel.tar.md5 using Odin. The device will not boot after flashing but we are just interested to see if the kernel will successfully flash.
2. To go back to normal flash the I545_OC1_Stock_Kernel.tar.md5 also in Odin.
This is the first test to determine if a downgrade workaround will be available for those that took the OC1 ota update.
muniz_ri said:
Can someone that has taken the OC1 ota update test to see if the 4.4.2 kernel has been blacklisted by:
1. Flash the I545_NK4_Stock_Kernel.tar.md5 using Odin. The device will not boot after flashing but we are just interested to see if the kernel will successfully flash.
2. To go back to normal flash the I545_OC1_Stock_Kernel.tar.md5 also in Odin.
This is the first test to determine if a downgrade workaround will be available for those that took the OC1 ota update.
Click to expand...
Click to collapse
Nope, it fails to flash
Here is the short log from the screen:
Code:
START [224, 1440]
SYS REV CHECK FAIL[K] : Refer 1 > Binary 0
SECURE MAGICCODE CHECK FAIL : boot
Is there a stock Odin TAR for this yet?
xdabens said:
Nope, it fails to flash
Here is the short log from the screen:
Code:
START [224, 1440]
SYS REV CHECK FAIL[K] : Refer 1 > Binary 0
SECURE MAGICCODE CHECK FAIL : boot
Click to expand...
Click to collapse
Not good. The 4.4.2 kernel has been blacklisted. Thx for testing.
Successful update (in two part harmony) yesterday. Stock system. Fox-Fi still works over Wi-Fi so I'm happy. No issues except 2nd update took a loooonngg time on the red Verizon screen. Make sure your battery is full or you are plugged in. No comments on battery life as I've been able to stay charged today. Getting used to it.
Hey everyone! If you getting the 402 Error, there is a thread that might have the fix. Go to the Error 402 when updating to Lolipop? thread. I am going to try it when I get home tonight.
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
Thanks! Muniz_ri mentioned that you also captured the OC1 OTA package. I searched a lot but did not find it. Could you provide the link? Thanks again!
danielzink said:
My update is failing as well.
I've wiped cache in recovery, wiped data and cache in download manager...
Still fails.
I was rooted at one time - not rooted anymore.
I do still get the "custom" boot screen with the padlock though...
Click to expand...
Click to collapse
I had the same custom boot screen--even after unrooting. Tried using Triangle Away to reset the binary count, but the count was already at 0. So ultimately I had to re-flash the NC5 kernel via Odin to get things truly back to being recognized as stock.
Then updates started rolling in for NG6, then NK1. Finally the two-part update for Lollipop.
Sent from my SCH-I545 using XDA Free mobile app
People getting tthe 40 error did you at one time have safestrap installed? ??
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
I've always found taking out sd card then a fresh Odin back to stock then doing my updates lead me to a flawless update process every time
Guys I'm on NC5 only rooted by towelroot what do I do please?!
Downloading it now at a blistering 200 kb/s as I refuse to pay, lol.
Oh, it's on Kies, too.
Just finished update via Kies, we'll see how this runs.
Welp, Kingroot no longer works....
I'm downloading now. I honestly found that I don't really need root. I have the 4.4.4 firmware saved so assume I can go back to 4.4.4 if I want later. I'm going to grab 5.0 before it loads as well.
Mike02z said:
I'm downloading now. I honestly found that I don't really need root. I have the 4.4.4 firmware saved so assume I can go back to 4.4.4 if I want later. I'm going to grab 5.0 before it loads as well.
Click to expand...
Click to collapse
Yeah, haven't really found anything nagging that I need root for, either.
5.0.1 is a nice improvement. . Seems to run smoothly with better battery life. Be prepared to completely start fresh as you will basically be installing the new 5.0.1 OS in place of the 4.4.4. Both my phone as well as my wife's required me to run the recovery feature during the upgrade process [deleting all but my ext. SD card].
Yes! Finally! Installed and doing well !!
Any way to force the Software Update? Guess I'm not one of the ones who are eligible to download it as of yet.. just got the first preliminary software update
jbzcar said:
Welp, Kingroot no longer works....
Click to expand...
Click to collapse
Just to confirm, KingRoot doesn't work?
Do you know if we can revert back to Kitkat?
wanb1i said:
Just to confirm, KingRoot doesn't work?
Do you know if we can revert back to Kitkat?
Click to expand...
Click to collapse
Correct, I even tried the updated 4.1 version from the Xperia board and it was a no go.
I would assume we could downgrade via odin if you have the old firmware saved or downloaded, but I haven't tried,
jbzcar said:
Correct, I even tried the updated 4.1 version from the Xperia board and it was a no go.
I would assume we could downgrade via odin if you have the old firmware saved or downloaded, but I haven't tried,
Click to expand...
Click to collapse
I can also confirm KingRoot doesn't work. I tried the 4.5 version with no luck. :crying:
I will download the kitkat firmware and see if I can revert.
I'll keep you posted.
****ing unusable.
Snapchat freezes *THE ENTIRE PHONE* all while making it unbearably hot to touch.
Swiftkey hangs and has to be force closed.
wanb1i said:
I can also confirm KingRoot doesn't work. I tried the 4.5 version with no luck. :crying:
I will download the kitkat firmware and see if I can revert.
I'll keep you posted.
Click to expand...
Click to collapse
Im also curious to know if you can flash back to an earlier firmware. If you can go back to ANL1 OR AOC1, that would be awesome. Im getting mine in about 2 weeks, so this is a must-know.
I have been running 5.0.1 since this post went up. Phone has been running terrible. Guess the whole memory leak issues with lollipop is just a thing across the board. Everything takes forever to happen, and I have to restart a LOT.
Let it be noted I just updated to 5.0.1 without a factory reset. I might do a reset this weekend and see if it performs better starting from scratch on 5.0.1, instead of running previous apps on new OS.
I have all three available firmwares for the VZW Edge. I can upload them to my server tonight. Would be faster downloading then trying to fight SamMobile for them. Let me know if that would help anyone here.
it'd hep me greatly. after waiting months for lollipop for months, it arrives with a gigantic letdown. overheating, horrible battery life, lag and force crashes/apps freezing. virtually none of these problems before lollipop came about. going to back things up with Helium first, then do a factory reset and see if that improves anything before i try to see about reverting back to lollipop or just using my note 4 instead.
I get it fixed. Hang on.
Link works but site wants username and password for access
Links fixed. Sorry about that.
N915VVRU1ANL1_N915VVZW1ANL1_VZW.zip
N915VVRU1AOC2_N915VVZW1AOC2_VZW.zip
N915VVRU2BOF2_N915VVZW2BOF2_VZW.zip
Has anyone had any luck downgrading? I want to go back to KitKat, but can't seem to flash AOC2 with Odin.
I'm running the stock rom from the 7.23.502.1 RUU. Last night I received notification that an OTA update has been downloaded and ready to install. Since I'm rooted, have TWRP installed, and have deleted most of the AT&T bloatware, I know the OTA won't flash. I pretty much need to run the RUU again, flash the OTA and set up everything from scratch. I'd rather not take the time to do that right now unless this includes the Stagefright patch. I haven't read anywhere that AT&T was even going to patch the M7. Patches for the M8 & M9 started rolling out a couple of weeks ago. From what I've read, those updates were about 50MB. The file I got is 193MB. I can't find any information anywhere regarding an update coming from AT&T for the M7, be it Stagefright, Sense 7 or Android 5.1.
I did notice something odd with this download. In the past all the OTAs I received downloaded to /cache/fumo/OTAPkg.zip. The one I just received was downloaded to /sdcard/fumo/OTAPkg.zip. Probably just being paranoid, but could some sort of malware disguise itself as an OTA?
Do any of the insiders here have info on what this update includes? Also, any way to kill the reminder to install the update w/o actually installing the update? If I delete the OTAPkg.zip, any way to prevent it from downloading again until I specifically request it?
sharksfan7 said:
I'm running the stock rom from the 7.23.502.1 RUU. Last night I received notification that an OTA update has been downloaded and ready to install. Since I'm rooted, have TWRP installed, and have deleted most of the AT&T bloatware, I know the OTA won't flash. I pretty much need to run the RUU again, flash the OTA and set up everything from scratch. I'd rather not take the time to do that right now unless this includes the Stagefright patch. I haven't read anywhere that AT&T was even going to patch the M7. Patches for the M8 & M9 started rolling out a couple of weeks ago. From what I've read, those updates were about 50MB. The file I got is 193MB. I can't find any information anywhere regarding an update coming from AT&T for the M7, be it Stagefright, Sense 7 or Android 5.1.
I did notice something odd with this download. In the past all the OTAs I received downloaded to /cache/fumo/OTAPkg.zip. The one I just received was downloaded to /sdcard/fumo/OTAPkg.zip. Probably just being paranoid, but could some sort of malware disguise itself as an OTA?
Do any of the insiders here have info on what this update includes? Also, any way to kill the reminder to install the update w/o actually installing the update? If I delete the OTAPkg.zip, any way to prevent it from downloading again until I specifically request it?
Click to expand...
Click to collapse
I'm guessing it's to address the Stagefright issue. See these links:
http://forums.androidcentral.com/t-htc-one/575243-software-update-7-23-502-4-a.html
http://www.att.com/esupport/article.jsp?sid=KB420290&cv=820
Thanks for the links. I saw the androidcentral article about AT&T pushing the Stagefright patch to M8 & M9, but it didn't mention the M7. I had not seen that AT&T support page info, though. It'd be nice if that specifically stated it does patch Stagefright. At least I know it's not some sort of malware. Gonna be a few days before I have time to run the RUU so I can apply the OTA.