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] Htc One Bricked? Not sure...[SOLVED]

Not sure what had gone wrong... I believe the phone may be bricked. I rooted the device and sometime after I attempted to unroot it. Several attempts later with guides from here, htcguru, and many RUU's later it still does not work. It has reached the point where it no longer boots to any sort of rom, rather it will only boot into TRWP's recovery system. previously it would boot to an old rom that was loaded onto it with twrp from htc guru's website. it did nto have any touch compatibility and only the volume and power buttons would work.
I now also cannot access the phone from a computer, the PC (windows) recognizes it in the device manager, but it doesn't show up in windows explorer (maybe because it wont boot anything but the twrp recovery?)
No RUU's can fix it apparently, they will only say they either cannot connect to the phone, or an unknown error occurs and it simply cannot update the phone.
I've tried All-in-one kit, nothing seems to work. I am really at a loss, I spent 14 hours straight trying to unroot it, only progressively making it worse. I also could not get it to accept a mouse input from an otg cable whilst in the no touch input rom, don't know why..
Is this phone now inevitably ****ed beyond repair? I have pretty much given up all hope, I think the last time I asked for help with anything computer related was well over 3 years ago. I finally met my match in the hack and crack world, I read a lot of pages and guides, watched alot of videos, and even the HTC Dev site had me convinced this would be simple, easy, and painless work. Boy was I fooled.
I don't even know where to look anymore for answers, any I have no idea what information to give you guys, please excuse my apparent utter noobness and help me, I will provide as much information as I can, if I can.
Thanks in advance.

zoline411 said:
Not sure what had gone wrong... I believe the phone may be bricked. I rooted the device and sometime after I attempted to unroot it. Several attempts later with guides from here, htcguru, and many RUU's later it still does not work. It has reached the point where it no longer boots to any sort of rom, rather it will only boot into TRWP's recovery system. previously it would boot to an old rom that was loaded onto it with twrp from htc guru's website. it did nto have any touch compatibility and only the volume and power buttons would work.
I now also cannot access the phone from a computer, the PC (windows) recognizes it in the device manager, but it doesn't show up in windows explorer (maybe because it wont boot anything but the twrp recovery?)
No RUU's can fix it apparently, they will only say they either cannot connect to the phone, or an unknown error occurs and it simply cannot update the phone.
I've tried All-in-one kit, nothing seems to work. I am really at a loss, I spent 14 hours straight trying to unroot it, only progressively making it worse. I also could not get it to accept a mouse input from an otg cable whilst in the no touch input rom, don't know why..
Is this phone now inevitably ****ed beyond repair? I have pretty much given up all hope, I think the last time I asked for help with anything computer related was well over 3 years ago. I finally met my match in the hack and crack world, I read a lot of pages and guides, watched alot of videos, and even the HTC Dev site had me convinced this would be simple, easy, and painless work. Boy was I fooled.
I don't even know where to look anymore for answers, any I have no idea what information to give you guys, please excuse my apparent utter noobness and help me, I will provide as much information as I can, if I can.
Thanks in advance.
Click to expand...
Click to collapse
post the output of ''fastboot getvar all'' except the IMEI and SERIALNO
btw forget toolkits and work drirectly from your cmd prompt.
and post links of the ruu you tried to flash
what twrp version do you have?

14 hours.. You are stubborn! Better hope the device is recognized in fastboot as asked above
sent from my mobile device

Requested info
alray said:
post the output of ''fastboot getvar all'' except the IMEI and SERIALNO
btw forget toolkits and work drirectly from your cmd prompt.
and post links of the ruu you tried to flash
what twrp version do you have?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3834mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
RUU 1
http://d-h.st/4VH
found at http://forum.xda-developers.com/showthread.php?t=2427328
RUU 2
http://dl3.htc.com/application/RUU_...10.38m.1157.04_release_336982_signed_2(2).exe
found at http://forum.xda-developers.com/showthread.php?t=2496074
I am using TWRP v2.6.0.1 So far that is the only thing bootable to, the computer will recognize the phone, so will fastboot, however it seems impossible to drop files onto the phone. Anything will be helpful right now, even if it wipes it clean (only wiped it clean about 70 times over the last 24 hours anyway...)
SaHiLzZ said:
14 hours.. You are stubborn! Better hope the device is recognized in fastboot as asked above
sent from my mobile device
Click to expand...
Click to collapse
Stubborn is one of my middle names, along with 'determined' and 'accident prone'
Thank you both for responding, and any others who try to help, again, I normally don't request or even need help, usually I can solve problems after tinkering for 9-12 hours, this time I decided I would ask because I fear I may be a hop, skip, and jump away from owning a $300 paperweight/bonfire-material...
Additionally, I can 'fastboot oem lock' with command prompt, and 'fastboot flash unlocktoken Unlock_code.bin' done both more times than I can count now, and I can't get the t-mobile startup sound out of my head anymore da-da-duh-duh-da-duh...

