Database Users

Twrp install problems

I am running cwm on Verizon and I am trying to install aospa(4.4) on my phone. I have to use twrp and every time I try to install twrp, it fails and I am left with a nonworking recovery. How do I install the latest version of twrp?
Sent from my LG-VS980

oadam11 said:
I am running cwm on Verizon and I am trying to install aospa(4.4) on my phone. I have to use twrp and every time I try to install twrp, it fails and I am left with a nonworking recovery. How do I install the latest version of twrp?
Sent from my LG-VS980
Click to expand...
Click to collapse
Try flashing with the app provided below, will do either a zip or a img file. Just make sure your new Recovery file has been Loki'd.
https://play.google.com/store/apps/details?id=com.cgollner.flashify

Jimi Mack said:
Try flashing with the app provided below, will do either a zip or a img file. Just make sure your new Recovery file has been Loki'd.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
How do I make it loki'd?
Sent from my LG-VS980

oadam11 said:
How do I make it loki'd?
Sent from my LG-VS980
Click to expand...
Click to collapse
The Recovery imagine you downloaded should already be Loki'd. Verify this from the location or forum you got it from.

Yeah Help
Ok totally dont get this, first i've rooted the thing, but cant seem to get into twrp. I installed it using flashify, I reboot goto the factory reset screen, hit power 3 times and black screen. I just want to flash a rom my galaxy s2 was so EASY

timenewton said:
Ok totally dont get this, first i've rooted the thing, but cant seem to get into twrp. I installed it using flashify, I reboot goto the factory reset screen, hit power 3 times and black screen. I just want to flash a rom my galaxy s2 was so EASY
Click to expand...
Click to collapse
Make sure the recovery you flashed with flashify was a zip or img, make sure it was for your phones model, make sure its loki'd, or download Quickboot from the play store and tap recovery.
Sent from my LG-D800 using xda app-developers app

I cant get adb to work just keeps saying looking for device, I installed the LG drivers, checked debugging, goto pc connection, ethernet. The recovery I have is an img from http://forum.xda-developers.com/showthread.php?t=2449670 for verizon.
---------- Post added at 06:57 AM ---------- Previous post was at 06:13 AM ----------
Ok I got adb to work I get to ./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.3-g2vzw.img then it says cant execute: permission denied

timenewton said:
I cant get adb to work just keeps saying looking for device, I installed the LG drivers, checked debugging, goto pc connection, ethernet. The recovery I have is an img from http://forum.xda-developers.com/showthread.php?t=2449670 for verizon.
---------- Post added at 06:57 AM ---------- Previous post was at 06:13 AM ----------
Ok I got adb to work I get to ./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.3-g2vzw.img then it says cant execute: permission denied
Click to expand...
Click to collapse
Hey 2.6.3.3 is a flashable zip from twrp....from their site try flashify app from playstore too easy as click and boot to recovery

Solved
Ok 2.6.3.2 will install, so install that first then 2.6.3.3 as an image

timenewton said:
Ok 2.6.3.2 will install, so install that first then 2.6.3.3 as an image
Click to expand...
Click to collapse
If you've got 3.2 installed already, if 3.3 is a zip, you should just be able to flash it. :good:

everything went fine until i typed adb reboot recovery
followed the guides on here to flash TWRP, finally got everything flashed through adb and when i went to the final step to reboot in to recovery it said "error : device not found" .... Is this normal? should i just unplug/replug and try the reboot bootloader command again? It said the image was loki verified and flashed succesfully, but when i typed in reboot recovery it said "error: device not found" any advice/help is much appreciated

[Q] Help flashing ROMs

Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.

sydtrakked said:
Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.
Click to expand...
Click to collapse
I'm stuck too, how did you flash the stock file?

sydtrakked said:
Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2587296
here for 12b recoveries
and search through the thread for edited roms

I have the TMO verison but plenty of my friend have successfully flashed trwp using flashify also what kernals and roms are you trying to flash over? are you clean or dirty flashing?

try latest version of twrp..
but i'm relying on twrp 2.6.3.3.. been working since i rooted the phone 2months ago

