I've been running Resurrection Remix without problem for months.
After booting by phone and trying to unlock it my phone just rebooted on the lock screen without any input from me (I might have been holding the power button or somthing acidently) after the reboot it put's me into TWRP. Trying to reboot it again results in a very long boot animation followed by another reboot into TWRP.
This is the second time this happend and I still have no idea what has caused this (I fixed it last time I tried by re flashing the rom). I haven't installed/changed/updated anything before it happend so I don't even know where I could begin looking for a cause.
Is there a way to fix this without re flashing/restoring a backup and can I do anything to prevent this/find out what's causing this? prevent this/find out what's causing this?
KeinNiemand said:
I've been running Resurrection Remix without problem for months.
After booting by phone and trying to unlock it my phone just rebooted on the lock screen without any input from me (I might have been holding the power button or somthing acidently) after the reboot it put's me into TWRP. Trying to reboot it again results in a very long boot animation followed by another reboot into TWRP.
This is the second time this happend and I still have no idea what has caused this (I fixed it last time I tried by re flashing the rom). I haven't installed/changed/updated anything before it happend so I don't even know where I could begin looking for a cause.
Is there a way to fix this without re flashing/restoring a backup and can I do anything to prevent this/find out what's causing this? prevent this/find out what's causing this?
Click to expand...
Click to collapse
In twrp check if everythings mounted
Try wiping Dalvik/ART Cache & Cache
Maybe reflash /system
Did you using any magisk modules?
Related
I rooted my phone back in December and have been using it without problems since then. I've rebooted it tons of time, haven't installed anything unusual or tried to modify anything. I just followed the normal instructions for rooting and flashing a custom rom. Today, I rebooted my phone and now it's hanging at the Galaxy SIII logo screen. Taking out the battery didn't help. I have no idea why it would do this out of the blue. What are my options for fixing this? Can I recover my data?
blueintegral said:
I rooted my phone back in December and have been using it without problems since then. I've rebooted it tons of time, haven't installed anything unusual or tried to modify anything. I just followed the normal instructions for rooting and flashing a custom rom. Today, I rebooted my phone and now it's hanging at the Galaxy SIII logo screen. Taking out the battery didn't help. I have no idea why it would do this out of the blue. What are my options for fixing this? Can I recover my data?
Click to expand...
Click to collapse
Should be easy to fix. Common issue.
Try booting into recovery. If you can then clear cache and dalvik. Try rebooting then.
If that doesn't work try re flashing the rom,
If you can't reboot into recovery but can get into download mode then you can easily fix it at the cost of losing all your data.
Let me know how it turns out.
At this point, my phone is just one big tweak.
Wiping the caches didn't work, so I ended up having to reflash the rom. Everything seems to be back to normal now though, thanks!
Dudes,
I was running CM 0701 nightly fine and decided to boot to CWM-based recovery and flash latest nightly from 0703. It got about 2/3 the way through updating apps after boot and froze. Then screen stayed black, but would backlight. Was unresponsive to touch, but I could get it to take screenshots (at least I could hear the sound made by triggering one). I longpressed the power button to force reboot and entered bootloader. Finally I could see the screen again. I thought all was better and it just needed a reboot so I reboot again and let it boot. Still no screen. So I longpressed to reboot, got into bootloader, then revovery... and tryed to reflash nightly from 0701 but it won't access my "/sdcard" because it won't mount. Same error ("Error mounting /data!) when I try to fatory reset or mount/unmount.
WTH?!
Anybody have any ideas what broke this? What it a change in last two nightlies? A change to the recovery?
I'm going to try http://forum.xda-developers.com/google-nexus-5/help/help-e-mount-sdcard-cwm-6-0-4-5-trying-t2802715 when I get home... in way too many hours. Sadface.
I also posted this in CM Forums: http://forum.cyanogenmod.com/topic/...cant-mount-data-after-0703-nightly-boot-fail/
Firstly try and fastboot flash a stock cache.img
rootSU said:
Firstly try and fastboot flash a stock cache.img
Click to expand...
Click to collapse
Thanks @rootSU. Ultimately and unexpectedly the phone came back to life before I could get to a computer with adb access. I had tried rebooting several times before, but magically after about 6 hours of downtime (no charge or anything) it rebooted up fine. It was a little shaky and slow at first, and ran the update apps process again on the next boot but has since be stable. No flashing. A couple reboots. All fine.
Thanks to the XDA community for existing and providing such a reassuring resource for knowledge and problem solving!
I experienced the infamous boot loop problem on my Nexus 5. I'm running stock android, and it started after the battery was depleted overnight - and after I recharged the phone.
First I tried to to just clear the cache in Recovery Mode. It went into a long loop where every other second a flash would appear on screen with the 'No Command' screen. I decided to abort that after 30 minutes and try a Wipe data/factory reset in recovery mode.
It seems to work fine in the beginning, but after a while it begins with the same loop, where it occasionally shows the 'No Command' screen.
Seems like there is broken hardware - or do you have any ideas what the reason may be and how to amend it?
Try to reflash all stuff with google factory images and check if your problems still exist.
What do you mean by "It seems to work fine in the beginning"? You're able to boot into the OS? Could be a faulty/broken power button which might be causing the bootloop as well.
Anyways, as mentioned above, flash the factory images to rule out the possibility of a software issue.
I would recommend unlocking your bootloader, flashing a custom recovery, doing a wipe with that and then flashing a stock nandroid.
If you aren't good with adb, and you don't have an OTG cable, I would look into how to flash the factory images from Google first, then once you're all set with that do the above.
Thanks
Thanks guys. I decided that I would invoke my warrany from Google and get a new phone.
I hope someone else benefits from your suggestions, I would have if I didn't have my warranty...
[Update 4/3: Logs] N5 works normally -> stuck on splash screen -> have to reflash ROM
My Nexus 5 is having a problem that is just confusing the hell out of me.
To summarize the issue...
1. Phone will get stuck on "Google" splash screen (written in white) on bootup.
-at this point, I can reach bootloader and recovery
-clear cache/format cache does not alleviate problem
-factory reset does not alleviate problem
-fastboot flash-all does not normally alleviate problem
-only flashing a ROM via TWRP works
2. ROM flashed via TWRP, things work like normal for ~4-24 hours. At some point, there will be a random reboot. Usually, this is while under stress (playing a game, updating apps). It will reboot normally and continue to work like normal for some time. But it's a ticking time bomb. There will be another random reboot at some point, often while idle - definitely not workload-related. This second one will get me stuck on the Google splash screen again, with the only way of fixing being re-flashing the ROM via TWRP.
These symptoms are basically the same regardless of the ROM - I've tried factory images, a stock-ish ROM with Gapps removed from XDA, and CyanogenMod. It seems like it could be a hardware problem, but I don't have a clue what it would be since it is so consistently fixable, albeit temporarily. Does anyone have any troubleshooting suggestions or a clue as to what part of the phone is likely failing?
Post logs.
Elluel said:
Post logs.
Click to expand...
Click to collapse
Okay, so this afternoon I went to check on it after spending some time on the charger. The LED was lit, so I thought things would be fine. It just wouldn't wake up. It wasn't responding to various button presses, but the LED turned off after I held the power button. It took a lot more attempts than normal to get to fastboot, but eventually got there. I used fastboot boot to get to TWRP and retrieved last_kmsg, kernel_log, and logcat. Logcast was empty. Here are pastebins for the other outputs.
last_kmsg: http://pastebin.com/z2KG2aHW
kernel_log_output: http://pastebin.com/v7TZZKeb
Thanks for the help!
I'm going to bump this one time, since there are now logs posted which I think might provide some clear insights to those who know how to interpret them.
Running AOSP Exstended 8.1.0 while seemingly normal use (in actual fact data stopped working, so I reset the phone to solve that issue).
It then proceeded to reboot loop a few seconds after it gets to the lockscreen. I'm not sure if it's related to the data partition, but it seemed to be the culprit, since wiping caches from TWRP or re-flashing the system.
I did end up making a backup of said partition and then wiping it, but I'd like to recover everything from data if possible (maybe flash it back later and fix it somehow?).
Can anyone recommend any specific steps?
I've never encountered the particular issue of it rebooting only after the lockscreen (regular boot loops in my experience are the boot logo).
I haven't been able to find anything useful on google though I did find a lockscreen reboot case on XDA that was unsolved.
Thanks in advance!
It happened again today.
Does nobody have any similar experiences? Would anyone know if it's the phone itself causing this issue or would it be tied to the ROM?