Database Develop

[SOLVED] Soft bricked after manual OTA

Hi,
First, I'm an idiot.
I tried to manually apply the 4.3 OTA by:
fastboot oem rebootRUU
Then flashed the firmware.zip from the OTA:
flash zip firmware.ota
Got a softbrick.
Tried wiping cache and data, wont boot at all.
HBoot updated to 1.55 and firmware rev appears as 3.62.401.1
I'm S-ON with locked bootloader.
Can't apply earlier RUU.
Is there any way you can think of to restore my phone without unlocking it through htcdev.com and flashing a custom recovery?
Thanks,

flash a 4.3 rom through recovery.
i guess you only flashed the firmware.zip and not the whole ota? 4.2.2 roms do not work for me with this firmware.zip
edit: didn't see your locked. i guess there's no way then.

Nemesis_00 said:
Hi,
First, I'm an idiot.
I tried to manually apply the 4.3 OTA by:
fastboot oem rebootRUU
Then flashed the firmware.zip from the OTA:
flash zip firmware.ota
Got a softbrick.
Tried wiping cache and data, wont boot at all.
HBoot updated to 1.55 and firmware rev appears as 3.62.401.1
I'm S-ON with locked bootloader.
Can't apply earlier RUU.
Is there any way you can think of to restore my phone without unlocking it through htcdev.com and flashing a custom recovery?
Thanks,
Click to expand...
Click to collapse
1- Question: why did you manually flash the OTA, if you're still locked and on stock??????????
2- after "fastboot oem rebootRUU", did "fastboot flash zip firmware.zip" TWICE?? you know that usually the first time it reports as "FAILED, push image again immediately" (or something like that).

nkk71 said:
1- Question: why did you manually flash the OTA, if you're still locked and on stock??????????
2- after "fastboot oem rebootRUU", did "fastboot flash zip firmware.zip" TWICE?? you know that usually the first time it reports as "FAILED, push image again immediately" (or something like that).
Click to expand...
Click to collapse
Hi,
1. It's already established I am an IDIOT. It was even the first line of my post
2. Yes, I have flashed it twice. Stuck at black screen after boot. No ADB. Connecting to the PC shows MTP driver as showing up but failing to install.

Nemesis_00 said:
Hi,
1. It's already established I am an IDIOT. It was even the first line of my post
2. Yes, I have flashed it twice. Stuck at black screen after boot. No ADB. Connecting to the PC shows MTP driver as showing up but failing to install.
Click to expand...
Click to collapse
You're not an idiot, take it easy but maybe next time do some more reading before doing something you're not comfortable with.
At least you flashed it twice, so good chance it updated the firmware correctly, but which version of
1- Windows are you on? (hopefully Win 7)
2- and HTC Drivers? (latest are "HTCDriver_4.8.0.002.exe" AFAIK)
3- you on stock or custom recovery?
3b-- if stock, is the OTA file still on your phone?
4- do you have an OTG cable?

nkk71 said:
You're not an idiot, take it easy but maybe next time do some more reading before doing something you're not comfortable with.
At least you flashed it twice, so good chance it updated the firmware correctly, but which version of
1- Windows are you on? (hopefully Win 7)
2- and HTC Drivers? (latest are "HTCDriver_4.8.0.002.exe" AFAIK)
3- you on stock or custom recovery?
3b-- if stock, is the OTA file still on your phone?
4- do you have an OTG cable?
Click to expand...
Click to collapse
Thanks for your help.
Im running Win7 with latest HTC drivers, stock recovery. I bit the bullet and unlocked the bootloader.
The OTA file is not on the phone, but I have an OTG cable.
Fastboot and ADB are installed and working.
P.S.
I have the decrypted 1.29.401.16 zip available.
Tried flashing the zip to the phone, got an error.
Thanks again,

Nemesis_00 said:
Thanks for your help.
Im running Win7 with latest HTC drivers, stock recovery. I bit the bullet and unlocked the bootloader.
The OTA file is not on the phone, but I have an OTG cable.
Fastboot and ADB are installed and working.
P.S.
I have the decrypted 1.29.401.16 zip available.
Tried flashing the zip to the phone, got an error.
Thanks again,
Click to expand...
Click to collapse
OK so fastboot and adb are working :good::good:
Now let's slow down a bit, and let us what your goal is. (ie what ROM do you want to run, ROOT, and anything else of importance).