zekurosu said:
try latest version of twrp..
but i'm relying on twrp 2.6.3.3.. been working since i rooted the phone 2months ago
Click to expand...
Click to collapse
Can you post a link to the latest twrp recovery for tmo? ive been looking but couldn't find one.

I have the vzw g2 and i took the 12b update and rooted it finally today. i have the same issue and your saying i need the newer cwm? extract the .lok and flash? Can you please help me and give me step by step instructions because im stuck in the bad cwm and only have cm 10.2 on my sdcard. ive tried going back to stock but none of those methods are working for me even though i have all drivers and follow everything. i tried the method where i use the kdz files and also the tot files. kdz fails at 49% with no explanation and the tot method never starts after the instructions say unplug then replug back in. Im completely baffled, i havent messed around in awhile.
---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
---------- Post added at 02:32 AM ---------- Previous post was at 02:31 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...

ceredics said:
I have the vzw g2 and i took the 12b update and rooted it finally today. i have the same issue and your saying i need the newer cwm? extract the .lok and flash? Can you please help me and give me step by step instructions because im stuck in the bad cwm and only have cm 10.2 on my sdcard. ive tried going back to stock but none of those methods are working for me even though i have all drivers and follow everything. i tried the method where i use the kdz files and also the tot files. kdz fails at 49% with no explanation and the tot method never starts after the instructions say unplug then replug back in. Im completely baffled, i havent messed around in awhile.
---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
---------- Post added at 02:32 AM ---------- Previous post was at 02:31 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
Click to expand...
Click to collapse
Have you tried to flash back to the 12A and not use the 12b

tbishop91 said:
Have you tried to flash back to the 12A and not use the 12b
Click to expand...
Click to collapse
Nope, the one i was using i believe was the 10. Also, when it boots it was secure boot unsuccessful. Im seeing a handful of people stuck with this with no solution thread.

You used ioroot did you open a cmd prompt and push a loki file using a adb command

tbishop91 said:
You used ioroot did you open a cmd prompt and push a loki file using a adb command
Click to expand...
Click to collapse
I used ioroot res i did. But no i dont recall EVER using adb....

ceredics said:
I used ioroot res i did. But no i dont recall EVER using adb....
Click to expand...
Click to collapse
How did you install your custom recovery did you do it thro the computer or thro your phone itself sorry for the question but im just trying to help and im a little confused

tbishop91 said:
How did you install your custom recovery did you do it thro the computer or thro your phone itself sorry for the question but im just trying to help and im a little confused
Click to expand...
Click to collapse
No i dont mind i appreciate it. i used the FreeGee app in the play store to install the CWM. It was the 60445 or whatever but with a 5 at the end.

ceredics said:
No i dont mind i appreciate it. i used the FreeGee app in the play store to install the CWM. It was the 60445 or whatever but with a 5 at the end.
Click to expand...
Click to collapse
so you flashed A ZIP thro you phone and you flashed it twice and not it wont boot? so you might have to use this method.
http://forum.xda-developers.com/showthread.php?t=2471370

tbishop91 said:
so you flashed A ZIP thro you phone and you flashed it twice and not it wont boot? so you might have to use this method.
http://forum.xda-developers.com/showthread.php?t=2471370
Click to expand...
Click to collapse
It boots and everything, I get into CWM. Just cant flash anything because I get abortion error status 7 every time. I see that method works for the TMO one, i have VZW.
Trying the method you posted now

ceredics said:
It boots and everything, I get into CWM. Just cant flash anything because I get abortion error status 7 every time. I see that method works for the TMO one, i have VZW.
Trying the method you posted now
Click to expand...
Click to collapse
have you tried to use twrp instead of clockwork, I think that's what cwm stands for make sure whatever you do you double check that method does not harm your device.

It didnt work... Fckkkkk. So to make it clearer
VZW
Lg G2
Rooted with io
Rom when rooted was stock latest ota
currently stuck in CWM with nothing to boot into because of consistent abortion then status 7.

can you sideload aboot.img from adb

