Database Develop

Did I just brick my Hero? Help!

Some basic info about my phone-
HBOOT 1.47.0000
Radio 2.42.01.04.23
Carrier- iWireless (Kroger, Sprint subsidary)
S-ON
Alright, so I was just using my phone as normal. Running CM7.2 and ClockWorkMod Recovery. I turned off my phone, everything was fine. When I went to turn it on again, it showed the green HTC logo, as per normal, then it suddenly rebooted. There, it showed the green HTC logo again, and it'll just stay there. So I tried to boot into recovery (pulled the battery, put it back in, held the red end call button + volume down, got into hboot, then pressed home to go to recovery).
The thing is- it did the same thing. Reboot before it gets to recovery, and then stuck at the HTC Logo. I tried using the Sprint RUU, didn't work- it told me to download the right RUU for this phone, and gives me an error 131. I used the flashable RUU found in this thread (found here), in conjunction with this tutorial (found here). It gave me an error that looked like this when I ran "fastboot flash zip *flashable RUU zip path*"
Code:
FAILED (remote: 42 custom id check fail)
I believe it has something to do with the fact that it is NOT a Sprint branded phone. It doesn't even have a Google logo on the back.
Since it's not S-OFF, I can't flash a recovery via fastboot. I'm stuck. Help?
*TO CLARIFY*
I can't get into Recovery, or the actual system. I also can't access adb. The only part I can access is the bootloader and fastboot.

How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\

laie1472 said:
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
About 75% if I remember correctly. Only light usage. And I just turned it off in school, we were taking a test. Nothing abnormal about turning it off. And yes, several times. Tried flashing recovery/system/boot in every way possible, using that command and not using that command. I noticed something else- it seems like the NAND memory is completely wiped. There is NOTHING on the phone, other than the bootloader.

After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\

laie1472 said:
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Yes, I tried flashing multiple times. As I said, it fails with a CID check failure. And it doesn't seem that there's anything on the NAND anymore, as it doesn't even get to the boot logo, and recovery will just restart the phone.
My PC recognizes my phone, only in fastboot. And just normal bootloader info- model number, baseband, etc.

Hard Reset Not Working

