Boot loop after trying to install CM - G2 Q&A, Help & Troubleshooting

Hello, I could us a little assistance. I was trying to install CM on my new Verizon LG G2 (VS980). I was able to root using ioroot, dump aboot.img, lokify CWM 6.0.4.4, loki_flash the recovery, and boot into CWM. When I tried to sideload the CM 10.2 image, I got some error about unable to lokify boot (it was missing /system/bin/loki.sh). It looks like the problem is that the pre CM 11 images have an old version of loki that fails regularly. It said it had aborted the installation, but something got totally hosed, as when I attempted to reboot, I got into a "secure boot unsuccessful" loop. I've made a verison of the CM 10.2 zip with the latest version of loki_patch and loki_flash from github, but I can't seem to get into recovery using the buttons (might be doing it wrong as the only time I went into recovery I just did adb reboot recovery) to try flashing another rom or return to stock. I can get in to download mode by holding up during boot, but I don't have easy access to a non-linux machine to use the lg mobile support tool. Is there any way to return to stock without a windows computer?
Edit:
Update, I was able to get back into recovery by unplugging the USB (apparently it doesn't like to boot into recovery if the USB cable is connected). Installed my patched CM 10.2 and everything worked like a champ.

DRayX said:
Hello, I could us a little assistance. I was trying to install CM on my new Verizon LG G2 (VS980). I was able to root using ioroot, dump aboot.img, lokify CWM 6.0.4.4, loki_flash the recovery, and boot into CWM. When I tried to sideload the CM 10.2 image, I got some error about unable to lokify boot (it was missing /system/bin/loki.sh). It looks like the problem is that the pre CM 11 images have an old version of loki that fails regularly. It said it had aborted the installation, but something got totally hosed, as when I attempted to reboot, I got into a "secure boot unsuccessful" loop. I've made a verison of the CM 10.2 zip with the latest version of loki_patch and loki_flash from github, but I can't seem to get into recovery using the buttons (might be doing it wrong as the only time I went into recovery I just did adb reboot recovery) to try flashing another rom or return to stock. I can get in to download mode by holding up during boot, but I don't have easy access to a non-linux machine to use the lg mobile support tool. Is there any way to return to stock without a windows computer?
Edit:
Update, I was able to get back into recovery by unplugging the USB (apparently it doesn't like to boot into recovery if the USB cable is connected). Installed my patched CM 10.2 and everything worked like a champ.
Click to expand...
Click to collapse
how did you patch cm 10.2

Related

Nexus won't boot properly after flash

Hey guys, I flashed SmoothRom via that app goo.im, and when I did it, it said that I needed a compatible recovery, so I flashed the one that it recomended. Well I flashed the rom, and now my Tablet won't boot properly. I can get it to fastboot, but even when I try to flash a recovery from fastboot, it gets stuck at the boot screen (Yes my bootloader is unlocked). I've been trying to use the Nexus 7 toolkit to flash the recovery,and it is saying that it is flashing successfully, but I still cannot boot into recovery. Any ideas? I know I'm not totally bricked cause I can still get into fastboot, I just need recovery to work so that I can flash a new rom and fix this issue!
Fixed it! Just flashed the stock recovery, wen't back into fastboot and flashed CWM. Mod's you can delete this thread now

[D800] Stuck on LG boot logo

I had CM11 M6 installed. I wanted to flash this kernel called Furnace. I used the AOSP version, not sure if I should've used stock. Before I flashed it, I tried to wipe the cache. It was taking about 5 minutes so I force rebooted it. After I did that, my phone would be on the LG boot screen for about 3 minutes (before it was about 5 seconds) then I would see the CM boot screen. Overnight I tried wiping the cache again. When I woke up, I was on the lock screen. I flashed Furnace and then I was stuck on the LG boot screen. I went back into recovery and tried resetting to factory or whatever it's called and it took awhile to format /cache but it eventually did. Still, I was stuck on the LG boot screen. For some reason I thought installing a new recovery would help (I had CWM before). I pushed a TWRP recovery file for my device to my phone. I then put this command in the adb shell: dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery (recoveryfilename.img was replaced with what it was named). I rebooted into recovery from the old recovery, and on the top left it said secure booting error. I tried restarting and booting into recovery, no luck. Now I'm not really sure how to flash a new recovery because I can't get into recovery. I'm pretty sure to fix my booting problems I need to reflash CM, which will flash CM's kernel...?
Also, when I try to use fastboot commands on my computer, I get ERROR: could not get pipe properties
Can I use adb while it's in this boot state? Please help!
By the way, I'm using a mac
Edit: Looked around on the Furnace Kernel thread, I guess I used a too new version of the kernel for CM11...
Edit: Found this: http://forum.xda-developers.com/showthread.php?t=2582142, gonna try it out soon...

Stuck at room boot animation, no recovery mode

I have installed Unofficial CM 13 successfully, but I forgot to root the device, so I go back and flash supersu file and reboot - I think I flashed wrong version for marshmallow. now phone stuck at cm boot animation, I have no recovery, only has access to download mode. I also have no access to phone through adb or fastboot.
I was in the similar situation before, where I was stuck at lg logo, and fix it by flashing stock rom (now I cannot find that thread), but now it tries to boot the rom, seems like a different situation.
What should I do?
lg g2 stuck on lg logo
Behzadsh said:
I have installed Unofficial CM 13 successfully, but I forgot to root the device, so I go back and flash supersu file and reboot - I think I flashed wrong version for marshmallow. now phone stuck at cm boot animation, I have no recovery, only has access to download mode. I also have no access to phone through adb or fastboot.
I was in the similar situation before, where I was stuck at lg logo, and fix it by flashing stock rom (now I cannot find that thread), but now it tries to boot the rom, seems like a different situation.
What should I do?
Click to expand...
Click to collapse
just short connectors and flash all partations again.

Unable to boot into twrp recovery after installing cm13 on t-mobile d801

I got cm 13 running on my d801 g2 the other day and I'm not a fan of it so I'm planning on flashing to cloudy g2 2.2 but now i am unable to boot into twrp. I enabled root, installed twrp and even enabled advanced reboot to boot directly into recovery but i keep getting secure booting error Cause: boot certification error which is what i was getting on stock android before getting cm13, i fixed the issue before with the kitkat auto rec app but I've read that auto rec can cause a hard brick if used in marshmallow. Trying to get into twrp through twrp, cm advanced reboot, hard key(power and vol down) recovery, flashify and adb reboot recovery command all cause the same error message. Any advice? I tried flashing twrp 3.0.0.4 and that put me into fastboot as does any other twrp version I've tried in flashify
lg g2 bricked
hevydevy said:
I got cm 13 running on my d801 g2 the other day and I'm not a fan of it so I'm planning on flashing to cloudy g2 2.2 but now i am unable to boot into twrp. I enabled root, installed twrp and even enabled advanced reboot to boot directly into recovery but i keep getting secure booting error Cause: boot certification error which is what i was getting on stock android before getting cm13, i fixed the issue before with the kitkat auto rec app but I've read that auto rec can cause a hard brick if used in marshmallow. Trying to get into twrp through twrp, cm advanced reboot, hard key(power and vol down) recovery, flashify and adb reboot recovery command all cause the same error message. Any advice? I tried flashing twrp 3.0.0.4 and that put me into fastboot as does any other twrp version I've tried in flashify
Click to expand...
Click to collapse
does ur phone goes in download mode?
kalpesh patil said:
does ur phone goes in download mode?
Click to expand...
Click to collapse
It will give me the download mode message then goes to a black screen. My computer brings up 15 disc partitions with only one partition containing data, one folder called image with files include adsp, cmnlib, mc_v2, modem, playread, wcnss and widevine they all have duplicates with different file types b00-b26 and mdt .

-PLEASE HELP- UNABLE TO FLASH TWRP OR ROOT

Hello
Sorry for my bad english
a few months ago, i decided to flash my first custom rom (One UI rom) and it worked fine
then i was testing a lot of other roms too until i tried lineage os 20
when i flashed lineage os 20, i decided to try another rom but i was stuck on the twrp logo screen. i tried methods of fixing it but none of them worked.
after trying a method of flashing twrp once again, it failed and i got stuck in a reboot loop and could only boot into download mode. so i booted into download mode and flashed a stock rom.
everything was working fine again until i wanted to try another custom rom. At first whenever i would flash twrp, they would always fail. but later i found the cause of that and fixed it. then, flashing twrp would always pass but my device would get stuck on a reboot loop once again and i had to flash stock rom again.
i tried rooting using auto root but it would show me a verification failed error and i had to reset my device. so now im stuck on a device which cannot flash twrp, nor can it be rooted. its been 1 month and i could not find a viable solution so any help would be extremely appreciated.
You have to just reflash your fastboot rom with fastboot mode unzip it and double click on flash_all.bat file or something like that
it is a samsung, there is no fastboot mode

Categories

Resources