Hi all,
My nexus 5 is stuck on the boot animation after a normal reboot.
I was not doing anything ROM related.
I'm in 4.4.2, rooted, TWRP and with faux kernel. But all this stuff has been working flawesly the last weeks. No relevant changes in the last days.
Last thing I did, was upgrading some xposed modules: gravitybox and others.
Just reboot to enable new versions downloaded and the phone is stuck in the boot animation.
I know that probably doing a factory reset/wipe data will solve my problem, but it has been two weeks from my last backup and I don't want to lose my last tasker stuff..... As adb is working maybe I could copy some data to the PC...
I attach my logcat, and maybe someone has any idea on the problem or howto to extract latest tasker data...
Did you change to ART instead of Dalvik because ART does not work with xposed and probably never will (per xposed announcement).
Factory reset is probably best option, or you could possibly dirty flash your ROM file again.
mistahseller said:
Did you change to ART instead of Dalvik because ART does not work with xposed and probably never will (per xposed announcement).
Factory reset is probably best option, or you could possibly dirty flash your ROM file again.
Click to expand...
Click to collapse
No changes related to ART/Dalvik
alvarezpja said:
No changes related to ART/Dalvik
Click to expand...
Click to collapse
Didnt xposed create a Xposed-Disabler-Recovery.zip when you installed it? If so, try flashing it.
just in case :good:
Flashed the zip, xposed is now disabled but the phone is still stuck on the boot animation.
I have also flashed the stock kernel just in case....
I didn't reboot in the last week so it can be any changes I make during this period...
Any guide/advice for understanding a logcat?
Fastboot erase cache. Try this entry in USB-connected fastboot.
Sent from my Nexus 5 using XDA Premium 4 mobile app
alvarezpja said:
Flashed the zip, xposed is now disabled but the phone is still stuck on the boot animation.
I have also flashed the stock kernel just in case....
I didn't reboot in the last week so it can be any changes I make during this period...
Any guide/advice for understanding a logcat?
Click to expand...
Click to collapse
Now that xposed is disabled what about factory reset/wiping cache and dalvik now?
Sent from my Nexus 5
Thanks to the guys at the tasker forum, I was able to recover some important data before the wipe.
I also pull all /data/data which was useful for example to recover my google authenticator configuration....
As expected, a factory reset was the solution.
Thanks guys for your ideas
Related
This is a flashable zip that simply returns your kernel and wireless.ko to stock GB 2.3.3 as delivered by LG in the update. This is for people who have played around with custom kernels and wish to go back to stock for whatever reason. Caveat: I have not tried the zip myself but one user has reported he has used it with success. This is a simple flash that simply replaces the boot.img and wireless.ko with the files from stock, so you should have no problems with it.
Disclaimer: I am not responsible if you brick your phone, void your warranty, or any other pain or suffering you may experience as the result of flashing this kernel.
Note: Always wipe the Dalvik Cache when flashing a new kernel. If you don't unintended consequences (i.e., boot stuck on LG logo or boot loop) may result. The first boot after flashing will take around five minutes or so. Please be patient and don't report your phone is bricked while it is still booting and rebuilding the Dalvik Cache, which takes several minutes depending on how many apps are installed.
Please report back any success or failures here.
Enjoy!
Attachments:
P999-GB-Kernel-Stock.zip (4.26 MB)
MD5: 52b1f38ff846082aed99bf8ac7fdb756
Reserved for future use by the OP.
This has been needed for a while. Thanks!
Thanks
Sent from my LG-P999 using xda premium
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
mojorisin7178 said:
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
Click to expand...
Click to collapse
This thread is for the stock kernel. Please post your question in the EB 2.1 and Trinity Kernel threads.
This is useful thanks, wish we had one for cm7.....
ONLY the D. Cache should be cleared right?
SyntekSystems said:
ONLY the D. Cache should be cleared right?
Click to expand...
Click to collapse
Yes. The Dalvik Cache is the crucial thing you need to clear when you flash any system file, kernel, etc. If you don't a bootloop or stuck boot is a likely result. If you flash a different rom then you should wipe the system also to be safe.
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
SyntekSystems said:
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
Click to expand...
Click to collapse
No reason to clear normal cache. In fact, if you use Rom Manager, that will delete the recovery it flashed as that is where it keeps it.
Hey everyone. I have a rooted HTC One S. I downloader ROM Manager and downloaded CM10. i installed it, but on startup, the CM10 boot animation just keeps going and going. the longest i let it go was close to 20 mins. I'm pretty sure tht this shouldn't be happening, any thoughts or suggestions would be nice.
have you followed all those steps: http://forum.xda-developers.com/showthread.php?t=1889339&highlight=cyanogenmod
?
most important thing is to wipe your system partition / dalvik cache.
if coming from another rom (stock or whatsoever) you need to do a factory reset too.
back up your data before, cause it will be gone then.
xXFlippyXx said:
have you followed all those steps: http://forum.xda-developers.com/showthread.php?t=1889339&highlight=cyanogenmod
?
most important thing is to wipe your system partition / dalvik cache.
if coming from another rom (stock or whatsoever) you need to do a factory reset too.
back up your data before, cause it will be gone then.
Click to expand...
Click to collapse
A wipe was all that needed to be done. The problem was ROM Manager wasnt wiping prior to installation. Thanks for the help, +1.
running cataclysm on my n5 and was changing some volume controls in gravity box, when i restarted i got system ui stopped. can i just flash cataclysm again without wiping anything to fix this? or at least get in to save some texts and data?
also factory reset on a nexus doesnt wipe the internal sd right?
First try delete gravitybox and see if things will get better or not,if not try go into recovery mode then and wipe cache,and dalvik's cache,if it's won't help you anyway then backup your apps data with Titanium Backup and make full wipe.
fergdizzle9090 said:
running cataclysm on my n5 and was changing some volume controls in gravity box, when i restarted i got system ui stopped. can i just flash cataclysm again without wiping anything to fix this? or at least get in to save some texts and data?
also factory reset on a nexus doesnt wipe the internal sd right?
Click to expand...
Click to collapse
Yes a dirty flash of the ROM should be fine
sent from my HAMMERHEAD neXus
CRIME INC. said:
Yes a dirty flash of the ROM should be fine
sent from my HAMMERHEAD neXus
Click to expand...
Click to collapse
+1
thanks i did the dirty flash and it fixed it. Simonna i wasnt able to do any of that because i had no UI
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
You can always flash the factory images here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You can flash any ROM and that should fix your issue
You will not lose your unlocked bootloader unless you flash the stock one which is in the factory images
Your bootloader will not relock unless you lock it yourself using fastboot. Flashing roms or factory images won't lock it by themselves.
And even if it somehow did, one fastboot command and you're unlocked again.
And as far as root goes....it takes 5 minutes to reroot.
So just flash whatever factory image you need and then custom recovery, and you're done. Maybe need to download superSU from play store after.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
justinisloco said:
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
Click to expand...
Click to collapse
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
xfranchize said:
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
Click to expand...
Click to collapse
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
vin4yak said:
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
xfranchize said:
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
Click to expand...
Click to collapse
Maybe your flashing a bad version of GApps since the force closes are on google Calander?
Are you using a 4.4.2 GApps?
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
gee2012 said:
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
Click to expand...
Click to collapse
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
xfranchize said:
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
gee2012 said:
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
Click to expand...
Click to collapse
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
gee2012 said:
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
Click to expand...
Click to collapse
Okay ill give it a shot, thanks alot. Ill update here if im successful.
Sent from my Nexus 5 using Tapatalk
I've got viper one rom and I'm trying to install android revolution hd. I checked the md5 and installed it with TWRP, but when the phone boots and the setup begins the first thing that appears is viper tweaks (from the viper one rom) requesting root access. Once the setup is finished a message appears saying "blinkfeed has stopped working" and then I can do absolutely nothing except power off the phone.
Shouldn't viper be removed when I wipe in TWRP?
Anyone have any idea wtf is going on?
I went from nV RLS 1.1 to RLS 2, clean flash in TWRP. When it booted my same setup was on the screen with everything force closing. I went back into TWRP attempted again, and it was still messed up. Tried to restore a backup, it failed, then TWRP started crashing. I could only get into fastboot.
Anyways, you can read my post in this section. I had to go back to stock, then restore a nandroid.
Sent from my Nexus 7 using Tapatalk
jova33 said:
I went from nV RLS 1.1 to RLS 2, clean flash in TWRP. When it booted my same setup was on the screen with everything force closing. I went back into TWRP attempted again, and it was still messed up. Tried to restore a backup, it failed, then TWRP started crashing. I could only get into fastboot.
Anyways, you can read my post in this section. I had to go back to stock, then restore a nandroid.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Were you able to successfully install RLS 2? If so how?
chobungus said:
Were you able to successfully install RLS 2? If so how?
Click to expand...
Click to collapse
I haven't yet. I want to know what went wrong the first time before I attempt it again.
Sent from your mom's smartphone
jova33 said:
I haven't yet. I want to know what went wrong the first time before I attempt it again.
Sent from your mom's smartphone
Click to expand...
Click to collapse
I actually just downloaded and installed nV RLS 2 with no problems at all.. My problem may related to the Android Revolution HD rom itself.. I'll have try to figure it out another time.
Thanks for your help!
For anyone who's interested I was able to successfully install ARHD to my phone after doing some research. Rather than just doing the standard wipe in TWRP (it wipes delvik, cache, and data) I had to selected "advanced wipe" and wipe system in addition to delvik, cache, and data. I believe this had to do with the htc build version on the phone being outdated but I'm not 100% sure.
chobungus said:
For anyone who's interested I was able to successfully install ARHD to my phone after doing some research. Rather than just doing the standard wipe in TWRP (it wipes delvik, cache, and data) I had to selected "advanced wipe" and wipe system in addition to delvik, cache, and data. I believe this had to do with the htc build version on the phone being outdated but I'm not 100% sure.
Click to expand...
Click to collapse
+1. I always use advanced wipe in TWRP, and wipe as you indicated. I'm thinking everyone posting here should also indicate which version of TWRP you are using, as that may be an issue as well.
xRogerxC said:
+1. I always use advanced wipe in TWRP, and wipe as you indicated. I'm thinking everyone posting here should also indicate which version of TWRP you are using, as that may be an issue as well.
Click to expand...
Click to collapse
Yes that's a good idea! I've just added TWRP version (2702) to my signature