Database Develop

[Q] stuck on boot no usb connection to computer

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Clockworkmod stuck in recovery loop for rooting. Unable to terminal connect

Hope I can find some help as I ran into what seems to be a pretty serious issue. I haven't been able to find any steps that gets my phone back into booting the actual OS, so posting my specific problem seems to be the only option. A lot of thanks for anyone that can possibly help.
So, followed these instructions to root my phone and get it ready for installing a new ROM, but got stuck at instruction 18.
Which says: (a few before too)
16. OK Now the bootloader is unlocked. Time to install a recovery. In Terminal ./adb reboot bootloader
17. In terminal ./fastboot flash recovery name_of_the_recovery.img (I used recovery-clockwork-6.0.3.1-m7.img)
18. After recovery has flashed POWER DOWN PHONE COMPLETELY Then restart it
Once I did that, I restarted my phone and it loaded up clockwork recovery screen. This seemed fine, but every time I clicked to restart system it keeps on putting me back to this screen.
* I've tried clearing cache and booting, creating a backup and restoring and booting,
* I've got to the bootloader of the OS, but when I go to recovery, it brings me back here.
* I can't connect via the terminal w/ adb or fastboot as it complains it can't connect to device or just waiting for device.
* Neither the Android File Manager nor HTC Sync Manager can connect.
* I've tried only having one application installed for file management hoping that it's just a conflict, but to no avail.
* Can't use an sdcard load since there's no sdcard
* Trying a sideload doesn't work because I can't connect to the device.
I'm afraid I bricked my phone. I hope someone can offer some suggestions.
Again, thank you for your time.
Chris

You can't reboot into bootloader with a longpress of Power + Vol- button under a strong light?

I can get there, to bootloader by using the power and volume down, but no matter what option i pick it gets me back to clockworkmod. I've tried connecting then via terminal, but still nothing. Pretty frustrating.

In fastboot with the command:
Code:
fastboot devices
you can't see your phone?
If yes, flash the latest TWRP/CWM, do an erase cache and flash or sideload a rom

Right, nothing is output w/ that. Neither in bootloader or clockworkmod screen.

You've the right driver installed?
And, in device manager you can see your phone without any yellow triangle?
p.s. are you using windows, right?

Forgot to mention that, I'm on a Macbook Pro.

So Fastboot flash different recovery does not work?
When you where in recovery, did you flash any new ROM?
Sent from my HTC One using XDA Premium 4 mobile app

herrfricke said:
Forgot to mention that, I'm on a Macbook Pro.
Click to expand...
Click to collapse
So you have to add a
Code:
./
before the fastboot/adb command.
In fastboot type:
Code:
./fastboot devices
and check if you can see your device
Sindroid said:
So Fastboot flash different recovery does not work?
Click to expand...
Click to collapse
If atm he can't recognize his device how he can flash a recovery?

Sindroid said:
So Fastboot flash different recovery does not work?
When you where in recovery, did you flash any new ROM?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the command... sadly it just says waiting for device. The core problem it seems now is that my computer won't recognize the USB connection for this device.
I think I just found out what I did wrong
instead of running this:
./fastboot flash recovery recovery-clockwork-6.0.3.1-m7.img
I ran this:
/fastboot flash boot recovery-clockwork-6.0.3.1-m7.img
based on command history. Crap.

If atm he can't recognize his device how he can flash a recovery?[/QUOTE]
Yeah, I know, only way you can get the whole process working is by adding ./ or if you wanted to put it on your $PATH variable, but that would be pointless.

Well your op says you attempted to do backups and restore, so you obviously seem to have CWM installed.
Sent from my HTC One using XDA Premium 4 mobile app

Sindroid said:
Well your op says you attempted to do backups and restore, so you obviously seem to have CWM installed.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, it's installed. Just I think now because it was put on as a boot vs recovery it's treating it as the OS, possibly, so when I try to boot the system,it just boots CWM. The OS is there though, if I do a backup you can see all the files (especially proprietary stuff from HTC) still on the drive. But w/o access to it via terminal I don't know if there's a way to fix the boot problem. I can get to the bootloader,if I only it could mount to my computer from there (or even in CWM). Access to the phones drive seems to be the only way to clean it up.