Id need step by step instructions on how to sideload something because ive never messed with adb. It seems if i adb a different recovery or a specific file it may start to work. Can i sideload TWRP?

let me consult my know it all friend lol

Help can't put rom on phone in TWRP, cant boot

Hello I was going to flash a rom from stock firmware with TWRP recovery installed when I accidentally wiped the system partition as well so there is now no rom on the internal storage and i cannot boot back into the normal firmware cause it just hangs at the LG logo on startup. I tried a USB OTG device in TWRP but it is not being detected and I don't know how to use the phone in mass storage mode inside TWRP. :crying:
Help would be much appreciated!

bump

Have you tried adb sideload? I did the same, wiped everything, system and internal , bacups and all. I managed to sideload a flashable rom, flashed it and managed to boot up. So: ADB Sideload through twrp is your answer.
Sent from my LG-D802 using XDA Premium 4 mobile app

KapteinKing said:
Have you tried adb sideload? I did the same, wiped everything, system and internal , bacups and all. I managed to sideload a flashable rom, flashed it and managed to boot up. So: ADB Sideload through twrp is your answer.
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Was about to try sideload but then just used the flashtool and went back to stock. Thanks anyway!

KiLLa007 said:
Was about to try sideload but then just used the flashtool and went back to stock. Thanks anyway!
Click to expand...
Click to collapse
I'm stuck with the same problem didn't make a back up. I have a ROM but it won't flash because of 12B OTA on G2. So i'm stuck on twrp. Can you send me a link to get flashtool? What else do I need beside flashtool to go back to stock? Thank you

its not system thats the problem, you wiped internal..
adb push the rom to internal. many accurate how to do that with search. dont know top of head
Sent from my LG-D802 using xda app-developers app

Well if you do end up fixing it upgrade to TWRP 2.6.3.4 because it has OTG support!
Sent from my LG-VS980 using xda app-developers app

I'm in the same boat here except I've already tried adb sideload with twrp 2.6.3.3 and it returns an error "cannot read rom.zip" I've tried 3 different zips, many combinations of renaming the zip files. My machine is set to always show file extensions. I've also tried both ways of trying to flash back to stock in download mode. One of them just hangs at BIN CRC check the other will get to 49% and error out. Any suggestions?
Sent from my Galaxy Nexus using xda app-developers app

files and carrier
simonsez2die said:
I'm in the same boat here except I've already tried adb sideload with twrp 2.6.3.3 and it returns an error "cannot read rom.zip" I've tried 3 different zips, many combinations of renaming the zip files. My machine is set to always show file extensions. I've also tried both ways of trying to flash back to stock in download mode. One of them just hangs at BIN CRC check the other will get to 49% and error out. Any suggestions?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
what carrier and flies are you using? What com port is your G2 using? Have you tried using the LG mobile support tool?
I have tried but cant brick this phone, so many ways to communicate

geosnipe said:
what carrier and flies are you using? What com port is your G2 using? Have you tried using the LG mobile support tool?
I have tried but cant brick this phone, so many ways to communicate
Click to expand...
Click to collapse
VS980 Verizon. I've tried Lg flashtool with "LGVS980_20130902_LGFLASHv151.dll"
and VS98010B_13.tot. on com port 41. This one hangs at BIN CRC Check for hours. Won't go any further. I've also tried the uptest method found here in the forums with the files that are in the OP. It gets to 49% and stops and tells me to retry. When I retry it will always stop at 49%\
I can get into download mode and TWRP .While in TWRP, adb recognizes my device and shows recovery next to it. When I go to adb sideload and type adb devices again it will show that I'm in sideload mode but no files will transfer. It just returns error cannot read filename.extension. I've to sideload all kinds of files with different extension types and it always returns the same thing.
---------- Post added at 11:41 AM ---------- Previous post was at 11:27 AM ----------
I just remembered that I had a backup made from a week or 2 ago when I was using cwm recovery. Which isnt recognized in twrp. I didn't loose all of my sdcard content with all this. I was just a moron and forgot to make a twrp backup before wiping my system. And the only rom I have on my sdcard aborts about halfway through.
Sent from my Galaxy Nexus using xda app-developers app

