So I saw that Oreo update is coming in batches, so I tried to get it (by tapping check update button million times).
Suddenly, I got a update, but it is not a Oreo update.
Instead, I got another December patch, with size about 1100mb. I already had second December update, with build number N2G47H.7.12.19.
Is there supposed to be a third Dec. update?
Okay, for curious guys like me, it is an Oreo update. There's absolutely no description about it being O, but it apparently it is!
I think it's the Oreo update! I got it too (after cleaning Google Framework Services, restarting and pressing the update button a few times).
It is oreo. Surprisingly they did not mention it in the description. However, Android O was written in the notification of system update.
I have also received another update. It is downloading
It's Oreo :laugh:
Isn't deleting the framework cache bad?
Related
An interesting thing just happened to me..
I restored a CWM backup to my tablet of the original 1.016.04 I backed up.
I removed super user and CWM and checked for updates.
Update to 1.139.04 was found and I proceeded to install. During install, the update failed and tablet reset. I checked details again and tablet was now on 1.016.01 not 1.016.04. Update notification again came through and it successfully updated to 1.139.04. Reset tablet and now have update for 4.10.40. Currently downloading ...
Unusual that when the update failed it reported as having flexrom of 1.016.01 instead of .04 yet still updated to 1.139.04.
Just sharing for those interested....
You want to know what else is strange ??
Take a look at the date of all these "decrypted" interrim updates & Full 300+ MB updates.
ie.
http://forum.xda-developers.com/showpost.php?p=15694533&postcount=267
all of them... not just the above example...
... their file date is 02/09/2011 !!
AFAIK .... there were no Iconia in February .... and these updates are the recent one that recently surfaced around the forum !!
ACER -->> One F**kup management that can't properly roll out updates.
I think at this point... they have manged to confused even themselves and things have been snowballed to a point of beyond remedy !
Timestamp of the files has nothing to do when the files were built...every nightly build of CM has a timestamp of 2/29/08...and if you build a ROM with dsixda's kitchen they get stamped 2/09/11...
Took an OTA update this AM in the US, but nothing seemed to change. Switched back to stock recovery, took update, downloaded, installed (no errors), rebooted, message said somethings about a Pre-Install APK, then nothing. Tablet info says I am now up to date, but nothing else seems to have changed.
I'm still on custom kernel (thor's), still on 3.1. I forget the GEN info, but I don't think that changed either.
Was this a pre-update update?
I got the update too.
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Ditto. Used stock recovery and unroot to get it to install. It's Gen 2.
Sent from my ADR6300 using XDA App
Same here, updated with no errors. Didn't lose root and it still says 3.1
With the update to 3.1 they sent out a smaller update a few days earlier. This one may be the same thing.
It's just a small update, about less than 20MB download. But I have no idea what's been changed.
GShyneDM said:
I got the update too.Same thing happaned to me
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Click to expand...
Click to collapse
Same thing happened to me...
System Update
System Update 4.010.13
(14.49MB).
A new system update is available for your device. A network connection is required to download and update your device. You may incur additional charges from your service provider. Thank you for not replacing me with the HP TouchPad.
Click to expand...
Click to collapse
i'm gonna hold off on installing this until i know more of what its all about...
I uploaded the zip in development, I don't think I'm gonna install either...
I also installed the 14MB update today. The tablet was rooted, but otherwise stock. After the update the tablet remains rooted. I have experienced no other issues.
Cheers,
A
I had the same experience as above. So far no issues.
This actually made me worried about the possibility of us to get an update to 3.2 on 8/25. Otherwise, they should just pass this incremental.
An initial update to build JWR66N and subsequent update to build JSS15J are available
Early adopters of Google's new Nexus 7 are being greeted with software updates right out of the box. The first update will automatically begin as soon as the tablet connects to WiFi for the first time, usually during the initial setup process. The tablet will shut down, boot into recovery, apply an update to bring the build number up to JWR66N, and bring the user back to the setup screen to continuing signing into a Google account.
The second update comes in a more traditional fashion: it is downloaded in the background, and then triggers a system update notification in the notification tray. Once the user accepts the update and it is applied, the build number becomes JSS15J. Both seem to be minor updates, most likely containing some system fine-tuning and bug fixes.
Source: Androidcentral
Look this pic
philos64 said:
An initial update to build JWR66N and subsequent update to build JSS15J are available
Early adopters of Google's new Nexus 7 are being greeted with software updates right out of the box. The first update will automatically begin as soon as the tablet connects to WiFi for the first time, usually during the initial setup process. The tablet will shut down, boot into recovery, apply an update to bring the build number up to JWR66N, and bring the user back to the setup screen to continuing signing into a Google account.
The second update comes in a more traditional fashion: it is downloaded in the background, and then triggers a system update notification in the notification tray. Once the user accepts the update and it is applied, the build number becomes JSS15J. Both seem to be minor updates, most likely containing some system fine-tuning and bug fixes.
Source: Androidcentral
Look this pic
Click to expand...
Click to collapse
Did you really need to make another thread about this? It's been discussed in multiple threads over the past few days at length, including work arounds for devices that are not able to process the second upgrade.
Also, the first update is <1MB and only has some minor changes. The second update is 50MB and contains significantly more.
GPS
After applying this update I can't get a gps lock. Any Ideas?
Thread closed
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
dmkozak said:
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
Click to expand...
Click to collapse
It's the first update of Google's announced security patch program. Expect frequent OS updates now to address security issues. This one patches the well publicized Stagefright MMS exploit.
That was my guess. I rarely text, or other, message, so I'm not too worried about Stagefright. My gut tells me to wait until others have installed. I have enough memory leak auto turn-off issues, that I'm afraid of making my phone worse than it is.
If Google would be so kind as to include a memory leak resolution in these updates, I'd jump all over it.
Well I had been postponing updating to Lollipop for months... (was still on 4.4.4 cuz I didn't quite like the new UI) and decided to update Sunday morning.
Big mistake.
The OTA 5.1.1 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome!
I currently can't even use my N4, and I'm trying to find a way to revert the upgrade, My 4.4.4 was rooted, and now it's not and I can't even enter Recovery mode.
Not sure if it's 100% related to your troubles, but I've been having similar random reboots lately and just general instability.
Edit: my bad, I just realized it was 5.0.1 I upgraded to.
update aug 10, 2015
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
robpoth said:
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
Click to expand...
Click to collapse
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Stevica Smederevac said:
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
ariesgodofwar said:
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
Click to expand...
Click to collapse
Yeah,you're right. Everything stock +locked bootloader for ota to work. I assumed he knew thhat part about everything stock.
Sent from my Nexus 4 using XDA Free mobile app
I have unlocked bootloader and still I updated successfully thru OTA. No problems at all.
Sent from my Nexus 4 using Tapatalk
hello i just got my 6p back from RMA today for the 3rd time , battery would not go 2 hours and microphone wouldn't work for calls, 1st 2 RMA they send me the phone back exactly as i sent it with glass screen protector still on ,they did nothing but update from MM to N to N 7.1 and then i have more issues than before where it shuts down with 20 30% remaining
i got it back today ,it was on 7.1.2 ,i tried to enter my google account , phone boots but play store will not install apps and phone hangs for 4 hours at installing apps , i shut it down but when i reboot it it says "system update in progress"
it was already on 7.1.2 , so what update?once before i sent it back for RMA and they told me don't worry that we updated it to 7.1 but it is a different version than normal OTA 7.1 that does not have the bootloop /battery issues
so is this phone trying to update to normal 7.1.2 and not the custom huawei 7.1.2 version? is it going to overwrite the different 7.1.2 version? is there any way to stop it from updating ?
why would it update i didn't select update i just shut it down after signign into my google account it singed in i got a notification on my other devices but it would not install my apps and froze at installing apps
i would like to boot it without updating is it too late? and is it bad to install the update? won't it overwrite fixed version? i take it nobody ever got to the bottom of the bootloop of death issue yet ?
long story short, got RMA phone back ,phone froze on setup , i shut it down ,then it prompted for a system update , but the phone was already on 7.1.2, i checked it before i shut it down
i want to know if this is because huawei installed a modified version of 7.1.2 and this is trying to overwrite it
i did not go to OTA i did not get any prompts for update so i do not know why i get installing update when i power on now, but i do not think it is a good idea so can i cancel this update or is it too late?
the last time i RMA'd my phone before this time they updated it to 7.1.1 and i asked about the boot loop issues with 7.1 and they told me not to worry that it reads 7.1.1 but that it is really a modified version of 7.0
so now i assume that this is a modified version of 7.1.2 that they installed on it when they sent it back and that the phone is somehow trying to update to the normal version for some reason