Database Develop

SOLVED phone stock on boot htc screen , cant flash ruu

hi
after having problems with ICS i wanted to go back to an original rom.
after downloading and running the ruu.exe my phone gets stuck on the white startup screen with the green HTC logo.
when going into recovery mode (hboot) i can go into recovery or usb mode.
choosing the usb mode should be able to do the ruu.exe again (prob did use the wrong version) only problem in here is the state of the battery -it's less the 30%- therefore it's not possible to run the ruu.exe.
and the alternative bootloader is not reachable/gone so i can't install a custom rom (zip.file)
been looking around overhere but cant seem to find the sollution how to fix this.
any help would be appreciated verry much.

theflyingdutchman said:
hi
after having problems with ICS i wanted to go back to an original rom.
after downloading and running the ruu.exe my phone gets stuck on the white startup screen with the green HTC logo.
when going into recovery mode (hboot) i can go into recovery or usb mode.
choosing the usb mode should be able to do the ruu.exe again (prob did use the wrong version) only problem in here is the state of the battery -it's less the 30%- therefore it's not possible to run the ruu.exe.
and the alternative bootloader is not reachable/gone so i can't install a custom rom (zip.file)
been looking around overhere but cant seem to find the sollution how to fix this.
any help would be appreciated verry much.
Click to expand...
Click to collapse
If you have adb/fastboot installed, open cmd window and type the following with your phone in fastboot mode
Code:
fastboot getvar all
post the output here not including imei and serial.

Nonverbose said:
If you have adb/fastboot installed, open cmd window and type the following with your phone in fastboot mode
Code:
fastboot getvar all
post the output here not including imei and serial.
Click to expand...
Click to collapse
In addition to this information, which HBOOT do you currently have installed?

tpbklake said:
In addition to this information, which HBOOT do you currently have installed?
Click to expand...
Click to collapse
after a hard-disk crash i first need to find drivers so the phone will be seen thru usb by the computer.

