So I was trying to unlock my bootloader with LG Laf Recovery MultiTool v1.2 (You can find it on android fourms) I choose Automatic unlock, and it went through fine. Until it got to the fastboot location. When it tried to use a command it returned: FAILED (remote: unknown command). Now its stuck booting into fastboot, but it won't accept any commands. They all return with the above error. Is there anyway that i can fix this?
What is your phone model? Can you enter download mode? If yes, then you can flash stock kdz ROM with LG Flash tool, see tutorial about returning to stock. Good luck.
I tried to flash stock rom through MiFlash with unlocked bootloader and now im getting this and phone is stuck at boot animation. Please help
EDIT: Delete, i get it working somehow.
You must likely were trying to flash your phone while on fastboot, you must boot on EDL mode to flash using Miflash
Format system_a
I followed the guide to bootloader unlocking and managed to get it working. I had upgraded via LGUP to Pie, then did the unlock, and it went smoothly.
I got TWRP installed and went through the process of flashing the Lineage 17 zip.
Afterwords, I get this screen. I can get to fastboot, I can get to Firmware update, and I can flash TWRP back on manually (it seems to be gone). What I can't do is get the phone to boot.
Is there anyone with some ideas to help me?
probably your device failed a routine saftey check, might want to flash back the pie firmware I use 20a which is the first pie release for my US V40. Flash back the KDZ and relock bootloader, then follow the procedure again.
gamblodar said:
I followed the guide to bootloader unlocking and managed to get it working. I had upgraded via LGUP to Pie, then did the unlock, and it went smoothly.
I got TWRP installed and went through the process of flashing the Lineage 17 zip.
Afterwords, I get this screen. I can get to fastboot, I can get to Firmware update, and I can flash TWRP back on manually (it seems to be gone). What I can't do is get the phone to boot.
Is there anyone with some ideas to help me?
Click to expand...
Click to collapse
Your phone can enter edl mode ?
KouaV1 said:
probably your device failed a routine saftey check, might want to flash back the pie firmware I use 20a which is the first pie release for my US V40. Flash back the KDZ and relock bootloader, then follow the procedure again.
Click to expand...
Click to collapse
I've gotten her back to life with LG Bridge. Now, when I try to flash the TWRP, it fails on
HTML:
fastboot boot TWRP-image.img
sondv04199 said:
Your phone can enter edl mode ?
Click to expand...
Click to collapse
Is that download mode? I got to that and revived via LG Bridge. I'm at Pie - 1 Joly 2019 security patch, kernel 4.9.12, build PKq1.190202.001, software V20a.IND-XX
gamblodar said:
I've gotten her back to life with LG Bridge. Now, when I try to flash the TWRP, it fails on
HTML:
fastboot boot TWRP-image.img
Click to expand...
Click to collapse
I forgot to mention my bootloader is still unlocked.
Should I re-lock then go through 9008 steps? Would that give me the best change of success?
When you used LG Bridge you overwrote the abl_a and the LAF partitions (When you first unlocked bootloader, abl_a was replaced with v35 engineering bootloader and both laf partitions were erased to get access to fastboot menu that allows the unlocking of bootloader and flashing of files in fastboot, but using the LG Bridge, you reverted these partitions to stock). With stock partitions you cannot flash or boot Twrp in fastboot menu. You gotta follow Xsavi's guide at:
https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Start with 'Flashing the engineering bootloader' steps 1 through 4, then skip the 'Unlocking the bootloader' 1 through 4 parts as your bootloader is already unlocked, but do the step 5 through 6 to gain access to fastboot. Then you can boot and/or flash twrp. I personally just use fastboot to boot twrpxxx.img then use twrp menu to flash twrpxxx.img onto the phone just to make sure it sticks. Hope this helps.
Android# said:
When you used LG Bridge you overwrote the abl_a and the LAF partitions (When you first unlocked bootloader, abl_a was replaced with v35 engineering bootloader and both laf partitions were erased to get access to fastboot menu that allows the unlocking of bootloader and flashing of files in fastboot, but using the LG Bridge, you reverted these partitions to stock). With stock partitions you cannot flash or boot Twrp in fastboot menu. You gotta follow Xsavi's guide at:
https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Start with 'Flashing the engineering bootloader' steps 1 through 4, then skip the 'Unlocking the bootloader' 1 through 4 parts as your bootloader is already unlocked, but do the step 5 through 6 to gain access to fastboot. Then you can boot and/or flash twrp. I personally just use fastboot to boot twrpxxx.img then use twrp menu to flash twrpxxx.img onto the phone just to make sure it sticks. Hope this helps.
Click to expand...
Click to collapse
You dont need step 5 and 6 as you already have fastboot command. By doing that you lose download mode and that means if you ****ed up your device is now paperweight unless you wanna waste time unbricking it as theirs no tutorials on comfiguring patch and xml files to use qpst to flash.
---------- Post added at 04:46 PM ---------- Previous post was at 04:41 PM ----------
gamblodar said:
I forgot to mention my bootloader is still unlocked.
Should I re-lock then go through 9008 steps? Would that give me the best change of success?
Click to expand...
Click to collapse
if you had bootloader unlocked and flashed back original kdz or firmware lg bridge, or whatever then yes you need to relock bootloader and redo the steps.
KouaV1 said:
You dont need step 5 and 6 as you already have fastboot command. By doing that you lose download mode and that means if you ****ed up your device is now paperweight unless you wanna waste time unbricking it as theirs no tutorials on comfiguring patch and xml files to use qpst to flash.
---------- Post added at 04:46 PM ---------- Previous post was at 04:41 PM ----------
if you had bootloader unlocked and flashed back original kdz or firmware lg bridge, or whatever then yes you need to relock bootloader and redo the steps.
Click to expand...
Click to collapse
OK Thanks for the tips.
I re-enabled OEM lock, rebooted, 9008-mode, overwrote the abl_a partition, rebooted to fastboot, fastboot oem unlock successful. Flashing the ablpiestock.img fails, and then I'm back to green screen.
I may just be cursed...
gamblodar said:
OK Thanks for the tips.
I re-enabled OEM lock, rebooted, 9008-mode, overwrote the abl_a partition, rebooted to fastboot, fastboot oem unlock successful. Flashing the ablpiestock.img fails, and then I'm back to green screen.
I may just be cursed...
Click to expand...
Click to collapse
Rename the ablpiestock to just abl before flashing the abl. That seems to be the issue.
gamblodar said:
OK Thanks for the tips.
I re-enabled OEM lock, rebooted, 9008-mode, overwrote the abl_a partition, rebooted to fastboot, fastboot oem unlock successful. Flashing the ablpiestock.img fails, and then I'm back to green screen.
I may just be cursed...
Click to expand...
Click to collapse
might just be your oled or your device issue. do lg up kdz restore using refurbrish which will erase everything. I never do os or software upgrades using lg up or bridge.
Having trouble installing TWRP.
I can fastboot and attempt:
`fastboot boot TWRP.img`
But it either fails or "succeeds" and then just hangs on the LG Logo.
`fastboot flash recovery TWRP.img`
-returns an error that recovery_a doesn't exist.
`fastboot flash abl_a TWRP.img`
-returns "Volume is Full"
Any ideas what I may be doing wrong?
Device is an ATT LG V40 with the V35 Engineering Bootloader if that helps.
You don't say if it's at&t pie or Q. Let's assume it's Q 30b?
Follow this link for the bootable partition with twrp already injected. You can either use qfil to flash it, or more easily since u have fastboot, just do fastboot flash boot_a the_name_of_the_file.img.
The only thing about using fastboot is you want to save the original boot_a image first. At&t doesn't make their kdz available and if u want /need to go back to stock u need to save it first.
After flashing it (either way), you need to immediately go to recovery, don't boot the device, u have to format data and reboot to recovery and then flash magisk and no verity zip. Otherwise a backup of your data won't work as it will be encrypted.
just one point, don't every flash something to a partition when yer not sure what yer doing. The abl partition is only about 1 meg in size, it's the 'android boot loader'. You could, if unlucky, flash something wrong for that partition and end up overwriting the partitions that are next to it, and essentially (just about) brick the device.
cheers
AsItLies said:
You don't say if it's at&t pie or Q. Let's assume it's Q 30b?
Click to expand...
Click to collapse
Sorry! It's Pie.
AsItLies said:
Follow this link for the bootable partition with twrp already injected. You can either use qfil to flash it, or more easily since u have fastboot, just do fastboot flash boot_a the_name_of_the_file.img.
Click to expand...
Click to collapse
This gives me the following:
Writing 'abl_a' FAILED (remote: 'Errorflashing partition :Volume Full')
I receive a similar message for `abl_b`, `recovery`, and `boot_a`
If I attempt flashboot boot the_image.img then I can get a success message on the fastboot-side and the phone reboots, but once again just to stick at the LG V40 screen.
sharpienation said:
Sorry! It's Pie.
This gives me the following:
Writing 'abl_a' FAILED (remote: 'Errorflashing partition :Volume Full')
I receive a similar message for `abl_b`, `recovery`, and `boot_a`
If I attempt flashboot boot the_image.img then I can get a success message on the fastboot-side and the phone reboots, but once again just to stick at the LG V40 screen.
Click to expand...
Click to collapse
Wow, so I don't think you understood some things. First, stop trying to flash an image to the wrong partition then what it's for. It is NOT for abl_a, and it is NOT for recovery (there is no recovery partition on a treble phone). STOP DOING THAT.
and second, because that boot_a (ONLY!!!) partition is for Q, as I said, you need one for Pie, and shouldn't even be trying to use it anyway.
and third, you can't fastboot boot these boot/twrp images, they have to be flashed to the partition and then you have to boot to recovery immediately after (don't try to boot the phone).
So if you can't flash the image with fastboot then the only option would be to use qfil, again, be sure to back up the original image first.
I'll look around and see if I can find one for Pie. We may have to create one if it's not around.
cheers
Just checking, but u do know how to use qfil yes? And, how did u get fastboot on the device? Using qfil I'm guessing? and you deleted laf_a? or the engineering abl?
This info is important because 1) the fastboot you get when simply erasing the laf_a is not as powerful and full featured as the engineering abl. The actual capabilities of the (laf_a erased) fastboot varies by OS variant, but some of them are basically worthless.
2) you'll have to be able to use qfil to get this accomplished.
let me know and we'll go from there.
I have Realme X2 Pro stuck in fastboot mode with bootloader unlocked, unable to access recovery or boot into system. Is there a way to know which variant my phone belongs to, or any details?
Fastboot shows, product name: msmnile, variant: SDM UFS, bootloader and baseband version are empty.
I don't know exactly which variant my phone belongs (EU/IN/CN). Tried flashing three different variants of fastboot flashable images in this order (boot > dtbo > system > vbmeta > vendor), files flashed successfully, but same result. Continious booting into fastboot mode. Also tried booting into recovery directly by using command "fastboot boot twrp.img" which gave an error - command failed (unknown command).
I downloaded the official .ozip file from realme website and extracted the images for flashing through fastboot, but no luck, same scenario.
Tried Realme Flash tool for this file "RMX1931EX_C.27.ofp", after flashing device rebooted into fastboot mode again.
Please help me out, I'm new to this.
I'm in the exact same spot as you. Did you find a fix?
Chromelon said:
I'm in the exact same spot as you. Did you find a fix?
Click to expand...
Click to collapse
Did u find any solution, I have same problem