zoline411 said:
RUU 1
http://d-h.st/4VH
found at http://forum.xda-developers.com/showthread.php?t=2427328
Click to expand...
Click to collapse
This RUU is a downgrade in version and require S-OFF to be flashed
zoline411 said:
RUU 2
http://dl3.htc.com/application/RUU_...10.38m.1157.04_release_336982_signed_2(2).exe
found at http://forum.xda-developers.com/showthread.php?t=2496074
Click to expand...
Click to collapse
This RUU is a downgrade in version and require S-OFF to be flashed
Afaik, there is no ruu for your phone version that can be flashed with S-ON
zoline411 said:
I am using TWRP v2.6.0.1 So far that is the only thing bootable to, the computer will recognize the phone, so will fastboot, however it seems impossible to drop files onto the phone. Anything will be helpful right now, even if it wipes it clean (only wiped it clean about 70 times over the last 24 hours anyway...)
Click to expand...
Click to collapse
TWRP 2.6.0.1 is very outdated. You'll need TWRP 2.6.3.3 to be able to flash 4.4+ roms.
zoline411 said:
Additionally, I can 'fastboot oem lock' with command prompt, and 'fastboot flash unlocktoken Unlock_code.bin' done both more times than I can count now, and I can't get the t-mobile startup sound out of my head anymore da-da-duh-duh-da-duh...
Click to expand...
Click to collapse
Woooh! Don't relock your bootloader! Its only needed to flash a RUU with s-on but there is no available for your phone!
Did you made a nandroid backup of your phone? If yes then restore it. if no, your only solution atm is to flash a custom rom (I personnaly recommend ARHD 53)
Is your bootloader still unlocked? If yes then:
Code:
fastboot flash recovery <twrp2.6.3.3>.img
fastboot erase cache [COLOR="Red"]<------ important[/COLOR]
fastboot reboot-bootloader
Download your custom rom and adb push it or adb sideload it from twrp recovery.