tpbklake said:
In addition to this information, which HBOOT do you currently have installed?
Click to expand...
Click to collapse
right now i still have the prob i can't find the drivers to connect the phone to the computer.
when i boot the phone with the volume key down i get the following information.
Revolutionary
VIVO PVT SHIP S-OFF RL
HBOOT -6.13.1002
RADIO-3822.10.08.28_M
eMME-BOOT
Apr 1 2011.18:34:39
HBOOT
<vol up> to previous item
<vol down> to next item
<power> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC
no matter what option i choose nothing will happen.
going for recovery phone freezes
going for factory reset phone will reboot and stucks on a white screen with HTC letters on it.
going for hboot usb nothing will happen since i dont have teh correct drivers to connect the phone in usb mode
(lost the correct drivers after a hard disk crash haven't found them yet)

Try this thread for drivers http://forum.xda-developers.com/showthread.php?t=1161769

Nonverbose said:
Try this thread for drivers http://forum.xda-developers.com/showthread.php?t=1161769
Click to expand...
Click to collapse
with the diver found here and the RUU i allready did download my phone is back to life thx for the tips/support

[Q] stuck on boot no usb connection to computer

** update **
just got usb working i think.
meaning when looking in the device list on my computer i got a "android phone - android bootloader interface"
but i dont see it in the explorer as a drive or something, so i am not quite sure if it's reachable by now or not.
** extra info
only got the original hboot so i can't choose a zip from the sd card to re-flash
hi
during a system update i had a power break down. no i got the problem my phone wont boot.
The phone is also not connectable thru usb (computer won't recognize the phone)
is there any way to solve this problem?
when i connect the phone to the usb port it starts searching for it but i get the error (unknown device and the driver won't be installed)
when i turn on the phone with volume down + power i get into the hboot screen with the next info.
vivo pvt ship s-off rl
hboot-6.13. 1002
radio- 3822. 10.08.28_m
emmc-boot
the factory reset doesn't work
going to hboot usb also does nothing.
any tips/help and advice is apriciated

theflyingdutchman said:
** update **
just got usb working i think.
meaning when looking in the device list on my computer i got a "android phone - android bootloader interface"
but i dont see it in the explorer as a drive or something, so i am not quite sure if it's reachable by now or not.
** extra info
only got the original hboot so i can't choose a zip from the sd card to re-flash
hi
during a system update i had a power break down. no i got the problem my phone wont boot.
The phone is also not connectable thru usb (computer won't recognize the phone)
is there any way to solve this problem?
when i connect the phone to the usb port it starts searching for it but i get the error (unknown device and the driver won't be installed)
when i turn on the phone with volume down + power i get into the hboot screen with the next info.
vivo pvt ship s-off rl
hboot-6.13. 1002
radio- 3822. 10.08.28_m
emmc-boot
the factory reset doesn't work
going to hboot usb also does nothing.
any tips/help and advice is apriciated
Click to expand...
Click to collapse
i did find a way to connect the phone to the computer (it is visable as a HTC in device manager list)
but still not reachable thru explorer
At this point it does only connect to the computer when booting in HBOOT (hboot usb)
are there any options to use it as a drive or something while booting in HBOOT since the phone won't be seen by the computer when i power up normally

theflyingdutchman said:
** update **
just got usb working i think.
meaning when looking in the device list on my computer i got a "android phone - android bootloader interface"
but i dont see it in the explorer as a drive or something, so i am not quite sure if it's reachable by now or not.
** extra info
only got the original hboot so i can't choose a zip from the sd card to re-flash
hi
during a system update i had a power break down. no i got the problem my phone wont boot.
The phone is also not connectable thru usb (computer won't recognize the phone)
is there any way to solve this problem?
when i connect the phone to the usb port it starts searching for it but i get the error (unknown device and the driver won't be installed)
when i turn on the phone with volume down + power i get into the hboot screen with the next info.
vivo pvt ship s-off rl
hboot-6.13. 1002
radio- 3822. 10.08.28_m
emmc-boot
the factory reset doesn't work
going to hboot usb also does nothing.
any tips/help and advice is apriciated
Click to expand...
Click to collapse
Can you enter recovery?
Doing any kind of system update is generally unadvisable on an s-off device. You may have mentioned this at some point but I missed it: By not booting, do you mean bootloop? What Rom did you have installed?

Nonverbose said:
Can you enter recovery?
Doing any kind of system update is generally unadvisable on an s-off device. You may have mentioned this at some point but I missed it: By not booting, do you mean bootloop? What Rom did you have installed?
Click to expand...
Click to collapse
i used to have a cynogen mod rom with an bootloader being able to flash zip files from the sd card (dont know wich one anymore)
after wanting back the stock rom i did a downgrade from cynogen to the stock rom with the original hboot ( so basicly factory settings)
When turn on the phone and go into HBOOT i can do a recovery or a factory reset and go into usb boot mode.
both the recovery and the restore option don't work, after a while the phone does reset and get stuck at a white screen with green HTCC letters THATS IT.
going into HBOOT usb mode the phone is found as a HTC device in the device manager but not shown in the explorer so still not reachable

I think you're still far away from having enough knowledge to even explain what problem you have, cause you obviously don't know the meaning and difference between bootloader and recovery.
You need to find some good noob tutorial and learn how it all works and how all should be done.

theflyingdutchman said:
i used to have a cynogen mod rom with an bootloader being able to flash zip files from the sd card (dont know wich one anymore)
after wanting back the stock rom i did a downgrade from cynogen to the stock rom with the original hboot ( so basicly factory settings)
When turn on the phone and go into HBOOT i can do a recovery or a factory reset and go into usb boot mode.
both the recovery and the restore option don't work, after a while the phone does reset and get stuck at a white screen with green HTCC letters THATS IT.
going into HBOOT usb mode the phone is found as a HTC device in the device manager but not shown in the explorer so still not reachable
Click to expand...
Click to collapse
Does the pc recognize the phone in fastboot mode?

Nonverbose said:
Does the pc recognize the phone in fastboot mode?
Click to expand...
Click to collapse
it is in the recognized as a "android phone - HTC "recognized in the device mannager BUT not shown in the explorer
ps after a re-install this weekend the phone won't be recognized and have to get that fixed again.

theflyingdutchman said:
it is in the recognized as a "android phone - HTC "recognized in the device mannager BUT not shown in the explorer
ps after a re-install this weekend the phone won't be recognized and have to get that fixed again.
Click to expand...
Click to collapse
When you get set up, post the output of the command
Code:
fastboot getvar all
remove info like imei and serial number before posting.

Just connect your phone in fastboot mode, check if you have HTC Sync and if drivers are installed. If drivers are not installed (and you have exclamation mark over it in Device Manager) choose to update driver and lead it to folder HTC in Program Files, there you have 2 different folders with drivers try both of them.
After that command prompt should see your phone in fastboot mode with
fastboot devices
Command.
Then simply flash recovery from fastboot
fastboot flash recovery c:\'path to your recovery'
Recovery can be obtained on RomManager site. After that just restore some of your backups or flash a clean new rom.
If that doesn't work, and shoud work, you can always run newest stocks ICS.
And one more question, how do you think to get your phone connected in storage mode (so you can see it in explorer) when you can't boot it up or boot to recovery???

nlooooo said:
I think you're still far away from having enough knowledge to even explain what problem you have, cause you obviously don't know the meaning and difference between bootloader and recovery.
You need to find some good noob tutorial and learn how it all works and how all should be done.
Click to expand...
Click to collapse
i sure do know

theflyingdutchman said:
i sure do know the difference between those 2 its prob more a lack of my english
btw what makes you think i don't know the difference between those 2?
Click to expand...
Click to collapse
Try to read my second post and don't be a dush.

Nonverbose said:
When you get set up, post the output of the command
Code:
fastboot getvar all
remove info like imei and serial number before posting.
Click to expand...
Click to collapse
ok this might sound stupid.
do you mean in a dos box within windows?
if i open a dos box ( cmd ) and type this commando i get an error like this is not recognized as an internal or external command
since the phone is only in the device mannager list i still have no option to get connected with it (thru explorer or something like that)

theflyingdutchman said:
ok this might sound stupid.
do you mean in a dos box within windows?
if i open a dos box ( cmd ) and type this commando i get an error like this is not recognized as an internal or external command
since the phone is only in the device mannager list i still have no option to get connected with it (thru explorer or something like that)
Click to expand...
Click to collapse
First, you don't wanna read and you want help, so why are we typing.
Second, for fastboot commands you nead ADB installed or at least fastboot.exe, and you have to lead command prompt to location of ADB tools.
And, at the end, to get phone recognized as a storage (or how you say a drive) YOUR PHONE HAS TO BE BOOTED AND CONNECTED TO PC AS A STORAGE DEVICE OR BOOTED TO A WORKING RECOVERY AND MOUNTED AS STORAGE DEVICE.
I still think that you need to read some tutorial about Android functioning, ADB, phone working mods and partitions and how to handle them. Also, for difference, try to read what we are typing...

1. Ensure you have installed the drivers for your phone model.
2. Search the forums on 'fastboot' (it is obvious you are not setting/using it correctly if you get that error - I know I did )
3. SDCard will only be seen by PC once Android system is booted up or HBOOT is loaded correctly then it can be accessed through HBOOT using fastboot - it will NOT show up as an external drive on the PC in it's current state.
4. Small steps, if you know roughly which rom you had installed I would use that to recover your phone from, starting with HBOOT then RECOVERY one at a time, to know what and how takes reading up in the forums for your phone and rom.
Sent from my Acer E320-orange using xda app-developers app

theflyingdutchman said:
ok this might sound stupid.
do you mean in a dos box within windows?
if i open a dos box ( cmd ) and type this commando i get an error like this is not recognized as an internal or external command
since the phone is only in the device mannager list i still have no option to get connected with it (thru explorer or something like that)
Click to expand...
Click to collapse
Yes I did mean a cmd window. As stated previously, you need fastboot and adb installed. If you use my downgrade script (link in Sig) and unzip it, it contains the correct files. You need your drivers installed though (install and uninstall HTCsync) and you need to cd to the files directory.

Nonverbose said:
When you get set up, post the output of the command
Code:
fastboot getvar all
remove info like imei and serial number before posting.
Click to expand...
Click to collapse
below are the results of the getvar all command.
<bootloader> version 2.5
<bootloader> version-bootloader: 6.13.1022
<bootloader> version-baseband: 3822.12.03.28_m
<bootloader> version-cpl: none
<bootloader> version-nicrop: none
<bootloader> version-nain: none
<bootloader> serialno
<bootloader> imei
<bootloader> product: vivo
<bootloader> platform: HBOOT-7630
<bootloader> modelid: FG3213200
<bootloader> cidnun: HTC_E11
<bootloader> battery-status: good
<bootloader> battery-voltage: 4179mV
<bootloader> partition-layout: Generic
<bootloader> security: off
<bootloader> build-mode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> conmitno-bootloader: dirty-8a731c5e
<bootloader> hbootpreupdate: 12
<bootloader> gencheckpt: 0

did follow these steps clockword mod recovery http://www.androidauthority.com/one-x-clockworkmod-touch-recovery-76853/
but i get the error con't load imagename.img

nlooooo said:
Just connect your phone in fastboot mode, check if you have HTC Sync and if drivers are installed. If drivers are not installed (and you have exclamation mark over it in Device Manager) choose to update driver and lead it to folder HTC in Program Files, there you have 2 different folders with drivers try both of them.
After that command prompt should see your phone in fastboot mode with
fastboot devices
Command.
Then simply flash recovery from fastboot
fastboot flash recovery c:\'path to your recovery'
Recovery can be obtained on RomManager site. After that just restore some of your backups or flash a clean new rom.
If that doesn't work, and shoud work, you can always run newest stocks ICS.
And one more question, how do you think to get your phone connected in storage mode (so you can see it in explorer) when you can't boot it up or boot to recovery???
Click to expand...
Click to collapse
drives might still be the problem.
there are no exclamation marks in the device manager. in the device manages i got a "Android usb device - My HTC" but adb wont show up any connected device.
checked thru "adb devices" there are no connected devices shown

Reboot to fastboot and type
fastboot devices
Not adb devices, abd commands can be used from recovery or a booted device. Try to google something about fastboot commands, you will find a lot of it.

If it's like my phone there may not be any output for 'devices' after executing the devices command with fastboot you get a blank return and your command prompt back in the command window.
Other commands can be sent regardless of an actual 'devices' returned name, at least that is what I get, with your phones problem atm the same may apply.
Sent from my Acer E320-orange using xda app-developers app

Not recognized on computer...

ok let me say first, that I am new to XDA-Developer and I am unsure of where to put this so i put this in the Incredible S General. And i have a problem at hand...... When i boot into bootloader and press fastboot (cuz i just installed cyanvivox and i needed fastboot flash it), it says just fastboot. not fastboot USB even though its connnected to the computer. I tried wiggling the USB in its socket, i tried different USB ports, i unplugged, plugged it back in. I wiped my phone (wipe data, cache partition, dalvik cache) in CWM. But no matter what i do, it still says Fastboot
!!!!!!!!!!
If it helps my bootloader screen says
***Unlocked***
VIVO PVT SHIP S-ON RL
HBOOT-2.03.000
Radio- 3831.19.00.19_M
eMMC-boot
Aug 28, 2012, 16 :41 :33
Any help appreciated!!!!

Change of situation
Sorry I forgot to add that i can mysteriously boot into my ROM................
However when i go into bootloader and press fastboot, it still odesnt say fastboot USB

Have you installed all the drivers for the device and fastboot?

markj338 said:
Have you installed all the drivers for the device and fastboot?
Click to expand...
Click to collapse
Yep i did a reinstall of HTC Sync, reboot my comp and i jacked my brother's cable. it seems to be working now. Thanks for taking your time to look at this thread tho. :victory:

072665995 said:
Yep i did a reinstall of HTC Sync, reboot my comp and i jacked my brother's cable. it seems to be working now. Thanks for taking your time to look at this thread tho. :victory:
Click to expand...
Click to collapse
np mate

[Q] [Help] Bootloop, No Recovery Access, Fastboot/adb Stuck On "Waiting For Device"

[Q] [Help] Bootloop, No Recovery Access, Fastboot/adb Stuck On "Waiting For Device"
ok so dumb me decided to flash a ROM that requires s-off while having s-on. After this my phone rebooted but got stuck on the logo so i held power+volume down to get to the bootloader, when i click recovery i see the CWM splash screen then it crashes and gets stuck in the boot again. I took to trying to reinstall CWM so i downloaded all the fastboot adb stuff but in the command prompt when i type "fastboot devices" nothing shows up so when i try to flash the recovery it says it can't find my phone. I am pretty sure im connected because it says "Fastboot USB" on my phone. I have downloaded HTC Sync to get the correct drivers. On my phone it says fastboot usb but no signs of connection show on my computer (I have tried on 2 different computers running windows 7 and 8)

mikesantoni said:
ok so dumb me decided to flash a ROM that requires s-off while having s-on. After this my phone rebooted but got stuck on the logo so i held power+volume down to get to the bootloader, when i click recovery i see the CWM splash screen then it crashes and gets stuck in the boot again. I took to trying to reinstall CWM so i downloaded all the fastboot adb stuff but in the command prompt when i type "fastboot devices" nothing shows up so when i try to flash the recovery it says it can't find my phone. I am pretty sure im connected because it says "Fastboot USB" on my phone. I have downloaded HTC Sync to get the correct drivers. On my phone it says fastboot usb but no signs of connection show on my computer (I have tried on 2 different computers running windows 7 and 8)
Click to expand...
Click to collapse
What rom exactly?
What is your bootloader version?
When your phone is in fastboot usb mode, in windows device manager, how the phone is listed? ''My HTC'' or ''One'' ?
What is the output of ''fastboot devices''?
What is the output of ''adb version''?
What version or CWM recovery are you using?

alray said:
What rom exactly?
What is your bootloader version?
When your phone is in fastboot usb mode, in windows device manager, how the phone is listed? ''My HTC'' or ''One'' ?
What is the output of ''fastboot devices''?
What is the output of ''adb version''?
What version or CWM recovery are you using?
Click to expand...
Click to collapse
1- was on cm11 tried to get to sense 6 arhd
2- not sure how to find this but my bootloader says "M7-UL PVT SHIP S-ON RH HBOOT-1.44.0000 RADIO-4A.14.3250.13 OpenDSP-v26.120.274.0202 eMMC-boot May 3 2013, 19:16:59:-1"
3- nothing shows up
4- blank
5- Andriod Debug Bridge v 1.0.31
6- Dont know for sure because i cant get to it to check, definently not the newest version, updated it around christmas/thanksgiving this year
thanks hope that helps

mikesantoni said:
1- was on cm11 tried to get to sense 6 arhd
2- not sure how to find this but my bootloader says "M7-UL PVT SHIP S-ON RH HBOOT-1.44.0000 RADIO-4A.14.3250.13 OpenDSP-v26.120.274.0202 eMMC-boot May 3 2013, 19:16:59:-1"
3- nothing shows up
4- blank
5- Andriod Debug Bridge v 1.0.31
6- Dont know for sure because i cant get to it to check, definently not the newest version, updated it around christmas/thanksgiving this year
thanks hope that helps
Click to expand...
Click to collapse
You need TWRP 2.6.3.3 or higher to flash ARHD not CWM
hboot 1.44 + Windows 8 = fastboot issue, use windows 7 or a live linux cd (ubuntu 12.04 32 bits)
should say: Android USB devices ---> My HTC, if not then you have drivers issues or connectivity issue because of ''hboot 1.44 + win8''
that confirm what said at #3
at least your adb is up to date
you will need to flash twrp 2.6.3.3+ anyway.
So get your hands on a win 7 PC or use a linux live cd (ubuntu 12.04 32 bit version)
Code:
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader
then enter twrp. hit install and select arhd.zip.

alray said:
You need or higher to flash ARHD not CWM
hboot 1.44 + Windows 8 = fastboot issue, use windows 7 or a live linux cd (ubuntu 12.04 32 bits)
should say: Android USB devices ---> My HTC, if not then you have drivers issues or connectivity issue because of ''hboot 1.44 + win8''
that confirm what said at #3
at least your adb is up to date
you will need to flash twrp 2.6.3.3+ anyway.
So get your hands on a win 7 PC or use a linux live cd (ubuntu 12.04 32 bit version)
Code:
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader
then enter twrp. hit install and select arhd.zip.
Click to expand...
Click to collapse
have a windows 7 pc, tried it on there still nothing, to get drivers what excactly do i do, all i did was install htc sync and then tried and nothing

mikesantoni said:
have a windows 7 pc, tried it on there still nothing, to get drivers what excactly do i do, all i did was install htc sync and then tried and nothing
Click to expand...
Click to collapse
Connect to windows 7 and post a screenshot of your device manager

SaHiLzZ said:
Connect to windows 7 and post a screenshot of your device manager
Click to expand...
Click to collapse
gyazo com/e2ac0081147eb07e8b53a57d79aaea00 there i fit my device manager and my command prompt in the shot, add the period after gyazo, cant post links yet

alray said:
You need or higher to flash ARHD not CWM
hboot 1.44 + Windows 8 = fastboot issue, use windows 7 or a live linux cd (ubuntu 12.04 32 bits)
should say: Android USB devices ---> My HTC, if not then you have drivers issues or connectivity issue because of ''hboot 1.44 + win8''
that confirm what said at #3
at least your adb is up to date
you will need to flash twrp 2.6.3.3+ anyway.
So get your hands on a win 7 PC or use a linux live cd (ubuntu 12.04 32 bit version)
Code:
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader
then enter twrp. hit install and select arhd.zip.
Click to expand...
Click to collapse
Was able to flash twrp but still nothing when I giro recovery now I see the twrp splash screen but it still crashes please help

mikesantoni said:
gyazo com/e2ac0081147eb07e8b53a57d79aaea00 there i fit my device manager and my command prompt in the shot, add the period after gyazo, cant post links yet
Click to expand...
Click to collapse
well from this screenshot I can see 2 things,
you did not took a screenshot of your device manager but a screenshot of your computer drives, and this is useless
despite what I said above, you are still trying to flash CWM recovery instead of TWRP....
---------- Post added at 11:37 AM ---------- Previous post was at 11:36 AM ----------
mikesantoni said:
Was able to flash twrp but still nothing when I giro recovery now I see the twrp splash screen but it still crashes please help
Click to expand...
Click to collapse
have you flashed the right version of twrp for your phone
and cleared cache after?

Device not detected in fastboot, adb or any kind of usb connection

Can't get my phone to be detected in fastboot or adb or anything at all.
I have TWRP 2.7.1.1 installed and I have been trying to get it to connect to the PC. This has happened before and I somehow got it to work again. This has probably something to do with fast charge or something.
Anyone has any ideas to this and is there a way to upgrade the firmware of my device without fastboot? The OS - Line in my fastboot is blank also.
Tried over 4 different cables, no difference.
Using both Windows and OS X.
Both see nothing in either adb or fastboot.
I had USB Fast Charge enabled but I've since tried to flash other ROMs to see if that would solve the problem but it doesn't.
If I remember correctly, the only way to solve the problem was to flash a full default RUU over. I can't do it because fastboot usb isn't even detecting my phone
I was running GPE 4.4.4 with Elemental X 15.1 Kernel.

I'm having a similar issue with my wife's m7. I've previously rooted and s-off'd her m7. I can connect to it via adb and maintain a stable adb shell connection . Rebooting via adb reboot-bootloader or vol down+power and choosing fastboot, I'm unable to see the device under fastboot. fastboot devices returns nothing. fastboot reboot-bootloader returns < waiting for devices >. When fastboot connects via USB, I get a "USB Device Not Recognized" bubble from Windows 7. I've used device manager to uninstall the driver, but it returns on next connection as "Unknown Device". She's on stock 4.3.
Meanwhile, fastboot devices plugged into my old m7 returns a device ID and fastboot reboot-bootloader proceeds immediately. I know that I've got the drivers installed correctly because I have no trouble connecting my old m7 via adb or fastboot, nor my m8.
What in the world could be causing the first m7 to identify incorrectly to Windows as an unknown device when the second identifies as an Android USB device? I've installed and reinstalled drivers a dozen times before testing the second m7 and everything working flawlessly - updated Windows 7 as well after reading a topic regarding Windows 8.1 fastboot issues, just to be safe. Still nothing. In the course of writing this post, I was able to connect via adb while in recovery with no issues. I did a factory reset from recovery and still have no fastboot connection.
Code:
Wife's m7 (no fastboot):
CWM Recovery v6.0.4.3
Android Version 4.3
Sense 5.0
Software number 2.10.605.1 CL278010 release-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.54.0000
RADIO-1.12.42.1104
OpenDSP-v31.120.274.0617
OS-1.10.605.15
eMMC-boot 2048mb
NOV 8 2013
Code:
My m7 (all working):
TWRP v2.8.0.2
Android Version 4.4.4
CM 11-20141112-SNAPSHOT-M12-m7vzw
Build number cm_m7vzw-userdebug 4.4.4 KTU84Q 8708283ec1 test-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.56.0000
RADIO-1.13.41.1109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048mb
Jan 20 2014
---------- Post added at 02:54 PM ---------- Previous post was at 02:44 PM ----------
Using basic troubleshooting skills that I thought I'd ruled out by getting both the m8 and other m7 to work fine, I swapped cables and ports. The original cable (an official HTC cable, possibly from my HTC Incredible) in the two test ports failed. A Nexus 7 2012 cable in both ports works fine. If I don't survive the project I'm working on right now, let it be known that Google killed me.

Tilgare said:
I'm having a similar issue with my wife's m7. I've previously rooted and s-off'd her m7. I can connect to it via adb and maintain a stable adb shell connection . Rebooting via adb reboot-bootloader or vol down+power and choosing fastboot, I'm unable to see the device under fastboot. fastboot devices returns nothing. fastboot reboot-bootloader returns < waiting for devices >. When fastboot connects via USB, I get a "USB Device Not Recognized" bubble from Windows 7. I've used device manager to uninstall the driver, but it returns on next connection as "Unknown Device". She's on stock 4.3.
Meanwhile, fastboot devices plugged into my old m7 returns a device ID and fastboot reboot-bootloader proceeds immediately. I know that I've got the drivers installed correctly because I have no trouble connecting my old m7 via adb or fastboot, nor my m8.
What in the world could be causing the first m7 to identify incorrectly to Windows as an unknown device when the second identifies as an Android USB device? I've installed and reinstalled drivers a dozen times before testing the second m7 and everything working flawlessly - updated Windows 7 as well after reading a topic regarding Windows 8.1 fastboot issues, just to be safe. Still nothing. In the course of writing this post, I was able to connect via adb while in recovery with no issues. I did a factory reset from recovery and still have no fastboot connection.
Code:
Wife's m7 (no fastboot):
CWM Recovery v6.0.4.3
Android Version 4.3
Sense 5.0
Software number 2.10.605.1 CL278010 release-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.54.0000
RADIO-1.12.42.1104
OpenDSP-v31.120.274.0617
OS-1.10.605.15
eMMC-boot 2048mb
NOV 8 2013
Code:
My m7 (all working):
TWRP v2.8.0.2
Android Version 4.4.4
CM 11-20141112-SNAPSHOT-M12-m7vzw
Build number cm_m7vzw-userdebug 4.4.4 KTU84Q 8708283ec1 test-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.56.0000
RADIO-1.13.41.1109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048mb
Jan 20 2014
---------- Post added at 02:54 PM ---------- Previous post was at 02:44 PM ----------
Using basic troubleshooting skills that I thought I'd ruled out by getting both the m8 and other m7 to work fine, I swapped cables and ports. The original cable (an official HTC cable, possibly from my HTC Incredible) in the two test ports failed. A Nexus 7 2012 cable in both ports works fine. If I don't survive the project I'm working on right now, let it be known that Google killed me.
Click to expand...
Click to collapse
I love the design of this phone but I've had more problems than i can count. So frustrated with this. I had a working device but since adb nor fastboot was working, I made a mistake and I wiped the internal system. Now i have no operating system on the phone. Essentially all i have on it now is the GPE firmware + TWRP Recovery. I still can't get a ROM on it because I can't transfer any files into the internal storage and adb nor fastboot is working. USB OTG seems to give some response in TWRP Terminal Emuatlor when I do "lsusb" but I still can't mount it.

ZaneChua said:
I love the design of this phone but I've had more problems than i can count. So frustrated with this. I had a working device but since adb nor fastboot was working, I made a mistake and I wiped the internal system. Now i have no operating system on the phone. Essentially all i have on it now is the GPE firmware + TWRP Recovery. I still can't get a ROM on it because I can't transfer any files into the internal storage and adb nor fastboot is working. USB OTG seems to give some response in TWRP Terminal Emuatlor when I do "lsusb" but I still can't mount it.
Click to expand...
Click to collapse
don't try and mount the usb-otg just boot into twrp and choose install / tap where it says Internel Storage xxxxxxmb / this will drop down and you can choose USB-OTG. now install your rom

clsA said:
don't try and mount the usb-otg just boot into twrp and choose install / tap where it says Internel Storage xxxxxxmb / this will drop down and you can choose USB-OTG. now install your rom
Click to expand...
Click to collapse
That was obviously the first thing to do. But USB-OTG is still showing me 0MB. So hence why I said i was trying to mount it. By i say mount it, it's not clicking mount in twrp. It's mounting via command line.
I've formatted the USB to NTFS, exFat and FAT32. Neither filesystem seems to be able to mount. But the OTG is clearly detected.

Tilgare said:
I'm having a similar issue with my wife's m7. I've previously rooted and s-off'd her m7. I can connect to it via adb and maintain a stable adb shell connection . Rebooting via adb reboot-bootloader or vol down+power and choosing fastboot, I'm unable to see the device under fastboot. fastboot devices returns nothing. fastboot reboot-bootloader returns < waiting for devices >. When fastboot connects via USB, I get a "USB Device Not Recognized" bubble from Windows 7. I've used device manager to uninstall the driver, but it returns on next connection as "Unknown Device". She's on stock 4.3.
Meanwhile, fastboot devices plugged into my old m7 returns a device ID and fastboot reboot-bootloader proceeds immediately. I know that I've got the drivers installed correctly because I have no trouble connecting my old m7 via adb or fastboot, nor my m8.
What in the world could be causing the first m7 to identify incorrectly to Windows as an unknown device when the second identifies as an Android USB device? I've installed and reinstalled drivers a dozen times before testing the second m7 and everything working flawlessly - updated Windows 7 as well after reading a topic regarding Windows 8.1 fastboot issues, just to be safe. Still nothing. In the course of writing this post, I was able to connect via adb while in recovery with no issues. I did a factory reset from recovery and still have no fastboot connection.
Code:
Wife's m7 (no fastboot):
CWM Recovery v6.0.4.3
Android Version 4.3
Sense 5.0
Software number 2.10.605.1 CL278010 release-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.54.0000
RADIO-1.12.42.1104
OpenDSP-v31.120.274.0617
OS-1.10.605.15
eMMC-boot 2048mb
NOV 8 2013
Code:
My m7 (all working):
TWRP v2.8.0.2
Android Version 4.4.4
CM 11-20141112-SNAPSHOT-M12-m7vzw
Build number cm_m7vzw-userdebug 4.4.4 KTU84Q 8708283ec1 test-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.56.0000
RADIO-1.13.41.1109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048mb
Jan 20 2014
---------- Post added at 02:54 PM ---------- Previous post was at 02:44 PM ----------
Using basic troubleshooting skills that I thought I'd ruled out by getting both the m8 and other m7 to work fine, I swapped cables and ports. The original cable (an official HTC cable, possibly from my HTC Incredible) in the two test ports failed. A Nexus 7 2012 cable in both ports works fine. If I don't survive the project I'm working on right now, let it be known that Google killed me.
Click to expand...
Click to collapse
I just realised something abouit your wife's m7. The hboot 1.54 has always had issues with fastboot in Windows 8.1. I have never gotten it working on Windows 8.

ZaneChua said:
I just realised something abouit your wife's m7. The hboot 1.54 has always had issues with fastboot in Windows 8.1. I have never gotten it working on Windows 8.
Click to expand...
Click to collapse
Interesting. I wonder if that somehow was related to my problem. Now that I've updated the hboot, I wonder if I'd have the same issues connecting with my usual USB cable or in particular USB ports. Might have to test if I can nab her phone from her - she's really digging her new Lollipop install.

Tilgare said:
Interesting. I wonder if that somehow was related to my problem. Now that I've updated the hboot, I wonder if I'd have the same issues connecting with my usual USB cable or in particular USB ports. Might have to test if I can nab her phone from her - she's really digging her new Lollipop install.
Click to expand...
Click to collapse
Your problem isn't as serious as mine. lol. Try having a phone which doesn't detect at all through device manager or anything.

Can you update or change the hboot without using usb-fastboot? I have 1.54 and its giving me the same issue with not detecting on Windows 8

det0ur said:
Can you update or change the hboot without using usb-fastboot? I have 1.54 and its giving me the same issue with not detecting on Windows 8
Click to expand...
Click to collapse
You don't have usb fastboot working?

Have you tried to completely uninstall the drivers in your computer and then reinstall them? I've had that work on more than one occasion...
Go to control panel/system, and where it says your windows rating or whatever, look up in the top left corner for device manager. You can completely uninstall the drivers from there.
On Windows 8,you may even be able to type "device manager" into that stupid little search thing in the start screen. Or download classic shell from the site that pops up in Google and get a real live start menu back...
Hope it helps. Seems like a driver issue more than a phone issue to me.

ATDavis said:
Have you tried to completely uninstall the drivers in your computer and then reinstall them? I've had that work on more than one occasion...
Go to control panel/system, and where it says your windows rating or whatever, look up in the top left corner for device manager. You can completely uninstall the drivers from there.
On Windows 8,you may even be able to type "device manager" into that stupid little search thing in the start screen. Or download classic shell from the site that pops up in Google and get a real live start menu back...
Hope it helps. Seems like a driver issue more than a phone issue to me.
Click to expand...
Click to collapse
Definitely not a driver issue. It's a phone issue. OTG doesn't even work. Device Manager doesn't even detect my phone or any kind of USB device when i attach my phone.

ZaneChua said:
You don't have usb fastboot working?
Click to expand...
Click to collapse
Nope. It doesn't work.

I fixed this problem with installing Kies.

Tobirexy said:
I fixed this problem with installing Kies.
Click to expand...
Click to collapse
What has Kies have to do with the HTC One? Isn't Kies for Samsung only phones? I don't believe HTC phones have an ODIN download mode.

Sorry that was the wrong post.

So for anyone who wanted to know what was wrong, it was definitely the usb port. I replaced it and now it works fine.