Database Users

I have recovery, but download mode error.

OK, so I have an issue that I have not seen before, I googled the issue but cannot find anyone with the same issue. So I will try to keep this brief and hope that somebody will please help me with this.
I have LS980 Sprint LG G2. Earlier today, I tot my phone to ZVE. I used the update.zip method to update to ZVG. Then I reboot into recovery, wiped data/system/cache/dalvik, flashed the new CloudyG2 3.1 rom, flashed the hotfix, then reboot my phone. It booted to the LG logo and stayed there. Did not go any further. No boot animation. So I reboot back to recovery, wiped data/system/cache/dalvik again and this time I tried by flashing the LP bootstack, then the CloudyG2 3.1, then the hotfix and reboot my phone. This time it just showed the LG logo then straight to a black screen and stayed there. So I reboot to recovery again, wiped again, then flashed KK baseband, then CloudyG2 2.2. Now that rom booted up and my phone was back to normal, or so I thought.
Now, I can boot into the rom and everything works in the rom. I can boot into recovery and it flashes the things I want it to flash. But I do not have download mode. When I try to go into download mode, it shows the blue dots and says download mode, but at the top it says secure boot error. Then goes to the black screen again. So now I cannot tot to go back to factory.
I also tried to flash the CloudyG2 3.1 from CloudyG2 2.2. After I booted into CloudyG2 2.2, I went back into recovery, wiped data/system/cache/dalvik, then flashed CloudyG2 3.1, the hotfix, then reboot the phone and it shows LG logo for a second then back to the black screen. I also tried flashing the LP bootstack before CloudyG2 3.1, logo then black screen.
I know this is somewhat of a repost. But there I am discovering new things along the way and nobody has helped me yet. Anyone know how I can fix this?

