Database Users

[Guide] How to [unlock/flash recovery/rom] on [Evo 4g 2.3.5] [Hboot 2.18.001]

THIS WILL BE USING THE CM 7.1 ROM. IT WORKS WITH OTHER ROMS TOO. JUST FOLLOW SAME PROCEDURE WITH YOUR ROM.
INTRODUCTION AND WARNINGS:
If you have an Evo 4g updated to android 2.3.5 with hboot 2.18.0001 and your wifi always randomly disconnects this guide is for you! The reason the server disconnects is because your router could be incompatible with your HTC phone. If it's just because of some wifi problems and some easy fixes could be made, I would go with that. But for those who have the same problem, not only will you get a cool Cyanogenmod 7.1 look... you'll be able to play PL with wifi.
I'll try to make it as easy to understand as possible... as I'm not good with this stuff either and it took time to understand the guides. Actually I used several guides but I'll kind of combine them.
This guide is for flashing Cyanogenmod 7.1 and what to do before. I am not responsible if there are any problems with your device. Use this guide at your own risk, although there's 99.99999% chance everything will go right if you follow the guide.
PART ONE:
First you'll want to install this file, you need winrar. Just unzip onto desktop so it's easier. You won't actually be using the tool but the root folder. Read the xda first post first though... http://forum.xda-developers.com/show...75&postcount=1
Here's link to download if you've read the post:
http://goo-inside.me/apps/frigid/
Then you'll want to go to www.htcdev.com.
You'll have to register there and use a real email address.
After you register login and click unlock boot loader. Where there's a scroll-down, choose "all other supported models"
Then click get started, the site will guide you through the next steps. Remember, this could void your warranty, I'm pretty sure there is a way to undo this all but remember do this at your own risk.
Tips: If you can't navigate to the right place remember to type "cd [insert name of root folder]"
To get the address, just go to root folder and click copy address at the top. (Right click on where it shows what folder you're in)
After you have successfully unlocked your boot loader you are ready for part 2.
PART TWO:
Enter fast boot on your phone again.
If you closed your command prompt, (which is fine) open it again.
Download this file and save it:
http://files.androidspin.com/downlo...ECOVERY/&file=recovery-RA-supersonic-v2.3.img
The file should appear in downloads.
Move the file into your folder titled root.
If the file is not named recovery rename it to that.
In your command prompt go the the root folder address like you did in part one.
Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)
Once the prompt finishes the command, go back to main boot loader screen. Then use the volume keys to go down to select recovery.
Press the power button to select recovery.
Once the recovery boots on your phone, select use the volume keys to select/highlight USB MS then press the power button.
Take this zip (don't unzip it) and place it into your sd card (just the root, not in any folders).
Zip: http://download.cyanogenmod.com/get/...nic-signed.zip
Press the power button to exit USB MS.
Now go back to main screen of recovery.
Highlight/select the choice flash zip from sd card and press the power button.
Select/highlight the zip you put in your sd card and press the power button to flash.
Press the power button again to confirm.
Once it's done flashing reboot your phone.
If your phone goes into boot loop (keeps rebooting at cyanogen logo thing) then go to your recovery again and select wipe and select wipe all data/factory reset.
OPTIONAL PART 2.5:
If you're looking for Google apps you might want to flash this too, same thing with the Cyanogen ROM, flash it same way.
http://cmw.22aaf3.com/gapps/gapps-gb...828-signed.zip

This working for everyone?

Do people actually read this? Did I post in wrong section?

Guide updated v1.1
Fixed link to Amon Ra Recovery. Last link worked but file was deleted.

Hey man, I have no need for the guide , but much thanks, sincerely. Thanks
sent from AOKP heaven

Ok... I guess...

so does using that htc super tool folder instead of android sdx not wipe everything while unlocking? Or does it still do a factory reset when you unlock?

Trying to figure out what I'm missing here. I have step one all finished. On step two I'm doing the part that says:
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img"
I have the USB Debugging on and Disk Drive on, and the phone in Fast Boot. When I type the "fastboot flash recovery recovery.img" and hit enter it says Waiting for device. Should it say waiting in the command prompt area? Even with that saying waiting, if I use volume down and pick recovery, the screen shows the green circle and downloading logo, then I get the red exclamation screen. What's messing things up? I have the instructions followed exactly up to this point.

BigPimpin said:
Trying to figure out what I'm missing here. I have step one all finished. On step two I'm doing the part that says:
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img"
I have the USB Debugging on and Disk Drive on, and the phone in Fast Boot. When I type the "fastboot flash recovery recovery.img" and hit enter it says Waiting for device. Should it say waiting in the command prompt area? Even with that saying waiting, if I use volume down and pick recovery, the screen shows the green circle and downloading logo, then I get the red exclamation screen. What's messing things up? I have the instructions followed exactly up to this point.
Click to expand...
Click to collapse
have to take it out of disk drive mode i believe and put it in charge only

evo4gnoob said:
have to take it out of disk drive mode i believe and put it in charge only
Click to expand...
Click to collapse
Tried doing that and it goes right to the red exclamation screen instead of the green first. The instruction say to have it in disk drive, so not sure what to do.
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)"