Ok...so I was able to adb push a file to my sdcard using "adb push filename.zip /sdcard/filename.zip. It returned the size and time it took to transfer. But adb push ROM.zip /sdcard/ROM.zip gives me nothing and seems as tho it may have froze up the command prompt. GRR!
---------- Post added at 12:19 PM ---------- Previous post was at 11:52 AM ----------
Got it...thanks anyway.

simonsez2die said:
VS980 Verizon. I've tried Lg flashtool with "LGVS980_20130902_LGFLASHv151.dll"
and VS98010B_13.tot. on com port 41. This one hangs at BIN CRC Check for hours. Won't go any further. I've also tried the uptest method found here in the forums with the files that are in the OP. It gets to 49% and stops and tells me to retry. When I retry it will always stop at 49%\
I can get into download mode and TWRP .While in TWRP, adb recognizes my device and shows recovery next to it. When I go to adb sideload and type adb devices again it will show that I'm in sideload mode but no files will transfer. It just returns error cannot read filename.extension. I've to sideload all kinds of files with different extension types and it always returns the same thing.
---------- Post added at 11:41 AM ---------- Previous post was at 11:27 AM ----------
I just remembered that I had a backup made from a week or 2 ago when I was using cwm recovery. Which isnt recognized in twrp. I didn't loose all of my sdcard content with all this. I was just a moron and forgot to make a twrp backup before wiping my system. And the only rom I have on my sdcard aborts about halfway through.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
The LG Flash Tool and Mobile Support Tool are 2 different utilities for the phone.
Glad to hear you are back up and running!

geosnipe said:
The LG Flash Tool and Mobile Support Tool are 2 different utilities for the phone.
Glad to hear you are back up and running!
Click to expand...
Click to collapse
I actually tried both utilities but both resulted in error. I ended up getting it with "adb push ROM.zip /sdcard/ROM.zip" . It took a really long time, I ended up just trying one last time and left it alone for about 10 mins. When I came back to it, it showed the size of file and time it took to push. I figured I'd post all of this on the off chance it may help someone who has a Custom recovery but no backup or Rom zips to flash on the device.

simonsez2die said:
I actually tried both utilities but both resulted in error. I ended up getting it with "adb push ROM.zip /sdcard/ROM.zip" . It took a really long time, I ended up just trying one last time and left it alone for about 10 mins. When I came back to it, it showed the size of file and time it took to push. I figured I'd post all of this on the off chance it may help someone who has a Custom recovery but no backup or Rom zips to flash on the device.
Click to expand...
Click to collapse
Man you are a life saver. Thanks for coming back and posting your solution for this problem. I had the exact same issue and after hours of trying to install different "rom.zip" files with the same "cannot read rom.zip" error, this finally worked.
I cannot stress enough, how helpful it is when someone like you finds an answer to a problem and takes the time to come back and post the solution.
Thanks again!!!

Got stuck trying to root, just want to return to stock/factory settings.

I'm new so please forgive me and my ignorance through all of this. I had a great root experience with my old LG G3, so when I got my Axon 7 (A2017U) I thought I'd try to root it too. I tried to follow DrakenFX's guide (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204) but I bit off more than I could chew. I got to the point where I had TWRP up, but this is where I think things started to fall apart. I was confused by the instructions and in a haste I continued anyway. In TWRP I went to Wipe>Format Data typed in yes like TWRP said and boom, I had no idea what happened. Rebooting only got a screen that said "Type in your password" but my passcode I had on the phone before it bricked didn't work. So by now I start panicking a bit. I thought I made a mistake earlier so I went back and tried to reinstall TWRP by putting the phone into EDL. The phone got stuck that way for a while, but I now I have it in TWRP. Right now, I just want to get back to safe stock android.
I'm 200% sure I messed with something I wasn't supposed to and I believe that is the system image(?)which Draken also linked (http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53). I'm downloading it as I type. I'm going to do my best to leave my phone just like it is right now, in TWRP, and wait for more advice on this before I do anything else.. What I'm curious about is where did I go wrong and what do I need to do to get my phone working again, preferably without returning it? Thank you for any advice you have to offer.
Update: It's worth noting I didn't know to enable OEM Unlocking when I was in stock android. Dumb move I know. I'm new here.

