Database Users

Secure Booting Error! Cause: Boot certification verify.

Hello there,
I updated my LG P700 to the v20c 4.1.2 JB version. After that, I couldn't find a wayu to root it, but found Framaroot app and succeeded with it. I got a little cocky how easy it was and downloaded ROM Manager. From it, I chose the CWM installation option and the window said it was a success. However, when I clicked to reboot into the recovery, only this little error appeared - "Secure Booting Error! Cause: Boot certification verify." in the left uper corner of the screen. Nothing worked, so I took out the battery and after turning the phone on, I noticed that all the internal memory got factory reseted or something like that and it is just a blank fresh android - all data was lost.
Long story short: flashing recovery from ROM Manager caused the wipe of the memory.
What happened?

[UPDATE] It could be caused by not unlocking the bootloader. I assumed that ROM Manager checks these things or flashes them with the recovery.
If that's the case (pls tell me) then I should unlock the bootloader. Maybe with this - http://forum.xda-developers.com/showthread.php?t=2197429 Does it work with v20c 4.1.2 android on my LG L7?

yes, the bootloader is locked, you need to unlock

Thanks, now I'm at least on to something. Does the method from the link works on v20c 4.1.2. version?
Sent from my LG-P700 using xda app-developers app

Macors said:
Thanks, now I'm at least on to something. Does the method from the link works on v20c 4.1.2. version?
Sent from my LG-P700 using xda app-developers app
Click to expand...
Click to collapse
it doesn`t matter if you have ICS or JB, it must work

I tried unlocking the bootloader with the Flash_Bootloader.bat file, but the error windows flashes only for a split second. I barely caught it and attached the screenshot of it saying "the system cannot find the path specified". What should I do now?
Phone connected in pc software mode, debuggin is on.
[Update] I moved the CWM folder directly to the local disk C and it worked, but didn't reboot the phone. I had to unplug it and then turn on. How to check if my bootloader is unlocked? I don't want any more fails with flashing the recovery ;/

Macors said:
I tried unlocking the bootloader with the Flash_Bootloader.bat file, but the error windows flashes only for a split second. I barely caught it and attached the screenshot of it saying "the system cannot find the path specified". What should I do now?
Phone connected in pc software mode, debuggin is on.
[Update] I moved the CWM folder directly to the local disk C and it worked, but didn't reboot the phone. I had to unplug it and then turn on. How to check if my bootloader is unlocked? I don't want any more fails with flashing the recovery ;/
Click to expand...
Click to collapse
you were needed to write adb reboot to rebbot your phone after, and the only way to chech the bootlaoder is to go on download mode or recovery

Everything is working, just rebooted into Recovery from the rom manager. By the way, how does this adb work? Do I have to run the .exe file after the .bin ?

Macors said:
Everything is working, just rebooted into Recovery from the rom manager. By the way, how does this adb work? Do I have to run the .exe file after the .bin ?
Click to expand...
Click to collapse
start - run cmd - cd %ADB% - and here you are

same here
Im using an lg lucid vs840 and is recently rooted, i downloaded rom manager and cyanogen mod 11, but when i try to install rom from sd card it reboots saying,
boot errer cause boot certification verify
Enter fast reboot...
Enter fast reboot...
Long time no see!
I can still use my phone but i cant install a new rom, any one help?
Thank you for reading.

lol nobody ever answers this same question many times on this site.... sorry first post but I get all my info from hereeeeee for a long time now

How to fix very bricked LG V20 from bad rooting?

jeanclaudevandamme said:
Right, I've figured out where things have went wrong but still can't find a fix
1) So after Step 14 after running the BAT files all cmd windows closed. I then clicked step3.bat while in fastboot mode. because he did not explain clearly where you were supposed to get CMD window for commands in Step 16.
I had used CMD / ADB / Fastboot years ago, but I had forgotten how they worked exactly, as the instructions for the previous phones I have rooted were so much better written.
later i discovered how to see what was inside a BAT file (use notepad to open it) so step3.BAT contained instructions to flash "boot1.img" which came with the Dirty Santa v20 files. I don't know what model that boot image was taken from. it also contained instructions to flash a twrp file name that didn't exist (so I guess nothing would have gotten flashed).
2) later I was able to launch into fastboot mode and manually flash the correct twrp file onto the phone. then led me being able to get into twrp recovery to flash kernel + SU.
However phone still didn't boot, presumably of the mistake was previously by clicking Step3.BAT, which flashed a "boot1.img" from dirty santa files
Also when going into download mode, the phone would crash with static 1 second after connection.
3) At the time, I didn't know the difference between aboot and boot files. So I went into fastboot and flashed abootbackup.img
I still don't know fully what aboot does. But the effect it has is it locked the bootloader, so i am no longer able to flash anything with fastboot. writing the old aboot.img has caused my device to go into a corrupt bootloop, cannot launch into recovery.
I think that if I flashed bootbackup.img then things might have worked out ok. i had 2 choices and I picked the wrong one, but that's gone now.
flashing the abootbackup.img also had another effect, download mode no longer crashed with static after 1 second, however a new error code came up when download mode is launched <633A B50>, the phone acts like a firmware is currently trying to be flashed but stuck at 0% even just by launching download mode.
I'm guessing there may be some sort of variant mismatch between the boot1.img and the abootbackup.img as the boot1.img wouldn't have originally come from my phone? As well as the other stuff pushed onto device in Step2.BAT
eithe way, LG Bridge / LGUP do not recognise model even with Uppercut.. LG Flash 2014 has the error messge of "connection to server failed", I tried letting it run in the background without closing error message as suggested in that thread, but I guess because of my 633A B50 error message, flashing did not occur in the background like other people.
----------------
I don't know where to go from here exactly. because
1) boot1.img, that came with dirtysanta files, which model / variant did it come from?
2) what LGUP_common.dll will recognise my device now? I know someone patched their DLL, but how do you patch a DLL using hex editor and how to make the DLL recognise my presumably mismatched device?
3) i don't know what the <633A B50> error message means exactly
------
https://forum.xda-developers.com/v20/help/help-h990ds-t3650303
looks like someone did something similar to what I did. he didn't get answers to his questions and he hasn't been logged in since August..
Click to expand...
Click to collapse
It's more bricked than usual..

Have a go at this?
I like using the LGUP Patched DLL for H91810J. It seems to recognize all variants.
as a last resort use LG Bridge, refurbish. it will repair all sorts of half installs and messed up partitions. the only thing is : IT WILL BRING YOUR BUILD UP TO 10q=================WHICH IS NOT ROOTABLE!!======================

Just in case this issue has not been resolved. I did the same thing 10 minutes ago. I flashed the wrong abootbackup.img (10c) instead of 10d.
All you have to do is open LGUP and if the device won't be recognise, just run the Uppercut tool and the device will show up. Flash your .kdz file and the phone should be running once again.

Axon 7 (A2017G) Brick.

I had stock android 7, used the toolkit, "Unlocked" the bootloader, after that there was a part with erasing all data to factory due to an error, something along the lines there was a pin or password detected, and after I pressed reset the screen went black, and when it tries to boot it shows ZTE for a second and then it vibrates and shuts off instantly. So I can get it in to edl mode and I see the Qualcomm HS-USB QDLoader 9008 in my devices, but I can't find any thread to fix this. Tried flashing stock firmwares via MiFlash, no luck. And the thing is, most roms I download give me a batch of files in a zip, if I put them in a folder and try to flash I get this - Object reference not set to an instance of an object. Help asap, because I am having a horrible time using my partially destroyed S6 Edge Plus. If I spelled smth wrong sorry, Russian here.

This is what I had - My device is stuck on an 'Enter your password to start Android' screen.
Unfortunately this requires a factory reset.
1) Boot your device into recovery mode by pressing and holding the power and volume up buttons for 10-15 seconds.
2) Stock Recovery: Use the volume down key to go down to 'Wipe data/factory reset' and press power to select. Press the volume down key again to go down to 'Yes' and press power to select.
TWRP Recovery: Tap "Wipe" < Tap "Advanced Wipe" < Check the box next to "data" < Tap "Repair or change file system" < Tap "EXT4" < Swipe to confirm.
3) Reboot your device.

Jazkade said:
I had stock android 7, used the toolkit, "Unlocked" the bootloader, after that there was a part with erasing all data to factory due to an error, something along the lines there was a pin or password detected, and after I pressed reset the screen went black, and when it tries to boot it shows ZTE for a second and then it vibrates and shuts off instantly. So I can get it in to edl mode and I see the Qualcomm HS-USB QDLoader 9008 in my devices, but I can't find any thread to fix this. Tried flashing stock firmwares via MiFlash, no luck. And the thing is, most roms I download give me a batch of files in a zip, if I put them in a folder and try to flash I get this - Object reference not set to an instance of an object. Help asap, because I am having a horrible time using my partially destroyed S6 Edge Plus. If I spelled smth wrong sorry, Russian here.
Click to expand...
Click to collapse
I had a similar problem on my 2017U model after flashing a .zip that was supposed to remove the "bootloader is unlocked" screen that shows up after you unlock the bootloader. Long story short, the .zip wasn't meant for U models. Only G. So my phone was in a worse situation than yours and would not power on. You'll need to download an EDL recovery firmware .zip for your phone and place it within the toolkits folders manually and then go through the steps of the toolkit which I'll try to help you do.
First, download the full stock B09 (G) firmware from here. You can OTA update to the latest firmware after a successful flash. It's okay to flash an older firmware in this situation.
Once done, navigate to C:\Axon7Development\Axon7Toolkit\MiFlash\B09\ (copy/move the full .zip of the B09 firmware you downloaded in the first step into this folder) If the B09 folder doesn't exist under \MiFlash, create it manually.
Run the toolkit again from the start and type 11 "RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)" and hit enter. On the next screen type in the number that will restore B09. It should tell you how to put the phone in EDL mode and automatically open MiFlash. Make sure to follow the steps and paste the directory path of the firmware in the top bar in MiFlash. After you pasted it his Flash and it should successfully flash the firmware. If it gives you an error or times out, unplug the phone and try a different USB port or USB cable. It's obviously recommended you use the one that came with the phone. My first attempt at MiFlash timed out and didn't flash anything. I tried a different USB port and then it flashed.
After it flashes the firmware, leave the phone plugged in and hold down the power button for about 10 seconds until it restarts out of EDL. From there you should have a working phone again with some exceptions. It'll be on an older firmware so I would recommend booting into stock recovery and factory resetting data and wiping your cache. Then restart the phone and do an OTA update to the latest firmware. After you reach the latest firmware you can then use the toolkit for whatever you need.
Sidenote, your English is very good considering you're Russian. No need to apologize because your post had no spelling errors. :highfive:

brian117 said:
I had a similar problem on my 2017U model after flashing a .zip that was supposed to remove the "bootloader is unlocked" screen that shows up after you unlock the bootloader. Long story short, the .zip wasn't meant for U models. Only G. So my phone was in a worse situation than yours and would not power on. You'll need to download an EDL recovery firmware .zip for your phone and place it within the toolkits folders manually and then go through the steps of the toolkit which I'll try to help you do.
First, download the full stock B09 (G) firmware from here. You can OTA update to the latest firmware after a successful flash. It's okay to flash an older firmware in this situation.
Once done, navigate to C:\Axon7Development\Axon7Toolkit\MiFlash\B09\ (copy/move the full .zip of the B09 firmware you downloaded in the first step into this folder) If the B09 folder doesn't exist under \MiFlash, create it manually.
Run the toolkit again from the start and type 11 "RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)" and hit enter. On the next screen type in the number that will restore B09. It should tell you how to put the phone in EDL mode and automatically open MiFlash. Make sure to follow the steps and paste the directory path of the firmware in the top bar in MiFlash. After you pasted it his Flash and it should successfully flash the firmware. If it gives you an error or times out, unplug the phone and try a different USB port or USB cable. It's obviously recommended you use the one that came with the phone. My first attempt at MiFlash timed out and didn't flash anything. I tried a different USB port and then it flashed.
After it flashes the firmware, leave the phone plugged in and hold down the power button for about 10 seconds until it restarts out of EDL. From there you should have a working phone again with some exceptions. It'll be on an older firmware so I would recommend booting into stock recovery and factory resetting data and wiping your cache. Then restart the phone and do an OTA update to the latest firmware. After you reach the latest firmware you can then use the toolkit for whatever you need.
Sidenote, your English is very good considering you're Russian. No need to apologize because your post had no spelling errors. :highfive:
Click to expand...
Click to collapse
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.

Jazkade said:
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Click to expand...
Click to collapse
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable

Jazkade said:
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Click to expand...
Click to collapse
Did you create the B09 folder in the MiFlash directory? I also had errors downloading firmwares through the toolkit, which is why I had to do it manually and move the firmware into the proper directory for the toolkit.

brian117 said:
Did you create the B09 folder in the MiFlash directory? I also had errors downloading firmwares through the toolkit, which is why I had to do it manually and move the firmware into the proper directory for the toolkit.
Click to expand...
Click to collapse
Yes I did

Choose an username... said:
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Click to expand...
Click to collapse
Can you give me a link pls?

Choose an username... said:
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Click to expand...
Click to collapse
Flashing in progress.. please may this work..

Oh yeis boiz, the phone is alive! And the main lol is, we have a guy that fixes devices for a living, and he was trashtalking that the Axon 7 is a trash phone and fixing it is a piece of cake, and he failed, and here I am thanks to you with a woring phone! I love you people, and xda in general!

EDIT: Seems you got it working. Congrats.

Jazkade said:
Oh yeis boiz, the phone is alive! And the main lol is, we have a guy that fixes devices for a living, and he was trashtalking that the Axon 7 is a trash phone and fixing it is a piece of cake, and he failed, and here I am thanks to you with a woring phone! I love you people, and xda in general!
Click to expand...
Click to collapse

Choose an username... said:
Click to expand...
Click to collapse
After I unlocked the bootloader via the toolkit by bkores, I get a message "To start android enter your password" even though it was a stock system with no password. Like I got every possible error and solved it and now this, just why?

Jazkade said:
After I unlocked the bootloader via the toolkit by bkores, I get a message "To start android enter your password" even though it was a stock system with no password. Like I got every possible error and solved it and now this, just why?
Click to expand...
Click to collapse
that's totally normal. Your internal storage is encrypted, you have to go into TWRP and format data (not wipe, format). Anyways by unlocking you lose all of your data so it's not like you lose anything
If it doesn't work, then you'll have to change the data partition's filesystem because it may be in F2FS. Change it back to ext4 if that happens

Choose an username... said:
that's totally normal. Your internal storage is encrypted, you have to go into TWRP and format data (not wipe, format). Anyways by unlocking you lose all of your data so it's not like you lose anything
If it doesn't work, then you'll have to change the data partition's filesystem because it may be in F2FS. Change it back to ext4 if that happens
Click to expand...
Click to collapse
I don't have TWRP, firs I Unlocked the bootloader, now I try to flash TWRP and get error due to the force encryption on Nougat, and I can't find a way to disable it, also now when I try to boot to stock recovery the led flashes for a milisecond and powers off.

Jazkade said:
I don't have TWRP, firs I Unlocked the bootloader, now I try to flash TWRP and get error due to the force encryption on Nougat, and I can't find a way to disable it, also now when I try to boot to stock recovery the led flashes for a milisecond and powers off.
Click to expand...
Click to collapse
Enter fastboot and type the command "fastboot erase userdata

Choose an username... said:
Enter fastboot and type the command "fastboot erase userdata
Click to expand...
Click to collapse
adb reboot fastboot and it just reboots normally.

Jazkade said:
adb reboot fastboot and it just reboots normally.
Click to expand...
Click to collapse
Well whatever then just install TWRP. Use controllerboy's guide

Choose an username... said:
Well whatever then just install TWRP. Use controllerboy's guide
Click to expand...
Click to collapse
idk how to downgrade to marshmellow.

Choose an username... said:
Well whatever then just install TWRP. Use controllerboy's guide
Click to expand...
Click to collapse
downgraded, unlocked, twrp is up and running

Error in installing twrp

Hy everyone ineed help..
I have h990ds in nouget android security before 2016.
I try to root but in the middle of proses,its error, i try to flashing by lgup but the screen only flashboot mode. :crying::crying:
The some words in my screen:
Fastboot mode(red color)
Product name_msm8996 64gb
Varian_msm8996 64gb
Hw version_rev10
Bla...
Serial number -lgus996af7da36 (my type h990ds)
Secure boot-disable
Lock state_lock
[1090]
[1140]fastboot mode started
There 3 steps .bat after runfirsttime.bat
An i click step3 after step 2.

nuqudlover said:
Hy everyone ineed help..
I have h990ds in nouget android security before 2016.
I try to root but in the middle of proses,its error, i try to flashing by lgup but the screen only flashboot mode. :crying::crying:
The some words in my screen:
Fastboot mode(red color)
Product name_msm8996 64gb
Varian_msm8996 64gb
Hw version_rev10
Bla...
Serial number -lgus996af7da36 (my type h990ds)
Secure boot-disable
Lock state_lock
[1090]
[1140]fastboot mode started
There 3 steps .bat after runfirsttime.bat
An i click step3 after step 2.
Click to expand...
Click to collapse
The good news is that you've got the dirtysanta bootloader installed (that's why it's reporting us996) so you should be able to fix it without using LG UP and having to redo most of the process.
Install twrp by doing fastboot flash path/to/twrp.img .then pull the battery when done. Then enter twrp by using to volume key method (hold volume down, press power until the screen turns on, then tap power repeatedly until a menu asking to factory reset appears, say yes (while twrp is installed it won't actually wipe anything).)
Flash a rom (a stock one is here), and magisk.
If you can't use an sdcard to get them accessible to the phone in twrp, in twrp you can go into advanced then sideload and connect to a PC and do adb sideload path/to/rom-or-magisk.zip

Phoenix591 said:
The good news is that you've got the dirtysanta bootloader installed (that's why it's reporting us996) so you should be able to fix it without using LG UP and having to redo most of the process.
Install twrp by doing fastboot flash path/to/twrp.img .then pull the battery when done. Then enter twrp by using to volume key method (hold volume down, press power until the screen turns on, then tap power repeatedly until a menu asking to factory reset appears, say yes (while twrp is installed it won't actually wipe anything).)
Flash a rom (a stock one is here), and magisk.
If you can't use an sdcard to get them accessible to the phone in twrp, in twrp you can go into advanced then sideload and connect to a PC and do adb sideload path/to/rom-or-magisk.zip
Click to expand...
Click to collapse
After use adb fastboot flash recovery twrp.img, there's new problem.
Using volume key mode my screen is blank, just like broken TV.. :crying::crying:

nuqudlover said:
After use adb fastboot flash recovery twrp.img, there's new problem.
Using volume key mode my screen is blank, just like broken TV.. :crying::crying:
Click to expand...
Click to collapse
to totally back out and bring your phone to totally stock use download mode (from powered off hold volume UP while connecting to the pc). The screen will be still messed up but it will still work on the pc.
Use patched LG UP in partition dl mode to flash everything with a stock h990(ds) kdz.
Once you start using dirtysanta next time (if you decide to try again) be very very careful when using LG UP (easier to just use stock flashabile zip) unless you want to redo the above and flash EVERYTHING back to stock (if you ever flash the aboot partition in LG UP and anything ISN'T stock it will brick you! This mostly applies to partition dl mode since upgrade mode flashes everything, but partition dl mode is the only mode you can even potentially flash things and keep root (but I don't encourage this... its easier and saferto just use zips in TWRP to flash firmware (mostly stock basedrom or so called stock flashible zips tend to also flash all of the firmware except parts needed to keep root. )

Phoenix591 said:
to totally back out and bring your phone to totally stock use download mode (from powered off hold volume UP while connecting to the pc). The screen will be still messed up but it will still work on the pc.
Use patched LG UP in partition dl mode to flash everything with a stock h990(ds) kdz.
Once you start using dirtysanta next time (if you decide to try again) be very very careful when using LG UP (easier to just use stock flashabile zip) unless you want to redo the above and flash EVERYTHING back to stock (if you ever flash the aboot partition in LG UP and anything ISN'T stock it will brick you! This mostly applies to partition dl mode since upgrade mode flashes everything, but partition dl mode is the only mode you can even potentially flash things and keep root (but I don't encourage this... its easier and saferto just use zips in TWRP to flash firmware (mostly stock basedrom or so called stock flashible zips tend to also flash all of the firmware except parts needed to keep root. )
Click to expand...
Click to collapse
I already use lgup pacher, when connected the message unknown model
Can i using flash laf.bin from fastbootmode?

nuqudlover said:
I already use lgup pacher, when connected the message unknown model
Can i using flash laf.bin from fastbootmode?
Click to expand...
Click to collapse
But did you use partition dl mode? It alone bypasses the model checks.
Partition dl mode isn't in regular lg up, you need the special patched version I linked (replace the files of your regular lg up with the special version)

Phoenix591 said:
But did you use partition dl mode? It alone bypasses the model checks.
Partition dl mode isn't in regular lg up, you need the special patched version I linked (replace the files of your regular lg up with the special version)
Click to expand...
Click to collapse
I already put your special patched to my Lgup..

nuqudlover said:
I already put your special patched to my Lgup..
Click to expand...
Click to collapse
Try uppercut then. Use upgrade mode if it works but partition dl mode is missing. Note uppercut asks for lg up version 1.14 . I can't remember what version the patched one is but you may have to reinstall that version instead.

LG G4 H81520p bootloader unlocked, Download mode avaliable, cant flash anything

Hello everybody. Im asking for help and im pretty desperate for my issue.
I have LG G4 h815 20p which was rooted few years back. Then the phone died and got re-balled recently and it works now. But i can not access twrp by using Volume Down and Power buttons combination. I can go to Download mode where i can updated firmware using LG UP and it will be processed to the end and after the required reboot phone stays black and recognized only as qualcom device in device manager.
I can not use ADB as it will never show any devices under adb device neither fastboot devices. Drivers are installed. Tried bunch of different versions on both win10 and win7 but no luck. I also tried installing those on ubuntu, where the phone is seen as a device under lsusb but not under fastboot or adb.
I just want to get the phone up and running. NO matter if i unroot or keep it rooted. It wont be used as daily phone but im eager to fix it.
The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
Tried LG UP, LG flash tool neither helped. LG Flash tool wont even end as LG UP finishes but wont boot after the reboot when process is completed.
Any help please will be extremely highly appreciated. I am also willing to arrange team viewer if necessary for easiness.

sbelcovski said:
Hello everybody. Im asking for help and im pretty desperate for my issue.
I have LG G4 h815 20p which was rooted few years back. Then the phone died and got re-balled recently and it works now. But i can not access twrp by using Volume Down and Power buttons combination. I can go to Download mode where i can updated firmware using LG UP and it will be processed to the end and after the required reboot phone stays black and recognized only as qualcom device in device manager.
I can not use ADB as it will never show any devices under adb device neither fastboot devices. Drivers are installed. Tried bunch of different versions on both win10 and win7 but no luck. I also tried installing those on ubuntu, where the phone is seen as a device under lsusb but not under fastboot or adb.
I just want to get the phone up and running. NO matter if i unroot or keep it rooted. It wont be used as daily phone but im eager to fix it.
The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
Tried LG UP, LG flash tool neither helped. LG Flash tool wont even end as LG UP finishes but wont boot after the reboot when process is completed.
Any help please will be extremely highly appreciated. I am also willing to arrange team viewer if necessary for easiness.
Click to expand...
Click to collapse
Boot to fastboot and exec
fastboot format userdata
(will obviously erase the whole device including photos etc)
If that does not help you can use SALT to flash TWRP to the BOOT (!) partition. For that you must start SALT from the cli with --experimental argument. If you plan to use SALT I recommend using the latest mAid njghtly which has all already installed.
For flashing with SALT you also must do a custom backup of the sbl1 partition and place the twrp image in the same dir where the sbl1 backup is.
Sent from my OnePlus 7T Pro using XDA Labs

steadfasterX said:
Boot to fastboot and exec
fastboot format userdata
(will obviously erase the whole device including photos etc)
If that does not help you can use SALT to flash TWRP to the BOOT (!) partition. For that you must start SALT from the cli with --experimental argument. If you plan to use SALT I recommend using the latest mAid njghtly which has all already installed.
For flashing with SALT you also must do a custom backup of the sbl1 partition and place the twrp image in the same dir where the sbl1 backup is.
Sent from my OnePlus 7T Pro using XDA Labs
Click to expand...
Click to collapse
Hey, Thank you.
I found your stuff uploaded, but i really cant figure it out. Whenever i press Volume UP and Power button to keep them 6-7sec then plug usb cable, the phone misses the chance to go into download mode. So i have no opportunity to go into fastboot. But i can go in download mode but neither fastboot or salt finds the device.
Could you please provide some more info?

sbelcovski said:
Hey, Thank you.
I found your stuff uploaded, but i really cant figure it out. Whenever i press Volume UP and Power button to keep them 6-7sec then plug usb cable, the phone misses the chance to go into download mode. So i have no opportunity to go into fastboot. But i can go in download mode but neither fastboot or salt finds the device.
Could you please provide some more info?
Click to expand...
Click to collapse
fastboot and download mode are complete different things. you cannot use fastboot commands in download mode.
you have to provide more info:
how do you run mAid? VirtualBox or from an USB stick (recommended)
share the debug log of SALT when your device is in download mode (Advanced menu -> debug log -> upload button -> share just the link)
boot your device in download mode and THEN start mAid first could also help
.-

steadfasterX said:
fastboot and download mode are complete different things. you cannot use fastboot commands in download mode.
you have to provide more info:
how do you run mAid? VirtualBox or from an USB stick (recommended)
share the debug log of SALT when your device is in download mode (Advanced menu -> debug log -> upload button -> share just the link)
boot your device in download mode and THEN start mAid first could also help
.-
Click to expand...
Click to collapse
Hello again.
I figured mAid out. I run from live usb, and i can connect to phone and get the device information through Salt..
What i did:
- i use experimental flag with root privileges and device is read and comes info that my Laf fw does not support direct flashing. (i cant figure it out how this works),
- i made backup of sbl1 partition, downloaded twrp image twrp-3.3.1-PREVIEW-196_g4_MM.img, placed the twrp image in same folder where the backup of sbl1 is.
- Now i dont know how to flash the the twrp to the boot partition. I tried to find some guides but no luck. Yesterday for some reason i had Flash button in salt on the bottom, today it is not there. The way i start salt is by browsing inside /home/android/Desktop/LG directory and use sudo ./SALT.desktop --experimental command. I use the latest mAid from your file server 4.19.126-1-MANJARO - mAid_v2020-07-14_23-43_x86_64_forgetful.iso.
3 attachments are uploaded bellow. The debug log from salt was unable to upload and gave bunch of package errors, so it is attached bellow in a txt file as well.
The phone keeps stable connection in download mode.
Please advice. I am very grateful.

sbelcovski said:
Hello again.
I figured mAid out. I run from live usb, and i can connect to phone and get the device information through Salt..
What i did:
- i use experimental flag with root privileges and device is read and comes info that my Laf fw does not support direct flashing. (i cant figure it out how this works),
- i made backup of sbl1 partition, downloaded twrp image twrp-3.3.1-PREVIEW-196_g4_MM.img, placed the twrp image in same folder where the backup of sbl1 is.
- Now i dont know how to flash the the twrp to the boot partition. I tried to find some guides but no luck. Yesterday for some reason i had Flash button in salt on the bottom, today it is not there. The way i start salt is by browsing inside /home/android/Desktop/LG directory and use sudo ./SALT.desktop --experimental command. I use the latest mAid from your file server 4.19.126-1-MANJARO - mAid_v2020-07-14_23-43_x86_64_forgetful.iso.
3 attachments are uploaded bellow. The debug log from salt was unable to upload and gave bunch of package errors, so it is attached bellow in a txt file as well.
The phone keeps stable connection in download mode.
Please advice. I am very grateful.
Click to expand...
Click to collapse
you start SALT in experimental mode as this in a terminal:
Code:
~/programs/SALT/salt --experimental
anyways the problem is that your LAF version is 100004 so flashing will likely not be possible.. You can try it anyways by using the above cmd which will bring up the flash buttons.
before doing that rename the twrp image to recovery.img to ease up things.
then you select flash (folder) and ensure that anything else then the recovery image is selected (e.g. do not flash sbl1 etc).
also ensure that the target partition is named "recovery" then choose flash.
as said it will likely not work though as your download mode (LAF) is too new though. you could downgrade with LGup to Lollipop which will allow flashing with SALT for sure.
but back to the initial description, you mentioned that:
[...] after the required reboot phone stays black and recognized only as qualcom device in device manager.
[...]The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
These indicates very very likely the beginning of the ILAPO. you can check my signature for some workarounds though there is no proper way to fix it other then by replacing the mainboard.
.-