Has anyone received thus OTA yet? Google posted the images for 5.1.1 online 29 days ago, but I haven't received it yet.
Germany lte version using 5.1.1 since ca. 2 weeks or so
Translated with my own brain to English
I still have not received the Android 5.0.2 update to upgrade
I still have not received the Android 5.0.2 update to upgrade to Android 5.1.1
I have a Nexus 9 LTE that I purchased from Google. I have emailed many times. Disappointing.
stock not rooted lte nex 9 -- received the ota to 5.1.1 over two weeks ago i think - los angeles
swcampbell said:
I still have not received the Android 5.0.2 update to upgrade to Android 5.1.1
I have a Nexus 9 LTE that I purchased from Google. I have emailed many times. Disappointing.
Click to expand...
Click to collapse
Where did you email? I called them and got double-talk. So, I'll email them. It probably takes X number of calls/emails from disappointed customers before they bother to look into it.
I never got 5.02. When I initially booted the device last December, it automatically OTA'd 5.01. I was hoping I'd get an OTA that would take from to 5.1.1 from 5.01.
DonDerham said:
Where did you email? I called them and got double-talk. So, I'll email them. It probably takes X number of calls/emails from disappointed customers before they bother to look into it.
I never got 5.02. When I initially booted the device last December, it automatically OTA'd 5.01. I was hoping I'd get an OTA that would take from to 5.1.1 from 5.01.
Click to expand...
Click to collapse
Guys, this is XDA. It's pretty easy to update yourself with the factory image. No need for the ota. Just flash the bootloader, system and boot images. No lose of data either.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Guys, this is XDA. It's pretty easy to update yourself with the factory image. No need for the ota. Just flash the bootloader, system and boot images. No lose of data either.
Click to expand...
Click to collapse
No loss of data assume the bootloader is already unlocked. In my case, it's still locked. Obviously, I can back up everything and flash, but part of the reason for buying a Nexus device includes prompt OTAs.
The device downloaded and installed 5.0.2 without a hitch. On reboot, it downloaded the 5.1.1 OTA, but errored on installation. I cleared the cache, rebooted and it repeated the process with the same error result. Nexus tech support, when they hear OTA, pretty much say "we know nothing."
So, I'll backup the device as best I can, do a factory reset and try the OTA again.
Now, I can unlock the device and ADB the images manually. Why not do so? You'd have to be married to understand. This is my wife's tablet. If I unlock the bootloader or root it or do anything other than "normal" Google stuff and anything ever goes amiss, my lovely wife will complain that my tinkering has caused her Candy Crush and Facebook to malfunction.
Related
[I will not have access to my home computer for a while... obviously would be much easier just seeing stuff on there]
I recently fouled things up with my phone and just decided to start over. I thought I flashed fireball 2.17... with the latest stock Sense 4.1, but I recently noticed that if I went to software update, I was asked if I wanted the 2.17.605.2 OTA update from last fall.
I did try to install it to see what would happen and it did not complete -- when it tried to reboot my phone, it launched straight into my recovery (TWRP) and from there I did a regular system reset and was back to my phone with the update still not having run.
Anyway, now I'm confused. Am I correct that this image and this image do not seem to match up? In other words, how do I have global mode in Sense 4.0??
Or is there a ROM out there that I could have flashed that would account for this?
Honestly, I don't even care that much about 4.0 vs. 4.1. And I only rooted my phone in the first place so I could make a few minor tweaks like the three button remap, etc. Mainly I just want to make sure I'm really still getting whatever supposed "improved LTE and wi-fi connectivity" benefit came with the OTA upgrade to 4.1 last fall.
Any thoughts?
Many thanks...
samstein66 said:
[I will not have access to my home computer for a while... obviously would be much easier just seeing stuff on there]
I recently fouled things up with my phone and just decided to start over. I thought I flashed fireball 2.17... with the latest stock Sense 4.1, but I recently noticed that if I went to software update, I was asked if I wanted the 2.17.605.2 OTA update from last fall.
I did try to install it to see what would happen and it did not complete -- when it tried to reboot my phone, it launched straight into my recovery (TWRP) and from there I did a regular system reset and was back to my phone with the update still not having run.
Anyway, now I'm confused. Am I correct that this image and this image do not seem to match up? In other words, how do I have global mode in Sense 4.0??
Or is there a ROM out there that I could have flashed that would account for this?
Honestly, I don't even care that much about 4.0 vs. 4.1. And I only rooted my phone in the first place so I could make a few minor tweaks like the three button remap, etc. Mainly I just want to make sure I'm really still getting whatever supposed "improved LTE and wi-fi connectivity" benefit came with the OTA upgrade to 4.1 last fall.
Any thoughts?
Many thanks...
Click to expand...
Click to collapse
No takers on this?
Maybe it's just too stupid. But I still don't get why I have global mode in what apparently looks like Sense 4.0.
How did you flash this?, I mean what method did you use to go back like you said, I can imagine you flashed the 4.0.3 ruu and then received the update then failed
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
How did you flash this?, I mean what method did you use to go back like you said, I can imagine you flashed the 4.0.3 ruu and then received the update then failed
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Did not use ruu.
Pretty sure this is what I flashed -- http://d-h.st/trx -- I checked and still have that zip sitting in my "Android-stuff" folder on my desktop.
Also pretty sure I had global mode immediately after flashing (I noticed the global setting available that day while getting all my preferences reset and before I had even noticed the available OTA or attempted to let it run).
samstein66 said:
Did not use ruu.
Pretty sure this is what I flashed -- http://d-h.st/trx -- I checked and still have that zip sitting in my "Android-stuff" folder on my desktop.
Also pretty sure I had global mode immediately after flashing (I noticed the global setting available that day while getting all my preferences reset and before I had even noticed the available OTA or attempted to let it run).
Click to expand...
Click to collapse
this is interenting, did you had android version 4.0.4 b4 ota?
samstein66 said:
No takers on this?
Maybe it's just too stupid. But I still don't get why I have global mode in what apparently looks like Sense 4.0.
Click to expand...
Click to collapse
Is global mode not supposed to be in 4.0? Possibly a dumb question but just asking... And I got a new device off of warranty replacement and it is completely stock. Haven't messed with anything yet, just disabled pointless apps that I will not be using yet. It does have Global Mode. When my LTE wasn't working for quite sometime, I had called Verizon and told them "what happened' and they used it to update my PRL. Anyway on topic, I think global mode is officially from Verizon.
vazersecurity said:
Is global mode not supposed to be in 4.0? Possibly a dumb question but just asking... And I got a new device off of warranty replacement and it is completely stock. Haven't messed with anything yet, just disabled pointless apps that I will not be using yet. It does have Global Mode. When my LTE wasn't working for quite sometime, I had called Verizon and told them "what happened' and they used it to update my PRL. Anyway on topic, I think global mode is officially from Verizon.
Click to expand...
Click to collapse
When the phone first came out last summer, it shipped with Sense 4.0 / Android 4.03 (without global mode available even though the phone was technically capable).
Verizon / HTC pushed an OTA update about four months later that upgraded phones to Sense 4.1 / Android 4.04 (with global mode available).
Not sure if they ship with the upgrade already running now or whether they still ship with original build and then receive the OTA shortly after activation.
samstein66 said:
When the phone first came out last summer, it shipped with Sense 4.0 / Android 4.03 (without global mode available even though the phone was technically capable).
Verizon / HTC pushed an OTA update about four months later that upgraded phones to Sense 4.1 / Android 4.04 (with global mode available).
Not sure if they ship with the upgrade already running now or whether they still ship with original build and then receive the OTA shortly after activation.
Click to expand...
Click to collapse
When I bought Mt second incredible it came with 4.0.3 so i giras they arent shipping them with ir
Sent from my ADR6410LVW using xda app-developers app
samstein66 said:
When the phone first came out last summer, it shipped with Sense 4.0 / Android 4.03 (without global mode available even though the phone was technically capable).
Verizon / HTC pushed an OTA update about four months later that upgraded phones to Sense 4.1 / Android 4.04 (with global mode available).
Not sure if they ship with the upgrade already running now or whether they still ship with original build and then receive the OTA shortly after activation.
Click to expand...
Click to collapse
Ahh okay.
Simply revert to a system only restore in recovery.
Once booted into bare stock, go to mobile network settings and select LTE option.
Sent from my Incredible 4G LTE using xda premium
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
TheKog said:
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
Click to expand...
Click to collapse
I do believe it's because of the latest OTA update. I know the OTA for Verizon patched our bootloader hack that we previously had and I think the same may have happened for AT&T. You might want to check through the AT&T forums section as you have an AT&T S4 and this is the Verizon section. Hope you find what your looking for!
TheKog said:
Any advice is much appreciated.
Click to expand...
Click to collapse
I'd begin with posting in the forum applicable to your device. That being said, in about sure at&t's update was on par with ours
Sent from my Nexus 7 using Tapatalk HD
I will start by saying I've never done any updating, rooting, unlocking, etc on any Android device. I used to do some with Blackberry but I've just stayed stock with my Android devices.
I'm currently using the HTC Droid DNA and I chatted online today with an HTC support person regarding my issues. I bought my phone from an individual last year and apparently he must have unlocked the bootloader. I'm running Android Version 4.1.1 and my software # is 1.15.605.4 701RD. Apparently I've missed the last 2 updates and I don't have the option from my phone to manually check for updates. Based on my chat today with HTC there's nowhere online they will allow me to download the updates. They mentioned taking it to a Verizon store but I don't want to do that. I would really like to be able to get the newest software version. Can anyone help me get the newest updates?
abpilgrim said:
I will start by saying I've never done any updating, rooting, unlocking, etc on any Android device. I used to do some with Blackberry but I've just stayed stock with my Android devices.
I'm currently using the HTC Droid DNA and I chatted online today with an HTC support person regarding my issues. I bought my phone from an individual last year and apparently he must have unlocked the bootloader. I'm running Android Version 4.1.1 and my software # is 1.15.605.4 701RD. Apparently I've missed the last 2 updates and I don't have the option from my phone to manually check for updates. Based on my chat today with HTC there's nowhere online they will allow me to download the updates. They mentioned taking it to a Verizon store but I don't want to do that. I would really like to be able to get the newest software version. Can anyone help me get the newest updates?
Click to expand...
Click to collapse
If it's rooted, install flash image gui from play store, install twrp recovery and then flash santod040's stock rom, to bring your phone to the latest stuff
supragrom said:
If it's rooted, install flash image gui from play store, install twrp recovery and then flash santod040's stock rom, to bring your phone to the latest stuff
Click to expand...
Click to collapse
Now first thing first. Try a factory reset.. backup your data first. If that doesn't fix the issue comment and Ill tell you what to do next.
Are you trying to be on the latest firmware as it comes from HTC (Stock), or the latest firmware modified with custom options and tweaks as in a custom ROM?
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.
I'm looking to update to the november update by using adb since my phone doesn't seem to be getting the update. It's an unlocked version from Google but I use it on Verizon. Do I need to download the verizon version of the update or just the generic?
download the google AND the verizon. Flash google, then verizon over it?
Krusej23 said:
I'm looking to update to the november update by using adb since my phone doesn't seem to be getting the update. It's an unlocked version from Google but I use it on Verizon. Do I need to download the verizon version of the update or just the generic?
Click to expand...
Click to collapse
Verizon version. I just did it, for some reason it's not getting pushed out. Same situation as you, Google device VZW provider.
Pachacouti said:
download the google AND the verizon. Flash google, then verizon over it?
Click to expand...
Click to collapse
There is no reason to do that.
Thanks, I just sideloaded the November update and it worked. It looks like it's a major issue for Verizon users and the Pixel 6 and some others at launch.
Krusej23 said:
Thanks, I just sideloaded the November update and it worked. It looks like it's a major issue for Verizon users and the Pixel 6 and some others at launch.
Click to expand...
Click to collapse
Yeah I saw that on Reddit.. Easy enough to do the side load until they figure it out.
Problem after updating. So now after updating using the verizon version of the update, it's losing the connection to verizon data, calls and sms. Any ideas?
Hi all, I've got this same issue (unlocked P6 being used on VZW unable to get the Nov security update). Seems like the official guidance is to sideload the VZW version (SD1A.210817.036.A8) and then you'll be on the VZW update path. However, I'm getting an error when trying to sideload. On my phone, it says:
Code:
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update package verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
I've verified that I'm using the correct file (oriole-sd1a.210817.036.a8-factory-65854912.zip) and verified the file with the SHA-256. Any suggestions for how I might fix this?
Krusej23 said:
Problem after updating. So now after updating using the verizon version of the update, it's losing the connection to verizon data, calls and sms. Any ideas?
Click to expand...
Click to collapse
Mine did that only once. Rebooted and it's never happened again. Also by sideloading the VZW version we should then get the OTAs moving forward from what I understand.
meberko said:
Hi all, I've got this same issue (unlocked P6 being used on VZW unable to get the Nov security update). Seems like the official guidance is to sideload the VZW version (SD1A.210817.036.A8) and then you'll be on the VZW update path. However, I'm getting an error when trying to sideload. On my phone, it says:
Code:
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update package verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
I've verified that I'm using the correct file (oriole-sd1a.210817.036.a8-factory-65854912.zip) and verified the file with the SHA-256. Any suggestions for how I might fix this?
Click to expand...
Click to collapse
Are you sure it's the correct file? That looks like the full factory image and not the OTA.
Krusej23 said:
Problem after updating. So now after updating using the verizon version of the update, it's losing the connection to verizon data, calls and sms. Any ideas?
Click to expand...
Click to collapse
So you lost network connectivity completely it seems. As per the previous poster reboot and it shouldn't happen again. Same thing happened here some days ago.
bobby janow said:
Are you sure it's the correct file? That looks like the full factory image and not the OTA.
Click to expand...
Click to collapse
-_- I'm an idiot, can you tell it's been a while since I sideloaded an OTA?
Thanks for pointing that out. Sideloaded the OTA no problem.
robn30 said:
Mine did that only once. Rebooted and it's never happened again. Also by sideloading the VZW version we should then get the OTAs moving forward from what I understand.
Click to expand...
Click to collapse
I rebooted multiple times, reseated the sim card and it was still doing it randomly. Took it to Verizon and they got me a new sim card. Seems to have fixed it now. Part of it was that it didn't look like it was fully activated either. I logged in MyVerizon and it still showed my 2XL as my phone instead of the 6.
Krusej23 said:
I rebooted multiple times, reseated the sim card and it was still doing it randomly. Took it to Verizon and they got me a new sim card. Seems to have fixed it now. Part of it was that it didn't look like it was fully activated either. I logged in MyVerizon and it still showed my 2XL as my phone instead of the 6.
Click to expand...
Click to collapse
Glad it's fixed. Faulty SIM was gonna be my next option. I thought that's what mine was gonna be but luckily the reboot seems to have squared it away.
So is everyone on Verizon with an unlocked phone from Google using the Verizon version of the OTA? I've been on a locked 3XL for almost three years, so it's taking me a bit to get used to things again. I've got root working perfectly and am afraid I'm going to mess it up when I sideload the OTA.
deercreek said:
So is everyone on Verizon with an unlocked phone from Google using the Verizon version of the OTA? I've been on a locked 3XL for almost three years, so it's taking me a bit to get used to things again. I've got root working perfectly and am afraid I'm going to mess it up when I sideload the OTA.
Click to expand...
Click to collapse
I used the Verizon version cause they are my carrier. I'm not rooted but I would imagine flashing the OTA via sideload would kill root. So would flashing the factory image via fastboot.