HTC One M7 PN0713000

[engineerchad]

I need some help with this device. It is an HTC One M7 (PN0713000).

Resurrection went smoothly and I can boot to hboot (actually it will attempt to boot to the OS but fails now)
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [HTC OneM7 (PN0713000) V1.0.5149.50216]

Connecting to the dead body...OK
Detected dead body ID: 0x207150E1 - CORRECT!
Set I/O Voltage reads as 1.81V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at 1 MHz]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x0090/0x014A (HBG4E, 0x000748000000 Bytes = 29.13 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0090/0x014A (HBG4E, 0x000000400000 Bytes = 4.00 MB)

No Resurrection Data is available for the eMMC Chip with Capacity = 29.13GB
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 29.12GB

Flashing the dead body...OK
Resurrection complete!

After resurrection, I attempt to flash RUU .zip (TMOUS JB 43) with this message:

sending 'zip' (1180768 KB)...
OKAY [ 57.868s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 177.885s

Then attempt JB50 TMOUS RUU with this result:
sending 'zip' (1037376 KB)...
OKAY [ 48.682s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 154.087s

I have attempted to use the RUU .exe only to find that the battery is not reporting any charge (no matter how long I charge the phone!) Here is the log from that ruu:
<LOG>
<T202750><INFO><VERSION>2.0.9.2014</VERSION></INFO></T202750>
<T202750><INFO>start read zip</INFO></T202750>
<T202750><INFO>T
</INFO></T202750>
<T202750><INFO>Finish read zip.</INFO></T202750>
<T202751><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T202751>
<T202757><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T202757>
<T202757><DEBUG><CMD>adb devices</CMD>
</DEBUG></T202757>
<T202757><DEBUG><OUT>List of devices attached
emulator-5554 device
</OUT>
</DEBUG></T202757>
<T202757><DEBUG><CMD>adb devices</CMD>
</DEBUG></T202757>
<T202759><DEBUG><OUT>List of devices attached
emulator-5554 device
</OUT>
</DEBUG></T202759>
<T202759><DEBUG><CMD>adb devices</CMD>
</DEBUG></T202759>
<T202800><DEBUG><OUT>List of devices attached
emulator-5554 device
</OUT>
</DEBUG></T202800>
<T202800><DEBUG><CMD>adb -s emulator-5554 shell cat /sys/class/power_supply/battery/capacity</CMD>
</DEBUG></T202800>
<T202801><DEBUG><OUT>/system/bin/sh: cat: /sys/class/power_supply/battery/capacity: No such file or directory</OUT>
</DEBUG></T202801>
<T203105><DEBUG><CMD>adb devices</CMD>
</DEBUG></T203105>
<T203106><DEBUG><OUT>List of devices attached
emulator-5554 device
</OUT>
</DEBUG></T203106>
<T203106><DEBUG><CMD>adb devices</CMD>
</DEBUG></T203106>
<T203107><DEBUG><OUT>List of devices attached
emulator-5554 device
</OUT>
</DEBUG></T203107>
<T203107><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T203107>
<T203109><DEBUG><OUT>* server not running *</OUT>
</DEBUG></T203109>
</LOG>


Anyone that can supply ideas on this? It would be greatly appreciated!

EDIT: fastboot variables added:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.00
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37GS906213
(bootloader) imei: xxxxxxxxxxxxxxx (redacted)
(bootloader) meid: xxxxxxxxxxxxxxxx (redacted)
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4273mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-57eb7f637d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
OKAY [ 4.850s]
finished. total time: 4.850s

[oblio]

(bootloader) cidnum: T-MOB010
.........
(bootloader) security: on

Either find a RUU for you cid: T-MOB010 or make it S-OFF then cid unlock to be able to flash any RUU...

[engineerchad]

I was using a T-Mobile RUU for that CID. I appreciate the idea you offered.

I got it up and running but only on the custom ROM the customer had already installed. Apparently my solution was to flash CWM touch then perform a factory reset and cache wipe. I didn't attempt the RUU again after I saw that /data and /cache were not mounting. First I attempted with TWRP, but no dice, then the formats worked with CWM so I left it as is booting into that custom rom they had.

[engineerchad]

Okay interesting issue now. The phone returned, the customer is now having trouble getting it to accept a SIM. It came to me without a valid IMEI so I set that and the CID in order to get the RUU to flash but, then no RUU from T-Mobile would flash. It then attempted to boot into the custom ROM, I left that there after the factory data reset restored the partitions. Now, it won't take the T-Mobile SIM nor the RUU, it says "No Network" as well as it stopped booting temporarily as well, apparently. The Product Code shows a different type of device, either Verizon or Sprint. Customer stated that it did not come directly from T-Mobile.

Any thoughts or suggestions would be appreciated.