Faint light...
alray said:
This RUU is a downgrade in version and require S-OFF to be flashed
This RUU is a downgrade in version and require S-OFF to be flashed
Afaik, there is no ruu for your phone version that can be flashed with S-ON
TWRP 2.6.0.1 is very outdated. You'll need TWRP 2.6.3.3 to be able to flash 4.4+ roms.
Woooh! Don't relock your bootloader! Its only needed to flash a RUU with s-on but there is no available for your phone!
Did you made a nandroid backup of your phone? If yes then restore it. if no, your only solution atm is to flash a custom rom (I personnaly recommend ARHD 53)
Is your bootloader still unlocked? If yes then:
Code:
fastboot flash recovery <twrp2.6.3.3>.img
fastboot erase cache [COLOR="Red"]<------ important[/COLOR]
fastboot reboot-bootloader
Download your custom rom and adb push it or adb sideload it from twrp recovery.
Click to expand...
Click to collapse
I was getting that feeling after about 8 hours of button pressing, t-mobile jingles, and seemingly endless reading of interwebs, that there wasn't any sort of RUU for my phone, thank god. This means I can stop performing Einstein's definition of insanity...
TWRP v2.6.3.3, right... This should be the correct link for me right? (below) Also the line in command prompt should be "<openrecovery-twrp-2.6.3.3-m7>.img" without quotes, should I decide not to rename it, correct? **EDIT** Will not let me post outside links, the link in this page will take you to techerrata, I used the dl link marked 2.6.3.3, also worth noting there is a 2.7.0.0, should I bother with 2.7? or leave it be.
http://forum.xda-developers.com/showthread.php?t=2173870
Bad thing I locked the bootloader? It's currently unlocked for the hundredth time it seems, under your recommendation I will leave it unlocked. Further under your recommendation, the link below should be the version of ARHD 53 needed for my phone also, correct? **DOUBLE EDIT** No link to the outside world aloud, below there is a link to the android rev blogspot, I picked the first dl under HTC One, KitKat 4.4.2.
http://forum.xda-developers.com/showthread.php?t=2183023
As I believe I mentioned earlier, it appears, at the moment, impossible to transfer files over to the phone via usb, it shows up in device manager, but not in windows explorer under "My Computer." If you have an idea around that that would be fantastic, although not particularly needed, the HTC Sync Manager 'drive' that usually also appears also no longer shows up, however the drivers were loaded into this computer already, but the folder in the fake drive containing drivers was not copied (i iz stupidz.)
Also I don't believe I made the nandroid backup, I don't know why, actually I do, it's because I was an idiot and didn't bother to take the normal precautions.
The whole reason I ever wanted to root the device was for s-off, It only turned into a nightmare, I obviously dont even want to do that (well not right now, I'll have to talk to more intelligent types before attempting it,) so since I cannot figure out how to drag and drop (perhaps a way through command prompt?) the files to the phone, can I get a guide or a link to a guide, and please make it into kind-noob-langauge for me, to use abd to push it (ARHD) to the phone, or use it to transfer it to the phone where I can then use TWRP to flash/sideload/not perfectly sure what sideload is, into place.
Sorry for tl;dr; though, I have a feeling you guys are somewhat used to it.
Thanks greatly, I see the faint light on the other end getting brighter, lets hope I'm in a tunnel and not dying.

zoline411 said:
TWRP v2.6.3.3, right... This should be the correct link for me right? (below) Also the line in command prompt should be "<openrecovery-twrp-2.6.3.3-m7>.img" without quotes, should I decide not to rename it, correct? **EDIT** Will not let me post outside links, the link in this page will take you to techerrata, I used the dl link marked 2.6.3.3, also worth noting there is a 2.7.0.0, should I bother with 2.7? or leave it be.
http://forum.xda-developers.com/showthread.php?t=2173870
Click to expand...
Click to collapse
I'll recommend you to use 2.6.3.3 not 2.7 , there is a minor bug with 2.7 which will prevent the screen to turn off when charging the phone when powered off.
Make sure your recovery file and your rom is in the same folder were abd and fastboot are on your computer.
Boot your phone in bootloader mode, select fastboot then connect usb cable
open a cmd prompt from your adb/fastoot folder (hold shift + right click a blank space in the folder, select ''start a commend prompt here'')
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
zoline411 said:
the link below should be the version of ARHD 53 needed for my phone also, correct? **DOUBLE EDIT** No link to the outside world aloud, below there is a link to the android rev blogspot, I picked the first dl under HTC One, KitKat 4.4.2.
http://forum.xda-developers.com/showthread.php?t=2183023
Click to expand...
Click to collapse
Yes this is the correct rom
zoline411 said:
As I believe I mentioned earlier, it appears, at the moment, impossible to transfer files over to the phone via usb, it shows up in device manager, but not in windows explorer under "My Computer." If you have an idea around that that would be fantastic, although not particularly needed, the HTC Sync Manager 'drive' that usually also appears also no longer shows up, however the drivers were loaded into this computer already, but the folder in the fake drive containing drivers was not copied (i iz stupidz.)
Click to expand...
Click to collapse
You will use ADB to transfer files to your phone when booted in TWRP recovery
boot your phone in twrp 2.6.3.3
go in windows device manager and make sure your device is listed as ''android usb device ---> My HTC''. If yes your good to push to rom. If your phone is listed as ''Other Devices ---> One'' you'll need to follow that guide before:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
PUSH THE ROM
Again make sure the rom is in the adb/fasboot folder
open a command prompt from that folder
boot your phone in TWRP main menu
Code:
adb push ''name_of_rom_file''.zip /sdcard/
then in twrp select ''install'' and browse the sdcard folder to find your rom. Select it and swipe to flash.
after it flashed reboot your phone.
If something is not clear/don't work, ask me here and post screenshot of your command prompt

I'm not Dead.
alray said:
I'll recommend you to use 2.6.3.3 not 2.7 , there is a minor bug with 2.7 which will prevent the screen to turn off when charging the phone when powered off.
Make sure your recovery file and your rom is in the same folder were abd and fastboot are on your computer.
Boot your phone in bootloader mode, select fastboot then connect usb cable
open a cmd prompt from your adb/fastoot folder (hold shift + right click a blank space in the folder, select ''start a commend prompt here'')
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Yes this is the correct rom
You will use ADB to transfer files to your phone when booted in TWRP recovery
boot your phone in twrp 2.6.3.3
go in windows device manager and make sure your device is listed as ''android usb device ---> My HTC''. If yes your good to push to rom. If your phone is listed as ''Other Devices ---> One'' you'll need to follow that guide before:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
PUSH THE ROM
Again make sure the rom is in the adb/fasboot folder
open a command prompt from that folder
boot your phone in TWRP main menu
Code:
adb push ''name_of_rom_file''.zip /sdcard/
then in twrp select ''install'' and browse the sdcard folder to find your rom. Select it and swipe to flash.
after it flashed reboot your phone.
If something is not clear/don't work, ask me here and post screenshot of your command prompt
Click to expand...
Click to collapse
<Farnsworth>
Good news everyone!
</Farnsworth>
It worked! Yay. I greatly thank you from the bottom of my heart. Now it's just as good as it was before, and better. Using the sense toolkit, love it, and more importantly, the phone is actually normal now, double love it.
I really do like the area rom, I installed Xposed, and used it to update to the latest sense toolkit. Everything is wonderful. Stayed away from twrp 2.7, and we'll yeah, it's all good.
How do I give you some kind of 'kudos' or something along those lines. It's worth mentioning that this thread question can be marked as solved, not sure how to do it myself on the app. But I will try to hunt it down.
Also, I would like to see a link to anything that contains all this miraculous knowledge within your brain, without having to pull a matrix stunt. Videos for everything you think I should watch, guides to read, and pictures to stare at. I would honestly love to be able to look at the Greek I gave to you and nearly instantly be able to both understand what is wrong, and how I fix it.
Wow, just wow, thank you. I nearly turned my phone into a $300 paperweight over the course of 14 or so hours, and you solved the problem in less than 10 posts combined. Epic Android Kudos.
THANK YOU!
Sent from my HTC One using xda app-developers app

zoline411 said:
<Farnsworth>
Good news everyone!
</Farnsworth>
It worked! Yay. I greatly thank you from the bottom of my heart. Now it's just as good as it was before, and better. Using the sense toolkit, love it, and more importantly, the phone is actually normal now, double love it.
I really do like the area rom, I installed Xposed, and used it to update to the latest sense toolkit. Everything is wonderful. Stayed away from twrp 2.7, and we'll yeah, it's all good.
How do I give you some kind of 'kudos' or something along those lines. It's worth mentioning that this thread question can be marked as solved, not sure how to do it myself on the app. But I will try to hunt it down.
Also, I would like to see a link to anything that contains all this miraculous knowledge within your brain, without having to pull a matrix stunt. Videos for everything you think I should watch, guides to read, and pictures to stare at. I would honestly love to be able to look at the Greek I gave to you and nearly instantly be able to both understand what is wrong, and how I fix it.
Wow, just wow, thank you. I nearly turned my phone into a $300 paperweight over the course of 14 or so hours, and you solved the problem in less than 10 posts combined. Epic Android Kudos.
THANK YOU!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Congrats
you can mark the thread as solved by editing your first post -> go advanced -> then you can edit the main thread title and include [SOLVED]
you can thank the people who helped you by pressing the little Thanks button, on their posts

zoline411 said:
Also, I would like to see a link to anything that contains all this miraculous knowledge within your brain, without having to pull a matrix stunt. Videos for everything you think I should watch, guides to read, and pictures to stare at. I would honestly love to be able to look at the Greek I gave to you and nearly instantly be able to both understand what is wrong, and how I fix it.
Click to expand...
Click to collapse
Guide to return stock from nkk71. There is good informationd in the FAQ.
Guide to push or sideload a rom
There is many more, but those 2 are essential to recover a soft bricked phone
There is also great guides from ARHD blogspot here

@alray
Wonderful, I've been reading and to my understanding my phone in its current state is no longer able to have S-off, is that right? I believe if has to do with an update that occurred not so long ago, and I of course not knowing well enough did opt for the update. Also I have no idea whether any sort of backup would have been helpful or not.
I'm going to spend a great deal of time reading those guides, what I should have done before ever making an attempt at rooting and S-off, so yeah... Time to hit the books.

HELP! Nasty Brick - No ADB/Recovery/RebootRUU + Borked Fastboot

I hate to add another one of these "help/brick" threads to the pile, but I've been reading around the forums for days, and I'm finally stumped.
My M7 is rooted, unlocked, S-OFF, superCID, with an InsertCoin custom rom and TWRP recovery... all hunky-dorey... Until I decided to return it to stock, so began simply by changing the CID back to original (11111111 - > HTC__622). This worked alright, except then everything suddenly stopped working:
1) Can't boot into OS (hangs on boot screen until eventual auto-reboot)
2) Can't boot into TWRP recovery (hangs on TWRP splash screen until eventual auto-reboot)
3) Can't enter RebootRUU via fastboot (just reboots phone)
4) Can't connect to pc via ADB within hboot/bootloader (no devices present)
5) Can't reboot itself into the bootloader from fastboot (it just resets the phone)
6) CAN enter bootloader manually via power+volume down
7) CAN connect to pc and issue fastboot commands within fastboot, BUT... fastboot is seemingly useless. Fastboot operations either report success (such as writecid and flash recovery giving an "OKAY") without actually writing anything; or they report failure (erase and others giving a "failed - remote: not allowed")
8) Another odd thing... in fastboot, when connecting to the USB, and the red label changes from "FASTBOOT" to "FASTBOOT USB" the label itself is partially 'torn'... that is, the top right corner of the fastboot usb label appears to be only partially drawn/rendered, by varying degrees over time, from completely showing to completely invisible. Weird.
I've tried everything from fastboot-flashing new recoveries (says OK, but nothing changes) to running RUU EXEs (they die when they can't reboot to the bootloader, just as fastboot cannot reboot to bootloader automatically either)
EDIT: I've also tried all of the above on older and newer computers and their different USB ports.
Here's my bootloader/hboot/fastboot status readout and my GETVAR, for those who are interested:
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-HTC__622
HBOOT-1.56.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
Nov 29 2013,20:47:04.0
FASTBOOT USB (this is what gets partially rendered!)
------------------------------------------------
GETVAR ALL:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.2
version-misc: PVT SHIP S-OFF
serialno: xxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__622
battery-status: good
battery-voltage: 4317mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
Thanks to all who can offer some help with this... I'm at the end of my rope here......... sigh.
Cheers, guys.

