Database Develop

[Q] M7 full wipe no system 6.12.161.8 M7_UL Vodafone

hi my problem is with my htc I wipe it full and I have no software on it , it is vodafone has HBOOT 1.57.0000 and firmware 6.12.161.8 they can help me back up to play a firmware ?:crying:
C:\Users\-\Desktop\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

XFX-Gaming said:
hi my problem is with my htc I wipe it full and I have no software on it , it is vodafone has HBOOT 1.57.0000 and firmware 6.12.161.8 they can help me back up to play a firmware ?:crying:
C:\Users\-\Desktop\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Remove your IMEI and SERIALNO from your getvar all.
I can't find any files useful to reset your phone back to stock 6.12.161.8 version. You should flash a custom recovery + a custom rom.

alray said:
Remove your IMEI and SERIALNO from your getvar all.
I can't find any files useful to reset your phone back to stock 6.12.161.8 version. You should flash a custom recovery + a custom rom.
Click to expand...
Click to collapse
how can I do that they can give me a manual or via teamviewer help me would be very grateful

XFX-Gaming said:
how can I do that they can give me a manual or via teamviewer help me would be very grateful
Click to expand...
Click to collapse
Follow this guide
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
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
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse

alray said:
Follow this guide
​
Click to expand...
Click to collapse
my htc is relocked

XFX-Gaming said:
my htc is relocked
Click to expand...
Click to collapse
same thing apply, follow the guide. (see 3rd prerequisite)

alray said:
same thing apply, follow the guide. (see 3rd prerequisite)
Click to expand...
Click to collapse
i have an error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found

XFX-Gaming said:
i have an error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Might be because your driver isn't installed (should not be the case if you have followed the guide)
or maybe because you haven't enabled USB debugging
Hoewever, just do it manually by holding power and volume down until your phone reboot in bootloader then select "recovery"

alray said:
Might be because your driver isn't installed (should not be the case if you have followed the guide)
or maybe because you haven't enable USB debugging
Hoewever, just do it manually by holding power and volume down until your phone reboot in bootloader then select "recovery"
Click to expand...
Click to collapse
and i have this problem
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrec
very-twrp-2.6.3.3-m7.img
target reported max download size of 1509875712 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.152s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s

XFX-Gaming said:
and i have this problem
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrec
very-twrp-2.6.3.3-m7.img
target reported max download size of 1509875712 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.152s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s
Click to expand...
Click to collapse
You are not following the guide! Make sure you have all prerequisites before starting and then proceed step by step.
You are having this error because your bootloader is locked/relocked (see 3rd prerequisite, click "show content" and see step 1)

alray said:
You are not following the guide! Make sure you have all prerequisites before starting and then proceed step by step.
You are having this error because your bootloader is locked/relocked (see 3rd prerequisite, click "show content" and see step 1)
Click to expand...
Click to collapse
yes my bootloader is relocked

So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file

alray said:
So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file
Click to expand...
Click to collapse
Yeah your dead right. Fixed this same issue in the Unbrick Thread just the other day.
Flashing the firmware and getting a new Unlock_code.bin fixed it.

alray said:
So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file
Click to expand...
Click to collapse
My German is not so great but look here >> http://www.handy-faq.de/forum/htc_o...c_one_firmwaresammlung_ruus_otas_backups.html

Here you go
zHi5k0 said:
My stautus is relocked. This is the problem. When I'm trying to unlock it with HTCDev method it 's trying to get to recovery but there's no recovery.
Click to expand...
Click to collapse
Danny201281 said:
Ok that makes some sense, you probably have a minor firmware incompatiblity that's causing this problem.
Download this firmware zip and put it in your fastboot folder. Rename it "firmware.zip"
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.11.zip
Reboot the phone into the bootloader and connect fastbootusb.
In the fastboot command line type.
Code:
fastboot erase cache
fastboot oem rebootRUU
**---case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
When that's done go to htcdev.com and go through the entire unlock my bootloader to get a new Unlock_code.bin then use it to Unlock your bootloader. :good:
The firmware will also restore your Stock Recovery, so after the unlock you will need to flash a new custom recovery.
Click to expand...
Click to collapse
zHi5k0 said:
I have an unlocked phone now. Thank you very much. I have no words about the help you did to me. Please tell me what should I do for getting the phone back to stock without bricking it again.
Click to expand...
Click to collapse

Danny201281 said:
Yeah your dead right. Fixed this same issue in the Unbrick Thread just the other day.
Flashing the firmware and getting a new Unlock_code.bin fixed it.
Click to expand...
Click to collapse
Thanks for the info
clsA said:
My German is not so great but look here >> http://www.handy-faq.de/forum/htc_o...c_one_firmwaresammlung_ruus_otas_backups.html
Click to expand...
Click to collapse
Nice collection, everything about x.xx.161.x can be found there... except the 6.12.161.8 firmware or ota we need
Btw the OP also have a thread about his issue on that forum here
and it looks like even them don't have the 6.12.161.8 firmware
will ask in the update thread just in case someone have it.

Mike1986 has 6.12.161.5 in his repository but thats the closest i can find

@alray, i'm capturing 6.12.161.9 OTA (didnt get the .8 one, got straight to .9).... i'll post firmware once i have it

