Every time I boot up my N5, the "Android is optimizing app..." message pops up and takes about 15 minutes to finish. I suspect this has something to do with the Dalvik Cache clearing up automatically? I'm running Cataclysm Apr-14 Stable version. I noticed this problem when I flashed the ElementalX kernel. After the flash, everytime it boots up, this happens. Any idea on what's going on/ how to fix it?
Try flashing the boot.img, stock kernel, from the factory image with fastboot. If that solved it is a kernel issue.
Sent from my Nexus 9 using XDA Free mobile app
Related
After flashing MOAR 5.01 (with a complete wipe of dalvik + cache), I go through the Aroma installer, then reboot. When booting up the phone it showed the MOAR splash page for somewhere between 15-30min. I wound up pulling the battery because I didn't wanna drain it completely.
Any idea of what could cause this?
thetestis said:
After flashing MOAR 5.01 (with a complete wipe of dalvik + cache), I go through the Aroma installer, then reboot. When booting up the phone it showed the MOAR splash page for somewhere between 15-30min. I wound up pulling the battery because I didn't wanna drain it completely.
Any idea of what could cause this?
Click to expand...
Click to collapse
An initial boot takes a long sometimes, try to boot it up again and let it sit. 10 minutes isn't too unusual.
If that still doesn't work, a factory reset in recovery should fix it.
Sent from my SCH-I535 using Tapatalk 2
after the third try I got it working.. loving MOAR.
Thanks!
Did you do anything special to get it to work? I'm currently stuck on the "android" animation boot screen, I've reflashed, reformatted, wiped, and still can't get by this screen, I've let it sit for up to 20 minutes...
Was your battery charged fully?
Sent from my SCH-I535 using xda app-developers app
thetestis said:
After flashing MOAR 5.01 (with a complete wipe of dalvik + cache), I go through the Aroma installer, then reboot. When booting up the phone it showed the MOAR splash page for somewhere between 15-30min. I wound up pulling the battery because I didn't wanna drain it completely.
Any idea of what could cause this?
Click to expand...
Click to collapse
you need to do a complete factory+data reset. not just wipe dalvik and cache. wipe system and data as well for good measure.
Hey,
I've been running several Lollipop ROMs on my Nexus 5 in the past few months.
Today my Nova Launcher suddenly stopped working and froze instantly on restart, so I rebooted the phone.
It got stuck shortly before ending the boot, after several seconds of those colored dots whizzing around the screen they froze.
This issue was reproducible, so I first cleared the Cache and Dalvik Cache and rebooted, same problem. I then tried to Fix Permissions to no avail.
I then erased System, Data, Cache and Dalvik Cache and reflashed my current L-ROM of choice, OptiPop.
The device still doesn't boot, same problem.
Now TWRP is showing an error in red font whenever I try to wipe or flash.
The error I'm getting is:
Code:
unable to stat '/data/data/com.google.android.feedback/cache/com.android.opengl.shaders_cache'
Does anyone have an idea on how to fix this?
Try reflashing TWRP and then wiping. If it still doesn't work flash the factory images from fastboot using either the script or ( optimally ) by hand one by one.
Your filesystem might have gotten corrupted well enough for TWRP not to make heads or tails of it.
If that still doesn't work search the forum for how to format the needed partitions - and triple check what you are formatting.
So every time I have dirty flashed Euphoria OS, it has frozen at the Google boot screen. This has forced me to wipe system, install the rom, install gapps, and reconfigure settings. What am I doing wrong that can't I update normally without having to wipe system?
stynatu46 said:
So every time I have dirty flashed Euphoria OS, it has frozen at the Google boot screen. This has forced me to wipe system, install the rom, install gapps, and reconfigure settings. What am I doing wrong that can't I update normally without having to wipe system?
Click to expand...
Click to collapse
What works for me is to wipe cache and davlik before I dirty flash the Rom.
Then after flashing the Rom, SuperSu......... etc wipe cache and davlik again before rebooting.
I have never had any problems dirty flashing Euphoria with this method on both Nexus 5 and Nexus 4.
One more thing. I always make sure to have the latest TWRP installed before I attempt any dirty flash.
Latest version as of this post is TWRP 2.8.5.2
joegestes said:
What works for me is to wipe cache and davlik before I dirty flash the Rom.
Then after flashing the Rom, SuperSu......... etc wipe cache and davlik again before rebooting.
I have never had any problems dirty flashing Euphoria with this method on both Nexus 5 and Nexus 4.
Click to expand...
Click to collapse
I usually do both of those things. I will say that I used ROM Installer to update it, but then dirty flashed with twrp and it still didn't work. Maybe next week I should just straight out flash with TWRP first?
Okay I just did this today and the thing STILL happens. I'd flash the update, wipe dalvik/cache, then reboot system. Then it hangs on Google boot screen for at least 10 minutes. Then I go back to TWRP, wipe system, data, cache, and flash it again and then starts to work, but all my apps are gone. Why can't I just flash the update and have it done with it instead of constantly tinkering around? Am I doing something wrong? is this what a dirty flash is?
I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Are you undervolting?
Ignore. Wrong thread.
Bump
stynatu46 said:
Okay I just did this today and the thing STILL happens. I'd flash the update, wipe dalvik/cache, then reboot system. Then it hangs on Google boot screen for at least 10 minutes. Then I go back to TWRP, wipe system, data, cache, and flash it again and then starts to work, but all my apps are gone. Why can't I just flash the update and have it done with it instead of constantly tinkering around? Am I doing something wrong? is this what a dirty flash is?
Click to expand...
Click to collapse
See if this helps.
If you have many apps, try waiting 10 minutes or longer after wiping cache/davlik before rebooting into android. Or you could try a double wipe.
Apparently, it can take quite a while for cache to clear even if TWRP shows complete.
joegestes said:
See if this helps.
If you have many apps, try waiting 10 minutes or longer after wiping cache/davlik before rebooting into android. Or you could try a double wipe.
Apparently, it can take quite a while for cache to clear even if TWRP shows complete.
Click to expand...
Click to collapse
I've tried this several times yesterday, I think I waited 20 minutes and rebooted again to do the same thing. I also don't have that many apps, I only have 4 rows filled in my app drawer
Okay everyone, I found the problem! All I had to do was uninstall the driver/app for CF.lumen before flashing because it tampered with the /system partition making it unable to boot. I then installed it again after the flash was done.
Hi all. Sometimes when I reboot my phone it will go through the process of optimizing all of my apps all over again without having wiped my cache or Dalvik cache. I did wipe my caches once to try to fix the problem however. I have also tried fixing permissions in TWRP. I understand that the phone has to optimize apps after wiping the caches. This happens at random, but it does not matter how I reboot my phone, whether it be a soft reboot, normal reboot, or completely powering the phone off and back on again.
I've experienced this when using BlissPop and CM 12.1 Nightlies. I am using the Banks GApps. I have tried using the stock kernel as well as AK Kernel with the same results regarding this issue. I would prefer to be able to use AK Kernel however. Thanks for any help!
Sent from my A0001 using XDA Free mobile app
Hi all,
I have been struggling with an issue for several months. Everytime I restart my phone the phone boots to my ROMs lock screen freezes and reboots again. Sometimes I can get my pin entered and sometimes not. Even if the phone unlocks it freezes and reboots shortly after.
I have had this issue on every ROM I have tried (Exodus, Euphoria, CM nightlies). I am currently running fastboot flashed stock COS 12.1, no root, stock recovery. My modem is current and I don't use any battery saving apps.
Has anyone experienced a similar issue?
Sent from my A0001 using Tapatalk
bucketheadmjs said:
Hi all,
I have been struggling with an issue for several months. Everytime I restart my phone the phone boots to my ROMs lock screen freezes and reboots again. Sometimes I can get my pin entered and sometimes not. Even if the phone unlocks it freezes and reboots shortly after.
I have had this issue on every ROM I have tried (Exodus, Euphoria, CM nightlies). I am currently running fastboot flashed stock COS 12.1, no root, stock recovery. My modem is current and I don't use any battery saving apps.
Has anyone experienced a similar issue?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
When flashing are you wiping properly (system, data, cache, dalvik cache)? Flashing the stock images with fastboot doesn't wipe data so unless you wiped data with TWRP first that hasn't happened and could be causing your problems.
If after trying wiping data it still doesn't work. Upload /proc/last_kmsg (dmesg from last boot) and the logcat.
Maybe we can find out what's going on by looking in the logs.
Heisenberg said:
When flashing are you wiping properly (system, data, cache, dalvik cache)? Flashing the stock images with fastboot doesn't wipe data so unless you wiped data with TWRP first that hasn't happened and could be causing your problems.
Click to expand...
Click to collapse
I didn't realize that flashing image files didn't completely overwrite the partition. I did a cache wipe today but it didn't seem to work from the stock recovery.
I have data encryption enabled BTW...
Sent from my A0001 using Tapatalk
Thymo said:
If after trying wiping data it still doesn't work. Upload /proc/last_kmsg (dmesg from last boot) and the logcat.
Maybe we can find out what's going on by looking in the logs.
Click to expand...
Click to collapse
I need to be rooted to provide the kernel logs and logcat correct?
Sent from my A0001 using Tapatalk
I will clean flash wiping and formatting everything this morning just to make sure and report back. Thanks for the support!!!
Sent from my A0001 using Tapatalk
Just a quick update... I took my OPO all the way back to stock using OnePlus's patch files that @Heisenberg re-posted. I did this after a full format of all the usual suspects. I then updated via OTA all the way to COS 12.1.
Prior to installing any apps I started experiencing the "double reboot" issue. I then erased and flashed both the persist image and reserve4 image.
I have since rooted, flashed twrp, and slowly begun to rebuild and test COS 12.1. So far no double reboots (which will now start to occur since I said that).
Admittedly, I don't completely understand the persist and reserve4 roles being played in all of this...
Sent from my A0001 using Tapatalk
I would like to go out on a limb and say my issue is fixed! Thanks to everyone for their help. This issue had plagued me for months through countless flashing...
Sent from my A0001 using Tapatalk
I have a quite similar issue: yesterday i restarted my Opo after activating Xposed and after reboot, the phone stuck in the lock screen (nothing works, touch ecc...). I've done a Nandroid with TWRP and after that i've made a wipe data (data partition only): now the phone starts and works as well, but if I restore the data partition it stucks in lock screen like before. Is it a battery problem too? I can upload the dmesg.log if needed.
TeoJohn92 said:
I have a quite similar issue: yesterday i restarted my Opo after activating Xposed and after reboot, the phone stuck in the lock screen (nothing works, touch ecc...). I've done a Nandroid with TWRP and after that i've made a wipe data (data partition only): now the phone starts and works as well, but if I restore the data partition it stucks in lock screen like before. Is it a battery problem too? I can upload the dmesg.log if needed.
Click to expand...
Click to collapse
Doesn't look like battery issue.Maybe caused due to xposed.
Mr.Ak said:
Doesn't look like battery issue.Maybe caused due to xposed.
Click to expand...
Click to collapse
After a clean flash, the phone worked smoothly for a whole day; but last night it restarted and began to reboot and lock on the unlock screen. (After the clean installation, I restored the apps and data via Titanium and the old Nandroid Backup). Now I'm installing a new rom, I'll see if the problem persists. Have no idea how this problem occurs.