tobin_o said:
I hate to add another one of these "help/brick" threads to the pile, but I've been reading around the forums for days, and I'm finally stumped.
My M7 is rooted, unlocked, S-OFF, superCID, with an InsertCoin custom rom and TWRP recovery... all hunky-dorey... Until I decided to return it to stock, so began simply by changing the CID back to original (11111111 - > HTC__622). This worked alright, except then everything suddenly stopped working:
1) Can't boot into OS (hangs on boot screen until eventual auto-reboot)
2) Can't boot into TWRP recovery (hangs on TWRP splash screen until eventual auto-reboot)
3) Can't enter RebootRUU via fastboot (just reboots phone)
4) Can't connect to pc via ADB within hboot/bootloader (no devices present)
5) Can't reboot itself into the bootloader from fastboot (it just resets the phone)
6) CAN enter bootloader manually via power+volume down
7) CAN connect to pc and issue fastboot commands within fastboot, BUT... fastboot is seemingly useless. Fastboot operations either report success (such as writecid and flash recovery giving an "OKAY") without actually writing anything; or they report failure (erase and others giving a "failed - remote: not allowed")
8) Another odd thing... in fastboot, when connecting to the USB, and the red label changes from "FASTBOOT" to "FASTBOOT USB" the label itself is partially 'torn'... that is, the top right corner of the fastboot usb label appears to be only partially drawn/rendered, by varying degrees over time, from completely showing to completely invisible. Weird.
I've tried everything from fastboot-flashing new recoveries (says OK, but nothing changes) to running RUU EXEs (they die when they can't reboot to the bootloader, just as fastboot cannot reboot to bootloader automatically either)
Here's my bootloader/hboot/fastboot status readout and my GETVAR, for those who are interested:
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-HTC__622
HBOOT-1.56.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
Nov 29 2013,20:47:04.0
FASTBOOT USB (this is what gets partially rendered!)
------------------------------------------------
GETVAR ALL:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.2
version-misc: PVT SHIP S-OFF
serialno: xxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__622
battery-status: good
battery-voltage: 4317mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
Thanks to all who can offer some help with this... I'm at the end of my rope here......... sigh.
Cheers, guys.
Click to expand...
Click to collapse
You may want to have a look at my thread. i am having similar problems. On the last post i make a summary of my problems:
http://forum.xda-developers.com/showthread.php?t=2685024&page=3

Have you tried a different computer or just a different USB on your own machine?. Try a USB 2.0 to send fastboot commands, erase cache, flash recovery again (try both CWM as well as TWRP) after that fastboot erase cache again
Then reboot back into boot loader and from there into recovery.
Hope you get it sorted
Sent from my HTC One using XDA Premium HD app

Darksnoopy, thank you *very* much for the link to your own issue... it sounds very much like the same problem. Sadly, this means I'm probably SOL.
Did you ever look into how much HTC would want to charge you for fixing this nastiness? The irony is that I was changing mine back to stock only because I wanted to get the infamous purple-haze camera replaced while the warranty was still good... now I would have to pay for the internal memory fix myself, and probably the camera replacement, too. What are the chances this would end up being more than the value of the phone...
darksnoopy said:
You may want to have a look at my thread. i am having similar problems. On the last post i make a summary of my problems:
http://forum.xda-developers.com/showthread.php?t=2685024&page=3
Click to expand...
Click to collapse

hardstuffmuc said:
Have you tried a different computer or just a different USB on your own machine?. Try a USB 2.0 to send fastboot commands, erase cache, flash recovery again (try both CWM as well as TWRP) after that fastboot erase cache again
Then reboot back into boot loader and from there into recovery.
Click to expand...
Click to collapse
Good suggestion, Hardstuff... I did in fact try two very different (in age) computers and all of their USB ports, all with the same result, unfortunately. I forgot to mention that fact in the OP.
Thanks, anyway!

