Develop Bugs

[SOLVED] Soft-bricked my device

Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.

with flashtool impossible to rollback . and impossible to flash kdz 6.0... a lot of people with this issue

Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.

gregor.eesmaa said:
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
Click to expand...
Click to collapse
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back

rotoko said:
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
Click to expand...
Click to collapse
There you go. Can't do any better as I am not an expert in how Android precisely works at this level.

have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815

leegreggs said:
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
Click to expand...
Click to collapse
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.

gregor.eesmaa said:
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
Click to expand...
Click to collapse
No I've decided to go back to my LG g2 till either flashtool gets updated or till a tot & dll comes out

gregor.eesmaa said:
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
Click to expand...
Click to collapse
:crying::crying: i forget to enable usb debugging, now my pc can not connect to phone under downloadmode. And i can not use adb to let it reboot bootloader.

I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..

rav0r said:
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
Click to expand...
Click to collapse
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.

AndHD2 said:
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
Click to expand...
Click to collapse
Same here, only a software issue. I cannot boot to download mode, and my device is locked.

[How to] [fix] LG G3 download mode not opening. Stuck at fastboot. [All Variants].

Sometimes it might have happened to you that you have erased your download mode while doing some fun with adb commands and enjoying android development with starter knowledge. In this process you unfortunately destroyed your download mode.
Now you want to go back to stock but your download mode is not appearing only a fastboot mode opening saying some very tensed and confusing things to understands. This is the situation where you are totally messed up and out of mind. Don't know what to do. Tried whole of internet and can't find a solution. Now method is working and you want a fix. Then this thread is gonna help you a lot. You will be very happy to read instructions here cause they are easy and also phone saving too. These instructions can even save your amount to be given to a repairing shop.
So a lot of introduction is done, let's proceed to the process. First of all read disclaimer to avoid any misunderstandings of future.
Code:
Your warranty is void now. I am not responsible for any mistake and wrong thing happens to your device. Always try if you have a good knowledge of that.
These steps are not an official LG and therefore not endorsed by LG Electronics in any way. As such, this is a 'try-at-your-own-risk' approach. Please make sure to back up your important files when trying this for the first time. I take no responsibility for any undue outcomes resulting from the use of these steps and instructions. And all the best for step.
Things you Need:
1: LG united mobile drivers here. (Skip you have already)
2: adb & Fastboot drivers from here. (To do flashing commands). Minimal Edition.
3: Make sure "USB debugging" is on for you LG G3 device. If not sure check here.
4: laf.img for your device . (Download mode image). Most important thing
Download it from here according to your device variant like as d850, d855 or etc.
Select your variant > Stock partitions > 10D > laf.img ( I prefer 10d laf.img you are welcome to try other ).
5: LG G3 device in fastboot mode by connecting to PC while phone is powered off pressing volume up(+) button.
6: And the most important thing a computer. (I tried it on Windows 10 but will work on 7,8 and others too.
Steps:
1: Install LG united mobile drivers.
2: Install "adb and fastboot mode" drivers. Copy "laf.img" to the directory where you installed them and run "MAF32.exe"
Mine is "C:\Program Files (x86)\Minimal ADB and Fastboot"
3: Connect your LG G3 device while in fastboot mode.(Make sure drivers are installed).
4: Check if connection is right by doing this command
Code:
fastboot devices
5: If you done right your device might appear. (Sometimes as a question mark too)
6: To flash download mode. Execute these commands in sequence.(Make sure "laf.img" is copied to that folder where you installed the adb and fastboot drivers and is named as "laf.img").
Code:
fastboot erase laf
fastboot flash laf laf.img
fastboot reboot
7: Pull battery of your device and reboot into download mode again if flashing is successful. Download mode might appear as original. If not then you might have not listened to instructions. (If still stuck ask in comments).
If i helped you anyhow press "Thanks"
All the best with process.
Credits:
Autoprime for the stock partitions.
shimp208 for minimal ADB and fastboot drivers.
And all others who gave some ideas, drivers and tools for that method to work.

in adb commands appears waiting for device along time and no thing happened ..... plz
dksoni411 said:
Sometimes it might have happened to you that you have erased your download mode while doing some fun with adb commands and enjoying android development with starter knowledge. In this process you unfortunately destroyed your download mode.
Now you want to go back to stock but your download mode is not appearing only a fastboot mode opening saying some very tensed and confusing things to understands. This is the situation where you are totally messed up and out of mind. Don't know what to do. Tried whole of internet and can't find a solution. Now method is working and you want a fix. Then this thread is gonna help you a lot. You will be very happy to read instructions here cause they are easy and also phone saving too. These instructions can even save your amount to be given to a repairing shop.
So a lot of introduction is done, let's proceed to the process. First of all read disclaimer to avoid any misunderstandings of future.
Code:
Your warranty is void now. I am not responsible for any mistake and wrong thing happens to your device. Always try if you have a good knowledge of that.
These steps are not an official LG and therefore not endorsed by LG Electronics in any way. As such, this is a 'try-at-your-own-risk' approach. Please make sure to back up your important files when trying this for the first time. I take no responsibility for any undue outcomes resulting from the use of these steps and instructions. And all the best for step.
Things you Need:
1: LG united mobile drivers here. (Skip you have already)
2: adb & Fastboot drivers from here. (To do flashing commands). Minimal Edition.
3: Make sure "USB debugging" is on for you LG G3 device. If not sure check here.
4: laf.img for your device . (Download mode image). Most important thing
Download it from here according to your device variant like as d850, d855 or etc.
Select your variant > Stock partitions > 10D > laf.img ( I prefer 10d laf.img you are welcome to try other ).
5: LG G3 device in fastboot mode by connecting to PC while phone is powered off pressing volume up(+) button.
6: And the most important thing a computer. (I tried it on Windows 10 but will work on 7,8 and others too.
Steps:
1: Install LG united mobile drivers.
2: Install "adb and fastboot mode" drivers. Copy "laf.img" to the directory where you installed them and run "MAF32.exe"
Mine is "C:\Program Files (x86)\Minimal ADB and Fastboot"
3: Connect your LG G3 device while in fastboot mode.(Make sure drivers are installed).
4: Check if connection is right by doing this command
Code:
fastboot devices
5: If you done right your device might appear. (Sometimes as a question mark too)
6: To flash download mode. Execute these commands in sequence.(Make sure "laf.img" is copied to that folder where you installed the adb and fastboot drivers and is named as "laf.img").
Code:
fastboot erase laf
fastboot flash laf laf.img
fastboot reboot
7: Pull battery of your device and reboot into download mode again if flashing is successful. Download mode might appear as original. If not then you might have not listened to instructions. (If still stuck ask in comments).
If i helped you anyhow press "Thanks"
All the best with process.
Credits:
Autoprime for the stock partitions.
shimp208 for minimal ADB and fastboot drivers.
And all others who gave some ideas, drivers and tools for that method to work.
Click to expand...
Click to collapse

mero_enriqi said:
Click to expand...
Click to collapse
That can happen because
1: USB debugging is off on your device
2: Drivers are not installed properly
Proper fixes
1: Turn on usb debugging.
2: Install driver again or try the procedure on some other computer
(If you can get a computer running Windows 7 32-bit that would be a good choice)

im stuck at firmware update. every time i restart my phone theres no download mode and directly go to firmware update. how can i back download mode? i cant open my phone to on the debug setting

Fastboot doesnt work
Hi there
I hardbricked my phone while reinstalling stock rom when my laptop crashed. Afterwards adb and download mode wouldn't start, only thing now is fastboot.
I tried your solution, but it doesn't seems to be working. The device is showing in CMD (fastboot devices) but further commands arent accepted, they show up at the G3 screen, but afterwards nothing happens. What can i do (I really don't want to try the "short-circut - Qualcom" method).
Drivers and so on are properly installed
Thanks in advance

Can't get to download mode!
I did everything as instructed and the flashing was successful...
But whenever I want to go to download mode, it just shows download mode icon and then goes straight to fastboot!
How can I fix this?

Lg G3 D851 10c here, trying this method after trying to flash magisk and got stuck with Fast boot mode. its been stuck on "erasing 'laf' ..." for a very very long time.

thanx..............work perfect lg d851 10c

Hi, Dev /..
Mine is lg ge d851 10f
What Shoud i flash to install recovery and boot into recovery to flash roms. kindly help me ASAP...:fingers-crossed:

hi mine is d85110f . which laf.img shoud i flash kindly help

booting to download mode
in adb type
PHP:
adb reboot bootloader
this should get you to download mode......
if you try
PHP:
adb reboot fastboot
or VOL UP+USB
you cannot enter download mode
if you are on a custom rom.
The phone will just reboot.
However
PHP:
adb reboot bootloader
seems to do the trick.
Also I am on LG G3 D858HK with mokee rom 7.1
and this works for me.

twrp working but unable to mount storage.
download mode showing but its not detect.
fastboot mode not working
tried everything change file system etc

D855 Stuck at Boot Screen

So I think I've gone and bricked my LG G3.
After the ROM I was using, cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd) from here, kept freezing 20 seconds after startup, I went to update to cm-13.0-20160325-NIGHTLY-d855 (CM13 March 25th). I booted into recovery (TWRP 2.8.7.0) as usual and went to flash both the ROM's .zip file and an Opengapps .zip file using TWRP's queue feature. However, it appeared to get stuck at a line (unfortunately I don't remember what it said exactly. Something involving patching system, I think), so I pulled the battery. I get the feeling this was a super not good thing to do, as my G3 now sits at the "LG - Life's Good" screen indefinitely. Holding Power+Vol.Down does not boot into Recovery, and neither does holding Vol.Up and plugging into my computer activate Download mode.
I tried to be as thorough as I could with exactly the steps I took, so I'm just hoping someone can give me a few pointers on what I can do.
As I type this I had the phone connected to my computer next to me, and I've suddenly heard the Windows "Device connected" sound and the phone is now showing this in the top right corner, in tiny font:
Code:
[784670] Fastboot mode started
[784820] -- reset --
[784820] -- portchange --
Edit: When this occurred, a device named "Android" appeared under the "Other devices" tab in Windows Device Manager. It's got a yellow warning sign next to the icon, and Properties says that the drivers for the device aren't installed.
Perhaps this is relevant to getting it working again.

First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...

bender_007 said:
First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...
Click to expand...
Click to collapse
Many thanks for the reply.
By ADB drivers for the LG G3, do you mean the Lg United Mobile Driver? I have version 3.13.2 of them, if that's what they are.
When I input the commands
Code:
adb devices
or
Code:
fastboot devices
nothing appears, so are there different drivers I should look for?
I'm not too sure how to "fix" partitions, either, but I'm guessing it requires ADB/fastboot.
The file aboot.img and laf.img, will I need to find somewhere to download them from?
Again, I appreciate the response.

In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)