Bricked tablet? :(

Hey everyone I'm really in need of help.
I flashed cyanogenmod's v 13 rom coming from 4.4.4. In cwm it said may of lost root, yes to fix? I wanted to go back but it booted anyway. Now I'm stuck on this ROM without any Gaaps, and when I go to boot into recovery to flash the gaaps, it only shows the Google logo so CWM appears gone. I've also tried downloading playstore and ROM manager via the Web and it force closes when it goes to download.
I'm I doomed or is this fixable?

D802, flashed CM 13, black screen after <1s LG logo

I have been using CM12.1 on an LG G2 D802 and decided to upgrade the device to CM 13 today. As the device was running the stock 4.4 ROM before I initially switched to CM 12.1, I figured it would already have the Kitkat bootloader installed and proceeded to download the latest CM 13 nightly from the CM page as well the stock OpenGapps package. I then booted into TWRP (v2.6.3.3), wiped system, dalvik, data and cache and then flashed the ROM and the Gapps package which worked just fine.
However, when I selected "reboot system", the screen went black. I turned the phone off by pressing the power button. turned it on again and found that the LG logo flashes up for less than 1 second, then the screen goes black again. Gladly, I am still able to boot into TWRP. I then searched the forums, decided to try the latest Lollipop bootstack from this thread and reflashed the ROM and the Gapps package, but the problem still persits.
I am now thinking if my seriously outdated TWRP version is causing the problem, but I hesitate to update that (as it is basically the only working thing on the phone right now) without making sure that it really could be the problem.
Do you have any tips for me what could be the problem and how I can fix the phone?
Thank you very much!

Any help is appreciated

lg g2 bricked
YassinTP said:
Any help is appreciated
Click to expand...
Click to collapse
bro does ur phone goes in download mode? if yes flash tot. if not i will solve ur issue through teamviewer. dont worry it will be solved.

YassinTP said:
Any help is appreciated
Click to expand...
Click to collapse
to boot into system you need hybrid bootstacks, and definitiverly need thermal twrp 2.8.7.3
you could either do both. download twrp and bootstaclks the hybrid ones.
first update twrp if you want. but i recomend as it has thermal to control heat during installations
once you in twrp. wipe all. then reboot into recovery from recovery.
flash hybrid bootstacks then again reboot into recovery from recovery, and when you in twrp flash rom it should boot.
just remeber to reboot into recovery each time you flash twrp ot hybrids to take effect.

zuk z1 bootloop when flashing any rom

i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks

Boot and recovery partitions
Sounds like you messed up boot and recovery sections. Since you can boot up successfully, you may try to flash back to ZUI which changes these two sections completely. If it's not a solution for you, I think the only way to repair is completely format including kernel, system and partitions. You can find the tutorial on Website.

...
you can fix it just use TOOL_ZUK_Z1_ENG_0.0.6

Try flashing COS 12.1 via fastboot.

crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
Hi!! I've flashed the NucleaRom too and for a couple of weeks it worked just fine. However one day, out of nowhere, the phone, while still on and working, restarted itself and entered a bootloop. After a few days it restarted normally and lasted a couple of hours but then it all started again. The BIG issue here is that when the phone enters in this bootloop where it remains on for about 15 seconds, it does it either in the system or the recovery/fastboot. I've managed to install two other ROMs via TWRP, when it miraculously remained turned on, but the problem persisted.
Is there a chance your problem was similar? How did you manage to flash via QFIL? I can't enter into that "emergency" or "download mode" in order to flash.
Many thanks in advance

i think that the problem is in the bootloader itself you should try flashing the latest os u have used and instal ordinary unofical lineage nightly (you can find everywhere) by this way your bootloader will be updated to 7.1 after that you can install any software i was having same problem when trying to migrate to lineage os

unable to install Custom ROM's
hi ,,
even i had the same problem like recovery was not accepting any ROMS... if we flash it ll go to recovery again and again,
and later i have flashed CM 13 with image file,, it worked and gone to recovery and updated the update to lineage OS 14.1 with Gapps..
hope it might help u...
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse

crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
i am continuously on the boot loop! how to get rid of it?
plz help its been 4 hrs, i think i am in trouble! any possible solutions!!!!

U can try one thing.... Install cm13 with flash file and then restart - - & go to recovery select install update and select lineage 14 and G apps... I did like this . And it worked....

Major heads up

Just thought I would tell everybody about my experience. Be careful when flashing ROMs. I was on marshmallow 3.1.1 xdabbebs. On a vs985 by the way. Anyway tried to Flash Jasmine 9.0 again with the 9.1 update...did everything correctly...wipe dalvik cache cache data system...then went on to Flash 35b bootstack...from there flashed Jasmine along with the update then the moderate debloat zip...after that did a factory reset...THEN when I went to reboot the screen was black...no logo no both in but odd thing was I could hear that it was booted...black screen of death...attempted to get into download mode to do a tot back to 10b not ring able to see anything on the phone...tried to Flash and failed every time. So...I tried the kdz method...numerous fails...for 20 minutes...out of nowhere phone vibrates and kicks on...I go to settings and somehow it took the 24b file...don't know how...anyways I tried to tot from there...to 10b...fail fail fail...then I tried the one click root method...nope didn't work...so I did king root...that worked...I then did the autorec twrp method...it flashed it...I then installed twrp manager to get the latest recovery...I flashed that...that seemed good...went to reboot to recovery...I got a security error message...I pulled battery and tried to reboot...same message every time...I then did the power and volume down and managed to get into recovery...thank God...LUCKILY I had a backup of xdabbeb 3.1.1 Rom...restored and I'm back up and running...lol...I think my Rom flashing days are over...lol...anyway...careful guys

matt1285 said:
Just thought I would tell everybody about my experience. Be careful when flashing ROMs. I was on marshmallow 3.1.1 xdabbebs. On a vs985 by the way. Anyway tried to Flash Jasmine 9.0 again with the 9.1 update...did everything correctly...wipe dalvik cache cache data system...then went on to Flash 35b bootstack...from there flashed Jasmine along with the update then the moderate debloat zip...after that did a factory reset...THEN when I went to reboot the screen was black...no logo no both in but odd thing was I could hear that it was booted...black screen of death...attempted to get into download mode to do a tot back to 10b not ring able to see anything on the phone...tried to Flash and failed every time. So...I tried the kdz method...numerous fails...for 20 minutes...out of nowhere phone vibrates and kicks on...I go to settings and somehow it took the 24b file...don't know how...anyways I tried to tot from there...to 10b...fail fail fail...then I tried the one click root method...nope didn't work...so I did king root...that worked...I then did the autorec twrp method...it flashed it...I then installed twrp manager to get the latest recovery...I flashed that...that seemed good...went to reboot to recovery...I got a security error message...I pulled battery and tried to reboot...same message every time...I then did the power and volume down and managed to get into recovery...thank God...LUCKILY I had a backup of xdabbeb 3.1.1 Rom...restored and I'm back up and running...lol...I think my Rom flashing days are over...lol...anyway...careful guys
Click to expand...
Click to collapse
After getting Secure boot error you could have flashed Mr.bump.