I can only add that do not lock the bootloader or s-on

SaHiLzZ said:
I can only add that do not lock the bootloader or s-on
Click to expand...
Click to collapse
Thanks for the reminder... at desperate times like this, we might be driven to try something crazy

What windows version do you have?
Just to make sure the steps:
Fastboot USB is detected? (that graphic glitch is nothing to worry about...I had that in the past)
And you have latest HTC drivers installed? If not, delete all HTC Sybc stuff including drivers, reboot computer, download latest HTC Syncmanager and install it, reboot computer again, de-install SyncManager, but leave drivers, and another reboot of computer!
Please download TWRP 2.6.3.3 file, put it into your adb/fastboot folder (it has to be named inside the folder WITHOUT the .img at the end) see attached pic
Please download a Sense 5.5 custom ROM, also put it into your adb/fastboot folder
Connect One using USB 2.0 to computer
fastboot erase cache
fastboot flash recovery openrecovery-twrp.2.6.3.3-m7ul.img (name exactly as the file is named inside adb/fastboot folder...see attached pic)
fastboot erase cache
Please post output to these commands with screenshot
Try to boot into recovery
If it works, back to bootloader, connect the One in Fastboot USB mode
adb devices (see attached pic)
adb push xxx.zip sdcard/
here in the cmd window not a lot happening as a Sense ROM has 1GB which takes a while to transfer, like 5 minutes, be patient
Once done, back into recovery and flash the .zip from there
Please report back if this solves the problem!
greets

tobin_o said:
Darksnoopy, thank you *very* much for the link to your own issue... it sounds very much like the same problem. Sadly, this means I'm probably SOL.
Did you ever look into how much HTC would want to charge you for fixing this nastiness? The irony is that I was changing mine back to stock only because I wanted to get the infamous purple-haze camera replaced while the warranty was still good... now I would have to pay for the internal memory fix myself, and probably the camera replacement, too. What are the chances this would end up being more than the value of the phone...
Click to expand...
Click to collapse
No not really, i know they are asking a lot of money for simple repairs, i am not going to ask for a new motherboard! And i cant find any motherboards on the internet to try to fix it myself
hardstuffmuc said:
What windows version do you have?
Just to make sure the steps:
Fastboot USB is detected? (that graphic glitch is nothing to worry about...I had that in the past)
And you have latest HTC drivers installed? If not, delete all HTC Sybc stuff including drivers, reboot computer, download latest HTC Syncmanager and install it, reboot computer again, de-install SyncManager, but leave drivers, and another reboot of computer!
Please download TWRP 2.6.3.3 file, put it into your adb/fastboot folder (it has to be named inside the folder WITHOUT the .img at the end) see attached pic
Please download a Sense 5.5 custom ROM, also put it into your adb/fastboot folder
Connect One using USB 2.0 to computer
fastboot erase cache
fastboot flash recovery openrecovery-twrp.2.6.3.3-m7ul.img (name exactly as the file is named inside adb/fastboot folder...see attached pic)
fastboot erase cache
Please post output to these commands with screenshot
Try to boot into recovery
If it works, back to bootloader, connect the One in Fastboot USB mode
adb devices (see attached pic)
adb push xxx.zip sdcard/
here in the cmd window not a lot happening as a Sense ROM has 1GB which takes a while to transfer, like 5 minutes, be patient
Once done, back into recovery and flash the .zip from there
Please report back if this solves the problem!
greets
Click to expand...
Click to collapse
I really hope it is not a eMMC failure, because if it is, none of the above will work. I lost one week of my life trying to fix my phone!

Hi Hardstuff, thanks for the thorough list of suggestions!
First, I'm running Win7-32bit on one computer, and Win7-64bit on the other.
Second, yeah, Fastboot USB is detected no problem, but that's about the only thing going for me.
I did as you said-- wiped every trace of the old drivers, and reinstalled the HTC drivers by way of HTC Sync install/uninstall, with reboots in between each step.
Sadly, everything with the cache erase and recovery flash went as always-- fastboot seems to indicate success on each command, but TWRP still freezes on the TWRP splash screen until it finally does a reboot by itself. I'm pretty sure this isn't a new install of TWRP that's freezing, as I tried flashing a CWM recovery the other day too, with a success message on the flash, then still came up freezing on a TWRP screen.
I did a screencap of the fastboot commands, as well as the driver install window, showing the collection of driver installs attempted as the phone went from power off, to bootloader, to fastboot, to attempting recovery, and so on. Windows also kept complaining that it was connected to a USB device that it couldn't recognize.
This entire series of steps and results was the same on each USB port on both computers - no variation.
Not sure if there's anything left to try at this point... I've never been this screwed with a phone before, and it was all just from a weenie little CID change - this sucks.
Anyway, thanks again Hardstuff!
hardstuffmuc said:
What windows version do you have?
Just to make sure the steps:
Fastboot USB is detected? (that graphic glitch is nothing to worry about...I had that in the past)
And you have latest HTC drivers installed? If not, delete all HTC Sybc stuff including drivers, reboot computer, download latest HTC Syncmanager and install it, reboot computer again, de-install SyncManager, but leave drivers, and another reboot of computer!
Please download TWRP 2.6.3.3 file, put it into your adb/fastboot folder (it has to be named inside the folder WITHOUT the .img at the end) see attached pic
Please download a Sense 5.5 custom ROM, also put it into your adb/fastboot folder
Connect One using USB 2.0 to computer
fastboot erase cache
fastboot flash recovery openrecovery-twrp.2.6.3.3-m7ul.img (name exactly as the file is named inside adb/fastboot folder...see attached pic)
fastboot erase cache
Please post output to these commands with screenshot
Try to boot into recovery
Click to expand...
Click to collapse