What software version are u on?

xiong77 said:
What software version are u on?
Click to expand...
Click to collapse
As far as I know I (was) on Android 6.0 A2017U B29. TWRP version 3.0.2-0

Get DrakenFX b29 mergeboot stack and b29 stock system and flash it then u should be OK. I did this too.

xiong77 said:
Get DrakenFX b29 mergeboot stack and b29 stock system and flash it then u should be OK. I did this too.
Click to expand...
Click to collapse
I tried, but the downloads take extremely long and are unreliable for me. I was downloading the stock system file at around 14 kbps and it eventually failed. Any other suggestions?

Wipe cache dalvik data and system reboot, ignore error message and reboot
---------- Post added at 06:54 AM ---------- Previous post was at 06:53 AM ----------
Try through ur computer
---------- Post added at 06:57 AM ---------- Previous post was at 06:54 AM ----------
Try go back to twrp and wipe like the op said

xiong77 said:
Wipe cache dalvik data and system reboot, ignore error message and reboot
---------- Post added at 06:54 AM ---------- Previous post was at 06:53 AM ----------
Try through ur computer
---------- Post added at 06:57 AM ---------- Previous post was at 06:54 AM ----------
Try go back to twrp and wipe like the op said
Click to expand...
Click to collapse
I've done the wipes multiple times. It's mostly the downloads I'm having trouble with. How and where do you get them? The links I found were dead or had a slow speed.

video_dewd said:
I've done the wipes multiple times. It's mostly the downloads I'm having trouble with. How and where do you get them? The links I found were dead or had a slow speed.
Click to expand...
Click to collapse
Did you save the recovery backup? If you did then use the axon7root.exe to flash the stock recovery. Then download the stock B20 from ZTE.

tabletalker7 said:
Did you save the recovery backup? If you did then use the axon7root.exe to flash the stock recovery. Then download the stock B20 from ZTE.
Click to expand...
Click to collapse
I've been able to find some recovery images that I found on other threads. The thing is, when I try to flash them on TWRP, I get an error about "/dev/block/sde14" being read-only.

video_dewd said:
I've been able to find some recovery images that I found on other threads. The thing is, when I try to flash them on TWRP, I get an error about "/dev/block/sde14" being read-only.
Click to expand...
Click to collapse
no no no no ..................... put phone in EDL mode. Copy the stock image into the folder with the axon7root.exe file you used to flash TWRP. Make sure the stock file is named recovery.img (or whatever the TWRP file is named in that folder, it has been a long time since I did this). Then use the axon7root.exe program the exact same way you did before. It will flash the stock recovery. Then in stock recovery you can flash the B20 from ZTE

tabletalker7 said:
no no no no ..................... put phone in EDL mode. Copy the stock image into the folder with the axon7root.exe file you used to flash TWRP. Make sure the stock file is named recovery.img (or whatever the TWRP file is named in that folder, it has been a long time since I did this). Then use the axon7root.exe program the exact same way you did before. It will flash the stock recovery. Then in stock recovery you can flash the B20 from ZTE
Click to expand...
Click to collapse
Ok, I will try this.
Update: I got the stock recovery back, but now I'm lost as to how to flash the stock b20 from zte. Thank you for all your help so far though.

video_dewd said:
Ok, I will try this.
Click to expand...
Click to collapse
got stock recovery working?

tabletalker7 said:
got stock recovery working?
Click to expand...
Click to collapse
Yes, I'm in the process of getting the update from sdcard feature working.
Update: Trying to use the update.zip file or unpacking it into the sdcard hasn't worked. Trying to use adb sideload returns "Cannot read 'update.zip'"

video_dewd said:
Yes, I'm in the process of getting the update from sdcard feature working.
Click to expand...
Click to collapse
ok - download it from zte. Put it on your SD card. In recovery select update from SD card. Be warned it will work but it is slow. Also note that while I will not say the bootloader unlock doesn't work on B29, I can say it worked flawlessly on B20. If you want unlocked I recommend doing so on B20.

