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
Related
Recently I flashed RebelRom Beta 2, it resulted in a the LG logo being displayed on my phone but nothing would happen. So I did a restore from CWM, and the restore worked fine for a couple of days but at some point my phone lost power. Now whenever I turn it on I get boot loops and am unable to get into CWM. My question is is my phone bricked, and what can I do to avoid another brick? (Note I never formatted /data and I always follow installation instructions.)
KindaWack said:
Recently I flashed RebelRom Beta 2, it resulted in a the LG logo being displayed on my phone but nothing would happen. So I did a restore from CWM, and the restore worked fine for a couple of days but at some point my phone lost power. Now whenever I turn it on I get boot loops and am unable to get into CWM. My question is is my phone bricked, and what can I do to avoid another brick? (Note I never formatted /data and I always follow installation instructions.)
Click to expand...
Click to collapse
It's a known problem, at this point the solution is to restore you back and don't shut off your phone. Reboots work fine, but shut off will boot loop it.
Hmmm so I can't turn off my phone. What do you mean by reboot/how do I reboot? Also does this mean I can't flash roms anymore? And finally is there a fix on the horizon?
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
ride1226 said:
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
Click to expand...
Click to collapse
You really have to investigate by adb. Look into the dmesg output and logcat as well. Maybe your sdcard is corrupt or 100 other issues are possible as well. What device do you own? H811? unlocked?
.
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
kunate said:
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
Click to expand...
Click to collapse
There are several users reporting that the latest cm version bootloop the best option is to start in download mode and Flash with LGUP Stock ROM.
You could also try to boot into Download Mode and then flash the latest twrp and then Boot into Factory Reset Mode again
i followed this guide
teamandroid.com/2016/03/08/update-tmobile-galaxy-note-2-t889-android-601-resurrection-remix-marshmallow-custom-rom/2/
and it worked perfectly until yesterday
the other day i looked at my phone and it formatted and restarted on its own. i didnt really lose much.
so i accepted it and reset up all my apps and such, and then when my phone died and i charged it
it got stuck in boot loop forever
i tried wiping both cache and reboot recovery it skips boot loop long enough to load up but as soon as i see my homescreen for a second it boot loops again.
so then i tried completely formatting the phone over which worked until this morning when i woke up my phone was dead. swapped batteries and turned it on. booom boot loop again.
is there any advice on what i should do?
im able to format it and get it working again if something needs installed etc
but i want to stop this from happening again
Q: is it possible that a certain app i downloaded is forcing the boot loop? i dont see why it would because ive had all the same apps for months and it just happened out of no where.
i appreciate any help, id just like to know why in the world its happening, and what the best course of action would be
im thinking maybe restore it back to factory firmware and unrooting and starting the process all over again
i seen something for 7.1 would that be better?
Hello,
Yesterday all out of a sudden, my nexus5x freezed. After a while it booted, and then it sticks for an amount of time in a bootloop. You see the google logo for a few secs and then it reboots.
After like 15 to 20 boots, it will normaly start up android, work for an amount of time, and then its al over again!!
I was running the latest pixelrom when it first happend. Its kinda strange since i used this version for a long time without problems. Ive flashed alot of roms but never had this before!
To be sure if it is the pixelrom is the problem, i went back to stock with twrp as recovery. Also with this combination, after a while the nexus5x will freeze and its al over again.
But.... The weird part of this is, that i have NO longer the twrp recovery... Its gone.
If i go into fastboot and choose boot into recovery, it gets stuck since either its not there or cannot load..
What could be the problem? Faulty system memory? Latest android ?
Before the freeze happends, i can fastboot into the twrp recovery but after the freeze i cant..
Same happened to me. Exact same situation. I tried latest factory image but it was the same. Phone only boots when it is hot enough to turn off 2 big cores. You my friend have bootloop problem.
Sent from my LG-D855 using Tapatalk
This can be locked!
i have found: https://forum.xda-developers.com/ne...ed-nexus-5x-bootloop-death-fix-t3641199/page9
Hi,
When i use my 5x for a hour or so, then try to reboot it, it stucks at the google logo. When i restarted with the physical button, its usually starts, but not always. There was a time when i couldn't make it work for at least 30minute, then i waited a hour and it started finally.
Every time when i stucked at google logo, i'm able to get to twrp. Tried with stock rom, locked bootloader, stock recovery too, but its same. When i use it for a long time and its get hot, its stucks at google logo when restarting.
But it never restarted automatically. I can use it for 10hours if i want, just if i restart it, its stucks.
Is it because faulty motherboard or what do you think?
Because it dont stuck forever, and i can access recovery mode.
That's probably some random issue, the BLOD happens like this:
You do your stuff on the N5X,
everything freezes for several seconds,
phone restarts itself and doesn't get past google logo,
can't access recovery, however you can access bootloader, which is very laggy,
starting up again is nearly impossible, you can hold the button for an hour and the phone won't even get to the google logo.
ZLevente said:
Hi,
When i use my 5x for a hour or so, then try to reboot it, it stucks at the google logo. When i restarted with the physical button, its usually starts, but not always. There was a time when i couldn't make it work for at least 30minute, then i waited a hour and it started finally.
Every time when i stucked at google logo, i'm able to get to twrp. Tried with stock rom, locked bootloader, stock recovery too, but its same. When i use it for a long time and its get hot, its stucks at google logo when restarting.
But it never restarted automatically. I can use it for 10hours if i want, just if i restart it, its stucks.
Is it because faulty motherboard or what do you think?
Because it dont stuck forever, and i can access recovery mode.
Click to expand...
Click to collapse
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Wakamatsu said:
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Click to expand...
Click to collapse
Thanks, i'll try bhz31a thanks
(I'll write in some days if it worked or not)
Wakamatsu said:
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Click to expand...
Click to collapse
Which bootloader is bhz31a? I tried the bootloop fixes, none worked. Only have access to bootloader, no recovery.
edit: i see bullhead-opm1.171019.011-factory-3be6fd1 has the bhz31a bootloader. I tried this, with no luck on my end. Even with the 4core modified recovery/boot. I must have one of the unfixable BLOD.
I tried that bootloader too, same
My phone can boot, just sometimes it's stucks at google logo, but i can access recovery every time, even if it's stucked at google logo.
Usually every 2. reboot stucks.