darksnoopy said:
No not really, i know they are asking a lot of money for simple repairs, i am not going to ask for a new motherboard! And i cant find any motherboards on the internet to try to fix it myself
I really hope it is not a eMMC failure, because if it is, none of the above will work. I lost one week of my life trying to fix my phone!
Click to expand...
Click to collapse
Yeah, and even if you could find a replacement mobo online, I've heard that the One is one of the worst phones ever for taking apart and reassembling.
What really burns me is that I've likely lost a fairly expensive phone without making any mistake that I could at least blame myself for. It sounds like your One also went south on you without any mistake on your part. My next question would be-- is this more likely to happen with the One? With all HTCs? Or all handsets equally? My backup Xperia Play has put on a lot of crazy mileage in terms of flashing, along with a Galaxy S2 that I sold some time ago. On the other hand, my One was virtually untouched by comparison...

tobin_o said:
Yeah, and even if you could find a replacement mobo online, I've heard that the One is one of the worst phones ever for taking apart and reassembling.
What really burns me is that I've likely lost a fairly expensive phone without making any mistake that I could at least blame myself for. It sounds like your One also went south on you without any mistake on your part. My next question would be-- is this more likely to happen with the One? With all HTCs? Or all handsets equally? My backup Xperia Play has put on a lot of crazy mileage in terms of flashing, along with a Galaxy S2 that I sold some time ago. On the other hand, my One was virtually untouched by comparison...
Click to expand...
Click to collapse
Yeah if you search for "emmc write protected" or "emmc lockout" you will find many threads about lots of different brands. Well if u consider how many htc ones have been sold, this problem is not quite common

Have you tried to get back to supercid?

SaHiLzZ said:
Have you tried to get back to supercid?
Click to expand...
Click to collapse
Yep. Same deal as the other fastboot write commands: It carries out the write operation as if it were successful, but then nothing has changed.

[Q] HTC One M7 - Developers Edition - Boot Loop HELP!!!!

Hello,
I am a newbie to the forum. I posses only limited knowledge.
I use a HTC one M7 developers editions. I dropped my phone and since then it had gone in a boot loop and I am not able to get through out of the home screen. It just keeps rebooting.
*** UNLOCKED ***
M7_ul S-ON
HBOOT - 1.57.0000
RADIO-4T.28.3218.04
OS - 6.07.1540.1
I tried to flash the RUU with the help of one of the threads here using an .exe file. As my phone was s-on, I was not able to use the zip. But it kept giving me a error 155. I then tried to have the s-off with FIREWATER to have an earlier RUU like 4.3 installed but I couldn't turn on the USB debugging from the inside of the phone.
I am not sure of what to do now. Any sort of help would be great.
Thanks a lot

ash3m21 said:
Hello,
I am a newbie to the forum. I posses only limited knowledge.
I use a HTC one M7 developers editions. I dropped my phone and since then it had gone in a boot loop and I am not able to get through out of the home screen. It just keeps rebooting.
*** UNLOCKED ***
M7_ul S-ON
HBOOT - 1.57.0000
RADIO-4T.28.3218.04
OS - 6.07.1540.1
I tried to flash the RUU with the help of one of the threads here using an .exe file. As my phone was s-on, I was not able to use the zip. But it kept giving me a error 155. I then tried to have the s-off with FIREWATER to have an earlier RUU like 4.3 installed but I couldn't turn on the USB debugging from the inside of the phone.
I am not sure of what to do now. Any sort of help would be great.
Thanks a lot
Click to expand...
Click to collapse
that ruu can not be flashed on your phone, because it require s-off.
I think you probably have hardware damage since your phone started bootlooping after you have dropped it. however you could try to restore the 6.07.1540.1 nandroid backup posted in the dev edition update thread in the general section and see if your phone can boot normaly

ash3m21 said:
Hello,
I am a newbie to the forum. I posses only limited knowledge.
I use a HTC one M7 developers editions. I dropped my phone and since then it had gone in a boot loop and I am not able to get through out of the home screen. It just keeps rebooting.
*** UNLOCKED ***
M7_ul S-ON
HBOOT - 1.57.0000
RADIO-4T.28.3218.04
OS - 6.07.1540.1
I tried to flash the RUU with the help of one of the threads here using an .exe file. As my phone was s-on, I was not able to use the zip. But it kept giving me a error 155. I then tried to have the s-off with FIREWATER to have an earlier RUU like 4.3 installed but I couldn't turn on the USB debugging from the inside of the phone.
I am not sure of what to do now. Any sort of help would be great.
Thanks a lot
Click to expand...
Click to collapse
There is no RUU for your version, the RUU you tried to run was a lower version and you can not run a lower version with being S-ON. If you have TWRP installed you can try to flash a nandroid 6.07.1540.1.

majmoz said:
There is no RUU for your version, the RUU you tried to run was a lower version and you can not run a lower version with being S-ON. If you have TWRP installed you can try to flash a nandroid 6.07.1540.1.
Click to expand...
Click to collapse
@majmoz : My phone did not have TWRP before. And I am not sure how to restore an android as my phone won't even open recovery !! Do you think I can still get something from the phone? Any ideas would be really helpful!!
Thanks

ash3m21 said:
@majmoz : My phone did not have TWRP before. And I am not sure how to restore an android as my phone won't even open recovery !! Do you think I can still get something from the phone? Any ideas would be really helpful!!
Thanks
Click to expand...
Click to collapse
If you can not get USB Debugging enabled, there is not much you can do except send the phone in for repair.

majmoz said:
If you can not get USB Debugging enabled, there is not much you can do except send the phone in for repair.
Click to expand...
Click to collapse
usb debugging not needed with fastboot he can flash TWRP

i have the same problem
i have same problem as above
mine is htc 038 indian version soff phone it keeps rebooting
tried every possible method from ruu to custom rom no luck
phone keeps on rebooting every 10 seconds
:crying:
yatindroid said:
usb debugging not needed with fastboot he can flash TWRP
Click to expand...
Click to collapse