herrfricke said:
Hope I can find some help as I ran into what seems to be a pretty serious issue. I haven't been able to find any steps that gets my phone back into booting the actual OS, so posting my specific problem seems to be the only option. A lot of thanks for anyone that can possibly help.
So, followed these instructions to root my phone and get it ready for installing a new ROM, but got stuck at instruction 18.
Which says: (a few before too)
16. OK Now the bootloader is unlocked. Time to install a recovery. In Terminal ./adb reboot bootloader
17. In terminal ./fastboot flash recovery name_of_the_recovery.img (I used recovery-clockwork-6.0.3.1-m7.img)
18. After recovery has flashed POWER DOWN PHONE COMPLETELY Then restart it
Once I did that, I restarted my phone and it loaded up clockwork recovery screen. This seemed fine, but every time I clicked to restart system it keeps on putting me back to this screen.
* I've tried clearing cache and booting, creating a backup and restoring and booting,
* I've got to the bootloader of the OS, but when I go to recovery, it brings me back here.
* I can't connect via the terminal w/ adb or fastboot as it complains it can't connect to device or just waiting for device.
* Neither the Android File Manager nor HTC Sync Manager can connect.
* I've tried only having one application installed for file management hoping that it's just a conflict, but to no avail.
* Can't use an sdcard load since there's no sdcard
* Trying a sideload doesn't work because I can't connect to the device.
I'm afraid I bricked my phone. I hope someone can offer some suggestions.
Again, thank you for your time.
Chris
Click to expand...
Click to collapse
As I gathered from your description, you are using a MAC.
I think you should use your friends PC to use the command to install the recovery and see if it solves the problem.
Alternatively you can use Heimdall Terminal fir MAC, which is sort of ODIN for MAC and try to reinstall your firmware.
Sent from my GT-I9070 using xda app-developers app

redndian said:
As I gathered from your description, you are using a MAC.
I think you should use your friends PC to use the command to install the recovery and see if it solves the probkem.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
I can use virtual box now... i'll give it a try.

I use Mac as well and I ran into same connectivity problems as you do, but it was not during unlocking, rooting.. I had a Bootloop going with some mods conflicts, anyway, not important. I used my missus win 7 laptop and there it would see it and I could fix my problems there. Mac has had issues with SdK not working.
Alas, do run the Fastboot flash recovery command if you get it talking, as you temporarily can access CWM before flashing it permanently.
Sent from my HTC One using XDA Premium 4 mobile app

redndian said:
As I gathered from your description, you are using a MAC.
I think you should use your friends PC to use the command to install the recovery and see if it solves the problem.
Alternatively you can use Heimdall Terminal fir MAC, which is sort of ODIN for MAC and try to reinstall your firmware.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Wait, heimdall is for samsung as i know.
And is different flash firmware for samsung and htc
Sent from One with Tapa4

Guich said:
Wait, heimdall is for samsung as i know.
And is different flash firmware for samsung and htc
Tried googling, and I found that it is samsung specific
I stand corrected.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse

I have a similar problem
My specs:
M7_WLS PVT SHIP S-ON RH
HBOOT 1.44 UNLOCKED
RADIO 1.00.20.0626
OpenDSP v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:-1
TWRP v2.6.3 - working correctly
I have no backup and no ROM on my phone
I can access HBOOT just fine via power + vol down
Team Win Recovery also seems to function properly
My phone is not listed under adb devices
and the worst of all, my phone won't connect to my PC!!
Here is the problem,
I got bored with my stock ROM, so I decided to try CyanogenMod 10.1. Having installed a few ROMs in the past, I felt comfortable tampering with the software on my HTC One (Sprint). I first had clockworkmod flashed and I booted to HBOOT and wiped everything I had an option to wipe. I fear this was my mistake, I also did not create a backup prior to my tampering. After wiping my phone with clockwork, I tried moving the Cyanogen zip to my phone. This is when I noticed my phone would not connect to the PC. I tried different PC's and cords. I am using USB 2.0 and the laptop even makes a ding noise when I enter fastboot usb. My phone is not listed in C: drive, device manager, or adb devices.
I now have flashed TWRP and made sure all my drivers are up to date. I installed HTC Sync Manager, which can not find my phone. I tried to send the cyanogen zip to my phone via fastboot flash zip cm-10.1.3-m7spr.zip. This failed to pass signature verification test. I thought being unlocked bypassed the sig check but I guess not. I tried to gain S-OFF using revone. I couldn't send revone to my phone either. I also tried installing the stock ruu. I got my phone to the black HTC screen and ran the ruu.exe and whammo! ERROR [155] UNKNOWN ERROR...
I'm looking for a way to move my rom zip file to my phone so I can install via TWRP. Any help would be GREATLY appreciated! Thank you!

