Database Develop

[Q] Got phone into a highly awkward state

I've got a 64GB HTC One, imported from HK. I (stupidly, in hindsight) accepted the OTA updates - then unlocked via HTCDev, and installed CWM and Cyanogenmod.
After some poking around, I decided to return to Sense, and followed one of the many guides.
I can flash via fastboot successfully (2.24.708.4). Unfortunately, the phone no longer appears in Windows Explorer or via ADB for me to push a ROM or backup image to be used by CWM.
I suspect that somehow I've got into a state where there is no USB debugging enabled on the device, and no system to boot into for me to enable USB debugging.
How can I get a ZIP like Cyanogen, Android Revolution, etc. onto the device without ADB or Windows Explorer?
Feeling somewhat stupid, and a bit helpless.

You should be able to send it through fastboot regardless of your phone state IF you can get to bootloader.
Download the drivers from htcdev, and make sure you have the most updated adb/fastboot. You'll need to get the phone into fastboot. You should be able to send a zip using---> fastboot oem rebootRUU
The send the zip by the cmd----> fastboot flash zip rom.zip (rom.zip being the actual name of the zip)
Let it send. It WILL FAIL. Press the arrow up key on your keyboard to repeat the command and send it a second time. It WILL be a success. Once the command window says success, type---> fastboot reboot
Personally I would use the ruu zip to go back to stock instead of flashing another custom Rom.
Sent from my HTC One using Tapatalk 2

InflatedTitan said:
You should be able to send it through fastboot regardless of your phone state IF you can get to bootloader.
Download the drivers from htcdev, and make sure you have the most updated adb/fastboot. You'll need to get the phone into fastboot. You should be able to send a zip using---> fastboot oem rebootRUU
The send the zip by the cmd----> fastboot flash zip rom.zip (rom.zip being the actual name of the zip)
Let it send. It WILL FAIL. Press the arrow up key on your keyboard to repeat the command and send it a second time. It WILL be a success. Once the command window says success, type---> fastboot reboot
Personally I would use the ruu zip to go back to stock instead of flashing another custom Rom.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Hey,
Thanks for the reply. I can certainly flash a ROM via rebootRUU. I have a 2.24.708.4.zip file, taken from http://forum.xda-developers.com/showthread.php?t=2182823, which contains IMG files (boot.img, recovery.img, etc). Are you saying that I should flash that, and reboot? If I do that, the phone either hangs at a 'HTC - Quietly Brilliant*' screen, or at a black screen.
I also have the larger OTA ZIP, taken from here - http://forum.xda-developers.com/showthread.php?t=2393790. This is what I believe I need to get onto the phone, somehow - are you saying that I can do that via rebootRUU?
Cheers,
steve
* extremely quiet, in my case...

steve_barham said:
Hey,
Thanks for the reply. I can certainly flash a ROM via rebootRUU. I have a 2.24.708.4.zip file, taken from http://forum.xda-developers.com/showthread.php?t=2182823, which contains IMG files (boot.img, recovery.img, etc). Are you saying that I should flash that, and reboot? If I do that, the phone either hangs at a 'HTC - Quietly Brilliant*' screen, or at a black screen.
I also have the larger OTA ZIP, taken from here - http://forum.xda-developers.com/showthread.php?t=2393790. This is what I believe I need to get onto the phone, somehow - are you saying that I can do that via rebootRUU?
Cheers,
steve
* extremely quiet, in my case...
Click to expand...
Click to collapse
Not sure if this will help but try fastboot erase cache after you flash the ruu
EDIT, also make sure you flash the RUU twice