ash3m21 said:
@majmoz : My phone did not have TWRP before. And I am not sure how to restore an android as my phone won't even open recovery !! Do you think I can still get something from the phone? Any ideas would be really helpful!!
Thanks
Click to expand...
Click to collapse
Let try these steps:
1. If you don't have fastboot and adb installed then use Minimal ADB & Fastboot TooL to install them. We will not be able to use the ADB commands but we will be able to use the fastboot commands.
2. Download and place in your adb and fastboot folder TWRP 2.7.1.2 and firmware 6.07.1540.1 (the unmodified one) rename to firmware.zip
3, We need to boot the phone into bootloader. Completely power off your phone. Once the phone is off, press and hold the Power Button + Vol Down the phone will boot into the bootloader. Using the Vol Buttons will move the selection up and down. Highlight or select FASTBOOT, then press the Pwr button to select. Once selected, you should see FASTBOOT where it previously said HBOOT.
4. Connect your phone to the computer, it should say FASTBOOT USB.
5. In the command window type the following commands:
Code:
[B][I][COLOR="Blue"]fastboot devices[/COLOR][/I][/B]
Note: Should see your "serial number device" Copy down your serial number
Code:
[B][I][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/I][/B]
Note: You should see a silver HTC logo come up on your phone after executing this command.
Note: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Code:
[I][B][COLOR="Blue"]fastboot flash zip firmware.zip[/COLOR][/B][/I]
Note: This will fail, message to say "please flush image again immediately" Just run the command again!
Code:
[B][I][COLOR="Blue"]fastboot flash zip firmware.zip[/COLOR][/I][/B]
Note: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Code:
[B][I][COLOR="Blue"]fastboot reboot[/COLOR][/I][/B]
Note: Your phone should boot up normally
If it doesn't or you just want to put the nandroid on your phone here is how it is done:
Unzip the nandroid and it will make its own folders on your PC. Since you don't have TWRP installed on your phone you will need to make some folders. Connect your phone to your PC, once it is connected open the Internal Storage folder. Here make a new folder called TWRP. Open that folder make a folder called BACKUPS. Open that folder and make a new folder the name will be your serial number that you copied earlier. Now copy the entire folder the nandroid made earlier to this folder.
Now boot into the bootloader like you did earlier.
Code:
[B][I][COLOR="Blue"]fastboot flash recovery twrp-2.7.1.2-m7.img[/COLOR][/I][/B]
Code:
[B][I][COLOR="Blue"]fastboot erase cache[/COLOR][/I][/B]
Code:
[B][I][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/I][/B]
Once back in the bootloader, select bootloader and on the next screen select Recovery. When TWRP boots up you will have a number of tiles Backup is one and Restore is another. For sanity sake, I would backup the present system before I restored the nandroid. When you select Restore you should see two if you made a backup the one with the name of the file folder you moved is the nandroid backup. Select it and once it is complete select reboot system and you are done.

Help finding M7 on Windows 10 to use ADB

Hi guys, I have been lurking for a while, but can't seem to find anything on my current issue. I am brand new to development and was able to sim unlock my old CM11 M7, reinstall CM11, and even rescue it from a bootloop through adb. That was all through windows 8.1.
I just bought a phone from ebay that is caught in a bootloop. No idea if USB debugging is enabled (does that matter for adb?), what ROMs were installed, etc. It looks like it's not rooted, but the Hboot says unlocked/tampered. I can access recovery (TWRP), fastboot/Hboot, but I cannot get my computer to recognize the phone in device manager (no misc. devices even appear when it's plugged in). I have tried installing various drivers, running/updating htc sync, and at one point, it even recognized the phone as a misc. device, but I wasn't able to do anything practical, nor replicate those conditions. I have windows 10 and have just wiped all of the htc programs.
Ideally, I plan to access adb, push a stock rom, check the imei (don't even know if it's stolen or not at this point), then find a custom rom that'll work with it (that still has ir blaster working).
My understanding is very limited, but I learn quick and would be very grateful for any help and insight into my situation!
Thank you very much for reading and for your time!

Install the drivers here. Then yes, you need to enable USB debugging for adb to work

Thanks to the mods who moved me here. I will post these questions in the Q&A from now on!
dd98 said:
Install the drivers here.
Click to expand...
Click to collapse
Thank you for the reply!
I think the cord was faulty, but device manager now sees my phone as an unknown device titled: "m7wls"
With everything HTC removed, I installed the driver you had recommended, but device manager still shows the caution symbol/"!" . I tried manually browsing for the driver and automatically searching, to no avail. I think I have found the unpacked version of the driver online as well, if it would help to put that somewhere and have device manager find that? I'm a little lost.
Then yes, you need to enable USB debugging for adb to work
Click to expand...
Click to collapse
This is disconcerting because I do not have access to a rom. Is there a way to enable USB debugging through TWRP? Here's hoping the last owner had it enabled :fingers-crossed:

Enigmatic Fart said:
Thanks to the mods who moved me here. I will post these questions in the Q&A from now on!
Thank you for the reply!
I think the cord was faulty, but device manager now sees my phone as an unknown device titled: "m7wls"
With everything HTC removed, I installed the driver you had recommended, but device manager still shows the caution symbol/"!" . I tried manually browsing for the driver and automatically searching, to no avail. I think I have found the unpacked version of the driver online as well, if it would help to put that somewhere and have device manager find that? I'm a little lost.
This is disconcerting because I do not have access to a rom. Is there a way to enable USB debugging through TWRP? Here's hoping the last owner had it enabled :fingers-crossed:
Click to expand...
Click to collapse
Ok well USB debugging is enabled by default in recovery and there is no way to toggle it anyway

