Database Develop

[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] Specific RUU

Hello there! First: Thanks for every answer in return - I'm currently a little bit in a pitch...and appreciate any help.
My problem is: my HTC One is currently stuck in a bootloop, due do some (my own) failures, when I tried to use a ROM.
In my own idioty I didnt made any backups or anything else.
Long story short - I would like to try to install a RUU for my version, but there is absolutely noone.
I'm on version-main 1.29.111.16 with the CID T-MOB101 and HBoot 1.44. I tried to search everywhere possible for a download,
even tried to personal message a few people who maybe could have the needed RUU, but so far no answers / no luck.
Tried to get S-OFF and use another RUU, but whatever I do, I cannot see my device under "adb devices". Tried everything /latest driver, cables and so on) so far but it absolutely wont show under adb and so I cannot see any other way to get S- OFF. Thats why I rely on the RUU for my version. So im here to ask, if someone else could give me a hint on where to find this RUU...or any tips on getting my ONE S-off. But like I said, I guess I tried almost everything I have read about (countless hours on google and xda- forum).
I know, I may write complete and utter nonsense - toying with my precious phone was like the biggest failure in my last few months and I regret it. :l
Thanks in advance!
Greetings,
Linte

Linte said:
Hello there! First: Thanks for every answer in return - I'm currently a little bit in a pitch...and appreciate any help.
My problem is: my HTC One is currently stuck in a bootloop, due do some (my own) failures, when I tried to use a ROM.
In my own idioty I didnt made any backups or anything else.
Long story short - I would like to try to install a RUU for my version, but there is absolutely noone.
I'm on version-main 1.29.111.16 with the CID T-MOB101 and HBoot 1.44. I tried to search everywhere possible for a download,
even tried to personal message a few people who maybe could have the needed RUU, but so far no answers / no luck.
Tried to get S-OFF and use another RUU, but whatever I do, I cannot see my device under "adb devices". Tried everything /latest driver, cables and so on) so far but it absolutely wont show under adb and so I cannot see any other way to get S- OFF. Thats why I rely on the RUU for my version. So im here to ask, if someone else could give me a hint on where to find this RUU...or any tips on getting my ONE S-off. But like I said, I guess I tried almost everything I have read about (countless hours on google and xda- forum).
I know, I may write complete and utter nonsense - toying with my precious phone was like the biggest failure in my last few months and I regret it. :l
Thanks in advance!
Greetings,
Linte
Click to expand...
Click to collapse
There is a Guru reset here
http://www.htc1guru.com/downloads/stock-rom-downloads/
Read the instructions on how to flash
http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
Sent from my HTC One using Xparent Skyblue Tapatalk 2

Thanks for the fast reply.
The problem is: I cannot get into recovery. I tried to flash the the recovery and the boot via fastboot from the corrospending
Guru, but I'll only get an "signature verify fail" error. I hoped for the fitting RUU- version for my 1.29.111.16, because it seems
to me that it may be the easiest solution for my problem.
Greetings,
Linte

Hi. Can you post your actual command and output?