nkk71 said:
OK so fastboot and adb are working :good::good:
Now let's slow down a bit, and let us what your goal is. (ie what ROM do you want to run, ROOT, and anything else of importance).
Click to expand...
Click to collapse
Obviously there is no ADB since the ROM doesnt boot, but fastboot works fine.
For now, I would like to get back to stock 4.2.2 (2.24.401.8) or even 4.3 (3.62.401.1) if possible.
The MID is PN0710000 and CID is HTC__102
Thanks

you should have manually flashed ota via stock recovery,need to be s-off as well
sent from my s-off 801n M7_UL

Nemesis_00 said:
Obviously there is no ADB since the ROM doesnt boot, but fastboot works fine.
For now, I would like to get back to stock 4.2.2 (2.24.401.8) or even 4.3 (3.62.401.1) if possible.
The MID is PN0710000 and CID is HTC__102
Thanks
Click to expand...
Click to collapse
adb works in recovery too. Are you on stock or custom recovery?
Sent from my HTC One using Tapatalk

Stock recovery.

Ok, I've installed TWRP, now just waiting to download guru reset.

Nemesis_00 said:
Ok, I've installed TWRP, now just waiting to download guru reset.
Click to expand...
Click to collapse
IMHO, if you are comfortably doing it
get http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
then use http://rumrunner.us/ to get s-off (there's a package for 3.62.401.1), then use a full RUU (exe) to go back to stock and get the OTAs.

Thanks, That's exactly what im doing.
Just copied the Guru reset to the usb flash

Nemesis_00 said:
Thanks, That's exactly what im doing.
Just copied the Guru reset to the usb flash
Click to expand...
Click to collapse
Any updates mate?

Sorry, ofcourse.
Flashed Guru Reset boots and works fine.
I didnt manage to S-OFF tho.
Followed all instructions except disabling lockscreen which is impossible with this fw.
Win7 x64 SP1. Firewall and AV disabled.
Stuck with the error message: "FATAL: F**k it" after the second boot into bootloader (test3).
Basically the ROM should be stock and no real reason to re-flash stock via RUU, but it seems somewhat less smooth than 4.2.2, and I have a FC from TuneIn Radio the moment I plug it into the original car dock.
So I thought id start again fresh.
I suppose I'll flash a different Sense based ROM and try to S-OFF again.

Nemesis_00 said:
Sorry, ofcourse.
Flashed Guru Reset boots and works fine.
I didnt manage to S-OFF tho.
Followed all instructions except disabling lockscreen which is impossible with this fw.
Win7 x64 SP1. Firewall and AV disabled.
Stuck with the error message: "FATAL: F**k it" after the second boot into bootloader (test3).
Basically the ROM should be stock and no real reason to re-flash stock via RUU, but it seems somewhat less smooth than 4.2.2, and I have a FC from TuneIn Radio the moment I plug it into the original car dock.
So I thought id start again fresh.
I suppose I'll flash a different Sense based ROM and try to S-OFF again.
Click to expand...
Click to collapse
You'll have to be on a ROM that's compatible with your firmware version (which is now 3.6xxxx). Here are a few things to check
1- Are you on Win7, it could work on Win 8 maybe 8.1 but only haphazardly
2- Did you update drivers to "HTCDriver_4.8.0.002.exe"
3- uninstalled HTC Sync
3- did you update adb sdk to latest
4- disable antivirus & firewall & windows defender, etc.
5- on the phone:
----- disable any lockscreen password, pin, etc (so the password or pin or face recognition, not the actual lockscreen)
----- enable USB debugging
----- disable SETTINGS -> POWER -> Fast boot
copy/paste command prompt of rummrunner for us to see

nkk71 said:
You'll have to be on a ROM that's compatible with your firmware version (which is now 3.6xxxx). Here are a few things to check
1- Are you on Win7, it could work on Win 8 maybe 8.1 but only haphazardly
2- Did you update drivers to "HTCDriver_4.8.0.002.exe"
3- uninstalled HTC Sync
3- did you update adb sdk to latest
4- disable antivirus & firewall & windows defender, etc.
5- on the phone:
----- disable any lockscreen password, pin, etc (so the password or pin or face recognition, not the actual lockscreen)
----- enable USB debugging
----- disable SETTINGS -> POWER -> Fast boot
copy/paste command prompt of rummrunner for us to see
Click to expand...
Click to collapse
Hi,
1. Win7 Pro x64. Device connected to USB2.0
2. The installed drivers are "HTCDriver_4.8.0.001.exe" Could not find 002 anywhere.
3. I never had HTC Sync
4. Updated Android SDK with SDK Manager to latest version..
5. Antivirus unloaded completely, firewall (Windows) disabled.
6. FW Version reported by fastboot is 3.62.401.1, same as the one reported by the OS itself.
7. Not password/pin/face lock etc.
8. USB Debugging enabled, and Fast Boot disabled.
9. Rumrunner log is as follows:
Code:
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0710000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (25/120)
Device detected.....................
[------------------------------------------------------------]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: **** it
...................
Thanks,

