Database Develop

[Q] Problems downgrading roms / installing recovery etc.

First time I post on this messageboard. I have issues with my Incredible S and because I have tried everything available on the internet and here, I decided to make a thread. I'm thankful for any response I get.
Technical Background:
S-ON
Unlocked with HTCDEV key
HBoot 2.00.0000
ClockWorkMod Recovery
(Currently no rom installed, had CM7)
Background for not working:
I decided to wipe Dalvik cache and cache on the phone, and CM7 ended up being in a bootloop. ClockWorkMod Recovery complains about:
Code:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
... etc.
I've tried to install RUU, but it hangs during the process of "restarting into bootloader"
I've tried to install stock rom through SDCard, but it complains about zip-file integrity. (even though I've checked MD5 checksums etc.)
According to "adb shell dmesg" everything seems to be fine in regards of the chip, except from this:
Code:
[11.368560] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem.
Assume this is part of the /cache partition?
---
So, to start somewhere, I need help to figure out why the phone get's unresponsive when I issue commands from fastboot, like the following:
Code:
fastboot oem rebootRUU
fastboot flash recovery cwm-4.0.1.4-vivo.img
I have to take the battery out to make the phone responsive again.
Another thing, when I press "reboot bootloader" inside HBOOT(on the phone) it also hangs.
What can I do to make my phone operative again?

dabih said:
First time I post on this messageboard. I have issues with my Incredible S and because I have tried everything available on the internet and here, I decided to make a thread. I'm thankful for any response I get.
Technical Background:
S-ON
Unlocked with HTCDEV key
HBoot 2.00.0000
ClockWorkMod Recovery
(Currently no rom installed, had CM7)
Background for not working:
I decided to wipe Dalvik cache and cache on the phone, and CM7 ended up being in a bootloop. ClockWorkMod Recovery complains about:
A
Code:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
... etc.
I've tried to install RUU, but it hangs during the process of "restarting into bootloader"
I've tried to install stock rom through SDCard, but it complains about zip-file integrity. (even though I've checked MD5 checksums etc.)
According to "adb shell dmesg" everything seems to be fine in regards of the chip, except from this:
Code:
[11.368560] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem.
Assume this is part of the /cache partition?
---
So, to start somewhere, I need help to figure out why the phone get's unresponsive when I issue commands from fastboot, like the following:
Code:
fastboot oem rebootRUU
fastboot flash recovery cwm-4.0.1.4-vivo.img
I have to take the battery out to make the phone responsive again.
Another thing, when I press "reboot bootloader" inside HBOOT(on the phone) it also hangs.
What can I do to make my phone operative again?
Click to expand...
Click to collapse
A couple of comments I noticed.
1. To reflash a RUU you need to have the bootloader relocked.
2. You don't have the latest version of CWM installed. Current version is 5.0.2.0
3. Do you have a file named PG32IMG.zip on the phone? If you do, that would hamper you getting into FASTBOOT USB mode.
4. Does the command: fastboot devices
Return the device serial number or does it hang too?
5. When you flashed CM7 did you manually flash the boot.img in Fastboot mode? This is required when you have an unlocked bootloader.

Try to relock the bootloader and unlock again. Then flash a newer version of the recovery. The latest of cwm is now 5.0.2.0
Sent from my HTC One X using XDA

Same thing happened to me when i flashed arhd 2.3.0....it went into a boot loop!
now incs does this..
what i did was flash the boot.img of the kernel again.
HBOOT 1.16 does some weird stuff and tends to cause issues; I think it interferes with the installation of the boot.img that ordinarily would be flashed with the ROM. Anyhow, grab the ROM that you downloaded earlier (CyanogenMod, in my example), and on your PC, unzip the file somewhere. Once unzipped, inside you'll see a file called "boot.img". Put this in the same folder as your other Android tools that you used earlier. Power your phone on, hold volume down, and instead of loading recovery by choosing "recovery", choose "usb fastboot".
Open up your command prompt again (Start > Run > "cmd"), and type (using the "android" folder for this example):
fastboot flash boot boot.img
hope it helps,

