Database Develop

[Q] Need Help-VZW Dev Edition (I've read)

I got a Dev Edition from Swapp. It was unlocked, rooted, with TWRP - PRE-camera update.
I struggled many hours last night to finally get it to where it is now. I now have: unlocked with Kit Kat
BUT, can't reboot into recovery. I've tried pushing the new TWRP in several different ways. (wanting that AND root). When trying to go to recovery, it simply goes to Any on his back ("no command"). I can from there push buttons and reboot back into the phone so it is usable.
I had to use the Toolkit to install TWRP...(at least I think it's installed - can't get there to really tell).
I went through so many things last night to get it to it's current state. It took a while to get the thing back to stock recovery and stock firmware...then I let it download camera update and then Kit Kat.
Just having a time with this TWRP thing. I can't Fastboot OR mfastboot. PC says missing aAdbWinApi.dll....not sure how to rectify. I've downloaded Moto Device Manager. I just downloaded Android SDK bundle to see if that would get me what I needed for fastboot. But, I'm not sure what to do with that Zip (too many things in it...no "install" that I see).
Work is going to kill me today because my mind is NOT going to be where it should be.
I sure would appreciate someone taking the time to point; state; show; give specific links; something if possible to get my TWRP and root going.
That was alot. Now I have to get my kids out to school.
Thanks!

http://forum.xda-developers.com/showthread.php?t=2536200
[HOW-TO][DEV EDITION ONLY]Root on 4.4 KitKat
Sent from my XT1060 using Tapatalk 2

One of the important things in the thread chaoslimits posted the link to is the newer twrp that is 44 compatible. It was released just overnight, after KK offically got pushed out by VZW.
Before that, there was a TWRP with 44 in its name, but it would hang if you tried to boot into it after you've rooted. The new version works.
So you might just be able to fastboot flash recovery with that newer TWRP and be good.

KidJoe said:
One of the important things in the thread chaoslimits posted the link to is the newer twrp that is 44 compatible. It was released just overnight, after KK offically got pushed out by VZW.
Before that, there was a TWRP with 44 in its name, but it would hang if you tried to boot into it after you've rooted. The new version works.
So you might just be able to fastboot flash recovery with that newer TWRP and be good.
Click to expand...
Click to collapse
I'm pretty sure I had the newest TWRP last night. I think it's my ADB & fastboot that's killing me. But, you'd think it would at least boot into normal recovery if it had not been able to work.

Dburgessme2 said:
I'm pretty sure I had the newest TWRP last night. I think it's my ADB & fastboot that's killing me.
Click to expand...
Click to collapse
If you got TWRP on your phone, fastboot & adb should have been working. Did something change on your PC? How does the phone show up on your PC in Device Manager?
Dburgessme2 said:
But, you'd think it would at least boot into normal recovery if it had not been able to work.
Click to expand...
Click to collapse
Also, not sure I follow what you mean because by flashing TWRP you overwrote the normal recovery. So booting normal recovery would no longer be possible after you flashed TWRP on.

Dburgessme2 said:
I'm pretty sure I had the newest TWRP last night. I think it's my ADB & fastboot that's killing me. But, you'd think it would at least boot into normal recovery if it had not been able to work.
Click to expand...
Click to collapse
Shut the phone down and reboot into fastboot mode (volume + power). The connect it to your PC. Open a command prompt and change directory to your fastboot location under AndroidSDK. Enter:
"fastboot devices"
and see if your phone shows up.

chaoslimits said:
Shut the phone down and reboot into fastboot mode (volume + power). The connect it to your PC. Open a command prompt and change directory to your fastboot location under AndroidSDK. Enter:
"fastboot devices"
and see if your phone shows up.
Click to expand...
Click to collapse
Yes, it shows there.

Dburgessme2 said:
Yes, it shows there.
Click to expand...
Click to collapse
Have you put the recovery IMG in the same folder that fastboot is located, fastboot cmd window type fastboot flash recovery twrp.2.6.3.1-ghost-4.4.img
Sent on my Moto X

Dburgessme2 said:
Yes, it shows there.
Click to expand...
Click to collapse
I AM ROOTED with TWRP! yay! (did it from my work Win XP machine)
Thanks to ALL!

Dburgessme2 said:
I AM ROOTED with TWRP! yay! (did it from my work Win XP machine)
Thanks to ALL!
Click to expand...
Click to collapse
Congratulations, I was wondering if you ever got it up and running, enjoy!!
Sent from my XT1060 using Tapatalk

LG Flash Tool does not recognized bricked G2 (vs980)

SERIOUSLY STUMPED!!
I was in the process of flashing the 24a ROM when i realized i had to put one more file in the storage in order to flash the ROM completely,but only after i wiped my "laf.img" so i got stuck in fastboot mode ..ended up using fastboot commands to recover my download mode but now I cannot get my device to be recognized by either laptop i tried re-installing drivers and unplugging re plugging,restarting both laptops..i just really don't know what else to do somebody please help ((
To anyone who took the time to read this and help out I also have team viewer available and thank you, any help is given thanks in advance i just need my phone back guys :/

TTMBeats said:
SERIOUSLY STUMPED!!
I was in the process of flashing the 24a ROM when i realized i had to put one more file in the storage in order to flash the ROM completely,but only after i wiped my "laf.img" so i got stuck in fastboot mode ..ended up using fastboot commands to recover my download mode but now I cannot get my device to be recognized by either laptop i tried re-installing drivers and unplugging re plugging,restarting both laptops..i just really don't know what else to do somebody please help ((
To anyone who took the time to read this and help out I also have team viewer available and thank you, any help is given thanks in advance i just need my phone back guys :/
Click to expand...
Click to collapse
I had to install 4 different items under Device Manager to get mine working, when you open it up, are there any icons with the yellow flag on them in the device manager tree?

mjones73 said:
I had to install 4 different items under Device Manager to get mine working, when you open it up, are there any icons with the yellow flag on them in the device manager tree?
Click to expand...
Click to collapse
no...? I restored mine to stock earlier today but mine was from 12b to 11a so I could take the OTA....

TheOriginalKyle said:
no...? I restored mine to stock earlier today but mine was from 12b to 11a so I could take the OTA....
Click to expand...
Click to collapse
I was just pointing out to the person having issues with the flash tool to make sure they have all the drivers installed...

Solved!!
mjones73 said:
I was just pointing out to the person having issues with the flash tool to make sure they have all the drivers installed...
Click to expand...
Click to collapse
Update : Guys I figured out what was wrong with some help of XDABBEB (the dev of the custom 24a ROM) he actually helped me step by step... turns out I lost my recovery somehow SOOOOO I was stuck with fastboot. Had to push a new recovery via fastboot from there I had to fix a lovely driver issue (courtesy of windows) which in the end I couldn't get it to work so I went with KOUSH universal adb driver which is a LIFESAVER! From there had to adb push the bootstack zip and the ROM file itself installed via TWRP 2.7.0.0 and did a clean install...... As you can see it was a fun night/day for me.. But as of now I am running 24a rooted and with all of XDABBEB'S mods.. And it is beautiful. Lol I know you alot of people won't take the time to read this whole thing but just in case anyone has the same problem there you are!

mjones73 said:
I was just pointing out to the person having issues with the flash tool to make sure they have all the drivers installed...
Click to expand...
Click to collapse
Sorry thought you were the op

TTMBeats said:
Update : Guys I figured out what was wrong with some help of XDABBEB (the dev of the custom 24a ROM) he actually helped me step by step... turns out I lost my recovery somehow SOOOOO I was stuck with fastboot. Had to push a new recovery via fastboot from there I had to fix a lovely driver issue (courtesy of windows) which in the end I couldn't get it to work so I went with KOUSH universal adb driver which is a LIFESAVER! From there had to adb push the bootstack zip and the ROM file itself installed via TWRP 2.7.0.0 and did a clean install...... As you can see it was a fun night/day for me.. But as of now I am running 24a rooted and with all of XDABBEB'S mods.. And it is beautiful. Lol I know you alot of people won't take the time to read this whole thing but just in case anyone has the same problem there you are!
Click to expand...
Click to collapse
i think this is the problem i am having but i don't know how you did any of that to fix it!?!?!? I am going out of town in 2 days and i desperately need my phone. Got any help for me?

First thing first see if you can get into recovery
Sent from my VS980 4G using XDA Premium 4 mobile app

TTMBeats said:
Update : Guys I figured out what was wrong with some help of XDABBEB (the dev of the custom 24a ROM) he actually helped me step by step... turns out I lost my recovery somehow SOOOOO I was stuck with fastboot. Had to push a new recovery via fastboot from there I had to fix a lovely driver issue (courtesy of windows) which in the end I couldn't get it to work so I went with KOUSH universal adb driver which is a LIFESAVER! From there had to adb push the bootstack zip and the ROM file itself installed via TWRP 2.7.0.0 and did a clean install...... As you can see it was a fun night/day for me.. But as of now I am running 24a rooted and with all of XDABBEB'S mods.. And it is beautiful. Lol I know you alot of people won't take the time to read this whole thing but just in case anyone has the same problem there you are!
Click to expand...
Click to collapse
Can you please give us step by step instructions?
Earlier I have updated my phone to 24A. Then rooted and tried to install irobot25 to install the TWRP and ended with the fastboot mode on the phone. Currently the phone is just recognized as Android phone but not as LG VS980. I am in the same situation as you are earlier.
I really appreciate your help. My phone is in this state from the past 2 weeks and really getting frustated with it.

Download the koush USB driver Google search it first then let me know when that's done
Sent from my VS980 4G using XDA Premium 4 mobile app

TTMBeats said:
Update : Guys I figured out what was wrong with some help of XDABBEB (the dev of the custom 24a ROM) he actually helped me step by step... turns out I lost my recovery somehow SOOOOO I was stuck with fastboot. Had to push a new recovery via fastboot from there I had to fix a lovely driver issue (courtesy of windows) which in the end I couldn't get it to work so I went with KOUSH universal adb driver which is a LIFESAVER! From there had to adb push the bootstack zip and the ROM file itself installed via TWRP 2.7.0.0 and did a clean install...... As you can see it was a fun night/day for me.. But as of now I am running 24a rooted and with all of XDABBEB'S mods.. And it is beautiful. Lol I know you alot of people won't take the time to read this whole thing but just in case anyone has the same problem there you are!
Click to expand...
Click to collapse
I'm in the exact same position as you, if you could help me out with what you did the unbrick this thing that would be great. Thanks

Even KOUSH drivers don't work
Digging up this thread ...
I have a bricked G2.. Flashing a ROM via LGFLASHTOOL 2014 went bad at 50%.. Now all it does is Firmware Update Mode.
Before the G2 was recognized and accessible, but now even the KOUSH drivers don't recognize the phone.
I tried reinstalling, uninstalling, rebooting, etc but keep getting the error: "This device cannot start. (Code 10)"
Command prompt ADB commands don't work either because the phone just isn't recognized.
Where do I go from here please?

elwnvd said:
Digging up this thread ...
I have a bricked G2.. Flashing a ROM via LGFLASHTOOL 2014 went bad at 50%.. Now all it does is Firmware Update Mode.
Before the G2 was recognized and accessible, but now even the KOUSH drivers don't recognize the phone.
I tried reinstalling, uninstalling, rebooting, etc but keep getting the error: "This device cannot start. (Code 10)"
Command prompt ADB commands don't work either because the phone just isn't recognized.
Where do I go from here please?
Click to expand...
Click to collapse
Same. I have bricked a L70.

[help] got a soft brick after a build.prop edit

A while earlier I was trying to enable tethering on my at&t N6 by editing the build.prop and after the reboot it's stuck in a boot loop. I don't imagine that this is important but it doesn't get to the dots animation; just white Google and the unlock at the bottom. I am still able to get into fastboot and recovery (stock one). I have a backup of the correct build.prop in the /system file named build.prop.back , so I'm hoping that there's a way to revert to that without needing to wipe my device again, but I'm not sure.
I found this thread, however my computer isn't recognizing the device when it's in recovery mode. I have the fastboot drivers installed (needed to root), so that may be why but, again, I'm not sure. the adb devices command shows that there is no device, I imagine because the driver is not installed.
any help would be appreciated. thanks in advance.

Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979

jj14 said:
Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Unfortunately that didn't fix the problem.
Do you know if the fastboot driver and recovery driver would be different? As far as I can tell from my research, I think they're the same, but I could be wrong. Hopefully that's the problem and you can direct me towards the correct driver.
If I select "show hidden devices" in the device manager, it shows the phone as ADB Interface, and I tried undating the driver for that but it said it was already up to date. not sure what to do from here.
Thanks for your help.

Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.

jawmail said:
Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.
Click to expand...
Click to collapse
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful

momo5732 said:
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful
Click to expand...
Click to collapse
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.

jawmail said:
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.
Click to expand...
Click to collapse
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...

momo5732 said:
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...
Click to expand...
Click to collapse
Cool glad it's working. Yes backup=nandroid
It's cool now I've also noticed the computer recognizes phone in TWRP. You can drag and drop files onto the phone while it's in TWRP not just booted in android, couldn't do that before unless I'm wrong which is often. This is really cool as I always forget a file or two or its location on SD card.

[STOCK][M][TMO] Guide H811 20i & 20o Bootloader Unlock + Root + TWRP

Note : This guide is for H-81120-I & H-81120-O the latest update any firmware version below it will cause hard-brick so be careful before attempting anything, i wont be held responsible.
As a user with less knowledge about Commands and all, i was searching for answers by reading threads here and there and found my answers though some time tricky and sometimes easy.
Also in reading those threads i found many fellow members stumble upon resulting Soft bricks and in some cases a Hard brick or can say making their beloved G4 a paper weight.
So i thought i must put some really easy steps in order to clearly guide people like me who are too noob to understand the sophisticated developers steps.
Another reason for this Thread is also i saw many people asking about how to etc after updating to 20-O update for our H811 MM.
Few things to Prepare before Start
1- Properly Install Drivers for your H811 Variant of G4, cant find them Install LG Bridge.
2- Read the Whole thread before starting anything.
3- Confirm that all requirements are full filled and your variant is capable of everything mention in the OP.
4- Enable Developer Option then inside it enable OEM unlock and Usb debugging.
5- Always use Command prompt as Administrator.
6- Make a folder name G4 and paste all the file required for the unlocking in it for easy access and remembrance.
7- For Safer side after unlocking the bootloader boot into TWRP from fast boot and do not install TWRP.
8- Flash your SuperSU after that boot into android and see if all works.
9- Again Via Fastboot boot into TWRP make a backup of everything working fine. Boot into android.
0- Again same Via Fastboot boot into TWRP and now install your TWRP image via TWRP install function. So if by any means this is the culprit you can still revive your phone via your backup.
Attachments to Download
1- Adb Package can be found Here.
2- Download the latest TWRP.img 3.0+ from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Since downloading is complete now simply unzip the adb folder (containing fastboot by default) and paste both the TWRP image file and SUPERSU zip inside it.
Now Hold Shift and Open Command prompt here.
1- Input command to see if your device is visible in ADB.
Code:
adb devices
if you see your device and the status is off line then there will be a prompt on your G4 screen waiting for approval, accept it and input same command now all will be fine.
2- Now input below commands one by one. ( All credits to Autoprime )
Code:
adb reboot bootloader ( This will reboot your device to Fastboot mode )
fastboot oem unlock ( This will wipe all your data )
fastboot getvar unlocked ( This will check your bootloader status: Should be successful )
fastboot boot twrp-3.0.2-0-h811.img ( Phone boots TWRP ) Please put the full file name with .img extension or it wont work.
3- Now the Phone should be in TWRP install SuperSU from there which you have already pasted inside your external SD card.
4- Reboot to system and see if SuperSU is installed. In some cases First flash of SuperSU does not work if your case is same the again boot to Fastboot and from there boot into recovery, since your bootloader is unlocked no need to repeat the unlock OEM command.
5- Now for safer side follow the steps 7, 9, 0 mention in Preparation heading above.
Hopefully all will be in your favor.
Useful Links if you still fail
Kdz 20-O after download must be unzipped
H81120o_00_0613.kdz
LGUP Software:
( All credits to MicroMod777 )
Disclaimer: Nothing in this thread is my work, if i have missed any credit please do let me know i will add. I know several guides are available for same purpose so if any body finds it offending any rights can ask the moderators to remove this thread. The purpose only is to guide simple people like me to save their devices from getting bricked.

As by reading the thread many people are falling for permanent TWRP installation as its mention in the OP anyways for people not getting permanent Recovery follow below:
Boot to TWRP from fastboot Bootloader
When recovery comes up click Install >>>> then in the right below corner you ll see a tab for IMAGE >>> press it browse the recovery IMG which you stored in your SD card >>> swipe to flash >>> From asking where to install >>> select recovery >>> DONE.

SignatureBoy said:
Attachments to Download
1- Adb Package can be found Here.
2- Download the from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Click to expand...
Click to collapse
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.

DrakenFX said:
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
the ADB package i uploaded contains the Fastboot inside it
The thread clearly states it for 20-O

SignatureBoy said:
the ADB package i uploaded contains the Fastboot inside it
Click to expand...
Click to collapse
ok i meant the TWRP file needs to be in the same folder where Fastboot file is

DrakenFX said:
ok i meant the TWRP file needs to be in the same folder where Fastboot file is
Click to expand...
Click to collapse
That is also mention if you read the first post,
Since downloading is complete now simply make a folder and put all files downloaded inside it unzip the adb folder and paste both the TWRP image file and SUPERSU zip inside it.
Click to expand...
Click to collapse

SignatureBoy said:
DrakenFX said:
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
The thread clearly states it for 20-O
Click to expand...
Click to collapse
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.

ApokrifX said:
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.
Click to expand...
Click to collapse
yes it is for 20-O only

SignatureBoy said:
yes it is for 20-O only
Click to expand...
Click to collapse
Thanks for clarification. I’d change 1st post a bit:
Few things to Prepare before Start
0. LG G4 with 20o (stock) firmware.

When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
DanGarion said:
When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
Click to expand...
Click to collapse
Nevermind, I forgot about OEM Unlock...

thanks for the write up

This is not specific to 20o. It's the same steps we've been using all along. Nothing new to see here.
Sent from my LG-H811 using XDA-Developers mobile app

problem with fastboot
Thanks you for helping:fingers-crossed:

problem with fastboot
Hi,
I am a newbie in xda. I am trying to root and install TWRP into my lg g4. I am using software version H81120o. I checked enable OEM unlock and USB debugging. I have downloaded lg driver though lg bridge and all the files from the post. However, I got two problem while installing the twrp-3.0.2-0-h811.img.
1st problem (stuck here and need to reboot also not showing h811 on "the list of devices attached" after typing command "adb reboot bootloader"):
C:\Windows\system32>adb devices
List of devices attached
LGH811xxxxxxxx device
C:\Windows\system32>adb reboot bootloader
C:\Windows\system32>fastboot oem unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.012s
C:\Windows\system32>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.004s
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
cannot load 'twrp-3.0.2-0-h811.img': No error
2. 2nd problem(stuck here and need to reboot):
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
< waiting for device >
I checked online this problem might do with driver not up to date. Under device manager, my lg g4 is recognized under android device with android bootloader interface.
What should I do now?
Thanks you for helping:fingers-crossed:

This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??

I did everything but can't seem to get TWRP installed

Thanks a lot for this write up. I have been trying for about 2 weeks to root my g4 and it worked finally, So many thanks to you

The Remedy said:
This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??
Click to expand...
Click to collapse
same problem here but I just now got it working...sort of . I still can not make anything come up except the factory data reset when I use the phone volume and power button.
I thought it might be just that I wasn't coordinated enough so I downloaded this small app to do a recovery reboot.
After I installed the app and used it, I got the little android guy with his chest opened with the red triangle. I took out my battery, put it back in and booted my phone with the power button.
I then connected my phone to computer via usb and went back into adb and opened TWRP and installed the twrp-3.0.2-0-h811.img again but this time I looked around a little more first, and noticed a setting to either install in boot or recovery partition. I selected recovery partition (neither were selected) and installed it. Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.

I had the same issue but when u get into twrp make sure the IMG is in your SD card and to permanently have twrp installed go to home and press install.. Choose from image and install hope this helps
Sent from my LGLS992 using Tapatalk

fuzzy_ said:
same problem here but I just now got it working...sort of ................
Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.
Click to expand...
Click to collapse
In regard to booting into TWRP recovery with just the power and vol buttons, I just read this on another thread:
It boots into what appears to look like a default LG G4 factory reset page. For me, i clicked reset, and then yes, and surprisingly it brought me to where i wanted to go. TWRP Recovery.
I tried this and it worked for me as well.
I had been there before and tried it and it did a factory reset after I had spent an hour or two tweaking my phone, I was not a happy person. This time I did feel almost positive I had TWRP installed correctly and did not have nearly as much time spent getting things set up like I want them on my phone...It was still scary pressing that reset button and yes button.
If you don't have TWRP (or maybe some other recovery) installed it will factory reset your phone. I just thought I would share this and what happened with me. Do it at your own risk.

[ROM]Lineageos 18.1 for LG G8s ThinQ [Betalm][WIP]

Code:
*** Disclamer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Introduction
This is the LineageOS 18.1 for LG G8s ThinQ
Click to expand...
Click to collapse
Installation instructions
1. Install Q Stock Rom onto your phone , follow some tutorial you can find in this forum
2. Flash boot.img and dtbo.img by typing fastboot flash boot boot.img and fastboot flash dtbo_a dtbo.img and fastboot flash dtbo_b dtbo.img
3. Wipe your userdata by typing fastboot erase userdata
4. Reboot the phone and immeditly do the recovery key combination
5. In Lineageos recovery select install and then sideload from adb
6. On your computer type adb sideload pathtotheromzip and press enter
7. The rom should now be flashed , flash gapps and other mods like magisk the same way
Click to expand...
Click to collapse
Download
ROM
RECOVERY
Click to expand...
Click to collapse
Changelog
Code:
Current changelog:16.01.2021
[note] 1st Release of Lineage 18.1
[new] Android 11 R
[changed]
[fixed] Rom boots into OS
Older changelogs:
Click to expand...
Click to collapse
FAQ
What doesnt work ?
You tell me
This is only for G8s not for G8 also not for G8X
VOLTE DONT WORK AND IT WONT EVER WORK
For Gapps i recommend NikGapps
Click to expand...
Click to collapse
Thanks To/Credits
Code:
@SGCMarkus
Sources
Code:
[URL="https://github.com/J0SH1X/android_kernel_lge_sm8150]Kernel[/URL]
[URL="https://github.com/J0SH1X/android_device_lge_sm8150-common"]Common[/URL]
[URL="https://github.com/J0SH1X/android_device_lge_betalm"]Device[/URL]
[URL="https://github.com/J0SH1X/android_device_lge_beta-common"]Device-Common[/URL]

Great work. Do you plan to do official LineageOs version?

Any chance for g8?

We wait for the next releases, finally something new. Already installed but hopefully soon a fix for the headphone jack

Great Work!!

Hello! Excuse me, is there a chance to install TWRP on the LG G8s?

thanks for your work that exactly what im looking for
lg makes some good hardware but the worst software support, im corrently waiting for january security patch but not yet
i want to ask if you will keep supporting LG G8S ?

OzAcid22 said:
We wait for the next releases, finally something new. Already installed but hopefully soon a fix for the headphone jack
Click to expand...
Click to collapse
Hello, did you test the variant of the 19 or 23?

Any1 that tried it can tell pros and cons vs LG stock Android 10 rom ?.
I'd like to try it but that means loosing DTS: X codec, equalizer or whatever it is that makes sound much better, and as long as I know Android 11 is worse than 10 for gaming, isn't it?
Does this rom has newer & better drivers for Adreno GPU?

BlackSunCL said:
Hello, did you test the variant of the 19 or 23?
Click to expand...
Click to collapse
19 but in 23 it has not been fixed yet I think, just read the change log of 23

Eduxki said:
Any1 that tried it can tell pros and cons vs LG stock Android 10 rom ?.
I'd like to try it but that means loosing DTS: X codec, equalizer or whatever it is that makes sound much better, and as long as I know Android 11 is worse than 10 for gaming, isn't it?
Does this rom has newer & better drivers for Adreno GPU?
Click to expand...
Click to collapse
I change everything a bit, the rom is obviously more stock and faster, especially if you use the gestures for navigation, it is true you lose the audio features, On the gaming side, I think it doesn't change much and I think it has the same drivers as the stock rom. The sure thing is that if you love android "stock" it is much better, unfortunately it is still very unripe for certain aesthetic things(For example the "notification panel" top bar turns out to be lower than the height of the notch, but you can fix it through some mods and magisk) but maybe soon it will be fixed.

I need help, I flash both the boot.img and the dtbo.img like said in the instructions and when I try to reboot into said Lineageos recovery it never works and I tried ever feasible key combination and it never goes into a lineageos recovery to continue the flashing, Any help or feed back would be appreciated.

sockopucko said:
I need help, I flash both the boot.img and the dtbo.img like said in the instructions and when I try to reboot into said Lineageos recovery it never works and I tried ever feasible key combination and it never goes into a lineageos recovery to continue the flashing, Any help or feed back would be appreciated.
Click to expand...
Click to collapse
I would recommend a flash of the stock system and then repeat the steps, if the volume keys and the Power on / off work you should go to the lineage recovery. Have you checked if there is any error during the terminal flash? Or check the files by re-downloading them, let me know if it works, to enter recovery mode you have to keep the volume key down and the power key, at the first writing you have to leave the power key and then press it again

OzAcid22 said:
I would recommend a flash of the stock system and then repeat the steps, if the volume keys and the Power on / off work you should go to the lineage recovery. Have you checked if there is any error during the terminal flash? Or check the files by re-downloading them, let me know if it works, to enter recovery mode you have to keep the volume key down and the power key, at the first writing you have to leave the power key and then press it again
Click to expand...
Click to collapse
Ok well I managed to get the recovery working by tapping the volume down key while the lg logo was up but now every time I try to adb sideload the Lineageos file it get's stuck at 47% on computer and then spits out an error saying failed to read command no error I've tried a number of "fixes" to no avail.

sockopucko said:
Ok well I managed to get the recovery working by tapping the volume down key while the lg logo was up but now every time I try to adb sideload the Lineageos file it get's stuck at 47% on computer and then spits out an error saying failed to read command no error I've tried a number of "fixes" to no avail.
Click to expand...
Click to collapse
I initially had the same problem apparently maybe you have multiple versions of adb installed, try to delete and uninstall everything and then install only one, check that the zip file is not damaged by simply opening it from the PC, if it gives you an error that will be the problem , if you had to try several times to transport the file through adb sidelaod just go to advanced and restart the recovery and then try the step again

OzAcid22 said:
I initially had the same problem apparently maybe you have multiple versions of adb installed, try to delete and uninstall everything and then install only one, check that the zip file is not damaged by simply opening it from the PC, if it gives you an error that will be the problem , if you had to try several times to transport the file through adb sidelaod just go to advanced and restart the recovery and then try the step again
Click to expand...
Click to collapse
I've uninstalled and reinstalled adb drivers on my computer but I'm still getting the same problem I think I'll just wait until there's a twrp recovery for the device being that it makes processes like this a whole lot easy, Thank you for the help anyway I appreciate it.

You can only install 19 the others don't work .. even if you install 19 and try to update to the latest version after the update it doesn't work anymore.

sockopucko said:
Ok well I managed to get the recovery working by tapping the volume down key while the lg logo was up but now every time I try to adb sideload the Lineageos file it get's stuck at 47% on computer and then spits out an error saying failed to read command no error I've tried a number of "fixes" to no avail.
Click to expand...
Click to collapse
Its normal for it to get "stuck" at 47%, because at that point its sideloaded to device already and should already be showing its installing on the device, it does give a wierd error but installs anyway, allow it to install and make sure you erased userdata in fastboot before trying to flash
Btw - you can install from ext SD as well not just sideload
If all fails, restore with LGup and make sure you first boot into lg rom and pass setup and FRP, device gives a wierd formatting bootloop if you dont.
Boot into fastboot
Erase userdata
Flash boot and dtbo
Boot into los recovery
Sideload /install zip from SD
After installing step 2 passes, reboot, give it a minute, rom should be booted

HI guys! i have any hard problem, i've delete all partition with "QFIL" and i've not files backup.qcn or rawprogram.xml or patch.Please if is possible load here your files for help me- ty much guys

Qualcuno può aiutarmi?