ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.
Jamesdbritt said:
ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.
Click to expand...
Click to collapse
if you can get to bootloader you're not bricked.
don't fiddle with your phone - just leave it like it is.
someone here who knows way more about this stuff than I do will be able to tell you what you need to do.
Jamesdbritt said:
ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.
Click to expand...
Click to collapse
get into fastboot mode and type "fastboot getvar all" in Command Prompt without the inverted commas. Post the output AND REMOVE IMEI AND SERIAL NO.
This is necessary to obtain a little more info abt the phone's current condition
raghav kapur said:
get into fastboot mode and type "fastboot getvar all" in Command Prompt without the inverted commas. Post the output AND REMOVE IMEI AND SERIAL NO.
This is necessary to obtain a little more info abt the phone's current condition
Click to expand...
Click to collapse
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28
Jamesdbritt said:
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28
Click to expand...
Click to collapse
Download and install latest android sdk http://developer.android.com/sdk/index.html
download in install latest htc sync (for drivers installation) then uninstall it, the drivers still be installed. http://www.htc.com/www/software/htc-sync-manager/
go to the folder you installed the android sdk then ---> sdk/platform-tools. Adb.exe and fastboot.exe should be in this folder. Always work in this folder (where adb and fastboot.exe are).
boot your phone in bootloader mode, select fastboot and connect usb cable to computer
Right click on a blank space in the folder where fastboot/adb are then select ''open a cmd prompt here''
in the command prompt type
Code:
fastboot getvar all
and copy paste output here MINUS IMEI AND SN
and please tell us what operating system are you using on your ocmputer? windows 7, 8.0 or 8.1?
How do I get into fastboot mode?
Jamesdbritt said:
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28
Click to expand...
Click to collapse
and how did you messed your phone?
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
Jamesdbritt said:
How do I get into fastboot mode?
Click to expand...
Click to collapse
when you are in bootloarder mode, select ''fastboot''. use vol up and down to navigate then power button to select.
{
"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"
}
When in fastboot mode you'll have a screen similar to this with fastboot highlighted in red:
When I right click there is no cmd option
Jamesdbritt said:
When I right click there is no cmd option
Click to expand...
Click to collapse
sry my bad
hold left SHIFT + right click
Ok found cmd typed above and it came with a list of commands
Update
Flashall
Etc..
Jamesdbritt said:
Ok found cmd typed above and it came with a list of commands
Update
Flashall
Etc..
Click to expand...
Click to collapse
please can you make a screenshot of your cmd prompt and post it here? I want to see the command you typed and the ouput
commands:
update <filename> reflash device from
flashall flash boot + recove
flash <partition> [ <filename> ] write a file to a f
erase <partition> erase a flash parti
format <partition> format a flash part
getvar <variable> display a bootloade
boot <kernel> [ <ramdisk> ] download and boot k
flash:raw boot <kernel> [ <ramdisk> ] create bootimage an
devices list all connected
continue continue with autob
reboot reboot device norma
reboot-bootloader reboot device into
help show this help mess
options:
-w erase userdata and
if supported by par
-u do not first erase
formatting
-s <specific device> specify device seri
or path to device p
-l with "devices", lis
-p <product> specify product nam
-c <cmdline> override kernel com
-i <vendor id> specify a custom US
-b <base_addr> specify a custom ke
default: 0x10000000
-n <page size> specify the nand pa
2048
-S <size>[K|M|G] automatically spars
an
size. 0 to disable
Jamesdbritt said:
commands:
update <filename> reflash device from
flashall flash boot + recove
flash <partition> [ <filename> ] write a file to a f
erase <partition> erase a flash parti
format <partition> format a flash part
getvar <variable> display a bootloade
boot <kernel> [ <ramdisk> ] download and boot k
flash:raw boot <kernel> [ <ramdisk> ] create bootimage an
devices list all connected
continue continue with autob
reboot reboot device norma
reboot-bootloader reboot device into
help show this help mess
options:
-w erase userdata and
if supported by par
-u do not first erase
formatting
-s <specific device> specify device seri
or path to device p
-l with "devices", lis
-p <product> specify product nam
-c <cmdline> override kernel com
-i <vendor id> specify a custom US
-b <base_addr> specify a custom ke
default: 0x10000000
-n <page size> specify the nand pa
2048
-S <size>[K|M|G] automatically spars
an
size. 0 to disable
Click to expand...
Click to collapse
type this command:
Code:
fastboot devices
what is the output?
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>FASTBO
T GETVAR ALL
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater t
an
size. 0 to disable
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Jamesdbritt said:
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>FASTBO
T GETVAR ALL -------> 1 ''o'' is missing from fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater t
an
size. 0 to disable
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
fastboot is case sensitive don't use capitals letter unless specified
type
''fastboot getvar all'' NOT ''FASTBOT GETVAR ALL''
and there is a letter missing at fastboot
C:\SDK\ADT\sdk\platform-tools>fastboot devices
FA39DS900733 fastboot
C:\SDK\ADT\sdk\platform-tools>
Jamesdbritt said:
C:\SDK\ADT\sdk\platform-tools>fastboot devices
FA39DS900733 fastboot
C:\SDK\ADT\sdk\platform-tools>
Click to expand...
Click to collapse
ok so now type ''fastboot getvar all'' DON'T USE CAPITALS!
C:\SDK\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA39DS900733
(bootloader) imei: xxxxxx
(bootloader) meid: xxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3769mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
C:\SDK\ADT\sdk\platform-tools>
Jamesdbritt said:
C:\SDK\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei: xxxxxx
(bootloader) meid: xxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3769mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
C:\SDK\ADT\sdk\platform-tools>
Click to expand...
Click to collapse
ok so you want to go back to stock rom or you want to install a custom rom?
alray said:
ok so you want to go back to stock rom or you want to install a custom rom?
Click to expand...
Click to collapse
stock right now I know SuperSU is not installed if that means anything
I was having data connection problems before all this started
Related
Just a question, can anybody execute this on an XL with unlocked bootloader using HTCDev and tell me the output please?
Code:
fastboot oem h
cause I was wondering, if we can execute this to get S-OFF as the bootloader is unlocked so it may give us more permissions?:
Code:
fastboot oem writesecureflag 0
Just wondering if it asks for SMART_IO.CRD or not
Any idea guys?
About htc sensation xl s-off
hi there if you could write set on teminal app see what is writen ?
turkish0852 said:
hi there if you could write set on teminal app see what is writen ?
Click to expand...
Click to collapse
I don't understand what you mean, can you please say it in a clearer way?
thank you
about s-off sensation xl
sorry about that,there's that app called termanel emulater in the market,I was messing around with it, I wrote ( set ) & it showed lots of data, wich I asked what it realy ment if anything,my phone is HTC sensation xl with beats audio permanetly rooted ,bootloader unlocked, s-on,sorry for sbelling.
---------- Post added at 01:04 AM ---------- Previous post was at 12:53 AM ----------
hope it's something worth looking into,type ( set ) then enter,
turkish0852 said:
sorry about that,there's that app called termanel emulater in the market,I was messing around with it, I wrote ( set ) & it showed lots of data, wich I asked what it realy ment if anything,my phone is HTC sensation xl with beats audio permanetly rooted ,bootloader unlocked, s-on,sorry for sbelling.
---------- Post added at 01:04 AM ---------- Previous post was at 12:53 AM ----------
hope it's something worth looking into,type ( set ) then enter,
Click to expand...
Click to collapse
maybe this can help
Code:
ort PATH=/data/local/bin:$PATH
$ su
# set
ANDROID_ASSETS=/system/app
ANDROID_BOOTLOGO=1
ANDROID_DATA=/data
ANDROID_PROPERTY_WORKSPACE=9,65536
ANDROID_ROOT=/system
ANDROID_SOCKET_zygote=10
ASEC_MOUNTPOINT=/mnt/asec
BOOTCLASSPATH=/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/HTCDev.jar:/system/framework/HTCExtension.jar:/system/framework/com.htc.framework.jar:/system/framework/com.scalado.util.ScaladoUtil.jar:/system/framework/com.orange.authentication.simcard.jar:/system/framework/android.supl.jar:/system/framework/com.ecrio.sip.jar
EXTERNAL_STORAGE=/mnt/sdcard
IFS='
'
LD_LIBRARY_PATH=/vendor/lib:/system/lib
LOOP_MOUNTPOINT=/mnt/obb
OPTIND=1
PATH=/data/local/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
PS1='# '
PS2='> '
PS4='+ '
TERM=screen
#
turkish0852 said:
sorry about that,there's that app called termanel emulater in the market,I was messing around with it, I wrote ( set ) & it showed lots of data, wich I asked what it realy ment if anything,my phone is HTC sensation xl with beats audio permanetly rooted ,bootloader unlocked, s-on,sorry for sbelling.
---------- Post added at 01:04 AM ---------- Previous post was at 12:53 AM ----------
hope it's something worth looking into,type ( set ) then enter,
Click to expand...
Click to collapse
nicky1980 said:
maybe this can help
Code:
ort PATH=/data/local/bin:$PATH
$ su
# set
ANDROID_ASSETS=/system/app
ANDROID_BOOTLOGO=1
ANDROID_DATA=/data
ANDROID_PROPERTY_WORKSPACE=9,65536
ANDROID_ROOT=/system
ANDROID_SOCKET_zygote=10
ASEC_MOUNTPOINT=/mnt/asec
BOOTCLASSPATH=/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/HTCDev.jar:/system/framework/HTCExtension.jar:/system/framework/com.htc.framework.jar:/system/framework/com.scalado.util.ScaladoUtil.jar:/system/framework/com.orange.authentication.simcard.jar:/system/framework/android.supl.jar:/system/framework/com.ecrio.sip.jar
EXTERNAL_STORAGE=/mnt/sdcard
IFS='
'
LD_LIBRARY_PATH=/vendor/lib:/system/lib
LOOP_MOUNTPOINT=/mnt/obb
OPTIND=1
PATH=/data/local/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
PS1='# '
PS2='> '
PS4='+ '
TERM=screen
#
Click to expand...
Click to collapse
thanks a lot guys! but unfortunately that's nt what I needed
I wanted to know if executing the command in the first post from your SDK tools will get you S-OFF or not with unlocked bootloader!
bootloader and s-off
hi there again,i exacuted those commands in the first posts the outcome is as follows;
fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloadre) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
fastboot oem writesecureflag 0
...
(bootloader) [ERR] Command error !!!
OKAY [ -0.000s]
finished. total time: -0.000s
hope this helps..
bootloader s-off
so any more idea's there,did that help in anyway?
turkish0852 said:
so any more idea's there,did that help in anyway?
Click to expand...
Click to collapse
I'm thinking of something, I dunno
turkish0852 said:
hi there again,i exacuted those commands in the first posts the outcome is as follows;
fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloadre) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
fastboot oem writesecureflag 0
...
(bootloader) [ERR] Command error !!!
OKAY [ -0.000s]
finished. total time: -0.000s
hope this helps..
Click to expand...
Click to collapse
thanks a lot, HTC has limited the oem commands on their bootloader :/
can you try this please?
fastboot oem rebootRUU
fastboot oem h
fastboot oem writesecureflag 0
to restart your phone:
fastboot reboot
and copy and paste me the output, thank you
C:\Users\Turkish>fastboot oem rebootRUU
...
(bootloader) erase sector 163328 ~ 163839 (512)
OKAY [ 0.484s]
finished. total time: 0.484s
C:\Users\Turkish>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Turkish>fastboot writesecureflag 0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Turkish>fastboot reboot
rebooting...
finished. total time: 0.312s
hope this helps,if anything else please let me know...
turkish0852 said:
C:\Users\Turkish>fastboot oem rebootRUU
...
(bootloader) erase sector 163328 ~ 163839 (512)
OKAY [ 0.484s]
finished. total time: 0.484s
C:\Users\Turkish>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Turkish>fastboot writesecureflag 0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Turkish>fastboot reboot
rebooting...
finished. total time: 0.312s
hope this helps,if anything else please let me know...
Click to expand...
Click to collapse
Thank You!
Seems like there is no real way of gaining S-OFF using oem..
I'll get an XL in several days and will see if I can do anything (but I don't really think I'll be able to anyway)!
We'll need to find a signed Engineering hboot that can be flashed to gain S-OFF after that!
Doesn't seem fair from HTC anyway.. They should unlock and S-OFF too in their unlocking process..
it was supposed to be "fastboot oem writesecureflag 0" I wrote it wrong, but anyway, as writesecureflag isn't accessible using oem, so it's useless to try it.
If anybody has any other idea, please share
bootloader and s-off
i exacuted the wright command again "fastboot oem secuerflag 0" but it gave me that same error "bootloader err Command error !!! "
But when i exacuted command " fastboot oem rebootRUU " the sensation xl screen whent black with black and white HTC letters in the midle of the screen,haven't seen that before...
I have XL with bootloader S-Off....tell me please, what I can do, to let you see, what the difference is
bootloader and s-off
icecream 4.0.1 has just been realeased for the sensation xe 1.0 beta version,i'd like to see this rom on the xl,iv had devices with bootloader s-off its bloody fantastic ,all htc's should come with bootloader s-off its a shame,i sapouse it's a waiting game,im shore great minds a working on it, I don't know if the sensation xl came with bootloader s-off in Australia......
jammysunny said:
I have XL with bootloader S-Off....tell me please, what I can do, to let you see, what the difference is
Click to expand...
Click to collapse
Ship s-off or Eng s-off?
ship s-off.....
turkish0852 said:
i exacuted the wright command again "fastboot oem secuerflag 0" but it gave me that same error "bootloader err Command error !!! "
But when i exacuted command " fastboot oem rebootRUU " the sensation xl screen whent black with black and white HTC letters in the midle of the screen,haven't seen that before...
Click to expand...
Click to collapse
yea, it wont work I know!
Its totally normal abt the rebootRUU thing, it just puts the phone in a state that accepts the flashing of any signed (or unsigned I think) images and many other things we may not know! Haha
jammysunny said:
ship s-off.....
Click to expand...
Click to collapse
interesting! may I ask how did you get it?
Would be good to acheive s-off but unlocked bootloader isnt half bad. We have permanent root and at least one custom rom so guess things will get up to speed as more people get the device. Alpha rev should do their thing soon so we can get full control over this device
Sent from my EPAD using xda premium
I got it with it....so, where you can see the difference between a normal and a ship s-offed Bootloader??
tapatraced with Sensation XL
pull the battery and then boot into hboot.Volume down and power.
eng hboot with S-off is hboot version 1.25.2003.
i started, this in the dev section, to have a CLEAN THREAD, with ONLY RELEVANT info.
if mod gives me permission i will clean this thread several times each day (if someone posts nonsense)
FOR DEVS ONLY! theres alot of other threads about this for Q&A etc..
thanks to orb3000 for making it a stickie..
reserved for later
What we got so far:
fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloadre) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
fastboot oem writesecureflag 0
...
(bootloader) [ERR] Command error !!!
OKAY [ -0.000s]
finished. total time: -0.000s
Click to expand...
Click to collapse
C:\Users\Turkish>fastboot oem rebootRUU
...
(bootloader) erase sector 163328 ~ 163839 (512)
OKAY [ 0.484s]
finished. total time: 0.484s
C:\Users\Turkish>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Turkish>fastboot writesecureflag 0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Turkish>fastboot reboot
rebooting...
finished. total time: 0.312s
Click to expand...
Click to collapse
We have tested to do these commands on the s-offed device of jammysunny.
cd/
cd SDK
cd platform-tools
adb devices
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
This worked successfully and we got an hboot.img file of his Device on the SD.
On the next step i tried to install his s-off hboot.img to my s-on device with the following commands:
cd/
cd SDK
cd platform-tools
adb devices
adb shell
su
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
This worked successfully too, but my bootloader is the same as before. Its s-on
Click to expand...
Click to collapse
hboot is useless from S-off device, as our bootloaders are unlocked.
What needs to be done is: get rid of Nand write protection, so we can flash radio's
Click to expand...
Click to collapse
Stickied, thanks!
waiting boot.img s-off
Im pretty sure s-off invokves the security flag on hboot not the boot.img
Sent from my HTC Sensation XL with Beats Audio X315b using XDA
Hi booyaga,
where I can find the s-off hboot.img file ?
thanks.
bye
Would love to see s-off lol
not sure if this can help...but my desire was s-off using alpharev
http://alpharev.nl/
maybe they can give some info ...?!?
with kind regards
It would be great to get alpharev on board. Seems everyone is neglecting our xl lol.
Sent from my GT-N7000 using xda premium
shingers5 said:
It would be great to get alpharev on board. Seems everyone is neglecting our xl lol.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
yep...if they dont want or do it (if we ask) maybe we can give a bit support...real s-off is nice...
Alex-V said:
yep...if they dont want or do it (if we ask) maybe we can give a bit support...real s-off is nice...
Click to expand...
Click to collapse
Willing to donate if needs be.
Sent from my GT-N7000 using xda premium
shingers5 said:
Willing to donate if needs be.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i also
with kind regards
Setting up a S-OFF donation thread to see who wants to donate and how much, might trigger there interest.
This is been seen on many dev treads, and can run up to few hundrerd euros
DutchDanny said:
Setting up a S-OFF donation thread to see who wants to donate and how much, might trigger there interest.
This is been seen on many dev treads, and can run up to few hundrerd euros
Click to expand...
Click to collapse
yea but not many devs even looking at xl and dont wanna line someones pocket who doesnt deliver!
shingers5 said:
yea but not many devs even looking at xl and dont wanna line someones pocket who doesnt deliver!
Click to expand...
Click to collapse
Guide them to the thread, and money will only be deliverd when s-off is deleverd
iḿ for that what DutchDanny says...and want give 20€ for s-off...who go with me...???!!!!!!!???!!
with kind regards
Alex-V said:
iḿ for that what DutchDanny says...and want give 20€ for s-off...who go with me...???!!!!!!!???!!
with kind regards
Click to expand...
Click to collapse
im in, with 10
DutchDanny said:
Guide them to the thread, and money will only be deliverd when s-off is deleverd
Click to expand...
Click to collapse
cool I shall donate soon as with 20 when needs be
Sent from my GT-N7000 using xda premium
30
Just because I want to learn more on this device and it will make life much easier!
Nice to See Some ideas, but Please make a bounty thread as its not really related to Development progress.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
So yesterday i bought myself a new HTC ONE phone from Egypt, the original owner used it for just 48 hours then sold it. When i received it i found the SuperUser installed and the OTA updates were not installing sin11ce the phone has been modified.
I followed a tutorial on XDA about getting back to stock rom and after flashing custom recovery and moving the stock rom to SD card i flashed it from recovery and it failed in the process.
Now the phone just boots into recovery, can anyone please post me a quick tutorial on getting the stock firmware back? i would really appreciate it.
Here is the info from the recovery:
*** UNLOCKED ***
M7_U PVT SHIP S-OFF RH
CID- 11111111
HBOOT- 1.54.0000
RADIO- 4A.21.3263.04
OpenDSP- v31.120.274.0617
OS- 2.24.401.9
eMMC-boot 2048MB
AUG 9 2013, 16:20:20.0
hello 1.....relock bootloader with htcdev from google
2.....download this ruu and run it from fastboot http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ sorry i fixed the link
3..change cid to 0_32 as bellow
now let's change CID so we can run the RUU.EXE for your ModelID: PN0712000
in bootloader/FASTBOOT USB, change your CID:
Code:
C:\ADB3>fastboot oem writecid CWS__0_32 <-- two underscores
...
(bootloader) Start Verify: 0
OKAY [ 0.023s]
finished. total time: 0.023s
C:\ADB3>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.041s
then take all the avalible updates
good guid here http://forum.xda-developers.com/showthread.php?t=2541082
bygrave said:
hello 1.....relock bootloader with htcdev from google
2.....download this ruu and run it from fastboot http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ sorry i fixed the link
3..change cid to 0_32 as bellow
now let's change CID so we can run the RUU.EXE for your ModelID: PN0712000
in bootloader/FASTBOOT USB, change your CID:
Code:
C:\ADB3>fastboot oem writecid CWS__0_32 <-- two underscores
...
(bootloader) Start Verify: 0
OKAY [ 0.023s]
finished. total time: 0.023s
C:\ADB3>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.041s
then take all the avalible updates
good guid here http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Thanks a lot for your reply. I am downloading the RUU now and till it finishes i have a quick question. Why should i change the CID to (0_32) instead of (11111111)?
Thanks again.
because you cant update with cid 11111111
once you have updated you can change it bk to 11111111 if you like:
---------- Post added at 05:25 PM ---------- Previous post was at 05:21 PM ----------
bygrave said:
because you cant update with cid 11111111
once you have updated you can change it bk to 11111111 if you like:
Click to expand...
Click to collapse
also write cid like this fastboot oem writecid HTC__032
capital HTC, two underscores, then 032
bygrave said:
because you cant update with cid 11111111
once you have updated you can change it bk to 11111111 if you like:
---------- Post added at 05:25 PM ---------- Previous post was at 05:21 PM ----------
also write cid like this fastboot oem writecid HTC__032
capital HTC, two underscores, then 032
Click to expand...
Click to collapse
Thanks a lot, now i get it.
One last question, should i change the CID before running the RUU or after running it?
yes it needs to be changed before u run the ruu. i always run the ruu from in fastboot mode
Sent from my HTC One using Tapatalk
let us know how u got on
Sent from my HTC One using Tapatalk
bygrave said:
let us know how u got on
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Unfortunately although i changed the CID but the RUU failed with an error that the RUU doesn't match my phone model number. :crying:
fastboot getvart all
and give us the results.
u did relock you're bootloader didn't u
Sent from my HTC One using Tapatalk
C:\mini-sdk>fastboot getvart all
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
DArkSm4sh said:
C:\mini-sdk>fastboot getvart all
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
Click to expand...
Click to collapse
fastboot getvar all
NOT getvarT
Remove your imei and serial number
sorry its fastboot getvar all
Sent from my HTC One using Tapatalk
bygrave said:
sorry its fastboot getvar all
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
The bootloader is still unlocked, should i relock it first?
C:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4324mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
yes needs to be locked for it to work
---------- Post added at 11:21 PM ---------- Previous post was at 11:14 PM ----------
just looking for a ruu u are in tawian is that write
did you get this sorted
So i looked at a bunch of threads but nothing was working out for me so i made a account. I have a ATT M7 running 4.4.2 and sense 6. I unlocked the boatloader, and i type in the commands to start the root process but it does nothing. At first it said cannot load, and somebody on here said that just means you've spelled it wrong. So then i noticed i had 2 different twrp files on my desktop. Deleted the old one and kept the newest one, after that, when i typed in the command, something else came up that i hadn't seen before
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
Click to expand...
Click to collapse
I have no idea what this means. My phones wiped bc of the boot loader but i have a back up, but i didn't want to wipe my phone for no reason.
If anybody has anything to contribute that'd be great. Im on mac os x 10.9 btw. Tried to root with PC also but it didn't work bc i didn't have drivers, installed some drivers but that didn't work either so i just gave up and went back to mac.
I did manually move the supersu file to the phone with the pc though
fastboot flash recovery twrp.img
Rename TWRP file to twrp.img put in pc adb folder
yatindroid said:
fastboot flash recovery twrp.img
Rename TWRP file to twrp.img put in pc adb folder
Click to expand...
Click to collapse
What do you mean put it in ADB folder? Thanks for the response though!!
I renamed it but I'm getting this "cannot load" message again. I read on here that all that means is that i spelled it wrong
stealth01 said:
What do you mean put it in ADB folder? Thanks for the response though!!
I renamed it but I'm getting this "cannot load" message again. I read on here that all that means is that i spelled it wrong
Click to expand...
Click to collapse
your recovery image must be in the same folder where you have adb.exe and fastboot.exe on your PC, otherwise, fastboot will not find the recovery image.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
alray said:
your recovery image must be in the same folder where you have adb.exe and fastboot.exe on your PC, otherwise, fastboot will not find the recovery image.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Mac osx ?
yatindroid said:
Mac osx ?
Click to expand...
Click to collapse
you are right, my bad. same principle apply. recovery image must be in the same folder you have adb and fastboot (not adb.exe) and you may have to use ./ before each command
Code:
./fastboot flash recovery name_of_recovery.img
./fastboot erase cache
./fastboot reboot-bootloader
alray said:
you are right, my bad. same principle apply. recovery image must be in the same folder you have adb and fastboot (not adb.exe) and you may have to use ./ before each command
Code:
./fastboot flash recovery name_of_recovery.img
./fastboot erase cache
./fastboot reboot-bootloader
Click to expand...
Click to collapse
Yeah that helped a bit bc i had like 3 twrp image files, i have one now and its still telling me it cannot load.
so frustrating! I messed up though because when i was first rooting it i was following like 2 guides, should've followed one. Its not bricked right?
stealth01 said:
Yeah that helped a bit bc i had like 3 twrp image files, i have one now and its still telling me it cannot load.
so frustrating! I messed up though because when i was first rooting it i was following like 2 guides, should've followed one. Its not bricked right?
Click to expand...
Click to collapse
what recovery image are you using and please post the output of "fastboot getvar all" (not the imei and sn)
alray said:
what recovery image are you using and please post the output of "fastboot getvar all" (not the imei and sn)
Click to expand...
Click to collapse
the latest TWRP
openrecovery-twrp-2.7.1.1-m7.img
Click to expand...
Click to collapse
The guide i watched told me to go the twrp site and find the latest one and use that. My phone was on 4.4 and sense 6 before i unlocked the boot loader.
and how do i get that to show? Do i select something on my phone?
nvm got what you were talking about
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
stealth01 said:
nvm got what you were talking about
Click to expand...
Click to collapse
I recommend you not use the latest twrp but to use ther version 2.6.3.3.
Now the screen you got (from your first post) is the help menu. It appear each time you enter an invalid command fastboot command.
so again make sure your recovery image (twrp 2.6.3.3) is in the same folder you have adb and fastboot on your mac.
with your phone in bootloader mode enter the following command:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you might have to add ./ before each command (depending how you have install your fastboot/adb on your mac)
now if it fail again, please post a screenshot of your terminal window and post a screenshot of your adb/fastboot folder.
alray said:
I recommend you not use the latest twrp but to use ther version 2.6.3.3.
Now the screen you got (from your first post) is the help menu. It appear each time you enter an invalid command fastboot command.
so again make sure your recovery image (twrp 2.6.3.3) is in the same folder you have adb and fastboot on your mac.
with your phone in bootloader mode enter the following command:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you might have to add ./ before each command (depending how you have install your fastboot/adb on your mac)
now if it fail again, please post a screenshot of your terminal window and post a screenshot of your adb/fastboot folder.
Click to expand...
Click to collapse
getting the same cannot load message. I even tried the older 2.6.3.2 version too
error: cannot load 'openrecovery-twrp-2.6.3.2-m7.img
Click to expand...
Click to collapse
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img
Click to expand...
Click to collapse
stealth01 said:
getting the same cannot load message. I even tried the older 2.6.3.2 version too
Click to expand...
Click to collapse
post the screenshot so we can see what you are doing wrong
{
"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"
}
alray said:
post the screenshot so we can see what you are doing wrong
Click to expand...
Click to collapse
my bad i was uploading them
i had like 3 android folders, but this is one that worked and would recognize the commands because this is the folder that installed my mac adb drivers. I downloaded like two other ones from tutorials but trashed them.
i also tried the ./ method, getting the same result
if anybody helps me out and it works I'll seriously donate $20. This has caused me a incredible amount of frustration and needs to get done
stealth01 said:
i had like 3 android folders, but this is one that worked and would recognize the commands because this is the folder that installed my mac adb drivers. I downloaded like two other ones from tutorials but trashed them.
Click to expand...
Click to collapse
have you changed directory (cd) in the terminal to the correct path where you have adb and fastboot? I see your adb, fastboot and recovery are in a folder named "android". you have censored a part of the terminal windows (probably the user name, so your name) so i can not see if your terminal is pointing the correct folder in your case "android". if this folder is on your dekstop then
Code:
cd Desktop/android [COLOR="Red"]or[/COLOR] cd /Users/<yourusername>/Desktop/android
fastboot flash recovery name_of_recovery
fastboot erase cache
fastboot reboot-bootloader
"can not load" error is because fastboot can't find the file
cause 1: file name miss-typed --->not your case
cause 2: file doesn't exist --->not your case
cause 3: not working from the correct path ---> might be your issue
cause 4: double file extension (more common on windows) i.e recovery.img.img (the second .img is hiden by the OS) --> might also be your issue, im not very familiar with mac so i dont know if the OS hide file extension for known file type like on windows
edit: looks like it also possible on a mac to have double file extension:
For one file
Select a file and choose File > Get Info or press Command (⌘)–I.
Click the triangle next to Name & Extension to expand the section and see the filename extension for the file.
To show or hide the filename extension, select or deselect “Hide extension.”
For all files
Choose Finder > Preferences, and then click Advanced.
Select or deselect “Show all filename extensions.”
Some filename extensions can’t be hidden. For example, images imported from a digital camera may continue to show the .jpg extension even after you deselect “Show all filename extensions.”
Click to expand...
Click to collapse
alray said:
have you changed directory (cd) in the terminal to the correct path where you have adb and fastboot? I see your adb, fastboot and recovery are in a folder named "android". you have censored a part of the terminal windows (probably the user name, so your name) so i can not see if your terminal is pointing the correct folder in your case "android". if this folder is on your dekstop then
Code:
cd Desktop/android [COLOR="Red"]or[/COLOR] cd /Users/<yourusername>/Desktop/android
fastboot flash recovery name_of_recovery
fastboot erase cache
fastboot reboot-bootloader
"can not load" error is because fastboot can't find the file
cause 1: file name miss-typed --->not your case
cause 2: file doesn't exist --->not your case
cause 3: not working from the correct path ---> might be your issue
cause 4: double file extension (more common on windows) i.e recovery.img.img (the second .img is hiden by the OS) --> might also be your issue, im not very familiar with mac so i dont know if the OS hide file extension for known file type like on windows
Click to expand...
Click to collapse
DUDE YOU FREAKING DID!!! I'm so happy finally!!
You'll be getting that $20 soon bro thank you so much!!!!
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 *
~ # [6n
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 *
~ # [6n
And it just stays there.
Click to expand...
Click to collapse
That is exactly what you want, you can now type your commands.
~ # [6n 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.