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!

[Q] Help! HTC One m7 not recognised by adb devices

Hey all, I'm stuck in a dilemma. Recently my phone has been acting up ever since I updated to a nightly version of CM11 and so tried to fix it. I did a factory reset but then now I cant get adb devices to recognise my phone. It says on the bootloader screen:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.000
RADIO-4T.21.3218.21
OPENDSP-V32.120.274.0909
OS-
EMMC-BOOT 2048MB
OCT 29 2013,17:34:05.0

167chong said:
Hey all, I'm stuck in a dilemma. Recently my phone has been acting up ever since I updated to a nightly version of CM11 and so tried to fix it. I did a factory reset but then now I cant get adb devices to recognise my phone. It says on the bootloader screen:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.000
RADIO-4T.21.3218.21
OPENDSP-V32.120.274.0909
OS-
EMMC-BOOT 2048MB
OCT 29 2013,17:34:05.0
Click to expand...
Click to collapse
Does your phone boot to system?

donkeykong1 said:
Does your phone boot to system?
Click to expand...
Click to collapse
No it doesn't

167chong said:
No it doesn't
Click to expand...
Click to collapse
Try one of these methods in this post!

majmoz said:
Try one of these methods in this post!
Click to expand...
Click to collapse
Thanks but I've already tried those methods and it comes up with
OKAY [ 46.977s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)

