Database Users

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.

Accidentally installed OTA update, now seeing many problems and can't find a fix

Yesterday I accidentally installed the OTA update. I got stuck in TWRP and flashed a new ROM. Phone booted up fine, but now I have no cellular signal, nothing that uses video or sound works. Camera doesn't work, flashlight doesn't work.
I tried several different ROMS and nothing changes. Even the system sounds, ringtones and so on do not work. Anyone have any idea what I can do? Thanks

boot into fastboot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase misc
fastboot erase fota
fastboot erase boot
then pull battery and reboot into twrp by holding power and vol down, when lg logo appears then click the power button and re-hold it down to get into twrp.
once in twrp, check and see if system is mounted, if it wont let you mount, go to wipe and wipe everything (not ur sd of course)
System, cache, dalvik, data, internal, everything... the fastboot should have already done this but let twrp do it too..
once done, use the format option and format data also, some of these may error thats okay, just keep going..
once done reflash the full rom that matches your device.. let it flash and reboot and do its thing. this should fix the issues...
once it boots you may need to let it activate, or re-activate.
Only other suggestion would be if you have a twrp backup and you backed up your efs, its time to restore it also and see if the NV files have been damaged.

I've tried installing several different roms available on xda but that didn't resolve the issue. My phone remains in a boot loop state. Is there a way I can return to stock without compromising my ability to use the current root exploits?

Might help to know what you've got currently, are you able to get to recovery at all, etc?

I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873

My Solution
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.

lanyueng said:
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
Click to expand...
Click to collapse
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.

jluca98 said:
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
Click to expand...
Click to collapse
This isn't working for me. Keeps rebooting to TWRP.
I get FAILED (remote: unknown command) with every adb command
Any ideas?

Drkphnxs2k said:
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
Click to expand...
Click to collapse
Don't use Easy Recowvery. Do it manually from the original thread. You can also google it for some sites that have cleaned the instructions up for easier reading.
I just did a H918 10d like this.

Can't get past TWRP

Phone was working fine yesterday. Went to sleep and woke up to the phone booted into recovery. Now I can't get it to reboot past recovery. Anyone know why this happened or how to fix it?
Thanks in advance.

Check and see if system is mounted. Also are you sure that it didn't attempt an update last night?

The EXACT same thing happened to me this morning! Unfortunately I had to get to class before I could figure out how to fix it. When I get back home tonight I will try to get my phone to boot like normal and will tell you how I did it.

my_handle said:
Check and see if system is mounted. Also are you sure that it didn't attempt an update last night?
Click to expand...
Click to collapse
I have no way of knowing if it attempted an update last night. I was asleep. I tried restoring a nandroid backup from 8 days ago and it still won't boot past TWRP.
Help please! I'm at the Cleveland Clinic with my wife and just found out that my grandmother died today and have to drive back to Michigan tonight. I need a phone and Waze!

animator776 said:
The EXACT same thing happened to me this morning! Unfortunately I had to get to class before I could figure out how to fix it. When I get back home tonight I will try to get my phone to boot like normal and will tell you how I did it.
Click to expand...
Click to collapse
I'm sorry to hear, but glad I'm not alone in this. Hopefully we can figure something out.

Sorry about your lose. But click mount and see if system is checked. That's what happened to me before. Making sure system was checked let me boot back up.
If that doesn't work plug your phone into your comp if possible and check to make sure you still have everything on your phone. Another time I had accidently wiped everything and only way to get back up was using the kdz
pieces of cake said:
I have no way of knowing if it attempted an update last night. I was asleep. I tried restoring a nandroid backup from 8 days ago and it still won't boot past TWRP.
Help please! I'm at the Cleveland Clinic with my wife and just found out that my grandmother died today and have to drive back to Michigan tonight. I need a phone and Waze!
Click to expand...
Click to collapse

my_handle said:
Sorry about your lose. But click mount and see if system is checked. That's what happened to me before. Making sure system was checked let me boot back up.
If that doesn't work plug your phone into your comp if possible and check to make sure you still have everything on your phone. Another time I had accidently wiped everything and only way to get back up was using the kdz
Click to expand...
Click to collapse
I checked system under mount, rebooted and still won't go past TWRP.

Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.

midmadn said:
Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.
Click to expand...
Click to collapse
Dude, I love you. I'm back! Just in time for my 3 hour drive home!

