Database Info

Nexus 5 stuck on boot animation

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

[Q] boot issue with cyanogenmod 11

Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated

Spartiata said:
Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated
Click to expand...
Click to collapse
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.

Lethargy said:
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.
Click to expand...
Click to collapse
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM

Spartiata said:
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM
Click to expand...
Click to collapse
Not sure what to tell you except try another ROM first.

Lethargy said:
Not sure what to tell you except try another ROM first.
Click to expand...
Click to collapse
i'll try with paranoid and let you know

Paranoids works fine, seems like a CM problem .-.

Spartiata said:
Paranoids works fine, seems like a CM problem .-.
Click to expand...
Click to collapse
CyanogenMod will always be CyanogenMod

Cyanogen Mod 6.0 for OPPO R7 PLUS

I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus

Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom

Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk

Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).

Very exited, good job

so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back

Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...

Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.

Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)

coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it

Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone

coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.

Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.

coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE

coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..

Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk

unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.

Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!

Blu Pure XL Help

Hello, i rooted my phone today using the http://forum.xda-developers.com/showthread.php?t=3269447 post.
After i did this i tried installing the xposed framework. I downloaded a bunch of different ones and they didn't work so i pressed wipe cache/dalvik and then when i rebooted it, it just shows the first boot screen, just the white one. And it just stays there.
I can still enter recovery and boot loader. Can someone please help me with this?

do you have twrp 2.8 or 3 installed?
3 has issues with wipes and partitions... did you let it finish or did you stop it in middle of wipe (3.0 takes FOREVER, and if you stop it, it corrupts partitions)
so 1st step is install twrp 2.8 if you are using 3+... use this one:
http://forum.xda-developers.com/pure-xl/development/twrp-twrp-blu-pure-xl-allview-x2-xtreme-t3269596
then load this nandroid:
http://forum.xda-developers.com/pure-xl/general/rom-blu-pure-xl-stock-rom-t3382722
if that doesnt work...
http://forum.xda-developers.com/pure-xl/help/guide-unbrick-softbricked-blu-pure-xl-t3371981
sp flash is the hardcore fix it no matter what factory new route... read THE WHOLE thread if the BLU nandroid doen't fix it for you...

Also as far as Xposed goes, you'll want the latest SDK 22 version that's ARM64. I don't usually clear cache after I install Xposed, works fine.

@tbirdguy Hey man long time no see. There's a flaw in your response... Lol jk
Thanks for the help but I fixed it I just flashed the boot recovery and system part of the allure rom. And after that it still didn't work so I flashed the whole rom. Now it works fine

Ashalinia said:
Also as far as Xposed goes, you'll want the latest SDK 22 version that's ARM64. I don't usually clear cache after I install Xposed, works fine.
Click to expand...
Click to collapse
If you don't mind can you please share a link to the download? I've downloaded 9 different Xposed zip files and none of them worked.

This is the one I use.
http://dl-xda.xposed.info/framework/sdk22/arm64/xposed-v86-sdk22-arm64.zip

Ashalinia said:
This is the one I use.
http://dl-xda.xposed.info/framework/sdk22/arm64/xposed-v86-sdk22-arm64.zip
Click to expand...
Click to collapse
Just curious, but, will any of these Xposed modules fix the Sim card detection issue I'm having right now?

Xposed, BusyBox and AdAway not installed with SuperMan ROM

I selected all of these things to be installed with the SuperMan ROM, But they weren't installed when I got to the home screen after installing the ROM, I know it worked because I have edge on a regular S7. help please. Also sorry for the amount of things I have posted if you have seen any.

Spooky11 said:
I selected all of these things to be installed with the SuperMan ROM, But they weren't installed when I got to the home screen after installing the ROM, I know it worked because I have edge on a regular S7. help please. Also sorry for the amount of things I have posted if you have seen any.
Click to expand...
Click to collapse
Hi
did you try to re flash them again from aroma , no wipe?

MAX 404 said:
Hi
did you try to re flash them again from aroma , no wipe?
Click to expand...
Click to collapse
No I haven't tried that, but I am worried, as I went and installed Xposed, I feel as if I should back up and wipe but I can't do either of those things it always says it fails through TWRP.

Spooky11 said:
No I haven't tried that, but I am worried, as I went and installed Xposed, I feel as if I should back up and wipe but I can't do either of those things it always says it fails through TWRP.
Click to expand...
Click to collapse
Hi mate
1 what errors you get and when , flashing xposed , what xposed file did you use?
2 TWRP is working ok? can you flash with it, did you wipe data during its installation?

1 of these 2 messages appear
1) failed to mount storage (appeared while wiping once and anotherwhilst installing rom.
2) /data failed (something) along these lines while wiping device
I wasn't ableto wipe device it wont let me no matter what.
Even tried when installed stock rom through smartswitch and still had all my stuff.

TWRP works fine and I will check what file I used when I get home in a few hours.