NWC83 said:
My specs:
M7_WLS PVT SHIP S-ON RH
HBOOT 1.44 UNLOCKED
RADIO 1.00.20.0626
OpenDSP v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:-1
TWRP v2.6.3 - working correctly
I have no backup and no ROM on my phone
I can access HBOOT just fine via power + vol down
Team Win Recovery also seems to function properly
My phone is not listed under adb devices
and the worst of all, my phone won't connect to my PC!!
Here is the problem,
I got bored with my stock ROM, so I decided to try CyanogenMod 10.1. Having installed a few ROMs in the past, I felt comfortable tampering with the software on my HTC One (Sprint). I first had clockworkmod flashed and I booted to HBOOT and wiped everything I had an option to wipe. I fear this was my mistake, I also did not create a backup prior to my tampering. After wiping my phone with clockwork, I tried moving the Cyanogen zip to my phone. This is when I noticed my phone would not connect to the PC. I tried different PC's and cords. I am using USB 2.0 and the laptop even makes a ding noise when I enter fastboot usb. My phone is not listed in C: drive, device manager, or adb devices.
I now have flashed TWRP and made sure all my drivers are up to date. I installed HTC Sync Manager, which can not find my phone. I tried to send the cyanogen zip to my phone via fastboot flash zip cm-10.1.3-m7spr.zip. This failed to pass signature verification test. I thought being unlocked bypassed the sig check but I guess not. I tried to gain S-OFF using revone. I couldn't send revone to my phone either. I also tried installing the stock ruu. I got my phone to the black HTC screen and ran the ruu.exe and whammo! ERROR [155] UNKNOWN ERROR...
I'm looking for a way to move my rom zip file to my phone so I can install via TWRP. Any help would be GREATLY appreciated! Thank you!
Click to expand...
Click to collapse
I once had a similar problem with my samsung abd tried this ..
1. Remove sd card from your phone.
2. Put the sd card in a card reader and copy your firmware on sd card through yout pc
3. Refit the sd card in your phone
4. Flash firmware through recovery.
I hope this helps.
Sent from my GT-I9070 using xda app-developers app

[Q] Htc One Bricked? Not sure...[SOLVED]

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

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

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

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

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

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

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

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

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

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

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

[Q] HTC One (M7) Bricked???

Hello. I have the following problem. I friend of mine that I've sold him my old rooted Htc One tried to make 4.4. kitkat
He tried to install
Android_Revolution_HD-One-53.0zip
BUT I don't know how he managed to stuck his phone.The problem is when I am power on the phone it shows the white HTC screen with the red letters "this build is for development purpose only..." after a while reboots in TWRP v2.5.0.0
And that's it , I cannot do anything because my PC won't recognize it via USB cable.
Any suggestions?
(excuse me for my English, with love from Greece )

As long as it boots into Recovery its not bricked. Do you have the HTC Driver installed on your computer?
Android Revolution HD 53 requires min. TWRP 2.6.3.3. Your version is too old.

foxgre said:
Hello. I have the following problem. I friend of mine that I've sold him my old rooted Htc One tried to make 4.4. kitkat
He tried to install
Android_Revolution_HD-One-53.0zip
BUT I don't know how he managed to stuck his phone.The problem is when I am power on the phone it shows the white HTC screen with the red letters "this build is for development purpose only..." after a while reboots in TWRP v2.5.0.0
And that's it , I cannot do anything because my PC won't recognize it via USB cable.
Any suggestions?
(excuse me for my English, with love from Greece )
Click to expand...
Click to collapse
From recovery go to fastboot connect phone to pc.
It must be recognized.
Then flash boot.img which is in the Revolution.zip.
Then install the rom via recovery.
Remember for unlock and not s-off users the boot.img must be flashed befor flashing a rom.zip.
Sent by myself, without help )

i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly

SAME problem (or pretty similar) here
foxgre said:
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
Click to expand...
Click to collapse
SAME problem (or pretty similar) here, trying to instal ARHD61.1... I don't know how did I screw up this so much...
My bootloader is TAMPERED, UNLOCKED, S-On. Recovery TRWP (2.7) launches but... many things don't work.
First thing I have to mention is that I didn't forget to enable debugging before all this started (and now I can't launch android to do it).
My HTC drivers should be up-to-date, as I installed yesterday HTC sync 3.00.52...
In bootloader, if I type "fastboot devices" I get "FA34HW903605 fastboot", and "fastboot reboot.bootloader" does what it is expected to do...
In recovery, "adb push" tells me "error: device not found".
Can someone help me? If you need more details, just ask. Thanks

foxgre said:
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
Click to expand...
Click to collapse
Duwie_80 said:
SAME problem (or pretty similar) here, trying to instal ARHD61.1... I don't know how did I screw up this so much...
My bootloader is TAMPERED, UNLOCKED, S-On. Recovery TRWP (2.7) launches but... many things don't work.
First thing I have to mention is that I didn't forget to enable debugging before all this started (and now I can't launch android to do it).
My HTC drivers should be up-to-date, as I installed yesterday HTC sync 3.00.52...
In bootloader, if I type "fastboot devices" I get "FA34HW903605 fastboot", and "fastboot reboot.bootloader" does what it is expected to do...
In recovery, "adb push" tells me "error: device not found".
Can someone help me? If you need more details, just ask. Thanks
Click to expand...
Click to collapse
can you guys check out FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082 if that's the problem you have

nkk71 said:
can you guys check out FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082 if that's the problem you have
Click to expand...
Click to collapse
Let me try and I'll tell you later. I also think it's a matter of drivers, so I was downloading and re-installing it... Thank you for your help
-------------------------------------------------- UPDATE --------------------------------------------------------------------------------
Well, I followed your steps (LET ME THANK YOU FOR MAKING THAT GUIDE) and now the device is "My HTC" as you show.
Something has changed:
If I type "adb devices" (in PC) when phone is in fastboot, the listing is void (before I got "FA34HW903605 fastboot"), and if I do the same while phone is in recovery, I get the mentioned "FA34HW903605 recovery".
In Windows7 I don't see "My HTC" as a conventional USB storage or Memory of a Camera (should it be?)
I've managed to ADB PUSH a ROM (ARHD) in recovery, but now I get an error message: "Unable to mount '/data' " and "Unable to mount internal storage " then FAILED. Now I'll try flashing a new recovery...

WOW WOW WOW!! It was enough for me, sir
1st) Solve comunnication issues as shown in FAQ #2 here
2nd) Solve TWRP recovery mount issues by:
2.a) Installing any other (clockwork) in fastboot using One All In One Kit (eaaaasy)
2.b) Formatting cache, system, data partitions
2.c) Installing TWRP again using One All In One Kit (Android Revolution REQUIRES this recovery)
2.d) Sending the ROM ('adb push your_rom.zip /sdcard/wherever_you_want_it')
2.e) Installing it from TWRP recovery.
An that was all. THANKS A LOT nkk71; without your help I still would be here trying to figure out what's broken... Thanks.

Duwie_80 said:
WOW WOW WOW!! It was enough for me, sir
1st) Solve comunnication issues as shown in FAQ #2 here
2nd) Solve TWRP recovery mount issues by:
2.a) Installing any other (clockwork) in fastboot using One All In One Kit (eaaaasy)
2.b) Formatting cache, system, data partitions
2.c) Installing TWRP again using One All In One Kit (Android Revolution REQUIRES this recovery)
2.d) Sending the ROM ('adb push your_rom.zip /sdcard/wherever_you_want_it')
2.e) Installing it from TWRP recovery.
An that was all. THANKS A LOT nkk71; without your help I still would be here trying to figure out what's broken... Thanks.
Click to expand...
Click to collapse
no problem, glad to be of help
remember for most 4.4 ROMs, (for m7_u/ul) TWRP 2.6.3.3 (or higher) is recommended at the moment.
though you should be good by downloading it, then checking MD5 to make sure the download isnt corrupt (that site doesnt work with download managers), then:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery and push the rom

Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:

