There have been 4 OTA updates, not including the Nougat update, since I last received one. The last update I received was in July (baseband version G930AUCU2APG1.) It isn't rooted but it's encrypted. It says everything is up to date when I check for updates on the phone. AT&T tried to push an update last night and they told me they were unable to contact my phone. I tried wiping it and checking for updates but that didn't work either. Is there a way to manually install these updates?
RustyWedges said:
There have been 4 OTA updates, not including the Nougat update, since I last received one. The last update I received was in July (baseband version G930AUCU2APG1.) It isn't rooted but it's encrypted. It says everything is up to date when I check for updates on the phone. AT&T tried to push an update last night and they told me they were unable to contact my phone. I tried wiping it and checking for updates but that didn't work either. Is there a way to manually install these updates?
Click to expand...
Click to collapse
Download the Odin pk1 files and flash with odin. After that you should be able to take the nougat update. I'm not sure if you have to decrypt your phone though or not to Odin
Related
Is there a limit to the number of times Sprint will push an OTA update to a specific phone?
I'm not receiving the MDL update anymore, and manually checking says I'm up-to-date, but I'm not being at MDC. I received it the first time and installed it, but as we all know, it broke root access and closed the motochopper exploit. So I reflashed the stock ROM and wiped everything, got the update again but ignored it. Well, I reset my phone again, and now that I actually want to install the update, Sprint doesn't seem to want to push it to my phone anymore.
Edit #1: Saw this thread: New Update is here! Here is how to force pull an OTA update. But I am still curious why Sprint isn't sending it to me automatically if anyone knows.
Edit #2: Woke up this morning and the update had been downloaded. *shrug*
Hi all,
I was running my stock 5.1.1 (LPD23.118-6.1) rom rooted for a long time and wasn't able to receive OTA updates due to the obvious reason about rooting and etc. My recovery wasn't changed. So, I saw the thread about that "flashable zips" about 6.0 roms and decided to test it. Due to some crashes and forced closes, I decided to back to my previous backup of rooted 5.1.1 stock rom. But now I want to have my phone stock as hell, and the first thing that I do was flash the most updated firmware that I found in here that was available to download. I flashed the whole LPD23.118-6.3 stock rom, a little bit newer than my old stock rooted rom. Everything working, everything fine, except...
In bootloader it says "Software status: modified", and when I try to manually check about updates, it says that my software is up to date, which I know isn't true, because OTA update of Android 6.0 is already available (i have a friend who got an X Play and he already received the ota).
How can I solve this?
Totemic_tHiRp said:
Hi all,
I was running my stock 5.1.1 (LPD23.118-6.1) rom rooted for a long time and wasn't able to receive OTA updates due to the obvious reason about rooting and etc. My recovery wasn't changed. So, I saw the thread about that "flashable zips" about 6.0 roms and decided to test it. Due to some crashes and forced closes, I decided to back to my previous backup of rooted 5.1.1 stock rom. But now I want to have my phone stock as hell, and the first thing that I do was flash the most updated firmware that I found in here that was available to download. I flashed the whole LPD23.118-6.3 stock rom, a little bit newer than my old stock rooted rom. Everything working, everything fine, except...
In bootloader it says "Software status: modified", and when I try to manually check about updates, it says that my software is up to date, which I know isn't true, because OTA update of Android 6.0 is already available (i have a friend who got an X Play and he already received the ota).
How can I solve this?
Click to expand...
Click to collapse
The force closes you got are completely normal and if you read the thread you will have found out you just need to reboot your phone until they go away.
The status modified just means your bootloader was unlocked and doesn't matter.
You have a few options, keep trying for OTA, flash another version and keep trying for OTA, sideload one of the available OTA zip files, or try a TWRP backup.
scottdanpor said:
The force closes you got are completely normal and if you read the thread you will have found out you just need to reboot your phone until they go away.
The status modified just means your bootloader was unlocked and doesn't matter.
You have a few options, keep trying for OTA, flash another version and keep trying for OTA, sideload one of the available OTA zip files, or try a TWRP backup.
Click to expand...
Click to collapse
Thanks for your reply. Actually i'm downloading the recently posted 6.0 firmware for the Brazilian/Latin American rom in firmware's thread. Unfortunately the download is very slow, but I guess I can surely update without losing anything. The only strange thing is that I didn't received any OTAs....
Totemic_tHiRp said:
Thanks for your reply. Actually i'm downloading the recently posted 6.0 firmware for the Brazilian/Latin American rom in firmware's thread. Unfortunately the download is very slow, but I guess I can surely update without losing anything. The only strange thing is that I didn't received any OTAs....
Click to expand...
Click to collapse
It's not necessary that if your friend has received the OTA then even you will receive it within few days. The OTA is rolled batch wise and no one knows which phone is in which batch except Moto of course. [emoji4]
Sent from my XT1562 using Tapatalk
This is a bit weird. When I saw that B370 is rolling out in Germany, I tried update on phone to check if update is available. Now strangest thing is, that even B330 is not showing. I'm on B180 and about month ago I received notifications that B330 is available.
I even updated to B330, didn't liked it, rolledback to B180 and even after rollback i could update to B330. Now there is no update available. Even tried with HiSuite....but nothing.
neXusSerbia said:
This is a bit weird. When I saw that B370 is rolling out in Germany, I tried update on phone to check if update is available. Now strangest thing is, that even B330 is not showing. I'm on B180 and about month ago I received notifications that B330 is available.
I even updated to B330, didn't liked it, rolledback to B180 and even after rollback i could update to B330. Now there is no update available. Even tried with HiSuite....but nothing.
Click to expand...
Click to collapse
I have the same issue! I don't know what is going on.
Now I found out that HiCare, when I started it, it asked me to update itself. So I did.
Now HiCare shows me OS early adoption update...something and when I press on it, it shows me that I can update to B370?
Weird huh? Even though regular updater doesn't show that there is an update.
neXusSerbia said:
Now I found out that HiCare, when I started it, it asked me to update itself. So I did.
Now HiCare shows me OS early adoption update...something and when I press on it, it shows me that I can update to B370?
Weird huh? Even though regular updater doesn't show that there is an update.
Click to expand...
Click to collapse
Yes , it is really weird.
I find it out guys! Just unroot and you can install the update via OTA.
I didn't rooted phone
Sent from my Huawei Honor 7
Jesus , then i really don't know how to help you..
Have you tried manually updating the phone? Try to download the b330 and then update to b370.
I found out how regular update can be done.
Just applying thru HiCare and accepting new version B370, phone updater gained access and now it is able to update B370/
Sent from my Huawei Honor 7
HiCare needs to be updated normally.
Then when setup (region and user agreement) is done it should present a new update.
Full HiSuite backup is highly recommended.
If on B180, the update should have 1.19GB if on B330 should be around 400MB.
I´ve updated manually (got errors probably due to unroot and restock recovery image) from B180 to B330 then automatically to B370.
Factory reset, format microSD, full HiSuite restore and clean as a whistle.
I notice on my phone that there is a software update coming thru. Wanted to know if this update will effect my chances of rooting in the future? Is this a good update? Should I update?
There is root now for PE1
The new update is PF2.
deleted
The PF2 update shows security patch level is July 1 on my phone.
yes, you are correct. I thought I took the update but the update failed. Don't know why.
Same thing happened to me this morning. Been trying to install it, but all I get is a 402 error message.
If anyone can let us know if root is still available after the update, that would be awesome!
Was able to root SGS7 on PF2 using guide on XDA Vz S7 Forum...
"Same thing happened to me this morning. Been trying to install it, but all I get is a 402 error message."
Try to install Smart Switch and update using it. I updated successfully by doing that.
Root works fine on PF2, I took the update and then rooted with no issues. Just use the general debloat script not the VZW specific one. However I had to use the samsung/verizon software to install the update, the OTA kept failing at 32%
Long story short, my Nexus 6P will not update to 7.0. I just got the OTA update notification today but when I downloaded it and waited forever for it to optimize my apps, my phone boots into 6.0.1. I tried getting 7.0 from the android developer program about a month ago and I was able to download it then too, but again, the phone just goes back to 6.0.1 for some reason. I decided to just wait until I get the OTA but the problem has still persisted. Any ideas on why its stuck on 6.0.1? Any way to fix this?
Also, I bought this phone about 1 and a half months ago used from eBay. It has been working perfectly fine. Just wanted to put that info out there.
It's possible you bought the phone rooted and/or with a custom ROM or recovery? If you aren't completely stock, an OTA update will fail. This isn't necessarily a single 'right' answer question, but you should probably flash the factory image for a completely fresh install. Grab the factory image at https://dl.google.com/dl/android/aosp/angler-nrd90u-factory-7c9b6a2b.zip and follow the guide, section 14 at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and you should be able to update.
I just got the 7.0 OTA myself completely stock and when it rebooted it's still on 6.0.
Nobody else is having this problem?
I think you've both misread the update info. I received MTC20L update yesterday, which said that it contains September security patches and also prepares the device for Android 7.0.
The update never claimed that your device will update to Android 7.0. But don't worry, we'll get it soon, at least I hope so!
MTC20L is the Aug security update and the factory image has been posted for 1.5 months, so odd that you're getting it now. Most people would have been receiving N OTA updates. The only way for us to guess what is going on with the OP is if he edits it to include the build number.
I also just got MTC20L yesterday.6.0.1. No idea why no 7.0. Waiting sucks..........It's been a month since "rollout".
It's true I didn't read what the update was yesterday, but I'm 95% sure it had something with "7.0" on there. How do I know what I installed yesterday? I'm on 6.0.1, with the Sept 6 security patch, and MTC20L.
MTC20F was the August update, MTC20L is September one, released 6.9.
I took the developer preview (mistake as it was a hassle that I had to fix) but remember guys, Android N updates in the background, so while it reboots to update, it doesn't take forever with the whole "android is upgrading" screen. I got the NRD90T OTA yesterday (wierd because the NRD90U is on the webpage) and later in the day I gave it a reboot just the set it straight again. I forget the actual wording but there is a secondary partition for updates so they do it in the background, and then revert back after a reboot.