tabletalker7 said:
ok - download it from zte. Put it on your SD card. In recovery select update from SD card. Be warned it will work but it is slow. Also note that while I will not say the bootloader unlock doesn't work on B29, I can say it worked flawlessly on B20. If you want unlocked I recommend doing so on B20.
Click to expand...
Click to collapse
I have the zip but it says, "Sorry,you can't sdcard upgrade".

video_dewd said:
I have the zip but it says, "Sorry,you can't sdcard upgrade".
Click to expand...
Click to collapse
try using adb sideload
---------- Post added at 07:48 AM ---------- Previous post was at 07:45 AM ----------
also people reportd sucess on the z-communities by placing the B20 on the internal sd card (phone storage)

tabletalker7 said:
try using adb sideload
---------- Post added at 07:48 AM ---------- Previous post was at 07:45 AM ----------
also people reportd sucess on the z-communities by placing the B20 on the internal sd card (phone storage)
Click to expand...
Click to collapse
I tried that. It won't accept the zip file and it's unclear which file to sideload. Would you happen to know? This is what files are in the unpacked zip. https://gyazo.com/c7546c3ed0dcb0972653eaeba42fcb40

video_dewd said:
I tried that. It won't accept the zip file and it's unclear which file to sideload. Would you happen to know? This is what files are in the unpacked zip. https://gyazo.com/c7546c3ed0dcb0972653eaeba42fcb40
Click to expand...
Click to collapse
Maybe - I'd have to download it to find out. If you can't get stock recovery to take it this post http://forum.xda-developers.com/showpost.php?p=69434328&postcount=17 gives you instructions on what lines to remove from the updater-script to make it flash in TWRP (I didn't have a problem making the stock B20 go in stock recovery, but I was unlocked at the time). You could reflash TWRP and try that.
Or just try this in TWRP http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

tabletalker7 said:
Maybe - I'd have to download it to find out. If you can't get stock recovery to take it this post http://forum.xda-developers.com/showpost.php?p=69434328&postcount=17 gives you instructions on what lines to remove from the updater-script to make it flash in TWRP (I didn't have a problem making the stock B20 go in stock recovery, but I was unlocked at the time). You could reflash TWRP and try that.
Or just try this in TWRP http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Click to expand...
Click to collapse
I'm going to try the first option. The second option's link take horrendously long to download.
Update: Trying to flash from TWRP results in error "Could not find 'META-INF/com/google/android/update-binary' which makes no sense since update binary is exactly where it should be.
Further Update: It seems that the problem might have been that when I compressed "update.zip" to fix "updater-script" it changed to file path by adding the title of the folder "update" to the beginning. I think that messed with the path giving the the meta-inf error.

video_dewd said:
I'm going to try the first option. The second option's link take horrendously long to download.
Update: Trying to flash from TWRP results in error "Could not find 'META-INF/com/google/android/update-binary' which makes no sense since update binary is exactly where it should be.
Click to expand...
Click to collapse
OK. How did you do that?
---------- Post added at 10:09 AM ---------- Previous post was at 09:54 AM ----------
Just suck it up and download the 2 b29 files. If it is that slow pick a different mirror

Unresponsive screen

I'm running h918 and never had a weird issue like this with any phone. I flashed Resurrection ROM latest version and Gapps with Magik 14.0 . The ROM won't boot which happens but when I go into twrp my screen is nonresponsive. Won't recognize any touch at all. I can get in fastboot mode also. Is there anything you guys could suggest trying to fix this cluster.Ive never had a ROM not boot then not be able to use twrp to fix. I didn't update to the latest bootloader were u can't roll back yet,if that would matter ..
Sent from my Nexus 6 using Tapatalk

The latest lineage source code is causing major issues with the v20. In order to fix the touch screen issue you need to reflash twrp through fastboot, or rerun dirty santa from step 3. Basically automates the fastboot stuff. Any rom that is using the latest lineage kernel trees for the the v20 is affected by this bug. I read somewhere it compiles with a corrupt ramdisk. Also flashing the werewolf 2.0 kernel fixes the unresponsive screen in twrp.