SaHiLzZ said:
Hi. Can you post your actual command and output?
Click to expand...
Click to collapse
Hey! Sorry for the delayed anwser (was on a short holiday trip),
I tired almost everything possible, as far as I know. So far I tried to flash allmost everything, from the .img (recovery/boot/) inside the Guru, wich bored_stupid sent me in his post, aswell as the whole .zip.
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\adb>fastboot flash recovery rec.zip
error: cannot open 'rec.zip'
C:\adb>fastboot flash recovery rec.img
sending 'recovery' (9136 KB)...
OKAY [ 1.121s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.062s
C:\adb>fastboot flash rom Guru.zip
sending 'rom' (1056149 KB)...
OKAY [ 41.443s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1174.768s
Click to expand...
Click to collapse
No matter what I try, I always get this "signature verify fail"- error. Thats why I was hoping for someone with the mentioned RUU, because they seem to work so far - except my HTC says something similiar: "RUU Error [132]: Signature error."
Greetings,
Linte
Btw, here's my getvar, in case it's needed:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4D.14.3250.26
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.111.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4252mV
(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.043s
C:\adb>
Click to expand...
Click to collapse

First of all, your drivers are missing or outdated, download HTC sync manager from the HTC site and install, then remove HTC sync from your computer, just leaving the drivers.
Next question is do you have usb debugging enabled on the phone in developer options ?
If you can't see developer options then goto menu, settings, about, software information, more, then tap build number 7 times, it should say you are now a developer and you will have a new menu in settings called developer options where you can enable usb debugging.
When you type adb devices it should list your phone's serial number not just say list of devices attached.
It could also be that you need to update your adb and fastboot, I had to do it recently after getting this phone, after using the same fastboot and adb for years.

Seanie280672 said:
First of all, your drivers are missing or outdated, download HTC sync manager from the HTC site and install, then remove HTC sync from your computer, just leaving the drivers.
Next question is do you have usb debugging enabled on the phone in developer options ?
If you can't see developer options then goto menu, settings, about, software information, more, then tap build number 7 times, it should say you are now a developer and you will have a new menu in settings called developer options where you can enable usb debugging.
When you type adb devices it should list your phone's serial number not just say list of devices attached.
It could also be that you need to update your adb and fastboot, I had to do it recently after getting this phone, after using the same fastboot and adb for years.
Click to expand...
Click to collapse
Again sorry for the late reply, business struck again. :l
To your points: Already installed the latest HTC drivers from their homepage more than four times so far. Im pretty sure I have the latest version and after installing, I deinstalled the Sync Manager, like you told me to do. Still no changes.
I cannot see any developer options, simply because I can't get any further than the bootscreen. Im stuck within a bootloop.
Also I got the latest fastboot and adb from the (SDK- Manager) Android Developer Tools- Bundle. That's why I am so clueless about my phone not getting recognized by my PC with "adb devices". Strange thing is, I get the ID of my phone in "fastboot devices"...
Later this da I will try to connect my phone to my new, clean Laptop, with the lastest HTC Drivers and adb/fastboot. Maybe this will help.
Thanks so far!
Linte
Edit: tried it with a clean Laptop, latest ADB, latest HTC Sync (installed and deinstalled) and different USB- slots. No success. Adb sill only says
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
Absoluteley no clue where I go wrong here... :l

Linte said:
Hey! Sorry for the delayed anwser (was on a short holiday trip),
I tired almost everything possible, as far as I know. So far I tried to flash allmost everything, from the .img (recovery/boot/) inside the Guru, wich bored_stupid sent me in his post, aswell as the whole .zip.
No matter what I try, I always get this "signature verify fail"- error. Thats why I was hoping for someone with the mentioned RUU, because they seem to work so far - except my HTC says something similiar: "RUU Error [132]: Signature error."
Greetings,
Linte
Btw, here's my getvar, in case it's needed:
Click to expand...
Click to collapse
I'm assuming your using Windows 8 or 8.1. They have an issue with hboot 1.44. Can you use a PC with Windows 7 or read here to make a Ubuntu USB live OS
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using Xparent Skyblue Tapatalk 2

bored_stupid said:
I'm assuming your using Windows 8 or 8.1. They have an issue with hboot 1.44. Can you use a PC with Windows 7 or read here to make a Ubuntu USB live OS
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Hmm...nope. So far I have only used Windows 7. But like I said, no progress at all. Everythings updated, even on a freshly installed system. Different USB- Ports and so on. No success... :l

Tried to get S-OFF and use another RUU
Click to expand...
Click to collapse
You need a working rom to s-off the phone.
simply because I can't get any further than the bootscreen. Im stuck within a bootloop.
Click to expand...
Click to collapse
Linte said:
Code:
C:\adb>[B][COLOR="Red"]adb devices[/COLOR][/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
ADB commands only works from a booted OS with usb debugging ON or from custom recovery. So ADB will never output your device is connected if you are not in the OS or in custom recovery. From bootloader, use FASTBOOT commands
i.e:
Code:
fastboot devices
Code:
C:\adb>fastboot flash recovery rec.img
sending 'recovery' (9136 KB)...
OKAY [ 1.121s]
writing 'recovery'...
(bootloader) signature checking...
FAILED[B][COLOR="Red"] (remote: signature verify fail)[/COLOR][/B]
finished. total time: 2.062s
Click to expand...
Click to collapse
Looks like your bootloader is locked, you need an unlocked bootloader to flash the recovery partition
Code:
[COLOR="Red"][B]C:\adb>fastboot flash rom Guru.zip[/B][/COLOR]
sending 'rom' (1056149 KB)...
OKAY [ 41.443s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1174.768s
Click to expand...
Click to collapse
This one is a custom rom (reset rom). You can't flash custom rom from fastboot. You can only flash custom rom from custom recovery.
from fastboot, all you can do is
flashing a custom recovery (with bootloader unlocked)
flashing a RUU.zip in ruu mode
flashing a firmware.zip in ruu mode
all roms (except RUUs) are flashed from custom recovery, including guru reset roms.
btw, there is no RUU for your phone.
unlock bootloader
flash twrp recovery 2.6.3.3
download and save this file to the same folder you have adb and fastboot in
open a cmd prompt from you fastboot/adb folder and boot your phone in bootloader mode (fastboot usb)
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb push the guru reset rom to your /sdcard/ from twrp recovery
download this guru reset rom: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/ and save it to your adb/fastboot folder
boot phone in twrp recovery
open a cmd prompt form your adb/fastboot folder
Code:
adb push guru_reset_m7_2.24.111.3.zip /sdcard/
wait for the file to transfer (5-10 min, there is no progress bar, just wait until adb says it complete)
install the reset rom using twrp

Wow! Thanks a lot!
After unlocking my bootloader again I was able to get into recovery. From there it was easy going to install the Guru.zip via sideload ("Install zip" didnt work for some reason, said something similiar to "Couldn't mount /sdcard/". But sideload worked fine.). Updated everything and my phone runs now like it always had!
Again: really, really thanks a bunch! Thought I somehow ruined my phone, but thanks to you all I got it done. I really appreciate your effort in helping me! You guys are awesome.
Greetings,
Linte
PS: I won't do anything stupid with my phone again, learnd this the hard way.

[Q] HELP! Deleted internal storage and adb doesn't work

So I really messed up my htc one. I flashed a kernel and as I rebooted stuck on the bootscreen. Then I wiped out everything (internal storage) and now adb doesn't work anymore, I can access fastboot and recovery though (twrp) .
Can't do anything no sideload no adb commands at all, because my pc doesn't recognize the phone! fastboot commands seem to work.
can anyone help me?

zabtos said:
So I really messed up my htc one. I flashed a kernel and as I rebooted stuck on the bootscreen. Then I wiped out everything (internal storage) and now adb doesn't work anymore, I can access fastboot and recovery though (twrp) .
Can't do anything no sideload no adb commands at all, because my pc doesn't recognize the phone! fastboot commands seem to work.
can anyone help me?
Click to expand...
Click to collapse
first install drivers so ADB can be used when your phone is booted in twrp recovery
then adb push or adb sideload a rom to your phone and install it using twrp. note that most newer rom will require twrp 2.6.3.3 or 2.6.3.4 to flash correctly.

alray said:
first install drivers so ADB can be used when your phone is booted in twrp recovery
then adb push or adb sideload a rom to your phone and install it using twrp. note that most newer rom will require twrp 2.6.3.3 or 2.6.3.4 to flash correctly.
Click to expand...
Click to collapse
Hey first thanks for your answer
so I already have installed htc sync aren't there drivers included? or do I need to download them seperately ?

zabtos said:
Hey first thanks for your answer
so I already have installed htc sync aren't there drivers included?
Click to expand...
Click to collapse
yes
boot your phone in twrp recovery (main menu)
what is the output of:
Code:
adb devices
?

alray said:
yes
boot your phone in twrp recovery (main menu)
what is the output of:
Code:
adb devices
?
Click to expand...
Click to collapse
Code:
C:\fastboot>adb devices
List of devices attached
maybe this will help you a bit
Code:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s

zabtos said:
Code:
C:\fastboot>adb devices
List of devices attached
Click to expand...
Click to collapse
update your adb and fastboot using this then see if it works: http://forum.xda-developers.com/showthread.php?t=2317790

Seanie280672 said:
update your adb and fastboot using this then see if it works: http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
installed it, but same problem
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
if I just could get adb to work then I could flash a new rom

zabtos said:
installed it, but same problem
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
if I just could get adb to work then I could flash a new rom
Click to expand...
Click to collapse
could try running this RUU to get back to stock to start with http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Just noticed something, uninstall HTC sync, it interferes, in the uninstall list on your computer, you should see HTC drivers just below HTC sync, its a separate application, leave the drivers, loose sync.

zabtos said:
installed it, but same problem
Click to expand...
Click to collapse
You need different hardware drivers to connect via ADB when in twrp vs. the OS because the device presents different devices id to the OS for each.
I use the drivers for the old Galaxy Nexus, download them here: http://www.samsung.com/us/support/owners/product/GT-I9250TSGGEN
Edit: actually, it's this driver: gnex_fastboot_driver_0.72.zip

ok I tried to istall the ruu, but it fails at the beginning: htc_fastboot.exe doesn't work anymore
uninstalled sync kept the drivers, but the phone is still not recognized
You need different hardware drivers to connect via ADB when in twrp vs. the OS because the device presents different devices id to the OS for each.
I use the drivers for the old Galaxy Nexus, download them here: http://www.samsung.com/us/support/ow...GT-I9250TSGGEN
Click to expand...
Click to collapse
and keep htc drivers or unistall them?
Edit: link doesn't work

zabtos said:
ok I tried to istall the ruu, but it fails at the beginning due fastboot connection lost
I will try to uninstall sync and keep the drivers as you mentioned or then the galaxy ones
Click to expand...
Click to collapse
if the above don't work:
go in nkk71's thread (link in my signature), refer to the FAQ, there is a guide to fix drivers.

alray said:
if the above don't work:
go in nkk71's thread (link in my signature), refer to the FAQ, there is a guide to fix drivers.
Click to expand...
Click to collapse
Seems it won't work since I have only a win 8 desktop and win 8.1 laptop

zabtos said:
Seems it won't work since I have only a win 8 desktop and win 8.1 laptop
Click to expand...
Click to collapse
Grab Ubuntu live CD or USB and run from that, no need to install.

Seanie280672 said:
Grab Ubuntu live CD or USB and run from that, no need to install.
Click to expand...
Click to collapse
will try it, give you the results after that

best way ive found to get out of this rut as ive been in it a few times. i bought a OTG cable for like $1.20 off amazon and i keep a flash drive with a stock like ROM and kernel on it aswell as some recoveries. Best thing i have ever purchased saved my ass a many of times.
then in twrp you go to flash and swap form internal storage to usb otg and tada can flash from the flash drive.
then you should be able to workout the adb issue while you have a functioning phone atleast lol.

Sieze said:
best way ive found to get out of this rut as ive been in it a few times. i bought a OTG cable for like $1.20 off amazon and i keep a flash drive with a stock like ROM and kernel on it aswell as some recoveries. Best thing i have ever purchased saved my ass a many of times.
then in twrp you go to flash and swap form internal storage to usb otg and tada can flash from the flash drive.
then you should be able to workout the adb issue while you have a functioning phone atleast lol.
Click to expand...
Click to collapse
hey sry I've never done this before, could u explain this more in detail (for idiots like me^^) and I just need this otg cable and nothing more?

you need an otg cable and a flash drive, and of course have TWRP installed on device.
boot phone into recovery
plug in the otg cable to the phone
plug in the flash drive with the files you want to flash on it.
in twrp tap install
tab the top grey rectangle that says Storage: Internal Storage
then select usb otg
Click ok then select the file to flash

Sieze said:
you need an otg cable and a flash drive, and of course have TWRP installed on device.
boot phone into recovery
plug in the otg cable to the phone
plug in the flash drive with the files you want to flash on it.
in twrp tap install
tab the top grey rectangle that says Storage: Internal Storage
then select usb otg
Click ok then select the file to flash
Click to expand...
Click to collapse
It worked! Installed stock rom and adb works too! Special thanks to you Sieze and to all others !

Sieze said:
you need an otg cable and a flash drive, and of course have TWRP installed on device.
boot phone into recovery
plug in the otg cable to the phone
plug in the flash drive with the files you want to flash on it.
in twrp tap install
tab the top grey rectangle that says Storage: Internal Storage
then select usb otg
Click ok then select the file to flash
Click to expand...
Click to collapse
zabtos said:
It worked! Installed stock rom and adb works too! Special thanks to you Sieze and to all others !
Click to expand...
Click to collapse
Not sure if you know about these but their really handy
http://www.amazon.com/Sony-Microvau..._m=ATVPDKIKX0DER&pf_rd_r=19AC0VZ1336AX2H0HW23
http://www.amazon.com/Kingston-16GB...pc&ie=UTF8&qid=1403956393&sr=1-3&keywords=OTG
http://www.amazon.com/gp/product/B0...pf_rd_t=3201&pf_rd_p=1774862022&pf_rd_i=typ03

hey so I got another problem. When I try to install a ruu it fails because htc_fastboot.exe has stopped working. On my other pc it just freezes at 5% .
I downloaded a new android sdk with adb and fastboot but the same error occured.

HTC M7 - Tried to root (Installed TWRP) but now phone won't boot

I tried to use this guide to on htconeroot
Got to installing the zip for SuperSU v1.30
The phone rebooted but it said SuperSU failed
Tried to install Update Super SU v2.46
Phone no longer reboots. It shows the white HTC One loading screen but then just goes very dark grey forever.
I can still access the white menu that comes up when you hold volume down and power
Can also access the TWRP screen, however I tried factory reset there and it didn't change, it still won't boot.
Can't take out sd or battery as metal case
Anyway not sure if this is meant to be in the HTC M7 category, a TWRP category, Rooting one.
I'm not sure if it is because the guide was for 4.3 and on 5.02 or what.
I also held the power off button when it was doing some things which may have also caused it
I don't really care about it being rooted so much as having my phone back. The only reason I wanted it rooted was to install the camera change that is supposed to get rid of the green tint.
Anyway thank you for your time. And I appreciate any assistance that can be given. I have spent hours trying to figure it out, but I am still confused and figure I am likely to screw it up even more

Syrup4 said:
I tried to use this guide to on htconeroot
Got to installing the zip for SuperSU v1.30
The phone rebooted but it said SuperSU failed
Tried to install Update Super SU v2.46
Phone no longer reboots. It shows the white HTC One loading screen but then just goes very dark grey forever.
I can still access the white menu that comes up when you hold volume down and power
Can also access the TWRP screen, however I tried factory reset there and it didn't change, it still won't boot.
Can't take out sd or battery as metal case
Anyway not sure if this is meant to be in the HTC M7 category, a TWRP category, Rooting one.
I'm not sure if it is because the guide was for 4.3 and on 5.02 or what.
I also held the power off button when it was doing some things which may have also caused it
I don't really care about it being rooted so much as having my phone back. The only reason I wanted it rooted was to install the camera change that is supposed to get rid of the green tint.
Anyway thank you for your time. And I appreciate any assistance that can be given. I have spent hours trying to figure it out, but I am still confused and figure I am likely to screw it up even more
Click to expand...
Click to collapse
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.

mb_guy said:
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.
Click to expand...
Click to collapse
Thank you very much for responding.
I am not sure what a nandroid backup is. I was following a guide.
I copied every file on phone to my computer via the file manager. And I used the command prompt and typed in "adb backup -apk -all -f backup.ab". I am not sure if that is the right kind.
I don't know how to post that output you asked for. I googled it, but it sounded like I needed to use my computer, and my computer no longer recognizes my phone due to it not booting. Or is that done in TWRP? Thank you again.
PS: htconeroot .com /htc-one-root/how-to-root-htc-one-windowsmaclinux/ is the guide I was following. Got up to install SU before it went bad. In case it helps. I can't properly link as I haven't made enough posts.

Syrup4 said:
Thank you very much for responding.
I am not sure what a nandroid backup is. I was following a guide.
I copied every file on phone to my computer via the file manager. And I used the command prompt and typed in "adb backup -apk -all -f backup.ab". I am not sure if that is the right kind.
I don't know how to post that output you asked for. I googled it, but it sounded like I needed to use my computer, and my computer no longer recognizes my phone due to it not booting. Or is that done in TWRP? Thank you again.
PS: htconeroot .com /htc-one-root/how-to-root-htc-one-windowsmaclinux/ is the guide I was following. Got up to install SU before it went bad. In case it helps. I can't properly link as I haven't made enough posts.
Click to expand...
Click to collapse
A nandroid backup is actually made with in twrp, read up on for future.
You obviously have adb installed since you used it for backup.
Put the phone in bootloader mode, restart holding down power and volume down. (have you not gone into twrp?) Then plug in usb and you should see "fastboot usb"
then from the adb folder type "fastboot getvar all"
Do some google searching there are dozens of articles regarding flashing htc one and using adb and fastboot commands phone bootloader and recovery .

Delete please, forgot to quote/ reply.

mb_guy said:
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.
Click to expand...
Click to collapse
Hello, thanks again. is this what you were referring to posting?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.661.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Removed
(bootloader) imei: Removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s

Syrup4 said:
Hello, thanks again. is this what you were referring to posting?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.661.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
When posting a "fastboot getvar all" edit out your imei and serialno, don't post these 2 numbers on the forum (edit your above post and remove them).
You should be able to restore your phone by flashing the 7.17.631.7 7.17.661.7 RUU. You'll first need to edit your MISC partition to change your version-main from 7.17.661.35 to 7.17.661.7 then relock your bootloader and flash the RUU. Once done, you'll have to install 2 ota updates so your phone is back to the 7.17.661.35 version. When back on this version, re-unlock your bootloader, re-flash twrp and flash supersu version 2.46 (any version lower than that will not work on lollipop)
Instructions how to change your version-main at the end of post #2 of this thread (see "how to downgrade with s-on")
The RUU and instructions how to flash it in the same thread at post #1

alray said:
When posting a "fastboot getvar all" edit out your imei and serialno, don't post these 2 numbers on the forum (edit your above post and remove them).
You should be able to restore your phone by flashing the 7.17.631.7 RUU. You'll first need to edit your MISC partition to change your version-main from 7.17.631.35 to 6.17.631.7 then relock your bootloader and flash the RUU. Once done, you'll have to install 2 ota updates so your phone is back to the 7.17.631.35 version. When back on this version, re-unlock your bootloader, re-flash twrp and flash supersu version 2.46 (any version lower than that will not work on lollipop)
Instructions how to change your version-main at the end of post #2 of this thread (see "how to downgrade with s-on")
The RUU and instructions how to flash it in the same thread at post #1
Click to expand...
Click to collapse
Thank you very much. Both for the help fixing it, and letting me know to remove that info. I read the instructions however given that it won't boot. My computer won't recognize it to transfer the tool (Misc_Tool_1.00.zip) over, so I can install it in TWRP. I tried pushing it using a command with adb. But it said Device not found. Given it has no removable SD card I do not know how to move it. The manual one also required adb shell, which says device not found. I shall continue looking things up in the mean time.
Edit: Strangely HTC Sync manager pops up when it does fail to boot if I restart the phone. Given it is set to do so when the phone is plugged in. However it always says "no phone connected". As if it recognizes it for a second then stops.

Syrup4 said:
Thank you very much. Both for the help fixing it, and letting me know to remove that info. I read the instructions however given that it won't boot. My computer won't recognize it to transfer the tool (Misc_Tool_1.00.zip) over, so I can install it in TWRP. I tried pushing it using a command with adb. But it said Device not found. Given it has no removable SD card I do not know how to move it. The manual one also required adb shell, which says device not found. I shall continue looking things up in the mean time.
Edit: Strangely HTC Sync manager pops up when it does fail to boot if I restart the phone. Given it is set to do so when the phone is plugged in. However it always says "no phone connected". As if it recognizes it for a second then stops.
Click to expand...
Click to collapse
First thing you want when using adb or fastboot commands is to make sure HTC Sync is not installed or your computer because it can interfere with adb/fastboot connectivity. So go ahead and uninstall it (not closing it, uninstall for real) don't uninstall the drivers btw.
Make sure you have the latest htc drivers installed, that you are using a good usb cable (preferably the original cable or any other cable already known to work with data transfer as opposed to usb cables that can only provide power). Make sure you are using a usb 2.0 port on your computer at the back of your tower (not using front ports neither an external usb hub). Finally, adb commands will only work when booted in twrp recovery, they will not work when in bootloader mode as opposed to fastboot commands which only works in bootloader.
If using the commands to change your version-main, better to post it here before so I can confirm its the correct one. A simple typo in this command could make the situation worse (i.e: corrupting your misc partition).

alray said:
First thing you want when using adb or fastboot commands is to make sure HTC Sync is not installed or your computer because it can interfere with adb/fastboot connectivity. So go ahead and uninstall it (not closing it, uninstall for real) don't uninstall the drivers btw.
Make sure you have the latest htc drivers installed, that you are using a good usb cable (preferably the original cable or any other cable already known to work with data transfer as opposed to usb cables that can only provide power). Make sure you are using a usb 2.0 port on your computer at the back of your tower (not using front ports neither an external usb hub). Finally, adb commands will only work when booted in twrp recovery, they will not work when in bootloader mode as opposed to fastboot commands which only works in bootloader.
If using the commands to change your version-main, better to post it here before so I can confirm its the correct one. A simple typo in this command could make the situation worse (i.e: corrupting your misc partition).
Click to expand...
Click to collapse
Hello, thank you again.
I uninstalled sync. I am using the original cable, and have now plugged it in to a USB 2.0 port on the back.
I also tried to use the commands while the phone is on the TWRP screen. The one with a grey background and big touch buttons with blue on them that say "Install" "Wipe" "Backup" etc.
But it still won't recognize my device. I can type in ADB to get a list of commands.
But when I try to push anything, it says "error: device not found"
I tried the command "adb get-serialno" to see if other commands worked but it said "unknown".
Edit: Got it to show up as a device when in Fastboot USB. However it won't show up as a drive in mycomputer. ADB won't recognize it in either that mode or on TWRP. And once I access TWRP, it changes to android phone" as shown in the second pic.
{
"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"
}

Syrup4 said:
Hello, thank you again.
I uninstalled sync. I am using the original cable, and have now plugged it in to a USB 2.0 port on the back.
I also tried to use the commands while the phone is on the TWRP screen. The one with a grey background and big touch buttons with blue on them that say "Install" "Wipe" "Backup" etc.
But it still won't recognize my device. I can type in ADB to get a list of commands.
But when I try to push anything, it says "error: device not found"
I tried the command "adb get-serialno" to see if other commands worked but it said "unknown".
Edit: Got it to show up as a device when in Fastboot USB. However it won't show up as a drive in mycomputer. ADB won't recognize it in either that mode or on TWRP. And once I access TWRP, it changes to android phone" as shown in the second pic.
Click to expand...
Click to collapse
When you're in TWRP are you sure you don't see the device as a disk drive, the newer versions of twrp support mtp which allows this. You should be able just to copy paste from you PC to the device. It looks to me this is working from your second picture.

mb_guy said:
It looks to me this is working from your second picture.
Click to expand...
Click to collapse
same. Maybe re-installing the latest drivers version wouldn't hurt...

alray said:
same. Maybe re-installing the latest drivers version wouldn't hurt...
Click to expand...
Click to collapse
mb_guy said:
When you're in TWRP are you sure you don't see the device as a disk drive, the newer versions of twrp support mtp which allows this. You should be able just to copy paste from you PC to the device. It looks to me this is working from your second picture.
Click to expand...
Click to collapse
Thanks once again both of you. But even though it seems like it should be listed. It is not. And if I right click on the device that appears, it is greyed out.
Which drivers? HTC ones? Android ones? or the Universal ADB (Android Debug Bridge) Driver for Windows.? I think I am getting confused between uninstalling and installing so many drivers, as to which overwrite.
Thanks again
Edit: It is TWRP v2.6.3.0

Syrup4 said:
Thanks once again both of you. But even though it seems like it should be listed. It is not. And if I right click on the device that appears, it is greyed out.
Which drivers? HTC ones? Android ones? or the Universal ADB (Android Debug Bridge) Driver for Windows.? I think I am getting confused between uninstalling and installing so many drivers, as to which overwrite.
Thanks again
Edit: It is TWRP v2.6.3.0
Click to expand...
Click to collapse
The HTC drivers, not the universal ones.
2.6.3.0 is to old and will cause problem. Once your drivers problem is fixed, update your twrp recovery before going any further (at least 2.6.3.3 or much newer if you want MTP support)
Ill be back in a few hours good luck

alray said:
The HTC drivers, not the universal ones.
2.6.3.0 is to old and will cause problem. Once your drivers problem is fixed, update your twrp recovery before going any further (at least 2.6.3.3 or much newer if you want MTP support)
Ill be back in a few hours good luck
Click to expand...
Click to collapse
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day

Syrup4 said:
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day
Click to expand...
Click to collapse
Is fastboot connectivity working? (boot in bootloader mode and use "fastboot device" command to see if your phone is detected) Or is it only adb not working when in twrp?
You can update twrp using fastboot commands when in bootloader mode:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
(replace "file_name.img" by the file name of the recovery you want to flash.

Syrup4 said:
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day
Click to expand...
Click to collapse
I have good luck with these adb tools. Also did you reboot pc after removing old drivers, sometime things just magically work after.
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP is updated from fastboot (fastboot flash recovery nameofrecovery.img)
https://dl.twrp.me/m7/

mb_guy said:
I have good luck with these adb tools. Also did you reboot pc after removing old drivers, sometime things just magically work after.
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP is updated from fastboot (fastboot flash recovery nameofrecovery.img)
https://dl.twrp.me/m7/
Click to expand...
Click to collapse
alray said:
Is fastboot connectivity working? (boot in bootloader mode and use "fastboot device" command to see if your phone is detected) Or is it only adb not working when in twrp?
You can update twrp using fastboot commands when in bootloader mode:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
(replace "file_name.img" by the file name of the recovery you want to flash.
Click to expand...
Click to collapse
THANK YOU.
There has been progress.
So I installed the new TWRP posted, version 2.8.7.0-m7.
At first it said signature checking failed, so I booted the token thing from HTCDev again.
It then allowed me to install the new TWRP.
When the new TWRP was installed it came up with a screen with errors in red. "Can't write to Cache" or something.
I was going to write them down but it restarted itself then got stuck.
However once I turned the phone off and on again then went into recovery the new version allowed "MTP Device" to be recognized as a drive on my computer and I was able to copy over Misc_Tool_1.00.zip.
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Thank you both again for your time:good:

Syrup4 said:
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Click to expand...
Click to collapse
The tool Ive made will indeed hang if used with recent twrp version, sorry i forgot to mention that. So yes flash the 2.6.3.3 version and you should be able to use it without any problem. MTP isn't supported in 2.6.3.3 but you should be able to use "adb push" commands to transfer files, anyway I don't think you'll need any other file for now. Just change your version-main then relock your bootloader and flash the ruu.

Syrup4 said:
THANK YOU.
There has been progress.
So I installed the new TWRP posted, version 2.8.7.0-m7.
At first it said signature checking failed, so I booted the token thing from HTCDev again.
It then allowed me to install the new TWRP.
When the new TWRP was installed it came up with a screen with errors in red. "Can't write to Cache" or something.
I was going to write them down but it restarted itself then got stuck.
However once I turned the phone off and on again then went into recovery the new version allowed "MTP Device" to be recognized as a drive on my computer and I was able to copy over Misc_Tool_1.00.zip.
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Thank you both again for your time:good:
Click to expand...
Click to collapse
First I would download the ruu suggested by Alray to your computer (if you haven't already) have it in the adb folder
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
7.17.661.7 ruu
Then
Just flash the older twrp like you did the installed version
fastboot flash recovery nameofrecovery.img
fastboot erase cache
fastboot reboot-bootloader
then run the misc tool and change cid
Then
then flash the ruu (it will replace twrp and rom with stock versions)
use the "how to flash" instructions on the first page of ruu download page.
Note: you MUST use htc_fastboot. Download it and place in the adb folder.
phone will reboot and then continue when flashing the ruu, don't rush, will take 10-15 min