Database Develop

Stuck in Bootloader

I got this used HTC one. I had google edition ROM on it when I got it. Then I flashed AR HD Rom on it. Everything was going fine till I decided to flash the latest firmware since I wanted to go to ARHD 30 and everyone seems to recommend to flash the new firmware.
I was going thru the normal steps and saw that I need to relock my device. I did this:
C:\Program Files\Android\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.110s
After this I noticed that I had relocked written in fastboot mode even though it said failed. So tried the next step:
C:\Program Files\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.040s
C:\Program Files\Android\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (28338 KB)...
OKAY [ 2.566s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.843s
And any step that I try it fails. The most unfortunate thing is I can only boot in fastboot & bootloader mode. I can't go in recovery neither can I boot normally. These are my phone details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(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: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.057s
I looked up online tried flashing recovery but now any step that I try to do in fastboot fails with following message:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
I saw in some places people mentioned to use RUU. Not sure what it is but if some one can point me to a correct RUU or let me know any other steps it would be greatly appreciated. My phone is almost bricked now since i can't go past fastboot/bootloader.

awaitforitb said:
(bootloader) version-bootloader: 1.44.0000
Click to expand...
Click to collapse
You have no idea how lucky you are. Before you do anything, get S-OFF using revone. Just go into CWM (or re-flash recovery) so you can use adb. Once you have s-off, follow my guide :
This guide requires S-OFF​Important
*** If there are files you need to keep, you can always use adb pull to get them out before hand (let's say a nandroid backup or something important)
This guide assumes you have knowledge about how adb and fastboot command work and that your HTC drivers are up to date.
I am in NO WAY responsible for any possible damage that may happen to your phone, I am only trying to help
Start your phone in bootloader by typing
Code:
adb reboot bootloader
or by other means.
Select "Fastboot" so that it appears in red instead of HBOOT
On your computer, make sure fastboot sees your device, then type
Code:
fastboot erase cache
Type
Code:
fastboot erase cache
Type
Code:
fastboot erase userdata
Type
Code:
fastboot erase system
Type
Code:
fastboot erase linux
Type
Code:
fastboot erase recovery
Type
Code:
fastboot erase cache
Type
Code:
fastboot reboot-bootloader
Download the new firmware.zip
Type
Code:
fastboot oem rebootRUU
Once it's rebooted on a silver HTC logo, type :
Code:
fastboot flash zip [pathonyourcomputer/firmware.zip]
Wait until it is done on your computer. The green line on the phone will never reach the end.
Type
Code:
fastboot reboot-bootloader
Reflash your recovery (I recommend CWM). Might as well play it safe.
Code:
fastboot flash recovery [pathonyourcomputer/recovery.img]
Reboot into recovery (select the option in fastboot)
Wipe data/factory reset (you will loose everythng)
Select "Wipe Cache partition"
Select "Advanced -> Wipe Dalvik Cache"
Now you have 2 options :
Push (Preferred)
While in recovery, type
Code:
adb push [path/rom.zip] /sdcard/rom.zip
Select "Install zip"
Select "Choose zip from sdcard"
Voila ! You should be good to go !
Sideload (If you can't push for some reason)
Select "Install zip"
Select "Install zip from sideload"
Type
Code:
adb sideload [path/rom.zip]
Voila ! You should be good to go !

attanasi0 said:
You have no idea how lucky you are. Before you do anything, get S-OFF using revone. Just go into CWM (or re-flash recovery) so you can use adb. Once you have s-off, follow my guide :
Click to expand...
Click to collapse
@awaitforitb:
I agree with the S-Off part, just check the date of your bootloader it has to be pre June 2013. Also, in order for revone to work you need a functioning ROM (4.1.2... 4.3 will NOT work). Do you have one functioning device, or are you "stuck in bootloader" as the title says.
You could run the RUU found on androidruu http://www.androidruu.com/?developer=M7, I believe yours would be http://www.androidruu.com/getdownlo....20_10.40.1150.04_release_326691_signed_2.exe
That's an exe you run directly from your PC, and it will walk you through the steps, this will wipe your phone completely! and restore everything back to 100% stock.
After that you should get S-Off, and then proceed to whatever your end goal is.
@attanasi0 just a couple of questions, why do you recommend all the "fastboot erase userdata/linux/system/recovery" ?
Also, please remember that when using "fastboot flash zip <name of firmware>.zip", in most cases, you have to do it twice after each other, the first will push the zip and say "failed, flush image again" (or something along those lines), the second flash will actually start the installation and should report success.
I usually use firmwares from @vomer's guide: http://forum.xda-developers.com/showthread.php?t=2365506 as they have the dzdata files removed, as well as the stock boot.img and recovery.img removed.

nkk71 said:
@attanasi0 just a couple of questions, why do you recommend all the "fastboot erase userdata/linux/system/recovery" ?
Also, please remember that when using "fastboot flash zip <name of firmware>.zip", in most cases, you have to do it twice after each other, the first will push the zip and say "failed, flush image again" (or something along those lines), the second flash will actually start the installation and should report success.
I usually use firmwares from @vomer's guide: http://forum.xda-developers.com/showthread.php?t=2365506 as they have the dzdata files removed, as well as the stock boot.img and recovery.img removed.
Click to expand...
Click to collapse
You're about pushing the zip at first, forgot about that.
I honestly don't know why I recommend that. I guess it's to make sure the phone is a clean slate and no conflict will be created TL;DR : Paranoia

[Q] Always cannot read android-info.txt on AT&T HTC One

The phone is used to reboot every 2 mins. Then I looked the articles here and try to fix it. But right now, I cannot flash the rom.zip to the phone.
Following are the steps I did:
1. s-off on the phone
2. installed ClockworkMod Recovery 6.0.5.1.
3. installed minimal_adb_fastboot
4. download superuser.zip and run CWM to install the file
5. downlaod the ElementX-m7-18.0-Sense.zip for Sense 6 Android 4.4.3 and run CWM to install the file
6. download the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2 rom
7. try to flash the rom after rebootRUU but always tell me cannot read android_info.txt
My current phone info:
ClockworkMod Recovery 6.0.5.1,
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -----------------
(bootloader) imei: ----------------------
(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: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Other info:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-hoot 2047MB
Sep 10 2013.01:32:23.0
:crying::crying::crying:I don't know where i did wrong. Really need helps on it.:highfive:

Michael Xie said:
The phone is used to reboot every 2 mins. Then I looked the articles here and try to fix it. But right now, I cannot flash the rom.zip to the phone.
Following are the steps I did:
1. s-off on the phone
2. installed ClockworkMod Recovery 6.0.5.1.
3. installed minimal_adb_fastboot
4. download superuser.zip and run CWM to install the file
5. downlaod the ElementX-m7-18.0-Sense.zip for Sense 6 Android 4.4.3 and run CWM to install the file
6. download the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2 rom
7. try to flash the rom after rebootRUU but always tell me cannot read android_info.txt
My current phone info:
ClockworkMod Recovery 6.0.5.1,
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -----------------
(bootloader) imei: ----------------------
(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: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Other info:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-hoot 2047MB
Sep 10 2013.01:32:23.0
:crying::crying::crying:I don't know where i did wrong. Really need helps on it.:highfive:
Click to expand...
Click to collapse
Well according to your getvar and the info shown in your bootloader your device is not s-off. Your still s-on so that ruu won't work for you anyway.
So what ever method you used to s-off apparently didn't work. And you need s-off to use that RUU.
However this RUU should work for you with s-on but you will need to relock your bootloader. And make sure you check the md5 of your download with this tool from www.winmd5.com
Correct md5 for this ruu is
Code:
5f121d72b8fa3f6f1704588467752605
http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Boot your device to the bootloader and connect fastboot usb. In the command window type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Make sure fastboot usb is connected then launch the ruu.exe on your pc.

Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".

Michael Xie said:
Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".
Click to expand...
Click to collapse
This is a visual c++ error I believe. Install this on your pc and try the ruu again http://www.microsoft.com/en-gb/download/details.aspx?id=29
---------- Post added at 06:58 AM ---------- Previous post was at 06:49 AM ----------
Alternatively you could use this RUU.zip
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
The procedure for flashing is a little more complex though.
Download the ruu.zip and put it in your fastboot folder and rename it to ruu.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
you can skip this part if your already locked.
Code:
fastboot oem rebootRUU
--- case sensitive ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the ruu.
Code:
fastboot flash zip ruu.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip ruu.zip
The second flash will take a little longer and this time it will flash the full ruu. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader

I just installed and tried again. but it says some problem cause the application is not working correct. the htc_fastboot.exe is still not working. Do i need to reboot my system after installation?
-----------------------------------------------------------
I am trying the zip file. Thank you so much.

Michael Xie said:
I just installed and tried again. but it says some problem cause the application is not working correct. the htc_fastboot.exe is still not working. Do i need to reboot my system after installation?
Click to expand...
Click to collapse
Rebooting wouldn't hurt :good:

I got this message three times during the flash:
target reported max download size of 1526722560 bytes
sending 'zip' (1158208 KB)...
OKAY [ 37.747s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 161.040s
Have to go sleep. Thanks

Michael Xie said:
I got this message three times during the flash:
target reported max download size of 1526722560 bytes
sending 'zip' (1158208 KB)...
OKAY [ 37.747s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 161.040s
Have to go sleep. Thanks
Click to expand...
Click to collapse
use the .exe ruu that danny linked above (post #2), you can't use the decrypted ruu.zip (from post #4) with s-on.
Decrypted ruu = not signed by htc private key
s-on = must check htc signature before flashing
s-on + decrypted ruu = signature verification fail.
so with s-on you can only use signed ruu same or higher version
s-off: you can use signed and decrypted ruu, same, higher or lower version.

Michael Xie said:
Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".
Click to expand...
Click to collapse
What version of Windows are you running on your pc?
Do you have HTC sync installed?
Is your SDK adb/fastboot up to date?
You can also try this ruu.exe http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/ , I'm not sure it will help with the fastboot error since I think that problem is pc side. But try it maybe the older installer will work with the c++ you installed previously. :good:

Michael Xie said:
Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".
Click to expand...
Click to collapse
if you have htc sync installed, uninstall it (but don't uninstall the drivers)

The one Danny201281 gives to me works!!!!!
However, the phone goes back to keep rebooting after I installed the rom.
Need big help here.

Michael Xie said:
The one Danny201281 gives to me works!!!!!
However, the phone goes back to keep rebooting after I installed the rom.
Need big help here.
Click to expand...
Click to collapse
do a factory reset from stock recovery
when you get in recovery from the bootloader push volume up and tap power to see the menu

After I entered the "recovery", I saw following:
Android system recovery <3e>
Volume up/down to move highlight:
Enter button to select:
reboot system now
apply from sd card
apply from phone storage
apply from cache
wipe data/factory reset
wipe cache partition
I didn't see the mean you give to me....
HTC One 32 GB AT&T
Rolled Back to Android 4.3 Sense 5.5 / ARHD 53
Is there anyway for me to install brand everything if I unlock with s-on? Or is there anyway for me to change from s-on to s-off? I used the htcdev to unlock but it doesn't change the "s-on" to "s-off"..

I did "adb devices", it shows:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
This is correct or not?

Michael Xie said:
Just tried, still don't work. the phone is rebooting during the green "htc" screen.
Is there anyway for me to install brand everything if I unlock with s-on? Or is there anyway for me to change from s-on to s-off? I used the htcdev to unlock but it doesn't change the "s-on" to "s-off"..
Click to expand...
Click to collapse
You need the phone to boot to a Rom to gain s-off.
If these reboots continue after flashing the ruu was successful there's a good chance your problem is hardware related.
Best option now it to unlock the bootloader and flash a Custom Recovery and Rom. I would also recommend doing a data format before flashing the new Rom to ensure your partitions are free from corruption.

So I just wipe cache partition or wipe data/factory reset?

Michael Xie said:
I did "adb devices", it shows:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
This is correct or not?
Click to expand...
Click to collapse
You should see your phone serial number here. But this will only work if booted into a custom recovery like TWRP.
Michael Xie said:
So I just wipe cache partition or wipe data/factory reset?
Click to expand...
Click to collapse
If you have Stock recovery it would be best to factory reset with that first if you haven't already. Other wise just flash a Custom recovery

I did "fastboot -w" and got following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
Creating filesystem with parameters:
Size: 27917287424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6815744
Block groups: 208
Reserved block group size: 1024
Created filesystem with 11/1703936 inodes and 150980/6815744 blocks
target reported max download size of 1526722560 bytes
Creating filesystem with parameters:
Size: 671084544
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2559
Label:
Blocks: 163839
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/40960 inodes and 5255/163839 blocks
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.003s
Is there something wrong here...

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.