Database Develop

[Q] HTC Incredible S Stucked at Bootloader

http://forum.xda-developers.com/showpost.php?p=16684717&postcount=38
Guys.. I'm in deep Trouble..
I was taking back my phone to stock by following the above link.. I did s-off to So-on.. But stucked at boot loader with Security warning..
The message shows is
*****LOCKED*******
****Security warning ****
Hboot-2.00.000
Radio - 3822.10.08.28_M
I was using RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed
shipped Rom..
My mainver is Shows in CMD - INFOversion-main : 2.30.405.1
Please Help me Guys..!! I'm stucked..!!

Please Help guys..~~

If your mainver is 2.30.405.1 you will need this RUU http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199308_signed.exe
You are using Windows, I gues. Follow this steps to install ADB and fastboot. (Extract the files to C:\Android like it says)
The next part should not be hard, since you already did this I gues. Run the RUU and when it is de-compressed to not press anyting and copy the rom.zip folder from your TEMP folder to C:\Android
Connect your phone to your pc/laptop in fastboot usb mode.
Open up cmd on your pc and use the following commands
cd C:\Android
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
That should work, because the same thing happend to me

Did Everything what you said..? But still i gets the same error message..
C:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 0.144s]
finished. total time: 0.144s
C:\Android>fastboot oem rebootRUU
... OKAY [ 0.188s]
finished. total time: 0.188s
C:\Android>fastboot flash zip rom.zip
sending 'zip' (257756 KB)... OKAY [ 43.671s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 84.377s
Click to expand...
Click to collapse

use a gold card

I'm in Fasboot mode..!! I cant create goldcard from here..

kannanz said:
I'm in Fasboot mode..!! I cant create goldcard from here..
Click to expand...
Click to collapse
Post the output from
Code:
fastboot getvar all
minus imei and serial number.
Edit: you can use a gold card created in any android phone.

Here's it..
INFOversion: 0.5
INFOversion-bootloader: 2.00.0000
INFOversion-baseband: 3822.10.08.28_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.30.405.1
INFOserialno: ********
INFOimei: **************
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__038
INFObattery-status: good
INFObattery-voltage: 4158mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-af9874be
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.029s
Click to expand...
Click to collapse

kannanz said:
Here's it..
Click to expand...
Click to collapse
There's no ruu posted anywhere for India. Try to create gold card in a friends phone or try this link for info http://forum.xda-developers.com/showthread.php?t=731424 you might need to enter recovery mode for adb commands to work

Ahh..!! Atlast Created Goldcard with my friends Htc and Patched Using Goldcard tool.. Now Working fine..
Thanks a Lot..

I know your problem is fixed but did you read this thread? Hope it helped

kannanz said:
Ahh..!! Atlast Created Goldcard with my friends Htc and Patched Using Goldcard tool.. Now Working fine..
Thanks a Lot..
Click to expand...
Click to collapse
Hi I got the same error as u except that my hboot is 1.16.0000. I have a gold card but i still got the failed error like yours. Help?

Mooseolly2 said:
Hi I got the same error as u except that my hboot is 1.16.0000. I have a gold card but i still got the failed error like yours. Help?
Click to expand...
Click to collapse
What error code are yo getting when you try to flash a RUU?

[Q] Bricked HTC One M7 after attempting to restore to stock using YouTube video guide

I am looking for some help in getting my HTC One M7 back up and working.
I used the online Cyanogenmod installer on my at&t HTC One M7 and it worked for the most part including where it contacts the HTC site to place the phone in developer mode.
Unfortunately the radio was far weaker and was losing it's signal all the time. I tried a few nightly's in hopes it was a bug that would be addressed but the issue with radio strength continued. Then an alert about an update from Cyanogen popped up and I trustingly clocked OK thinking that perhaps THIS would fix the radio stregth issue and I can keep my rooted ROM. Instead it broke Bluetooth entirely.
So I watched a YouTube video on restoring to stock. Apparently I can't post the link,
I got all the way to the part where I use fastboot to install the zip, HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
It failed but not in the manner described in the video I believe it is due to the phone security set to S-ON but I have yet to find a way to set it back to S-OFF from where things are now.
This was the steps from the video I followed starting with fastboot getvar version-main and the fastboot oem lock
I then went through the following commands
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.054s
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot>fastboot flash zip HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
sending 'zip' (1249780 KB)...
OKAY [ 47.434s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.191s
And so it failed. The HTC screen came up but there was no progress bar so I know that fast boot is talking to the phone. I have been looking for a fix ever since and I am presently using a flip phone while working on getting the HTC One back.
Presently the phone boots directly into fastboot and will not allow me to do anything but reboot or power down but I can still use fastboot.
Revolutionary just sits at waiting for device.
The HTC One Toolkit is of no use as it also cannot see the device.
This is what is on the screen presently. Any help would be appreciated.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.502.2
eMMC-boot 2048MB
Apr 22 2014,01:10:58.0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Here is the results for fastboot getvar all
C:\fastboot>fastboot getvar all
(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) serialno: XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4290mV
(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
all: Done!
finished. total time: 0.048s

TexMachina said:
I am looking for some help in getting my HTC One M7 back up and working.
I used the online Cyanogenmod installer on my at&t HTC One M7 and it worked for the most part including where it contacts the HTC site to place the phone in developer mode.
Unfortunately the radio was far weaker and was losing it's signal all the time. I tried a few nightly's in hopes it was a bug that would be addressed but the issue with radio strength continued. Then an alert about an update from Cyanogen popped up and I trustingly clocked OK thinking that perhaps THIS would fix the radio stregth issue and I can keep my rooted ROM. Instead it broke Bluetooth entirely.
So I watched a YouTube video on restoring to stock. Apparently I can't post the link,
I got all the way to the part where I use fastboot to install the zip, HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
It failed but not in the manner described in the video I believe it is due to the phone security set to S-ON but I have yet to find a way to set it back to S-OFF from where things are now.
This was the steps from the video I followed starting with fastboot getvar version-main and the fastboot oem lock
I then went through the following commands
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.054s
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot>fastboot flash zip HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
sending 'zip' (1249780 KB)...
OKAY [ 47.434s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.191s
And so it failed. The HTC screen came up but there was no progress bar so I know that fast boot is talking to the phone. I have been looking for a fix ever since and I am presently using a flip phone while working on getting the HTC One back.
Presently the phone boots directly into fastboot and will not allow me to do anything but reboot or power down but I can still use fastboot.
Revolutionary just sits at waiting for device.
The HTC One Toolkit is of no use as it also cannot see the device.
This is what is on the screen presently. Any help would be appreciated.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.502.2
eMMC-boot 2048MB
Apr 22 2014,01:10:58.0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Here is the results for fastboot getvar all
C:\fastboot>fastboot getvar all
(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) serialno: HT3xxxxxxxxxxxxxx
(bootloader) imei: 354xxxxxxxxx
(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: 4290mV
(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
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Ok
First thing .. edit your post above and remove the Serialno and IMEI
second the file you downloaded is my TWRP Backup and has to be restored using TWRP ...not flashed
it would be easier for you to use the Guru Reset I made
here >> http://www.androidfilehost.com/?fid=23501681358545274
So unlock your bootloader and flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload the Guru Reset from within TWRP
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
Ok
First thing .. edit your post above and remove the Serialno and IMEI
Click to expand...
Click to collapse
Whooops!
Thanks for the heads up on that. I'll get to work on the fix and post an update later.

I am getting the signature verify fail error when attempting to load the recovery image now. Is this due to security being set on, S-ON?
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.
3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.116s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.863s
I made sure the images were in the fastboot directory.
Directory of C:\fastboot
08/23/2014 12:56 PM <DIR> .
08/23/2014 12:56 PM <DIR> ..
04/05/2012 05:49 AM 162,816 adb.exe
04/05/2012 05:49 AM 96,256 AdbWinApi.dll
04/05/2012 05:49 AM 70,144 fastboot.exe
08/23/2014 12:48 PM 986,880,264 Guru_Reset_M7_5.12.502.2_clsA.zip
08/23/2014 12:42 PM 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
5 File(s) 996,613,896 bytes

TexMachina said:
I am getting the signature verify fail error when attempting to load the recovery image now. Is this due to security being set on, S-ON?
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.
3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.116s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.863s
I made sure the images were in the fastboot directory.
Directory of C:\fastboot
08/23/2014 12:56 PM <DIR> .
08/23/2014 12:56 PM <DIR> ..
04/05/2012 05:49 AM 162,816 adb.exe
04/05/2012 05:49 AM 96,256 AdbWinApi.dll
04/05/2012 05:49 AM 70,144 fastboot.exe
08/23/2014 12:48 PM 986,880,264 Guru_Reset_M7_5.12.502.2_clsA.zip
08/23/2014 12:42 PM 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
5 File(s) 996,613,896 bytes
Click to expand...
Click to collapse
no your doing fine.. just unlock the bootloader

clsA said:
no your doing fine.. just unlock the bootloader
Click to expand...
Click to collapse
I'm not sure I am doing this right. I am getting what appears to be a syntax error.
C:\fastboot>fastboot devices
HT34XXXXXXXX fastboot
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.023s]
finished. total time: 0.023s
This is the command I sued from the original YouTube video on locking it for stock ROM. It shows it as having already been locked now.
C:\fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.002s]
finished. total time: 0.002s
Stupid me, sorry. I had Cyanogenmod do it for me last time. I am on HTCDev getting my unlock token now.

TexMachina said:
I'm not sure I am doing this right. I am getting what appears to be a syntax error.
C:\fastboot>fastboot devices
HT34XXXXXXXX fastboot
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.023s]
finished. total time: 0.023s
This is the command I sued from the original YouTube video on locking it for stock ROM. It shows it as having already been locked now.
C:\fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
no you have to go back to HTCDEV.com and get the unlock token from htc

clsA said:
no you have to go back to HTCDEV.com and get the unlock token from htc
Click to expand...
Click to collapse
Sorry about that. I had the Cyanogenmod install site do it for me last time.
I completed the unlocking but the Android Debug Bridge does not recognize the sideload command. It just spits back the help menu.
C:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
finished. total time: 0.146s
C:\fastboot>fastboot devices
HT34xxxxxxxx fastboot
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.115s]
writing 'recovery'...
OKAY [ 0.718s]
finished. total time: 1.833s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\fastboot>adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
Android Debug Bridge version 1.0.29
... <entire help menu>
Perhaps my adb version is not correct. I did find reference to a push command in the help menu.
adb push <local> <remote> - copy file/dir to device
Also, there is that fastboot command I attempted to use before I unlocked the bootloader.
Also also, thanks for all the help.
edit: I didn't reboot into recovery. I did now but it is asking for a password

TexMachina said:
Sorry about that. I had the Cyanogenmod install site do it for me last time.
I completed the unlocking but the Android Debug Bridge does not recognize the sideload command. It just spits back the help menu.
C:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
finished. total time: 0.146s
C:\fastboot>fastboot devices
HT34xxxxxxxx fastboot
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.115s]
writing 'recovery'...
OKAY [ 0.718s]
finished. total time: 1.833s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\fastboot>adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
Android Debug Bridge version 1.0.29
... <entire help menu>
Perhaps my adb version is not correct. I did find reference to a push command in the help menu.
adb push <local> <remote> - copy file/dir to device
Also, there is that fastboot command I attempted to use before I unlocked the bootloader.
Also also, thanks for all the help.
edit: I didn't reboot into recovery. I did now but it is asking for a password
Click to expand...
Click to collapse
theirs no password on TWRP
To sideload
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
theirs no password on TWRP
To sideload
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
I appreciate all the help and I don't want to appear difficult but when I run the adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip with the rom in the same folder adb simply refuses to recognize the sideload command. It spits back the help menu and I can't find sideload in said menu.
edit: I am using adb push to place the rom on the phones /sdcard directory and I am gong to use TWRP to install while in recovery mode. The copy is taking a while so if this is going to brick my phone let me know.
edit 2: now I don;t think I want to do this. The online resource don't mention anything specifically about installing a ROM using this method.
edit 3: I tried using the HTC One Toolkit which comes with adb 1.0.31. It gave me the following error
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT34xxxxxxxx recovery
adb sideload "File Path..."
* cannot read 'sideload' *
adb sideload "C:\fastboot\Guru_Reset_M7_5.12.502.2_clsA.zip"
error: closed
I am going to the gym to clear my head. Thanks again for all the help so far.

TexMachina said:
I appreciate all the help and I don't want to appear difficult but when I run the adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip with the rom in the same folder adb simply refuses to recognize the sideload command. It spits back the help menu and I can't find sideload in said menu.
edit: I am using adb push to place the rom on the phones /sdcard directory and I am gong to use TWRP to install while in recovery mode. The copy is taking a while so if this is going to brick my phone let me know.
edit 2: now I don;t think I want to do this. The online resource don't mention anything specifically about installing a ROM using this method.
Click to expand...
Click to collapse
your doing fine ..what was the error and why is sideload not in your version of TWRP ?
Is this the same resource that suggested flashing a TWRP recovery file with fastboot ? ... trust me you in good hands now ..just push the rom and flash it
during install choose no to install stock recovery and yes to Root the phone.
unless of coarse you want a stock unrooted phone

clsA said:
your doing fine ..what was the error and why is sideload not in your version of TWRP ?
Is this the same resource that suggested flashing a TWRP recovery file with fastboot ? ... trust me you in good hands now ..just push the rom and flash it
during install choose no to install stock recovery and yes to Root the phone.
unless of coarse you want a stock unrooted phone
Click to expand...
Click to collapse
I didn't realize the thread went to page 2. I thought you just dropped off the tread.
Sideload is in TWRP but it does ask for a password. I loaded TWRP 2.6.3.0 and it doesn't ask for a password.
I am pushing the Guru_Reset_M7_5.12.502.2_clsA.zip to /sdcard again. I will try the install once it is there.

TexMachina said:
I didn't realize the thread went to page 2. I thought you just dropped off the tread.
Sideload is in TWRP but it does ask for a password. I loaded TWRP 2.6.3.0 and it doesn't ask for a password.
I am pushing the Guru_Reset_M7_5.12.502.2_clsA.zip to /sdcard again. I will try the install once it is there.
Click to expand...
Click to collapse
I can't tell you if TWRP 2.6.3.0 will work with the Guru Reset ..it's very old and untested
if you saw a password in TWRP 2.6.3.3 you just swipe to make it go away

clsA said:
I can't tell you if TWRP 2.6.3.0 will work with the Guru Reset ..it's very old and untested
if you saw a password in TWRP 2.6.3.3 you just swipe to make it go away
Click to expand...
Click to collapse
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.

TexMachina said:
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.
Click to expand...
Click to collapse
Yeah have a great night.
When you get back >>
Is you phone sdcard full ?
have you done factory reset and or format data partition in TWRP?
If it's too full to push / sideload a rom.
TWRP does have a file manager feature you may need to free up space using it. adb 1.0.31 is the version i use all the time... never an issue.
you would get mounting errors if the partitions were formatted or erased...it's ok the new rom recreates them

TexMachina said:
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.
Click to expand...
Click to collapse
Point D here: http://forum.xda-developers.com/showpost.php?p=53270352&postcount=21

clsA said:
Yeah have a great night.
When you get back >>
Is you phone sdcard full ?
have you done factory reset and or format data partition in TWRP?
If it's too full to push / sideload a rom.
TWRP does have a file manager feature you may need to free up space using it. adb 1.0.31 is the version i use all the time... never an issue.
you would get mounting errors if the partitions were formatted or erased...it's ok the new rom recreates them
Click to expand...
Click to collapse
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.

TexMachina said:
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.
Click to expand...
Click to collapse
Great !! Thank you !

TexMachina said:
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.
Click to expand...
Click to collapse
clsA said:
Great !! Thank you !
Click to expand...
Click to collapse
a few months late to the party but how did you clear the partitions because I'm getting
E: Unable to mount '/cashe'
edit: Finished the adb push but HTC One still goes into Cyanogenmod......hopefully i can just leave this alone for a while cause atleast it turns on now

xaviergreaux said:
a few months late to the party but how did you clear the partitions because I'm getting
E: Unable to mount '/cashe'
edit: Finished the adb push but HTC One still goes into Cyanogenmod......hopefully i can just leave this alone for a while cause atleast it turns on now
Click to expand...
Click to collapse
after pushing a file you still have to install it
adb sideload copy's the file and installs it. Push does not

[Q] Softbricked the M7, made it even worse afterwards. Do'nt know what to do

So, I've tried to get S-Off for a while, but my OS had to be the same as ROM version, so I did that. But here's where it went from bad to worse.. I flashed what I thought was a new ROM, but apparently there was no OS installed now.. It asked me if I wanted to unroot my phone in recovery, I unknowingly swiped yes.. So now I'm stuck here in fastboot without recovery and I can't flash a new recovery since I also did fastboot oem lock, and when I try to unlock bootloader all I get is "cannot open Unlock_code.bin" Any help would be greatly appreciated! I'm quite familiar with rooting, I've had similar ROMs on my phone before. The phone is from december 2013. Anyone knows what I can do

RichardFilipino said:
So, I've tried to get S-Off for a while, but my OS had to be the same as ROM version
Click to expand...
Click to collapse
not entirely necessary, sometimes helps, S-Off options (depending on your situation)
revone/moonshine -> rumrunner -> firewater -> sunshine (sunshine is by far the easiest and most reliable, but does cost $25)
RichardFilipino said:
It asked me if I wanted to unroot my phone in recovery, I unknowingly swiped yes
Click to expand...
Click to collapse
it asked you if you wanted to root, not UNroot.
RichardFilipino said:
"cannot open Unlock_code.bin"
Click to expand...
Click to collapse
cannot open / cannot load is usually MyFileNameIsWrong, or not in the same folder etc.

Sorry, I meant root yes..
The code name is right and it's in the right folder.. I've checked that multiple times even when trying to fastboot other files, recovery.img is able to read but not able to flash since I locked it..

RichardFilipino said:
Sorry, I meant root yes..
The code name is right and it's in the right folder.. I've checked that multiple times even when trying to fastboot other files, recovery.img is able to read but not able to flash since I locked it..
Click to expand...
Click to collapse
please:
1- post a "fastboot getvar all" (excluding IMEI and s/n)
2- post the directory contents
3- also, please post the complete command line output as you try to flash the unlock token

getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I can't post pictures yet is what it says .

RichardFilipino said:
getvar all:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
I can't post pictures yet is what it says .
Click to expand...
Click to collapse
Edit you post and remove your IMEI and s/n.
don't do screenshots, copy/paste command prompt
example:
Code:
C:\ADB2>cd \ADB3
C:\ADB3>dir
Volume in drive C has no label.
Volume Serial Number is 0622-9D4A
Directory of C:\ADB3
10/10/2014 16:37 <DIR> .
10/10/2014 16:37 <DIR> ..
30/09/2014 19:41 1,482 .twrps
06/02/2014 13:30 513,791 1.29.401.12_hboot_1.44.zip
21/03/2014 15:34 <DIR> 1.29.401.12_hboot_1.44_v2_old
28/03/2014 22:28 0 2014-03-28-adbsync.txt
21/12/2013 13:26 819,200 adb.exe
19/09/2013 22:17 98,304 adbsync.exe
21/12/2013 13:26 96,256 AdbWinApi.dll
21/12/2013 13:26 60,928 AdbWinUsbApi.dll
03/09/2013 13:05 4,164,094 aroma-2.70RC2.zip
30/09/2014 18:31 <DIR> BACKUPS
04/08/2014 18:47 493,416 blink.txt
06/06/2014 21:06 26,904 dmesg.txt
02/05/2014 18:39 0 enter
21/12/2013 13:26 160,256 fastboot.exe
07/03/2014 15:27 <DIR> fw
29/01/2014 18:58 25,271,322 fw_4.19.401.8_custom.zip
22/06/2014 17:22 30,308,418 fw_5.11.401.10_custom.zip
09/09/2014 19:09 30,305,900 fw_6.09.401.5_custom.zip
14/11/2013 21:54 3,645,591 Guru_Bootloader_Reset_1.0.zip
01/05/2014 11:51 1,047,040 mmcblk0p19_bak__xx.img
22/02/2014 14:18 1,047,040 mmcblk0p19_donkeykong1_repaired__xx.img
13/09/2014 13:45 1,047,040 mmcblk0p19_misc.img
02/05/2014 18:40 1,047,040 mmcblk0p19_repaired.img
01/07/2014 16:46 671,088,128 mmcblk0p36_cache.img
12/06/2014 12:22 262,144 mmcblk0p6_bak.img
19/11/2013 16:13 297,289,697 one-1.28.401.7-preloaded-modaco-withoutmovie.zip
09/06/2013 14:21 498,167 orig_hboot_1.44.0000_M7_RUUmode.zip
31/01/2014 11:35 <DIR> partitions
02/05/2014 15:31 <DIR> partitions_2014-01-13
29/04/2014 15:17 <DIR> partitions_2014-02-22
01/05/2014 16:41 <DIR> partition_x1
30/09/2014 18:31 <DIR> RECOVERIES
09/06/2013 16:02 648,208 revone
03/11/2013 21:56 249,028 Screenshot_2013-11-03-20-51-36.png
26 File(s) 1,070,189,394 bytes
10 Dir(s) 26,743,398,400 bytes free
C:\ADB3>
Code:
C:\ADB3>adb version
Android Debug Bridge version 1.0.31
C:\ADB3>fastboot devices
HT34xxxxxxxx fastboot <- you are in bootloader
C:\ADB3>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s

Oh it said excluding.. That was dumb.. Quite new to this all..
c:\adb>fastboot flash unlocktoken unlock.bin
error: cannot open 'unlock.bin'

RichardFilipino said:
Oh it said excluding.. That was dumb.. Quite new to this all..
c:\adb>fastboot flash unlocktoken unlock.bin
error: cannot open 'unlock.bin'
Click to expand...
Click to collapse
file name is wrong

I named it that myself.

RichardFilipino said:
I named it that myself.
Click to expand...
Click to collapse
In your fastboot command window type
Code:
fastboot flash unlocktoken
Leaving a space on the end
Then drag and drop the unlock_code.bin into the command window, and hit enter.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

That worked!
Although I tried to flash a stock RUU with the bootloader still locked..
c:\adb>fastboot flash zip "C:\adb\fastboot\RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3
.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.z
ip"
target reported max download size of 1514139648 bytes
sending 'zip' (1180768 KB)...
OKAY [ 47.548s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 166.616s

RichardFilipino said:
That worked!
Although I tried to flash a stock RUU with the bootloader still locked..
c:\adb>fastboot flash zip "C:\adb\fastboot\RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3
.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.z
ip"
target reported max download size of 1514139648 bytes
sending 'zip' (1180768 KB)...
OKAY [ 47.548s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 166.616s
Click to expand...
Click to collapse
The fact that dragging and dropping the file worked indicates that previously there was a problem with the files name or location. Check your using the correct fastboot/adb folder for both storing your files and running your commands.
You can't downgrade untill your s-off. Your hboot suggests your on 4.xx.531.x so you can't use that ruu.
If your phone is not booting you need to push a Rom and try to s-off first. The initial problem you had (with no os installed) was probably due to rom/recovery incompatibility.
Download Twrp 2.6.3.3 form here
http://techerrata.com/browse/twrp2/m7 and flash it in fastboot.
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Then boot to twrp recovery home screen and push your Rom
Code:
adb push "nameofrom".zip /sdcard
You can use the drag and drop method for these commands also (if you need) just remember to leave spaces in the appropriate places. The command window will appear unresponsive until the push completes. Once it's done install the Rom with twrp recovery.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
In your fastboot command window type
Code:
fastboot flash unlocktoken
Leaving a space on the end
Then drag and drop the unlock_code.bin into the command window, and hit enter.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Ah, I have to remember that one
Danny201281 said:
Your hboot suggests your on 4.xx.531.x so you can't use that ruu.
Click to expand...
Click to collapse
RichardFilipino said:
That worked!
Although I tried to flash a stock RUU with the bootloader still locked..
c:\adb>fastboot flash zip "C:\adb\fastboot\RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3
.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.z
ip"
target reported max download size of 1514139648 bytes
sending 'zip' (1180768 KB)...
OKAY [ 47.548s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 166.616s
Click to expand...
Click to collapse
You can't use those RUUs, those are for US T-Mobile (MID= PN0713000 + CID: T-MOB010), you have a German T-Mobile (MID= PN0710000 + CID: T-MOB101)
so you should currently be on 4.xx.111.x

nkk71 said:
You can't use those RUUs, those are for US T-Mobile (MID= PN0713000 + CID: T-MOB010), you have a German T-Mobile (MID= PN0710000 + CID: T-MOB101)
so you should currently be on 4.xx.111.x
Click to expand...
Click to collapse
Ahh yes that makes more sense , i thought it should be with identifier 111 after searching cid and mid.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
The fact that dragging and dropping the file worked indicates that previously there was a problem with the files name or location. Check your using the correct fastboot/adb folder for both storing your files and running your commands.
You can't downgrade untill your s-off. Your hboot suggests your on 4.xx.531.x so you can't use that ruu.
If your phone is not booting you need to push a Rom and try to s-off first. The initial problem you had (with no os installed) was probably due to rom/recovery incompatibility.
Download Twrp 2.6.3.3 form here
http://techerrata.com/browse/twrp2/m7 and flash it in fastboot.
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Then boot to twrp recovery home screen and push your Rom
Code:
adb push "nameofrom".zip /sdcard
You can use the drag and drop method for these commands also (if you need) just remember to leave spaces in the appropriate places. The command window will appear unresponsive until the push completes. Once it's done install the Rom with twrp recovery.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
TWRP 2.6.3.3 didn't work.. Recovery still gets me to the screen of fastboot usb..

RichardFilipino said:
TWRP 2.6.3.3 didn't work.. Recovery still gets me to the screen of fastboot usb..
Click to expand...
Click to collapse
So you flashed TWRP 2.6.3.3 and fastboot erase cache which were successful?
But when you boot to Recovery it goes back to the bootloader, Is that correct?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

So you flashed TWRP 2.6.3.3 and fastboot erase cache which were successful?
But when you boot to Recovery it goes back to the bootloader, Is that correct?
Click to expand...
Click to collapse
Yes, that is correct. Don't really know what options are left at the moment

RichardFilipino said:
Yes, that is correct. Don't really know what options are left at the moment
Click to expand...
Click to collapse
It's possible something has been flashed that maybe shouldn't have and made a mess of the partitions.
Try this :- Download this stock recovery
http://d-h.st/Eq1
And flash it with fastboot remember to fastboot erase cache, then try boot to Recovery. If it boots the screen will be blank for a short while, then display an image of a phone with red exclamation this is normal. Holding volume up and press the power button to reveal the stock recovery menu. Ignore the Mount sd card errors that's also normal in stock recovery. Now perform a factory reset and wipe cache.
Reboot the phone back to the bootloader and flash twrp 2.6.3.3 then fastboot erase cache. Hopefully now twrp will boot. :finger-crossed:
If it does go into the "Wipe" options and select " Format Data" you will be prompted to type yes to confirm. Then 're-push the Rom and install with TWRP.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

It's possible something has been flashed that maybe shouldn't have and made a mess of the partitions.
Try this :- Download this stock recovery
http://d-h.st/Eq1
And flash it with fastboot remember to fastboot erase cache, then try boot to Recovery. If it boots the screen will be blank for a short while, then display an image of a phone with red exclamation this is normal. Holding volume up and press the power button to reveal the stock recovery menu. Ignore the Mount sd card errors that's also normal in stock recovery. Now perform a factory reset and wipe cache.
Reboot the phone back to the bootloader and flash twrp 2.6.3.3 then fastboot erase cache. Hopefully now twrp will boot. :finger-crossed:
If it does go into the "Wipe" options and select " Format Data" you will be prompted to type yes to confirm. Then 're-push the Rom and install with TWRP.
Click to expand...
Click to collapse
Tried that:
Code:
c:\adb>fastboot flash recovery C:\adb\recovery_4.20.111.21.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12422 KB)...
OKAY [ 1.527s]
writing 'recovery'...
OKAY [ 0.928s]
finished. total time: 2.456s
c:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.527s]
finished. total time: 0.527s
Went from fastboot USB to bootloader, tried to enter recovery.. Nothing, straight into fastboot USB again.

RichardFilipino said:
Tried that:
Code:
c:\adb>fastboot flash recovery C:\adb\recovery_4.20.111.21.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12422 KB)...
OKAY [ 1.527s]
writing 'recovery'...
OKAY [ 0.928s]
finished. total time: 2.456s
c:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.527s]
finished. total time: 0.527s
Went from fastboot USB to bootloader, tried to enter recovery.. Nothing, straight into fastboot USB again.
Click to expand...
Click to collapse
sorry man I'm running out of ideas here. Only options left really is to flash firmware or an ruu. Unfortunately I can't find anything that will work for you with s-on.
What was the last recovery you had working on the phone?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Stuck at Silver logo screen

