Database Users

Anyone else get a system update 10 Aug 2015?

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

Another M-N post upgrade bootloop - on completely stock 6p

Just so everyone's aware, I got this boot loop too today with the following scenario:
Completely stock 6p, upto date with latest MM, never been rooted, flashed, whatever.
Signed up for beta N programme today
Immediately got the N OTA update
Installed it - it rebooted post install but back into MM not N.
Rebooted - it got stuck on the Google logo for 30 minutes
Rebooted - permanent boot loop
I can get into the recovery menu and bootloader, and have tried sideloading the latest 7 OTA but still have the bootloop. Reset/cache clearing all tried.
Annoyingly my bootloader is locked - I've never tried doing anything other than installing standard OTA updates from Google so was unaware that unlocking it might save my bacon until it was too late.
I guess it's a phone call to Google tomorrow....
Update - sideloading this installed OK but I still have the boot loop:
6.0.1 (MTC20F) Link 5a1e93e9974908a0683a4ac8a732b81023f4b01182fd3ead3f091f54300de5ce

So all is not lost. I have an unlocked bootloader, but everything else the same as you. Doesn't really matter as I'm unable to flash anything....even updated my android SDK.
Anyway, I too signed up for Android beta program this morning, and instantly got the N update. Boom bootloop. Non stop. Most I could get it was 20 minutes after a factory reset.
What has worked for me (since 12pm today) was a factory reset and upon signing in to setup. I didn't. I set it up like it was brand new and didn't take ANY restore of apps or data from Google. I added my Gmail after and it's up and running with no reboots for 8 hours now.
It really sucks. The only thing I was able to salvage were my ringtones and notification sounds. It's like starting with a brand new phone ( froyo days without titanium backup). Google has a list of all your apps in the store but reinstalling all of them and logging in is a real pia. Been at it all day. But I do have a functioning stable Android 7.

please help 3 RMA's and counting

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

G4 Play OTA update from 6.0.1 to 7.1.1 fails

Hello,
My father has a Moto G Play (XT1602, reteu). It is currently running Android 6.0.1 with september 2017 patches. Build number is MPIS24.241-15.3-26.
The device is completely stock. No unlocked bootloaded, no custom recovery, kernel or ROM. Just a few small apps were installed.
There is a OTA system update to Android 7.1.1, build number NPI26.48-36. After downloading, it prepares for installation, reboots, and starts installing.
When the blue progress bar reaches about 40%, it stops and just says "Error". After some time the device reboots and says the upgrade failed, and no changes were made.
How can I find the cause of the failing update? How can I get the update to install successfully?

