Database Develop

[SOLVED] Please guys, need help to bring my One back working

Hi guys.
Yesterday i decided to s-off via rumrunner.
I was on a GPE ROM (so yes, rooted, twrp recovery and custom rom) so i downloaded and flashed a sense based ROM as suggested, but after repeating 2 times the 8 pouring attempts i was still s-on.
I decided to try another sense base flashing a ruu back to stock to be sure it was compatible, so I relocked the bootloader.
The ruu install went immediately wrong (FAILED signature check verification). The problem now is that when I power it on it immediately goes in fastboot mode (yes fastboot, not bootloader). If I press bootloader and then recovery it goes back to fastboot.
So I tried another thing: unlock again the bootloader to manually flash back a custom recovery to make it work again.
Great idea, so i prepared back the unlocktoken, flash it and BAM: again signature check verification fail.
If I can't unlock and custom recovery again my only hope I guess its an ruu reset.
Now, I know that I can't revert hboot to an older version, and mine is 1.54.0000 so pretty high, but i tried also a 3.x RUU i found inside the RUU collection thread and got the same error msg.
Also smth must be definitely wrong cause I don't think the Unlocktoken should get that error msg, I never got it!
So to summarize:
- tampered, relocked and s-on 1.54.0000 hboot
- FAILED signature check verification if I try to unlock it via htcdev tocken
- RUU zips get same signature check fail error
- same signature check verification error if I try to manually flash just the boot partition (fastboot flash boot)
Guys I had a Desire, a One XL, a Nexus 4 but I think it's the first time I'm stuck with a completely useless slab and really don't know how to recover it.
Really ANY suggestion to make it boot again would be much appreciated...
Thanks

Yorgan said:
Hi guys.
Yesterday i decided to s-off via rumrunner.
I was on a GPE ROM (so yes, rooted, twrp recovery and custom rom) so i downloaded and flashed a sense based ROM as suggested, but after repeating 2 times the 8 pouring attempts i was still s-on.
I decided to try another sense base flashing a ruu back to stock to be sure it was compatible, so I relocked the bootloader.
The ruu install went immediately wrong (FAILED signature check verification). The problem now is that when I power it on it immediately goes in fastboot mode (yes fastboot, not bootloader). If I press bootloader and then recovery it goes back to fastboot.
So I tried another thing: unlock again the bootloader to manually flash back a custom recovery to make it work again.
Great idea, so i prepared back the unlocktoken, flash it and BAM: again signature check verification fail.
If I can't relock my only hope I guess its an ruu reset.
Now, I know that I can't revert hboot to an older version, and mine is 1.54.0000 so pretty high, but i tried also a 3.x RUU i found inside the RUU collection thread and got the same error msg.
Also smth must be definitely wrong cause I don't think the Unlocktoken should get that error msg, I never got it!
So to summarize:
- tampered, relocked and s-on 1.54.0000 hboot
- FAILED signature check verification if I try to unlock it via htcdev tocken
- RUU zips get same signature check fail error
- same signature check verification error if I try to manually flash just the boot partition (fastboot flash boot)
Guys I had a Desire, a One XL, a Nexus 4 but I think it's the first time I'm stuck with a completely useless slab and really don't know how to recover it.
Really ANY suggestion to make it boot again would be much appreciated...
Thanks
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n before posting)

nkk71 said:
can you post a "fastboot getvar all" (remove IMEI and s/n before posting)
Click to expand...
Click to collapse
Sure, here it is:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid:
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 4200mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
gencheckpt: 0
Thanks for the quick answer

Yorgan said:
Sure, here it is:
version-bootloader: 1.54.0000
version-main: 2.24.401.1
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0710000
cidnum: HTC__032
Thanks for the quick answer
Click to expand...
Click to collapse
A) Do you still have custom recovery? If yes, can you enter recovery, and on your PC open a shell: "adb shell", does it show $ or #
can you copy/paste the command prompt
B) did you get a new unlocktocken from HTCdev, or are you using your old one?
Hit thanks button if I've helped, though it to soon to tell if I did

nkk71 said:
A) Do you still have custom recovery? If yes, can you enter recovery, and on your PC open a shell: "adb shell", does it show $ or #
can you copy/paste the command prompt
B) did you get a new unlocktocken from HTCdev, or are you using your old one?
Hit thanks button if I've helped, though it to soon to tell if I did
Click to expand...
Click to collapse
yup i forgot to press it =)
no custom recovery as i said, it just goes back to fastboot, i wanted to unlock it to flash twrp again but this stupid signature check is preventing me from doing anything!
i somehow think that my rom is still inside, just not booting, that's why i also tried to manually flash just the boot.img.
nope, i obtained a new one after the old gave me the error, no luck
really i dont know what to think

