Database Users

ATT D800 Fastboot Loop No Recovery No Download Mode

Hello All,
I've been searching for hours. I had rooted my LG G2 weeks ago with no problems. I then un-rooted it and I thought reset it to factory. Today in Target I pulled it out of my pocket to make a call and it was black screened to Fastboot.
I have tried holding down Volume - and Power and entering recovery to reset to factory but it immediately goes to Fastboot loop.
I have tried holding down Volume + while plugging in USB for Download Mode but it immediately goes to Fastboot loop.
I have tried adb commands, error: device not found.
I have tried manually updating the Android drivers through Computer Management and selecting many of the Android Platform Sooner versions. My Win7 PC recognizes the phone as ADB Interface > Andriod Sooner Single ADB Interface in Device Manager.
I have tried this http://forum.xda-developers.com/showthread.php?t=2477595 and flashed both laf.img and I cannot get into Download Mode.
What else can I do? Does anyone have any other ideas?
Thanks for your time!

hey same exact thing just happened to me. i had it rooted from earlier, but ended up keeping the stock rom on my AT&T LG G2 D800. What I think happened was ATT just pushed out an OTA update (not sure about other carriers), supposedly some small 15mb update to prepare for upcoming releases and despite declining the install, the phone of course did it anyways.
No recovery, no download mode, factory reset doesn't do anything.
Thanks AT&T! :good:
Are we completely boned here?

This worked for me
http://forum.xda-developers.com/showthread.php?t=2451696
Follow this thread, I tried the TWRP terminal code and it worked. Let me know how it goes

Did anyone figure this out? I am stuck in fastboot mode. I can run fastboot commands, but thats about it.
I can't get to ADB, I can't get to recovery, I can't get to download mode. I reboot the phone and it goes immediately back to fastboot.
I've tried flashing recovery, the laf.img, and even rom's inside fastboot and nothing is seeming to work.

sniffs said:
Did anyone figure this out? I am stuck in fastboot mode. I can run fastboot commands, but thats about it.
I can't get to ADB, I can't get to recovery, I can't get to download mode. I reboot the phone and it goes immediately back to fastboot.
I've tried flashing recovery, the laf.img, and even rom's inside fastboot and nothing is seeming to work.
Click to expand...
Click to collapse
If you can't get adb access with either single sooner or pdanet drivers, you may have to resort to this..
http://forum.xda-developers.com/showthread.php?t=2582142
(actually kind of sounds like fun to me)

if you're stuck in fastboot mode then you can simply use the fastboot commands to write the aboot, sbl1, boot, recovery, laf, rpm, tz and dbi partitions.
you can substitute stock recovery.img for a properly patched twrp/cwm img (renamed recovery). from there you should be able to boot into download mode... custom recovery.. or boot back up.

autoprime said:
if you're stuck in fastboot mode then you can simply use the fastboot commands to write the aboot, sbl1, boot, recovery, laf, rpm, tz and dbi partitions.
you can substitute stock recovery.img for a properly patched twrp/cwm img (renamed recovery). from there you should be able to boot into download mode... custom recovery.. or boot back up.
Click to expand...
Click to collapse
I found a site that had the backed up D800 .img files. I had to use Ubuntu to write them back to my device.. after like 15hrs of googling/writing on forums, I finally got my device to boot back up! lol..
of course there was a popup saying that my device was suspected of rooting and it won't update.. but who cares, it works now!

im onthe verizon variant and stuff like this just annoys me to no end you say no lg pushes it to your device anyway its wrong not even samsung stoops this low i am glad i have a custom rom

sniffs said:
I found a site that had the backed up D800 .img files. I had to use Ubuntu to write them back to my device.. after like 15hrs of googling/writing on forums, I finally got my device to boot back up! lol..
of course there was a popup saying that my device was suspected of rooting and it won't update.. but who cares, it works now!
Click to expand...
Click to collapse
what site?

Sorry for comment this old post, but i need help with my D800 y cant unbrick it

Keep trying flashing the D800 file or what?

Hello friends to see if I draw from this setback. My situation is that I have no recovery or download, but when trying to get the img fastboot does not exceed by "erasing" or "writing" who knows how to solve this please !!
Thank you :good:

Problem after root attempt