bender_007 said:
In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)
Click to expand...
Click to collapse
I used PdaNet to install the LG drivers, and inputting the command "fastboot devices" now shows
Code:
? fastboot
Inputting "adb devices" does not show anything, however.
I then attempted to flash a recovery, TWRP version 2.8.7.0 with the command "fastboot flash recovery "recovery.img"". However, the phone's screen showed the following:
Code:
[998960] Error: Command never completed
[998960] Error: Auto CMD12 Error
[998960] Error: Command never completed with errors
[998960] Failed Writing block @ 1
How do I fix the partitions and find the files "aboot.img" and "laf.img"?
Thanks for your help so far, I'm glad that there is progress now.

it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor

bender_007 said:
it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor
Click to expand...
Click to collapse
I retried the command fastboot flash recovery recovery.img but it resulted in the same output as before.
I followed the exact instructions to enter TWRP but it just stays at the LG logo screen. I've held Power+Vol.Down for about a minute after quickly releasing it+pressing it again at the LG logo, but it just doesn't do anything.
I've found myself a Lollipop KDZ file. The CyanogenMod I was running, however, ran on Android 6.0 Marshmallow. Will I need a Marshmallow KDZ file instead?

check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)

bender_007 said:
check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)
Click to expand...
Click to collapse
I appreciate the offer to use Teamviewer to help me, but I think it would be best if you typed out some instructions in a reply to this thread so that others with the same issue can refer to here.

