[Solved] Android is Upgrading... Starting apps on EVERY BOOT (CM12 Lollipop) - YU Yureka General

I recently flashed the official CM12 build using recovery to my YU Yureka device.
There's a new issue that I've encountered. Everytime I boot my device , just after boot animation, "Android is upgrading... Starting apps" shows up. It does its animation for about 10 seconds to resume the boot afterwards. First of all, I don't think that is normal at all. It is expected on first boot but not on every boot. Is there any solution to this?
In general the performance has suffered a lot. The AnTuTu Benchmark scores have dropped from ~29000 in KitKat to about ~21000 for Lollipop. The interface is laggy and unresponsive at times.
I've tried cleaning the cache partition from the stock recovery menu too with no effect or change whatsoever.
(Been using the CM12 for about 8hrs + now)
EDIT: Issue resolved by factory reset from the recovery. Do make sure to take backup of all the apps and contacts before doing a factory reset. The dialog box at boot up screen is now gone.
Even though new AnTuTu scores are not as high as other users have been reporting (~32000) but around ~29000. Also, device feels more smooth and responsive.

It happened with me also!
Its normal
In the start it lags!
But after it gets settled it just a treat
If it dosent dissapear den factory reset it!

rahulsingh616 said:
It happened with me also!
Its normal
In the start it lags!
But after it gets settled it just a treat
If it dosent dissapear den factory reset it!
Click to expand...
Click to collapse
For how long have you been using this? And approximately, after how long your system was normal again?

As i finished rooting and resroring all my apps!
About 2 hours later!
Antutu score 34000+

Related

Problems after flashing

Hello everyone , until yesterday I had 0 problems with flashing ROM's ... Last night i tried to flash the newest Xylon and after i flashed it and it booted up, problems started ... My phone became so UNUSABLE that I had to pull battery out and boot into recovery - wipe - restore and continue ... Today the same thing happened when I tried to flash the newest Atom - and the same thing over again ... My recoveries are working great, since whenever I restore to them I have 0 problems ... Any1 has an idea? My recovery is purity ROM v4.4 + AK kernel purity v021. and it's working awesome ...
I had a issue with the latest version of xylon. GSM Gnex. It flashed fine then on reboot the phone kept restarting on the boot animation. Sometimes it wouldnt even make it to the boot animation. It would just restart on the google screen. Tried factory reset. Wiping the phone completely. I tried going back to stock but nothing worked. So i relocked the bootloader did a complete wipe. And now its on on its way back to samsung.
Sent from my Nexus 4 using Tapatalk 2
Thx for the answer, but my problems aren't quite like yours ... Seems that, whenever I want to flash a new ROM it slows down like hell, it takes like 3 - 5 secs to register a touch, and then another 3 - 5 secs till my phones DOES what I've pressed on ... I've got like 7.5 GB of free storage, so that shouldn't be the problem ... I've also heared about that problem with a certain "chip" - the phone gets so slow ( not really remember what the problem was ) - but my chip isn't the one that actually HAS that problem, so it's not that either ...

[Q] HTC Desire HD boots but black screen afterwards

So I have a rooted HTC desire HD with Jellytime on it. All was working great till recently when it would shut down by itself. Today after I wanted to test a new boot screen from Rom toolkit I restarted it and while the boot screen worked great after it finished I see a black screen (backlit so I know its on). I tried going to the bootloader but after I try to go to wipe cache for example it restarts by itself and it gets stuck after the boot screen... Any ideas?
ok an update seems that if I go to the recovery via down button and power it lets me do actions. All this time I went to recovery mode when phone was shut down and plugged into a power source. I did a wipe cache and now it says android is upgrading and now it finished saying starting apps. Hope it didnt get stuck there because it keeps doin the cycle animation but doesn't do anything else.. I ll leave it be for a bit like this... :/ Had to restart it by removing the battery after 20 minutes... same problem as before still...
another update... just before it goes to a black screen when the boot screen finishes an orange light appears just briefly (where the green light appears when it charges)
Wipe everything (system data cache) and install a stock-ish ROM. What happens?
bananagranola said:
Wipe everything (system data cache) and install a stock-ish ROM. What happens?
Click to expand...
Click to collapse
I flashed the rom again and wiped data and all seem to be ok now. I ll update this because I saw many people have similar problems... thanks in advance for any help!
Have the same problem.
I bought this with the problem that it keeps rebooting all the time.
I unlock the bootloader with htcdev,root with Easy Ace Tool,flashed the new cyanogenmod 11,
but did the same .
At least 3-4 rebooting before open normally.
I said that it must be ROM issue and flashed the KK-LegacyCarbon-4.4.
Did the things should be...flash the ROM and then the boo.img separately.
Now i have black screen and the only screen i am able to get is bootloader and the recovery 4EXT.
I reflased cyanogenmod back but nothing happened,any thoughts???