if this dosnt work
use twrp file manager to go find the fota and mis folders,
or boot into fastboot and send these comands
fastboot erase misc
fastboot erase fota
data/mis
data/fota
something like this is its path.
data/etc/misc
data/etc/fota
this 2 spots have the update commands that cause twrp loop.
i have a help post in my rom with full walkthrough.

Bootloop into TWRP recovery
Thank you so much, I too was having a panic attack after I flashed a custom rom and it some how altered this and put me in a boot loop into TWRP. I had a couple of questions in regards to ROMS that have native tethering enabled. 1. Is there one that allows Native tethering enabled for sprint? and 2. Is there one that you can update the PRL and profile settings and also one that does use an APN that has DNS issues and a proxy that blocks certain sites? currently I downloaded the ROM that is on the Dirty Santa site its called LS997-deODEXd-signed and it has a hidden proxy that blocks DNS from certain sites also you cannot update.

pwoolston2 said:
Thank you so much, I too was having a panic attack after I flashed a custom rom and it some how altered this and put me in a boot loop into TWRP. I had a couple of questions in regards to ROMS that have native tethering enabled. 1. Is there one that allows Native tethering enabled for sprint? and 2. Is there one that you can update the PRL and profile settings and also one that does use an APN that has DNS issues and a proxy that blocks certain sites? currently I downloaded the ROM that is on the Dirty Santa site its called LS997-deODEXd-signed and it has a hidden proxy that blocks DNS from certain sites also you cannot update.
Click to expand...
Click to collapse
Download one of my 11 roms ive currently put out.
they all work 100% as far as dns stuff
for tether you need to add the "dun" to your apns. There isnt currently a built in mod.
as well as using shortcut master to add the "dun" to your apns also gets you to where you can change them
prl and profile updates work also as well as fm radio, wifi calling, fingerprint, comfort view etc.

midmadn said:
Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.
Click to expand...
Click to collapse
I had to do this again today. This is not good. How can we stop this? I rely on my phone as an alarm clock and this could really screw me if it happens again at night.

Have you frozen or disabled the apps that look for updates?
Supposedly this is what causes it. The bootloader looks for update files in the folders where updates are downloaded and if it finds a file there it reboots recovery.
You have to remove those files, ( I think it automatically deletes them if you go through the factory reset process with the volume down, power button sequence).
And you have to freeze or disable the update apps.

These are the apps I froze. The 3 near the bottom that are blue.

i did this https://forum.xda-developers.com/v20/help/lg-v20-access-to-fastboot-t3557328

Most bootloops are caused by an update file residing on the internal memory. It is not necessary to do all of the stuff in that post. You just need to do the volume down / power button trick to go through the 2 factory reset screens.
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.

N910TUVS2EPK2 - got it rooted!

Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.

Thanks man, had the same issue. I figured it might be something to do with booting int OS. Sure enough with 6.0.1 EPK2 rom you MUST load into boot recovery right after flashing TWRP as you stated.
Something went wrong with my OTA update of EPK2 and it started to bootloop( 2 vibrates upon restart and then random amount of bootloops, and then random, soon-coming freeze upon loading in OS and continuing boot-looping) sometime after the update. I erased most of the old stuff via TWRP reinstalled EPK2 bootloader separately and then flashed EPK2 rom and it seems to be OK so far (knock on wood). We'll see hopefully it's not hardware issues like many people were reporting with bootlooping.

Can't you just uncheck the Odin option to reboot instead of the frantic battery pull?
Just wondering, as I'm going to do this later- thanks!
Steven.RN
Followup: Yep. Slip over to the options tab in Odin and uncheck "auto reboot". After Odin flashes TWRP, (the bar is all the way across the download screen, and the Odin Log says "succcess") go ahead, disconnect the phone from USB. Do your battery pull, replace battery. Close up the phone, then hit Volume up, home, and power at the same time- Bang! TWRP screen.
Further note: first time I did this flash, it didn't work, it just stopped in it's tracks. Then I realized I had to enable "developer mode" by clicking on the build number in the "About phone" sections in settings 5 times, going into Developer mode (the new option will present itself in the menu on settings), then: enable OEM unlock and USB debugging. Odin will flash TWRP just fine after that. (Duh on me!)

planetjeff said:
Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.
Click to expand...
Click to collapse
thanks for the info, might give it a shot tonight. you have a link to the software update so i can load it with odin?

Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?

Charlie Rock said:
Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?
Click to expand...
Click to collapse
sammobile.com
Sent from my SM-N910T using Tapatalk

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 ?