@alray here is the signed firmware from 6.12.161.9
https://www.dropbox.com/s/ov1x96x8c5qhyb6/signed_ota_firmware_6.12.161.9.zip?dl=0
Code:
modelid: PN0710000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAPE17
cidnum: VODAP405
cidnum: VODAP304
cidnum: VODAPD18
cidnum: VODAP120
cidnum: VODAP110
mainver: 6.12.161.9
btype:1
aareport:1
hbootpreupdate:3
as this is only an OTA update it only contains:
Code:
android-info.txt
boot.img
hboot_signedbyaa.img
rcdata.img
recovery.img
splash1.nb0
I was able to capture (even while on SuperCID )
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.5-5.16.161.2_release_387413_VodaIT.zip (608 MB)
then
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.9-6.12.161.5_release_401650aawyk6dy4kqo5flm.zip (250 MB)
don't know why no 6.12.161.8.... i'll try again in a bit (using different CID), so if you wanna wait to see if i can get the .8 version i'll let you know shortly....
@alray EDIT: just changed cid to VODAP102 and got the 6.12.161.8 update info..... downloading... (i've removed the other one from my dropbox)

nkk71 said:
@alray here is the signed firmware from 6.12.161.9
https://www.dropbox.com/s/ov1x96x8c5qhyb6/signed_ota_firmware_6.12.161.9.zip?dl=0
Code:
modelid: PN0710000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAPE17
cidnum: VODAP405
cidnum: VODAP304
cidnum: VODAPD18
cidnum: VODAP120
cidnum: VODAP110
mainver: 6.12.161.9
btype:1
aareport:1
hbootpreupdate:3
as this is only an OTA update it only contains:
Code:
android-info.txt
boot.img
hboot_signedbyaa.img
rcdata.img
recovery.img
splash1.nb0
I was able to capture (even while on SuperCID )
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.5-5.16.161.2_release_387413_VodaIT.zip (608 MB)
then
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.9-6.12.161.5_release_401650aawyk6dy4kqo5flm.zip (250 MB)
don't know why no 6.12.161.8.... i'll try again in a bit (using different CID), so if you wanna wait to see if i can get the .8 version i'll let you know shortly....
@alray EDIT: just changed cid to VODAP102 and got the 6.12.161.8 update info..... downloading... (i've removed the other one from my dropbox)
Click to expand...
Click to collapse
Thanks so much!
 @XFX-Gaming New hope :good:

[Q] Need to Restore to stock

If this is posted in the wrong place I apologize in advance :angel:
Scenario:
I currently own 2 HTC One M7's -One is my daily driver, which is running stock (Lollipop) which works fine with no errors. Never been rooted / anything done to it.
The second is a 'Spare' one which I purchased from a friend rather than having him recycle it for cheap, as there's no hardware fault, he just wanted an upgrade.
This 2nd device is currently rooted -Looks like with TWRP, running a HTC Dev version.
It does not show as "Tampered"
It does show as "Unlocked"
From the BIOS<? screen it is currently S-OFF
Phones original carrier is O2 UK
The only issue with this as far as I can see is that is fails to update, so its running Android 4.4.2 Sense version 5.5 - When installing any update from the 'software updates' area the phone crashes and resets/wipes itself.
What I'm Seeking:
Can anyone link me to a word by word / specific guide in restoring this to (Unlocked) factory stock? Or how to take an image of my first phone and duplicate it onto the second.
End result I would like the phone back to stock, UNLOCKED to accept any SIM so it can be updated and used like a 'normal' phone (To me normal means that nothing has been done to the phone at all relating to rooting -If that makes sense.) with the ability to update and do whatever my 1st phone can without error or major intervention :victory:
I've tried to find an online guide for the past week or 2, with the required software/file however everything I find is either out of date (So it's links no longer work) or expects me to already have all the tools and know how to use them (Which I don't, at all! :crying: )
Reason: I've never been a fan of rooted phones/doing anything I don't fully understand, and don't want the hassle of having to update it manually. That and I don't like old-android.
Love anyone who takes the time to assist me (No-Homo) :highfive:

mentize said:
If this is posted in the wrong place I apologize in advance :angel:
Scenario:
I currently own 2 HTC One M7's -One is my daily driver, which is running stock (Lollipop) which works fine with no errors. Never been rooted / anything done to it.
The second is a 'Spare' one which I purchased from a friend rather than having him recycle it for cheap, as there's no hardware fault, he just wanted an upgrade.
This 2nd device is currently rooted -Looks like with TWRP, running a HTC Dev version.
It does not show as "Tampered"
It does show as "Unlocked"
From the BIOS<? screen it is currently S-OFF
Phones original carrier is O2 UK
The only issue with this as far as I can see is that is fails to update, so its running Android 4.4.2 Sense version 5.5 - When installing any update from the 'software updates' area the phone crashes and resets/wipes itself.
What I'm Seeking:
Can anyone link me to a word by word / specific guide in restoring this to (Unlocked) factory stock? Or how to take an image of my first phone and duplicate it onto the second.
End result I would like the phone back to stock, UNLOCKED to accept any SIM so it can be updated and used like a 'normal' phone (To me normal means that nothing has been done to the phone at all relating to rooting -If that makes sense.) with the ability to update and do whatever my 1st phone can without error or major intervention :victory:
I've tried to find an online guide for the past week or 2, with the required software/file however everything I find is either out of date (So it's links no longer work) or expects me to already have all the tools and know how to use them (Which I don't, at all! :crying: )
Reason: I've never been a fan of rooted phones/doing anything I don't fully understand, and don't want the hassle of having to update it manually. That and I don't like old-android.
Love anyone who takes the time to assist me (No-Homo) :highfive:
Click to expand...
Click to collapse
can you post the output of "fastboot getvar all" from the phone you want to restore back to stock (don't post the imei# nor serialno#)? Is that phone already sim-unlocked? (btw ***unlocked*** in the bootloader doesn't mean sim-unlocked but bootloader unlocked). If yes, it will stay sim-unlocked forever if no you'll need to unlock it.
Wait for your "fastboot getvar all" then we can start reverting back to stock.

alray said:
can you post the output of "fastboot getvar all" from the phone you want to restore back to stock (don't post the imei# nor serialno#)? Is that phone already sim-unlocked? (btw ***unlocked*** in the bootloader doesn't mean sim-unlocked but bootloader unlocked). If yes, it will stay sim-unlocked forever if no you'll need to unlock it.
Wait for your "fastboot getvar all" then we can start reverting back to stock.
Click to expand...
Click to collapse
The phone is currently sim-unlocked, and I want it to stay that way.
@alray Requested Information:
C:\Users\XXXX>Fastboot getvar all
<bootloader> version: 0.5
<bootloader> version-bootloader: 1.56.0000
<bootloader> version-baseband: 4A.25.3263.21
<bootloader> version cpld: None
<bootloader> version-microp: None
<bootloader> version-main: 4.19.401.11
<bootloader> version-misc: PVT SHIP S-OFF
<bootloader> Serialno: XXXXXXXXXXXX
<bootloader> meid: XXXXXXXXXXXXXX
<bootloader> product: m7_u1
<bootloader> platform: HBOOT-8064
<bootloader> modelid: PN0710000
<bootloader> cidum: HTC__001
<bootloader> battery-status: good
<bootloader> battery-voltage: 4178mV
<bootloader> partition-layout: Generic
<bootloader> security: off
<bootloader> build-mode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> commitno-bootloader: dirty-4dab9d12
<bootloader> hbootpreupdate: 11
<bootloader> hencheckpt: 0
all: Done!
finished. total time: 0.087s

mentize said:
The phone is currently sim-unlocked, and I want it to stay that way.
@alray Requested Information:
C:\Users\XXXX>Fastboot getvar all
<bootloader> version: 0.5
<bootloader> version-bootloader: 1.56.0000
<bootloader> version-baseband: 4A.25.3263.21
<bootloader> version cpld: None
<bootloader> version-microp: None
<bootloader> version-main: 4.19.401.11
<bootloader> version-misc: PVT SHIP S-OFF
<bootloader> Serialno: XXXXXXXXXXXX
<bootloader> meid: XXXXXXXXXXXXXX
<bootloader> product: m7_u1
<bootloader> platform: HBOOT-8064
<bootloader> modelid: PN0710000
<bootloader> cidum: HTC__001
<bootloader> battery-status: good
<bootloader> battery-voltage: 4178mV
<bootloader> partition-layout: Generic
<bootloader> security: off
<bootloader> build-mode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> commitno-bootloader: dirty-4dab9d12
<bootloader> hbootpreupdate: 11
<bootloader> hencheckpt: 0
all: Done!
finished. total time: 0.087s
Click to expand...
Click to collapse
You could flash the stock 7.19.401.2 ruu. Instruction and files in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(make sure to use the 7.19.401.2 version not the 7.19.401.102 one)

alray said:
You could flash the stock 7.19.401.2 ruu. Instruction and files in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(make sure to use the 7.19.401.2 version not the 7.19.401.102 one)
Click to expand...
Click to collapse
@alray
I have downloaded both the RUU and Fastboot exe - the fastboot file was not called "HTC_Fastboot.exe" it was just called fastboot.exe, i assume this is correct?
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Rename htc_fastboot to fastboot or if you don't rename the htc_fastboot.exe, then the command will be htc_fastboot flash zip RUU.zip
6. htc_fastboot oem rebootRUU -done
7.htc_fastboot flash zip RUU.zip -when doing this I am told "Cannot open file RUU.zip"
Ideas?

mentize said:
@alray
I have downloaded both the RUU and Fastboot exe - the fastboot file was not called "HTC_Fastboot.exe" it was just called fastboot.exe, i assume this is correct?
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Rename htc_fastboot to fastboot or if you don't rename the htc_fastboot.exe, then the command will be htc_fastboot flash zip RUU.zip
6. htc_fastboot oem rebootRUU -done
7.htc_fastboot flash zip RUU.zip -when doing this I am told "Cannot open file RUU.zip"
Ideas?
Click to expand...
Click to collapse
can not open file error is caused by fastboot not finding the ruu. the ruu must be in the same folder as fastboot (htc's fastboot) and must be name "ruu" or "ruu.zip" if file extension are not hidden by default by windows.
And yes the file linked as htc_fastboot.exe is now named only fastboot.exe.Make sure to use this one.
Can you post a screenshot of your fastboot folder please?

alray said:
can not open file error is caused by fastboot not finding the ruu. the ruu must be in the same folder as fastboot (htc's fastboot) and must be name "ruu" or "ruu.zip" if file extension are not hidden by default by windows.
And yes the file linked as htc_fastboot.exe is now named only fastboot.exe.Make sure to use this one.
Can you post a screenshot of your fastboot folder please?
Click to expand...
Click to collapse
@alray - see attached screenshot

mentize said:
@alray - see attached screenshot
[edit] - nvm, rebooted phone, got past error that was originally put here - back to not seeing file
Click to expand...
Click to collapse
You have double file extension at your ruu file. See how the .exe extension of adb and fastboot are hidden? Its the same thing for the zip file. Zip file are considered "known file type" by windows so by default the extension (.zip) is hidden. By renaming the file "ruu.zip" you have double file extension (ruu.zip + the hidden .zip = ruu.zip.zip)
So delete the .zip from the file name and try the command again. Should work fine.
To avoid this kind of problem in the future, you can change windows settings to never hide files extension
http://windows.microsoft.com/en-us/...ions#show-hide-file-name-extensions=windows-7

alray said:
You have double file extension at your ruu file. See how the .exe extension of adb and fastboot are hidden? Its the same thing for the zip file. Zip file are considered "known file type" by windows so by default the extension (.zip) is hidden. By renaming the file "ruu.zip" you have double file extension (ruu.zip + the hidden .zip = ruu.zip.zip)
So delete the .zip from the file name and try the command again. Should work fine.
Click to expand...
Click to collapse
@alray
Done - same error.
Will re-start the whole process in-case it didn't detect the name change and update this post/reply accordingly
[EDIT] - restarted process (so let phone start up, re-booted into oem reboot. Same error

mentize said:
@alray
Done - same error.
Will re-start the whole process in-case it didn't detect the name change and update this post/reply accordingly
[EDIT] - restarted process (so let phone start up, re-booted into oem reboot. Same error
Click to expand...
Click to collapse
post a screenshot of your command prompt

alray said:
post a screenshot of your command prompt
Click to expand...
Click to collapse
@alray - see attachments. I've also posted the new folder.
I have tried leaving the .zip off the end of the command, same error.
-update, forgot attachments, will update in 4 minutes (forum spam filter)

mentize said:
@alray - see attachments. I've also posted the new folder.
I have tried leaving the .zip off the end of the command, same error.
-update, forgot attachments, will update in 4 minutes (forum spam filter)
Click to expand...
Click to collapse
Try to flash the firmware first then the ruu. You can download the firmware here: https://www.androidfilehost.com/?fid=95916177934534374
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
and then using htc's fastboot:
Code:
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot reboot
you could also check the md5 of the ruu and confirm its not corrupted/bad download.

alray said:
Try to flash the firmware first then the ruu. You can download the firmware here: https://www.androidfilehost.com/?fid=95916177934534374
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
and then using htc's fastboot:
Code:
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot reboot
you could also check the md5 of the ruu and confirm its not corrupted/bad download.
Click to expand...
Click to collapse
Downloaded the firmware from provided link - replaced the fastboot file with the original - copy / pasted the command given - Error "Cannot Load M7_UL_Firmware_7.19.401.2.zip"

mentize said:
Downloaded the firmware from provided link - replaced the fastboot file with the original - copy / pasted the command given - Error "Cannot Load M7_UL_Firmware_7.19.401.2.zip"
Click to expand...
Click to collapse
did you started your command prompt from the same folder where fastboot is? I see in your command prompt screenshot that you are working from the folder C:\User\Jason> when fastboot and other files are in C:\User\Jason\AppData\local\Android\android-sdk\platform-tools>
thats probably why fastboot is giving you the "can not load" error. Its not finding the file because you did not changed directory of your command prompt...

alray said:
did you started your command prompt from the same folder where fastboot is? I see in your command prompt screenshot that you are working from the folder C:\User\Jason> when fastboot and other files are in C:\User\Jason\AppData\local\Android\android-sdk\platform-tools>
thats probably why fastboot is giving you the "can not load" error. Its not finding the file because you did not changed directory of your command prompt...
Click to expand...
Click to collapse
@alray
-Moved CMD, now get the attached error

mentize said:
@alray
-Moved CMD, now get the attached error
Click to expand...
Click to collapse
you are doing:
Code:
fastboot reboot
fastboot flash zip ruu.zip
when you should do:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
don't forget to use htc's version of fastboot. This fastboot version must be in the same folder.
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
I have to go at work. Will try to answer you in my 1st break if it still not working otherwise i'll be back tomorrow to help you. Meanwhile there is many other ppl here that can help you.
good luck

alray said:
you are doing:
Code:
fastboot reboot
fastboot flash zip ruu.zip
when you should do:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
don't forget to use htc's version of fastboot. This fastboot version must be in the same folder.
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
I have to go at work. Will try to answer you in my 1st break if it still not working otherwise i'll be back tomorrow to help you. Meanwhile there is many other ppl here that can help you.
good luck
Click to expand...
Click to collapse
I'm aware of the commands being used - I am deliberately doing non-oem reboots whenever i 'restart' the cycle, to ensure nothing is stuck before trying again.
@alray - Appreciate all your help, I've restarted both the phone & computer and tried again - see attached screenshot of where we are up too.
Double checked the fastboot is the HTC one, and is in the correct folder, along with the RUU file.
(Ignore that it says 25s to execute the reboot, that's because i forgot to boot the phone into fastboot manually from power-up.
I'm off to sleep, wont be back on for another 9hours or so (yay days off work :victory: )

Come back to this today:
Completely re-installed the platform-tools folder
Re-downloaded both the RUU & HTC Fastboot from different mirrors
Confirmed ADB can see the device
Replaced original Fastboot with HTC Fastboot
Placed the RUU file in the same directory
Ran "Fastboot oem rebootruu"
--Phone rebooted into a black-screen with "HTC" in the centre
Ran "Fastboot flash zip ruu.zip"
---Fastboot.exe has stopped responding (CMD states too many threads same as in previous screenshots)

mentize said:
Come back to this today:
Completely re-installed the platform-tools folder
Re-downloaded both the RUU & HTC Fastboot from different mirrors
Confirmed ADB can see the device
Replaced original Fastboot with HTC Fastboot
Placed the RUU file in the same directory
Ran "Fastboot oem rebootruu"
--Phone rebooted into a black-screen with "HTC" in the centre
Ran "Fastboot flash zip ruu.zip"
---Fastboot.exe has stopped responding (CMD states too many threads same as in previous screenshots)
Click to expand...
Click to collapse
I think you should try using a windows 7 computer. Looks like windows 8 doesn't like htc's fastboot... This fastboot works fine on my computer and downloaded from the same link.

hey guys, i'm trying to the same thing,
did the flashboot oem rebootRUU, which was fine, then i got this:
C:\Users\hp\Desktop\Minimal ADB and Fastboot>fastboot flash zip RUU.zip
sending 'zip'... (43286 KB) OKAY
sending time = 3.114 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 10(s)
any ideas>?>?

Soft bricked my HTC ONE M7_UL (S-ON,HBOOT 1.57) Have access to TWRP

Evening,
I've been desperately trying to figure this out myself but I've concluded that it's too complex for me to go it alone, as it stands my HTC one M7_UL is I believe soft bricked, I can get to the bootloader and into TWRP recovery but I've had no luck with FASTBOOT/ADB, I can sideload a rom.zip but it just fails to do anything after 100%, I reboot it and it just gets stuck on the previous bootloop. Currently have no OS installed and honestly I don't have a clue what I'm doing, exactly why I'm in this mess in the first place, I bricked it a while ago but I figure I wiped system partitions and as a result am in a bad place any advice you could offer would be brilliant.
Thank you in advance, I've included some additional details below but let me know if I've missed anything.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA39PWxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-44d68d6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
Also I get this as well not sure if it's a problem but I haven't seen it anywhere else -
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx offline
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx sideload

mattage101 said:
Evening,
I've been desperately trying to figure this out myself but I've concluded that it's too complex for me to go it alone, as it stands my HTC one M7_UL is I believe soft bricked, I can get to the bootloader and into TWRP recovery but I've had no luck with FASTBOOT/ADB, I can sideload a rom.zip but it just fails to do anything after 100%, I reboot it and it just gets stuck on the previous bootloop. Currently have no OS installed and honestly I don't have a clue what I'm doing, exactly why I'm in this mess in the first place, I bricked it a while ago but I figure I wiped system partitions and as a result am in a bad place any advice you could offer would be brilliant.
Thank you in advance, I've included some additional details below but let me know if I've missed anything.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA39PWxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-44d68d6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
Also I get this as well not sure if it's a problem but I haven't seen it anywhere else -
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx offline
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx sideload
Click to expand...
Click to collapse
What is your twrp version?

alray said:
What is your twrp version?
Click to expand...
Click to collapse
TWRP v2.6.3.0
Thanks for the interest!

mattage101 said:
TWRP v2.6.3.0
Thanks for the interest!
Click to expand...
Click to collapse
You should take a few minutes and update your twrp first because there's not much you'll be able to flash with this version and also because newer version will allow you to use mtp instead of sideload (you'll be able to see your phone storage from your computer when booted in TWRP like if it was a thumb drive)
Here is the link to download the latest version (3.0.M5.0) http://android.cmphys.com/twrp-m7/
Save the file in your fastboot/adb folder. With the phone booted in bootloader mode showing "fastboot usb" in red, start a command window and type:
Code:
fastboot flash recovery twrp-3.0.M5-0-m7univ.img
fastboot erase cache
fastboot reboot-bootloader
then you can restore this twrp backup: https://www.androidfilehost.com/?fid=95897840722646675
To restore a backup,boot in twrp and make a backup of boot.img only (this is only to generate a backup path). Then using twrp's files manager navigate to /sdcard/TWRP/BACKUPS/your_serial_number/date_of_backup and delete backup files in this folder and replace them by the files contained in the nandroid backup you want to use. Then select "restore" and restore all available partitions.

alray said:
You should take a few minutes and update your twrp first because there's not much you'll be able to flash with this version and also because newer version will allow you to use mtp instead of sideload (you'll be able to see your phone storage from your computer when booted in TWRP like if it was a thumb drive)
Here is the link to download the latest version (3.0.M5.0)
Save the file in your fastboot/adb folder. With the phone booted in bootloader mode showing "fastboot usb" in red, start a command window and type:
Code:
fastboot flash recovery twrp-3.0.M5-0-m7univ.img
fastboot erase cache
fastboot reboot-bootloader
then you can restore this twrp backup:
To restore a backup,boot in twrp and make a backup of boot.img only (this is only to generate a backup path). Then using twrp's files manager navigate to /sdcard/TWRP/BACKUPS/your_serial_number/date_of_backup and delete backup files in this folder and replace them by the files contained in the nandroid backup you want to use. Then select "restore" and restore all available partitions.
Click to expand...
Click to collapse
Mate. MATE! I can't thank you enough, got it to work, cheers buddy - for what it's worth you're awesome!

mattage101 said:
Mate. MATE! I can't thank you enough, got it to work, cheers buddy - for what it's worth you're awesome!
Click to expand...
Click to collapse
I do have one question though, why when I try to update the OS does it reboot into TWRP, am I suppose to update it from in there?

mattage101 said:
I do have one question though, why when I try to update the OS does it reboot into TWRP, am I suppose to update it from in there?
Click to expand...
Click to collapse
In order to flash the official OTA you need stock recovery. You can't update your phone the official way with custom recovery

HTC One
I followed your instructions, copied all the downloaded files to the Date folder, except the file "system.ext4.win000" 1.5GB. It hangs, won't go past approx. 15-20%. I tried a very similar method yesterday, and the same happened.

vik919 said:
I followed your instructions, copied all the downloaded files to the Date folder, except the file "system.ext4.win000" 1.5GB. It hangs, won't go past approx. 15-20%. I tried a very similar method yesterday, and the same happened.
Click to expand...
Click to collapse
Try another usb cable and another usb port. I would also format data.
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
mattage101 said:
I do have one question though, why when I try to update the OS does it reboot into TWRP, am I suppose to update it from in there?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95897840722646669

alray said:
Try another usb cable and another usb port. I would also format data.
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
https://www.androidfilehost.com/?fid=95897840722646669
Click to expand...
Click to collapse
So I flashed the stock recovery .img you linked and I searched for software updates, clicked ok and it reboots and comes up with a screen with a phone displaying a green triangle, after a couple of minutes the triangle turns red, I pressed the power button and the volume up button so I could see the error report and I got this:
Finding update package...
opening update package...
Verifying update package...
Installing update...
Verifying current system...
Check /data/preload/SoundHound_Freemium.apk failed, error No such file or directory()
Installation aborted.
Write host_mode:0 done
What do you make of it?
Thanks again for all your responses, genuinely appreciate it!

mattage101 said:
Verifying current system...
Check /data/preload/SoundHound_Freemium.apk failed, error No such file or directory()
Click to expand...
Click to collapse
Looks like the nandrdoid backup was missing the files in /data/preload. When unlocking the bootloader, /data is wiped to prevent unauthorized access to your files. Unfortunately HTC packed a few stock apps in /data/preload so these apps are lost when unlocking. So the person who made that nandroid backup did it after unlocking the bootloader hence why the missing files. Sorry
When installing an OTA update, the updater-script check for all the files to be updated (thousand of files). They must all be there and as expected (not modded or corrupt). If only one of these files is missing/corrupt, the ota installation will abort, this is to prevent patching wrong files and making your system unusable.
This can usually be corrected by restoring the missing files. Unfortunately I can't find the /data/preload files for your version...
Another option would be to update your firmware so you can flash the latest version using a RUU
Download these 3 files and save them in your adb/fastboot folder on your computer:
https://www.androidfilehost.com/?fid=95916177934535002
https://www.androidfilehost.com/?fid=24385226645962836
https://www.androidfilehost.com/?fid=24341993505161791
re-lock your bootloader (needed since your phone is S-ON):
Code:
fastboot oem lock
Update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot reboot-bootloader
Flash the RUU:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459056_signed.zip
fastboot reboot

alray said:
Looks like the nandrdoid backup was missing the files in /data/preload. When unlocking the bootloader, /data is wiped to prevent unauthorized access to your files. Unfortunately HTC packed a few stock apps in /data/preload so these apps are lost when unlocking. So the person who made that nandroid backup did it after unlocking the bootloader hence why the missing files. Sorry
When installing an OTA update, the updater-script check for all the files to be updated (thousand of files). They must all be there and as expected (not modded or corrupt). If only one of these files is missing/corrupt, the ota installation will abort, this is to prevent patching wrong files and making your system unusable.
This can usually be corrected by restoring the missing files. Unfortunately I can't find the /data/preload files for your version...
Another option would be to update your firmware so you can flash the latest version using a RUU
Download these 3 files and save them in your adb/fastboot folder on your computer:
https://www.androidfilehost.com/?fid=95916177934535002
https://www.androidfilehost.com/?fid=24385226645962836
https://www.androidfilehost.com/?fid=24341993505161791
re-lock your bootloader (needed since your phone is S-ON):
Code:
fastboot oem lock
Update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot reboot-bootloader
Flash the RUU:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459056_signed.zip
fastboot reboot
Click to expand...
Click to collapse
Ok I'm all sorted that worked, thanks for your time!

802w bricked, "decrypt storage"

Hi there.
Well, my 802w (M7Cdug) is bricked. First it used to have this cycle of "turn on - work for a couple of minutes - restart - work for a couple of minutes", when I woke up next day after leaving it on cable I got this message of "decrypt storage, to start Android enter your password", of course whatever password I write it ends up with "pasword is correct, but data is corrupt", then it suggests to hard reset the phone. Doing that ends up with opening the Android system recovery with the following info in the log:
Code:
E:failed to mount /data (Invalid argument).. try emmc mount handle_cota_install: Can't mount /data/data/cwtemp/cwpkg.zi, 508056 times
Wiping cache partition (which is completed) and wiping data (which ends up with the same info and information on completion) does nothing.
Getting to the bootloader it says it's locked.
What else have I tried (I'm a real newbie in this topic so I might have done something absolutely stupid which couldn't have worked, but if you have any solution, please tell me):
* Unlocking: using the command "fastboot flash unlocktoken Unlock_code.bin" makes the phone show the "Unlock bootloader?" screen, choosing yes restarts it and makes it go back to the recovery screen, going back to the bootloader it's still locked.
* Moonshine S-OFF: ends up with "ERROR: run distiller again and READ"
* Minimal ADB and Fastboot & TWRP: the device is connected, doing the "fastboot flash recovery" ends up with "(bootloader) signature checking... FAILED (remote: signature verify fail)" and the "fastboot oem unlock" with "Command error".
* Minimal ADB and Fastboot & RUU: running "rebootRUU" ends up with phone again at the decrypt screen, getting it back there and running flash zip RUU.zip ends up with: signature checking / rom parsing start / rom parsing finish / FAILnot allowed / FAIL (remote: not allowed)"
I'm out of ideas - maybe I'm doing something wrong? If you guys have any idea what can help or if you'd like to help eg. via a TeamViewer I would be really thankful - having a $200 brick is not really satysfying, as well as having to use a shabby Xperia J with a broken screen as I can't afford anything new
If you need some info on what files should be used here's some stuff I got from fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.19.3509.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.402.55
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4281mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d0e3b226
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Bump?

Like... seriously? Nothing can be done?

YacoobPL said:
Wiping cache partition (which is completed) and wiping data (which ends up with the same info and information on completion) does nothing.
Click to expand...
Click to collapse
* Unlocking: using the command "fastboot flash unlocktoken Unlock_code.bin" makes the phone show the "Unlock bootloader?" screen, choosing yes restarts it and makes it go back to the recovery screen, going back to the bootloader it's still locked.
Click to expand...
Click to collapse
* Minimal ADB and Fastboot & RUU: running "rebootRUU" ends up with phone again at the decrypt screen
Click to expand...
Click to collapse
These 3 symptoms make it sounds like your Emmc might be faulty
* Minimal ADB and Fastboot & TWRP: the device is connected, doing the "fastboot flash recovery" ends up with "(bootloader) signature checking... FAILED
Click to expand...
Click to collapse
You must have an unlocked bootloader to flash the recovery partition, it can't be unlocked so trying to flash recovery is useless, will not work.
"fastboot oem unlock" with "Command error".
Click to expand...
Click to collapse
fastboot oem unlock isn't a supported command on your model, on the GPE variant can be unlocked this way.
,
* Minimal ADB and Fastboot & RUU: running "rebootRUU" ends up with phone again at the decrypt screen getting it back there and running flash zip RUU.zip ends up with: signature checking / rom parsing start / rom parsing finish / FAILnot allowed / FAIL (remote: not allowed)"
Click to expand...
Click to collapse
Getting it back where? In bootloader? RUU can only be flashed when booted in RUU mode (black screen with silver HTC logo). If you're not booted at this screen, trying to flash RUU is useless, will not work.
If you guys have any idea what can help
Click to expand...
Click to collapse
The dual sim variant can be flashed using the external sd card. Rename the RUU file to "PN071IMG.zip" (watch out for souble file extension when renaming). Move the file at the root of your external sd card (must be formatted using FAT32), reboot in bootloader mode and you should be asked if you want to update. Btw what RUU were you using? With S-On you can only use the same (or newer) RUU than your version-main number (you're already on the newest version so only the 7.17.402.55 should work, hope you already have it cause I cant find this version).
Also the ouput of "fastboot oem dmesg" and "fastboot oem last_dmesg" might help determine any hardware failure.

New to forum - Help Required

I got a HTC phone from a friend and I do not know how to find out the model. Also it does not have an OS on it and I am looking to find out how to install one. I read a few of the threads and could not figure out what the terms meant. Such as OTG, RUU,ADB, TWRP, ETC. So I am not able to follow. Please assist me if you can.

You say it doesn't have an OS on it, so it's basically a blank device that you need to install an OS on.
Th easiest way for us to identify it would be for you to take a photo of it and post it here for us to look at. Once we know what model of HTC you have, we can easily help you get Android back on there.
Or if you can find it on the HTC website, that would help. Or even Google somewhere.

the_scotsman said:
You say it doesn't have an OS on it, so it's basically a blank device that you need to install an OS on.
Th easiest way for us to identify it would be for you to take a photo of it and post it here for us to look at. Once we know what model of HTC you have, we can easily help you get Android back on there.
Or if you can find it on the HTC website, that would help. Or even Google somewhere.
Click to expand...
Click to collapse
I found that it is an HTC One M7.

Ah in that case, take a look in our HTC One M7 forums: https://forum.xda-developers.com/htc-one
In "HTC language", an RUU is a ROM, which is what you need in order to flash the OS back onto your device.
I haven't owned an HTC for a number of years now, so I can't recall the place place to find stock firmware (RUU) files.
I will move this thread to the M7 Q&A forum for you, so that hopefully someone else can assist you further.
It will probably help if you can let us know which region you are from, as firmware is often region specific. Which country?

the_scotsman said:
Ah in that case, take a look in our HTC One M7 forums: https://forum.xda-developers.com/htc-one
In "HTC language", an RUU is a ROM, which is what you need in order to flash the OS back onto your device.
I haven't owned an HTC for a number of years now, so I can't recall the place place to find stock firmware (RUU) files.
I will move this thread to the M7 Q&A forum for you, so that hopefully someone else can assist you further.
It will probably help if you can let us know which region you are from, as firmware is often region specific. Which country?
Click to expand...
Click to collapse
I am located in the United States. Montana.

Prayerwimp said:
I am located in the United States. Montana.
Click to expand...
Click to collapse
We"ll need a bit more info to indentify your phone. If you dont already have adb and fastboot installed on your computer, Google search for "minimal adb and fastboot". You should find an xda thread explaining how to set up adb and fastboot. Once done youll also need to install HTC drivers. It can be done by installing HTC Sync manager from htc's website. Then connect your phone using the usb calbe, boot in bootloader mode (power + volume down). Start the minimal adb and fastboot terminal window and type "fastboot getvar all" (without the quotes. Post the output of that command in this thread (take care to remove the imei and serialno lines before posting).

alray said:
We"ll need a bit more info to indentify your phone. If you dont already have adb and fastboot installed on your computer, Google search for "minimal adb and fastboot". You should find an xda thread explaining how to set up adb and fastboot. Once done youll also need to install HTC drivers. It can be done by installing HTC Sync manager from htc's website. Then connect your phone using the usb calbe, boot in bootloader mode (power + volume down). Start the minimal adb and fastboot terminal window and type "fastboot getvar all" (without the quotes. Post the output of that command in this thread (take care to remove the imei and serialno lines before posting).
Click to expand...
Click to collapse
I have installed the "minimal adb and fastboot" and HTC Sync manager.
This is what I came up with:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(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: 3774mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you for your time and assistance. Next step please.

Prayerwimp said:
I have installed the "minimal adb and fastboot" and HTC Sync manager.
This is what I came up with:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(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: 3774mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you for your time and assistance. Next step please.
Click to expand...
Click to collapse
There is a mismatch between your version-main and your cid/mid. The version-main (firmware version) is an old at&t version but your cid/mid are set to accept t-mobile firmware. That will be easy to fix but first what OS do you want on your phone? The latest official Sense rom (lollipop 5.0.2), latest GPE rom (lollipop 5.1) or latest custom rom (Nougat 7.1)?

alray said:
There is a mismatch between your version-main and your cid/mid. The version-main (firmware version) is an old at&t version but your cid/mid are set to accept t-mobile firmware. That will be easy to fix but first what OS do you want on your phone? The latest official Sense rom (lollipop 5.0.2), latest GPE rom (lollipop 5.1) or latest custom rom (Nougat 7.1)?
Click to expand...
Click to collapse
From what I understand it originally was an AT&T phone that was switched to T-Mobile. As for which OS. I am not picky so whichever is easiest and then I guess the newest.
Thanks again.

Prayerwimp said:
From what I understand it originally was an AT&T phone that was switched to T-Mobile. As for which OS. I am not picky so whichever is easiest and then I guess the newest.
Thanks again.
Click to expand...
Click to collapse
Is there a custom recovery installed on your phone, like TWRP or CWM?
Boot your phone in bootloader mode then select "recovery" and hit the power button. If you don't see "recovery'' that's because you"re booted in "fastboot" menu, in this case select "bootloader" and you should see the "recovery" option.
Your phone will reboot in recovery mode, just need to know what recovery is installed for now. If your phone is running stock recovery you will see an exclamation mark in a red triangle, otherwise you'll see TWRP splash screen or CWM menu. If booting to TWRP or CWM please report back what version number it is.

alray said:
Is there a custom recovery installed on your phone, like TWRP or CWM?
Boot your phone in bootloader mode then select "recovery" and hit the power button. If you don't see "recovery'' that's because you"re booted in "fastboot" menu, in this case select "bootloader" and you should see the "recovery" option.
Your phone will reboot in recovery mode, just need to know what recovery is installed for now. If your phone is running stock recovery you will see an exclamation mark in a red triangle, otherwise you'll see TWRP splash screen or CWM menu. If booting to TWRP or CWM please report back what version number it is.
Click to expand...
Click to collapse
Chose recovery from boot screen. ClockworkMod Recovery v6.0.4.3 is at top of screen with a list of options:
- Reboot system now
- Install zip
- Wipe data/factory reset
- Wipe cache partition
- Backup and restore
- Mounts and storage
- Advanced
Thanks.

Prayerwimp said:
Chose recovery from boot screen. ClockworkMod Recovery v6.0.4.3 is at top of screen with a list of options:
- Reboot system now
- Install zip
- Wipe data/factory reset
- Wipe cache partition
- Backup and restore
- Mounts and storage
- Advanced
Thanks.
Click to expand...
Click to collapse
Good, we can fix your CID and MID first. You can use this guide to write supercid to your phone. WIth your phone in bootloader mode (in the fastboot menu) Start the minimal adb and fastboot terminal then follow the guide from step 9 - 12.
Then to change your MID reboot in recovery and type:
Code:
adb shell
and
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
Better to copy/paste that one...
Then reboot in bootloader mode again and confirm your mid is now PN0710000 (your can use the "fastboot getvar all" command)
Download this firmware and save it in the same location where minimal adb and fastboot.exe is installed on your computer
WIth your phone in bootloader mode (fastboot menu) type (the command is case sensitive btw):
Code:
fastboot oem rebootRUU
Your phone will reboot in RUU mode, you should see a black screen with a silver HTC logo
type:
Code:
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
Should take a few seconds before saying : FAILED (remote: 90 hboot pre-update! please flush image again immediately).
So do the same command again:
Code:
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
The second time, it should take a few minutes and you'll see "okay" at the end, then proceed with
Code:
fastboot reboot-bootloader
Back in bootloader mode again, confirm your version-main is now 7.19.401.2 (use "fastboot getvar all")
If everything went fine you can proceed to the final steps:
Download this RUU and this version of htc_fastboot.exe and save both files in the same folder where you already have minimal adb and fastboot.exe.
reboot again in ruu mode:
Code:
fastboot oem rebootRUU
and once there type:
Code:
htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
The flash should take a while and your phone will reboot once during the process. Once 100% done you can reboot the phone and it will boot in the OS (android 5.0.2 with HTC Sense)

alray said:
Good, we can fix your CID and MID first. You can use this guide to write supercid to your phone. WIth your phone in bootloader mode (in the fastboot menu) Start the minimal adb and fastboot terminal then follow the guide from step 9 - 12.
Then to change your MID reboot in recovery and type:
Code:
adb shell
and
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
Better to copy/paste that one...
Then reboot in bootloader mode again and confirm your mid is now PN0710000 (your can use the "fastboot getvar all" command)
Download this firmware and save it in the same location where minimal adb and fastboot.exe is installed on your computer
WIth your phone in bootloader mode (fastboot menu) type (the command is case sensitive btw):
Code:
fastboot oem rebootRUU
Your phone will reboot in RUU mode, you should see a black screen with a silver HTC logo
type:
Code:
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
Should take a few seconds before saying : FAILED (remote: 90 hboot pre-update! please flush image again immediately).
So do the same command again:
Code:
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
The second time, it should take a few minutes and you'll see "okay" at the end, then proceed with
Code:
fastboot reboot-bootloader
Back in bootloader mode again, confirm your version-main is now 7.19.401.2 (use "fastboot getvar all")
If everything went fine you can proceed to the final steps:
Download this RUU and this version of htc_fastboot.exe and save both files in the same folder where you already have minimal adb and fastboot.exe.
reboot again in ruu mode:
Code:
fastboot oem rebootRUU
and once there type:
Code:
htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
The flash should take a while and your phone will reboot once during the process. Once 100% done you can reboot the phone and it will boot in the OS (android 5.0.2 with HTC Sense)
Click to expand...
Click to collapse
The first step changing the CID worked. But when I tried to change the MID I had a problem. When you say boot into recovery do you mean go into recovery from the hdboot screen? The only way adb can find the phone is from the fastboot screen. here is what I get when in recovery :
adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
And when in Fastboot:
adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
Also, When I boot into fastboot the phone is identified as Android in devices and the HTC Sync Manager finds it. In hdboot or recovery it is identified as "one" and HTC Sync Manager cannot find it.
Sorry for all the difficulties.
Thank you.

Prayerwimp said:
The first step changing the CID worked. But when I tried to change the MID I had a problem. When you say boot into recovery do you mean go into recovery from the hdboot screen? The only way adb can find the phone is from the fastboot screen. here is what I get when in recovery :
adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
And when in Fastboot:
adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
Also, When I boot into fastboot the phone is identified as Android in devices and the HTC Sync Manager finds it. In hdboot or recovery it is identified as "one" and HTC Sync Manager cannot find it.
Sorry for all the difficulties.
Thank you.
Click to expand...
Click to collapse
try with twrp recovery instead, you can download it from here and as usual, save it in the same folder where you have your minimal adb/fastboot.exe installed
to flash twrp, boot in bootloader mode (fastboot menu)
Code:
fastboot flash recovery twrp-3.2.1-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
then select "recovery" and wait for twrp to boot (you'll see a twrp splash screen, then the twrp main menu. With your phone in twrp main menu, you should be able to use the adb commands.

I cannot figure out where ADB is located. The program I have installed allows me to use it from anywhere. Here is what shows up when I open the powershell. Isn't there a way to open the shell in any folder?
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS C:\WINDOWS\system32>
Thank you.

alray said:
try with twrp recovery instead, you can download it from here and as usual, save it in the same folder where you have your minimal adb/fastboot.exe installed
to flash twrp, boot in bootloader mode (fastboot menu)
Code:
fastboot flash recovery twrp-3.2.1-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
then select "recovery" and wait for twrp to boot (you'll see a twrp splash screen, then the twrp main menu. With your phone in twrp main menu, you should be able to use the adb commands.
Click to expand...
Click to collapse
I figured out how to start shell in a folder and was able to get TWRP to install. This is what I got.
target reported max download size of 1514139648 bytes
sending 'recovery' (12756 KB)...
OKAY [ 1.526s]
writing 'recovery'...
OKAY [ 0.870s]
finished. total time: 2.400s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.059s]
finished. total time: 0.061s
rebooting into bootloader...
OKAY [ 0.039s]
finished. total time: 0.039s
Now with TWRP loaded I get a message about a partition. DoI want to have a parition??
Unmodified system partition
Keep system read only?
TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root you device.
installing zips or performing adb operations may still modify the system partition.
Now when I run code: "adb shell" this is what shows:
adb server is out of date. killing...
* daemon started successfully *
~ # 
And it just stays there.

Prayerwimp said:
I figured out how to start shell in a folder and was able to get TWRP to install. This is what I got.
target reported max download size of 1514139648 bytes
sending 'recovery' (12756 KB)...
OKAY [ 1.526s]
writing 'recovery'...
OKAY [ 0.870s]
finished. total time: 2.400s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.059s]
finished. total time: 0.061s
rebooting into bootloader...
OKAY [ 0.039s]
finished. total time: 0.039s
Now with TWRP loaded I get a message about a partition. DoI want to have a parition??
Unmodified system partition
Keep system read only?
TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root you device.
installing zips or performing adb operations may still modify the system partition.
Click to expand...
Click to collapse
You can swipe the slider to "allow system modification"
Now when I run code: "adb shell" this is what shows:
adb server is out of date. killing...
* daemon started successfully *
~ # 
And it just stays there.
Click to expand...
Click to collapse
That is exactly what you want, you can now type your commands.
~ #  is the prompt telling you that you are root user from adb shell.

Is this correct?
PS C:\Users\praye\Desktop\HTC One M7> .\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36YW903409
(bootloader) imei: 354439050980004
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4129mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.105s
You can swipe the slider to "allow system modification"
I skipped this because I was not sure. Is there a way to go back and do this???
So I made it all the way to the last step and this is what I get:
PS C:\Users\praye\Desktop\HTC One M7> htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
htc_fastboot : The term 'htc_fastboot' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 ...
+ ~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (htc_fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command htc_fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\htc_fastboot". See "get-help about_Command_Precedence" for more details.
I followed the suggestion and this is the result:
PS C:\Users\praye\Desktop\HTC One M7> .\htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.40
1.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
htc_fastboot v3.0.9.2 (2015-05-29)
error: cannot load 'RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe'
htc_fastboot finished. total time: 0.355s
The phone has been powered down over the weekend.
Thanks for all the help.

Prayerwimp said:
Is this correct?
PS C:\Users\praye\Desktop\HTC One M7> .\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36YW903409
(bootloader) imei: 354439050980004
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4129mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.105s
You can swipe the slider to "allow system modification"
I skipped this because I was not sure. Is there a way to go back and do this???
So I made it all the way to the last step and this is what I get:
PS C:\Users\praye\Desktop\HTC One M7> htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
htc_fastboot : The term 'htc_fastboot' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 ...
+ ~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (htc_fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command htc_fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\htc_fastboot". See "get-help about_Command_Precedence" for more details.
I followed the suggestion and this is the result:
PS C:\Users\praye\Desktop\HTC One M7> .\htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.40
1.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
htc_fastboot v3.0.9.2 (2015-05-29)
error: cannot load 'RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe'
htc_fastboot finished. total time: 0.355s
The phone has been powered down over the weekend.
Thanks for all the help.
Click to expand...
Click to collapse
Will be easier to use the old terminal window (cmd.exe) instead of the powershell. You can call cmd.exe directly from the powershell by typing cmd.exe

alray said:
Will be easier to use the old terminal window (cmd.exe) instead of the powershell. You can call cmd.exe directly from the powershell by typing cmd.exe
Click to expand...
Click to collapse
PS C:\Users\praye\Desktop\HTC One M7> CMD.exe
Microsoft Windows [Version 10.0.16299.192]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Users\praye\Desktop\HTC One M7>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.094s]
finished. total time: 0.095s
C:\Users\praye\Desktop\HTC One M7>htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
htc_fastboot v3.0.9.2 (2015-05-29)
error: cannot load 'RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe'
htc_fastboot finished. total time: 0.302s
Here is the result. Not sure what I am doing wrong.
Thank you.