Hi there,
I have a Samsung Galaxy Nexus (GSM) with Jelly bean from here, and franco.Kernal nightly r240, with 384Mhz GPU. I auto-flashed it, and it got stuck on "Android is upgrading - starting apps". I've cleaned the cache and fixed permissions and it boots once but the next time I try to start it, it gets stuck again on "Android is upgrading - starting apps". I've tried installing it with CWM Recovery but it makes no difference. So do I have to clean the cache everytime I want to boot, or how do I resolve this problem? Reflashing the ROM would be my last resort.
Any help would be much appreciated.
I've re-installed my ROM without wipeing data - everything is fine with stock. Then when I flash franco.Kernal through ClockWorkMod Recovery it boots! ... but not the second time. I cleaned my cache and fixed permissions and now I'm back to step one. I'll stick with stock kernal or an old version.
Yharooer said:
I've re-installed my ROM without wipeing data - everything is fine with stock. Then when I flash franco.Kernal through ClockWorkMod Recovery it boots! ... but not the second time. I cleaned my cache and fixed permissions and now I'm back to step one. I'll stick with stock kernal or an old version.
Click to expand...
Click to collapse
hi, i am having issue also with this. have Kernal nightly r240, with 384Mhz GPU in Xenon HD v8 JB. upon reboot I get stuck. my fix is to remove battery and reboot again without any problems. I have not encountered this with other kernels. Will try to flash the rom again and wipe everything and see if the problem persist.
update; just downloaded newly realeased r241 franco kernel. No more stuck at "upgrading android".
mrm43 said:
update; just downloaded newly realeased r241 franco kernel. No more stuck at "upgrading android".
Click to expand...
Click to collapse
Same here. Thanks for the fix Franco.
For it worked the opposite
I installed r240 when it became available and had no problems with being stuck on "starting apps...", but today I installed r241 and discovered that audio jack for headphones is not functioning - if I plug in headphones or car aux it continue using built in speaker. Restarted the phone to recovery, cleaned cache and dalvik cache and upon restart I was stuck in "starting apps..." screen. Removed battery and phone booted ok, but audio jack still didn't work, so I returned back to r240 and now I can use headphones
Stuck at Android is updating starting apps .
Hi there ! How to solve this problem my phone stuck at android is upgrading starting apps after i select recovery from Rom Manager anyone can help me with this issue ? Thank You in advance
Related
Having trouble with the latest LeeDroid HD ROM have flashed many LeeDroid roms before without issue but for some reason aftering clearing all caches and running the latest rom it will install ok but on reboot it just hangs on the White HTC screen and won't boot in.
Any Ideas what could be causing it?
Currently Running LeeDroid HD v3.0.1, LeeDroid Kernel v3.1.1 radio 12.54.60.25_26.09.04.11_M2
Make sure you're deleting all data do a full factory reset (deletes all data does not actually restore to factory condition) then clear the dalvik cache, re apply the ROM make sure its CLEAN and you haven't modified it, don't apply any themes or anything, then let it boot and be patient.
Try downloading it again also it could be a corrupt download.
m3t4lh34d said:
Having trouble with the latest LeeDroid HD ROM have flashed many LeeDroid roms before without issue but for some reason aftering clearing all caches and running the latest rom it will install ok but on reboot it just hangs on the White HTC screen and won't boot in.
Any Ideas what could be causing it?
Currently Running LeeDroid HD v3.0.1, LeeDroid Kernel v3.1.1 radio 12.54.60.25_26.09.04.11_M2
Click to expand...
Click to collapse
I had similar issue few days back. But i had the Leedroid rom (same rom,kernel as urs) already runing flawlessly for a few days. It decided just to hangs at the same HTC Screen... tried to clear caches(all), hard reset, reflash same rom... still stuck same place. I finally had to flash stock 1.32 image, root all over again, etc. ... and flash Leedroid (same) again... works fine now
I got the feeling that I made my friends with their stock DHD and Iphone users drooling and jealous of my phone(csutomised with sense 3.0 stuffs), and they collectively jinxed my phone, and had this crash! lolz
btw. i flashed SAME rom i had on my sdcard, so I think the rom fine(mine at least). just something triggered that crash!
all the best...
Yea i tried reflashing from stock rom the other day loaded up one of the RUU exe's and rerooted etc and tried to reflash with no luck so i'm all out of ideas
raidenxl said:
Make sure you're deleting all data do a full factory reset (deletes all data does not actually restore to factory condition) then clear the dalvik cache, re apply the ROM make sure its CLEAN and you haven't modified it, don't apply any themes or anything, then let it boot and be patient.
Try downloading it again also it could be a corrupt download.
Click to expand...
Click to collapse
Have also done factory reset and cleared dalvik cache etc. no joy
Just managed to find a copy of LeeDroid HD V3.0.2 have installed and found it also crashes but.... it gets to the LeeDroid Android screen, little further but unfortunately still crashes
Managed to get 3.0.3 working on my DHD turns out it was just down the cwm version i had, updated to 3.0.2.5 and boom worked first time =D only problem i have had with both 3.0.1 and 3.0.3 is the camera keeps dropping out, app doesn't force close but the screen keeps going black and all buttons dissapear then all comes back... =( Atleast i'm up to date though
Any Idea's on the Cam issue?
have run logcat and noticed the following in the log
W/mm-camera( 1400): config_proc_CAMERA_STOP_SNAPSHOT: state is not correct ctrl->state = 25 W/mm-camera( 1400): VFE_RESET_ACK illegal ctrl->state 24
dunno if that makes any sense to anyone
tinkered with it a little last night didn't seem to make a difference so left it over night and for some odd reason works fine this morning i think the issue was down the camera app itself but it looks to be working fine now thankfully
UPDATE:
Ok looks like the issue is still there found out what is causing it thought, the camera works fine but...only when wifi is off, if you turn wifi back on you get the same issue as before,
Please anyone got an idea on wtf?
UPDATE2: have worked out it must be the camera app due to the fact i download a different app which appeared to work fine. Not sure why there's a glitch though
Hi there!
I installed
http://forum.xda-developers.com/showthread.php?t=1912187
with basbeand 77 instead of the recommended ones, and it appeared to work just fine for two days.
Today, I installed the LBE Guard, and so my Desire was stuck in bootloop, which I could get out of after a fullwipe and a new install.
So, then, I installed the LBE privace Master (v4.3.2738),
http://forum.xda-developers.com/showthread.php?t=1422479
because I read it was okay for JB. While configuring it, my phone crashed, and I was again stuck in a bootloop. I tried to make a fullwipe again, and a new install, but I have still these random (but appearing soon after booting) crashings and then a bootloop. It even appears when I use the Aroma Installer, but not in the CWM.
So my question is - what went wrong and more importantly, how do I get my phone to work again?
Thanks for replying.
The part with the baseband is wrong - that was my other phone.
I am quite the noob-cookie, I also have the problem with random reboots and freezes. I have been messing around with the new Nikez 4.2 Jellybean Rom, i thought that could be the reason why. But now I am also experiencing it with the old Nikez 4.1 Rom that used to be very stable for me. Anyone know a good solution? I have done several full wipes..
Cheers!
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Are you still using the same version of TWRP you used to flash slimbean 4.1? If you are trying to flash newer ROMS with an older version of TWRP, that could be causing the problem.
supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Try TWRP 2.6.1.0
Hello guys,
I have a SG2 T989 Model.
I went ahead and rooted it today, then went ahead and installed TWRP Recovery, then I went ahead and flashed a;
[Stable CM10.2 Hercules Firmware/Software.]
From here; http://download.cyanogenmod.org/?device=hercules&type=stable
Then I also went ahead and got;
GApps for CM10.2 .
Then rebooted and it turned on in Cyanogenmod.
Everything was working fine until I rebooted my phone and then the phone would turn on and show;
" Samsung" Logo and then it would dissapear very quickly and the screen would go "Blank off"
I fixed it by going back to; TWRP backing up my data files, then factory reset, wipe cache, then I installed 10.2 over again, Installed GApps then wiped dalvik Cache, then finally Rebooted.
It turned on, I setup everything again, didn't restore my files yet, tried restarting to make sure everything is okay/fine before restoring, but..... I guess not, for some unknown reason it keeps happening.
I hope someone can help me here.
malimt said:
Hello guys,
I have a SG2 T989 Model.
I went ahead and rooted it today, then went ahead and installed TWRP Recovery, then I went ahead and flashed a;
[Stable CM10.2 Hercules Firmware/Software.]
From here; http://download.cyanogenmod.org/?device=hercules&type=stable
Then I also went ahead and got;
GApps for CM10.2 .
Then rebooted and it turned on in Cyanogenmod.
Everything was working fine until I rebooted my phone and then the phone would turn on and show;
" Samsung" Logo and then it would dissapear very quickly and the screen would go "Blank off"
I fixed it by going back to; TWRP backing up my data files, then factory reset, wipe cache, then I installed 10.2 over again, Installed GApps then wiped dalvik Cache, then finally Rebooted.
It turned on, I setup everything again, didn't restore my files yet, tried restarting to make sure everything is okay/fine before restoring, but..... I guess not, for some unknown reason it keeps happening.
I hope someone can help me here.
Click to expand...
Click to collapse
Strangely enough, I have solved the issue.
CM10.2 Seems to be buggy.....
So I downloaded a stable version of CM10.1.3 and Downloaded GApps 10.1 and flashed both Via TWRP Recovery and I also had to wipe/factory reset in order to downgrade followed by Wipe Cache and Dalvik.
Then now it's rebooting perfectly fine, everything is more than fine for the past 2hours. Thank god.
I have been running CM13 for few months now. Yesterday the phone turned off and when I tried to turn it back on, it always kept on turning off once it gets to CM boot logo. Sometimes there might be few background flashes (the white circle that keeps on coming up behind sid, like normal boot) and then it would die.
I have since did a clean install with latest CM13 nightly with opengapps pico without xposed framework just to rule it being the cause of the issue. I am able to boot the first time after clean flash but if I reboot, the issue happens.
Installed fulmics 5.0 ROM for testing and it worked fine If I flash CM13 back again, the issue happens.
Tried to capture logcat by running adb logcat and turn on the phone. It still is stuck at waiting for device.
Does anyone else have issues with latest CM13?
Did you try older builds?
Just ask - Did you made full wipe?
halekhonza said:
Did you try older builds?
Just ask - Did you made full wipe?
Click to expand...
Click to collapse
The oldest build I could find is cm-13.0-20160422-NIGHTLY which I tried and same result.
Yes. wiped system, data, cache, Dalvik Cache & Internal storage partitions.