Solution
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.

HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)

bender_007 said:
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)
Click to expand...
Click to collapse
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.

HexManiacSpeck said:
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.
Click to expand...
Click to collapse
No problem, sometimes you have to trust people
There were people who asked for help, installed teamviewer and didn´t gave any control permissions (which is fine). But they were expecting someone is having soo much free time to explain things (which I would if I had time)
cheers, flad you fixed it

Fixed my G3 I was about to send to trash!
HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" fromhere, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Thanks a million for pointing to this recovery file!
I was also in a situation where all my attempts to flash a recovery were failing due to:
Failed Writing block @ 1
Click to expand...
Click to collapse
The rest of my phone was unusable (no working recovery, no download mode, just the LG logo or this fastboot mode)
I tried several TWRP recovery versions & flavors, but so far, I only successfully reboot in recovery using CyanogenMod recovery file (download.cyanogenmod.org/?device=d855). Though I was not able to do much afterwards apart some adb commands that were not working either.
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p20
dd: /dev/block/mmcblk0p20: write error: I/O error
This recovery img did the trick and I'm now back with a CyanogenMod ROM and a wiped phone.

XT1676 - Stuck in Unlocked Bootloader, after Wipe Cache(?!)

Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...

oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...

now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?

Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there

First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:

Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)

Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .

Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen

TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.

Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work

TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?

Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)

Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?

TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..

Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)

On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work

in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?

Bootloader Unlock and Root Instruction - No Octoplus Box Required

Do you want to bootloader and unlock and root your V35? Do you want to do this yourself? Are you feeling the need for some adventure? If you answered yes to these questions, then you are at the right place. The goal with these instructions is to make the process as smooth and pain-free as possible. These instructions are based upon what I know works through firsthand experience and what I have gathered reading. My experience is with an AT&T branded V350AWM. Others also report success. That said, there can still be problems leading to bricked phone so don’t continue if you are not comfortable with the risk. An unavoidable side-effect of bootloader unlocking is that all data on your phone will be erased. Make a back up if you don’t want to lose it permanently.
This is what you will be doing in a nutshell.
Setting the phone into a baseline Oreo conditions
Extraction of abl, laf, and boot partititions
Installation of the engineering abl and erasing the laf's using QFIL
Unlocking the phone
Flashing to Pie and maybe Q in the future if you want to update from Oreo
Generation and installation of a magisk-patched boot image for root
Upon successful completion, you will have a fresh, bootloader unlocked and rooted phone that is otherwise stock.
Preparation and requirements:
On the hardware side, you will need a PC with MS Windows installed either directly or as a virtual machine and a high quality USB cable designed for data transfer. Older USB 2.0 hardware is preferred when working with LG phones. There is a long list of software to install.
Minimal adb and fastboot
Instructions: https://forum.xda-developers.com/showthread.php?t=2317790
Download: https://www.androidfilehost.com/?fid=746010030569952951
The LG mobile drivers, http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Dev-Patched LGUP
Instructions and warnings in post #6 with thanks to @ChazzMatt: https://forum.xda-developers.com/lg-v35/help/att-v35-unlocked-wont-verizon-t3958765
Download with thanks to @tecknight for the software: https://androidfilehost.com/?fid=11410963190603845019
9008 Port Driver:
https://raw.githubusercontent.com/g...alcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip
QPST with QFIIL
Some basic instructions: https://androidmtk.com/use-qpst-flash-tool
Download: https://qpsttool.com/qpst-tool-v2-7-480
Download and install each of these programs on your PC in the listed order.
You are also going to need some super important supporting files that make all of this magic possible.
The V35 engineering abl that will give you fastboot with thanks to @vlad48 for making it available: https://www.androidfilehost.com/?fid=1395089523397895796. Yes,it says V20, ignore it, it is fine. Extract abl_a and abl_b, and append a “.img” extension to each. Note the locations on your PC for future use.
The recently available emergency download (EDL) firehose that makes direct partition flashing possible released by Biao on Telegram. It is available here:
https://androidfilehost.com/?fid=4349826312261705871
or as an attachment in @Xsavi’s similar and earlier instructions for the V40: https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Note its location for later use.
Troubleshooting:
These instructions assume that your phone boots normally. Even with that there can still be issues due to software drivers and pc-hardware. They can be broadly summarized as a difficulty getting the computer to recognize and communicate with the phone and vice-versa. They arise frequently. If you encounter difficulties, review these troubleshooting tips compiled and written by @ChazzMatt and taken from his V30 WTF instructions.
Look in your ADB folder on your PC and confirm all known Windows file extensions enabled, https://goo.gl/YxLRG5.
Confirm all Windows hidden files and folders are visible, https://goo.gl/1jBKne.
Confirm USB debugging is on in Developer Options, and your PC has authorization for your phone, https://goo.gl/DgojL9.
Install another version of ADB. Install as close to the root of your hard drive as possible. X:\ADB where X is your hard drive.
Re-install LG mobile drivers, https://is.gd/Jbrvx1.
Try another USB cable.
Installing this Windows driver found attached to this post, (Thanks @gazzacbr and @FZZF) https://goo.gl/CqqNZT.
Install Google USB driver, (Thanks @s0lidsneak) https://goo.gl/z2Tahw.
Try another USB port on your computer or try cheap USB 2.0 hub, https://is.gd/gM1mM0.
Reboot the computer.
Try another computer. (THIS usually solves the problem, https://goo.gl/x637H1. Kudos if you find an an old Win7 PC, https://goo.gl/EaGMhs.)
Master Reset (full reset of phone using hardware buttons), https://goo.gl/N4LcLD. Phone will be reset anyway after bootloader unlock. Doing it prior may fix something preventing the command from working.
Step 1: Setting an Oreo baseline:
The engineering files for bootloader unlock of the V35 phone are designed to work with Oreo. If you are an Pie or Q, it is highly recommended that you flash back to Oreo. For those of you with the common AT&T V350AWM model that is not on Oreo, there are a couple of points to consider
AT&T does not release flashable roms. If you are on AT&T Pie or eventually Q, there is no going back unless of course you take the time to make a backup of the rom itself. That is not covered in this guide nor am I aware of a guide on how to do this.
AT&T sim-locks its branded V35’s and the menu to unlock is specific to the AT&T rom. You should strongly consider purchasing of a sim-unlock code and applying it before flashing another rom!
To set the baseline:
If you are already on Oreo perform a master reset. To do this, start by turning the phone off. Then press and hold the power and volume - buttons at the same time until you see the LG logo appear. When the LG log appears, release the power button and then press and hold it again while continuing to press the volume – button. Follow the menus to perform the reset.
If you are on Pie or Q, you are going to flash or cross-flash back to Oreo. The kdz's are available for downloaded from https://lg-firmwares.com/lg-lmv350ulm-firmwares/#tab=firmwares. Reports are that roms can be cross-flashed across V35 models with the exception of the Korean V350N. If you are not familiar with the roms, the favored ones are the Google Fi / North American versions for the V350ULM. Down load the latest Oreo version
https://lg-firmwares.com/downloads-file/18971/V350ULM10i_00_NAO_US_OP_0221, md5sum: 64554877b692601d5906d2bdc9691712​To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 2: Partition Extraction, Modification and Bootloader Unlock
Enable “OEM Unlock”: Turn on the phone and go through a minimal set-up process. Next go to Settings→ System→ About Phone→ Software info. Repeatedly tap on “Build Number” until you receive a message that you are now a “Developer”. Next go to Next go to Settings→ System→Developer options. Look for “OEM unlock” and flip the switch to on. Exit the “Settings” menus.
Boot the phone in EDL 9008 mode: The “button dance” to put the phone into EDL mode requires quick hands. To increase the likelihood of success, take the phone out of any case to expose the volume buttons. With the phone fully booted and turned on, connect it to your computer by USB. Press and hold the power and volume – keys at the same time. The phone will likely take a screenshoot, keep holding the buttons, afterwards it will bring up a reboot countdown message. With one second left, start pressing the volume + button while still keeping the power and volume – buttons pressed. The phone will show a black screen and windows with make its connection sound if you succeeded in reaching ECL mode. Release the button immediately. Look at your computer, you should also see an entry in the Windows Device Manager under “Ports” that reads:
“Qualcomm HS-USB QDLoader 9008 (COMXX)”
where XX is the port. The phone will just reboot if you didn’t click the volume + button sufficiently fast. Keep trying, you will eventually succeed. If the screen on the phone does go black and you don't see the phone listed in the Windows Device Manager, then you should check installation of 9008 port driver.
Start and configure QFIL: Go to the Start Menu or whatever passes for it on your Windows computer and fire up QFIL. Survey the screen:
You should see “Qualcomm HS-USB QDLoader 9008 XX” next to “Select Port…”.
There should be small text in the lower right corner that reads “Storage Type:”; Select “ufs”.
There is a subheading near the upper left that reads “Select Build Type”. Tick “Flat Build”.
Now using the “Browse…” button under the “Select Programmer", navigate to the folder that contains the firehose file, “prog_ufs_firehose_Sdm845_lgev40.elf” and select it.
Extract partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look for “abl_a”, “laf_a”, “abl_b”, and “laf_b”.
Right click on “abl_a”
Select “Manage Partition Data”
Select “Read Data…”
Open a folder and navigate to location where the extracted file is located. The QFIL “Status” output shows the location and filename. On my PC, it reads:
“C:\Users\whoiam\AppData\Roaming\Qualcomm\QFIIL\COMPORT_XX\ReadData_ufs_xxxxx.bin” where XX is the port number and the “xxxxx” are details about the partition name. Copy the file to a dedicated folder and rename it “abl_a.img”.
Repeat the this process for “laf_a”, “boot_a”, “abl_b”, “laf_b”, and “boot_b” partitions. Note the locations of these files as back-ups and also for the following section on rooting.
Use QFIL to get fastboot:
Write the engineering abl’s: In QFIL, do the following:
Right click on abl_a.
Select “Manage Partition Data”
Select “Load Image”
In the dialog, Navigate to the location of the engineering abl_a.img file you downloaded in the preparation section, select it, and click “Open”.
Repeat this same procedure for abl_b.
Erase laf’s: In QFIL, do the following:
Right click on “laf_a”
Select “Manage Partition Data”
Select “Erase”
Confirm that you want to erase
Repeat for laf_b.
Unplug the phone from USB
Press and hold the power and volume - buttons until the LG V35 boot logo appears. Allow the phone to reboot.
Turn the phone off.
Unlock the bootloader:
Enter fastboot mode: Hold the volume + button and plug in the USB cable. The phone will boot to a series of menus that include “Start” and “Power off”.
Run a command prompt as Administrator. If necessary navigate to the directory where you installed adb.exe and fastboot.exe.
Check that the phone communicates with fastboot: Type “fastboot devices” and press enter. It should return details about your device. It reads “LMV350AWMxxxxxxx fastboot” with my phone.
Bootloader unlock: Type “fastboot oem unlock”. Congratulations if it reports OK, your phone is now unlocked. If it reports failed then try another USB port on your PC, a better/different cable, and potentially even another PC.
Reboot the phone
Step 3: Restore download mode and flash to desired rom:
If the current version of Oreo is where you want to be then skip to Step 4.
If you want to upgrade to Pie or eventually Q, then you need to restore the laf_a, laf_b, abl_a, and abl_b partitions to recover download mode. It should be clear from what you have done above with QFIL how to do this.
Download the kdz of your desired rom. The Google/NAO version of Pie is recommended and available at this link, https://lg-firmwares.com/downloads-file/22230/V350ULM20f_00_NAO_US_OP_0218.
To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 4: Install Magisk for Root:
Re-enter EDL mode with the above button dance procedure
Extract boot_a and boot_b partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look "boot_a” and “boot_b”.
Generate a Magisk-patched booted image working directly with the phone:
Download a stable version of Magisk Manager from the official website: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445. It should be saved in the “Download” folder.
In Settings, navigate to Apps & Notifications→ Special access → Install unknown apps. Click on File Manager and set it to allowed.
Open the “File Manager” app and navigate to the Download folder.
Select and install the “MagiskManager-v7.5.1.apk” file keeping in mind that the version numbers may be different.
Connect the phone to USB and place it in file transfer mode.
Copy boot_a.img and boot_b.img to the phone Download folder
Start “MagiskManager” and select “Install”. When presented with the option, tap “Select and Patch a File”.
Navigate to the “Downloads” folder where and select boot_a.img.
There will now be a file named “magisk_patched.img” in the “Downloads” folder. Change its name to magisk_patched_a.img.
Repeat this process with boot_b.img.
Install the Magisk-patched boot images using the PC:
Copy the magisk_patched_a.img and magisk_patched_b to the windows computer.
Put the phone into 9008 EDL mode with the button dance described above.
Start QFIL, configure it as described above, and then click on “Tools” in the menu bar of QFIL and Select “Partition Manager”.
Scroll through the list of partitions and locate boot_a. Right click on it and select “Load Image”. Point it to the magisk_patched_a.img file.
Repeat the previous step for boot_b and load the magisk_patched_b.img file
Reboot your rooted phone.
Step 5: Remove Root Checker: (Added 20200409)
I say with sarcasm that another way that LG has made our lives better was to implement a root-check and monitoring system. Many here are familiar with the root check daemon from the V30. There is a root-check disable twrp package to fix this problem. Installation and use of TWRP for the V35 is tricky. Don't worry, there is another way.
Put the phone in USB debug mode
Connect to your computer
With adb from a command prompt on the computer do the following
adb devices <-- If your devices is properly connect and recognized, adb will respond
List of devices attached
LMV350XXXXXXXXX device
adb shell <-- If you have a shell into the phone you will now see
judyp:/ $
pm uninstall -k --user 0 com.lge.srtc <-- This command removes the root checker, if it succeeds you will get the response:
Success
pm uninstall -k --user 0 com.lge.mlt <-- This command removes the LG monitor, if it succeeds you will get the response:
Success
Happy Rooting!

Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?

THANK YOU for this. Seriously. Really well done. I can't wait to try it if I ever get my phone back into shape where I CAN try it. ?

There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse

cmrntnnr said:
There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
Click to expand...
Click to collapse
I was one of those who leaped to the Korean KDZ. Now I am running NAO firmware. Guide looks well written. I might wind up taking the leap. Good job bro!

Thanks, I follow your steps very carfully, and now I have a rooted v35.

Nicely done. Thank yoh for sharing the result.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse
vavoo said:
Thanks, I follow your steps very carfully, and now I have a rooted v35.
Click to expand...
Click to collapse

So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?

I am stuck at Fastboot Mode. It says the "Device state - Unlocked", but when if I choose Start or Power off/on my phone it just goes back into fastboot everytime.
1. I installed and flashed the Pie rom you linked in step 1
2. I turned "Oem unlock" to On.
3. placed the phone in 9008 mode, backed up abl_a, laf_a, boot_a, abl_b, laf_b, and boot_b.
Loaded the img to abl_a and abl_b.
Finally, Erased laf_a and laf_b
4. within fastboot, unlocked bootloader
Any ideas ?

If the phone unlocked, go back into 9008 EDL mode and restore the laf and abl images using your backups. That should get you booting.

dave1567 said:
Any ideas ?
Click to expand...
Click to collapse
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.

vlad48 said:
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.
Click to expand...
Click to collapse
I didn't use your bat since it looks like I can still boot into 9008 mode with the button dance method.
Unfortunately, still nothing!
I flashed my abl_a.img and abl_b.img backups I made to the abl_a/b partitions and flashed your FTM_BL.img to my FTM partition, but it didn't seem to do anything except cause some graphical glitches within fastboot menu (everything still functioned though)
Just in case, I re-locked my phone (fastboot oem lock) and started the QFIL process over (flashing with engineered abl_a and abl_b imgs)
Then within fastboot mode, I ran "fastboot oem unlock" a few times because it fails, but finally it went through
Now the phone is unlocked again, but still just always just boots into fastboot mode!

Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.

vlad48 said:
Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.
Click to expand...
Click to collapse
Unfortunately, I don't understand. Thanks for trying to help though.
Anyways, I managed to fix the problem and I'm all set.
- Restored my laf_a and laf_b partitions
- Booted into download mode and re-installed the pie image with LG Up.
- Was now able to boot normally
- Followed the instructions in the guide to get magisk installed and now I'm all set!
Thanks all and hope this helps someone

I scouted my way through these very same steps a couple weeks ago. Soft bricked my device a couple times ? but eventually got her there. Glad too see a dedicated guide is out now. Only problem I've run into is the ctsprofile:fail problem. Been able to fix with spoof pixel fingerprints but it's not ideal. Still looking for solutions if anyone knows anything.

Iantuition said:
So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?
Click to expand...
Click to collapse
What is the minimum needed for you to enter download mode? I have backups of most partitions i will be happy to share and you can use Qfil to flash those to get to download mode then use LGUP to flash a normal kdz? If so, let me know.

so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do

Sorry to hear that. The first time I tried to use QFIL I got a Sahara error and could not see partitions. It was resolved by reinstalling the 9008 port driver and then QPST in that order. It happened again later when windows tries to be helpful by automatically reinstalling drivers when the phone is plugged in but with a mode change.
Flowtron3000 said:
so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do
Click to expand...
Click to collapse

Will this help me sim/carrier unlock my v35awm?

Can you lock the bootloader after this is done and keep root? Need it for banking apps.