Yorgan said:
nope, i obtained a new one after the old gave me the error, no luck
really i dont know what to think
Click to expand...
Click to collapse
Okay, this is bad
Yorgan said:
that's why i also tried to manually flash just the boot.img.
Click to expand...
Click to collapse
Won't work with locked/relocked bootloader
Yorgan said:
no custom recovery as i said, it just goes back to fastboot,
Click to expand...
Click to collapse
A) did you at any point flash a stock recovery? (either using a Guru Reset ROM or fastboot flash recovery etc?)
B) have you tried:
fastboot erase cache
fastboot reboot-bootloader
and try to enter RECOVERY (using the volume and power buttons)?

nkk71 said:
Okay, this is bad
Won't work with locked/relocked bootloader
A) did you at any point flash a stock recovery? (either using a Guru Reset ROM or fastboot flash recovery etc?)
B) have you tried:
fastboot erase cache
fastboot reboot-bootloader
and try to enter RECOVERY (using the volume and power buttons)?
Click to expand...
Click to collapse
Nope i never wanted to remove TWRP, but does relocking bootloader not flash back the stock one?
Unluckily it just enters fastboot no matter if i power the phone up with or without volume buttons pressed!
I always thought that "if there's fastboot there's hope", but how to bypass the signature check if i'm s-on?
And why the heck does it fail checking signature of the Unlocktoken?

Yorgan said:
Nope i never wanted to remove TWRP, but does relocking bootloader not flash back the stock one?
Unluckily it just enters fastboot no matter if i power the phone up with or without volume buttons pressed!
I always thought that "if there's fastboot there's hope", but how to bypass the signature check if i'm s-on?
And why the heck does it fail checking signature of the Unlocktoken?
Click to expand...
Click to collapse
you're definitely in a pickle here.
But when in bootloader screen (the screenshot attached), can you select the second line; use VOL DOWN to get to second line, then press POWER to select it, where does it go?

nkk71 said:
you're definitely in a pickle here.
But when in bootloader screen (the screenshot attached), can you select the second line; use VOL DOWN to get to second line, then press POWER to select it, where does it go?
Click to expand...
Click to collapse
It vibrates, White screen with Htc logo, it writes 'entering recovery' for half a second and then back to fastboot

nkk71 said:
you're definitely in a pickle here.
But when in bootloader screen (the screenshot attached), can you select the second line; use VOL DOWN to get to second line, then press POWER to select it, where does it go?
Click to expand...
Click to collapse
OMG the UnlockCode worked!
Just to let you know, i changed absolutely nothing: the command i sent was the same as before and so was the token.
I think that maybe one of the many failed RUU attempts just flashed the partition i was missing, not enough to flash rom but enough to check the signature of the token!
Thx a lot dude, you gave me the hope to try to mess around again =)
Happyyy =))

Yorgan said:
OMG the UnlockCode worked!
Just to let you know, i changed absolutely nothing: the command i sent was the same as before and so was the token.
I think that maybe one of the many failed RUU attempts just flashed the partition i was missing, not enough to flash rom but enough to check the signature of the token!
Thx a lot dude, you gave me the hope to try to mess around again =)
Happyyy =))
Click to expand...
Click to collapse
:good::good::highfive::highfive::highfive::highfive::highfive::highfive::highfive: (I know that looks funny )
So go get yourself S-Off, and never go back S-On. S-Off is your "get out of jail" card!!!
Do not relock, unless S-Off, there's a thread somewhere around here where plenty of people weren't able to get HTCdev to unlock again!!
Any other help needed, let me know.