Lately my phone has been rebooting itself quite a bit. It seems to be getting progressively worse to the point where if I open any app for more than a minute or two then my phone will reboot. I've tried uninstalling quite a few third party apps but that didn't do the trick. Whenever I try to do a hard reset (whether it's through settings or the HBOOT menu) the phone will shut down and then instead of getting the picture of a phone with the green thing in the middle and a status bar below that indicating the phone is resetting, I get a picture of a phone with a red symbol similar to a hazard sign that will last for about 30 seconds then the phone just boots back up to my home screen. I had put an incorrect custom ROM on this phone about 5-6 months ago but I was able to get the stock Sprint ROM back on the phone and relock the boot loader and the phone functioned fine ever since up until about a week ago when it started rebooting randomly. I have a feeling this may be part of the reason why the factory reset is not working. Does anyone have any ideas on how to proceed? Can I do a factory reset by pushing a ROM to the phone through my computer?

If u are s-off then I suggest u download the ruu and run it. If s-off all u have to do is go to hboot and select fast boot and run the program it will reset the phone back to whatever software version it is for the ruu. If your not s-off you will need to get the ruu that matches your firmware. That should fix your troubles if not then you have something faulty with the hardware itself
Sent from my iPad using Tapatalk

Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked

coppertop4646 said:
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
Click to expand...
Click to collapse
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk

luigi311 said:
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Ok I tried that RUU yesterday and couldn't seem to get anywhere because I kept getting error 170 (tried updating drivers, installing HTC sync, etc). Tried again today and got error 170 again, so then I went in my bootloader, then fastboot, connected USB cable, fastboot usb. I then ran the RUU and it said it was going to update my phone. The status bar then said "Waiting for bootloader" and my phone just rebooted itself to the home screen and then I got like error 171 or something (another USB error). I'm kind of running out of ideas at this point. I believe something is wrong with my recovery or I have some sort of bug because I attempted to flash a custom recovery today (TWRP) but when I unlocked my bootloader, I restarted the phone and entered my bootloader again but it still said relocked (even though the prompt on my phone came up giving me the warnings asking if I was sure I wanted to unlock the bootloader) so when I run the command fastboot flash recovery twrp.img I get something along the lines of can't read twrp.img or can't open twrp.img (yes I made sure the file is in the same folder that I am running the adb out of). Willing to try any recommendations at this point because my phone is pretty useless as of right now because it restarts every couple minutes. HTC wants $150 to fix it which I told them I'm not willing to pay, rather buy a new phone.

[Q] Need to RUU back to stock from bootloader only

I'm stuck in the boot loader and adb devices says *daemon not running. starting it now.... *damon started successfully* List of devices attached ... BLANK...
I need to go back to stock since ALL RUU's cannot flash says wrong version
Image version 1.31.651.2 when installing 1.29.651.10 .... Error will not work..
I'm stuck in the bootloader without TWRP or recovery or anything other than Fastboot USB and Bootloader reboot power down basically...
THANKS

[Q] Carrier Unlock to AT&T Anyone?!?
Can someone help me get my phone completely wiped back to 110% stock everything so I can attempt to carrier unlock it to AT&T?
I paid for my Carrier unlock codes and want to use the phone on AT&T but nothing pops up to enter codes or anything like that at all...
My phone apparently has no recovery and no rom but hangs booting the rom....
Can someone who already carrier unlocked to AT&T in the USA tell me about the speeds and thoughts on how you did it?
I paid for my IEMI unlock pin and codes... now i just need to enter them and i had tried on ViperOne ... not stock
THANKS

1chris89 said:
I'm stuck in the boot loader and adb devices says *daemon not running. starting it now.... *damon started successfully* List of devices attached ... BLANK...
I need to go back to stock since ALL RUU's cannot flash says wrong version
Image version 1.31.651.2 when installing 1.29.651.10 .... Error will not work..
I'm stuck in the bootloader without TWRP or recovery or anything other than Fastboot USB and Bootloader reboot power down basically...
THANKS
Click to expand...
Click to collapse
Try this RUU.

Threads merged. @1chris89 please do not post like questions in different sections.

TonyStark said:
Threads merged. @1chris89 please do not post like questions in different sections.
Click to expand...
Click to collapse
Loading latest RUU ... has been about 10 minutes and its stuck at 4%... I just killed the process on windows 7 x64 and with it still on the HTC logo held power and volume down. Which booted back to bootloader... Gonna try it again...................................................

1chris89 said:
I'm stuck in the boot loader and adb devices says *daemon not running. starting it now.... *damon started successfully* List of devices attached ... BLANK...
I need to go back to stock since ALL RUU's cannot flash says wrong version
Image version 1.31.651.2 when installing 1.29.651.10 .... Error will not work..
I'm stuck in the bootloader without TWRP or recovery or anything other than Fastboot USB and Bootloader reboot power down basically...
THANKS
Click to expand...
Click to collapse
well first youre not supposed to use adb in the bootloader thats what fastboot is for. ensure that youre in fastboot and not hboot mode and if your drivers are installec properly you will see fastboot usb and is you run fastboot devices your device will appear when plugged into the computer. also you dont have to be on a stock rom to sim unlock just have to be on a sense rom.

Thanks I have gone through the tutorials and sim unlocking doesn't work. Its not the same as when unlocking an AT&T or T-Mobile phone when you put in the new sim and it asks for a code to unlock, enter code ----- Done.
So right now my TWRP is frozen basically can't use my touch to use it it's frozen.
Should I just RUU back to 5.0.3.6 stock....?
I just want to enter my unlock code HTC sent me.... Otherwise this phone is literally a Paper Weight.
Thanks

Are you soff?

Hi I installed GSM TWRP on my SPRINT and I can't get TWRP to work anymore it's like frozen to touch input...
I just wanna get SPRINT TWRP so I can disable SIMLOCK in the BOOTLOADER so I can use my AT&T sim with it.
I tried all the RUU's and they sit at "1/5 CHECKING HEADER..."
THANKS

That's the step it kept stopping at for me. Try the guide I wrote here: http://forum.xda-developers.com/spr...de-reset-phone-using-ruu-htcfastboot-t2876110

HTC Desire 510 can't do anything with it. Stuck

So here's the story... this is an HTC Desire 510 purchased from Telus here in Canada. I've been messing around with different kernels, ROMs, etc. None of them really worked well for me, so I decided to go back to stock, unlock and try to sell it. Now I'm stuck at the bootloader and I can't figure out what to do. I tried to re-lock the bootloader so I could flash the stock ROM (those were the instructions I read)...
Whenever it boots, it gets to the recovery screen. ("Fastboot USB" / HBOOT) it says *Tampered* and *Relocked* at the top.
Then, when I try to unlock it with Unlock_code.bin (I have tried every method available), and say "Yes", I get the Fastboot USB screen with an overlay that says - at the top: Entering Recovery...
at the bottom it says: This build is for development purposes only, etc.
Then it just stays there until I remove the USB cable and the battery.
I reboot and I get the same thing every time.
Is there any way to fix this? I've tried many an adb command with no avail. I'm ready to throw this thing into the river.

cjmitchell said:
So here's the story... this is an HTC Desire 510 purchased from Telus here in Canada. I've been messing around with different kernels, ROMs, etc. None of them really worked well for me, so I decided to go back to stock, unlock and try to sell it. Now I'm stuck at the bootloader and I can't figure out what to do. I tried to re-lock the bootloader so I could flash the stock ROM (those were the instructions I read)...
Whenever it boots, it gets to the recovery screen. ("Fastboot USB" / HBOOT) it says *Tampered* and *Relocked* at the top.
Then, when I try to unlock it with Unlock_code.bin (I have tried every method available), and say "Yes", I get the Fastboot USB screen with an overlay that says - at the top: Entering Recovery...
at the bottom it says: This build is for development purposes only, etc.
Then it just stays there until I remove the USB cable and the battery.
I reboot and I get the same thing every time.
Is there any way to fix this? I've tried many an adb command with no avail. I'm ready to throw this thing into the river.
Click to expand...
Click to collapse
Is it 64 bit or 32 bit? And what type of recovery did you have on it before?

MrMike2182 said:
Is it 64 bit or 32 bit? And what type of recovery did you have on it before?
Click to expand...
Click to collapse
It's 32 bit and it had TWRP.

cjmitchell said:
It's 32 bit and it had TWRP.
Click to expand...
Click to collapse
What you need to do first of all is find an RUU for your device and then find the original recovery, not the twrp recovery but the actual recovery that was on the phone when you first got it. If you don't flash the original recovery then the RUU will refuse to continue and that's basically HTC's way of trying to prevent us from breaking the phone.. The unlock code you got from HTC you should have kept and whenever you sell the phone pass it along to the new owner.. So to help you understand everything I said first unlock your bootloader again and then flash the original recovery and then lock the bootloader again then run the RUU on the PC.. Some times you have to run the RUU a few times to finally get it to finish completely cause some times it'll hang and just sit there so just end the process and restart it but before ending it be sure you gave it enough time to try before thinking it's stuck because it may not be... After the RUU finishes, the phone will totally be stock again the same way it was the day you bought it..

MrMike2182 said:
What you need to do first of all is find an RUU for your device and then find the original recovery, not the twrp recovery but the actual recovery that was on the phone when you first got it. If you don't flash the original recovery then the RUU will refuse to continue and that's basically HTC's way of trying to prevent us from breaking the phone.. The unlock code you got from HTC you should have kept and whenever you sell the phone pass it along to the new owner.. So to help you understand everything I said first unlock your bootloader again and then flash the original recovery and then lock the bootloader again then run the RUU on the PC.. Some times you have to run the RUU a few times to finally get it to finish completely cause some times it'll hang and just sit there so just end the process and restart it but before ending it be sure you gave it enough time to try before thinking it's stuck because it may not be... After the RUU finishes, the phone will totally be stock again the same way it was the day you bought it..
Click to expand...
Click to collapse
HTC or Telus don't provide a RUU for the Telus version of the phone so I've been trying the Cricket version, doesn't work. It gives me the message: ERROR [131]: CUSTOMER ID ERROR.
There is some russian website that seems to have it for Telus, but you have to pay to access it, and I don't even know if it's what I need. ir-file.com (I can't post links)
So I'm not going down that rabbit hole.
I can't flash any recovery I find...
"fastboot getvar platform" gives me hTCBmsm2886
"fastboot flash recovery (*.img)" gives me a message saying FAILED (remote: signature verify fail) for every single recovery image I can find. Nothing works.

cjmitchell said:
HTC or Telus don't provide a RUU for the Telus version of the phone so I've been trying the Cricket version, doesn't work. It gives me the message: ERROR [131]: CUSTOMER ID ERROR.
There is some russian website that seems to have it for Telus, but you have to pay to access it, and I don't even know if it's what I need. ir-file.com (I can't post links)
So I'm not going down that rabbit hole.
I can't flash any recovery I find...
"fastboot getvar platform" gives me hTCBmsm2886
"fastboot flash recovery (*.img)" gives me a message saying FAILED (remote: signature verify fail) for every single recovery image I can find. Nothing works.
Click to expand...
Click to collapse
Did you try to reflash twrp? If I was in your predicament I'd flash twrp and then there is a rom that I configured to work great on the 32 bit phones it's the Modded CM11 and I'm pretty sure it'll work on yours albeit the cameras aren't working yet at least it's a start and you can find the CM11 I configured here ----> Modded CM11

MrMike2182 said:
Did you try to reflash twrp? If I was in your predicament I'd flash twrp and then there is a rom that I configured to work great on the 32 bit phones it's the Modded CM11 and I'm pretty sure it'll work on yours albeit the cameras aren't working yet at least it's a start and you can find the CM11 I configured here ----> Modded CM11
Click to expand...
Click to collapse
Yeah, I tried to reflash TWRP, I get that message "FAILED: (remote: signature verify fail)"
That is after I type in the C:\adb\ folder "fastboot flash recovery twrp-2.8.7.0-a11.img"
and every other recovery image I can find, including older versions of TWRP.
This is why I'm frustrated, nothing works. If I could flash a ROM that'd be cool, but I can't get out of the bootloader, I can't even get into recovery.

cjmitchell said:
Yeah, I tried to reflash TWRP, I get that message "FAILED: (remote: signature verify fail)"
That is after I type in the C:\adb\ folder "fastboot flash recovery twrp-2.8.7.0-a11.img"
and every other recovery image I can find, including older versions of TWRP.
This is why I'm frustrated, nothing works. If I could flash a ROM that'd be cool, but I can't get out of the bootloader, I can't even get into recovery.
Click to expand...
Click to collapse
I need you to type everything you see on your HBoot screen when you pull the battery and put it back in and then hold the volume down button and then press the power button at the same time and when the screen comes up type everything you see in here so I can see it... I think the reason you're getting the remote signature failure is because the bootloader is still locked and you have to make sure it really is unlocked.. Try that then get back to me.

Yeah, the bootloader is still locked. here's what it says:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 19 2015,21:13:29.0
Then the regular menu.
I can't seem to unlock the bootloader.

cjmitchell said:
Yeah, the bootloader is still locked. here's what it says:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 19 2015,21:13:29.0
Then the regular menu.
I can't seem to unlock the bootloader.
Click to expand...
Click to collapse
Well if you had the boot unlocked before, why can't you send the unlock_code.bin to it and have it unlock again? Or did you lose the key? Because you're supposed to keep that key.. Did you use some sort of program to try and root the phone? Like them 1 click root apps...
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Go download this to a computer/laptop whatever and connect the phone to it and try to run this RUU on the PC while the phone is connected to it and turned on in HBoot/fastboot... Do this before trying to unlock the boot again and if it hangs try it again because some times it can take 3 or 4 tries to get it to work... Download Cricket RUU - http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Edit: I know you said your carrier is Telus and I know that's a Cricket RUU that I listed, but they are both the same so run it!!
Edit again: Never mind don't bother running the RUU because you're not s-off and you can't change your CID so I suggest you find a way to unlock your bootloader again somehow and then flash the CM11 to test out.

MrMike2182 said:
Well if you had the boot unlocked before, why can't you send the unlock_code.bin to it and have it unlock again? Or did you lose the key? Because you're supposed to keep that key.. Did you use some sort of program to try and root the phone? Like them 1 click root apps...
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Go download this to a computer/laptop whatever and connect the phone to it and try to run this RUU on the PC while the phone is connected to it and turned on in HBoot/fastboot... Do this before trying to unlock the boot again and if it hangs try it again because some times it can take 3 or 4 tries to get it to work... Download Cricket RUU - http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Edit: I know you said your carrier is Telus and I know that's a Cricket RUU that I listed, but they are both the same so run it!!
Edit again: Never mind don't bother running the RUU because you're not s-off and you can't change your CID so I suggest you find a way to unlock your bootloader again somehow and then flash the CM11 to test out.
Click to expand...
Click to collapse
I have the unlock_code.bin, I've been trying to send it to the phone but it doesn't work. I've tried the WinDroid app and the command line "fastboot flash unlocktoken unlock_code.bin" and I get to the screen that asks if I want to unlock the bootloader, but when I select "Yes" it hangs and sticks on that screen, but at the top it says: "Entering Recovery..." and at the bottom it says "This build is for development purposes only", etc.
If I can't flash anything then I'm guessing it's perma-bricked... :/

cjmitchell said:
I have the unlock_code.bin, I've been trying to send it to the phone but it doesn't work. I've tried the WinDroid app and the command line "fastboot flash unlocktoken unlock_code.bin" and I get to the screen that asks if I want to unlock the bootloader, but when I select "Yes" it hangs and sticks on that screen, but at the top it says: "Entering Recovery..." and at the bottom it says "This build is for development purposes only", etc.
If I can't flash anything then I'm guessing it's perma-bricked... :/
Click to expand...
Click to collapse
Right it hung there because there was no recovery flashed so right after you unlock that no matter what just flash twrp to it the second after you tap yes to unlock the bootloader send the recovery to it.

MrMike2182 said:
Right it hung there because there was no recovery flashed so right after you unlock that no matter what just flash twrp to it the second after you tap yes to unlock the bootloader send the recovery to it.
Click to expand...
Click to collapse
as soon as I hit the "Yes" option on the "Unlock bootloader?" screen, it tries to go into recovery. And it's instant. There is no window where I can flash the recovery - I've tried it multiple times.
So I can't unlock it and I can't flash a recovery.
I'm afraid this thing is done for...

cjmitchell said:
as soon as I hit the "Yes" option on the "Unlock bootloader?" screen, it tries to go into recovery. And it's instant. There is no window where I can flash the recovery - I've tried it multiple times.
So I can't unlock it and I can't flash a recovery.
I'm afraid this thing is done for...
Click to expand...
Click to collapse
You are supposed to be unlocking it from a PC and flashing the recovery from the PC also not trying to flash the recovery from the phone you cant do that unless the phones working.. Don't you have minimal ADB and Fastboot installed on a Windows PC?

Bad Encryption Gone Wrong

Hi Guys/Girls,
So today a friend gave me a HTC m7 to try and fix........From what i can gather something went wrong when they tried to encrypt the phone. Now when turn it on it asks for a password, when you get it wrong it wants to reset the phone, but this achieves nothing and you end up back at the encryption page. Neither Recovery Or Factory Reset work it comes up with: E:failed to mount /data. Also says some stuff before that about E:missing bitmap oem_unlock_bg, which im guessing is why i cant unlock the bootloader? i can get fastboot to work but as soon as i ask for the token it just sits and does nothing. adb does not seem to work.
As a side note i have 2 other htc m7's with broken screens, so if this is something that needs a hardware change that may be possible id assume?. I'm just unsure where to go from here, if i cant unlock the bootloader then what can you do???
I've rooted a few phones but your talking to abit of a beginner here guys.
Anyway TIA!

RUU (Rom update utility)
Sent from my SM-N930F using Tapatalk

clsA said:
RUU (Rom update utility)
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
Sorry if this seems nooby, but can you use a RUU with a locked boot loader and s-on? i cant even get the phone to respond to "fastboot oem get_identifier_token". I've been all over htc1guru but its abit beyond me, does fastboot flash work on a locked bootloader?

This seems to be a pretty bad catch 22, i cant fix the issue, because the issue stops me from doing anything. Any alternate ways around this guys???

Happyhog11 said:
Sorry if this seems nooby, but can you use a RUU with a locked boot loader and s-on? i cant even get the phone to respond to "fastboot oem get_identifier_token". I've been all over htc1guru but its abit beyond me, does fastboot flash work on a locked bootloader?
Click to expand...
Click to collapse
When S-ON, a ruu must be flashed with a locked bootloader, thats the only way Only S-OFF phones can flash a ruu with an unlocked bootloader.
Happyhog11 said:
This seems to be a pretty bad catch 22, i cant fix the issue, because the issue stops me from doing anything. Any alternate ways around this guys???
Click to expand...
Click to collapse
Can your phone at least reboot in RUU mode (Black screen with silver HTC logo)?
Code:
fastboot oem rebootRUU
Can you post the outputs of
Code:
fastboot oem last_dmesg
and
Code:
fastboot oem dmesg

alray said:
When S-ON, a ruu must be flashed with a locked bootloader, thats the only way Only S-OFF phones can flash a ruu with an unlocked bootloader.
Can your phone at least reboot in RUU mode (Black screen with silver HTC logo)?
Code:
fastboot oem rebootRUU
Can you post the outputs of
Code:
fastboot oem last_dmesg
and
Code:
fastboot oem dmesg
Click to expand...
Click to collapse
None of those commands work all i get is "< waiting for devices >". It is connecting to my pc i hear the noise of a device connecting plus "fastboot version" comes up with "htc_fastboot version 2.0.1", seems to be any oem commands wont work???

Also i was just playing around with the encryption page and can get access to the phones settings so i turned on usb debugging, some of the stuff in settings does not seem to work correctly and it crashes occasional but i thought this info might be useful....?

Happyhog11 said:
None of those commands work all i get is "< waiting for devices >"
Click to expand...
Click to collapse
Is your phone booted in bootloader mode with "fastboot usb" highlighted in red?

alray said:
Is your phone booted in bootloader mode with "fastboot usb" highlighted in red?
Click to expand...
Click to collapse
yep, some commands it just seems to hang on, comes up with ***Locked*** in purple, then a heap of info in green then below that FASTBOOT USB in red............