Help - D801 won't reboot after flashing new ROM - T-Mobile LG G2

Please help. I have a D801, it was running cm12.1. I installed twrp (previously had an old cm recovery), did a backup, wipe cache and dalvik, then flashed the RR Marshmallow Rom and Gapps, all successful. But when I pressed reboot, the LG logo flashed on the screen and nothing happened after that. The phone became very hot at the top.
I went back Into twrp and did a restore. That also went correctly but again on reboot, the same problem. I had about 80% charge.
Now I cannot access recovery, the LG logo flashes but nothing else. The display is dimly lit.
I had used the latest twrp img file from their web site.
For now I have the phone charging, but no led indicator is on.
Please guide to revive the phone. Thank you. I would be happy going right back to original ROM.

Related

[Q] Stuck in recovery loop, LG Spectrum

Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
I was in the process of manually installing CWM Touch via Rashr Flash Tool to replace an old 6.0.1.1 non-touch version i had on it before, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS.
I've tried the following with no success:
Clearing data factory reset
Clearing cache
Clearing Dalvik cache
Full restore to V6 stock
Full restore to Cyanogen (I made a backup when I first got to CWM Touch)
This is the current behavior of my phone:
When powered on, it will display the LG logo, then it will flicker to black and then fade in the LG logo again, 5 seconds later recovery boots. If phone was off and you insert USB cable to charge, the LG logo appears, but the battery mode sort of screen never comes after. Its just stays at the LG logo, and never turns off the display.
It will keep rebooting to recovery no matter if I even tell the recovery to reboot to bootloader.
I don't know exactly how the bootup structure is for androids but the only thing I can think of that may be the issue is the recovery itself if it wasn't the app that caused this. It just doesn't make sense that after a full restore, it would still have an issue, other than the recovery itself, UNLESS there is some secret boot instruction file that's stuck with a "Reboot_to_Recovery = 1" parameter.
Since this thing is stuck in a recovery boot, how would I be able to manually, without OS access, reflash another version of CWM on the device? Or if there's another possible way to fix this, please help me.
Maybe the ROM hasn't flashed on your phone properly .try again with a clean flash. may help
HiT Thank$ If HelPed
I believe this is independent of the ROM. I had noticed in preparing to flash a new ROM that instead of restarting to the OS, it restarted to the recovery. I didn't take much note of this, but it was clear that this problem began when I flashed the new recovery. Also, the fact that I had used 2 seperate, very different restores (full restores) with no success means that it couldn't have been the ROM.
My only probably clue right now is that the recovery is to blame (which is weird since CWM notes 6.0.4.7 as compatible with LG Spectrum. I had 6.0.1.1 before with no issue). I have no idea how to change this recovery however, given that I can't even boot the OS at all, and there doesn't seem to be a "flash recovery' option in recovery (which is kinda annoying).

I can't reboot into full twrp...please help

Hello all. I was on Flashable stock lollipop and suddenly my phone froze. I rebooted into twrp 2.8.1.0 if I recall correctly and cleaned dalvik and cache. Now, the phone will not boot into the ROM (keeps rebooting to the Motorola screen) or twrp. When booting into recovery, twrp flashes briefly and then goes black for a second or two. Then the teamwin screen shows and it stays on that screen. I pushed via adb a new ROM and also philz and twrp, but I cannot boot into anything else but fastboot and the corrupted twrp. Can someone please help me?
The 4.4.4 firmware download for XT1032 is unavailable.
The firmware you may need could be here: http://www.filefactory.com/folder/c6cdedc45a775d27
Many thanks for the link. I've searched for the US KitKat version of XT1032, but I believe that it is in the other file factory link that is down.
Edit: thanks to advice from @lost101, I erased user data via fastboot, rebooted and now I'm back in action.
The reason for the issue was the twrp version I used was not fully compatible with Lollipop, even though it could flash it. I thought I would be ok, even after reading the warning, but now I know otherwise.
Mod, please feel free to close this thread, if you wish.

CM ROM issue. URGENT

sorry if this is the wrong section.
My problem is complicated. So i was trying to flash my first rom ever on my lg g2 vs980. The rom was Rashed's unofficial CM 12. So i was on twrp 2.7 but i tried to update to 2.8.5.1 i think it was. After doing this i also flashed the EFS backup final.zip file (i was following a youtube tut). then i flashed my radio.zip and su.zip. I was going make another backup after doing this but then it said backup failed and i think it wiped my phones storage so i decided to just flash cm 12.zip (i didnt wipe or factory reset anything myself). So the phone boots the the cyanogen boot logo and it said "upgrading android" and below it said something like "configuring apps". Then it changed to a blue screen and rebooted. Eventually it booted to "cm 12" and for a split second i can see whats supposed to be to be on the screen, but then it turns black besides the battery, time, and back button. Help?

CM13 flashing problems. Phone keeps rebooting at CM splash screen after flash

Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
You need to be on 5.0 Lollipop. Custom recovery. Rooted. Then flash the ROM after you Wipe in Twrp

Please help! My phone shows a black screen after I try to boot into the system!

Hello all,
After I wiped my system, I tried to install the latest Magisk (From the official MagiskManager website) and then, after I wiped again, and tried to reboot, my phone just showed a black screen it wouldn't even show the unlocked bootloader warning or the boot logo and when I charge it, the LED flashes constantly (I'm not sure what that means) therefore I have to boot back into the recovery or the bootloader as there is no system. I looked at the system files and there was nothing there although the Lineage OS flashed successfully.
Can anyone help me?
I'm not sure whether my phone is bricked or something as every other time I did it (2 times) there were no problems.
Version of Lineage OS I tried to install (lineage-14.1-20180108-nightly-athene-signed.zip)
Device: Motorola Moto G4 2016 (Athene)
Custom Recovery: TWRP 3.0.2.0
Magsik Version: Magisk-v15.3.zip
Thanks in advance!
You never wipe system unless you are flashing a rom. You pretty much removed the OS and then tried. To boot it.
zelendel said:
You never wipe system unless you are flashing a rom. You pretty much removed the OS and then tried. To boot it.
Click to expand...
Click to collapse
Yeah after I flashed Resurrection Remix, everything went back to normal, but thanks anyways.

Categories

Resources