[Q] Bricked after flashing Insertcoin 4.4 ROM (ADB can't find device)

I flashed the ROM in recovery. I thought I was S-OFF but am S-ON. It gave me error code 7 and the installation failed. Now I can't even boot into recovery (it just cycles between the HTC splash screen and then tries booting into recovery for a second. I see the recovery logo and then it reboots).
Holding down the volume down and power buttons I can get into HBOOT, but can't do a factory reset or recovery from there. I can get into the FASTBOOT menu, but my computer just tells me that the device connected has malfunctioned and can't recognize it. running "ADB Devices" returns with no devices found.
I downloaded and ran the RUU, but it can't find the phone. I'm out of ideas. I appreciate any help you guys can offer.

Caboose127 said:
I flashed the ROM in recovery. I thought I was S-OFF but am S-ON. It gave me error code 7 and the installation failed. Now I can't even boot into recovery (it just cycles between the HTC splash screen and then tries booting into recovery for a second. I see the recovery logo and then it reboots).
Holding down the volume down and power buttons I can get into HBOOT, but can't do a factory reset or recovery from there. I can get into the FASTBOOT menu, but my computer just tells me that the device connected has malfunctioned and can't recognize it. running "ADB Devices" returns with no devices found.
I downloaded and ran the RUU, but it can't find the phone. I'm out of ideas. I appreciate any help you guys can offer.
Click to expand...
Click to collapse
I'm willing to help.. but I am very busy.. can I have a look into this a bit later? Maybe someone else is going to be able to help you.. but if there isn't... I'm going to help you.
To calm down: As long as you can get into your hboot, everything is fine! You are not hardbricked!
Let me know if that's ok for you.

LibertyMarine said:
I'm willing to help.. but I am very busy.. can I have a look into this a bit later? Maybe someone else is going to be able to help you.. but if there isn't... I'm going to help you.
To calm down: As long as you can get into your hboot, everything is fine! You are not hardbricked!
Let me know if that's ok for you.
Click to expand...
Click to collapse
Hey, as long as you're willing to help, I can wait. I'm at work for the next 6 hours and don't really NEED my phone until I get off. So I've got time to wait.
Thanks.

Caboose127 said:
Hey, as long as you're willing to help, I can wait. I'm at work for the next 6 hours and don't really NEED my phone until I get off. So I've got time to wait.
Thanks.
Click to expand...
Click to collapse
Hmm.. in 3 hours I'm going to sleep.. (Switzerland time zone) And so I write some basic thing that you can test and try out.. so that we can determine what the best steps will be.
First: Give me the output from that command(while in fastboot-ubs):
fastboot getvar all
Click to expand...
Click to collapse
Second:
What hboot version do you have? 1.44/1.54/1.55
What's the stock ROM you recieved with the factory fresh phone? z.zz.XXX.z now.. what was the XXX number exactly? The international edition for example is: 1.24.401.7 I only need the 3-digit number.
Third:
Unlocked or Locked/Relocked?

LibertyMarine said:
Hmm.. in 3 hours I'm going to sleep.. (Switzerland time zone) And so I write some basic thing that you can test and try out.. so that we can determine what the best steps will be.
First: Give me the output from that command(while in fastboot-ubs):
Second:
What hboot version do you have? 1.44/1.54/1.55
What's the stock ROM you recieved with the factory fresh phone? z.zz.XXX.z now.. what was the XXX number exactly? The international edition for example is: 1.24.401.7 I only need the 3-digit number.
Third:
Unlocked or Locked/Relocked?
Click to expand...
Click to collapse
The phone is unlocked, HBOOT version is 1.44
running fastboot getvar all yields "waiting for device" Windows doesn't recognize the phone when it's plugged in. I know I have the correct drivers installed. When it tries to boot into recovery, I briefly see the device show up in Device Manager, but it disappears again. I don't know what the stock ROM was that came with the phone. I want to say it was 1.27.531.8, but I don't know for sure.

Caboose127 said:
The phone is unlocked, HBOOT version is 1.44
running fastboot getvar all yields "waiting for device" Windows doesn't recognize the phone when it's plugged in. I know I have the correct drivers installed. When it tries to boot into recovery, I briefly see the device show up in Device Manager, but it disappears again. I don't know what the stock ROM was that came with the phone. I want to say it was 1.27.531.8, but I don't know for sure.
Click to expand...
Click to collapse
Are you in the fastboot mode? I mean you booted your phone into the bootloader.. then you chose "fastboot" and after this there's written "FASTBOOT USB"? and then you got this waiting for device? because simply being in hboot doesn't allow you to use fastboot commands. Sorry if this is a noob question.. but if your device wasn't recognized.. this would be f***ing difficult to get anything running again. This bug with the recovery.. hmmm... don't boot into recovery again.. recovery is connected to adb not fastboot... and to calm down.. here we have a RUU to get back stock(don't use it right now):
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe

have you tried re flashing a new recovery via fastboot?

LibertyMarine said:
Are you in the fastboot mode? I mean you booted your phone into the bootloader.. then you chose "fastboot" and after this there's written "FASTBOOT USB"? and then you got this waiting for device? because simply being in hboot doesn't allow you to use fastboot commands. Sorry if this is a noob question.. but if your device wasn't recognized.. this would be f***ing difficult to get anything running again. This bug with the recovery.. hmmm... don't boot into recovery again.. recovery is connected to adb not fastboot... and to calm down.. here we have a RUU to get back stock(don't use it right now):
Click to expand...
Click to collapse
Nope, the phone is currently displaying "FASTBOOT USB" in red and I have the following selectable options on the screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN

khhhhris said:
have you tried re flashing a new recovery via fastboot?
Click to expand...
Click to collapse
I would flash a new recovery, but my computer doesn't seem to be recognizing my device. It does for a second during boot into recovery, but once the recovery crashes and the phone resets, the phone disappears from device manager. It doesn't show backup when I'm in FASTBOOT USB.
I'm going to try it on a coworkers computer.

Caboose127 said:
Nope, the phone is currently displaying "FASTBOOT USB" in red and I have the following selectable options on the screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Click to expand...
Click to collapse
this is weird... try another computer. Try different drivers from here:
http://forum.xda-developers.com/showthread.php?t=2191279
TRY EVERYTHING GO GET THE COMPUTER RECOGNIZING YOUR HTC ONE
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
khhhhris said:
have you tried re flashing a new recovery via fastboot?
Click to expand...
Click to collapse
...lol this would be funny.. maybe his recovery partition is corrupt.. hmmm then we'd have to use different error handling strategies...

Progress! I was able to get fastboot working on my coworkers computer: Here's the gitvar results:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(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: 4267mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
Click to expand...
Click to collapse
The phone shows up in Device Manager when I'm in FASTBOOT USB, but not when I'm in HBOOT. I still can't do anything with ADB.
I was able to flash a new recovery with FASTBOOT, but that recovery crashed as well.

If you are still trying for your computer to recognize the adb device and still hasn't then just buy an USB OTG then put an USB to flash a rom from there.
http://www.androidapps4u.com/temp/screenshot_3-usb-otg-cable.jpg

Define crashed? TWRP 2.6.3.0 ? or CWM ? What happens in recovery mode?

Caboose127 said:
Progress! I was able to get fastboot working on my coworkers computer: Here's the gitvar results:
The phone shows up in Device Manager when I'm in FASTBOOT USB, but not when I'm in HBOOT. I still can't do anything with ADB.
I was able to flash a new recovery with FASTBOOT, but that recovery crashed as well.
Click to expand...
Click to collapse
adb commands won't work while in fastboot mode/bootloader. fastboot needs to be used while in fastboot mode. While your in fastboot, try
fastboot erase cache
Then fastboot flash your recovery again (fastboot flash recovery nameofrecovery.img), and try to access recovery

Thanks for all of your help guys. I finally got it working.

For everyone else reference, mark your thread [SOLVED] and post a brief description how you fixed it..

Thanks guys for helping me out!

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] AT&T HTC One M7 soft-bricked. Fastboot works, can't boot to recovery [Concluded]

[Q] AT&T HTC One M7 soft-bricked. Fastboot works, can't boot to recovery [Concluded]
Wondering if I can get somebody to weigh in on this one. Trying to help a friend of a friend out--I don't know the back story of what happened to this, but sounded like a 'bricked his phone doing dangerous things without enough knowledge' kind of situation.
The phone is stuck in a boot loop, just the HTC wordmark on a white background. You can enter the bootloader just fine, and fastboot can read and send commands just fine, flash recovery just fine, etc. The device cannot, however, enter recovery mode. It just says "entering recovery..." at the top, with the same HTC wordmark and white background. It displays for 30 seconds, then the screen goes black for 4-5 seconds, then back to the HTC logo.
Some info about the phone:
AT&T HTC One M7
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: [redacted]
imei: [redacted]
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3838mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Things I have tried already:
The first thing I did was I re-locked the bootloader and flashed the RUU exe, thinking that might be the quickest fix. The exe took the expected length of time and said it was successful, and rebooted the phone.
Still looping.
I then got the unlock token, unlocked the bootloader again, erased the cache, and fastboot flashed CWM recovery-clockwork-6.0.4.3-m7att.img - Attempted to reboot to recovery.
Still looping.
Cleared the cache, flashed openrecovery-twrp-2.7.1.1-m7.img - Attempted to reboot to recovery.
Still looping.
What's Next?
So that's about where I am now, I have functional bootloader and fastboot, but something is corrupted and I just absolutely can't get into recovery no matter what I try. I really thought the RUU would be a simple way to fix it, and was surprised when it didn't work.
From the reading I've done it sounds like there's some sort of emmc partition corruption possibly? Am I going in the right direction? I did post the fastboot getvar all results above--perhaps that can tip somebody off? I don't know quite enough to be able to spot trouble there at a glance, unfortunately.
I don't personally have a lot invested in getting this running, its owner already replaced it and I'm just doing it for the fun and challenge of the learning experience. But I may be out of my depth at this point, I've exhausted my barely-passable knowledge when it comes to this stuff.
Thanks for any comments or guidance you can provide!
Thanks to all for your help. I've come to believe the issues were hardware related, and have returned the phone.

matt314159 said:
Wondering if I can get somebody to weigh in on this one. Trying to help a friend of a friend out--I don't know the back story of what happened to this, but sounded like a 'bricked his phone doing dangerous things without enough knowledge' kind of situation.
The phone is stuck in a boot loop, just the HTC wordmark on a white background. You can enter the bootloader just fine, and fastboot can read and send commands just fine, flash recovery just fine, etc. The device cannot, however, enter recovery mode. It just says "entering recovery..." at the top, with the same HTC wordmark and white background. It displays for 30 seconds, then the screen goes black for 4-5 seconds, then back to the HTC logo.
Some info about the phone:
AT&T HTC One M7
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: [redacted]
imei: [redacted]
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3838mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Things I have tried already:
The first thing I did was I re-locked the bootloader and flashed the RUU exe, thinking that might be the quickest fix. The exe took the expected length of time and said it was successful, and rebooted the phone.
Still looping.
I then got the unlock token, unlocked the bootloader again, erased the cache, and fastboot flashed CWM recovery-clockwork-6.0.4.3-m7att.img - Attempted to reboot to recovery.
Still looping.
Cleared the cache, flashed openrecovery-twrp-2.7.1.1-m7.img - Attempted to reboot to recovery.
Still looping.
What's Next?
So that's about where I am now, I have functional bootloader and fastboot, but something is corrupted and I just absolutely can't get into recovery no matter what I try. I really thought the RUU would be a simple way to fix it, and was surprised when it didn't work.
From the reading I've done it sounds like there's some sort of emmc partition corruption possibly? Am I going in the right direction? I did post the fastboot getvar all results above--perhaps that can tip somebody off? I don't know quite enough to be able to spot trouble there at a glance, unfortunately.
I don't personally have a lot invested in getting this running, its owner already replaced it and I'm just doing it for the fun and challenge of the learning experience. But I may be out of my depth at this point, I've exhausted my barely-passable knowledge when it comes to this stuff.
Thanks for any comments or guidance you can provide!
Click to expand...
Click to collapse
Try to download TWRP 2.6.3.3 from here http://techerrata.com/browse/twrp2/m7 . When it has downloaded put it in your fastboot folder, plug your phone into your computer, open a command window, and type "fastboot devices" to make sure it recognizes your phone. If it doesn't you will need the drivers, if it does recognize it type "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" . That is the same file and procedure I just used a week ago, hope it helps you.

chuckwago88 said:
Try to download TWRP 2.6.3.3 from here http://techerrata.com/browse/twrp2/m7 . When it has downloaded put it in your fastboot folder, plug your phone into your computer, open a command window, and type "fastboot devices" to make sure it recognizes your phone. If it doesn't you will need the drivers, if it does recognize it type "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" . That is the same file and procedure I just used a week ago, hope it helps you.
Click to expand...
Click to collapse
Thanks for the suggestion, but it's still no joy: TWRP 2.6.3.3 acts the same as TWRP 2.7.1.1 and CWM 6.0.4.3
I'm starting to think this thing is toast.

matt314159 said:
Thanks for the suggestion, but it's still no joy: TWRP 2.6.3.3 acts the same as TWRP 2.7.1.1 and CWM 6.0.4.3
I'm starting to think this thing is toast.
Click to expand...
Click to collapse
I noticed that you have 3.17.502.3 firmware, you might try to flash this RUU 4.18.502.7 it is a higher version and might correct what I suspect is a mismatch between your version and the hboot. If this is successful, you might think about this AT&T 5.12.502.2 Guru Reset. Read the entire OP for both, it might give you some insight.

Hmm... With this RUU, I get as far as "Updating 1/5 Checking headers" at 5% and never any further. Thought I might just need to be more patient, so I left it through three episodes of Trailer Park Boys season 8, and a subsequent afternoon nap before powering off the handset and killing the windows process. Tried it again and it seems to be doing the same thing. The MD5 matched so I don't think it was a bad download, so I wonder if there are any workarounds.
I'm running windows 7 x64, have the proper drivers installed, HTC Sync has been removed, and I've used this PC successfully on another HTC One when I needed to get it back to factory stock to send in for warranty work just a couple of weeks ago. So I'm pretty sure it's nothing to do with my setup...

Can you find the same firmware (or extract from ota) and flash it?

matt314159 said:
Hmm... With this RUU, I get as far as "Updating 1/5 Checking headers" at 5% and never any further. Thought I might just need to be more patient, so I left it through three episodes of Trailer Park Boys season 8, and a subsequent afternoon nap before powering off the handset and killing the windows process. Tried it again and it seems to be doing the same thing. The MD5 matched so I don't think it was a bad download, so I wonder if there are any workarounds.
I'm running windows 7 x64, have the proper drivers installed, HTC Sync has been removed, and I've used this PC successfully on another HTC One when I needed to get it back to factory stock to send in for warranty work just a couple of weeks ago. So I'm pretty sure it's nothing to do with my setup...
Click to expand...
Click to collapse
Those 4.xx.502 RUU are crap...
Are you sure the 3.x.502 RUU completed ? I have never seen a phone bootloop after flashing that RUU.

clsA said:
Are you sure the 3.x.502 RUU completed ? I have never seen a phone bootloop after flashing that RUU.
Click to expand...
Click to collapse
Fairly sure, anyway? It takes the expected length of time (about 10 minutes), the progress bars march through their steps on the computer screen and phone screen, and the RUU exe congratulates me and says it's going to reboot the phone now when it's finished.
Can I try fastboot flashing a zip RUU, or does it require S-Off for that?

matt314159 said:
Fairly sure, anyway? It takes the expected length of time (about 10 minutes), the progress bars march through their steps on the computer screen and phone screen, and the RUU exe congratulates me and says it's going to reboot the phone now when it's finished.
Can I try fastboot flashing a zip RUU, or does it require S-Off for that?
Click to expand...
Click to collapse
it's no different ..if the EXE RUU worked and your still in bootloop you have a corrupt partition and will need expert advice. Maybe @nkk71 will have some time to help you

clsA said:
it's no different ..if the EXE RUU worked and your still in bootloop you have a corrupt partition and will need expert advice. Maybe @nkk71 will have some time to help you
Click to expand...
Click to collapse
Okay, thanks. I'm going to be taking this back to my colleague at work tomorrow, so I probably don't want nkk71 to spend much time on it unless he thinks it's something quick I can do tonight to get it running again.
Just on a lark, I also flashed twrp-recovery-2.7-m7-nobcb.img from This thread.--no change. Although my symptoms were different, it sounded like it might be worth a shot, but no dice.

matt314159 said:
Okay, thanks. I'm going to be taking this back to my colleague at work tomorrow, so I probably don't want nkk71 to spend much time on it unless he thinks it's something quick I can do tonight to get it running again.
Just on a lark, I also flashed twrp-recovery-2.7-m7-nobcb.img from This thread.--no change. Although my symptoms were different, it sounded like it might be worth a shot, but no dice.
Click to expand...
Click to collapse
@clsA is quite right about those 4.xx RUUs, they do work, but are very sensitive (for lack of a better word), about PC configuration, USB ports, etc... no clue what is the defining problem.
though all this sounds strange indeed, usually when the emmc is fried, "fastboot oem rebootRUU" will throw an error.
can you extract the ROM.ZIP from the 3.17.502.3 RUU.EXE and try flashing it using fastboot commands:
run the RUU.EXE, once you're at the welcome screen, it would have extracted all the files into %TEMP%/<weird long numbered folder name> (use sort by date modified to find the newest folders), in it you should find a 1.5GB or so ROM.ZIP <- that's an encrypted/signed ruu.zip) copy it to your fastboot folder, exit the RUU.EXE, and flash the ROM.ZIP (it will give a lot more output):
relock bootloader (since you are S-On):
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice, the first one only does the hboot preupdate
fastboot reboot-bootloader
and copy/paste the command prompt output here, make sure to set the command prompt buffer size to a large enough size (at least 500+ lines)
obviously, if we had some background as to what happened previously, it would/could help too

nkk71 said:
@clsA is quite right about those 4.xx RUUs, they do work, but are very sensitive (for lack of a better word), about PC configuration, USB ports, etc... no clue what is the defining problem.
though all this sounds strange indeed, usually when the emmc is fried, "fastboot oem rebootRUU" will throw an error.
can you extract the ROM.ZIP from the 3.17.502.3 RUU.EXE and try flashing it using fastboot commands:
run the RUU.EXE, once you're at the welcome screen, it would have extracted all the files into %TEMP%/<weird long numbered folder name> (use sort by date modified to find the newest folders), in it you should find a 1.5GB or so ROM.ZIP <- that's an encrypted/signed ruu.zip) copy it to your fastboot folder, exit the RUU.EXE, and flash the ROM.ZIP (it will give a lot more output):
relock bootloader (since you are S-On):
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice, the first one only does the hboot preupdate
fastboot reboot-bootloader
and copy/paste the command prompt output here, make sure to set the command prompt buffer size to a large enough size (at least 500+ lines)
obviously, if we had some background as to what happened previously, it would/could help too
Click to expand...
Click to collapse
Thank you for the clear instructions. I followed them over my lunch hour. My only problem was getting the command prompt buffer to stick, I changed it to 999 but it kept truncating the output anyhow. So I ran the commands a second time and snagged the output a few times throughout the process and cobbled it back together.
Here's the output at pastebin: http://pastebin.com/dNKaKKtd (note that it does not show the lock command as this was the second iteration that I captured)
presently, the phone is still looping.
I still have the phone for another night, so I'll keep going with this if you have more suggestions or instructions.
Many Thanks!

