Database Users

Can't boot, tried flashtool, not going well, help

So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?

I think it's getting a model information check fail in lg flashtool, ugh this sucks.

bova80 said:
So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?
Click to expand...
Click to collapse
LOL, i just went through the same thing. I'll be posting a fix tonight I worked out with Scott.
"There is a "back door" method. This is why they updated TWRP by the way...
Download this: https://dl.dropboxusercontent.com/u/...with cmd.zip
Extract it to desktop. open the command.bat file.
Type "adb reboot recovery" then press enter. You need to keep doing this during the factory reset.
This assumes you have drivers installed. If you have no drivers installed for recovery mode then just select generic Google Nexus ADB drivers.
You kinda have to hammer the reboot recovery command. Its all timing... To hammer it... press the up arrow in the dos prompt and that will repeat the line. then press enter.
Keep doing it until you see it reboot to twrp and you should be able to sideload or load from storage.
It may take 10 or 15 minutes to get the exact right timing so dont give up.
And of course, this is all dependent upon you having the drivers already installed."
- Scott
For timing, you'll need to wait right when TWRP starts writing the script and start hammering it out. Timing is everything so when you see the TWRP screen starting hitting the up cursor and enter. It should load recovery. Don't bother using the tool, it won't work as it thinks your device is a D802 and won't be compatible with the dll. This will get you back to normal and from here you can just wipe and reinstall the rom again fresh with out losing media/data on the your drive.

I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated

MkV05 said:
I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated
Click to expand...
Click to collapse
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.

SamsungGalaxyStig said:
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.
Click to expand...
Click to collapse
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?

ccmbr002 said:
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?
Click to expand...
Click to collapse
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip

so I got it right when it said teamwin to reboot but everytime it reboot it tried to run the script and would never actually go into twrp. att is sending me a new phone but I'm worried when I send this one back they'll get me for being rooted.

SamsungGalaxyStig said:
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip
Click to expand...
Click to collapse
I just messaged him to double check - I don't have access to my phone for a few days (out of town) but if he hasn't responded by the time I get home I'll just go ahead and try it and post here if it works or not. Thanks again for sharing this file!

Got the file... and MANY THANKS!!! It allowed me to un-softbrick my G2 finally

this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
updating partition details
Running boot script....
Finished running bootscript,
Processing AOSP recovery commands....
----Wiping Data Partition----
Wiping data without data/media...
Done.
Removing all files under '/cache'
---- data partition wipe complete!
Done processing script file
Click to expand...
Click to collapse

bova80 said:
this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
Click to expand...
Click to collapse
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?

SamsungGalaxyStig said:
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?
Click to expand...
Click to collapse
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?

bova80 said:
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?
Click to expand...
Click to collapse
Are you constantly doing the adb recovery reboot? or once or twice?

SamsungGalaxyStig said:
Are you constantly doing the adb recovery reboot? or once or twice?
Click to expand...
Click to collapse
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?

bova80 said:
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?
Click to expand...
Click to collapse
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.

SamsungGalaxyStig said:
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.
Click to expand...
Click to collapse
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?

bova80 said:
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?
Click to expand...
Click to collapse
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?

SamsungGalaxyStig said:
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?
Click to expand...
Click to collapse
on a pc. when i go under device manager I think it says something like lg modem, I'll know for sure when I get home.

omg it finally worked! thanks, I eventually just gave up with the command prompt and it went in.

[SOLVED] Bootloop. No recovery. Bootloader locked.

================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit

The same just happened to me, wtf

Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.

GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too

Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.

Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop

Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...

GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters

Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?

I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.

Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.

p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?

And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.

p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT

Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.

I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!

Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.

hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin

gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?

Hi GusGold No its 9008

Can only boot into locked bootloader after installing twrp, stuck in a boot loop.