167chong said:
Thanks but I've already tried those methods and it comes up with
OKAY [ 46.977s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
Click to expand...
Click to collapse
what were you trying to wriye to your phone when it came up with that, looks like you were trying to flash a rom the wrong way, if so which rom ?

Seanie280672 said:
what were you trying to wriye to your phone when it came up with that, looks like you were trying to flash a rom the wrong way, if so which rom ?
Click to expand...
Click to collapse
I just tried to flash stock rom for HTC is there possibly another rom that i could flash?

167chong said:
I just tried to flash stock rom for HTC is there possibly another rom that i could flash?
Click to expand...
Click to collapse
If your trying to flash an ruu.exe it needs to be run from windows, if your trying to run an ruu.zip then your phone needs to be in ruu mode, you also need the make 100% sure you have the right ruu, it also needs to be a full ruu not an ota.
You need to post your fastboot getvar all without India and serial number so we can find the correct ruu for your phone

Seanie280672 said:
If your trying to flash an ruu.exe it needs to be run from windows, if your trying to run an ruu.zip then your phone needs to be in ruu mode, you also need the make 100% sure you have the right ruu, it also needs to be a full ruu not an ota.
You need to post your fastboot getvar all without India and serial number so we can find the correct ruu for your phone
Click to expand...
Click to collapse
This is my getvar info
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei: 355859054474598
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__622
battery-status: good
battery-voltage: 4304mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-14eb688c
hbootpreupdate: 11
gencheckpt: 0

Also whenever i try adb devices it doesnt come up with any device

167chong said:
Also whenever i try adb devices it doesnt come up with any device
Click to expand...
Click to collapse
Type adb devices (in windows cmd) when in sideload mode from your recovery
If that doesn't work out
1. adb kill-server
2.adb usb
3.adb devices
If still nothing use a different port and try again
If you get an error that looks like
error
error
Unplug usb cable and go again
I soft bricked my phone on monday and learned alot while trying to fix it. One of the things with adb I noticed (and read somewhere) is that if something fails you can't just run the command again. It will fail. You have to kill the server and start over.
Also don't use windows 8. Its a nightmare for this.
Best of luck bro

What is the phone booted to when you adb devices? It will not respond when in bootloader. The phone is in Fastboot mode and will only respond to Fastboot commands. Type "Fastboot devices" and it should pop up.
Are you able to boot to recovery? If so, try "adb devices" while in recovery. If it responds, try to sideload a new Rom. If you cannot run recovery, you will have to reflash recovery or ruu.
If you cannot run adb commands in recovery, it is most likely driver issues. If you are able to use OTG to flash a Rom from recovery. (OTG cable and an SD card)
Sent from my HTC6500LVW using XDA Free mobile app

Running Windows 7 with the phone connected with a USB 2.0 port , adb also didnt work. adb devices couldn't find my phone, strange thing
because fastboot devices DID see my phone.
Then i connected the phone to a macbook pro and with the same cable both adb and fastboot worked just fine.
So maybe your using a USB 3.0 port, if so try a 2.0 port. Maybe try another USB cable and if that doenst help, you could try Windows 7 or XP or even Ubuntu or Mac OS.

MrSm1th said:
Running Windows 7 with the phone connected with a USB 2.0 port , adb also didnt work. adb devices couldn't find my phone, strange thing
because fastboot devices DID see my phone.
Then i connected the phone to a macbook pro and with the same cable both adb and fastboot worked just fine.
So maybe your using a USB 3.0 port, if so try a 2.0 port. Maybe try another USB cable and if that doenst help, you could try Windows 7 or XP or even Ubuntu or Mac OS.
Click to expand...
Click to collapse
I assumed you went to adb sideload mode already. You don't adb from fastboot mode. You have to go to the adb sideload section of your recovery. If TWRp is your recovery check in advanced. Fastboot is only for fastboot commands

Ultimakaiser said:
I assumed you went to adb sideload mode already. You don't adb from fastboot mode. You have to go to the adb sideload section of your recovery. If TWRp is your recovery check in advanced. Fastboot is only for fastboot commands
Click to expand...
Click to collapse
So i have tried adb kill-server and stuff and it hasnt worked. Yes I have done it in recovery, no my usb isnt USB 3.0 nor is it windows 8. It recognises my fastboot devices but for ADB devices it says:
List of attached devices
AND thats it, it doesnt pop up my device

167chong said:
So i have tried adb kill-server and stuff and it hasnt worked. Yes I have done it in recovery, no my usb isnt USB 3.0 nor is it windows 8. It recognises my fastboot devices but for ADB devices it says:
List of attached devices
AND thats it, it doesnt pop up my device
Click to expand...
Click to collapse
reboot phone and pc
switch ports
doesnt matter if all are usb 2.0
switch them. trust me (sorry for the lazy typing I'm tired)
Make sure its adb kill-server
then
adb usb
that should get you running eventually
btw buddy.....please tell me you have a folder that has this name
adt-bundle-windows-x86_64-20140702
with sdk manager installed.

Ultimakaiser said:
reboot phone and pc
switch ports
doesnt matter if all are usb 2.0
switch them. trust me (sorry for the lazy typing I'm tired)
Make sure its adb kill-server
then
adb usb
that should get you running eventually
btw buddy.....please tell me you have a folder that has this name
adt-bundle-windows-x86_64-20140702
with sdk manager installed.
Click to expand...
Click to collapse
Yeah I did all of that and yes i have that adt bundle folder with sdk manager installed
thanks for your time

167chong said:
Yeah I did all of that and yes i have that adt bundle folder with sdk manager installed
thanks for your time
Click to expand...
Click to collapse
One more thing. I think this is the final piece of the puzzle. You are are using TWRP.
I'm certain. Flash clockwork recovery and try again. That should work.

Ultimakaiser said:
One more thing. I think this is the final piece of the puzzle. You are are using TWRP.
I'm certain. Flash clockwork recovery and try again. That should work.
Click to expand...
Click to collapse
You are correct! I am using TWRP I changed it to CWM but it didnt help. It still gives me:
C:\Users\Gooby\Downloads\adt-bundle-windows-x86_64-20140702\platform-tools>adb
kill-server
C:\Users\Gooby\Downloads\adt-bundle-windows-x86_64-20140702\platform-tools>adb
usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Also when i go into recovery it does this triple buzz like "do-do-do". Don't know if that has anything to do with anything but yeah. Appreciate all of your time

167chong said:
You are correct! I am using TWRP I changed it to CWM but it didnt help. It still gives me:
C:\Users\Gooby\Downloads\adt-bundle-windows-x86_64-20140702\platform-tools>adb
kill-server
C:\Users\Gooby\Downloads\adt-bundle-windows-x86_64-20140702\platform-tools>adb
usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Also when i go into recovery it does this triple buzz like "do-do-do". Don't know if that has anything to do with anything but yeah. Appreciate all of your time
Click to expand...
Click to collapse
If you are getting an ADB error, cancel the sideload from your phone, unplug and replug your phone, and restart the process. Also I checked around and found this: You may need to manually put the adb and fastboot files in your /usr/bin/ folder. Some users have the same issue and that seems to fix it. Someone confirmed it worked for them. I'd try the other stuff first tho

How do i run ADB from system32??? [solved]

I am trying to recover my HTCone m7 from this stuck logo screen upon lunch. At this point I want to get s-off in order to RUU my phone. The bagillion potential fixes online have lead me to believe that i need to push Android Rev HD in order to add firewater which will grant me s-OFF, allowing me to run the RUUexe. following>>>>>htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-firewater-any-computer-015123
NOW i need to use abd but it wont connect for s--t. I'm guessing its because my computer is referencing the drivers from system32 but when i move my platform-tools folder to systems32 i get "...adbwinapi.dll file missing" or somethiing like that.
My question. How do i get ADB working from system32?

tacoDawg said:
NOW i need to use abd but it wont connect for s--t. I'm guessing its because my computer is referencing the drivers from system32 but when i move my platform-tools folder to systems32 i get "...adbwinapi.dll file missing" or somethiing like that.
My question. How do i get ADB working from system32?
Click to expand...
Click to collapse
Don't know why you think you have to do this. Adb doesnt have to be executed from system32. You can execute it from anywhere as long that all files are in the same folder (adb.exe, fastboot.exe and their related dynamic link library like adbwinapi.dll and adbwinusbapi.dll)
You also need your HTC drivers correctly installed on your computer.
ADB commands will only work from a custom recovery or from a booted OS with usb debug enabled.
Fastboot commands are used from bootloader mode.

Jxt. said:
Hello there, you do not need to have your adb folder in your system 32 folder in order to work. Instead, try moving it to the root of your Hard drive, so that it looks like C:/adb then try it from there. Tell me if that works
Click to expand...
Click to collapse
well moving the abd folder to the C drive did get fastboot working without the "adbwinapi.dll file missing" error but adb just wont connect. Its showing up in device manager as "ACER composite ADB Interface" and in Driver File Details its pulling files from system32.

Jxt. said:
Hello there, you do not need to have your adb folder in your system 32 folder in order to work. Instead, try moving it to the root of your Hard drive, so that it looks like C:/adb then try it from there. Tell me if that works
Click to expand...
Click to collapse
alray said:
Don't know why you think you have to do this. Adb doesnt have to be executed from system32. You can execute it from anywhere as long that all files are in the same folder (adb.exe, fastboot.exe and their related dynamic link library like adbwinapi.dll and adbwinusbapi.dll)
You also need your HTC drivers correctly installed on your computer.
ADB commands will only work from a custom recovery or from a booted OS with usb debug enabled.
Fastboot commands are used from bootloader mode.
Click to expand...
Click to collapse
i thought the adb.exe and the driver needed to be in the same place for some reason... Ive switched out the htc drivers a gazillion times i dont think thats the issue..or maybe it is..... all i know is ADB refuses to cooperate.

tacoDawg said:
i thought the adb.exe and the driver needed to be in the same place for some reason... Ive switched out the htc drivers a gazillion times i dont think thats the issue..or maybe it is..... all i know is ADB refuses to cooperate.
Click to expand...
Click to collapse
You might try and start over.
** Uninstall the HTC driver from your computer and reboot.
** Download and install the latest HTC drivers. Do not install Sync or remove it after it installed.
** Download and install ADB & Fastboot in your root drive
** Assuming you can boot your phone normally, check Settings >> Developer options >> USB Debugging must have a check by it showing it is enabled.
** Now connect the phone to the computer and type the following in a cmd window:
Code:
adb devices
You should see your serial number in the cmd window.
Now type:
Code:
adb reboot bootloader
You should see the bootloader screen on your phone.
** Using the pwr and vol buttons select Recovery assuming a custom recovery is installed
** While at Recovery's main screen, type:
Code:
adb devices
You should see your serial number and next to it recovery Now you should be able to run the adb commands that you desire.
You mention that you want to run a RUU and that is why you want to s-off! If the RUU is the same version or higher you can run it as long as your bootloader is locked/relocked. If it is lower or a different version then you need s-off.

majmoz said:
You might try and start over.
** Uninstall the HTC driver from your computer and reboot.
** Download and install the latest HTC drivers. Do not install Sync or remove it after it installed.
** Download and install ADB & Fastboot in your root drive
** Assuming you can boot your phone normally, check Settings >> Developer options >> USB Debugging must have a check by it showing it is enabled.
** Now connect the phone to the computer and type the following in a cmd window:
Code:
adb devices
You should see your serial number in the cmd window.
Now type:
Code:
adb reboot bootloader
You should see the bootloader screen on your phone.
** Using the pwr and vol buttons select Recovery assuming a custom recovery is installed
** While at Recovery's main screen, type:
Code:
adb devices
You should see your serial number and next to it recovery Now you should be able to run the adb commands that you desire.
You mention that you want to run a RUU and that is why you want to s-off! If the RUU is the same version or higher you can run it as long as your bootloader is locked/relocked. If it is lower or a different version then you need s-off.
Click to expand...
Click to collapse
ive tried starting from scratch.. i have this RemoveOldHTCDriver3.exe that ive run but i dont know if that does the trick.. also what about the adb drivers? how would i remove those?
my phone is stuck at the launch screen, RUU seems like it would fix this.. so if i dont need s-off when i run the RUU why dose it stick at sending evvvvverrrrryyyyyyyyy eeeeffffiiiinnnnggggggg time?
Im going to try downloading another newer RUU maybe that will work..
thanks btw.

tacoDawg said:
ive tried starting from scratch.. i have this RemoveOldHTCDriver3.exe that ive run but i dont know if that does the trick.. also what about the adb drivers? how would i remove those?
my phone is stuck at the launch screen, RUU seems like it would fix this.. so if i dont need s-off when i run the RUU why dose it stick at sending evvvvverrrrryyyyyyyyy eeeeffffiiiinnnnggggggg time?
Im going to try downloading another newer RUU maybe that will work..
thanks btw.
Click to expand...
Click to collapse
To remove the HTC drivers go into Control Panel >> Programs and Features >> find HTC Drivers and highlight then select uninstall. To remove the adb and fastboot just delete the folder but save your files that are to be flashed or pushed to another folder first. When you download the newer RUU make sure it is for your variant and the version number is higher than what you presently have.

majmoz said:
To remove the HTC drivers go into Control Panel >> Programs and Features >> find HTC Drivers and highlight then select uninstall. To remove the adb and fastboot just delete the folder but save your files that are to be flashed or pushed to another folder first. When you download the newer RUU make sure it is for your variant and the version number is higher than what you presently have.
Click to expand...
Click to collapse
did everything you suggested.. got further than before kinda. I feel asleep at like 2am with the RUU app still sending.. I woke up around 5 something and it was still sending so i just shut down my computer and went back to sleep... when i wake up again the phone says RUU failed or something.
I re-run the app thinking maybe it was because i didnt 'run as administrator' two hours later its still sending...........................
this is the ruu im using: RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2(2)
maybe that bracketed 2 is throwing something off, i dont know.
is there an alternative to RUUexe.... maybe adb push a zip?

majmoz said:
To remove the HTC drivers go into Control Panel >> Programs and Features >> find HTC Drivers and highlight then select uninstall. To remove the adb and fastboot just delete the folder but save your files that are to be flashed or pushed to another folder first. When you download the newer RUU make sure it is for your variant and the version number is higher than what you presently have.
Click to expand...
Click to collapse
Jxt. said:
Hey taco, so all you are trying to do is flash an RUU?
if so you might want to check that you have the proper model id and matching RUU file, afterwards type "fastboot oem rebootRUU" capital sensitive.
Then start the RUU, If that's not what your trying to get done then tell me what you are trying to do.
Click to expand...
Click to collapse
Yes im trying to RUU, i ran it and after forever it still said sending. I shut the computer down and the phone booted to bootloader with no options to chose from, all it said was "RUU, RUU zip transfer failed" or something like that.. i rebooted and am trying the ruu ran as administrator.

Jxt. said:
Okay so you are getting a flashing error.
Are you in RUU mode when flashing this? (black screen, silver logo of HTC).
You have the correct RUU? (Can you give me a link of where you got it?)
Can you take a screenshot of your pc when you get the error?
That should let me know whats going wrong.
Click to expand...
Click to collapse
my computer just restarted out of nowhere so i lost the cmd prompts from the last attempt but after like 3 hours of sending (ruu app says sending........ and the phone has silver htc w/ blk bkg) i entered fastboot rebbotRUU and the phone reboots to the stuck launch green htc logo screen.. on my computer the ruu app says successful transfer or something... im guessing it didnt work.
ruu:
http://forum.xda-developers.com/showthread.php?t=2496074
phone says: relocked ***security warning***, hboot 1.56
htcONE m7 tmobile....

tried RUU for the 5th time... force rebooted the HTC after 2 hours, got 'ruu 155 unknown error'
results of fastboot getvar all:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA425W909681
(bootloader) imei: ******1457712
(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: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s

tacoDawg said:
tried RUU for the 5th time... force rebooted the HTC after 2 hours, got 'ruu 155 unknown error'
results of fastboot getvar all:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Click to expand...
Click to collapse
You are trying to run a RUU that is a lower version than your phone. Give this one a try is should be the same version or higher.

Jxt. said:
You might want to edit your last post and delete your imei, you don't want to show that around !
---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------
Another thing, you should be s-off or at least have a stock recovery. One of the two.
Click to expand...
Click to collapse
damn, how stupid of me...thanks. yea, i was trying to get s-off but they suggest ruu.

majmoz said:
You are trying to run a RUU that is a lower version than your phone. Give this one a try is should be the same version or higher.
Click to expand...
Click to collapse
MY GOD I COULD KISS YOU! I have been struggleing with this phone for liike 3 months now and you just broke the case like it was nothing. If you ever need to hide a body, consider me down, I owe you one.

tacoDawg said:
MY GOD I COULD KISS YOU! I have been struggleing with this phone for liike 3 months now and you just broke the case like it was nothing. If you ever need to hide a body, consider me down, I owe you one.
Click to expand...
Click to collapse
You are welcome glad I could help. If you could put [Solved] on the title of your first post that would be great. Happy flashing!!!

majmoz said:
You are trying to run a RUU that is a lower version than your phone. Give this one a try is should be the same version or higher.
Click to expand...
Click to collapse
Jxt. said:
Yeah, tell me how that works
Click to expand...
Click to collapse
s***s working now, thanks for looking out.

[Q] Restore os and RUU issue

Hello
I'm struggling since some days with my One M7 and since I'm not an expert I'm asking for some help..
I have unlocked the phone, installed twrp and by mistake wiped the os, so the phone doesn^t boot anymore. I would like to restore the original settings before trying again to root and install a custom rom.
The problem is that my phone is currently recognized only by fastboot and not by adb, tried several times with different usb cables and os (Win and mac) without success.
my understanding is that the only way to restore the os is via an official RRU.exe (as the device is s-on),am i correct?
Here the details
hboot 1.57.0000
radio 4t.28.3218.04
Opendsp v32.120.274.0909
I downloaded a RUU.exe but getting a security fail message in bootloader, again my understanding is that the image signature is wrong ? which ruu.exe can I use to successfully restore my device ?
many thanks in advance and best regards
Michele

zzmike76 said:
Hello
I'm struggling since some days with my One M7 and since I'm not an expert I'm asking for some help..
I have unlocked the phone, installed twrp and by mistake wiped the os, so the phone doesn^t boot anymore. I would like to restore the original settings before trying again to root and install a custom rom.
The problem is that my phone is currently recognized only by fastboot and not by adb, tried several times with different usb cables and os (Win and mac) without success.
my understanding is that the only way to restore the os is via an official RRU.exe (as the device is s-on),am i correct?
Here the details
hboot 1.57.0000
radio 4t.28.3218.04
Opendsp v32.120.274.0909
I downloaded a RUU.exe but getting a security fail message in bootloader, again my understanding is that the image signature is wrong ? which ruu.exe can I use to successfully restore my device ?
many thanks in advance and best regards
Michele
Click to expand...
Click to collapse
Right first of all adb commands wont work in the bootloader so stop trying different cables etc as your wasting your time, adb is only for when your in a booted rom or in recovery, fastboot commands are for the bootloader.
Next please post your fastboot getvar all without imei and serial number.
also, if you intend on going to a custom rom, there is no point flashing an RUU, you are already halfway there to flashing a custom rom, so which rom do you want to flash ?

hello
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
thanks and regards
michele

zzmike76 said:
hello
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
thanks and regards
michele
Click to expand...
Click to collapse
I can tell you now with a CID of VODAP110 there is no RUU for your phone, I used to have a TWRP backup for vodaphone, that was a long time ago before I got s-off, i'll have a look through and see if I can find it, which custom rom do you want to flash ?

Seanie280672 said:
I can tell you now with a CID of VODAP110 there is no RUU for your phone, I used to have a TWRP backup for vodaphone, that was a long time ago before I got s-off, i'll have a look through and see if I can find it, which custom rom do you want to flash ?
Click to expand...
Click to collapse
well, actually I would be happy to have my mobile booting again
as I'm not an expert I would kindly ask you for any suggestion for custom roms
thanks a lot!
Michele

zzmike76 said:
well, actually I would be happy to have my mobile booting again
as I'm not an expert I would kindly ask you for any suggestion for custom roms
thanks a lot!
Michele
Click to expand...
Click to collapse
Rom suggestions are not allowed.
Put TWRP 2.6.3.3 on your phone if you don't already have that version, it must be that version, I know its a bit old but its still the best for sense based rom's, you can get it from here: http://techerrata.com/browse/twrp2/m7
place the img file in the same folder as your adb and fastboot files on your computer then open a command windows from there and with your phone plugged in and fastbootUSB showing on your phone, issue the following commands
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
then download this file, this is stock unbranded rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.12_odexed.zip re-name it to rom.zip and place it in the same folder as adb and fastboot on your computer, then enter recovery on your phone, just the main screen no sub menu's, and then open a cmd window on your computer from the adb/fastboot folder and with your phone plugged into the computer type this command:
Code:
adb push rom.zip /sdcard/
it will appear unresponsive for quite a while, just leave it alone, takes about 5 mins to push the file but it will let you know when its done.
unplug your phone and flash the rom, when its finished reboot your phone and set it all up.
when everything is done that you want done to it, boot back into recovery and select reboot - system, it will say your rom is not currently rooted, do you want to install SuperSU now, select yes if you want root, your phone will then boot back up, follow the instructions on your phone screen when it boots back up, simple as that to root.

thanks for the information, i downgraded twrp to the suggested version but when entering recovery mode i cannot see the phone with the command adb devices...i noticed that when i plug the phone in windows for few seconds show the phone in device manager with name My HTC under android usb devices but then it disappears
i installed the latest htc drivers but still no phone detection

zzmike76 said:
thanks for the information, i downgraded twrp to the suggested version but when entering recovery mode i cannot see the phone with the command adb devices...i noticed that when i plug the phone in windows for few seconds show the phone in device manager with name My HTC under android usb devices but then it disappears
i installed the latest htc drivers but still no phone detection
Click to expand...
Click to collapse
that's strange that it pops up and then disappears, are you using the original HTC cable, or try a different one, also make sure HTC Sync is uninstalled, just leave the drivers on your computer, you will need to restart after uninstalling HTC Sync.
Sounds more like a computer issue to me than the phone.
Do you have a USB OTG cable you can use ?

original cable (tried also with another one), htc synch uninstalled 8and rebooted), driver version is 2.0.7.23
strang ething it appens on mac as well
i have no otg cable, if i buy one could it solve the issue ?

zzmike76 said:
original cable (tried also with another one), htc synch uninstalled 8and rebooted), driver version is 2.0.7.23
strang ething it appens on mac as well
i have no otg cable, if i buy one could it solve the issue ?
Click to expand...
Click to collapse
yes, you just copy the rom.zip to a memory stick, plug it into one end of the otg cable and the other end into your phone, does away with the use for a computer.
my driver is 2.0.7.28
could be your adb and fastboot, you could always try mine, link below
just find it very strange that it see's it, and then it disappears, ive never experienced anything like this happening to me, yet fastboot works fine, its got to be your drivers, you may have to force your driver in device manager whilst in recovery on your phone, are you using windows 8 ?

Seanie280672 said:
yes, you just copy the rom.zip to a memory stick, plug it into one end of the otg cable and the other end into your phone, does away with the use for a computer.
my driver is 2.0.7.28
could be your adb and fastboot, you could always try mine, link below
just find it very strange that it see's it, and then it disappears, ive never experienced anything like this happening to me, yet fastboot works fine, its got to be your drivers, you may have to force your driver in device manager whilst in recovery on your phone, are you using windows 8 ?
Click to expand...
Click to collapse
no windows 7 , this evening will try with an old xp laptop..but on the mac as well i can only see the device in fastboot
is there away to reformat the sdcard from twrp ? maybe it is damaged

zzmike76 said:
no windows 7 , this evening will try with an old xp laptop..but on the mac as well i can only see the device in fastboot
is there away to reformat the sdcard from twrp ? maybe it is damaged
Click to expand...
Click to collapse
inside twrp you can select wipe and then format data, that will wipe everything all partitions etc, you shouldn't be having any problems with windows 7 though.

update..bought an otg cable and was able to restore the image you sent me...MANY THANKS !!
still the device does not show on windows (there must be some driver issue), but now adb commands work on my mac (yesterday they didn't) so i have a working environment
need to understand how to s-off on mac , is it possible or windows is required ?
thanks again for your support!

zzmike76 said:
update..bought an otg cable and was able to restore the image you sent me...MANY THANKS !!
still the device does not show on windows (there must be some driver issue), but now adb commands work on my mac (yesterday they didn't) so i have a working environment
need to understand how to s-off on mac , is it possible or windows is required ?
thanks again for your support!
Click to expand...
Click to collapse
the only way to s-off on your current HBOOT is to use sunshine, your best off connecting your phone to wifi and download it straight to your phone as its an apk file actually for your phone, not to be run from the computer, it will check your phone first to see if it can be s-off'd and if it can then you'll have to pay $25 though paypal etc, it will then proceed, its well worth it, you can get rid of that vodaphone branded rubbish straight away and flash any RUU should you come stuck again, I paid to have mine done in a shop in Sheffield before sunshine came about and firewater didn't work.
http://theroot.ninja/

Seanie280672 said:
the only way to s-off on your current HBOOT is to use sunshine, your best off connecting your phone to wifi and download it straight to your phone as its an apk file actually for your phone, not to be run from the computer, it will check your phone first to see if it can be s-off'd and if it can then you'll have to pay $25 though paypal etc, it will then proceed, its well worth it, you can get rid of that vodaphone branded rubbish straight away and flash any RUU should you come stuck again, I paid to have mine done in a shop in Sheffield before sunshine came about and firewater didn't work.
http://theroot.ninja/
Click to expand...
Click to collapse
another update....it seems that after a while the phone is entering the usb host adapter mode and refuses to charge/being detected by mac/pc..at least i now can see the warning within the phone..now reading this thread http://forum.xda-developers.com/showthread.php?t=2481211
will try again to wipe everything and reinstall to see whether windows can detect it just for s-offing the phone

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