matt314159 said:
Thank you for the clear instructions. I followed them over my lunch hour. My only problem was getting the command prompt buffer to stick, I changed it to 999 but it kept truncating the output anyhow. So I ran the commands a second time and snagged the output a few times throughout the process and cobbled it back together.
Here's the output at pastebin: http://pastebin.com/dNKaKKtd (note that it does not show the lock command as this was the second iteration that I captured)
presently, the phone is still looping.
I still have the phone for another night, so I'll keep going with this if you have more suggestions or instructions.
Many Thanks!
Click to expand...
Click to collapse
Well that output looks just fine, the ruu is successfully flashed, and has put everything back to stock. So unfortunately i can't really think of anything else, my only two guesses would be:
1- hardware problem
2- if he did flash something into p19 (the active cmdline overflow error), then maybe try the older cwm 6.0.2.8 recovery which seems to sometimes work for s-on users
you should first try to find out from your friend if this was the result of him flashing something, or if it happened by itself (in the latter case, it would be a hardware problem for sure)

nkk71 said:
Well that output looks just fine, the ruu is successfully flashed, and has put everything back to stock. So unfortunately i can't really think of anything else, my only two guesses would be:
1- hardware problem
2- if he did flash something into p19 (the active cmdline overflow error), then maybe try the older cwm 6.0.2.8 recovery which seems to sometimes work for s-on users
you should first try to find out from your friend if this was the result of him flashing something, or if it happened by itself (in the latter case, it would be a hardware problem for sure)
Click to expand...
Click to collapse
Thanks so much for your help! Nothing ended up working, so I gave the phone back. My colleague wasn't sure the history of it, but I'm willing to bet hardware issue. I appreciate your guidance, though! This was good learning experience for me. I feel a lot more at home with a lot of the basic fastboot commands and that kind of thing, so it wasn't a total loss on my part. I'm usually having to look up tutorials just to remember basic syntax!
Anyway thanks to all who chimed in. If mods want, they can close this thread, otherwise I'll just let it sink to its grave.

