Database Users

[Q] Stock Nexus 4 bad install of 4.3 OTA

Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!

Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.

gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall

Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly

Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot

Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:

Didn't work Will try other method

Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!

Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:

Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.

I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .

oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1

Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...

FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.

Phone Recovery Bricked?

Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
https://www.youtube.com/watch?v=e9sjILIiFFU

xDaDeevellopar said:
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
Click to expand...
Click to collapse
ok what is the problem? if it is TWRP asking for that password I only got away from that by unlocking the phone

tabletalker7 said:
ok what is the problem? if it is TWRP asking for that password I only got away from that by unlocking the phone
Click to expand...
Click to collapse
Well, I can't boot into recovery as it would boot into the ZTE logo for 1 second and turn off but when I boot it up to system or android, it works. Added a YouTube link in the post.

xDaDeevellopar said:
Well, I can't boot into recovery as it would boot into the ZTE logo for 1 second and turn off but when I boot it up to system or android, it works. Added a YouTube link in the post.
Click to expand...
Click to collapse
Mine did that when I tried to re-lock my bootloader (don't ask). I used the goodies in here http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 to install TWRP and then used TWRP to do a factory reset.

tabletalker7 said:
Mine did that when I tried to re-lock my bootloader (don't ask). I used the goodies in here http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 to install TWRP and then used TWRP to do a factory reset.
Click to expand...
Click to collapse
Can you tell me the exact steps? I'm not too good at doing stuff like this though I do have a basic understanding.
nevermind, I fixed it lol but I still have the password issue in TWRP help?

xDaDeevellopar said:
Can you tell me the exact steps? I'm not too good at doing stuff like this though I do have a basic understanding.
nevermind, I fixed it lol but I still have the password issue in TWRP help?
Click to expand...
Click to collapse
I noticed that password on TWRP - it is caused by the factory encryption. I wanted to unlock my bootloader and when I did the unlock, it did away with that problem. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 just go slow, the directions are pretty straight forward (if you want to unlock)

tabletalker7 said:
I noticed that password on TWRP - it is caused by the factory encryption. I wanted to unlock my bootloader and when I did the unlock, it did away with that problem. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 just go slow, the directions are pretty straight forward (if you want to unlock)
Click to expand...
Click to collapse
What does it mean by "navigate to your adb location."?

Damn, just encounter another problem... wifi...
It's ain't turning on and when I go to the Wifi settings in Settings, all it show is it is turned off with no networks and doesn't say anything beside the 3 dots, Wifi, back button, and the off button for wifi. help?

xDaDeevellopar said:
Damn, just encounter another problem... wifi...
It's ain't turning on and when I go to the Wifi settings in Settings, all it show is it is turned off with no networks and doesn't say anything beside the 3 dots, Wifi, back button, and the off button for wifi. help?
Click to expand...
Click to collapse
Do yourself a huge favor - there is a giant box in the top left of the screen as you read this. It is called a search bar. Everything (and I mean EVERY SINGLE THING) you have asked about thus far has been gone over to COMPLETE EXHAUSTION many times over. I am trying to be nice and help you through this whole process but wow, come on already. http://forum.xda-developers.com/axon-7/how-to/please-check-wifi-flashing-bootloops-t3451544 read this post from front to back, then back to front, and then if you still have questions the people over there odds are have your solution

xDaDeevellopar said:
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
https://www.youtube.com/watch?v=e9sjILIiFFU
Click to expand...
Click to collapse
hey, could u please tell me how u managed to boot up ur device again... i've also bricked my a2017g to a point where i can't even boot into edl mode...
i submitted this post - https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990#post70561874

Help! Stuck in TWRP recovery

Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks

alane708 said:
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
Click to expand...
Click to collapse
I haven't run into this on my V20, but a couple times on my V10 when i'd softbricked my device and couldn't seem to revive it (even with ToT or KDZ files on LGUP) i was able to recover with LG bridge. Basically you go to the third tab titled "software update" but instead of selecting software update, select the "update error recovery" link at the bottom right. It takes awhile but i think it downloads and restores files (or maybe partitions) that other recovery methods don't. Give it a try and let us know if it worked.

jaysonic88 said:
I haven't run into this on my V20, but a couple times on my V10 when i'd softbricked my device and couldn't seem to revive it (even with ToT or KDZ files on LGUP) i was able to recover with LG bridge. Basically you go to the third tab titled "software update" but instead of selecting software update, select the "update error recovery" link at the bottom right. It takes awhile but i think it downloads and restores files (or maybe partitions) that other recovery methods don't. Give it a try and let us know if it worked.
Click to expand...
Click to collapse
LG Bridge doesn't see my device either =(

alane708 said:
LG Bridge doesn't see my device either =(
Click to expand...
Click to collapse
When you plug it in does it even show up in Device Manager on your computer? If so what does it show up as?

jaysonic88 said:
When you plug it in does it even show up in Device Manager on your computer? If so what does it show up as?
Click to expand...
Click to collapse
Yeah windows sees it as a Portable Device (Attached), I can transfer files to it.

This is very similar to what happened to me, I couldn't get into TWRP though.
I could not find a resolution then and still havent, but I did return my phone for a new one.

slayerh4x said:
This is very similar to what happened to me, I couldn't get into TWRP though.
I could not find a resolution then and still havent, but I did return my phone for a new one.
Click to expand...
Click to collapse
Now I wish it was hard bricked so I could exchange for new one.. I don't think they can do it now since it shows I modified it

alane708 said:
Now I wish it was hard bricked so I could exchange for new one.. I don't think they can do it now since it shows I modified it
Click to expand...
Click to collapse
Mine showed the bootloader message and they still took it back.

slayerh4x said:
Mine showed the bootloader message and they still took it back.
Click to expand...
Click to collapse
I guess I can only wait for a custom ROM now

I'm having the same issue. I've tried every step here. I've flashed multiple ROMS, just hoping one would boot and every one keeps booting right back into TWRP after showing the "your device software cannot be checked for corruption...".
PLEASE HELP! LOL...not sure what else to do. I'm, using the latest version of TWRP and I can get into bootloader.
Tried running the "EasyRecowvery.cmd" and it loads fine. I go into twrp and do the format data and then attempt to run any of the options and I get a "This Device doesn't look like a T-Mobile V20. Proceed anyway? I stop and can't get anything. But when it initially ran it said SUCCESS when locating adb .exe and found the device as well omni_h918.
No matter what it continues to go into TWRP. ANY ANY ANY additional help would be great. I want to return this device to T-Mobile before my 14 days is up. Please help out if you can.

mrbigdrawsz said:
I'm having the same issue. I've tried every step here. I've flashed multiple ROMS, just hoping one would boot and every one keeps booting right back into TWRP after showing the "your device software cannot be checked for corruption...".
PLEASE HELP! LOL...not sure what else to do. I'm, using the latest version of TWRP and I can get into bootloader.
Tried running the "EasyRecowvery.cmd" and it loads fine. I go into twrp and do the format data and then attempt to run any of the options and I get a "This Device doesn't look like a T-Mobile V20. Proceed anyway? I stop and can't get anything. But when it initially ran it said SUCCESS when locating adb .exe and found the device as well omni_h918.
No matter what it continues to go into TWRP. ANY ANY ANY additional help would be great. I want to return this device to T-Mobile before my 14 days is up. Please help out if you can.
Click to expand...
Click to collapse
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.

alane708 said:
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
Click to expand...
Click to collapse
What variant are you using?

imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
You, sir, are a lifesaver. I jumped through all the same hoops as you and was actually starting to panic a little, as the last time I got into a similar string of unsuccessful fixes, I managed to hard brick my Note 2. This worked like a charm on my Verizon variant (the backup part was seemingly unnecessary, as my backup was toast by this point). You definitely have my thanks!

WishRyder said:
You, sir, are a lifesaver. I jumped through all the same hoops as you and was actually starting to panic a little, as the last time I got into a similar string of unsuccessful fixes, I managed to hard brick my Note 2. This worked like a charm on my Verizon variant (the backup part was seemingly unnecessary, as my backup was toast by this point). You definitely have my thanks!
Click to expand...
Click to collapse
Awesome. I was getting a little worried myself when I was stuck in TWRP because I was trying everything I could think of.
I didn't think the backup part was necessary but it's one of those things where you mention everything you did just in case.

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

imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
^ This 100% worked for me after my h918 got stuck in recovery after I got a system update message and accidently selected "reboot & install".
Thank you imucarmen!!!!:good::highfive:

OMG thank you so much. Merry Christmas to me. It worked like a charm. Tytyty

imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
I had the same issue after rooting with Dirty Santa and have been sweating it for the past hour. Stumbled upon your solution and voila! THANK YOU!!

imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
I had some trouble following this at first but it indeed worked.
My v20 was stuck in TWRP (3.0.2-1) after forgetfully hitting OK on the System Update, it was running H91810q and was previously rooted.
I first backed up my phone in TWRP to my SD card and then copied that to my laptop.
In TWRP: Mount > System, I have 3 buttons on the bottom: 'Mount USB Storage', 'Select Storage', and 'Disable MTP'. If I choose 'Mount USB Storage' it goes to the next screen and the only button is Unmount. I cannot get it to shutdown without pulling the battery.
What is missing here is to press Unmount go back to the main TWRP menu, then Reboot > Power Off.
I held Power+VolumeDown, released Power while still holding volume down and I got the white Factory data reset screen. I choose Yes on the next two options to perform the factory reset.
Then it restarted and went back into TWRP. I choose Mount, selected System, pressed Mount USB Storage, then Unmount, Reboot, System.
It booted and took a while since I also flashed the H91810t rom to do an upgrade at the same time from here:
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
Interesting all my apps, and settings were still on the phone.
THANK YOU FOR SAVING MY PHONE, TIME AND $ !!!

0m3ga said:
I had some trouble following this at first but it indeed worked.
In TWRP: Mount > System, I have 3 buttons on the bottom: 'Mount USB Storage', 'Select Storage', and 'Disable MTP'. If I choose 'Mount USB Storage' it goes to the next screen and the only button is Unmount. I cannot get it to shutdown without pulling the battery.
What is missing here is to press Unmount go back to the main TWRP menu, then Reboot > Power Off.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
Interesting all my apps, and settings were still on the phone.
THANK YOU FOR SAVING MY PHONE, TIME AND $ !!!
Click to expand...
Click to collapse
Glad you got it working. As far as the issue with the instructions that could be down to a change in the newer versions of TWRP. I posted this 16 months ago and many new versions of TWRP have come out since. I remember trying to be extremely accurate in my instructions but it is possible I screwed up. Been too long ago and I can't remember now.

Verizon Lg V20 on 13a. Root? Anyway to go back to 11?

As title states. I recently traded for this phone with a friend so I could use viper4android. He had already updated it. Is there anything I can do? Thanks internet.

You can still root on 12a. Download the .Kdz file

my_handle said:
You can still root on 12a. Download the .Kdz file
Click to expand...
Click to collapse
Thanks so much. I will try that again. I was just having issue with lg up.

If it's an issue with lgup not seeing the device try using the uppercut program like I did. https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Tzimmerman15243 said:
Thanks so much. I will try that again. I was just having issue with lg up.
Click to expand...
Click to collapse

my_handle said:
If it's an issue with lgup not seeing the device try using the uppercut program like I did. https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Click to expand...
Click to collapse
That worked great! Thanks so much! However, i am now having issues with Root/Twrp/Bootloader. I can make it through to installing twrp, but the device does not continue boot up past the Verizon logo and loading animation. I let it stay there vibrating for about 30 minutes. Haha

Tzimmerman15243 said:
That worked great! Thanks so much! However, i am now having issues with Root/Twrp/Bootloader. I can make it through to installing twrp, but the device does not continue boot up past the Verizon logo and loading animation. I let it stay there vibrating for about 30 minutes. Haha
Click to expand...
Click to collapse
What exactly have you done?

my_handle said:
What exactly have you done?
Click to expand...
Click to collapse
Lets see..
I have followed the steps here multiple times.
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
If you are familiar, i get through step3 and it requires you to reboot to recovery via adb after start up, but it never starts up. I have tried flashing boot2.img as well to try it, but that gets me too a secure start up password thing I cant get past.
Also, in some directions i t says to enable OEM unlocking in developer settings. I am on Verizon and I do not have that option. Not sure if this is related? Just throwing that out there.

Tzimmerman15243 said:
Lets see..
I have followed the steps here multiple times.
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
If you are familiar, i get through step3 and it requires you to reboot to recovery via adb after start up, but it never starts up. I have tried flashing boot2.img as well to try it, but that gets me too a secure start up password thing I cant get past.
Also, in some directions i t says to enable OEM unlocking in developer settings. I am on Verizon and I do not have that option. Not sure if this is related? Just throwing that out there.
Click to expand...
Click to collapse
If you're stuck where I think
*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
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.

my_handle said:
If you're stuck where I think
*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
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.
Click to expand...
Click to collapse
So i did try the first part. I flashed boot2 and it got me to the Password screen. The second part says to fix that by booting recovery (Twrp) and erasing the things correctly. I cant get into twrp or any sort of recovery. Not by adb (cant boot phone past password screen or verizon screen) or by button holding on power up. (just continues with boot up. I can get into fastboot mode and download mode.

I would try step 2..bat again if you still can't get it try reaching out to @me2151. He's the mad genius that got this and he's pretty good with helping those who are stuck

my_handle said:
I would try step 2..bat again if you still can't get it try reaching out to @me2151. He's the mad genius that got this and he's pretty good with helping those who are stuck
Click to expand...
Click to collapse
Thanks so much! I'm very new to posting. Is there some way I thank you? Like officially? haha

Tzimmerman15243 said:
Lets see..
I have followed the steps here multiple times.
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
If you are familiar, i get through step3 and it requires you to reboot to recovery via adb after start up, but it never starts up. I have tried flashing boot2.img as well to try it, but that gets me too a secure start up password thing I cant get past.
Also, in some directions i t says to enable OEM unlocking in developer settings. I am on Verizon and I do not have that option. Not sure if this is related? Just throwing that out there.
Click to expand...
Click to collapse
If you get to the secure start up password and you cannot get any further, you did not decrypt the phone by formatting the data and such.

nahepler90 said:
If you get to the secure start up password and you cannot get any further, you did not decrypt the phone by formatting the data and such.
Click to expand...
Click to collapse
Is decrypting something I need to do before getting into Twrp? I can't get into recovery.

Also, and this might be nothing, but it seemed to work in my case, but when you're in that rebooting step, make sure you're unplugged. Mine did the same, sat there for 20+ minutes vibrating away. I redid the steps but without it plugged in, and it went through. I've also noticed that on rebooting my phone (different ROM now but still), if I'm plugged into my computer, it'll go into vibrating and act quirky during the reboot, whereas if I'm not plugged into the USB, then it restarts normally.
Totally might be all coincidental, but if you haven't tried it that way, worth a shot.

Tzimmerman15243 said:
Is decrypting something I need to do before getting into Twrp? I can't get into recovery.
Click to expand...
Click to collapse
No the decrypting is done in twrp. Did you successfully install twrp through adb/fastboot?

CharlzO_2000 said:
Also, and this might be nothing, but it seemed to work in my case, but when you're in that rebooting step, make sure you're unplugged. Mine did the same, sat there for 20+ minutes vibrating away. I redid the steps but without it plugged in, and it went through. I've also noticed that on rebooting my phone (different ROM now but still), if I'm plugged into my computer, it'll go into vibrating and act quirky during the reboot, whereas if I'm not plugged into the USB, then it restarts normally.
Totally might be all coincidental, but if you haven't tried it that way, worth a shot.
Click to expand...
Click to collapse
Thanks for the reply! I have tried all sorts of booting with both Boot1 and boot2 img. Both unplugged and plugged in to no avail.

nahepler90 said:
No the decrypting is done in twrp. Did you successfully install twrp through adb/fastboot?
Click to expand...
Click to collapse
I think its installed? Haha. It goes through in fastboot as in fastboot flash recovery twrp.....blah blah.img
But, i have not been able to boot to it in any form.

Solved! I messaged @me2151 himself and he straightened me out. It is always the simplest things. I was trying to boot into recovery the incorrect way by way of not only releasing the power button. Thanks for all the friendly internet help. When I posted here, I had no idea there were so many great people out here behind the text. Thanks again!

Tzimmerman15243 said:
Solved! I messaged @me2151 himself and he straightened me out. It is always the simplest things. I was trying to boot into recovery the incorrect way by way of not only releasing the power button. Thanks for all the friendly internet help. When I posted here, I had no idea there were so many great people out here behind the text. Thanks again!
Click to expand...
Click to collapse
Sorry o didnt get back to you sooner. Glad you got it worked out! @me2151 helped me out getting root on my phone as well. Hes a good help

Glad you got it figured out. And I told you he was good about helping

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 ?