gewe said:
Hello,
My father has a Moto G Play (XT1602, reteu). It is currently running Android 6.0.1 with september 2017 patches. Build number is MPIS24.241-15.3-26.
The device is completely stock. No unlocked bootloaded, no custom recovery, kernel or ROM. Just a few small apps were installed.
There is a OTA system update to Android 7.1.1, build number NPI26.48-36. After downloading, it prepares for installation, reboots, and starts installing.
When the blue progress bar reaches about 40%, it stops and just says "Error". After some time the device reboots and says the upgrade failed, and no changes were made.
How can I find the cause of the failing update? How can I get the update to install successfully?
Click to expand...
Click to collapse
If the device is pure stock (never rooted) the problem lies with Lenovo/Moto. There is little you can do to self-address short of performing a 'factory reset' which may not (probably won't) help. Be aware all personal data will be lost.
A few tips:
- insure there is adequate free space for the update
- remove the SD card if installed
- try clearing the cache partition from stock recovery
Your best best may be to seek assistance from whatever carrier your father uses. Failures if this nature are not uncommon - especially installing a new Android version via OTA update.

I updated my phone today on 7.1.1 but my network is not working. Can't access calls/msgs. Can anyone help me?
Sent from my XT1609 using Tapatalk

zohaibkhan143 said:
I updated my phone today on 7.1.1 but my network is not working. Can't access calls/msgs. Can anyone help me?
Click to expand...
Click to collapse
Posting the SAME question in a half dozen threads does not endear you to the community or yield a faster/better response. I don't know the answer nor does anyone else here based on the lack of replies. Restore the backup you created before updating.

Davey126 said:
Posting the SAME question in a half dozen threads does not endear you to the community or yield a faster/better response. I don't know the answer nor does anyone else here based on the lack of replies. Restore the backup you created before updating.
Click to expand...
Click to collapse
The phone's bootloader is locked so I didn't make a backup now I wondering can I flash the previous rom again which is android 6.0 (241-2.35.1.17) or downgrading cause some issues?

zohaibkhan143 said:
The phone's bootloader is locked so I didn't make a backup now I wondering can I flash the previous rom again which is android 6.0 (241-2.35.1.17) or downgrading cause some issues?
Click to expand...
Click to collapse
Have no idea. Limited feedback suggest downgrading is not a smooth ride as bootloader/kernel was likely updated with the ROM. Hard brick is a possibility.

Davey126 said:
Have no idea. Limited feedback suggest downgrading is not a smooth ride as bootloader/kernel was likely updated with the ROM. Hard brick is a possibility.
Click to expand...
Click to collapse
Thanks I am expecting the same thing.

Davey126 said:
If the device is pure stock (never rooted) the problem lies with Lenovo/Moto. There is little you can do to self-address short of performing a 'factory reset' which may not (probably won't) help. Be aware all personal data will be lost.
A few tips:
- insure there is adequate free space for the update
- remove the SD card if installed
- try clearing the cache partition from stock recovery
Your best best may be to seek assistance from whatever carrier your father uses. Failures if this nature are not uncommon - especially installing a new Android version via OTA update.
Click to expand...
Click to collapse
The phone was not bought via a carrier. So the carrier will be of little help.
I collected some information from the phone:
Of the 16 GB ROM, Android uses 5,04 GB. Of the remaining 10,96 GB only 3,78 GB is used. So 7,18 GB is free. There is no SD card installed.
Of the 1,9 GB RAM on average 52% is in use. 0,9 GB is free.
Current build number is MPIS24.241-15.3-26, Android 6.0.1 with patches up to 1 September 2017.
The update has build number NPI26.48-36, Android 7.1.1.
When I was at my parents today, I forgot your last tip, about clearing the cache partition from stock recovery.. I will try to explain the instructions to my father.

I finally had a chance to clear the cache partition. Unfortunately this does not solve the problem. Installing the update still fails.

Did I brick My S7?!?

Edit: I just did a hail mary and was able to get into the recovery menu, I deleted the cache partition and.... the phone rebooted, albeit with a factory reset!!
So I'm saved by the grace of the chip Gods.
So I just got a brand new Samsung S7 32gb SM-G930T along with my wife.
I updated it via Odin v3.13.3 to Oreo 8.0
AP_G930TUVU4CRF1_CL13718910_QB18653810_REV02
BL_G930TUVU4CRF1_CL13718910_QB18653810_REV02
CP_G930TUVU4CRF1_CP9980724_CL13718910_QB18653810_REV02
CSC_TMB_G930TTMB4CRF1_CL13718910_QB18653810_REV02
Today I wanted to change it to:
AP_G930UUEU4CRG2_CL13710148_QB18808851_REV02
BL_G930UUEU4CRG2_CL13710148_QB18808851_REV02
CP_G930UUEU4CRG2_CP10090194_CL13710148_QB18808851_REV02
CSC_OYM_G930UOYM4CRG2_CL13710148_QB18808851_REV02
While doing so Odin reported fail time and time again.
Now my phone will Bootloop to blue screen with Android "Intalling System Update" then black screen flash to system recovery screen for a split second, repeat ad nauseum!
I can Volume down/Home button & Power button it into the "Warning" A custom OS can cause critical problems in phone and installed applications" the go to the download screen.
I've tried installing this stock AP program alone through Odin:
AP_G930TUVU3APG1_CL8439036_QB10212948_REV02
But that fails as well. It will NOT power off.
Any suggestions at all would be greatly appreciated and I might even mail you some chocolate!
Regards,
Claus

i ACTUALLY DID SOMETHING WORSE - BUT UNBRICKED IT (HERE'S HOW)
TheMadDane said:
Edit: I just did a hail mary and was able to get into the recovery menu, I deleted the cache partition and.... the phone rebooted, albeit with a factory reset!!
So I'm saved by the grace of the chip Gods.
So I just got a brand new Samsung S7 32gb SM-G930T along with my wife.
I updated it via Odin v3.13.3 to Oreo 8.0
AP_G930TUVU4CRF1_CL13718910_QB18653810_REV02
BL_G930TUVU4CRF1_CL13718910_QB18653810_REV02
CP_G930TUVU4CRF1_CP9980724_CL13718910_QB18653810_REV02
CSC_TMB_G930TTMB4CRF1_CL13718910_QB18653810_REV02
Today I wanted to change it to:
AP_G930UUEU4CRG2_CL13710148_QB18808851_REV02
BL_G930UUEU4CRG2_CL13710148_QB18808851_REV02
CP_G930UUEU4CRG2_CP10090194_CL13710148_QB18808851_REV02
CSC_OYM_G930UOYM4CRG2_CL13710148_QB18808851_REV02
While doing so Odin reported fail time and time again.
Now my phone will Bootloop to blue screen with Android "Intalling System Update" then black screen flash to system recovery screen for a split second, repeat ad nauseum!
I can Volume down/Home button & Power button it into the "Warning" A custom OS can cause critical problems in phone and installed applications" the go to the download screen.
I've tried installing this stock AP program alone through Odin:
AP_G930TUVU3APG1_CL8439036_QB10212948_REV02
But that fails as well. It will NOT power off.
Any suggestions at all would be greatly appreciated and I might even mail you some chocolate!
Regards,
Claus
Click to expand...
Click to collapse
What I did was worse - I was on V9 bootloader and installed Magisk (via Magisk Manager), but forgot about dm-verity. If you install Magisk without forcing dm-verity on (there is a switch in Magisk Manager for this), you will brick your Samsung device (thanks to secure boot). Fortunately, there's a fix - install a later firmware than the one you just grenaded.
SamFirm (0.3.9) to the rescue!
It let me fetch the March 12th (of this year) T-Mobile firmware for my phone (the latest full fetch). Due to my backing up regularly (to both Google AND to Samsung), I'm out exactly squat (except any apps updated since yesterday's backups - and those I fetch today via the Play Store or Samsung's own Galaxy Store.
And no - 0.3.9 is NOT a typo - the latest linked here is 0.3.6. However, version 0.3.9 is findable via Google (which is how I found it). Barring further screwups (by me) or other issues, I'll be driving the S7 for another week until I replace it with a 3a XL next week - which then will put the "Dragon" into Honorable Retirement