Hello,
I tried to root my P8 Lite, which is something I've already done on a lot of other smartphones. So I first unlocked my bootloader, then I tried to follow a guide to root it. Everything was going smooth, but when I hit enter for the last time into the command line (at this point of the process, it just installed superSU) my phone rebootd and stucked on the huawei logo. After 20mn I decided it was enough, I unplugged it and hard rebooted it, but still stuck on huawei logo.
Since this, I wasn't able to reboot my phone, nor enter the fastboot/rescue mode. Now I tried on more time to enter the fastboot, and I don't know why but after a few time it showd up !
So basically my phone is now on fastboot mode, unlocked, and I come here to seek answers about the method to flash it and start again with a fresh android. I don't even know where to find the correct rom to flash, nor how to flash, if for instance I should use adb, etc.
If someone here is able to help me, that would be greatly appreciated.
By the way, I manually updated the phone to android 6 and EMUI 4.
Thank you a lot for enlightments.

Hello! Since you are in fastboot mode you can easily fix the issue. Just download a stock rom you wanna flash and use (you can try the new B588) and with the Huawei Update Extractor, extract the boot.img, recovery.img, cust.img, system.img from the UPDATE.APP file. Then flash these in the order i wrote them (using the fastboot command for example:
Code:
fastboot flash boot boot.img
, same thing for all of these just change the file names). That is how i fixed my last 2-3 bootloops. I would suggest looking here first though: https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 on Chapter 4. Hope this helps and good luck

Hi,
Thank you for your answer.
Problem is now, my phone ran out of bttery so not in fastboot mode anymore and I just can't figure out how to go back in fastboot anymore.
I tried to power on the phone while pressing vol up, wait for the huawei logo and wait for ten more seconds, nothing except a black screen. I tried vol down, both vol up and down, still nothing. Thing is, yesterday I don't even know how I managed to enter fastboot, I just tried, didn't work, so I put my phone on the bed, and ten minuts later I realized it was on fastboot mode. Informatics huh.
If you have any idea on how to go back in fastboot mode, I tried using adb, but it needs the phone to reach systm to be able to reboot.
By the way you talked about a specific rom, where can I find this one ?
Thank you again for your time.
EDIT : Ok I managed to reach fastboot, what I did was to plug it on my laptop, powered off, then pressed vol down and power on, and it worked. Informatics has its reasons...
Still interested into the rom ou talked. I'll try to find it on my own though. But if you got a link, I would be happy to download it.
EDIT2 : Ok I tried to flash, everything went good, but my huawei is still in its bootloop. I extracted the B588 rom, but there was way more than 4 img files. I still flashed only the four you and the link you gave me told me, but maybe I need to flash more than these 4 ?

Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 <-- follow the " Bootloop/Softbrick" method if you cannot install the latest firmware directly. You may need to flash original recovery first too. Any recovery version will do they are all the same, find the how too under the "install TWRP" section, but basically it goes "enter fastboot, type fastboot flash recovery recovery.img" while you have recovery.img in the same directory.
[edit]
Also, if you are on MM you should not be using a batch file to root. Once you have TWRP installed, you need to flash 2 zips via TWRP. They can also be found in the mega thread.

yodaofborg said:
Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 <-- follow the " Bootloop/Softbrick" method if you cannot install the latest firmware directly. You may need to flash original recovery first too. Any recovery version will do they are all the same, find the how too under the "install TWRP" section, but basically it goes "enter fastboot, type fastboot flash recovery recovery.img" while you have recovery.img in the same directory.
[edit]
Also, if you are on MM you should not be using a batch file to root. Once you have TWRP installed, you need to flash 2 zips via TWRP. They can also be found in the mega thread.
Click to expand...
Click to collapse
Single stable SuperSu v2.76 also works for builds less than b580.. For builds greater than that, use 2 zips method

Well, it obviously didn't

PSA: Ticwatch E&S factory reset

This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.

BackCheck said:
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
Click to expand...
Click to collapse
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.

EpicLPer said:
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
Click to expand...
Click to collapse
Flash Tool is a mighty powerful tool, alright. I couldn't find a good scatter file so in a caffeine deprived state I tried to cobble one together. I may have damaged the preloader. It does show up in device manager but it is different that the VCOM preloader device that was showing. Now it totally crashes Flash Tool too. I'm still working on it but since I have a second watch now, I might just RMA this one and start over.
Again, if anyone has a good scatter file please post it. I found one after the fact but I get errors and it's for another MT2601 device, not the Ticwatch.
The good news is I found if you power down the watch and hold the power button on boot you'll get a long vibrate. If you release the button and hit it 3 or 4 times during the vibrate you'll be in the bootloader.

Anyone have stock or even custom working system.img and boot.img?

great
thank you very much man, i was blocked in twrp recovery after a factory reset, and now i should have installed stock recovery, thanks to your post .

Hard/soft brick

I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum

jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/

That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.

https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed

SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed

jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.

wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc

Was finally able to get into recovery, so all is well. Thanks for the help yall

OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?

gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc

My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!

katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?

I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.

katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.

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.
.-