dd98 said:
Ok well USB debugging is enabled by default in recovery and there is no way to toggle it anyway
Click to expand...
Click to collapse
Shameless bump!
Alright guys, I have the weekend to work on this project and I'm doing my research now.
In ADB, the phone does not appear in device manager, nor will it appear in command prompt; adb under devices. In fastboot, IT APPEARS (as "My HTC")!!! It also connects via command prompt; fastboot!
In recovery, it shows as m7wls.
I think I need to access adb to push a rom and cannot via fastboot, right? If so, is there anything else I can try?

Enigmatic Fart said:
Shameless bump!
Alright guys, I have the weekend to work on this project and I'm doing my research now.
In ADB, the phone does not appear in device manager, nor will it appear in command prompt; adb under devices. In fastboot, IT APPEARS (as "My HTC")!!! It also connects via command prompt; fastboot!
In recovery, it shows as m7wls.
I think I need to access adb to push a rom and cannot via fastboot, right? If so, is there anything else I can try?
Click to expand...
Click to collapse
If your using any TWRP version 2.8.3.0 and up, you can just drag and drop the file like normal. Just open Computer and you should see something like "One" or "MTP Device"

dd98 said:
If your using any TWRP version 2.8.3.0 and up, you can just drag and drop the file like normal. Just open Computer and you should see something like "One" or "MTP Device"
Click to expand...
Click to collapse
EDIT: disregard the following, TWRP is at 2.6.3.0
Ha, no way, that'd be way too easy! Uhh, but how? The phone appears in the device manager, but not as a storage device under my computer.
While in recovery, Windows device manager shows my phone as an exclamation point without a driver (after installing the latest one linked above) as "m7wls". I took it upon myself to do a manual installation (device manager>m7wls>update driver software>browse>let me pick from driver software on the computer>My HTC) and now it appears as "My HTC". This has not rectified the absence from my computer.
So back to the adb push idea: the phone appears in device manager as My HTC in fastboot and recovery, but does not appear at while in Hboot, for adb.

Enigmatic Fart said:
EDIT: disregard the following, TWRP is at 2.6.3.0
Ha, no way, that'd be way too easy! Uhh, but how? The phone appears in the device manager, but not as a storage device under my computer.
While in recovery, Windows device manager shows my phone as an exclamation point without a driver (after installing the latest one linked above) as "m7wls". I took it upon myself to do a manual installation (device manager>m7wls>update driver software>browse>let me pick from driver software on the computer>My HTC) and now it appears as "My HTC". This has not rectified the absence from my computer.
Click to expand...
Click to collapse
Download the latest TWRP image here(its 2.8.7.0) and flash it in fastboot and then you should have access to your internal storage using windows explorer

dd98 said:
See above post: can't post links on new account
Click to expand...
Click to collapse
I can do that...
Except, the only hangup is that I cannot push TWRP onto my phone without adb, right? fastboot will flash, but not push, I thought I had understood. I'm new though.
This is all a very strange and interesting process, so I really appreciate your patience and attention here, man (or ma'am)! It's some fun problem solving!
If I can push a file onto my phone, everything would be solved. The lack of rom, and lack of drivers seem to be the main issues.

You don't need to push anything on your phone if you're using fastboot. Just putt your TWRP.img in your adb folder on your PC and flash using flastboot flash recovery "recovery name".img. After that you just drag and drop ROM.zip using MTP in your recovery

donkeykong1 said:
You don't need to push anything on your phone if you're using fastboot. Just putt your TWRP.img in your adb folder on your PC and flash using flastboot flash recovery "recovery name".img. After that you just drag and drop ROM.zip using MTP in your recovery
Click to expand...
Click to collapse
Dude, I completely forgot you could do that. AAAAAGGGGGHHHHHH!!!!!!!! Lol, Ok, let me see what I can do and post back some results.
Thank you sooooo much again, you guys!

Alright, so for all intents and purposes, I'm up and running. I can swap the ROMs I need and do well enough with TWRP and Fastboot. Unfortunately, I still do not have access to my device in ADB. It still doesn't show in device manager.
I had thought that installing a sense ROM and plugging it into the computer would automatically rectify this, then I even plugged in a SIM card for a software update, but I guess they won't update a tampered device.
Where can I go from here? I assume that it's just Windows 10 compatibility issues?
EDIT: phone's rooted and unlocked bootloader.

Enigmatic Fart said:
Alright, so for all intents and purposes, I'm up and running. I can swap the ROMs I need and do well enough with TWRP and Fastboot. Unfortunately, I still do not have access to my device in ADB. It still doesn't show in device manager.
I had thought that installing a sense ROM and plugging it into the computer would automatically rectify this, then I even plugged in a SIM card for a software update, but I guess they won't update a tampered device.
Where can I go from here? I assume that it's just Windows 10 compatibility issues?
EDIT: phone's rooted and unlocked bootloader.
Click to expand...
Click to collapse
Now go to settings/about/software info and click on build number untill it says "you are a developer now". Then settings/developer optinions and enable USB debugging

donkeykong1 said:
Now go to settings/about/software info and click on build number untill it says "you are a developer now". Then settings/developer optinions and enable USB debugging
Click to expand...
Click to collapse
Yessir, no effect.
EDIT:Wait, for S&Gs, I tried "adb devices" while in the system of a sense rom and it shows, but as unauthorized. I'm going to play some more.
EDIT 2: Wiping everything and starting from scratch.

Bump again,
Back to ground zero:
I uninstalled all HTC programs and drivers
I reinstalled SDK and all the components
I have adb files placed in root of C:/
I installed the latest drivers
Device manager still only recognizes my android in fastboot, recovery, and system, but not ADB. (everything lists as android USB Devices>MY HTC
Phone is rooted, unlocked, and USB debugging is enabled.
What am I missing?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
Maybe there are some other basics I am missing? I installed jdk previously before.