Hi I got a solution to endless bootloops (at least working for me ) every time I flash new ROM I got stuck with bootloops so I experimented little bit and this solution seems to be working ...
I am using CM10 with Semaphore JB
You will need fixrecovery.tar and Odin (I used v1.83) you can download them in attachments.
For those who don't have flashable kernel on Internal SDCard can skip step 5 and second half of step 3.
1. So first of all you have to remove SIM and SDCard.
2. Flash fixrecovery.tar with Odin and uncheck Auto Reboot
3. Get into recovery and wipe only cache and flash kernel you want
4. Flash normal kernel with Odin and again uncheck Auto Reboot
5. Get into recovery and again flash kernel of your choice
6. Now you should be ready to switch your phone on
Maybe this excessive flashing of kernel is not necessary but I did it this way
Did you make this fix by yourself? There is already a fix for bootloop from stratosk!
Yes I did... can you post stratosk's fix please ?
Syntaxer said:
Yes I did... can you post stratosk's fix please ?
Click to expand...
Click to collapse
sorry, my mistake, it's probably made by someone else. Search the thread.
Anyway, thanks for the fix...
No problem I hope someone will find this fix useful
Syntaxer said:
Yes I did... can you post stratosk's fix please ?
Click to expand...
Click to collapse
sure you did ... [Q] Cannot boot or enter recovery (CM9 20120425)
Didn't see that post earlier, but it's not working for me anyway ... I had to clear cache additionally
Thats big development time... Clear cache ftw!
Sent from my XT910 using xda premium
Hello there,
Thanks for the guide. This hasn't worked for me?
I was upgrading versions of aways ROM (from ICS to Jellybean) and once I had flashed the ROM and GAPPS the phone rebooted. The link for the GAPPS was broken on the ROM website but it found me a replacement that I used. The phone does boot but FC on setup and no longer boots into recovery and is stuck in bootloop.
I thought this would fix the issue as I could still enter download mode but I still have the same problem? Phone won't boot into recovery and just loops...
Any thoughts?
Thanks in advance : )
I have a device that is experiencing bootloop just stop at the logo, I think this is the kind of Mtk, rooted, Kitkat. I do not know exactly what causes it bootloop, Before bootloop I edit files and install Tweaks build.prop through the application My pimp and when I restart the device bootloop ensued, do you think this is file damage build.prop or else. So that my device bootloop
Related
Hi there,
I'm new so I'm sorry if there is already a thread like this.
I'm having problems installing CM9 on my Gio. I'm following the instructions by Maclaw. Here are the steps I do:
1. install via Recovery Menu the px-cwm-v2.zip (ClockworkMod I think)
2. reboot
3. install the CM9 main zip (cm-gio-ota-eng.13052012.zip)
4. factory reset
5. reboot
6. Apply patch v2 and v3 (patch-cm9-v2.zip & patch-cm9-v3.zip)
7. reboot
I thought that was it but all i see now on the screen is "ANDROID". I tried rebooting several times but nothing works for me.
I tried the whole process now for 3 times but everytime the same failure. I have now Android 2.3.3 with root rights but I want to try out CM9.
I don't know what I'm doing wrong so pls help me if you know where the problem is.
Thanks a lot
-Hibuja
xXHibujaXx said:
Hi there,
I'm new so I'm sorry if there is already a thread like this.
I'm having problems installing CM9 on my Gio. I'm following the instructions by Maclaw. Here are the steps I do:
1. install via Recovery Menu the px-cwm-v2.zip (ClockworkMod I think)
2. reboot
3. install the CM9 main zip (cm-gio-ota-eng.13052012.zip)
4. factory reset
5. reboot
6. Apply patch v2 and v3 (patch-cm9-v2.zip & patch-cm9-v3.zip)
7. reboot
I thought that was it but all i see now on the screen is "ANDROID". I tried rebooting several times but nothing works for me.
I tried the whole process now for 3 times but everytime the same failure. I have now Android 2.3.3 with root rights but I want to try out CM9.
I don't know what I'm doing wrong so pls help me if you know where the problem is.
Thanks a lot
-Hibuja
Click to expand...
Click to collapse
Don't apply patch, they are very outdated and should be removed.
iok1 said:
Don't apply patch, they are very outdated and should be removed.
Click to expand...
Click to collapse
THANK YOU!!! Now it's working!
LOL
I was having the same problem even a half year ago....
Lolzz
So i'v been trying to get cm10 on my xperia s.
I have unlocked my bootloader, and followed this guide
https://www.youtube.com/watch?v=O52IeX93Jek
Steps i took:
1.Factory reset
2.I placed the ziped "FXP221-cm-10-20130524-UNOFFICIAL-nozomi" and "gapps-jb-20121011-signed" files on the sd card
3. flashed boot.img using fast boot
4. Installed the rom and then the gaps
5. reboot
But when i reboot i'm stuck in the boot loop.
I've now tried this 3 times but always get the boot loop. What can i do to avoid that?
Just format system & then flash rom.Everything will be fine
Sent from my Xperia SL using xda premium
I'm knew to the concept of installing new roms so i need a bit more elaborate answers.
At the moment I'm back on the stock rom and would like to know what i have to do different so that i can install cm10 without getting a boot loop.
I was successful in installing a new rom.
schpongo said:
I'm knew to the concept of installing new roms so i need a bit more elaborate answers.
At the moment I'm back on the stock rom and would like to know what i have to do different so that i can install cm10 without getting a boot loop.
I was successful in installing a new rom.
Click to expand...
Click to collapse
The Reason Why You Are Getting A Bootloop.
Flashing of Boot.img is Not Proper.
What You Need To Do.
Flash boot.img using FLASHTOOL.
In the zip file you have got, extract boot.img in the zip and place it on desktop or anywhere you can find.
Keep zip file in your phone storage.
Set USB Debugging On from Settings - Developer Options.
Connect the phone to the PC.
Click 1 - Click the Lightning icon.
Select 2 - Select the Fastboot Mode.
Click 3 - Click Ok.
Click 4 - Select Reboot Into Fastboot Via Adb and wait for the phone to go into fastboot mode. (Blue led).
Click 5 - Select Reboot Into Fastboot Via Fastboot and wait for the phone to go into fastboot mode. (Blue led).
Click 6 and 7 - Select the boot.img (from desktop if you have extracted there)
Click 8 - Reboot phone. After reboot, the phone will be in recovery mode.
In Recovery
-Whip Cache Partion,
-Cache,
-Dalvik Cache,
-Fix Permissions,
Flash The ROM
(Step By Step GUIDE With Images)
http://forum.xda-developers.com/showthread.php?t=1963961
little problem
dwarkesh2492 said:
The Reason Why You Are Getting A Bootloop.
Flashing of Boot.img is Not Proper.
What You Need To Do.
Flash boot.img using FLASHTOOL.
In the zip file you have got, extract boot.img in the zip and place it on desktop or anywhere you can find.
Keep zip file in your phone storage.
Set USB Debugging On from Settings - Developer Options.
Connect the phone to the PC.
Click 1 - Click the Lightning icon.
Select 2 - Select the Fastboot Mode.
Click 3 - Click Ok.
Click 4 - Select Reboot Into Fastboot Via Adb and wait for the phone to go into fastboot mode. (Blue led).
Click 5 - Select Reboot Into Fastboot Via Fastboot and wait for the phone to go into fastboot mode. (Blue led).
Click 6 and 7 - Select the boot.img (from desktop if you have extracted there)
Click 8 - Reboot phone. After reboot, the phone will be in recovery mode.
In Recovery
-Whip Cache Partion,
-Cache,
-Dalvik Cache,
-Fix Permissions,
Flash The ROM
(Step By Step GUIDE With Images)
http://forum.xda-developers.com/showthread.php?t=1963961
Click to expand...
Click to collapse
Don't know why, but it doesn't work for me.
Got a XPeria Go with formerly CM9 on it, updated to 4.1.2 and follow this guide: http://go.apeboys.org/index-de.html wich with CM9 worked perfectly. But, now with CM10 i got everytime a Bootloop and not able to fix it.
i used also your guide for flashing the boot.img but it even doesn't work
i tried it several times, and searched for reasons and another guids and tipps, but nothing worked, and since my x10 mini got a sim-lock wich i can't fix, im a little afraid about exotic tipps.
i got an open Bootloader and everything should be ready to do this....
so my question is: How can i fix that?
thanks for help and sry for my bad english.
Exact same problem here
Aaskereija said:
Don't know why, but it doesn't work for me.
Got a XPeria Go with formerly CM9 on it, updated to 4.1.2 and follow this guide: http://go.apeboys.org/index-de.html wich with CM9 worked perfectly. But, now with CM10 i got everytime a Bootloop and not able to fix it.
i used also your guide for flashing the boot.img but it even doesn't work
i tried it several times, and searched for reasons and another guids and tipps, but nothing worked, and since my x10 mini got a sim-lock wich i can't fix, im a little afraid about exotic tipps.
i got an open Bootloader and everything should be ready to do this....
so my question is: How can i fix that?
thanks for help and sry for my bad english.
Click to expand...
Click to collapse
I don't know what's the problem here. The last thing that would cause this would be the fact that I changed the .zip's name (I did that).
AlexBurnout77 said:
I don't know what's the problem here. The last thing that would cause this would be the fact that I changed the .zip's name (I did that).
Click to expand...
Click to collapse
Thank you for the answer.
I fixed the Problem be reflashing the rom and kernel.
How?
schpongo said:
Thank you for the answer.
I fixed the Problem be reflashing the rom and kernel.
Click to expand...
Click to collapse
BTW this is still a problem for me. Nothing seems to work. I flashed everything and wiped everything before flashing but still no satisfying outcome.
Hey guys so I'm in boot loop. Yes I know there are many guides all over saying how to fix it but I have tried many of them and they didnt work.
What happens is I start the phone, it shows the boot image and then restarts after a time.
I can boot into the Recovery mode by spamming the back button when the Logo comes. And can install zip files from the SD card.
I also have tried flashtool to restore it to stock but when i try flashing it detects my device "Device connected in flash mode" but when i try toflash it, it gives an error "Error flashing. Aborted".
I tried many many room whit kernels but stuck on bootloop every time, no way. I have never seen this problem before. Maybe bricked bootloader ?
I tried to relock the bootloader but doesnt help either.
Any help?
Ok, since you can boot into recovery can you flash you ROM.zip and try to boot into ROM? I also need some details:
- ROM you were using
- Kernel you were using
- How you got bootloop
Flashtool should work, try to recover using flashtool.
僕のLT18iから送られてきた
popthosegaskets said:
Ok, since you can boot into recovery can you flash you ROM.zip and try to boot into ROM? I also need some details:
- ROM you were using
- Kernel you were using
- How you got bootloop
Flashtool should work, try to recover using flashtool.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Before this happened i was using Ultimate HD 4.0 and Vengeance kernel ayame. The telephone was crashed and i didnt any backup. I tried to upgrade it to android 4.2 or 4.1 and the probleme begin I relocked the bootloader but doesnt help. I flashed it but doesnt accept any firmware, show Error flash bla bla bla Flash aborted. tried almost roms and kernels but doesnt help. I can install rooms and flash kernels, and boot up to recovery but after that is just stuck on boot animation or bootloop.:crying::crying::crying:
During the upgrade to JB, did you flash the kernel that came with it?
I assume you wanted to update to CM10/10.1? Vengeance Kernel is not compatible with JB. You need to flash UHD4 back to /system partition if you want to stick with UHD or flash the boot.img that came with the JB ROM.zip.
Do a clean install. Your phone should be working again if you do the steps correctly.
If you still have problems, you can reply to this thread or send me a PM if you wish to be more private about it.
Regards, 日焼けさん.
僕のLT18iから送られてきた
popthosega-skets said:
During the upgrade to JB, did you flash e ä'ökernel that came with it?
I assume you wanted to update to CM10/10.1? Vengeance Kernel is not compatible with JB. You need to flash UHD4 back to /system partition if you want to stick with UHD or flash the boot.img that came with the JB ROM.zip.
Do a clean install. Your phone should be working again if you do the steps correctly.
If you still have problems, you can reply to this thread or send me a PM if you wish to be more private about it.
Regards, 日焼けさん.9
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Thank you very much but i need steps . Plzz
Best regards
popthosegaskets said:
During the upgrade to JB, did you flash the kernel that came with it?
I assume you wanted to update to CM10/10.1? Vengeance Kernel is not compatible with JB. You need to flash UHD4 back to /system partition if you want to stick with UHD or flash the boot.img that came with the JB ROM.zip.
Do a clean install. Your phone should be working again if you do the steps correctly.
If you still have problems, you can reply to this thread or send me a PM if you wish to be more private about it.
Regards, 日焼けさん.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Sorry but i want tell you that the last i tried is this but doesnt help, stuck on boot animation. I gone be crazy.
OBS !!!!!! When i install rom and not working whit me i look on SD on pc if the installation files are there but nothing just the rom zip. I changed the SD but the same happened
Having issues realted to this one. Here's my device info. Hope it helps.
Device:
-> never been modded.
-> all stock rom.
-> stuck on a bootloop due to bluetooth.
It doesn't even have a recovery mod. So I'm pretty much stuck.
Can you help me out? And another thing, sorry for bringing this
old topic back. Haha.
Hello,
My son's gn is catched in a boot loop : google then X then google and so on
I wiped (factory reset) No result
I can access to recovery so i flashed 4.3 (JWR66Y) google factory image here : https://developers.google.com/android/nexus/images?hl=FR. The flash is completed but still catched in a boot loop.
I can even flash a custom recovery and all goes well i can perform anything in recovery mode but i'm still in the boot loop
when i restart the phone.
Any idea ?
Thanks in advance.
DarkGruf said:
Hello,
My son's gn is catched in a boot loop : google then X then google and so on
I wiped (factory reset) No result
I can access to recovery so i flashed 4.3 (JWR66Y) google factory image here : https://developers.google.com/android/nexus/images?hl=FR. The flash is completed but still catched in a boot loop.
I can even flash a custom recovery and all goes well i can perform anything in recovery mode but i'm still in the boot loop
when i restart the phone.
Any idea ?
Thanks in advance.
Click to expand...
Click to collapse
No idea anyone ? Could it be hardware related for instance ?
Wipe system, data, cache, dalvik cache and internal. Then flash factory image.
h4xx0rr said:
Wipe system, data, cache, dalvik cache and internal. Then flash factory image.
Click to expand...
Click to collapse
I did, about 5 or 6 times and still in boot loop.
ty
DarkGruf said:
Hello,
My son's gn is catched in a boot loop : google then X then google and so on
I wiped (factory reset) No result
I can access to recovery so i flashed 4.3 (JWR66Y) google factory image here : https://developers.google.com/android/nexus/images?hl=FR. The flash is completed but still catched in a boot loop.
I can even flash a custom recovery and all goes well i can perform anything in recovery mode but i'm still in the boot loop
when i restart the phone.
Any idea ?
Thanks in advance.
Click to expand...
Click to collapse
What caused this ? Did you flash a ROM or something ?
Bootloader is unlocked (padlock symbol visible) right? If you've previously locked it, then Recovery won't do anything if you haven't unlocked.
FredFS456 said:
Bootloader is unlocked (padlock symbol visible) right? If you've previously locked it, then Recovery won't do anything if you haven't unlocked.
Click to expand...
Click to collapse
Yes it's unlocked, I can even flash a custom recovery.
Atishay Jain said:
What caused this ? Did you flash a ROM or something ?
Click to expand...
Click to collapse
It's my son's device so i don't know really but I'mquite sure he did not flash anything. I do it for him when he needs.So no, I have no idea. One minute before it was working one minut after it reboot itself and stays in boot loop.
DarkGruf said:
It's my son's device so i don't know really but I'mquite sure he did not flash anything. I do it for him when he needs.So no, I have no idea. One minute before it was working one minut after it reboot itself and stays in boot loop.
Click to expand...
Click to collapse
Was there any mod installed (something that u flashed to make the phone faster) like the v6 supercharger or any other mod ?
Also I think that you should try updating your recovery and then flashing a rom onto your device. I think CM is available for your device (which I assume to be a nexus as you have mentioned the nexus system images page in the OP). Search the xda threads for a ROM and try flashing it.
Atishay Jain said:
Was there any mod installed (something that u flashed to make the phone faster) like the v6 supercharger or any other mod ?
Also I think that you should try updating your recovery and then flashing a rom onto your device. I think CM is available for your device (which I assume to be a nexus as you have mentioned the nexus system images page in the OP). Search the xda threads for a ROM and try flashing it.
Click to expand...
Click to collapse
What is v6 supercharger???
h4xx0rr said:
What is v6 supercharger???
Click to expand...
Click to collapse
Its a script to improve performance. Anyways u seem to be unaware of that so it means you've not done anything like installing a MOD, Try updating the recovery.
Can you give me link for supercharger?
Atishay Jain said:
Was there any mod installed (something that u flashed to make the phone faster) like the v6 supercharger or any other mod ?
Also I think that you should try updating your recovery and then flashing a rom onto your device. I think CM is available for your device (which I assume to be a nexus as you have mentioned the nexus system images page in the OP). Search the xda threads for a ROM and try flashing it.
Click to expand...
Click to collapse
No, I did not intall any mod, last rom i had on it was a modaco but when I gave thephone to my son I just pushed the last stock root rom i picked from xda 4.2 I think. Still I goona try what u sayed, I did not try to push a custom rom only google images. TY, I will tell what happens. And yes it's an European Samsung Galaxy Nexus as we are in Galaxy nexus section
h4xx0rr said:
Can you give me link for supercharger?
Click to expand...
Click to collapse
Here you go :
http://forum.xda-developers.com/showthread.php?t=2733251
There are also a few other tricks and MODs listed there if u want to improve your phone's performance.
Rate the thread well if it helped you.:good:
Looks allot like my girlfriends phone and this thread http://forum.xda-developers.com/galaxy-nexus/help/normal-boot-loop-problem-t2875961
factory reset does not do/wipe anything, pushed files don't stay on the device after reboot, flashing new rom from PC does not stick
Nexus seems to be in some kind of readonly mode.
Hi,
I made a CM14 update yesterday, but since then, my phone boots in recovery mode. I tried to reinstall TWRP, in current and previous versions, and other roms (I can flash), but nothing works; each time I reboot, TWRP appears...
Any hint ?
Thanks very Much !
gdoucou said:
Hi,
I made a CM14 update yesterday, but since then, my phone boots in recovery mode. I tried to reinstall TWRP, in current and previous versions, and other roms (I can flash), but nothing works; each time I reboot, TWRP appears...
Any hint ?
Thanks very Much !
Click to expand...
Click to collapse
Try to install my latest BETA (check my signature)
steadfasterX said:
Try to install my latest BETA (check my signature)[/QUOT
Hi, thanks for your answer. I tried, but it still reboots on TWRP... (tried to install AICP).
There's an error message when installing :
patching system image unconditionnally
E:unknown command [log]
But it keeps going on with "dectected filesystem ext4 for /dev/boot [...]
Then it reboots in recovery...
Click to expand...
Click to collapse
gdoucou said:
steadfasterX said:
Try to install my latest BETA (check my signature)[/QUOT
Hi, thanks for your answer. I tried, but it still reboots on TWRP... (tried to install AICP).
There's an error message when installing :
patching system image unconditionnally
E:unknown command [log]
But it keeps going on with "dectected filesystem ext4 for /dev/boot [...]
Then it reboots in recovery...
Click to expand...
Click to collapse
Please try build 186
Click to expand...
Click to collapse
dont work for me same Probleme
TooThPicK said:
dont work for me same Probleme
Click to expand...
Click to collapse
Try my latest beta and if that is not working build 186
And which nightly causes that problem?
i think its not the recovery i test the cyanogen and this dont work
test installing stock but dont work
testet both not working
no Rom is working evrytime its boot to recovery
TooThPicK said:
i think its not the recovery i test the cyanogen and this dont work
test installing stock but dont work
testet both not working
no Rom is working evrytime its boot to recovery
Click to expand...
Click to collapse
Which cm version? tell exact build date.
Try to reflash stock kdz
Is there a way to Flash kdz from fastboot or recovery lgup dont find my device
ok i find the download mode now lgup find my device i downloading 20g and test
The issue is due to change in Google code not being compatible with TWRP.
I had the same issue, I flashed stock ROM with LGUP and then flashed CM14.1 after that.
Once your back up and running you can't use the in built updater, you have to download the update, manuay reboot to recovery and then flash.
Lgup dont find my device i only have recovery and fastbood
ceanth said:
The issue is due to change in Google code not being compatible with TWRP.
I had the same issue, I flashed stock ROM with LGUP and then flashed CM14.1 after that.
Once your back up and running you can't use the in built updater, you have to download the update, manuay reboot to recovery and then flash.
Click to expand...
Click to collapse
The change in Google code was the reason for one of the beta series I made. I was able to fix that in twrp even when this is no twrp issue. The internal updater worked fine afterwards when using any build after 15 of dec while using my latest beta.
That's why I ask several times what cm build they used (both do not answered this yet).
This is important so I can reproduce the issue and may can release a new twrp workaround if possible.
.
TooThPicK said:
Lgup dont find my device i only have recovery and fastbood
Click to expand...
Click to collapse
Not sure dude, best to post in the dedicated TWRP or cm14.1 thread.
its fixt thank you for your help the trick is turn off the g4 hold the + button and plugin the cabel now the device comes to downloadmode and now lgup is working
---------- Post added at 02:30 PM ---------- Previous post was at 02:28 PM ----------
steadfasterX said:
That's why I ask several times what cm build they used (both do not answered this yet).
This is important so I can reproduce the issue and may can release a new twrp workaround if possible.
.
Click to expand...
Click to collapse
on my is the nigtly from 23.12
I got the same problem booting permanently in TWRP.
Flashing the build (02.12.) I had before also doesn't work.
Some kind of tips here?
xXfreshXx said:
I got the same problem booting permanently in TWRP.
Flashing the build (02.12.) I had before also doesn't work.
Some kind of tips here?
Click to expand...
Click to collapse
Install my latest beta. I know that this do not solve the problem but then after flashing it try to boot into system. This will fail. Then pull the recovery log and provide it on http://paste.omnirom.org
If you don't know how to get that log it is easy. Check my FAQ #4 A.
http://forum.xda-developers.com/showpost.php?p=68249027&postcount=3
.
steadfasterX said:
Install my latest beta. I know that this do not solve the problem but then after flashing it try to boot into system. This will fail. Then pull the recovery log and provide it on http://paste.omnirom.org
.
Click to expand...
Click to collapse
Thanks for your reply
https://paste.omnirom.org/view/6e5948df
xXfreshXx said:
Thanks for your reply
https://paste.omnirom.org/view/6e5948df
Click to expand...
Click to collapse
Hm . This is really after a boot into system??...
Ok as I cannot see relevant data pls do the same again but with build 186 now. Provide the log again. The reason is that this build handles the bootloader commands in an other way and I may see then what I wanna see.
Thx
.
Hm . This is really after a boot into system??...
Ok as I cannot see relevant data pls do the same again but with build 186 now. Provide the log again. The reason is that this build handles the bootloader commands in an other way and I may see then what I wanna see.
Thx
.
Click to expand...
Click to collapse
Here you are.
https://paste.omnirom.org/view/594df4ce
xXfreshXx said:
Here you are.
https://paste.omnirom.org/view/594df4ce
Click to expand...
Click to collapse
Hm the reason for that reboot lays somewhere else...
Please tell me exactly what you had done to produce that loop:
Which exact version of cm installed before upgrading?
Upgraded with internal cm updater or by flashing new zip in twrp?
The above would help me to reproduce the issue.
Besides the short questions above it would be great if you could test 2 things for me and if not skip to 3 (if you're in hurry):
1. The hw key combo test
2. The force twrp test
3. Last resort LG up
1. The hw key combo test
Flash the latest beta twrp and reboot into this twrp
Create a full backup if not already done so!!!
Power off the device and pull out the battery
Use the hardware key combo to get into factory reset screen (press vol down + power and keep them pressed. plugin battery. Wait until you see the LG logo and then release only the power button for 1 sec then press it again and keep both pressed until you see the factory reset screen)
Follow through this process and twrp will showing up without resetting anything
Grab the recovery log and paste it again
Then try to reboot to system
2. The force twrp test
If the first method hasn't worked it would be great to see the log anyways but then try the the following:
Boot into twrp (doesn't matter how for this test)
Flash again the latest twrp beta with twrp itself (choose img button at the bottom) and now when getting asked flash it to BOOT partition! Yes this is no problem or causes any damages. Just do it.
Then choose reboot into system and twrp will popup again (but now it starts from boot partition)
Now install the cm version of your choice or any other rom
Do NOT reboot yet
before rebooting grab the recovery log again and paste it again
3. LG up
If the above does not work and as I believe you need your device back soon the best bet would be do a full backup with the latest twrp beta version. Then use LG up to flash stock kdz again to get a working device.
.