Thank you for replying, all of you.
If I could just reflash recovery. The phone get's stuck whenever fastboot/hboot tries to write the recovery image or the boot images. I'm stuck in the middle until I find out what this is caused by.
tpbklake said:
A couple of comments I noticed.
1. To reflash a RUU you need to have the bootloader relocked.
2. You don't have the latest version of CWM installed. Current version is 5.0.2.0
3. Do you have a file named PG32IMG.zip on the phone? If you do, that would hamper you getting into FASTBOOT USB mode.
4. Does the command: fastboot devices
Return the device serial number or does it hang too?
5. When you flashed CM7 did you manually flash the boot.img in Fastboot mode? This is required when you have an unlocked bootloader.
Click to expand...
Click to collapse
1. I've run "fastboot oem lock" to lock before RUU.
2. I can't update the recovery. When I try to update CWM (either through SDcard or fastboot) it fails during "writing". In HBOOT the phone locks, telling me not to power off the phone while "update" is being applied. Same goes for the fastboot method. The phone get's unresponsive.
3. I have the PG32IMG.zip only when I want to boot the update/image.
4. It returns the device. I can also do whatever I want on the phone shell. (create folders/run compiled C/delete files/chmod/format/mke2fs et. al). I can "push" files to the phone just fine too.
5. When I manually flash the boot.img in Fastboot it hangs like the scenarios mentioned above when it starts "writing"
Code:
C:\android>fastboot.exe flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.676s]
writing 'recovery'...
Code:
C:\android>fastboot.exe flash boot "IceColdSandwich-7.2-vivo (1)\boot.img"
sending 'boot' (2164 KB)...
OKAY [ 0.788s]
writing 'boot'...
^C
Code:
C:\android>fastboot.exe getvar mainver
mainver: 3.08.405.3
finished. total time: 0.003s
Code:
C:\android>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 3822.10.08.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.08.405.3
(bootloader) serialno: HT18xxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxx
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3959mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-af9874be
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.025s

dabih said:
Thank you for replying, all of you.
If I could just reflash recovery. The phone get's stuck whenever fastboot/hboot tries to write the recovery image or the boot images. I'm stuck in the middle until I find out what this is caused by.
1. I've run "fastboot oem lock" to lock before RUU.
2. I can't update the recovery. When I try to update CWM (either through SDcard or fastboot) it fails during "writing". In HBOOT the phone locks, telling me not to power off the phone while "update" is being applied. Same goes for the fastboot method. The phone get's unresponsive.
3. I have the PG32IMG.zip only when I want to boot the update/image.
4. It returns the device. I can also do whatever I want on the phone shell. (create folders/run compiled C/delete files/chmod/format/mke2fs et. al). I can "push" files to the phone just fine too.
5. When I manually flash the boot.img in Fastboot it hangs like the scenarios mentioned above when it starts "writing"
Code:
C:\android>fastboot.exe flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.676s]
writing 'recovery'...
Code:
C:\android>fastboot.exe flash boot "IceColdSandwich-7.2-vivo (1)\boot.img"
sending 'boot' (2164 KB)...
OKAY [ 0.788s]
writing 'boot'...
^C
Code:
C:\android>fastboot.exe getvar mainver
mainver: 3.08.405.3
finished. total time: 0.003s
Code:
C:\android>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 3822.10.08.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.08.405.3
(bootloader) serialno: HT18xxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxx
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3959mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-af9874be
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.025s
Click to expand...
Click to collapse
Ok so you did relock before running he RUU. Did you manually run they RUU or did you extract the ROM.zip and copy it to your SD card as PG32IMG.zip?
After that failed, did you then unlock again before trying to update the recovery or flash the boot.img?