[Q] Help...can't make/receive calls (Andriod 5.02 / Rev. 90.1)

Hi there,
I bought a 2nd hand phone [HTC M7] off ebay with Revolution 90.1 / Android 5.02 / Build No. 7.15.401.1
Everything works great...but I can't make or receive calls. I figured this was the same issue that struck HTC phones in Dec, but from my understanding 7.15.401.1 is more recent than the official HTC fix (6.10.531.10) & Rev. 90.1 already has this fix included also. I've also installed Viperone 7.02 (fix incl.), but no difference, so I'm now back to Rev. 90.1. I've also cleared google caches, froze HTC lockscreen etc etc but now I've run out of ideas.
Can anybody help?!
Thanks..!

Dial tone on a mobile phone... Whaaat? Bring the phone to your service provider, which is advice I never really give out, but from what you wrote, I think your missing something, like installing the SIM card or provisioning the phone correctly. Do you even have service and signal on it?
Sent from my HTC One using Tapatalk

synt3k said:
Dial tone on a mobile phone... Whaaat? Bring the phone to your service provider, which is advice I never really give out, but from what you wrote, I think your missing something, like installing the SIM card or provisioning the phone correctly. Do you even have service and signal on it?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Sorry - Dial tone meaning when I call I don't hear a ring [orig post now edited].
Data/Wifi works & I get signal. If people call me my phone rings, I can pick up but then silence