Nemesis_00 said:
Hi,
1. Win7 Pro x64. Device connected to USB2.0
2. The installed drivers are "HTCDriver_4.8.0.001.exe" Could not find 002 anywhere.
3. I never had HTC Sync
4. Updated Android SDK with SDK Manager to latest version..
5. Antivirus unloaded completely, firewall (Windows) disabled.
6. FW Version reported by fastboot is 3.62.401.1, same as the one reported by the OS itself.
7. Not password/pin/face lock etc.
8. USB Debugging enabled, and Fast Boot disabled.
9. Rumrunner log is as follows:
Code:
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0710000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (25/120)
Device detected.....................
[------------------------------------------------------------]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: **** it
...................
Thanks,
Click to expand...
Click to collapse
Let me be honest, I have never tried (at least not yet ) rumrunner (I got S-Off with revone), but I did go through rumrunner thread, and the only two things I can think of, seeing your output:
Code:
Waiting for fastboot (7/120)
FATAL: **** it
that would be caused by the fastboot.exe (maybe the latest version is not the best )
Code:
...................
that's usually caused by a firewall or something else interfering with the internet connection.
I can't remember where I got the drivers from, but uploaded them for you:
HTCDriver_4.8.0.002.exe 15.1 MB
https://mega.co.nz/#!TAcGAJ7L!YdWM4AIji95b1ow8kVgagggOx5Yh7csRN5G0KJaCo6w
or you could, uninstall HTC xxxxxx, then download and install the latest HTC Sync Manager (from HTC web site), and then just uninstall the sync manager and keep drivers.
If all that doesn't work, I would give the Ubuntu Live CD/USB a try.

nkk71 said:
Let me be honest, I have never tried (at least not yet ) rumrunner (I got S-Off with revone), but I did go through rumrunner thread, and the only two things I can think of, seeing your output:
Code:
Waiting for fastboot (7/120)
FATAL: **** it
that would be caused by the fastboot.exe (maybe the latest version is not the best )
Code:
...................
that's usually caused by a firewall or something else interfering with the internet connection.
I can't remember where I got the drivers from, but uploaded them for you:
HTCDriver_4.8.0.002.exe 15.1 MB
https://mega.co.nz/#!TAcGAJ7L!YdWM4AIji95b1ow8kVgagggOx5Yh7csRN5G0KJaCo6w
or you could, uninstall HTC xxxxxx, then download and install the latest HTC Sync Manager (from HTC web site), and then just uninstall the sync manager and keep drivers.
If all that doesn't work, I would give the Ubuntu Live CD/USB a try.
Click to expand...
Click to collapse
As I've seen rumrunner has it's own fastboot.exe so I doubt it's that. There's also no firewall or anything, fastboot and adb work just fine on their own.
I've also S-OFF using revone, but later the emmc chip died, so I sent it for repair. Got it back with 1.54 hboot.
I'll give the Live CD a try later when I get the chance.

[Q] Converting my ONE into a GE Android

So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...
What can I do!?

elfrisi said:
So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...
What can I do!?
Click to expand...
Click to collapse
If you've still got s-off and can use fastboot, you could just change your CID and install a GE ruu.

davewuvswaffles said:
If you've still got s-off and can use fastboot, you could just change your CID and install a GE ruu.
Click to expand...
Click to collapse
I do have the S-OFF, however, once I enter the Fastboot menu, Windows wont recognize the device and wont let me push anything. It gets stuck in "Waiting for device". Ive installed the latest Google USB Device drivers using the SDK Manager and nothing has changed. :crying:

Try a different USB cable, or port, or a different computer..
Your phone says Fastboot or Fastboot USB?

