If I let my Nexus 10 update to 4.2.2 when it has downloaded an goes to reboot, it displays an Android on it's back with a red error triangle, then after a few minutes reboots back to 4.2.1. This happens every time. I have never rooted the device, what are my options?
Hello
I was on 4.2.2 stock, not root when I received ota. After upgrade I stuck in the X boot loop.
If I try to install the 4.3 with fastboot I've the same result
If I restore the 4.2.2 with fastboot I haven't any problem
Please help me, I don't know what its happening with my phone
Best regards
Enviado desde mi GT-P6810 usando Tapatalk 2
I have same problem , started my OTA 4.3 upgrade 40mins back . My phone keeps restarting with "installing system update ". Any idea how can i stop this ?
Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
deusfaux said:
Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
Click to expand...
Click to collapse
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.
oneguy77 said:
I have same problem , started my OTA 4.3 upgrade 40mins back . My phone keeps restarting with "installing system update ". Any idea how can i stop this ?
Click to expand...
Click to collapse
Exact same problem with N4. Have ota'd Galaxy Nexus and Nexus 7 no problems...
________________________
Update:
After waiting about 10-15 mins I eventually reset the phone by holding down the power button for 10 secs. It then moved to the "updating apps" screen and eventually rebooted to the Nexus "X" logo. But it hung at it the X logo for about 15 mins. I again lost patience and restarted again. It finally booted all the way up to the lock screen. I now have 4.3 and it seems to be running fine...
Just wanted to share my experience as I had the same problem. It kept saying 'installing system update...' in a loop. Then I pressed the power button. It got turned off. I turned it back on and it got stuck at X logo.
Then I booted it up in recovery mode. It again said installing system update but only once and then it started updating apps and all went fine.
t2dc said:
Exact same problem with N4. Have ota'd Galaxy Nexus and Nexus 7 no problems...
________________________
Update:
After waiting about 10-15 mins I eventually reset the phone by holding down the power button for 10 secs. It then moved to the "updating apps" screen and eventually rebooted to the Nexus "X" logo. But it hung at it the X logo for about 15 mins. I again lost patience and restarted again. It finally booted all the way up to the lock screen. I now have 4.3 and it seems to be running fine...
Click to expand...
Click to collapse
I have a Note 4 and I was very satisfied with the performance until a few weeks ago, an upgrade to Android 6.0.1 was downloaded and applied.
It seems the update failed and despite I'm now in Android 6.0.1, the phone is working very erratic. Sometimes it freezes for a while (10 seconds, 30, 1 minute, 2 minutes) and then just continues as normal (when it freezes for more than a minute, it goes directly to lock screen ). Sometimes it says some app or system process (touchwiz and the like) has failed and sometimes it simply reboots without any reason. I have restarted it in secure mode but there is no difference.
I have uninstalled all downloaded apps but there is no difference. I have reset it to factory defaults but keeps failing.
I have downloaded latest 6.0.1 Firmware from Sammobile and flashed it with Odin but the fail is still there.
One thing I have noticed is when I start in recovery mode (power+home+vol up), instead of the recovery menu, the android robot appears and the text installing update. It goes for a while, then crashes (robot with red triangle) and then the recovery menu appears. This happens every time I start in recovery mode so it looks like there is some update that was applied (since I have 6.0.1 instead of 5.x) but only partially.
Any help?
is there a way to revert it back to Lollipop?
Hi!
Same thing happened to me. Connect to a computer and use Samsung Smart Switch to do an emergency recovery.
But the phone will be erased.
After that, my Note 4 got even better than before!
Good luck!
Tried Emergency Recovery but phone doesn't show up in the list, so I tried Update Firmware. It told me the firmware I have would be replaced by current version (The SAME version) but I went ahead anyway. Firmware was downloaded from internet, phone booted in Download mode and Smart Switch copied the firmware to the phone, then restarted, installing... Error Message: "No Command", nothing else.
I removed battery, rebooted and error message appeared telling there was a problem with firmware update and I would need to use emergency recovery from Kies (I understand I have to use Smart Switch, no Kies). So I connected it again to Kies and opened Emergency Recovery but once again, it doesn't appear in the list. So trying again with Firmware update. If this doesn't work, I'm afraid I have a very expensive paperweight
Failed again. At 25% update, Download screen showed:
ODIN: flash write failure
A window in Smart Switch tells me something went wrong and offers me Emergency Recovery. It also tells me I have to write a recovery code if using another PC. The recovery code is blank. not a good signal.
Again, Emergency Recovery is showing nothing in the list of devices
Ok, I finally downgraded to Firmware 5.1.1 using Odin and the phone is alive again, but I don't think everything is OK. First time I tried to update the firmware with Odin, it failed at the middle of the process, just like Smart Switch did. But second time it completed the process and rebooted. I will leave it as is a few days for testing and if no issues appear, I will allow it to update OTA. In any case, if update OTA fails again, I always can go back to where I am now.
Restarting in recovery mode now shows the android guy with the blue thing spinning (no text) and after a while the fallen android guy with the danger signal and then the recovery menu. That's not what should appear. It should go directly to recovery menu, so I think it is still not 100% good.
jedikalimero said:
Ok, I finally downgraded to Firmware 5.1.1 using Odin and the phone is alive again, but I don't think everything is OK. First time I tried to update the firmware with Odin, it failed at the middle of the process, just like Smart Switch did. But second time it completed the process and rebooted. I will leave it as is a few days for testing and if no issues appear, I will allow it to update OTA. In any case, if update OTA fails again, I always can go back to where I am now.
Restarting in recovery mode now shows the android guy with the blue thing spinning (no text) and after a while the fallen android guy with the danger signal and then the recovery menu. That's not what should appear. It should go directly to recovery menu, so I think it is still not 100% good.
Click to expand...
Click to collapse
please keep posting your observations, i am on the verge of trying flashing 5.1.1 myself.
would be great to know if this resolves our issues.
Phone kept failing also with 5.1.1 so it was not a problem of the Android version. The difference is that while at first phone freezing was the regular thing and reboots were the exception, now reboots are the regular thing, so the situation is worse.
Since it was failing with 5.1.1 and the situation was not better but worse, I didn't wait anymore an installed the OTA update that obviously appeared as soon as the phone booted in 5.1.1
After the phone said it would reset itself, it didn't turn on again. I had to turn it on manually and the the installation began without any incidents. then a new OTA update appeared (this time only ~350 MB). I'm not sure if this was a new update that appeared yesterday or was already applied when mi phone updated to 6.0.1 before the problems started.
So I accepted this update and it was downloaded but then failed to install and the phone told me to contact the repair service.
So now I am just as in the beginning, with a failing phone that freezes and reboots frequently.
I went to the repair service. The guy there didn't know how to fix it an told me to send it to Madrid for repair. But I haven't sent it yet for two reasons. The phone is still under warranty (as ANY OTHER Note 4 bought in the EU), but first, he told me it would take 25 days to repair (this is Spain, you know. In UK it would take 3 days) and second, my front glass cracked so I had to take it to a repair shop to replace just the glass for 30 euros instead of the 200 euros it would have costed to replace the whole (and totally functional) screen officially. So I'm afraid they would find out the glass was replaced and take this as an excuse to void my warranty. In older models you could replace the glass and nobody would notice it, but in the Note 4 you have to break a copper heat dissipation foil that lies between the back of the screen and the metal frame in order to disassemble the phone.
jedikalimero said:
Phone kept failing also with 5.1.1 so it was not a problem of the Android version. The difference is that while at first phone freezing was the regular thing and reboots were the exception, now reboots are the regular thing, so the situation is worse.
Since it was failing with 5.1.1 and the situation was not better but worse, I didn't wait anymore an installed the OTA update that obviously appeared as soon as the phone booted in 5.1.1
After the phone said it would reset itself, it didn't turn on again. I had to turn it on manually and the the installation began without any incidents. then a new OTA update appeared (this time only ~350 MB). I'm not sure if this was a new update that appeared yesterday or was already applied when mi phone updated to 6.0.1 before the problems started.
So I accepted this update and it was downloaded but then failed to install and the phone told me to contact the repair service.
So now I am just as in the beginning, with a failing phone that freezes and reboots frequently.
Click to expand...
Click to collapse
so sad!
I have a stock moto x play whose hardware sku is XT1564. It's on android ver 5.1.1 and system version is 23.21.25.lux_lra.en.US
I have not performed any soft mods or alterations, be it root or bl unlocking.
The only thing that I would think is different than normal is that the phone is encrypted, so it asks for password whenever it boots up.
I got a notification to update to 24.74.5.en.US a few days ago and decided to try doing it today.
It downloads the update fine and when I press on the notification for it to start the update process where it says it needs to perform a reboot to update it goes into a "phone will reboot in 10 seconds" screen and when countdown finished it shows the "shutting down..." popup that appreas when you try to shutdown the phone.
Then the phone stays with that popup until it finally shutsdown like 4 minutes later on what appears to be a hard shutdown because it doesn't reboot. I have to manually power it on and then the phone starts up normally asks me for my password and about a minute after android fully loads the phone tries to shutdown again without any input. And then it just keeps doing that until I boot the phone into fastboot and try to get it to bootloader, where it shows the dead android logo with a red yield sign and promptly shutsdown. Then when I start the phone normally it shows an "update unsuccessful" screen.
Anyone have any idea what might be the problem?
I've been thinking it might be the encryption but IDK. Also I've checked the thread with the firmware versions and couldn't find mine there. Is there a way I could dump mine for backup in case I **** something up trying to get OTA to work.(without unlocking bootloader and rooting, of course)
Now the update has stopped appearing and I can't get it to recognize there being an update for this device.
Fudge!
Hi guys I kindly require your assistance concerning my Samsung A5 2016 A510F, device was running android 5.1.1 before I updated to android 7.0. Here's the reason why I updated, device was acting shaggy it would suddenly close apps during operation. for an example with error "messaging has stopped working" would close most of the apps with the same error or suddenly restarts itself especially when the battery is less than 50%.
So I then attempted to do OTA update but failed to install "error, invalid file" so I went the Odin way, Downloaded stock firmware and flashed via Odin, everything went smooth until reached the "apps optimization 40 of 40" stacked there for about 30 minutes until i decided to restart the device, upon restart the device no longer went pass the Samsung logo stacked there.
Here's what I tried to resolve the issue:
- Cleared cache
- Factory reset
On recovery screen i noticed an error about "e: failed to mount partition" I tried almost every solution I came across to on Google with no luck. I then tried flashing to this custom rom https://forum.xda-developers.com/samsung-a-series/development/rom-resurrection-remix-rr-v6-unofficial-t3765542
Installed successfully but gets stuck on "checking for software update" I reinstalled the custom ROM again but this time without the GAPPS device booted successfully to home screen, went back to TRWP this time installed the GAPPS rebooted, it went successful, however device is unusable it keeps popping error "google play services closed" every 2 seconds.
Please help, is my phone officially dead I need clarity. Your assistance will be highly appreciated thanks in advance
b0ng0s said:
Hi guys I kindly require your assistance concerning my Samsung A5 2016 A510F, device was running android 5.1.1 before I updated to android 7.0. Here's the reason why I updated, device was acting shaggy it would suddenly close apps during operation. for an example with error "messaging has stopped working" would close most of the apps with the same error or suddenly restarts itself especially when the battery is less than 50%.
So I then attempted to do OTA update but failed to install "error, invalid file" so I went the Odin way, Downloaded stock firmware and flashed via Odin, everything went smooth until reached the "apps optimization 40 of 40" stacked there for about 30 minutes until i decided to restart the device, upon restart the device no longer went pass the Samsung logo stacked there.
Here's what I tried to resolve the issue:
- Cleared cache
- Factory reset
On recovery screen i noticed an error about "e: failed to mount partition" I tried almost every solution I came across to on Google with no luck. I then tried flashing to this custom rom https://forum.xda-developers.com/samsung-a-series/development/rom-resurrection-remix-rr-v6-unofficial-t3765542
Installed successfully but gets stuck on "checking for software update" I reinstalled the custom ROM again but this time without the GAPPS device booted successfully to home screen, went back to TRWP this time installed the GAPPS rebooted, it went successful, however device is unusable it keeps popping error "google play services closed" every 2 seconds.
Please help, is my phone officially dead I need clarity. Your assistance will be highly appreciated thanks in advance
Click to expand...
Click to collapse
Hi there, I am wondering if you resolved your issue because I have exactly the same problem. Any infos would help me a lot.
Thank you