How can I flash werewolf? I've tried in adb fastboot..Dude this is frustrating as fk..I'm trying not to throw this phone against the wall..Been trying for hours
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
How can I flash werewolf? I've tried in adb fastboot..Dude this is frustrating as fk..I'm trying not to throw this phone against the wall..Been trying for hours
Click to expand...
Click to collapse
You can put the phone in fastboot mode and rerun dirty santa from step 3. Should reflash twrp and boot and get you into a working twrp. If you can't use fastboot ( fastboot flash boot "name of boot".img and fastboot flash recovery "name of recovery".img) - make sure the boot/recovery image is in the same directory as fastboot and ADB then the only thing you can try is grabbing a USB otg mouse and trying to use that once in twrp. Fastboot is super finicky so try renaming twrp and boot to simple names such as recovery.img and boot.img. Like I said rerunning dirty santa step 3 handles this automatically and after you should be able to power off and hardware combo directly into a working twrp. Don't really know what else to suggest.
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
Worst comes to worst you can always use lgup to kdz back to stock to get back up and running again. If you want root again be sure to use a of with an early security patch. Dec 2016 or earlier. H918 have lots of kdz available.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Also it doesn't have to be werewolf. Any working kernel in boot.img form for h918 can be placed in your fastboot directory and flashed. It will fix the broken touch screen as it is related to the kernel.

I don't think my fast boot is working...I've tried for 2 days .to flash twrp and a boot image ..Is it normal when downloading twrp to a windows 10 computer that the file is a disc file?It keeps saying corrupt..Or fastboot says no such file or directory but in adb and fastboot it always recognize my device ..Never had a issue like with this
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
I don't think my fast boot is working...I've tried for 2 days .to flash twrp and a boot image ..Is it normal when downloading twrp to a windows 10 computer that the file is a disc file?It keeps saying corrupt..Or fastboot says no such file or directory but in adb and fastboot it always recognize my device ..Never had a issue like with this
Click to expand...
Click to collapse
Yes windows will read it as a disc image file and will give a warning about not being able to read it that's fine. Fastboot should work regardless of ADB. mine is installed under c :/android/tools. You have to navigate there using cmd in order for fastboot to work. Also make sure you have your working boot.img right there next to fastboot.exe. They should be next to each other. Fastboot cannot flash anything unless the images are in the exact same directory. If your boot/recovery images are in any other folder besides the fastboot folder flashing will fail saying it could not locate it. Dirty Santa step 3 does this for you. If fastboot is borked completely and you know everything you are doing is correct than boot into download mode and run lgup. It will get your phone back to running bone stock. Many people have faced the same issue with the broken touch screen and have gotten their phone back. Check out the rez remix and lineage threads and read a few pages back. Lots of info on there

Yep mine was remix too..I've been reading for a couple days..One more question..Since my computer updated it now gives me power shell and not command prompt when shift and double click to open a window..Is that a issue ..They are similar but different in commands..Mine is in platform tools that's OK right ? I have the boot and the twrp in there too
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Yep mine was remix too..I've been reading for a couple days..One more question..Since my computer updated it now gives me power shell and not command prompt when shift and double click to open a window..Is that a issue ..They are similar but different in commands..Mine is in platform tools that's OK right ? I have the boot and the twrp in there too
Click to expand...
Click to collapse
Power shell should work just fine but if you think it may be causing issues open cmd and use cd c:\pathtofastboot\pathtofastboot. That will get you into the correct directory. Then try fastboot commands as normal. But I haven't heard of powershell causing issues as I've used it myself without problems just never used it to flash stuff.
You'll know if the path isn't correct because command prompt will report back with "unknown command" errors. Platform tools is fine

Got a new ROM flashed and wolf but no fix of touch screen
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Got a new ROM flashed and wolf but no fix of touch screen
Click to expand...
Click to collapse
Have you reflashed the recovery image as well? Reflashing twrp should fix it if you haven't. If that doesn't work I'm out of ideas