foxgre said:
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
Click to expand...
Click to collapse
you're really not giving any details... so you hear a sound... what does Windows Device Manager show??

foxgre said:
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
Click to expand...
Click to collapse
It wont be so easy, I'm afraid. Even if comunication issues are solved, you won't be able to copy your ROM using windows file manager, opening the phone like a conventional drive...
You have to install "ADB" in your PC (search in HTC ONE subforums, there's a lot of info about ADB pusing (=copying) ROMS) and use it to copy your ROM. One advice: while "pushing" the ROM, be patient: it takes a long time. When your ROM is "pushed", just install it in recovery and... that's it!!
I think here you have a good starting point.

Duwie_80 said:
It wont be so easy, I'm afraid. Even if comunication issues are solved, you won't be able to copy your ROM using windows file manager, opening the phone like a conventional drive...
You have to install "ADB" in your PC (search in HTC ONE subforums, there's a lot of info about ADB pusing (=copying) ROMS) and use it to copy your ROM. One advice: while "pushing" the ROM, be patient: it takes a long time. When your ROM is "pushed", just install it in recovery and... that's it!!
I think here you have a good starting point.
Click to expand...
Click to collapse
Thanks again i am already looking for it.

AT LAST!!!
I've managed to push the rom.
Thank you very much for your help

foxgre said:
AT LAST!!!
I've managed to push the rom.
Thank you very much for your help
Click to expand...
Click to collapse
Hey, congratulations!! :good::good::good:

[Q] HTC One, tampered, unlocked, S-ON, no OS, device not foun on laptop. Cluster****.

Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!

PrimalMK said:
Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
Click to expand...
Click to collapse
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs

clsA said:
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
Click to expand...
Click to collapse
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version of TWRP does not work. I have no preferences when it comes to OS's. A stock OS (is OS and ROM the same thing?) would be fine.

Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.

PrimalMK said:
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version does not work. I have no preferences. A stock OS (is OS and ROM the same thing?) would be fine.
Click to expand...
Click to collapse
Well your going to need adb / fastboot on your PC
use mine here >> https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip
and install the HTC Drivers here >> http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
unzip that to c:\ so you have c:\fastboot in windows explorer
now inside the folder you shift + right click / command prompt here
now you have a command prompt window type
fastboot getvar all
and post the result here / minus your serial number and IMEI
then i can find you the correct recovery and rom for your phone
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
PrimalMK said:
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
Click to expand...
Click to collapse
yes window 8 will be a problem till you get another hboot above 1.44/1.54
hboot 1.55 has no problem on windows 8 ( I use windows 8.1)

clsA said:
instructions
Click to expand...
Click to collapse
Downloaded fastboot, unzipped in c:
Drivers from that link are classed as malware. Trying to find earlier drivers/other mirror.

Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.

PrimalMK said:
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
Click to expand...
Click to collapse
this will work fine
just put TWRP and the Rom in the fastboot folder
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse

clsA said:
this will work fine
just put TWRP and the Rom in the fastboot folder
Click to expand...
Click to collapse
error: cannot open 'openrecovery.......img'
What to do?

PrimalMK said:
error: cannot open 'openrecovery.......img'
What to do?
Click to expand...
Click to collapse
is it in the fastboot folder ?

clsA said:
is it in the fastboot folder ?
Click to expand...
Click to collapse
Yes, see screenshot.

PrimalMK said:
Yes, see screenshot.
Click to expand...
Click to collapse
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?

clsA said:
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
Click to expand...
Click to collapse
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?

PrimalMK said:
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
Click to expand...
Click to collapse
fastboot crashes ?
no if fastboot getvar worked it will all work
it's only 4 commands and your phone will be working
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb sideload rom.zip
sideload takes about 8 min

calculation icatkg
clsA said:
fastboot crashes ?
no if fastboot getvar worked it will all work
Click to expand...
Click to collapse
Restarted a couple of times etc. It worked. Will do the ROM thing now.

PrimalMK said:
Restarted a couple of times etc. It worked. Will do the ROM thing now.
Click to expand...
Click to collapse
great your about done ...your phone will be android 4.3 when it finishes
don't take any updates to the OS

cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:

PrimalMK said:
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
Click to expand...
Click to collapse
no problem, hit the thanks button