Remove unneeded drivers
elfrisi said:
I do have the S-OFF, however, once I enter the Fastboot menu, Windows wont recognize the device and wont let me push anything. It gets stuck in "Waiting for device". Ive installed the latest Google USB Device drivers using the SDK Manager and nothing has changed. :crying:
Click to expand...
Click to collapse
If Windows PC can see phone in normal working state ( like MTP device / Android ADB / USB disk ect ... ) mean - you no need to worry - HW is OK, then try to use a small free tool called DeviceRemover and just clean unneeded ( wrong / old / damaged / ect.. ) FastBoot driver(s) from your system and then try again to connect phone in fastboot mode. Hint - use last tab "Display Mode" to select "Hidden / Deattached" devices - these that not work for you.

elfrisi said:
So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...
What can I do!?
Click to expand...
Click to collapse
You'll have to use a different computer, one running a pre windows 8.1 os.
Windows 8.1 only recognises fastboot for 1.55 or greater bootloaders at the moment.
I had the same situation and had to re-install windows 8 which was a bit drastic but solved this problem

If you're having trouble with the connection in Windows 8.1 like that your Phone does not get recognised, easiest solution get a Linux Live ISO on a USB stick.
Get Universal USB Installer from here http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Let it Download a UBUNTU Live ISO
Let the Programm install it on your USB stick and set the Persistent File Size to your liking
Boot from the stick
Open Terminal Window
Install "adb" and "fastboot" with .... sudo apt-get install android-tools-adb android-tools-fastboot
Connect the Phone and check if the Phone is recognised (fastboot devices or adb devices)
Do the update

Well, it was a driver issue. I did everything using the Mac OS X partition of my MacBook (for some odd reason I thought all this process was "exclusive" to Windows due to the exes and whatnot, but I was wrong). Now I am running the Stock Google Play Edition on my phone with no issues.

[Q] Trying to flash zip, now fastboot doesn't work

Hi Guys,
So I have successfully S-OFF'd my device using rumrunner, and I was then using the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2358781 in order to flash my device to a Google Play Edition device.
It worked fine for the commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip
and then I got the expected error message. I then entered the same command again as instructed, but this time I got the message "waiting for device" which didn't go away.
I've tried rebooting my phone a few times, and I can no longer get any fastboot.exe commands to work, I just continuously get the "waiting for device"message. adb.exe still works correctly, so after rebooting my phone I can use adb to boot into fastboot (I know that's not the only way, I'm just saying it to demonstrate that adb appears to be fine) but after that no fastboot.exe commands work anymore.
My phone is running Software version 3.62.401.1. My Hboot I was very sure used to be 1.55 but now after that failed "fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip" it now shows as HBOOT 1.54.
Thanks guys, any help would be immensely appreciated.

Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?

SaHiLzZ said:
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
Click to expand...
Click to collapse
Trying another fast boot package didn't work, but a different computer did. Now I'm all set and ready to go thanks!
Just for the record, on the first computer my phone no longer showed up when I put in fastboot devices. I guess for some strange reason there's now a problem with the drivers on the first computer? I thought perhaps reinstalling HTC Sync would help that apparently not.
Anyways, that problem is solved until I want to do this again and want to use the first computer again.

