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.
Related
Over the years I've always been good at solving these things, but this is the first time I've every had to request help/guidance.
LG
1. Came from from 4.4.2, ioroot rooted, installed twrp via freegee, but not the kernel patch. This prevented me from booting back into Android.
2. Factory reset everything, wiped everything from twrp.
3. Ran adb commands here:http://forum.xda-developers.com/showthread.php?t=2451696 Got me into fastboot.
4. Flashed all .img files for LG D800 from prime's D800 img stash. Fastboot rebooted.
5. Installed Mahndi ROM via adb. Reboot
6. Stuck. Phone hangs on LG logo, loading modem and com drivers in windows. Recovery is now stock, so no flashing. Download mode works but always get a "Device Model is different" error at 0% when flashing from LG Flash Tools. Correct .tot and correct .dll for D800.
Any help or ideas to get my G2 up and running again would be amazing. I'm still trying to figure out if I can modify the .tot to match my device's current model or just ignore it and overwrite (best hope). Even if i can get ubuntu to detect the phone that would lit my spirits.
Thanks.
Progress
So I have actually figured out the problem completely, yet I do not yet have a solution.
-I after flashing the correct .img over to my device, I was all set to go, but read somewhere about flashing over mahdi ROM.
-I successfully flashed Mahdi, but DID NOT FLASH THE DEVICE VERSION PATCH (literally hit my head on the desk when I realized).
-I panicked after it did not work and reflashed all the .img so I was stuck with stock recovery, no adb, no sideload, no fastboot.
Is there ANY WAY to flash back to stock with the LG Flash Tool for the ATT D800 that ignores the model number inconsistency. This type of phone only supports the .TOT method of flashing. There is no other way (KDZ = NO). Currently my device's build.prop says that the model is "g2" (this is what the patch was supposed to fix) and my flashing file/.dll is for "D800".
My device can not be seen in Ubuntu.
Any suggestions?
datdude_tc said:
So I have actually figured out the problem completely, yet I do not yet have a solution.
-I after flashing the correct .img over to my device, I was all set to go, but read somewhere about flashing over mahdi ROM.
-I successfully flashed Mahdi, but DID NOT FLASH THE DEVICE VERSION PATCH (literally hit my head on the desk when I realized).
-I panicked after it did not work and reflashed all the .img so I was stuck with stock recovery, no adb, no sideload, no fastboot.
Is there ANY WAY to flash back to stock with the LG Flash Tool for the ATT D800 that ignores the model number inconsistency. This type of phone only supports the .TOT method of flashing. There is no other way (KDZ = NO). Currently my device's build.prop says that the model is "g2" (this is what the patch was supposed to fix) and my flashing file/.dll is for "D800".
My device can not be seen in Ubuntu.
Any suggestions?
Click to expand...
Click to collapse
over here http://androtransfer.com/AndroidUser00110001/ROM/G2/KK/D80220a/ there is a dll named lgup_8974.dll which is for d800 and is supposed to skip the model check
datdude_tc said:
Over the years I've always been good at solving these things, but this is the first time I've every had to request help/guidance.
LG
1. Came from from 4.4.2, ioroot rooted, installed twrp via freegee, but not the kernel patch. This prevented me from booting back into Android.
2. Factory reset everything, wiped everything from twrp.
3. Ran adb commands here:http://forum.xda-developers.com/showthread.php?t=2451696 Got me into fastboot.
4. Flashed all .img files for LG D800 from prime's D800 img stash. Fastboot rebooted.
5. Installed Mahndi ROM via adb. Reboot
6. Stuck. Phone hangs on LG logo, loading modem and com drivers in windows. Recovery is now stock, so no flashing. Download mode works but always get a "Device Model is different" error at 0% when flashing from LG Flash Tools. Correct .tot and correct .dll for D800.
Any help or ideas to get my G2 up and running again would be amazing. I'm still trying to figure out if I can modify the .tot to match my device's current model or just ignore it and overwrite (best hope). Even if i can get ubuntu to detect the phone that would lit my spirits.
Thanks.
Click to expand...
Click to collapse
I have almost the exact same problem will keep an eye on thread, hope we git it sorted soon!
I'll Take a look
XxZombiePikachu said:
over here http://androtransfer.com/AndroidUser00110001/ROM/G2/KK/D80220a/ there is a dll named lgup_8974.dll which is for d800 and is supposed to skip the model check
Click to expand...
Click to collapse
Thanks!
I have seen and downloaded that one before, and if I recall correctly, I didn't get a model error, but rather something else. I believe it was a bin file error??, but I do not recall. I actually just sent my G2 in on a warranty claim (*please oh please don't notice I replaced the screen") and hopefully that will take care of it. I was just posting so that maybe someone doesn't have to dig through 350 pages of replies to find out what happened. I'll keep the post going when I find anything out though.
Working together!
MRobbo80 said:
I have almost the exact same problem will keep an eye on thread, hope we git it sorted soon!
Click to expand...
Click to collapse
I won't have my phone available for a few days. Any chance you could go ahead and give that lgup_8974.dll a test run and report back? I'd be more than willing to help do any research if it gives a different error besides the model.
Sorry to dig up this thread, but I have the exact same problem, except I flashed mahdi on my D802 and somehow the version patch didnt flash correctly. Is there anything like a lgup_8974.dll for D802s?
I'm really desperate here.
i have the exact same problem!!
Any solution found yet??
Get rid of shutting down after "device corrupt" message - so possibility to gain root
Some of you might face the problem that whatever you do anything you change on your device in order to gain root even if your bootloader is unlocked your device is turning off after promting "device corrupt, etc..." message.
Sometimes you can't even unbrick with lg bridge cos' it can't see that your firmware has any problems.
Typical symptom of this problem that very interestingly your phone is not showing any corrupt messages during normal boot up even if your bootloader is unlocked (it should write some warnig message at every boot up).
Also when you "fastboot boot yourstockbootimage.img" it's booting up but writing some network related error then shuts down saying corrupt battery.
In order to root your phone you must be able to change the firmware a bit (tweak the boot image).
First of all you need to unlock your bootloader if you didn't do it yet: http://forum.xda-developers.com/lg-k10/how-to/unlock-bootloader-lg-k10-mtk-devices-t3486302
All you have to do is allow modifications in TWRP step 2.1 here: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
It means the rest written under is fully unnecessary but i keep it just in case the above mentioned method would not work for someone:
Other requirements:
- lg up working with your device: http://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839
- kdz firmware
- twrp recovery of your device (usually you can find it in your favorite root thread or somewhere on xda)
Extract boot image from your firmware with lg firmware extractor (http://viid.me/qe7ufH). First you have to extract the ".dz" file and then the boot image form that ".dz" file.
Once you have your boot image (eg. boot_157696.bin) rename it to "boot.img"!
Put this "boot.img" on your sd card!
Flash this firmware (that you taken your boot image form!!!) on your phone with LG UP.
Boot up and see if it works also tick all the necessary options (oem unlock in developer options, usb debug,...)
Reboot to fastboot, check if your bootloader is still unlocked ("fastboot getvar all"). If it's locked unlock it!
Boot into your TWRP (fastboot boot twrp.img), you can allow it to read system.
Go to "install" (tick install image) and flash your "boot.img" form your sd card (naturally onto your boot partition).
Now before you reboot make a full wipe (fastory reset) in TWRP (wipe menu) then you can reboot to system.
After the "device corrupt" message it must be booting on and boot up normally and during every boot up there should be that message.
Now you can go and root your phone - always use that boot image you just flashed during the first step of the root process (recompress this boot image to gzip and ... read a rooting guide: http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807 there this should be "bootlz4_0.img")
There is no explanation why it works... wierd.
Hi.
I have this problem, corrupt device screen and continuous bootloops, I only have access to the download mode, but LG UP does not allow me to flash the .kdz even though I have the boot.img file on the sd card. It shows me the typical error at 9% of the process 'Error code = 0x81000304, CBasicFlash :: _func_LoadGptF - ErrorCode: 8222'. Would someone tell me what it is and how can I fix it?
I have tried to revive the cell phone in myriad ways and it is not possible for me.
I appreciate any suggestions.
Thank you very much.
Llony said:
I appreciate any suggestions.
Thank you very much.
Click to expand...
Click to collapse
This thread is not about bootloops but shutting down. Different subject. You should start a new thread about it.
However i looked at it, check out this comment:
http://forum.xda-developers.com/showpost.php?p=66135219&postcount=74
anyways if i were you i'd do a hard reset (http://www.hardreset.info/devices/lg/lg-k10/) and then i'd use lg bridge's update error recovery function (or you can change the order - first lg bridge, then hard reset).
Also make sure you chose "refurbish" when you use lg up and also make sure you are using the right kdz file (i recommend using lg mobile support tool to download your kdz - there is a possibility under options and upgrade recovery that using your imei it downloads the kdz to a hidden folder: http://forum.xda-developers.com/showthread.php?t=2395323)
I have bootloop with usb connected, without usb powered off
Llony said:
I have bootloop with usb connected, without usb powered off
Click to expand...
Click to collapse
I see... okay. However check out what i wrote above and one more thing: make sure you use usb 2.0 not any 3.0 ports.
I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it
Llony said:
I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it
Click to expand...
Click to collapse
Did you try lg bridge - update error recovery?
LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.
Llony said:
LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.
Click to expand...
Click to collapse
What do you mean it doesn't give you the option? I mean LG bridge, there is no update error recovery on the software update page? As in this video:
https://www.youtube.com/watch?v=b_GqAG02OXU
I'm trying to find the latest kdz file for the H918 (T-Mobile LG V20). After looking at several guides, I still can't track it down.
This guide gives a link where you can supposedly download the firmware, but all I can find by following that guide is the Android source code, not a .kdz file.
This guide gives a url you can visit (on a non-standard port), and you have to put your phone's IMEI number in the URL parameters. This url will return an xml file that contains another url where you can download the kdz for your specific phone. However, when I followed this guide, the xml file returned a successful response but the sw_url field was empty (along with most other fields).
Other guides have said to go to https://lg-firmwares.com/category/lg-series/lg-v20/ but I am getting a 500 server error on that page. Maybe it's just down today, but seems kind of odd that I can't access it. When I try to find LGH918 by visiting the main domain name (lg-firmwares.com) and navigating from there, I can't seem to find anything.
The closest I have come so far is this download page, but it is for the LGH918TN (instead of LGH918). Is that "close enough" or is it going to brick my phone?
UPDATE: I think I did find the correct kdz file since I started writing this post, but I am going to post this information anyway, for anybody else having the same issue. I went to lg-firmwares.com and clicked "Check IMEI" and entered my phone's IMEI number. It directed me to a download page for LGH918TN, so it looks like that is correct for my phone! I will try and remember to report back here on whether the kdz file actually worked or not. Hoping it doesn't brick my phone, yet again.
As an update to my original post, I did manage to successfully flash the kdz file using the "Upgrade" option in LGUP, and did not lose any of my data. However, I'm still getting the unlocked bootloader message when I start my phone ("Your device cannot be checked for corruption..."). Does anybody know if flashing the .kdz file causes TWRP to be replaced with the original recovery mode? I don't want to try to boot into TWRP in case it has been replaced, thus triggering a factory reset and losing all my data.
It ok to try and relock the bootloader now? (if so, how?) Or do I need to replace TWRP too?
fronzee88 said:
As an update to my original post, I did manage to successfully flash the kdz file using the "Upgrade" option in LGUP, and did not lose any of my data. However, I'm still getting the unlocked bootloader message when I start my phone ("Your device cannot be checked for corruption..."). Does anybody know if flashing the .kdz file causes TWRP to be replaced with the original recovery mode? I don't want to try to boot into TWRP in case it has been replaced, thus triggering a factory reset and losing all my data.
It ok to try and relock the bootloader now? (if so, how?) Or do I need to replace TWRP too?
Click to expand...
Click to collapse
You need to use LG Bridge to restore to stock. That will replace TWRP. Then you need to fastboot OEM lock.
If you don't want root and want to relock the bootloader to stop seeing that screen, you will lose data.
Sent from my LG-H918 using XDA Labs
OS - Windows 10 Enterprise N LTSC 64-bit
How I got here:
Rolled back to 2016 build using LGUP (store, patched).
Used dirtysanta to unlock bootloader and install TWRP.
On first boot, I got static and a constant buzz from the haptic feedback motor.
Not knowing that Verizon users sometimes need to wait over 20 minutes, after 10 or so I assumed I was toast.
Tried to flash NotYetADev's Oreo build with the same result. (https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669)
Attempted repairs:
Tried LG Flashtool using dksoni411's method (https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732) and it failed to work.
Now LGUP is not working. Changes between "not recognized" and "wrong DLL" depending upon LHUP_common.dll version.
Uppercut ran after disabling A/V but didn't work and required a system restore to get Windows back to a normal state.
Flashing several alternate kernels doesn't fix.
Flashing LineageOS, same thing.
What's still working:
Download Mode
Fastboot Mode
TWRP
Notes:
I have the original files from the first LGUP dump.
Looking at the build.prop from the TWRP terminal, each flash appears to be successful but still hangs at the LG "Life's good" screen.
I am kind of at a loss as to how to proceed. I have some reservations pushing aboot or any other files via fastboot as I don't want to risk a hardbrick condition. Any assistance would be greatly appreciated. I can spinup a VM if needed to run Uppercut. I am not going down that road again...
Update:
Installed all software, drivers, etc. in a Windows VM. Same results. Uppercut still fails to work with LGUP...
Out of desperation, I flashed bootbackup.img to the device. No change.
Anyone? Anyone? Bueller?
It appears that TWRP is not flashing the system partition even though it is mounted.
Anyone?
You don't need uppercut. Remove it. You need lgup patched working. Do that first. Trial and error I recall with dll file. Just keep trying. Forget virtual machine. If you don't need Verizon firmware you can use US996 and then dirtysanta. Vibrator issue is with verizon firmware only.
Sent from my LGE LG-US996 using XDA Labs
Posting an updated request in another thread as no help is forthcoming here.
if i remember correctly it has to do with dirty santa step 3 where you install twrp and need to type
"adb reboot recovery"? this step almost screwed me over... you actually dont need to wait for vibrate to stop to boot in twrp, wait 5mins then type the adb command, and it will reboot in recovery...
Thanks for the reply.
I got LGUP (patched) working again on a clean virtual machine. My work PC is very loaded with software and I wanted to avoid driver conflicts. Sadly, the original KDZ dated December 2016 that I first flashed won't work now. It throws a "wrong model" error likely caused by my using the LG flash tool and it failing to complete the flash.
It turns out that my file system was hosed but I managed to fix that in TWRP. Rather than try and use fastboot to flash the files individually from the original LGUP dump, I am making a TWRP flashable zip. Hopefully, that will work.
If I can get it back to stock, I am confident that I can get it going. My main screwup was not waiting long enough on the first rooted boot (static screen, and vibrate). I now have a kernel to flash that is supposed to fix that. I have a bad feeling that I will need to revisit the LG Flashtool and correct those errors before anything will be resolved.
More information in an updated thread here:
https://forum.xda-developers.com/v2...anta-bootloader-t3519410/page400#post81065413
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.
.-