tpbklake said:
Ok so you did relock before running he RUU. Did you manually run they RUU or did you extract the ROM.zip and copy it to your SD card as PG32IMG.zip?
After that failed, did you then unlock again before trying to update the recovery or flash the boot.img?
Click to expand...
Click to collapse
Actually I tried to do both, because this is actually my first time fiddling with the phone at this level. (I'm a programmer, but not a phone expert).
1a. I ran RUU both when phone was unlocked (not locked or relocked) and locked (oem lock)
1b. I've done both ROM.zip (sdcard method, PG32IMG.zip) and the PC version (*.exe)
In total 4 different combinations instead of 2 due to my lack of knowledge/understanding of lock/unlocked state of the bootloader.
Though all combinations fail at some point.
2a. PC Version RUU fails at "rebooting to bootloader". (Can wait up to 60 min, nothing happens even though it says wait 10 minutes. It is just stuck, as with the phone. Have to take the battery out.)
2b. Bootloader approach loads the Image just fine, (the blue progressbar up in the right corner) but gives me an error about ZIP file being corrupted or something. It's hard to see what it actually says because the screen returns to the bootloader menu very fast.
So. What I want at this point, would be RUU the phone, then revert back to my custom ROM. So maybe we can figure out how we can have the RUU work sucessfully.
I'm using this RUU:
Code:
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_sig.exe
It has the SAME radio that was on the phone before I installed CM7 a few months ago. It's the same android/sense version also. (My GF has the same phone)
I've also tried with this RUU:
Code:
RUU_VIVO_SENSE30_S_HTC_WWE_3.11.405.2_Radio_20.4805.30.0822U_3822.01.08.14_M_release_252414_signed.exe

Here are some more details on the filesystem etc.
Code:
~ # ls
boot init sys
cache init.rc system
data proc tmp
datadata res ueventd.goldfish.rc
default.prop root ueventd.rc
dev sbin ueventd.vivo.rc
emmc sd-ext
etc sdcard
~ # ls -la /etc
drwxr-xr-x 2 root root 0 Jan 1 1970 .
drwxr-xr-x 18 root root 0 Jan 8 02:16 ..
-rw-r--r-- 1 root root 333 Jan 1 1970 recovery.fstab
~ # cat /etc/recovery.fstab
# mount point fstype device [device2] fstype2
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p27 NULL ext3
/data ext4 /dev/block/mmcblk0p26 NULL ext3
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p25 NULL ext3
eMMC chip model:
Code:
~ # cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
M4G2DE
Will update with dmesg/ksmg info later because the phone is charging and is spamming recharge data in the kmsg/dmsg output.

You cannot flash a custom recovery on a locked bootloader. I suggest you go through the unlock process, flash the latest clockworkmod or 4ext recovery then do a clean install of cm7.
After you flash cm7, wipe the cache partition then manually flash the boot.img from the cm7 zip file
Code:
fastboot flash boot boot.img

Nonverbose said:
You cannot flash a custom recovery on a locked bootloader. I suggest you go through the unlock process, flash the latest clockworkmod or 4ext recovery then do a clean install of cm7.
After you flash cm7, wipe the cache partition then manually flash the boot.img from the cm7 zip file
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I've gone through the process of unlocking with fastboot and the "Unlock_code.bin" file I received from HTCDEV. Still not able to do anything.
My wish is to use a RUU, but I need to downgrade my "version_main" first, which is not possible with "misc_version" for me. (It tells me it updated the "partition" etc. but version is still the same).

dabih said:
I've gone through the process of unlocking with fastboot and the "Unlock_code.bin" file I received from HTCDEV. Still not able to do anything.
My wish is to use a RUU, but I need to downgrade my "version_main" first, which is not possible with "misc_version" for me. (It tells me it updated the "partition" etc. but version is still the same).
Click to expand...
Click to collapse
Get a rom working first

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

nexus 6 stuck in fastboot, unable to flash factory image IMEI set to zero's

Device is stuck in fastboot mode
screen shows
Device is LOCKED: Status code: 0
IMEI : 00000000000
SKU: 00000
Serial number shows values
Date being shown as 01-01-1970
Bootloader logs shows
fastboot reason: failed to initialize partition table
any advise on how to recover from this?

Fastboot erase userdata plus cache
Sent from my Nexus 6 using XDA-Developers mobile app

get error on erase
MacBook-Pro:~ user$ fastboot devices -l
994f3b10 fastboot usb:337641472X
MacBook-Pro:~ user$ fastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.067s
MacBook-Pro:~ user$ fastboot erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.066s
MacBook-Pro:~ user$

fastboot flash bootloader. Are you trying to flash N Preview?

reagan1998 said:
fastboot flash bootloader. Are you trying to flash N Preview?
Click to expand...
Click to collapse
my device was running fine with 5.1 and not sure what caused to get into this stuck where its stuck in fastboot boot
i am just trying to flash factory images from https://developers.google.com/android/nexus/images#shamu

Given the suddenness of your problem as well as the symptoms, I believe the internal memory has failed, meaning a service call. However, I hope I'm wrong.
Regardless, flashing factory images won't work because your bootloader is locked. Assuming this is a software issue you may be able to restore the system by sideloading the Android N OTA through recovery. If you can successfully do that, head to Developer Options in the N preview and enable OEM unlock. From there, unlock the bootloader, so you can flash factory images.

Strephon Alkhalikoi said:
Given the suddenness of your problem as well as the symptoms, I believe the internal memory has failed, meaning a service call. However, I hope I'm wrong.
Regardless, flashing factory images won't work because your bootloader is locked. Assuming this is a software issue you may be able to restore the system by sideloading the Android N OTA through recovery. If you can successfully do that, head to Developer Options in the N preview and enable OEM unlock. From there, unlock the bootloader, so you can flash factory images.
Click to expand...
Click to collapse
- I read some threads on sideload, they need device booted with adb access, since mine is stuck in fastboot, i don't have access to device via adb, would side load still work?
- still looking for zip for side load for nexus 6, if you have pointer for it, please let me know

To sideload the Android N OTA, which is the only thing that will help you here, you need to be able to get into recovery and set the recovery to adb sideload mode. If you cannot get into recovery, you definitely have a hardware problem and will need to get the internal storage chip replaced. As for the Android N OTA zip, check in the General subforum. Of course you could also simply do a quick Google search for "Android N OTA Brick" and get to Google's page of OTA zips that way.

Strephon Alkhalikoi said:
To sideload the Android N OTA, which is the only thing that will help you here, you need to be able to get into recovery and set the recovery to adb sideload mode. If you cannot get into recovery, you definitely have a hardware problem and will need to get the internal storage chip replaced. As for the Android N OTA zip, check in the General subforum. Of course you could also simply do a quick Google search for "Android N OTA Brick" and get to Google's page of OTA zips that way.
Click to expand...
Click to collapse
Android N has a new bootloader, so sideloading it will probably make the device not boot into Android.
---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------
Have you tried flashing a TWRP recovery and maybe flashing a custom ROM to see if it is a storage issue? This phone is not even two years old, it should not be having internal storage issues.

The Android N OTA I'm talking about includes the bootloader, as it is a full system image. Flashing TWRP will not work as the device has a locked bootloader. But since the device apparently has no partitions at all, the exercise I believe is moot. This is a hardware issue.

Run 'fastboot format cache' and 'fastboot format userdata', then run the most holy words in android 'fastboot oem unlock'. Check this: http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783 it really helped me out of a deep hole.

The only way that will work is if the OP enabled OEM Unlocking in Developer Options prior to the device forgetting its partitions. I hope he did, as having the option enabled doesn't affect the ability to get OTAs from Google. If however his device's EMMC chip failed as I believe, it won't help him resolve this issue.

reagan1998 said:
Run 'fastboot format cache' and 'fastboot format userdata', then run the most holy words in android 'fastboot oem unlock'. Check this: http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783 it really helped me out of a deep hole.
Click to expand...
Click to collapse
apologies for delayed response, i didn't realize there was second page in replies and you guys are still trying to help
here is outout
sh-3.2# fastboot devices
994f3b10 fastboot
sh-3.2# fastboot format cache
Formatting is not supported for filesystem with type ''.
sh-3.2# fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
sh-3.2# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-71.08(*)
(bootloader) product: shamu
(bootloader) board: shamu
(bootloader) secure: yes
(bootloader) hwrev: 0x83A0
(bootloader) radio: 0x6
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Elpida S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: 994f3b10
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: 7858B30111000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) aboot.git: git=MBM-NG-V71.08-0-g32b8854
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.040s
sh-3.2#