toastyp said:
Have you reflashed the recovery image as well? Reflashing twrp should fix it if you haven't. If that doesn't work I'm out of ideas
Click to expand...
Click to collapse
Yeah bro I have flashed several times.Been looking for a twrp flash able version .Ive found away to flash in twrp without a touch screen..I think something could be wrong with my fastboot or on both my computers it keeps saying can't find IMG but it's right there in the folder..Thanks for your help
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Yeah bro I have flashed several times.Been looking for a twrp flash able version .Ive found away to flash in twrp without a touch screen..I think something could be wrong with my fastboot or on both my computers it keeps saying can't find IMG but it's right there in the folder..Thanks for your help
Click to expand...
Click to collapse
That really sucks sorry to hear that man. Really doesn't make sense considering it is due to the lineage kernel. Try contacting the op of the rez remix thread. He had similar problems and was able to fix it. Might be able to help. And if you need the phone back immediately there's always lgup. When you figure it out let us know how you fixed it. Could help a lot of people who flash the latest lineage builds or compile rez remix themselves.
Also the op of the return to v10m stock thread might be able to help. There's a lot of people having issues with fastboot

I GOT IT FIXED BRO....USED ADB SHELL WHILE IN TWRP AND RESTORED A BACKUP OF A STOCK ROM AND BOOOOOM..AFTER DAYS OF STAYING UP AND TRYING ..I NEVER KNEW YOU COULD DO THAT WITH TWRP AND ADB..MAN THANK THE LORD ..
Sent from my LG-H918 using Tapatalk

kenbrownstone said:
I GOT IT FIXED BRO....USED ADB SHELL WHILE IN TWRP AND RESTORED A BACKUP OF A STOCK ROM AND BOOOOOM..AFTER DAYS OF STAYING UP AND TRYING ..I NEVER KNEW YOU COULD DO THAT WITH TWRP AND ADB..MAN THANK THE LORD ..
Click to expand...
Click to collapse
That's awesome! Happy to hear it. Definitely good to know that an ADB restore of a working backup can solve touchscreen issues for people where fastboot is failing. Definitely stay away from lineage sources until someone reports that it's working.

I am for sure...thanks man
Sent from my Nexus 6 using Tapatalk

toastyp said:
The latest lineage source code is causing major issues with the v20. In order to fix the touch screen issue you need to reflash twrp through fastboot, or rerun dirty santa from step 3. Basically automates the fastboot stuff. Any rom that is using the latest lineage kernel trees for the the v20 is affected by this bug. I read somewhere it compiles with a corrupt ramdisk. Also flashing the werewolf 2.0 kernel fixes the unresponsive screen in twrp.
Click to expand...
Click to collapse
THANK YOU!!! I have a 2 day old US996 that I was ready to take a hammer to. Flashed latest Lineage and booted up after a very long time...only to find the touchscreen not responding. I figured a ROM issue so I pulled battery and got back into TWRP but it also would not respond. At this point I figured it was certainly a hardware failure and I was freaking since I've unlocked the bootloader and it's no longer under warranty.
You are a lifesaver my friend. Many many thanks. Reflashing TWRP with fastboot worked a trick. Never seen a ROM completely disable a portion of the hardware. lol

LGtMgG2t said:
THANK YOU!!! I have a 2 day old US996 that I was ready to take a hammer to. Flashed latest Lineage and booted up after a very long time...only to find the touchscreen not responding. I figured a ROM issue so I pulled battery and got back into TWRP but it also would not respond. At this point I figured it was certainly a hardware failure and I was freaking since I've unlocked the bootloader and it's no longer under warranty.
You are a lifesaver my friend. Many many thanks. Reflashing TWRP with fastboot worked a trick. Never seen a ROM completely disable a portion of the hardware. lol
Click to expand...
Click to collapse
Glad to hear it! Some people have been having issues with fastboot itself so nice to hear it worked well for you. A couple of members have figured out the touch screen issue and have uploaded the changes to Gerrit. Hopefully we will see it merged within the next few days. The firmware makefile within the kernel source was not calling the appropriate firmware images breaking the touchscreen in the process.