BigPimpin said:
Tried doing that and it goes right to the red exclamation screen instead of the green first. The instruction say to have it in disk drive, so not sure what to do.
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)"
Click to expand...
Click to collapse
when i did it to my phone i had it in charge only

This is my first time trying to do anything to my phone. What exactly does the recovery step I'm doing do? It is saving all my personal data on the phone? I could care less if the phone gets wiped. I have all my contacts in Gmail and re-installing apps take like 5 minutes, so wondering if I could just skip it?
This rooting thing is getting more and more confusing. I'm pretty good computer wise, but reading on this site to try and root this phone, I find topics which are like 100+pages long, and the topic I find link to other topics and it keeps going on and on, and not sure what to do after a while. This topic has gotten me closer to finally doing it then any other. Hopefully I can get it to work fully.

Tried disk drive on and off a couple times and still getting stuck on the red exclamation.

BigPimpin said:
This is my first time trying to do anything to my phone. What exactly does the recovery step I'm doing do? It is saving all my personal data on the phone? I could care less if the phone gets wiped. I have all my contacts in Gmail and re-installing apps take like 5 minutes, so wondering if I could just skip it?
This rooting thing is getting more and more confusing. I'm pretty good computer wise, but reading on this site to try and root this phone, I find topics which are like 100+pages long, and the topic I find link to other topics and it keeps going on and on, and not sure what to do after a while. This topic has gotten me closer to finally doing it then any other. Hopefully I can get it to work fully.
Click to expand...
Click to collapse
Recovery just puts a base place where you can flash roms and stuff.
And if you get a bootloop on CM7.1 yes you will have to wipe all.
As for the recovery flash problem, try putting it on charge only and usb debugging. Then power off phone or just take out battery and reboot into bootloader. Go into fastboot again and try to flash recovery on again. Then try it.

Did you rename the recovery img to recovery? Or if it's not saved as recovery.img rename it to that.

I have it named recovery like it's supposed to be. Still get the green screen then the red exclamation mark.
What should happen when you first go into the fast boot? The reason I ask that is, when it first goes into the fast boot screen it takes a second or so to do it's thing. I see some text going on the screen real quick, and from what I can read of the text I see something about no image and can't read much else, then it is ready to use the volume up and down to make selections. Is that normal, the text part and all about no image? My phone works fine, just can get the steps in this tutorial to work.

BigPimpin said:
I have it named recovery like it's supposed to be. Still get the green screen then the red exclamation mark.
What should happen when you first go into the fast boot? The reason I ask that is, when it first goes into the fast boot screen it takes a second or so to do it's thing. I see some text going on the screen real quick, and from what I can read of the text I see something about no image and can't read much else, then it is ready to use the volume up and down to make selections. Is that normal, the text part and all about no image? My phone works fine, just can get the steps in this tutorial to work.
Click to expand...
Click to collapse
When you go to the bootloader it scans for a PC36IMG.zip file. Normally if you were s-off that's how you would flash a recovery. Since your s-on unlocked the only thing that can be flashed in PC36IMG.zip format is a file signed by HTC like a RUU
Sent from my swiper using XDA App

I got a chance to see some of the names of the missing files it lists when going into boot load. The PC36IMG.zip is one of them that says no image. So guessing that file isn't even there at all. I searched for a PC36IMG.zip file and put it in there and got more then I have seeme before on that screen. I had a blue progress meter on the right side. When it got done it said something about being too old and unsuccessful.
Also, I tried starting all over, even going into the htcdev site again. When I did that all the step worked, but when it's supposed to get to the screen where it tells you it will wipe your phone, that screen never comes up. Now I'm wondering if I can just start all the way over. Can I go into my phone and of I select factory reset, will it make the phone a totally stock phone again and change anything I might have changed? Not that I'm sure I have even changed anything at all to this point.