[Q] JellyTime gets stuck on bootanimation

Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.
You could try dirty flashing, but if that doesn't work you'll have to reflash.
bananagranola said:
You could try dirty flashing, but if that doesn't work you'll have to reflash.
Click to expand...
Click to collapse
Thanks for the tip, but it didn't help, gets stuck still on bootanimation.
Time to full wipe and flash it again then. Wipe&FlashTime
Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3
GuyInTheCorner said:
Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3
Click to expand...
Click to collapse
I did battery pull several times considering that the phone refused to shutdown even when holding the power button for 10 secs, so battery pull was needed every time.
Anyway, it's now running fine when I reflashed.
910263 said:
Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.
Click to expand...
Click to collapse
I have the same problem since a crash on opening the outlook-email App (JellyTime 4.2 R9).
I found, that the "data" partition causes the trouble when booting. Formating the "data" partition with "4ext recovery" fixes boot-freezing. But this is not an option for me as my last (working) backup is a couple of months ago (yes, I know - should backup more frequently...).
I was able to backup the up-to-date "data" partition (with 4ext recovery) but when restoring it (even on an fully wiped and updated system) boot sequence freezes again.
Any ideas???
Many thanks!
Solved the problem with the data-backup. Instead of restoring complete partition the APP "AppExtractor" works fine for restoring data of the partition backuped.
For now, system runs perfectly.
Conclusion:
If system hangs in Boot-Animation use Recovery for backup of up-to-date system. Full wipe system and install ROM of your choise. After that restore SMS, contacts, etc. with "AppExtractor". Apps should be installed from PlayStore as far as possible. "AppExtractor" allows restoring of app, data+app, data.

[Q] Infinite boot loop out of nowhere.

I was using my phone earlier today and was attempting to extract an archived file with OfficeSuite 7. I had merely 400-500 of free space available at this point. After a few attempts and cancellations due to failure to extract I decided to restart my phone. Upon restarting it continuously will vibrate, show the Samsung logo for a moment, the screen will flicker off and it loops through that process all over again indefinitely. I can access download mode and recovery mode. I tried clearing the cache through recovery and removing the battery as well as smacking around the power button but it did not fix the problem.
I'm using stock TouchWiz Android 4.1.1 partly debloated, rooted, and stock recovery (because this ROM reflashes the stock recovery after a reset if a non stock recovery is installed).
I figure a factory reset might be the fix but I would need to extract my apps, settings, and SMS/all other data and I'm not sure how to do this with the phone in this condition and without an external SD card. Maybe I could flash ClockWorkMod, do a nandroid backup, and than extract this data with Titanium Backup? Can Titanium Backup do all that I am asking (I've barely used it)? Does anyone have an idea as to what the cause of the problem is to have this suddenly happen? I'm thinking it's the power button malfunctioning. The day prior twice my phone turned itself off.
Twrp has built in file manager. Copy to sd, then to computer?
Otherwise look into ADB.
what is happening
strange I am have the same issues . from working great to now FC and rebooting . almost like it the power button malfunctioning but it is not. Its something more. I was running DocHoliday 4.3 and was great . then I tried Aamir Mod V2 UVDMD5 4.3 same great . but this morning noticed it kept rebooting for no reason . wiped reset, nothing . looped and looped . wipe/reset and re-flashed and it will only stay on for a mintue . and if sleeps will not turn it F/C as soon as I touch power button.. crazy ???
anyone having the same problems with any 4.3 ROMs ??
I'm having the problem on my S3, but I'm not on 4.3 yet....
I already had this issue once 2 weeks ago and I factory wiped and started over. Fast forward two weeks forward and it started again today. WTF?
Qverse said:
strange I am have the same issues . from working great to now FC and rebooting . almost like it the power button malfunctioning but it is not. Its something more. I was running DocHoliday 4.3 and was great . then I tried Aamir Mod V2 UVDMD5 4.3 same great . but this morning noticed it kept rebooting for no reason . wiped reset, nothing . looped and looped . wipe/reset and re-flashed and it will only stay on for a mintue . and if sleeps will not turn it F/C as soon as I touch power button.. crazy ???
anyone having the same problems with any 4.3 ROMs ??
Click to expand...
Click to collapse
insaneoctane said:
I'm having the problem on my S3, but I'm not on 4.3 yet....
I already had this issue once 2 weeks ago and I factory wiped and started over. Fast forward two weeks forward and it started again today. WTF?
Click to expand...
Click to collapse
Are you using TWRP? I had a similar issue, upgraded to newest TWRP 2.6.3.1 and it was fixed. Before this I tried everything, factory reset/modem upgrade/different roms.. and it wasn't working..other than a rooted touchwiz rom.
Give it a shot.. might work..
As per Perseus71:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash.

Samsung Galaxy Tab S stuck in bootloop after flashing official ROM and factory reset.

After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
AussieMouse said:
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
Click to expand...
Click to collapse
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
It worked! Thank you so very much!
And I'm not a huge fan of updating my Android devices due to past experiences, but if this happens again, I might just update it to Marshmallow.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
@ashyx
i love you man...this worked for me too...thank you...now i need to reinstall TWRP again and see what's cooking......
I had this problem recently too, with the added complexity that the "Factory Reset" option in recovery wasn't working -- it would say something like "MDM does not allow factory reset" and then just reboot.
Fixed it by directly flashing TWRP with heimdall, then booting into the new TWRP recovery, performing a factory reset, and then rebooting the OS. This time it got pass the bootloop.
i flashed new twrp for T700 it's bootloop cannot enter the twrp menu keep bootlooping ...what's the solution for this?please help
Help ME!
What are "stock firmware" and "MM"? and where to get it?
I've replaced the power button thinking it was a hardware issue but now I'm not sure. I've also installed a few different stock roms but still have the same problem. Does anyone have any insight as to what could be going wrong and what I can try to get it fixed? Thanks for any help you can give. The device is a Samsung SM T-800

Categories

Resources