If it's failing to initialize the partition table, there's nothing you can do here. It needs to go to Motorola for warranty service.
EDIT: How I can tell? The date was set to 1/1/70. That's the beginning date of the Unix clock, which means something got screwed up internally. That plus the lost IMEI and the failure of the device to find its partitions means a bad device.
Sorry to be the bearer of bad news here, but this isn't something software can fix.

Strephon Alkhalikoi said:
If it's failing to initialize the partition table, there's nothing you can do here. It needs to go to Motorola for warranty service.
EDIT: How I can tell? The date was set to 1/1/70. That's the beginning date of the Unix clock, which means something got screwed up internally. That plus the lost IMEI and the failure of the device to find its partitions means a bad device.
Sorry to be the bearer of bad news here, but this isn't something software can fix.
Click to expand...
Click to collapse
Thanks for looking in, warranty must be void since i had open the back cover .

EDIT: Bad advice given.

Strephon Alkhalikoi said:
I would try anyway. The worst that will happen is they will want to charge you.
Click to expand...
Click to collapse
Which is considered fraud and not condoned by xda.

@zelendel: Echh. I'm not looking to get myself or XDA in trouble. I'll edit my post appropriately. Thank you for the reminder.

Strephon Alkhalikoi said:
@zelendel: Echh. I'm not looking to get myself or XDA in trouble. I'll edit my post appropriately. Thank you for the reminder.
Click to expand...
Click to collapse
Not a worry. I know a lot of people advise it but we don't condone it. This is why the disclosure in the OP of every rom thread. We accept what we do might mean killing our device and having to buy a new one. It's a risk of the hobby.

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.