Removed the batter over and over till I could see the message that comes up very quickly when fast book first starts up. It reads:
Loading...[PC36DIAG.ZIP]
No Image!!!
Loading...[PC36DIAG.NBH]
No Image!!! or Wrong Image!!!
Loading...[PC36IMG.ZIP]
No Image!!!
Loading...[PC36IMG.NBH]
No Image!!! or Wrong Image!!!
Know where I go from here to correct things?

BigPimpin said:
Removed the batter over and over till I could see the message that comes up very quickly when fast book first starts up. It reads:
Loading...[PC36DIAG.ZIP]
No Image!!!
Loading...[PC36DIAG.NBH]
No Image!!! or Wrong Image!!!
Loading...[PC36IMG.ZIP]
No Image!!!
Loading...[PC36IMG.NBH]
No Image!!! or Wrong Image!!!
Know where I go from here to correct things?
Click to expand...
Click to collapse
it shouldnt find a PC36IMG.zip file or the other. Only files in that can be flashed in that format is radios hboots splash screen RUUs recoveries. You shouldnt go around just flashing random things in the bootloader you can end up bricking your phone

HELP! Bricked Nexus 7, cannot boot into boot loader

Hello everyone, I'm new in this forum and have just bricked my Nexus 7 .
I was not very happy with my Nexus 7 with JB version 4.2.1, it lagged and took long time to load apps etc. I used the Nexus 7 toolkit to unlock my bootloader, flash recovery and then tried a few custom roms. I eventually flash the official 4.1.2 firmware from google but the constant notification for firmware update annoyed me and I decided to root and get rid of the firmware update notifications by installing fotakill.apk.
But when I tried to root using the Nexus 7 toolkit, I chose the option to sideload the zip files for rooting automatically. It asked to flash my boot loader to a lower version (3.34, mine was 3.41) and afterwards it rebooted the device and eventually got stuck at a screen with these lines:
now send the package you want to apply
to the device with adb sideload <filename>
after a long time without anything happening, I suspected that things went wrong and pressed the power button for a few seconds and the device turned off. Now I cannot turn it back on, when plugged in it doesn't show the charging battery, also I cannot boot into fastboot mode by holding Volume down + Power button. The screen stays black the whole time.
I even tried to open the back power and pull the battery out and in again and try to turn on the tablet, nothing happens. I remember the battery level was like roughly 90% the last time the tablet was working, so I don't know what went wrong .

Hold power + vol down button about 30 seconds
Sent from my Nexus 7 using XDA Premium HD app

semeru said:
Hold power + vol down button about 30 seconds
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I tried that but nothing happened .

Press all buttons on the side simultaniously untill fastboot/bootloader mode appears. This should work, no matter if your device is booted or not, or soft bricked or whatever. Then: http://forum.xda-developers.com/showthread.php?t=1907796 .
If it doesn't work however (like after 30-60 seconds), then connect your nexus 7 to your PC. Go to device manager and identify your device. Does it say apx-mode or something like that? Then your device is possibly hard bricked and you might find some answers here: http://forum.xda-developers.com/showthread.php?t=1879228 .
Your should not have used rootkits. Most of these topics appear after people using toolkit. Learn to use fastboot. It's the only program you'll need for the nexus 7. Yes, it's a command line tool but at least it forces you to think before flashing. For example, it was not necessary to downgrade your bootloader. I really don't get why you did that. Also, if you want to run a stable 4.1.2 without the annoying update messages, you can, for example, flash cyanogenmod 10. It's stable, very smooth, and way better than stock.

Westervoort said:
Press all buttons on the side simultaniously untill fastboot/bootloader mode appears. This should work, no matter if your device is booted or not, or soft bricked or whatever. Then: http://forum.xda-developers.com/showthread.php?t=1907796 .
If it doesn't work however (like after 30-60 seconds), then connect your nexus 7 to your PC. Go to device manager and identify your device. Does it say apx-mode or something like that? Then your device is possibly hard bricked and you might find some answers here: http://forum.xda-developers.com/showthread.php?t=1879228 .
Your should not have used rootkits. Most of these topics appear after people using toolkit. Learn to use fastboot. It's the only program you'll need for the nexus 7. Yes, it's a command line tool but at least it forces you to think before flashing. For example, it was not necessary to downgrade your bootloader. I really don't get why you did that. Also, if you want to run a stable 4.1.2 without the annoying update messages, you can, for example, flash cyanogenmod 10. It's stable, very smooth, and way better than stock.
Click to expand...
Click to collapse
Thanks I did a search and finally found an answer. I was running fine on my N7 with PACMan and suddenly it got stuck booting up. So I booted into recovery and reflashed the ROM, and wiped dalvik and cache. When I rebooted it went to "Android is upgrading" like usual after wiping dalvik, then it got stuck there. So I rebooted again and nothing. Just a blank screen. Your suggestion of holding all the buttons down for 30-60 seconds awoke my Nexus. I'm going to wipe everything and start over.