Tinky24 said:
Sorry - Dial tone meaning when I call I don't hear a ring [orig post now edited].
Data/Wifi works & I get signal. If people call me my phone rings, I can pick up but then silence
Click to expand...
Click to collapse
can you post the fastboot getvar all of the phone please, remove imei and serial number before posting

Seanie280672 said:
can you post the fastboot getvar all of the phone please, remove imei and serial number before posting
Click to expand...
Click to collapse
:
I can't get Min. Adb & Fastboot to see my device [ adb devices just prints "List of Devices" then a blank line], which suggests I'm missing drivers
I've done both routes suggested on technobuzz.net/fastest-easiest-method-setup-adb-fastboot-windows/ and no luck. I've uninstalled and reinstalled my HTC m7 drivers, to no avail.

Tinky24 said:
:
I can't get Min. Adb & Fastboot to see my device [ adb devices just prints "List of Devices" then a blank line], which suggests I'm missing drivers
I've done both routes suggested on technobuzz.net/fastest-easiest-method-setup-adb-fastboot-windows/ and no luck. I've uninstalled and reinstalled my HTC m7 drivers, to no avail.
Click to expand...
Click to collapse
which version of windows are you using ?
also have a look in device manager whislt your phone is plugged in and phone in bootloader with fastbootUSB showing on the screen, see if device manager is seeing your device, it should say MyHTC under Android Devices (post a pict of device manager if possible)
fastboot commands only whilst in bootloader, adb wont work, adb is only for booted rom and recovery.
Just had a look at the link you posted, The adb and fastboot files are fine, I use those ones myself, the drivers are probably too far out of date, download HTC sync manager and install it, then goto add remove programs and remove HTC sync only, you will see the driver package just above it, leave that there, then plug your phone in and try fastboot devices or fastboot getvar all again.