Hello guys,
I'm in a very frustrating situation. After hours of research i finally post this because i couldn't find anything that helped yet.
So here's my problem:
I got my OnePlus2 today, wanted to root it straight away, and so i did. After installing TWRP and rooting my phone, i f'ed up (as i found out until now):
I went back into the developer options, disabled USB-Debugging as well as the OEM-lock, which allowed me to unlock the bootloader , because i wanted to disable developer options again (i like it clean). Bad idea, as it turns out. My bootloader is now locked again and could not be unlocked as of now, after hours of trying to figure out a way.
Another problem that came with it is the bootloop when i try to (re)start the device. The phone flashes the OnePlus-logo for half a second, vibrates, and starts again, over and over. The only way to get the phone out of the loop is by pressing POWER + VOLUME UP and booting into fastboot. Then i can do all the fastboot-commands on my PC, but i can't get into the recovery or flash anything because the bootloader is locked. Trying to 'fastboot oem unlock' only results in the device restarting and getting stuck in the bootloop i mentioned before again.
I managed to get the phone to work a few times by executing 'fastboot continue', which either starts to show the charging battery symbol or booting up like normal (about a 50% chance I'd say).
ADB commands can then be executed, but I'd need a way to flash a ROM without going into the bootloader or recovery, which seems to be impossible.
Is there any way you could help? Is there an ADB command to reset the phone to the state it was delivered, without me having any sort of backup? Or can the bootloader be unlocked via ADB?
Thanks a million in advance! :fingers-crossed:

Rattig said:
Hello guys,
I'm in a very frustrating situation. After hours of research i finally post this because i couldn't find anything that helped yet.
So here's my problem:
I got my OnePlus2 today, wanted to root it straight away, and so i did. After installing TWRP and rooting my phone, i f'ed up (as i found out until now):
I went back into the developer options, disabled USB-Debugging as well as the OEM-lock, which allowed me to unlock the bootloader , because i wanted to disable developer options again (i like it clean). Bad idea, as it turns out. My bootloader is now locked again and could not be unlocked as of now, after hours of trying to figure out a way.
Another problem that came with it is the bootloop when i try to (re)start the device. The phone flashes the OnePlus-logo for half a second, vibrates, and starts again, over and over. The only way to get the phone out of the loop is by pressing POWER + VOLUME UP and booting into fastboot. Then i can do all the fastboot-commands on my PC, but i can't get into the recovery or flash anything because the bootloader is locked. Trying to 'fastboot oem unlock' only results in the device restarting and getting stuck in the bootloop i mentioned before again.
I managed to get the phone to work a few times by executing 'fastboot continue', which either starts to show the charging battery symbol or booting up like normal (about a 50% chance I'd say).
ADB commands can then be executed, but I'd need a way to flash a ROM without going into the bootloader or recovery, which seems to be impossible.
Is there any way you could help? Is there an ADB command to reset the phone to the state it was delivered, without me having any sort of backup? Or can the bootloader be unlocked via ADB?
Thanks a million in advance! :fingers-crossed:
Click to expand...
Click to collapse
You might want to contact Naman Bhalla. I know he's helping out people fix bricked phones on xda as well as opo forums. I've messaged him as well. Hope he's got time today.
Till he replies, try to make sure that your battery stay charged, somehow.

Hetalk said:
You might want to contact Naman Bhalla. I know he's helping out people fix bricked phones on xda as well as opo forums. I've messaged him as well. Hope he's got time today.
Till he replies, try to make sure that your battery stay charged, somehow.
Click to expand...
Click to collapse
Thank you so very much! I will try to contact him.
Also battery should be no problem as I can boot the phone via fastboot. Either way, I'll have an eye on it!

Rattig said:
Thank you so very much! I will try to contact him.
Also battery should be no problem as I can boot the phone via fastboot. Either way, I'll have an eye on it!
Click to expand...
Click to collapse
I think he did message you. Check your private messages.

Hetalk said:
I think he did message you. Check your private messages.
Click to expand...
Click to collapse
Yes he did. Thanks a lot!

Rattig said:
Yes he did. Thanks a lot!
Click to expand...
Click to collapse
I'm glad your issue got resolved. :good:

If your issue is resolved then please post the solution for others it might help someone

The solution was simple i followed the guide below and it bought my phone back from the dead.
https://www.youtube.com/watch?v=R4SVSovw4Jo

sandeeppathak007 said:
If your issue is resolved then please post the solution for others it might help someone
Click to expand...
Click to collapse
I'm really sorry, I meant to post the solution but obviously I forgot...
So here's how I (with the help of aforementioned Naman Bhalla) fixed my OP2:
https:// forums.oneplus. net/threads/mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ (just remove the spaces i put in because I'm not allowed to post links just yet)
It's as simple as to follow the steps in this Guide. Take some time, read through it and everything should work out fine.
I can't really give more tips as I was lucky enough to be helped by the OP of the guide linked above. If nothing works for you, just try to PM him, he's a very nice and friendly guy!

Hi guys my T-mobile LG V20 is in a bootloop help...

I got the new T-mobile LG V20 I went thru the the whole proccess step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help

jessiemougeot said:
I got the new T-mobile LG V20 I went thru the the whole proccess step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
Click to expand...
Click to collapse
same problem here and cant find solution ...

I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should

Flash the latest su and your fine.

ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
did that but my adb says no devices or emulators?

jo4mvp24 said:
did that but my adb says no devices or emulators?
Click to expand...
Click to collapse
Make sure your on charging mode and you have adb debug enabled

send the adb reboot recovery command as soon as the twrp connects to the computer. as soon as you hear it connect to the computer it should work if your drivers are working.

charlieb620 said:
Make sure your on charging mode and you have adb debug enabled
Click to expand...
Click to collapse
how do i do that when phone stuck on encryption unsuccessful screen?

exactly my issue
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
Ya that is exactly what happend give me a few minutes ill try it out and let you know....THANKS...THANKS....THANKS...It worked, i got it on my first try. Your right ...you have to be quick. thank u so much you saved me along night of downloads! :victory:

This method WORKS!!!! Same situation happened to me. THANK YOU 500x!! you saved my brick!

ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
This works 100% thank you so much. Just have patience as it has to be at the right time....WORKS WORKS WORKS!!!!!

Help
Can someone explain the commands and how to do this please thanks in advance

I did the data reset and im still in the bootloop. Worst thing is now i cant seem to get into recovery

epr2175 said:
I did the data reset and im still in the bootloop. Worst thing is now i cant seem to get into recovery
Click to expand...
Click to collapse
What screen are you stuck in? Do you have adb up and running?

Same as before Encryption unsuccessful. I was able to do the trick, got into two and wiped data. Then rebooted to system and it went right back to that screen. I've tried 100 times or so to get back into twrp with no luck. I hear the computer recognize the device when it goes into twrp for 2 seconds after you click reset. Not sure if that means add is up and running or not.

jessiemougeot said:
Ya that is exactly what happend give me a few minutes ill try it out and let you know....THANKS...THANKS....THANKS...It worked, i got it on my first try. Your right ...you have to be quick. thank u so much you saved me along night of downloads! :victory:
Click to expand...
Click to collapse
Well it booted then got stuck on the lg boot screen again. Adb does not recognize my device, can only boot into Fastboot. Fastboot does see my device, tried lgup, lg bridge, and lg update none see my device, tried relocking bootloader after oem lock bootloader rebooted said my device was corrupted and shut itself off went back into Fastboot unlocked bootloader again and back to the same lg screen help?

This did not work for me, my phone reboots back into TWRP whenever I install a system image it still gives me the encryption message.
---------- Post added at 02:06 PM ---------- Previous post was at 01:11 PM ----------
crazyc78 said:
This did not work for me, my phone reboots back into TWRP whenever I install a system image it still gives me the encryption message.
Click to expand...
Click to collapse
Now I don't even have the encryption screen it just reboots back to TWRP very frustrating!!

fixed!
jessiemougeot said:
I got the new T-mobile LG V20 I went thru the the whole process step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
Click to expand...
Click to collapse
Had the same problem and could not for the life of me do the adb thing. Someone here stated something that I thought I'd try: Press volume down while plugging in the phone to get into fastboot. In a command window issue "fastboot oem lock" (this will relock the boot) > Let the phone reset and you'll see the "Phone corrupt message" > Plug the phone in again to do a fastboot and issue "fastboot oem unlock" > Take the battery out let the phone boot and BAM-E WHAM success!
btw. I followed the steps here to do the whole root thing with Android . how (google "how to root the v20")
I think the "data" wipe did this and according to this site it's not a necessary step so skip it.

This option works!
SyHusky said:
Had the same problem and could not for the life of me do the adb thing. Someone here stated something that I thought I'd try: Press volume down while plugging in the phone to get into fastboot. In a command window issue "fastboot oem lock" (this will relock the boot) > Let the phone reset and you'll see the "Phone corrupt message" > Plug the phone in again to do a fastboot and issue "fastboot oem unlock" > Take the battery out let the phone boot and BAM-E WHAM success!
btw. I followed the steps here to do the whole root thing with Android . how (google "how to root the v20")
I think the "data" wipe did this and according to this site it's not a necessary step so skip it.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I go my T-mobile LG V20 H918 on 11/23/16 and sure enough, I followed the same thread as listed above where it added the step of "data wipe" crap. I was caught in a bootloop, where phone kept bootlooping back to the "reset to factory." The other method of entering the adb command at the right time was more frustrating than anything. (I never got it to work). I spent all day yesterday trying to get this phone working. I re-read (x30) the above thread and on the first attempt it worked. I did not get the "Phone Corrupt Message," but I went ahead and entered the "fastboot oem unlock" and the F#$king phone finally reboot to the setup initial screen. It wiped everything, but having a phone working rather than a nice $800 paperweight, I wanted to kiss SkyHusky for sharing this simple method. YOU ARE AWESOME!!!!
By the way, since I am a glutton for punishment, I followed the steps to root again. After flashing the SuperUser, I rebooted to System. I was at the initial setup screen. My phone is rooted, has TWRP, and SuperUser! As soon as I got the phone working, I went back to TWRP and made a BACKUP!!!!
It is amazing that every time I f-up a phone, I can always come to XDA and get a solution. THANKS GUYS!

jay_h_jacob said:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I go my T-mobile LG V20 H918 on 11/23/16 and sure enough, I followed the same thread as listed above where it added the step of "data wipe" crap. I was caught in a bootloop, where phone kept bootlooping back to the "reset to factory." The other method of entering the adb command at the right time was more frustrating than anything. (I never got it to work). I spent all day yesterday trying to get this phone working. I re-read (x30) the above thread and on the first attempt it worked. I did not get the "Phone Corrupt Message," but I went ahead and entered the "fastboot oem unlock" and the F#$king phone finally reboot to the setup initial screen. It wiped everything, but having a phone working rather than a nice $800 paperweight, I wanted to kiss SkyHusky for sharing this simple method. YOU ARE AWESOME!!!!
By the way, since I am a glutton for punishment, I followed the steps to root again. After flashing the SuperUser, I rebooted to System. I was at the initial setup screen. My phone is rooted, has TWRP, and SuperUser! As soon as I got the phone working, I went back to TWRP and made a BACKUP!!!!
It is amazing that every time I f-up a phone, I can always come to XDA and get a solution. THANKS GUYS!
Click to expand...
Click to collapse
No problem!! Also I forgot to add I only rooted afterward and didn't try to install a ROM or anything. I would think you risk danger with some ROMs without that decryption thing turned off. So maybe in the short future there will be better fixes.

DirtySanta Root Attempt on Verizon LGV20 - Stuck After Step 3 Sitting on Fastboot

Hi, I don't have enough posts to ask this in the actual DirtySanta thread.
I meticulously followed the steps in the DirtySanta thread making sure I had all the correct software, all the pre-requisites, all files in my ADB folder (except SuperSU zip, which is on the SD card on the phone). Suffice it to say that I did all the steps exactly as written in the guide. I was prompted when to run the next batch files each time, etc. Entered the proper commands in the terminal utility, and so on. Everything as written.
After clicking on step3.bat, the phone immediately rebooted to a Fastboot screen. In the meantime, the batch files disappeared off my desktop.
So, for the past 15 minutes or so the phone has been sitting on Fastboot and vibrating away.
Here's what I see in the small Fastboot screen:
Fastboot Mode (in red)
stuff like Product_name, Variant, HW_Version, etc. up until it says LOCK_STATE.
Ok, after all of that basic stuff, it says:
[1090]
[1140] Fastboot mode started
[1670] fastboot: processing commands
[17600] usb_read() transaction failed; txn_status= -1
[17650] usb_read: DONE: ERROR len=64
[1700] fastboot: oops!
[17750] fastboot: processing commands
And that's where it sits, doing seemingly nothing and vibrating away.
Can anyone assist?

Try a different usb port. then rerun step 3.

me2151 said:
Try a different usb port. then rerun step 3.
Click to expand...
Click to collapse
Will do...was just thinking of doing that since it said "usb read error". Will report back.

Heyitsrick said:
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Click to expand...
Click to collapse
First off, a big thanks for helping me.
Update: OK, changing the USB port worked I re-ran Step3.bat. I have made it through getting to TWRP, and have done these steps:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
So, with that all complete, it's rebooted to a Verizon screen (horizontal progress dots) and a low buzzing.
I did try what you mentioned in the guide to get over the wait time by pulling the battery, reinserting with vol down key pressed and re-attaching the USB to flash boot2.img via fastboot, but it didn't get back to fastboot after the battery/voldown/usb. It went back to the same Verizon screen after the obligatory "Corrupt" screen came on.
Can I assume that I can wait this out for 20 minutes, or did I miss something in how to interrupt this waiting period for first setup? I do want to (and know I have to) flash boot2.img.
EDIT: wasn't holding vol key down long enough to get into fastboot. Doh. Just flashed boot2.img and rebooted.
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.

Heyitsrick said:
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Click to expand...
Click to collapse
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24

NegativeX said:
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
Click to expand...
Click to collapse
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
The first time I tried this, it booted up fine, but it went right back to the Logo screen. Doh! I figured perhaps I wasn't waiting long enough with the Volume Down button so I tried it again. What happened the first time when it rebooted to the Logo screen is I released the Volume Down button the moment the phone started to turn on (you feel the vibration). That's when it booted back to the Logo. This second time, I removed the battery again while it was on that never-ending Logo screen to power it off and disconnected the USB cable again. I put the battery back in, then with the Volume Down button pressed down, I reconnected the USB cable. The difference this time is that I did not release the Volume Down button this time UNTIL I saw it was in the Fastboot screen and not the Verizon Logo.
So, at this point the phone was on the Fastboot screen and I saw it was it was ready to go, so I initiated the ADB command to flash boot2.img. It went through its paces and once it got back to the ADB command prompt, I did an ADB Fastboot Reboot command. It rebooted, first with the obligatory corrupt warning, then the Verizon Logo and progress dots, but then after a short while I got the "Hello" screen in red and I knew it was actually going to finish. Whew! Relief! At that point I was eventually at the phone's setup screen for a new user, and I finished setting up the phone, reinstalling apps, etc.
One caveat in this: I don't know why, but even though I had gone through all the steps in "4" section of the instructions, when I checked Root, I wasn't rooted! Huh?
In other words, I had already gone through this part:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
Click to expand...
Click to collapse
After setting up the phone and reinstalling my apps, I opened up the SuperSU app, and it said there was no executable installed. In other words, it didn't recognize that I had flashed it in step 4.1. Perhaps flashing boot2.img overwrote that? Not sure, but at this point, I set about to figure out how to boot into TWRP Recovery on the phone (not fastboot) to flash it from there (again).
It took me a while to find the instructions on how to boot into TWRP, lol, and it's a little unnerving that before it boots to TWRPyou are warned that all your data is going to be overwritten before you can boot to it, but it did get me back into TWRP. Once in TWRP, I re-flashed Supersu-blahblah.zip and rebooted via the system reboot. (did not wipe any caches again, though).
After reboot, I checked root again, and this time after a bit SuperSu brought up the permissions screen for the Root app that I had to allow, and it brought back a successful Root message.
I then set about to do what I really wanted to do with root - bypass the Verizon entitlement check for hotspot usage, and got that working fine.
All in all, I have to say this was the diciest rooting I've ever had to go through. I guess that's because of Nougat and that there can't be (at least not yet) a "one-click" root. But man, was I worried when I was at the point where I first posted in this thread. I bought this phone as a "new-resale" (never used) phone from Swappa.com for $450, so if I bricked it, I was out of luck. But it seems to be ok now.

Heyitsrick said:
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
​
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
Click to expand...
Click to collapse
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha

NegativeX said:
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
Click to expand...
Click to collapse
Late response - sorry.
There must be something we each did differently, as we both have the same phones, same carrier, same software revision (13a). I was able to get to TWRP via the button method on the phone. Didn't use ADB for that. I was presented with an ominous white screen about all files will be wiped/deleted, but when accepting that (and hoping for the best, lol), it just went to TWRP. So, again...something or some step(s) must be done differently to get to that point on your end from what I did.
I'm guessing you're through with doing the flashing on this thing, so this is all moot now.

Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please

kratos380 said:
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
Click to expand...
Click to collapse
Called a twrp loop. Easy fix. Been posted a lot. Look around for it

me2151 said:
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
Click to expand...
Click to collapse
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir

kratos380 said:
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
Click to expand...
Click to collapse
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now

me2151 said:
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
Click to expand...
Click to collapse
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated

kratos380 said:
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3

Sorry for the constant posts but i followed the steps on that thread, deleted the misc/fota files and it stopped it going to twrp and booted to the lg logo with the black screen, i waited there for about 2-3 hours to no avail rebooted into bootloader tried the fastboot img 2 and the same thing happened it was just stuck at the lg logo now when it boots to the fastboot screen however adb doesnt recognize the device anymore but fastboot does. Is it time to kdz and start over ?