Hi
I flashed my HTC One M7 firmware to OS-7.19.401.2 (Unfrotunately wasn't in S-Off when I did it).
This is what it looks lke at the moment:
*** RELOCKED ***
M7-UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.2 (7.19.401.2)
I did it after I tried to update to Lollipop from Android 4.4.3 which crashed on me. Being impatient I terminated the update after taking so long.
I tried relashing but am not having any luck getting it to return to normal(when I do reflash it the second time with the same command it stalls at the silver htc logo screen), I do have the unlock.bin file but it's not working and I can't access the SDcard on the phone either.
Thanks for any help!

klaymeb said:
Hi
I flashed my HTC One M7 firmware to OS-7.19.401.2 (Unfrotunately wasn't in S-Off when I did it).
This is what it looks lke at the moment:
*** RELOCKED ***
M7-UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.2 (7.19.401.2)
I did it after I tried to update to Lollipop from Android 4.4.3 which crashed on me. Being impatient I terminated the update after taking so long.
I tried relashing but am not having any luck getting it to return to normal(when I do reflash it the second time with the same command it stalls at the silver htc logo screen), I do have the unlock.bin file but it's not working and I can't access the SDcard on the phone either.
Thanks for any help!
Click to expand...
Click to collapse
seems your using a custom firmware, try this one >> https://www.androidfilehost.com/?fid=95916177934533542
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot

So I changed the zip folder name to firmware, And reflashed it again as per above instructions, And it worked...
The only thing is I keep ending back at the same point again, of the phone not going back into Anfroid (I haven't put a Sim card back in yet)...
What else do I need to do to get it back into Android? Stuck in Bootloader....

klaymeb said:
So I changed the zip folder name to firmware, And reflashed it again as per above instructions, And it worked...
The only thing is I keep ending back at the same point again, of the phone not going back into Anfroid (I haven't put a Sim card back in yet)...
What else do I need to do to get it back into Android? Stuck in Bootloader....
Click to expand...
Click to collapse
This is my 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: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

klaymeb said:
This is my 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: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
!!!!read all steps first!!!!
1. unlock your bootloader
2. flash custom recovery TWRP 2.8.5.0 ("fastboot flash recovery twrp.img" then "fastboot erase cache" finally "fastboot reboot-bootloader")
3. download this rom https://basketbuild.com/dl/devs?dl=Artur0588/M7_7.19.401.2.zip and put it on the fastboot/adb folder
4. extract firmware.zip (thread #2) and copy boot.img in the fastboot folder
5. extract from the firmware.zip (that you've downloaded in thread #2) recovery.img and paste in the fastboot/adb folder
6. "adb devices" to verify that your device is connected, then "adb push rom.zip /sdcard/" it will take about 5 min.
7. now "fastboot flash boot boot.img" then "fastboot reboot-bootloader"
8. enter to recovery mode and make full wipe (data/dalvick/chache)
9. choose install >> select rom.zip and swipe.
10. when installation finish up flash the stock recovery "fastboot flash recovery recovery.img" , "fastboot erase cache" , "fastboot oem lock" and "fastboot erase cache"

Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.

klaymeb said:
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
Click to expand...
Click to collapse
Write the unlock command that you are using here, and the error message too.

klaymeb said:
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
Click to expand...
Click to collapse
Are you using the correct drivers for Windows 8.1?
In your device manager is your phone detected?
When your phone is in bootloader is it detected by fastboot? Type fastboot devices into your command prompt and it should list the serial no of your device.
Also, use USB 2.0 rather than 3.0

VoynichJimmy said:
Write the unlock command that you are using here, and the error message too.
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin (as per HTCdev instructions)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1492578304 bytes
error: cannot load 'Unlock_code.bin': No error

klaymeb said:
fastboot flash unlocktoken Unlock_code.bin (as per HTCdev instructions)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1492578304 bytes
error: cannot load 'Unlock_code.bin': No error
Click to expand...
Click to collapse
The command looks like it's ok. The unlock code is definitely in your fastboot folder
When you go to device manager when your phone is connected at the bootloader screen is your phone detected there? Does the command fastboot devices show your serial no?

stovie_steve said:
Are you using the correct drivers for Windows 8.1?
Driver Version: 2.0.7.27
In your device manager is your phone detected?
Yes.
When your phone is in bootloader is it detected by fastboot? Type fastboot devices into your command prompt and it should list the serial no of your device.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
FA426W904521 fastboot
Also, use USB 2.0 rather than 3.0
Click to expand...
Click to collapse
Ok Thanks, I thought that might be the case with it.

stovie_steve said:
The command looks like it's ok. The unlock code is definitely in your fastboot folder
When you go to device manager when your phone is connected at the bootloader screen is your phone detected there?
Does the command fastboot devices show your serial no?
Click to expand...
Click to collapse
Only thing I can think of if your drivers are working, fastboot detects your phone and you are running the right command is to start it again and request a new unlock code

stovie_steve said:
Only thing I can think of if your drivers are working, fastboot detects your phone and you are running the right command is to start it again and request a new unlock code
Click to expand...
Click to collapse
I just tried that, but no luck...
This is what I'm getting at the moment:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
I think the SDCard is not working.

klaymeb said:
I just tried that, but no luck...
This is what I'm getting at the moment:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
I think the SDCard is not working.
Click to expand...
Click to collapse
The sdcard wouldn't have any effect on this working...
The unlock code should be in your adb folder on your PC

stovie_steve said:
The sdcard wouldn't have any effect on this working...
The unlock code should be in your adb folder on your PC
Click to expand...
Click to collapse
I have put it in a ADB_Windows folder which was created when I installed Minimal ADB and Fastboot software, so I'm not sure why it's not running at this stage.
Do I need to reinstall ADB and Fastboot on the PC again and create a new folder for it?

klaymeb said:
I have put it in a ADB_Windows folder which was created when I installed Minimal ADB and Fastboot software, so I'm not sure why it's not running at this stage.
Do I need to reinstall ADB and Fastboot on the PC again and create a new folder for it?
Click to expand...
Click to collapse
What is the folder directory where you have your adb and fastboot files?

stovie_steve said:
What is the folder directory where you have your adb and fastboot files?
Click to expand...
Click to collapse
Just figured out that I wast trying to use the Unlock file in the wrong place, This is what I've just done now:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unloc
k_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.151s

klaymeb said:
Just figured out that I wast trying to use the Unlock file in the wrong place, This is what I've just done now:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unloc
k_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.151s
Click to expand...
Click to collapse
And I just tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.033s]
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 20.471s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 72.998s

klaymeb said:
And I just tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.033s]
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 20.471s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 72.998s
Click to expand...
Click to collapse
As you are s-on, your bootloader needs to be locked to flash firmware, unlock it after the flash, but just to be sure, as you struggled to even unlock your bootloader, which firmware are you trying to flash, because if its the wrong one, you'll hard brick your phone.
if your looking to upgrade to Lollipop, just flash this, it will make you full stock Lollipop, it will also wipe your device, so make sure you backup anything you want to keep
https://www.androidfilehost.com/?fid=95916177934537475
just rename the file once its downloaded to RUU and put it in the same folder as adb, fastboot, your unlock code etc on your computer and then follow these instructions:
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip - fully automated so no need to do it twice
fastboot reboot-bootloader
fastboot reboot
after your first setup, you can do what you want, unlock your bootloader at this point, flash a custom recovery, root etc.

Seanie280672 said:
As you are s-on, your bootloader needs to be locked to flash firmware, unlock it after the flash, but just to be sure, as you struggled to even unlock your bootloader, which firmware are you trying to flash, because if its the wrong one, you'll hard brick your phone.
if your looking to upgrade to Lollipop, just flash this, it will make you full stock Lollipop, it will also wipe your device, so make sure you backup anything you want to keep
https://www.androidfilehost.com/?fid=95916177934537475
just rename the file once its downloaded to RUU and put it in the same folder as adb, fastboot, your unlock code etc on your computer and then follow these instructions:
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip - fully automated so no need to do it twice
fastboot reboot-bootloader
fastboot reboot
after your first setup, you can do what you want, unlock your bootloader at this point, flash a custom recovery, root etc.
Click to expand...
Click to collapse
So this is what I did, And I still end up back at the bootloader.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Device was already locked!
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.032s]
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1264453 KB)...
OKAY [ 41.892s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 122.212s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.035s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>

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.