Seanie280672 said:
which version of windows are you using ?
also have a look in device manager whislt your phone is plugged in and phone in bootloader with fastbootUSB showing on the screen, see if device manager is seeing your device, it should say MyHTC under Android Devices (post a pict of device manager if possible)
fastboot commands only whilst in bootloader, adb wont work, adb is only for booted rom and recovery.
Just had a look at the link you posted, The adb and fastboot files are fine, I use those ones myself, the drivers are probably too far out of date, download HTC sync manager and install it, then goto add remove programs and remove HTC sync only, you will see the driver package just above it, leave that there, then plug your phone in and try fastboot devices or fastboot getvar all again.
Click to expand...
Click to collapse
Right, getting somewhere, thanks for clarifying the fastboot/adb difference:
fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main: 1.29.401.2
version-misc: PUT SHIP S-OFF
meid: 000000000000
product: my_url
platform: HBOOT-8064
modelid: PN710000
cidnum: 11111111
battery-status: good
battery-voltage: 4250mv
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
[Windows 7 btw]

Tinky24 said:
Right, getting somewhere, thanks for clarifying the fastboot/adb difference:
fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main: 1.29.401.2
version-misc: PUT SHIP S-OFF
meid: 000000000000
product: my_url
platform: HBOOT-8064
modelid: PN710000
cidnum: 11111111
battery-status: good
battery-voltage: 4250mv
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
[Windows 7 btw]
Click to expand...
Click to collapse
dont change to windows 8 you will have all sorts of problems due to your HBOOT, you are on a very early firmware there and as you are s-off, that helps alot, I think you really need to bring your phone back up to speed to be sure thats not whats causing the issues your having, bear with me whilst I find the link of 401 firmwares. (version-main: 1.29.401.2)
If there is anything on the phone you need to keep, pictures, photo's music etc, please back it up now as firmware flash can wipe the device in some cases.
OK heres the link to the firmwares, you need to flash them one at a time, starting with the earliest 2.24.401's then the 3xxxxxx's then the 4xxxxx's then the 5xxxxxx and finally the 6xxxxxx's,: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/ this issue you experiencing was fixed in the 7xxxxxx firmware which i'll find the link for shortly.
Do you know how to flash the firmware ?

