Hello to the community, I just want to ask. When I used Resurrection Remix, one time it stuck into Infinite loop. Dirty flashed ROM and later when I reboot my N5X, again. It also appeared on LineageOS. Dirty flashing ROM every time when the phone stuck into infinite loop and wont open normally to Android is very irritating. So can anyone help how to take logcat while it stuck into infinite loop? (Possibly bootloop due to software) (In AOSP ROM's I didn't have the issue with stucking into infinite loop). Because I want to send a bug report to LineageOS Jirra and I don't know how to get it.
When I dirty flash the ROM, can I get the logcat of this issue?
Related
So here is the problem, I try and install a new ROM with TWRP and it goes through with no problems. Once I go to restart it, the problem begins. My Note keeps getting stuck when it gets to the updating andriod apps screen after the initial (first) reboot after install. I have tried this with two different roms and can not get it to work. An outlying problem that i also have is that when it is off for long periods of time when I turn it on it gets stuck in system boot mode (boot animation). I have no idea what is going on. Can someone please help.
Current Setup:
NOTE 2
TWRP
MACK Allstar 5.0 Rom
Only one .bak on the system update.
Everything else is APK based
I was having boot loop while installing cm 12.1 i could boot if i unplug the battery and leave te phone for half an hour. When booted the phone has no problems. But the problem is while booting. It gave me constant bootloops. So i decided to do a complete factory rom change. So i flashed fastboot rom vi mi flash tool. Still the problem persists te phone is looping with a blue flash at the top.
A bit too late, sorry, but I think I have had some minor issues after flashing a fastboot rom few times.. I think it can be solved by entering MiRecovery, cleaning cache and then rebooting from recovery to system. If the system is not booting up in 5 minutes, it's not fixed. On the other side, maybe you haven't done it right or something is wrong with your file. I recommend doing it again with v45 Miui5 fastboot Rom. That one always works for me.
Anyone to help ??
Only way to make it booting is installing rr rom. With beast v5 kernel. That too with multiple reboots while android upgrading progress
I tried miui5 and i have twrp. I think this is happening by improper kernel configuration.
As i told earlier i can use phone awesomely by installing RR rom with beast v5 kernel.
Hi. I've got a jem, which was previously running CM11, which I finally got around to trying to update. In the process, I ended up with AICP installed. It won't fully boot; it hangs at the logo, but is responsive using adb (shell, logcat, etc).
Since their release notes mention a new recovery requirement, I tried to upgrade my recovery and it failed. Now, I can boot the AICP rom (which hangs at the logo), but all efforts to get into either the recovery or fastboot fail, and aicp still isn't booting completely (i let it sit overnight, and the logo was still spinning in the morning.
I'm hoping that since adb works, the tablet isn't a brick.
Can anyone suggest a path out?
thanks
bricklayer16 said:
Hi. I've got a jem, which was previously running CM11, which I finally got around to trying to update. In the process, I ended up with AICP installed. It won't fully boot; it hangs at the logo, but is responsive using adb (shell, logcat, etc).
Since their release notes mention a new recovery requirement, I tried to upgrade my recovery and it failed. Now, I can boot the AICP rom (which hangs at the logo), but all efforts to get into either the recovery or fastboot fail, and aicp still isn't booting completely (i let it sit overnight, and the logo was still spinning in the morning.
I'm hoping that since adb works, the tablet isn't a brick.
Can anyone suggest a path out?
thanks
Click to expand...
Click to collapse
To self-reply, for some reason, adb reboot bootloader wouldn't work, but adb reboot recovery got me into fastboot. I've managed to get things repaired.
Hello there
After my phone randomly rebooted while watching a video it ran into a bootloop.
I had been running LineageOS for the past couple of months and everything was fine up until yesterday.
I have tried restarting, and everything and only managed to reflash twrp via adb and force it to boot into twrp, but now it's stuck booting into that.
when I try to boot into lineage I only see the boot animation of lineage that never stops, and when I boot into twrp I see the boot screen of that, which never stops.
I've let the phone do its thing for so long that it has run out of power, so it's not something that just takes a long time. I feel like this thing is completely bricked now.
Anyone maybe got a solution? Any help would be appreciated.
Hi,
Think I might have the same issue, except I didn't flash or modify anything on the phone. I'm running all stock ROM and all the rest.
Stuck in a bootloop in recovery mode. Mini partition does not recognise the phone. Same with QPST. QComDloader does, but only for a few seconds, so whatever I try it's not fast enough before the next reboot...
Whats are the options? I don't want to have to send it back to China
Hi guys
I have the chinese version with global rom.
Successfully installed TWRP and crDroid 10.0 rom but the google first time setup kept freezing (everything else worked perfect) so I decided to reflash the rom.
When I reflashed the rom it keeps getting stuck on the crDroid boot screen, have left it overnight and same.
Tried reflashing vbmeta, firmware and then crDroid with various wipes but same result.
I would appreciate any advice.
Mubs