[Q] System boot hangs with "Android is upgrading..." and "Starting apps"
I'm sure this is familiar to many, but I have yet to see a solution that is more intelligent than a simple whitewash of the apps.
I have had the same problem several times on my Nexus 10 and once on my Galaxy S2. Each time I have spent several hours looking for advice on line and poking around Android trying to find why it has hung. I seem no closer now than I ever was.
Surely someone has some insight?
I am running stock KitKat 4.4.4 KTU84P with TWRP recovery, and my strategy has been to
Wipe Dalvik cache
Wipe cache
Wipe data
Each followed by a "Fix permissions" from recovery.
I have never had any success until I reach the third step - to wipe the data partition and reinstall and reconfigure everything from scratch.
Surely there's a better way?
Related
Hey guys,
I've tried to flash DarkSide preFinal on my Atrix, now the phone is stuck on "Unlocked, Dual Core"-Screen.
Here's what I did:
Downloaded latest DarkSide and saved it to internal SD
Factory Reset via Recovery Console
Wipe Data
Wipe Cache
Wipe Dalvik Cache
Flashed the zip file
the process seemed to go through just fine, now when I'm trying to boot the phone it is stuck at the "Dual Core"-screen
Any ideas on how to solve this? I tried to factory-reset and wipe several times, still stuck
Any help is appreciated!
1. Do you have an unlocked bootloader?
2. Are you using a CWM-based recovery?
If you have answered yes to both 1 and 2 then:
3. Have you tried flashing the zip from the external SD?
4. Did you try to flash anything else after flashing the ROM while still in the same recovery session?
(If you answered "Yes" to #4 then re-flash the rom by itself and boot at least once before flashing anything else)
EDIT: Ignore question #1, I just realized you mentioned "Unlocked" on the boot logo.
rbf101 said:
Hey guys,
I've tried to flash DarkSide preFinal on my Atrix, now the phone is stuck on "Unlocked, Dual Core"-Screen.
Here's what I did:
Downloaded latest DarkSide and saved it to internal SD
Factory Reset via Recovery Console
Wipe Data
Wipe Cache
Wipe Dalvik Cache
Flashed the zip file
the process seemed to go through just fine, now when I'm trying to boot the phone it is stuck at the "Dual Core"-screen
Any ideas on how to solve this? I tried to factory-reset and wipe several times, still stuck
Any help is appreciated!
Click to expand...
Click to collapse
Thanks for the quick reply.
I reflashed with Wet Dream from the external SD (newer is always better, right? ).
Everything is working now
Seems like being a great ROM.
rbf101 said:
Hey guys,
I've tried to flash DarkSide preFinal on my Atrix, now the phone is stuck on "Unlocked, Dual Core"-Screen.
Here's what I did:
Downloaded latest DarkSide and saved it to internal SD
Factory Reset via Recovery Console
Wipe Data
Wipe Cache
Wipe Dalvik Cache
Flashed the zip file
the process seemed to go through just fine, now when I'm trying to boot the phone it is stuck at the "Dual Core"-screen
Any ideas on how to solve this? I tried to factory-reset and wipe several times, still stuck
Any help is appreciated!
Click to expand...
Click to collapse
how long did you let it sit at the loading screen?
Usually when I have boot loops, I let it sit on the loading screen for awhile(2-4 minutes). If it still doesnt boot, then I do a battery pull, and then usually after that it boots.
And if it doesn't boot just reboot into recovery mode, wipe cache, data and dalvik and reinstall the ROM again.
Sent From Rob's RP-Hybrid Atrix.
When installing any new rom, it can take a while to build up the dalvik cache again. I've had it take up to 10 min before. Best to just walk away and come back and check on it.
Guys, I desperately need help. I followed this guide to install CM7.1 nightly into my Defy and at the end I got the CM7 logo loop. Based on the guide, I took out the battery and put it back and now it's stuck at the small "Google" logo. I took out the battery again and went to the system recovery to wipe cache/factory reset. I got bunch of "mount" cache errors (command, log). I then went to the custom recovery and did the wipe cache again, this time beside "mount" cache error, there were some "open" cache errors. I did the wipe one more time and all of these errors gone. Booted it up again, and it still stuck at the "Google" screen so I went into the custom recovery trying to wipe dalvik cache as the guide said. I selected that option but nothing happened. No question asked to confirm the wipe and all it did was a short blink screen and the screen stayed the same.
Any helps would be highly appreciated !!!
That sounds a bit tricky to me, but first things first.
The first boot after installing CM7 can take a while (some minutes) since all the dalvik cache and other things has to be built. Taking out the battery during that is somewhat risky I think. After the first boot, the system starts pretty fast.
The best guess for you (at least that is what I would try) is:
go to recovery, clear dalvik cache and cache. If you have not installed CM7 before, i would also recommend to clear data as well (ok you lose you data but I hope that you were not doing it without a backup).
Then I would reflash cm7 and try again.
since you had the cm7 boot scree, I believe you have no kernel problem...
by the way, do you know what version your initial rom was?
I think it`s better to flash it from scratch:
1) Flash your previous rom with RSD
2) Root + cwm recovery
3) Cyan
(and if I were you - I would do wipe from stock recovery after 1st step and wipe from custom recovery after 3 step)
Yes, as Iddqd2 suggested just flash stock froyo using RSD Lite and then go all over for CM7 method of installation.
You dont have to say I am silly or noob or stupid, cause I know that already. This is what has happened in case someone stucks in the same situation.
Three weeks using Nexus 4 (my first smartphone and first android phone ofcourse) and I have restocked 2 times (succesful, not count the fail one). Sometimes I felt frustrated and desperate, sometimes happy like I win lottery tickets )
- I used 4.2.2 franco kernel r80, nominal CPU. It sounds crazy but I UV -200 for all frequencies (the lowest one from 900 to 700). And everything run completly normal, I have tested ASpahlt 7 for 4 hours. NO reboot. 2 days without any reboot.
- I turned off the phone to charge it. Then opened again. UV -200, but it rebooted this time.
- Bootloop.
- I have tried to flash boot.img. It passed the X, then stuck at "Upgrading apps, starting apps" or something like that, I dont remember exactly.
- Then tried to reset to stock kernel. Stuck at Upgrading again.
- I try to restore my nadroid through CWM recovery mode, but the d*** recovery said MD5 checking failed.
- I restocked to 4.2.1 by Nexus Root tool kit, option: bootloop. After finishing, it stayed at fastboot for 15 minutes (i can still choose to recovery or reboot) while the tool says wait for the device to boot or something similar. I restart manually --> still stuck at Upgrading apps. I knew something was wrong here. Restart --> bootloop
- I restocked to 4.2.2 --> bootloop. (followed this guide http://forum.xda-developers.com/showthread.php?t=2010312)
- I restocked to 4.2.1 ---> bootloop.
- I restocked to 4.2.1 by NExus Root tool kit --> bootloop.
- I restocked to 4.2.1 by fastboot again --> still bootloop.
- About to call Google for RMA.
- I have no idea why I did the following thing. I went to recovery mode (the one with the android lying with a red triangle).
- Wipe cache partition
- Wipe data/factory reset. (maybe this is what saved me)
- Reboot.
- Huray, my darling comes alive again.
- But what has happened? Would you mind explaning for me please.
When you get a boot "error" due to a great UV the first thing to do is to reflash a kernel-> wipe cache and dalvik. If it doesn't work then you should Wipe data-> cache-> dalvik and here you go.
Important: Reflashing stock images without doing a wipe cache and dalvik cache often cause a bootloop, because you have the cache of the OLD ROM on your device.
These are my experiences, i may have said a lot of bulls***s
I can't give a good explanation, only an incomplete one. But when /cache contains bad data, reflashing /system and /boot will do nothing to solve the problem. Restoring a nandroid backup would work if you didn't encounter the md5 failure. The real question is why /cache got populated with bad data.
I got stuck in a bootloop when I first rooted my phone (by flashing CWM, then installing a .zip that contained SU). Wiping /cache cleared up the problem. It seems /cache is more prone to corruption on the N4 than my previous phone.
sorcio91 said:
When you get a boot "error" due to a great UV the first thing to do is to reflash a kernel-> wipe cache and dalvik. If it doesn't work then you should Wipe data-> cache-> dalvik and here you go.
Important: Reflashing stock images without doing a wipe cache and dalvik cache often cause a bootloop, because you have the cache of the OLD ROM on your device.
These are my experiences, i may have said a lot of bulls***s
Click to expand...
Click to collapse
I did wipe the cache and davilk when I reflashed the stock kernel, but I didnt wipe the data, maybe I should try this in the first time.
Thanks for your replying I am still a fresh man, so everything has its value, no bulls___s here :good:
fenstre said:
I can't give a good explanation, only an incomplete one. But when /cache contains bad data, reflashing /system and /boot will do nothing to solve the problem. Restoring a nandroid backup would work if you didn't encounter the md5 failure. The real question is why /cache got populated with bad data.
I got stuck in a bootloop when I first rooted my phone (by flashing CWM, then installing a .zip that contained SU). Wiping /cache cleared up the problem. It seems /cache is more prone to corruption on the N4 than my previous phone.
Click to expand...
Click to collapse
Thanks for this too
I am rooting my phone. Such a long night.
my problem is that suddenly my TPT hangs and keep rebooting, it starts the system normally then it hangs for 3 sec then reboots and so on
-from CWM i did wipe data factory reset and wipe cache partition, but the problem still occurs
-i tried to restore a backup and i get this message "error while restoring /system"
-i tried to make advanced restore, all options can be restored normally except for restore system i get the above message
-the new now the tab is not rebooting and stuck at the lenovo screen
-now i tried to install CM10 ROM from my internal memory and it installs normally
-when cyanogenmod screen loading then it freezes for 3 sec and reboots again and again
any advice and suggestions will be greatly appreciated
m7mdrda said:
my problem is that suddenly my TPT hangs and keep rebooting, it starts the system normally then it hangs for 3 sec then reboots and so on
-from CWM i did wipe data factory reset and wipe cache partition, but the problem still occurs
-i tried to restore a backup and i get this message "error while restoring /system"
-i tried to make advanced restore, all options can be restored normally except for restore system i get the above message
-the new now the tab is not rebooting and stuck at the lenovo screen
-now i tried to install CM10 ROM from my internal memory and it installs normally
-when cyanogenmod screen loading then it freezes for 3 sec and reboots again and again
any advice and suggestions will be greatly appreciated
Click to expand...
Click to collapse
I'm in the same boat. Boot loop, can get into CWM recovery, but can't do anything to get it functional; factory reset, wiping cache, reflashing koshu's 0.91 build, none of these work. Only other suggestion I've seen is getting an ADB shell while in CWM and checking the partitions are not corrupt. As per this post:
http://forum.xda-developers.com/showpost.php?p=39917591&postcount=7
At the bottom of that thread there's reference to a possibly related Lenovo thread of people suffering similar problems, which was closed in Feb with a message about an extended repair program, valid until August.
It'd be a shame if it's a hardware issue, that we can't claim on because we're running custom software... you have to accept that risk when you decide to flash a custom ROM, but I don't think I'll be buying Lenovo again; mine's been repaired once already, and now this.
Hi all,
Since I tried to update my phone, I'm stuck at boot after updating apps.
Screen displays 'Launching apps' but the phone seams stuck.
I already triedd to wipe cache and dalvik cache.
I also wipe several partitions (including cache, dalvik cache, system, data) and then try again to install and boot the ROM but same result.
Finally I wiped all the partitions (cache, dalvik cache, system, data, internal data) and install ROM again but I'm still facing the problem
Then I found this thread : http://forum.xda-developers.com/galaxy-nexus/help/stuck-android-upgrading-starting-apps-t2825113
So I tried to use 'Fix permissions' option without any success.
After that, I also connected to the device with adb and execute fix_permissions.sh script provided in the thread by it doesn't work better.
Do you have any idea how to fix that?
Thanks by advance.
Have you tried sideloading another ROM and flashing to see if the issue still persists? I assume you get this after it optimizes all the Apps?
I forgot that I have no more access neither to adb nor fastboot...
I read that my last chance is LGNPST.
Do you have any recent pointers to a process to recover my phone, please?
Thanks