Thanks so much.
I've found a guide

Tinky24 said:
Thanks so much.
Is it the same way as flashing a ROM i.e. Recovery > Install?
Click to expand...
Click to collapse
no, heres a good guide on how to do it: https://trjlive.com/guide-install-firmware-htc-one-m7/
if your phone is already in fastbootUSB mode, then skip the first 2 commands, also something not mentioned in the guide is the firmware.zip file MUST be in the same folder as your adb and fastboot files on your computer, when you download the firmware files (one at a time) they will be named as per the name on the site, just rename them to firmware.zip for ease, once you've finished flashing each one and the phone has finished booting, delete it and download the next then follow the prceedure once again.
your battery must be 50% or more before proceeding, but I can see yours is good at the moment at 4250mv
If you check yourself, no need to post each one, you should notice the version main number going up, the HBOOT version going up, you will also have stock recovery (a red triangle with an exclamation mark)
do not skip any steps and you'll be fine, report back after the first flash and let us know how it went, any problems, just ask.

Ok all done, getvar now gives me:
version-main: 6.09.401.12
HBOOT 1.57

Tinky24 said:
Ok all done, getvar now gives me:
version-main: 6.09.401.12
HBOOT 1.57
Click to expand...
Click to collapse
perfect, as long as it still says your s-off, ps, never go s-on, you'll regret it, you can do one of the following.
You can flash this firmware https://www.androidfilehost.com/?fid=95897840722644637 (unsigned) not official yet, but will work for you as your s-off, if you go s-on your phone will brick, and then test your rom, your issue should be fixed.
Or you can do this which is what I did: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311 This is official

I rebooted after finishing the v6 updates, then got the red triangle thing - do I now factory reset?
"can not mount SD card"

Tinky24 said:
I rebooted after finishing the v6 updates, then got the red triangle thing - do I now factory reset?
Click to expand...
Click to collapse
hold down the power button with the volume down, keep holding whilst the home and back bottuns on the bottom flash about 15 times, when they stop flashing, release the power button, but continue to hold down the volume down, the phone should boot to the bootloader, factory reset is in the list, use the volume button up / down to highlight it and power button to select, why do you want to factory reset ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
cannot mount sdcard is a normal error if you have entered recovery, there is no sdcard.

Sorry ignore the fact. reset bit.
I've now uploaded the last firmware zip you gave me. Can I just System reboot or is there something left to do?

Tinky24 said:
Sorry ignore the fact. reset bit.
I've now uploaded the last firmware zip you gave me. Can I just System reboot or is there something left to do?
Click to expand...
Click to collapse
yeah just system reboot, the lollipop rom's do really require Lollipop firmware which is what you just flashed in order toi work properly, your firmware was about 2 years out of date.

Reboot brings up the white HTC screen...then the screen returns to Stock Recovery Triangle...

Tinky24 said:
Reboot brings up the white HTC screen...then the screen returns to Stock Recovery Triangle...
Click to expand...
Click to collapse
The firmware flash may of messed up your rom, did you flash android revolution 90.1 yourself ?

No it came with Rev. Should I reflash it?

Tinky24 said:
No it came with Rev. Should I reflash it?
Click to expand...
Click to collapse
yes, or a rom of your choice, you will need a custom recovery first, so download this:
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
put your phone into fastbootUSB mode on the screen again by holding down the volume down and power button method again as I described earlier, this is the white screen not the black screen with silver HTC logo.
rename the download above to recovery.img and place it in the same folder as adb and fastboot again and with your phone plugged in issue these commands one at a time:
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery, as long as your drivers are working correctly, this recovery supports MTP so the computer should see the internal storage, just downlaod and copy the rom you want to flash straight to the internal storage, unplug your phone and install it, its recommended to install option with full wipe, dont worry, internal storage isnt touched, just wipes data and system.