Hmmm those are updates. I've never fastbooted an OTA, it's always been full ruu zips. Before we progress, can you share with me the hboot, are you s-off or s-on, type of M7 you have? (International, Google play, att, tmobile, etc...)
It would be awesome if you could actually snap a pic of your bootloader for me with a different phone and post it here
Also like the poster above me stated, make sure while in rebootRUU you type---> fastboot flash zip rom.zip (rom.zip being the actual zip file name that's in fastboot folder) let it try to send and it'll fail.
Without doing anything more, press the arrow up on your keyboard and it'll repeat the exact command. Let it send for the second time and it'll say success. Then --->fastboot reboot
Sent from my HTC One using Tapatalk 2

[Q] Trying to flash drunk- failed. Now what?

Ok guys, so I was trying to flash the software on my Sprint HTC One with a custom one, while drunk. Needless to say it didn't work. I suspect that chrome f*cked up downloading the rom, because it was only 800mb, and should have been about 1gb. Now, the phone isn't working. When I try to turn it on it shows the htc logo and then boots up in fastboot. Fastboot still receives cmd commands, but I still havent found a way to flash an RUU on it. Tryed with twrp as a recovery- cant mount to computer. Tryed sending the file to phone through cmd- some error about not working radio came through. I'm cutting corners explayning all the methods I tryed to make it work, but there were a lot of them and I dont remember all. I have flashed the boot and the recovery back to the stock ones, bootloader IS unlocked. Phone vertion (as shown in the bootloader screen):
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT- 1.44.0000
OpenDSP-v31.120.274.0617
eMMC- boot
Jul 5 2013,17:19:22:-1
My question is how do I return it to stock condition (or unlocked to all networks if possible)? Please, I've been trying to fix it on my own for over a week now, and am getting desperate. If possible please give links to step-by-step tutorials and/or files I'll need. Thank you in advance.
PS.: Also, for some reason my computer does fails to install the HTC MTP device driver. Could it be from that, and if it is- will using a different computer solve the problem (tryed a million times to fix that as well- no luck)?

drobalqk said:
Ok guys, so I was trying to flash the software on my Sprint HTC One with a custom one, while drunk. Needless to say it didn't work. I suspect that chrome f*cked up downloading the rom, because it was only 800mb, and should have been about 1gb. Now, the phone isn't working. When I try to turn it on it shows the htc logo and then boots up in fastboot. Fastboot still receives cmd commands, but I still havent found a way to flash an RUU on it. Tryed with twrp as a recovery- cant mount to computer. Tryed sending the file to phone through cmd- some error about not working radio came through. I'm cutting corners explayning all the methods I tryed to make it work, but there were a lot of them and I dont remember all. I have flashed the boot and the recovery back to the stock ones, bootloader IS unlocked. Phone vertion (as shown in the bootloader screen):
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT- 1.44.0000
OpenDSP-v31.120.274.0617
eMMC- boot
Jul 5 2013,17:19:22:-1
My question is how do I return it to stock condition (or unlocked to all networks if possible)? Please, I've been trying to fix it on my own for over a week now, and am getting desperate. If possible please give links to step-by-step tutorials and/or files I'll need. Thank you in advance.
Click to expand...
Click to collapse
It sounds like you have the same problem that a lot of people are getting into around here, myself included. You tried to flash a non-cdma compatible rom onto your phone.
There are numerous postings about how to fix this, however, it depends on the condition of your phone which step you take.
If you have recovery installed and you have access to recovery you will take different steps than if you only have access to fastboot.
You need to have a recovery installed and you need to relock your phone to fastboot ruu. Once that is done you basically start from scratch and unlick your phone again and then you can reinstall the recovery and then flash the correct cdma compatible roms.

MrFixit007 said:
It sounds like you have the same problem that a lot of people are getting into around here, myself included. You tried to flash a non-cdma compatible rom onto your phone.
There are numerous postings about how to fix this, however, it depends on the condition of your phone which step you take.
If you have recovery installed and you have access to recovery you will take different steps than if you only have access to fastboot.
You need to have a recovery installed and you need to relock your phone to fastboot ruu. Once that is done you basically start from scratch and unlick your phone again and then you can reinstall the recovery and then flash the correct cdma compatible roms.
Click to expand...
Click to collapse
The recovery I can install in a matter of seconds, same with relocking. I have the lastest vertions on both TWRP and Clockwork. Which one do I install and how do I proceed after? Thank you

drobalqk said:
The recovery I can install in a matter of seconds, same with relocking. I have the lastest vertions on both TWRP and Clockwork. Which one do I install and how do I proceed after? Thank you
Click to expand...
Click to collapse
do you have adb access? or only fastboot access?

MrFixit007 said:
do you have adb access? or only fastboot access?
Click to expand...
Click to collapse
adb- Im not sure. How do I check? Fastboot- I think so. It accepts my cmd commands for flashing recovery and rom (although when I tryed to flash rom it failed).

drobalqk said:
adb- Im not sure. How do I check? Fastboot- I think so. It accepts my cmd commands for flashing recovery and rom (although when I tryed to flash rom it failed).
Click to expand...
Click to collapse
In your command window in the same directory you run fastboot from, you should be able to run adb.
The easiest way to check is to type: adb devices
this should return a value if you are booted into recovery.
it will give you nothing if you aren't in recovery.
if you cannot get into recovery then you need to make sure your phone is unlocked and then fastboot a recovery onto your phone.

MrFixit007 said:
In your command window in the same directory you run fastboot from, you should be able to run adb.
The easiest way to check is to type: adb devices
this should return a value if you are booted into recovery.
it will give you nothing if you aren't in recovery.
if you cannot get into recovery then you need to make sure your phone is unlocked and then fastboot a recovery onto your phone.
Click to expand...
Click to collapse
I currently have the stock recovery flashed on it. Is that one going to work or should I flash TWRP/ Clockwork?

drobalqk said:
I currently have the stock recovery flashed on it. Is that one going to work or should I flash TWRP/ Clockwork?
Click to expand...
Click to collapse
as long as you can boot into recovery, it should work. i personally favor twrp, but any recovery should work.
try out some adb commands and see.
adb sevices
adb shell
if you get anywhere with those while booted into recovery you should be ok.

MrFixit007 said:
as long as you can boot into recovery, it should work. i personally favor twrp, but any recovery should work.
try out some adb commands and see.
adb sevices
adb shell
if you get anywhere with those while booted into recovery you should be ok.
Click to expand...
Click to collapse
adb devices returns no values
adb services returns big list of commands
adb shell returns error device not found.
I'm into TWRP v.2.6.1.0 start screen.

drobalqk said:
adb devices returns no values
adb services returns big list of commands
adb shell returns error device not found.
I'm into TWRP v.2.6.1.0 start screen.
Click to expand...
Click to collapse
did those adb errors or no devices found occur while your phone was showing the twrp start screen?
if yes, then we need to reboot into the bootloader-- to fastboot.
if no then try adb shell again while showing the twrp start screen.

MrFixit007 said:
did those adb errors or no devices found occur while your phone was showing the twrp start screen?
if yes, then we need to reboot into the bootloader-- to fastboot.
if no then try adb shell again while showing the twrp start screen.
Click to expand...
Click to collapse
Yes, I was IN TWRP recovery home screen. I'll try the commands in fastboot as soon as I come back from work. Thank you for the time you spend trying to help me, I do very much apreciate it.

drobalqk said:
Yes, I was IN TWRP recovery home screen. I'll try the commands in fastboot as soon as I come back from work. Thank you for the time you spend trying to help me, I do very much apreciate it.
Click to expand...
Click to collapse
It seems like you need to fastboot flash recovery onto your phone again.
Here are the steps as I think they should work to get you back up and running.
**Make sure your phone is unlocked. (it should display ***UNLOCKED*** at the top of the bootloader screen)
if you ARE unlocked do the following(+++see below if you are NOT unlocked+++)
1. from bootloader select fastboot - connect phone to computer. fastboot should change to fastboot usb when you have a good connection.
on your computer:
2. open a command window and navigate to the folder where adb and fastboot are located
3. type in "fastboot flash recovery xxxxxxxx.zip" where xxxxxxxx.zip is the name of recovery zip file without quotes. Make sure you download a good copy appropriate for your phone. I would use this one: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.1.0-m7wls.img
4. type fastboot reboot
on your phone:
5. once it is rebooted and in bootloader select recovery and boot into recovery.
on your computer:
6. once your phone shows recovery main screen then typeat the command prompt: adb shell
7. no matter what the prompt looks like type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
8. no matter if it errors or not type: adb reboot bootloader
9. type: fastboot oem lock
10. type: fastboot oem rebootRUU
11. type fastboot flash zip xxxxxxxxxxxxx.zip where xxxxxxxxxxxxx.zip is the name of the ruu.zip file. i would use this one: http://www.androidfilehost.com/?fid=22926241640219526
12 reboot your phone once that is successful!! If you get the "flush image again immideately" error message then repeat step 11. then reboot your phone.
you should now be running a stock sprint phone.
you can now unlock your phone again and reinstall a recovery.
to unlock your phone the second time:
13. boot your phone into bootloader then go to fastboot - make sure the phone is connected to the computer
14. on your computer type in: fastboot flash unlocktoken Unlock_code.bin
15. on your phone select unlock with volume rocker and press power once unlock is selected
16. on computer type: fastboot flash recovery xxxxxxxxx.zip where xxxxxxxxxx.zip is the same recovery zip file we used above in step 3
17. reboot your phone and you are now unlocked and you have a custom recovery installed and you can download a CDMA compatible rom to your phone and install it with the recovery like normal. or you can continue to run stock.
MAKE SURE YOU ONLY DOWNLOAD CDMA COMPATIBLE ROMS FROM THE SPRINT HTC ONE FORUMS.
enjoii!!
+++if you are NOT unlocked+++
try the following:
step 13
step 14
step 15
step 16
step 4
step 5
step 6-17
make sure you complete all the way through 17 after you do step 6. good luck and let me know what your results are.

MrFixit007 said:
It seems like you need to fastboot flash recovery onto your phone again.
Here are the steps as I think they should work to get you back up and running.
**Make sure your phone is unlocked. (it should display ***UNLOCKED*** at the top of the bootloader screen)
if you ARE unlocked do the following(+++see below if you are NOT unlocked+++)
1. from bootloader select fastboot - connect phone to computer. fastboot should change to fastboot usb when you have a good connection.
on your computer:
2. open a command window and navigate to the folder where adb and fastboot are located
3. type in "fastboot flash recovery xxxxxxxx.zip" where xxxxxxxx.zip is the name of recovery zip file without quotes. Make sure you download a good copy appropriate for your phone. I would use this one: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.1.0-m7wls.img
4. type fastboot reboot
on your phone:
5. once it is rebooted and in bootloader select recovery and boot into recovery.
on your computer:
6. once your phone shows recovery main screen then typeat the command prompt: adb shell
7. no matter what the prompt looks like type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
8. no matter if it errors or not type: adb reboot bootloader
9. type: fastboot oem lock
10. type: fastboot oem rebootRUU
11. type fastboot flash zip xxxxxxxxxxxxx.zip where xxxxxxxxxxxxx.zip is the name of the ruu.zip file. i would use this one: http://www.androidfilehost.com/?fid=22926241640219526
12 reboot your phone once that is successful!! If you get the "flush image again immideately" error message then repeat step 11. then reboot your phone.
you should now be running a stock sprint phone.
you can now unlock your phone again and reinstall a recovery.
to unlock your phone the second time:
13. boot your phone into bootloader then go to fastboot - make sure the phone is connected to the computer
14. on your computer type in: fastboot flash unlocktoken Unlock_code.bin
15. on your phone select unlock with volume rocker and press power once unlock is selected
16. on computer type: fastboot flash recovery xxxxxxxxx.zip where xxxxxxxxxx.zip is the same recovery zip file we used above in step 3
17. reboot your phone and you are now unlocked and you have a custom recovery installed and you can download a CDMA compatible rom to your phone and install it with the recovery like normal. or you can continue to run stock.
MAKE SURE YOU ONLY DOWNLOAD CDMA COMPATIBLE ROMS FROM THE SPRINT HTC ONE FORUMS.
enjoii!!
+++if you are NOT unlocked+++
try the following:
step 13
step 14
step 15
step 16
step 4
step 5
step 6-17
make sure you complete all the way through 17 after you do step 6. good luck and let me know what your results are.
Click to expand...
Click to collapse
Nope, adb still doesn't work. Could it be something wrong with the drivers my computer installs? Because when I'm in recovery my computer detects the device in "Other Devices" as "M7WLS", and I don't have a driver for that and neither does microsoft update. Any suggestions?

drobalqk said:
Nope, adb still doesn't work. Could it be something wrong with the drivers my computer installs? Because when I'm in recovery my computer detects the device in "Other Devices" as "M7WLS", and I don't have a driver for that and neither does microsoft update. Any suggestions?
Click to expand...
Click to collapse
Did you install HTC Sync or did you install the naked drivers from here?
Otherwise, where in the process did you get stopped?
EDIT: You can always PM me your teamviewer info and I can work on it.

[Q] Trying to flash zip, now fastboot doesn't work

Hi Guys,
So I have successfully S-OFF'd my device using rumrunner, and I was then using the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2358781 in order to flash my device to a Google Play Edition device.
It worked fine for the commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip
and then I got the expected error message. I then entered the same command again as instructed, but this time I got the message "waiting for device" which didn't go away.
I've tried rebooting my phone a few times, and I can no longer get any fastboot.exe commands to work, I just continuously get the "waiting for device"message. adb.exe still works correctly, so after rebooting my phone I can use adb to boot into fastboot (I know that's not the only way, I'm just saying it to demonstrate that adb appears to be fine) but after that no fastboot.exe commands work anymore.
My phone is running Software version 3.62.401.1. My Hboot I was very sure used to be 1.55 but now after that failed "fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip" it now shows as HBOOT 1.54.
Thanks guys, any help would be immensely appreciated.

Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?

SaHiLzZ said:
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
Click to expand...
Click to collapse
Trying another fast boot package didn't work, but a different computer did. Now I'm all set and ready to go thanks!
Just for the record, on the first computer my phone no longer showed up when I put in fastboot devices. I guess for some strange reason there's now a problem with the drivers on the first computer? I thought perhaps reinstalling HTC Sync would help that apparently not.
Anyways, that problem is solved until I want to do this again and want to use the first computer again.

[Q] 'No OS installed! Are you sure you want to boot?' How to reinstall android os?

I dont know much about this stuff (def not tech savvy), but I decided to take my bad esn Sprint HTC One (running 4.3) and try to unlock it myself. I was successful in unlocking the bootloader, and I even rooted the device on my own (woo!!!). I was on the last stage of finally unlocking the phone, so I decided to go for it.
I tried to follow these steps to finally unlock my HTC One, but I did not know how to go to /system/app to replace the files (The 'Root Reader' app didn't show /system/app in my phone).
://forum.xda-developers.com/showthread.php?t=2491840
The files were:
HtcOMADM_SettingsPlugin_SPCS.apk
HtcOMADM_SPCS.apk
As a result, I tried to flash the copy files mentioned previously using this video as a guide
http://www.youtube.com/watch?v=JhR4Je4I8yw
I dragged and dropped the copies into the 'system storage' (not into a specific file) and started wiping data in TWRP 2.6 (Im assuming I wiped something that I shouldnt have). However, now whenever I try to boot my HTC One out of TWRP, I get the 'No OS installed..." message and it just just keeps showing the white screen with the HTC logo when I do boot anyways. When I connect my HTC One to my PC via usb cable, it doesnt even show up. I decided to take a screen shot of my files/drives/etc that I used. When I click on the 'instal' button in TWRP, it no longer shows the 'android' folder while scrolling through the list of things. My phone also automatically shuts off when leaving it on idle (TWRP running) for a bit, it doesnt connect to my PC anymore too
What should I do to get the phone working again? Could I unlock it from here or do I have to backtrack or something? I have very little knowledge about this stuff so please try to explain things easily for me lol

You need to relock your phone and run a ruu and to reroot your phone with the latest version of twrp 2.6 .3.0 and supersu 1.9.1 I think but you can check that when you run the ruu in the app store real quick to see if it is the latest version.

On the PC download the RUU
http://dl3.htc.com/application/RUU_..._NV_SPCS_4.38_003_release_348053_signed_2.exe
Connect USB cable to the phone to the PC (keep the phone connected until you are done)
1. Boot your phone to the bootloader (volume down and power on). Go to fastboot option on the phone menu.
2. Now using fastboot on your PC type fastboot oem lock
3. Boot your phone to the bootloader (volume down and power on). Go to fastboot option on the phone menu.
4. Now using fastboot on your PC type fastboot oem rebootRUU
5. Run the RUU that you downloaded. That will put your phone back to stock.
---------------------------------------
To unlock the bootloader:
1. Goto http://www.htcdev.com/ follow the steps.
Install custom recovery
2. Install TWRP. Download http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img put in in the same folder on your PC as your fastboot.exe command.
3. fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
4. reboot phone.
Install root:
download http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip?retrieve_file=1
copy UPDATE-SuperSU-v1.65.zip to the phone
Boot your phone to the bootloader (volume down and power on). Go to recovery option on the phone menu. That will boot into TWRP. Use the install and install the zip UPDATE-SuperSU-v1.65.zip.

Just sideload a rom.zip
Sent from my HTC One using Tapatalk

elvisypi said:
Just sideload a rom.zip
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
How would I do that? I just installed the HTC 4.2.001 driver to my pc as well

stuck, failed ruu no os

flashed twrp the other night, didn't realize it was the wrong version... apparently sprint needs a special one.
flashed the right one. somehow have no os now.
ran ruu which failed. now it's stuck on black htc screen with exclamations in all four corners.
tried to run ruu again, just says usb error.... don't know what to do next.

Mud3 said:
flashed twrp the other night, didn't realize it was the wrong version... apparently sprint needs a special one.
flashed the right one. somehow have no os now.
ran ruu which failed. now it's stuck on black htc screen with exclamations in all four corners.
tried to run ruu again, just says usb error.... don't know what to do next.
Click to expand...
Click to collapse
I recently had the same issue, you should be able to fix this by following these steps, keep in mind, continuing this process will unroot your device. Thus, you will loose all of your data on your phone.
first begin by booting into bootloader, then plugging in your device via usb cable to your computer, it should now say "fastbootusb" on the device's screen.
if you don't already have the the fastbooot files required for your computer, you can download them here: ftp.qbking77.(com)/Files/OneDrivers_Fastboot.zip
after that, extract the zip file somewhere on your computer, and open the fastboot folder. Now hold down shift and click on an empty space in the folder and choose open new command window here, or something along those lines.
Now that you've done this, type fastboot oem lock and press enter, this will relock your phones bootloader.
Now, unplug your phone from usb, and reboot back into fastboot, and once again, plug the device into the computer. Just as before, your phones screen should now say fastboot usb. You can now flash this file via fastboot by following the instructions below.
androidfilehost.(com)/?fid=23329332407568410
rename the file downlaoded to firmware.zip and copy it to the folder containing your fastboot.exe file
now in the command prompt window, type in Fastboot oem rebootRUU
you should now see a black screen with the HTC logo, type Fastboot flash zip firmware.zip,
once that is complete, type fastboot reboot and once more, reboot into fastboot
you can now download this RUU file from the following link: androidfilehost.(com)/?fid=23329332407573774
extract the zip folder somewhere on your computer
boot into bootloader, and once again choose fastboot,
plug in your usb cable to your phone and computer, and the phone should once again say fastboot usb.
now open the folder you extracted and run ARUWizard.exe, this will unroot your device and return you to stock.
now, if you wish, you may re root your device.
Hope this works, if none of this makes sense, mention it. I typed this up in a bit of a rush.
also, you will have to copy and paste the links, as I have not made 10 general posts, so I can't add direct links to my post. Sorry mate.

have issue with the first step there... can't boot into bootloader, i'm stuck on the black screen with silver htc letters in the middle, exclamation on all four corners. i'm able to turn off the phone using the flashlight trick, but when i boot back up it's to that screen every time. it's stuck there from a failed ruu, just don't know how to get un stuck...

okay, some more info here. I was running hboot 1.57 ( i did relock) trying to run ruu 5_03_651_3 i'm not even positive this is the ruu i should be trying to use. now when I try to run the ruu it starts going but every time eventually fails wtih windows bringing up an error that says htc_fastboot.exe has topped working. i hit close program and the rom update utility gives me error [171]: usb connection error
edit: and now after the sixth time of that failing i am able to boot into bootloader again! weird... and it says i have an os now... still wont boot up all the way, but it's no longer blank on the bootloader screen.
second edit: after getting the usb error again and again i remembered glossing over something about flashing roms not liking usb 3.0 or something... switched to a usb 2.0 port and ruu worked perfectly. now to try and get this thing rooted again.