[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

[SOLVED]Any hope?

So i was trying to get my at&t htc one back to 100% stock so i could send it in for warranty. I got my replacement htc one, but while in the process of going back to stock something happened the phone wont load into recovery, when it boots into the os it stays at the htc screen but plays the at&t boot animation sound, and to top it off the old phone wont connect properly through usb (the new one will just fine). So i am stuck in bootloader anyone have any ideas?

crazyvash1 said:
So i was trying to get my at&t htc one back to 100% stock so i could send it in for warranty. I got my replacement htc one, but while in the process of going back to stock something happened the phone wont load into recovery, when it boots into the os it stays at the htc screen but plays the at&t boot animation sound, and to top it off the old phone wont connect properly through usb (the new one will just fine). So i am stuck in bootloader anyone have any ideas?
Click to expand...
Click to collapse
what guide are you using to get to stock ?
how far did you get ? are you s-off ?
what was the last version OS on the phone ? What hboot ?

clsA said:
what guide are you using to get to stock ?
how far did you get ? are you s-off ?
what was the last version OS on the phone ? What hboot ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2358738 this was the guide *Remove red warning from boot screen + custom hboot: http://forum.xda-developers.com/showthread.php?t=2316726 thats where things got messed up i pushed the FUU and flashed it thats where things got messed up. the phone is s-off Hboot-1.55.0000 and the os-1.20.401.1(3.10.502.2)
im guessing i screwed up and rushed things i just figured i would post as a last resort and get outside input before i decided if i should send it in as is send the new one back or what lol i appreciate any help.

crazyvash1 said:
http://forum.xda-developers.com/showthread.php?t=2358738 this was the guide *Remove red warning from boot screen + custom hboot: http://forum.xda-developers.com/showthread.php?t=2316726 thats where things got messed up i pushed the FUU and flashed it thats where things got messed up. the phone is s-off Hboot-1.55.0000 and the os-1.20.401.1(3.10.502.2)
im guessing i screwed up and rushed things i just figured i would post as a last resort and get outside input before i decided if i should send it in as is send the new one back or what lol i appreciate any help.
Click to expand...
Click to collapse
you should check this post before going any further
http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3
I don't know what you mean by I pushed the FUU and flashed it. do you mean you flashed firmware?
If you flashed a custom hboot with no red text you will brick the phone when you lock the bootloader.
Don't lock bootloader !!
Use this tool to remove Tampered and set to Locked
Guru_Bootloader_Reset_1.0.zip
http://www.androidfilehost.com/?fid=23501681358538585
MD5: fdb8264a8f4741bae22939cd7734f7c2
at this point just flash the AT&T RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
and see where your at.
From the Guide you linked
Before you can proceed with the 2 following threads for removing Tampered and then Locking you need to have Superuser installed. There are links to how to do this in each thread. You can also use this toolkit. Just remember to delete the SuperUser and busybox apk if installed before you return the phone.
2. - First remove the Tampered Flag. Instructions are in this thread
http://forum.xda-developers.com/showthread.php?t=2477792
3. - Second Lock the bootloader. Instructions are in this thread
http://forum.xda-developers.com/showthread.php?t=2475914
The older REVONE commands/instructions for Tampered and Locking:
Now since you had to install SuperUser to perform the previous 2 steps make sure you unroot by deleting the Superuser.apk and busybox.apk (If installed) from the /system/app folder and also the su binary from /system/xbin on your phone.
If you ran a RUU your systems firmware and software is all reset back to stock. If you restored via Stock ROM reset or Nandroid you should be running the stock software but it could be on non stock (version mismatch) firmware.
In either case your bootloader should display Locked and no Tampered just like out of the box. Now all that’s left is to S-On. To do that issue this fastboot command:
Code:
fastboot oem writesecureflag 3
Done - device should be just like it was out of the box with no indication of any modding.
*******I am not responsible for any problems you encounter. I am simply informing you of what is needed to complete a restoration to Stock. Read all steps and commands carefully and perform them in the correct order.********
Click to expand...
Click to collapse

clsA said:
you should check this post before going any further
http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3
I don't know what you mean by I pushed the FUU and flashed it. do you mean you flashed firmware?
If you flashed a custom hboot with no red text you will brick the phone when you lock the bootloader.
Don't lock bootloader !!
Use this tool to remove Tampered and set to Locked
Guru_Bootloader_Reset_1.0.zip
http://www.androidfilehost.com/?fid=23501681358538585
MD5: fdb8264a8f4741bae22939cd7734f7c2
at this point just flash the AT&T RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
and see where your at.
From the Guide you linked
Click to expand...
Click to collapse
the problem im having is the phone wont connect properly through usb to either of my computers ive tried different ports and different cables
This device cannot start. (Code 10)
A device which does not exist was specified.
thats the error i get in device status but my other htc connects perfect

crazyvash1 said:
the problem im having is the phone wont connect properly through usb to either of my computers ive tried different ports and different cables
This device cannot start. (Code 10)
A device which does not exist was specified.
thats the error i get in device status but my other htc connects perfect
Click to expand...
Click to collapse
are they both windows 8 computers ?
Windows 8.1 and hboot 1.44 don't get along
you'll have to use a driver hack to get it working

Both windows 8.1 like i said the weird part is one phone works perfect through usb the old one (the one i need to work) doesn't

crazyvash1 said:
Both windows 8.1 like i said the weird part is one phone works perfect through usb the old one (the one i need to work) doesn't
Click to expand...
Click to collapse
yeah .. here's the driver hack to make it work
Download
I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
Here are the steps:
0. Have a Linux or Windows LiveCD just in case something goes wrong
1. Download and extract files from attachment
2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
3. Right-click franken-usb.bat and click "Run as Administrator"
5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
6. Install ADB/Fastboot drivers just like on Windows 8
7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
8. Enjoy and wait for official fix
How does it work:
It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
Old files don't check for BOS descriptor so Fastboot can work.
Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!
Hope it helps you!
Regards!
Click to expand...
Click to collapse
Taken for here >> http://forum.xda-developers.com/showthread.php?p=49131915
It Works I been using it for over a year

Ok thank you very much i will try this when i get home from work tomorrow and hopefully its works for me then i can just follow the guide you posted to get back to stock then all will be good

im still getting the same issue with the drivers i made sure to manually install the files but still no luck.

Have you tried a Linux live boot disc? If you have troubles with Windows drivers, always fall back to Linux as it will always work if the device isn't faulty.
Sent from my HTC6500LVW using XDA Free mobile app

Uzephi said:
Have you tried a Linux live boot disc? If you have troubles with Windows drivers, always fall back to Linux as it will always work if the device isn't faulty.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
ive been trying with linux my issue now is just getting fasboot to work (as i have very little knowledge of linux) and still having no luck with windows im considering just sending the replacement they sent and then saving and buying a phone out right

crazyvash1 said:
ive been trying with linux my issue now is just getting fasboot to work (as i have very little knowledge of linux) and still having no luck with windows im considering just sending the replacement they sent and then saving and buying a phone out right
Click to expand...
Click to collapse
all you have to do is install the driver I linked reboot the pc
put the phone is fastboot USB mode and plug it into the pc.
if it's still not visible with fastboot devices
go to device manager find the failed driver / Unknown device
choose update driver / Browse for Driver / Let me Pick / uncheck show compatible hardware
Choose HTC on the left and My HTC Version 2.0.7.22 on the Right. ...Click next / click done ..

clsA said:
all you have to do is install the driver I linked reboot the pc
put the phone is fastboot USB mode and plug it into the pc.
if it's still not visible with fastboot devices
go to device manager find the failed driver / Unknown device
choose update driver / Browse for Driver / Let me Pick / uncheck show compatible hardware
Choose HTC on the left and My HTC Version 2.0.7.22 on the Right. ...Click next / click done ..
Click to expand...
Click to collapse
ok so i got it to work in fastboot now as for getting back to stock i am on hboot 1.55 and the os will not boot now i can flash the hboot 1.44 that you linked and i can use the gruu bootloader to get the tampered and set to lock (should i do this with having no working os on the phone?) and once you run the RUU.exe doesnt the phone need to be booted up and into the os? with usb debugging enabled or can i run it with it in the bootloader or fastboot? i just want to make sure im clear before i attempted to go through and do this again lol

crazyvash1 said:
ok so i got it to work in fastboot now as for getting back to stock i am on hboot 1.55 and the os will not boot now i can flash the hboot 1.44 that you linked and i can use the gruu bootloader to get the tampered and set to lock (should i do this with having no working os on the phone?) and once you run the RUU.exe doesnt the phone need to be booted up and into the os? with usb debugging enabled or can i run it with it in the bootloader or fastboot? i just want to make sure im clear before i attempted to go through and do this again lol
Click to expand...
Click to collapse
just do the steps in order
the RUU.exe step will put the OS back on the phone and your essentially done after that
From HTC ..ignore the t-mobile
Manual system update instructions:
If you are outside of T-Mobile/Wi-Fi coverage, or the update is not found, you may perform a manual system update. This process requires that you download and install HTC Sync Manager first in order to get the proper drivers. If you do not have HTC Sync Manager installed already, you may download the software from http://www.htc.com/www/software/htc-sync-manager/.
WARNING: Performing the system update manually will delete all information from the device. Ensure all information is backed up before proceeding. See the Help & How To section of this website for more information on backing up your device contents.
Performing the ROM Update:
1. Download and save the HTC One™ for T-Mobile ROM update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ for T-Mobile ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, the device is ready for use.
Note: If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit FASTBOOT manually, use the volume keys to navigate to REBOOT and press the POWER button to select it.
Click to expand...
Click to collapse

Thank you so much for your help everything is stock and perfect its all set and ready to be sent back

crazyvash1 said:
Thank you so much for your help everything is stock and perfect its all set and ready to be sent back
Click to expand...
Click to collapse
Very good ...just hit the thanks button and change the thread title to [solved] if you get time