[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.

brick problem, noob here, plz help

my problem is kind of abnormal. i couldnt find solution anywhere so i came here. my device was zenfone 5(t00f)/lollipop.
so i wanted to root my phone. i followed this guide >>
HTML:
http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
the tool i used is called ZenfoneToolkit_20160719, downloaded from here
HTML:
https://drive.google.com/drive/folders/0B0AFmAAcGS5xbWpTQzBQVTN3b1k
. its a bundle of .exe, .dll, .img, .bin files. but no need to work on them seperately, there is a simple cli tool from which you can choose what you want to do and it executes that file for you. below is the list what you can do.
1. Wipe Cache
2. Factory Reset
3. Flash Boot
4. Flash Recovery
5. Flash Fastboot
6. Flash Stock ROM
7. Root
8. Unroot
9. Unlock Bootloader
10. Relock Bootloader
11. Zenfone Rescue aka Debrick
12. Fixing Generic IMEI 004999010640000
13. Backup MicroSD
14. Flash Boretz Kernel Lollipop
so wiped cache[1] first then i tried to root[7]. sadly it didnt work, when i turned the phone on it took me to fastboot screen, there i had only a few options like, normal boot(doesnt happen), recovery mode, restart. when i turned it off and pressed power and volume up together it would go to recovery where none of the options works. i though that was what called brick, so followed this guide to make my life better
HTML:
http://zenfone-blog.blogspot.com/2015/06/guide-how-to-unbrick-asus-zenfone-4-5-6.html
.
my phone by default came with kitkat. so when i downloaded the firmware i wanted to get a kitkat. but i couldnt find a matching recovery img and firmware for kitkat on asus official page. so i downloaded jellybean. ASUS ZenFone 5(T00F/T00J) software Image: V1.18.40.9 ww for firmware from here
HTML:
https://www.asus.com/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/
. and recovery img is 1.18.40.9_ww_recovery.img from here
HTML:
https://www.asuswebstorage.com/navigate/s/644D9E0A19714899974C75FC4B6C87EDY
. i dont know what "ww" means in those name but i saw it in my software version before so i went with it.
All the steps went smoothly, by the end of it i guessed my phone charge would be low so i put it in charge and turned it on. first time it turn on without a problem. i checked out a few things and leave it for charge. after a while i came back and battery was 0%. i thought i would be wise to plug out and in charging port again. as soon as i pull out the pin, screen instantly turned black and the phone went dead after a looooong ass vibration.
now when i try to charge the orenge light at top lights up but the animation that shows battery always show its empty. if i try to turn it on while plugged, it shows asus logo/intel logo and goes dead again. if i try to turn it on without being plugged, it shows a battery logo with a question mark, which i think means the phone cannot find battery.
i am stuck here.... plz someone be my savior.

Hello my dear, to get out of this problem I did the following: I connected the phone to compuador by USB cable (with himself off), then he calls and gets the question symbol, it held the power button plus volume up he must restart to get the logo asus about 4 seconds after loose the power button and continue with the volume button up insured. It should enter into fastboot mode there do the necessary procedures to reflash the system.
I hope you helped, hug!

matheusgcdj said:
Hello my dear, to get out of this problem I did the following: I connected the phone to compuador by USB cable (with himself off), then he calls and gets the question symbol, it held the power button plus volume up he must restart to get the logo asus about 4 seconds after loose the power button and continue with the volume button up insured. It should enter into fastboot mode there do the necessary procedures to reflash the system.
I hope you helped, hug!
Click to expand...
Click to collapse
i tried. but just cannot get to the fastboot screen. :'(

nooblett said:
i tried. but just cannot get to the fastboot screen. :'(
Click to expand...
Click to collapse
use this thread and perhaps there is hope

matheusgcdj said:
use this thread and perhaps there is hope
Click to expand...
Click to collapse
thnx. i am gonna try it now.

@matheusgcdj: yes it worked

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 ?