HTC One M8 - Issues on bootloop & WiFi - AT&T HTC One (M8)

Hello,
I need your expertise help to resolve my phone issues. Hope someone can help. Currently, i am bit panic that my device has become unusable. Please help!!
My problem statement:
1. HTC One M8 is currently in boot loop. It boots approximately around 6 to 7 times and then enters to normal operation. This happens everytime i reboot.
2. WiFi is greyed. unable to "On" the Wifi. Still i can use my data through my SIM card.
One Important information: I DONT HAVE ANY BACKUP. I LOST IT. i kept them in the internal storage and mistakenly wiped the internal storage as well. I am unlucky
Brief of my device:
I bought this device from US. It came with AT&T. I came to India and i was using it without any issues. Howev, it doesnt update at all through Wifi or Data. Hence, with my limited knowledge, i unlocked, rooted and flashed with custom ROM. There the problem started. It got into boot loop and WiFi is greyed out. So, i thought brining back to Stock would resolve the issue and did the Stock ROm flash and recovery as well. No luck. Currently, i still have the boot loop and "WiFi" greyed out.
I used TWRP.
Below is current details & Versions:
-----------------------------------------------------
1. Bootlader:
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
openDSP-V38.2.2-00542-m8974.0311
OS-
eMMC-BOOT 2048MB
Apr 18 2014,16:06:33.0
-----------------------------------------------------
2. fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
---------------------------------------------------------
3. Software information
Androin version: 5.0.1
HTC Sense version: 6.0
Software number: 4.16.401.10
HDC SDK API level: Unknown
Kernel version: 3.4.0-g6af28ec [email protected] #1 SMP PREEMPT
BASEBAND VERSION: 1.16.21331931.LA11G_20.31A.4145.02L
Build number: 4.16.401.10 CL448934 RELEASE-KEYS
------------------------------------------------------------------
Awaiting your valuable help. Thanks in advance!
Apologise if it is not the right forum.
Thank you,
Selvaraj

---

Hi @selva_rag,
Thanks for posting in XDA Assist. I am going to move your thread to the HTC One (M8) Q&A and Troubleshooting Forum as the users there will be much better suited to help you out.
-- Gandalf

---

Your firmware is outdated (hboot, radio, etc.) , and does not support any of the current custom ROMs. Broken WiFi is a known result of firmware mismatch; and the boot loops is likely due to the same reason.
Similarly, unless you flashed any but the oldest stock ROMs (1.58.502) you will suffer from the same firmware mismatch issue.
AT&T M8 won't OTA update since you are outside the US and not on the AT&T network (this is a AT&T specific complication).
I would advise to backup your personal data (your phone will be wiped), relock your bootloader (command: fastboot oem lock) then run the 4.28.502.1 RUU here: http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
The RUU will update your firmware. From there, you can unlock the bootloader again via HTCDev.com, flash current version TWRP 2.8.7, then flash a current Lollipop custom ROM of your choice.
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
selva_rag said:
One Important information: I DONT HAVE ANY BACKUP. I LOST IT. i kept them in the internal storage and mistakenly wiped the internal storage as well. I am unlucky
Click to expand...
Click to collapse
This has nothing to do with luck. This is a failure to use good judgement, or follow some basic precautions:
1) You shouldn't be wiping partitions unless you are completely aware of what it means and what the results will be. The "Advanced" wipe section is called that for a reason, avoid using those options if you don't fully understand them. It says right on the default Wipe screen that the default wipe (user data, cache and Dalvik - leaves internal storage untouched) is the only wipe that is needed most of the time. Again, it says that for a reason, and you chose to ignore it.
2) Copy backups onto your computer, to avoid such situations

---

HI,
Thanks for the help and agree it was my mistake of deleting the backup.
I tried your suggestion. However, the RUU updater just frozen at "Sending 0/6" on my PC. And on the device it stays on the "HTC" black screen itself and no progress shown.
Steps I did:
1. Reclocked the boot loader using " Fastboot oem lock"
2. Rebooted the device in Fastboot USB
3. Ran the given RUU from my PC and followed the onscreen options.
4. It just stays there in the same stage of Sending 0/6 in my pc for more than 2 hours
5. Device is "HTC" Black screen
Am i making any mistake?
Thank you,
Selva
redpoint73 said:
Your firmware is outdated (hboot, radio, etc.) , and does not support any of the current custom ROMs. Broken WiFi is a known result of firmware mismatch; and the boot loops is likely due to the same reason.
Similarly, unless you flashed any but the oldest stock ROMs (1.58.502) you will suffer from the same firmware mismatch issue.
AT&T M8 won't OTA update since you are outside the US and not on the AT&T network (this is a AT&T specific complication).
I would advise to backup your personal data (your phone will be wiped), relock your bootloader (command: fastboot oem lock) then run the 4.28.502.1 RUU here:
The RUU will update your firmware. From there, you can unlock the bootloader again via , flash current version TWRP 2.8.7, then flash a current Lollipop custom ROM of your choice.
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
This has nothing to do with luck. This is a failure to use good judgement, or follow some basic precautions:
1) You shouldn't be wiping partitions unless you are completely aware of what it means and what the results will be. The "Advanced" wipe section is called that for a reason, avoid using those options if you don't fully understand them. It says right on the default Wipe screen that the default wipe (user data, cache and Dalvik - leaves internal storage untouched) is the only wipe that is needed most of the time. Again, it says that for a reason, and you chose to ignore it.
2) Copy backups onto your computer, to avoid such situations
Click to expand...
Click to collapse

---

selva_rag said:
HI,
Thanks for the help and agree it was my mistake of deleting the backup.
I tried your suggestion. However, the RUU updater just frozen at "Sending 0/6" on my PC. And on the device it stays on the "HTC" black screen itself and no progress shown.
Click to expand...
Click to collapse
At your own risk, you can try to disconnect the phone, or otherwise kill the RUU. I know it sounds scary, but its not uncommon for the RUU to stall out, then run correctly when you try again. But again, killing the RUU process has its risks; and I won't take any responsibility for any damage that may occur. Although is most likely fine, since its just stuck at "sending" not actually gotten to installing anything; plus it apparently hasn't even started "sending".
What Windows version? Win10 has been reported to be very problematic. I don't know if anyone has even gotten an RUU to run on Win10.

---

I am using windows 10.
Anyhow, I killed it and got back into fastboot. This time i going to try in Windows 7 PC.
When i rebooted the Devide, it showed ***Security Warning***. But when i rebooted the device, it just gone.
Let me try and update you. Thanks again.
redpoint73 said:
At your own risk, you can try to disconnect the phone, or otherwise kill the RUU. I know it sounds scary, but its not uncommon for the RUU to stall out, then run correctly when you try again. But again, killing the RUU process has its risks; and I won't take any responsibility for any damage that may occur. Although is most likely fine, since its just stuck at "sending" not actually gotten to installing anything; plus it apparently hasn't even started "sending".
What Windows version? Win10 has been reported to be very problematic. I don't know if anyone has even gotten an RUU to run on Win10.
Click to expand...
Click to collapse

---

selva_rag said:
I am using windows 10.
Anyhow, I killed it and got back into fastboot. This time i going to try in Windows 7 PC.
Click to expand...
Click to collapse
That would be my recommendation. Good luck!

---

I tried to run in the windows 7 several times. However, the Exe file is not moving after the first screen (After i agree to the terms & condition). Attmpted to run in the compatibility mode...still it is not working.
I checked in the RUU log and it is as below. Also, i copied the ROM.ZIP to my downloads folder. Is it possible to flash this ROM.ZIP manually?
----------------------------------------------------------------
<LOG>
<T223155><INFO><VERSION>2.0.16.2014</VERSION></INFO></T223155>
<T223155><INFO>start read zip</INFO></T223155>
<T223155><INFO>T
</INFO></T223155>
<T223155><INFO>Finish read zip.</INFO></T223155>
<T223155><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T223155>
<T223204><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T223204>
<T223204><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223204>
<T223204><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223204>
<T223205><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223205>
<T223205><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223205>
<T223206><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223206>
<T223206><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223206>
<T223206><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223206>
<T223207><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223207>
<T223207><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223207>
<T223208><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223208>
<T223208><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223208>
<T223209><DEBUG><OUT>boot-mode: FASTBOOTExecution time is 56(ms)</OUT>
</DEBUG></T223209>
<T223209><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223209>
<T223209><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223209>
<T223210><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223210>
<T223210><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223210>
<T223211><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223211>
<T223211><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223211>
<T223211><DEBUG><OUT>boot-mode: FASTBOOTExecution time is 83(ms)</OUT>
</DEBUG></T223211>
<T223211><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar battery-status</CMD>
</DEBUG></T223211>
<T223212><DEBUG><OUT>battery-status: goodExecution time is 4(ms)</OUT>
</DEBUG></T223212>
<T223212><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T223212>
<T223212><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223212>
<T223212><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223212>
<T223213><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223213>
<T223213><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223213>
<T223214><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223214>
<T223214><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223214>
<T223214><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223214>
<T223215><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223215>
<T223215><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223215>
<T223216><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223216>
<T223216><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223216>
<T223217><DEBUG><OUT>boot-mode: FASTBOOTExecution time is 186(ms)</OUT>
</DEBUG></T223217>
<T223217><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar version-main</CMD>
</DEBUG></T223217>
<T223218><DEBUG><OUT>version-main: Execution time is 5(ms)</OUT>
</DEBUG></T223218>
<T223249><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T223249>
<T223249><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223249>
<T223249><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223249>
<T223249><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223249>
<T223249><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223249>
<T223250><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223250>
<T223250><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223250>
<T223250><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223250>
<T223252><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223252>
<T223252><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223252>
<T223252><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223252>
<T223252><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223252>
<T223253><DEBUG><OUT>boot-mode: FASTBOOTExecution time is 62(ms)</OUT>
</DEBUG></T223253>
<T223253><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar version-main</CMD>
</DEBUG></T223253>
<T223254><DEBUG><OUT>version-main: Execution time is 4(ms)</OUT>
</DEBUG></T223254>
<T223254><DEBUG>[ComparisonDlg][_initData()]get rom version
</DEBUG></T223254>
<T223254><DEBUG>[getRomVersion] +++
</DEBUG></T223254>
<T223254><DEBUG>[_getRomVersion] +++
</DEBUG></T223254>
<T223254><DEBUG>[_getRomVersion] single rom, fopen rom.zip
</DEBUG></T223254>
<T223303><DEBUG>[CAruRomHandler::CheckTheFirstZipEncrypted] The first.zip is encrypted!
</DEBUG></T223303>
<T223303><DEBUG>This is NOT a combined ROM, use the original method to get the ROM version.
</DEBUG></T223303>
<T223303><DEBUG>[CAruRomHandler::_getRomVersion] Large and signed rom
</DEBUG></T223303>
<T223303><DEBUG>[_getRomVersion] (Encrypted) Main version: 4.28.502.1
</DEBUG></T223303>
<T223303><DEBUG>[_getRomVersion] ---
</DEBUG></T223303>
<T223303><DEBUG>[getRomVersion] ROM Ver: 4.28.502.1
</DEBUG></T223303>
<T223303><DEBUG>[getRomVersion] ---
</DEBUG></T223303>
<T223327><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T223327>
<T223327><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T223327>
<T223327><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T223327>
<T223327><DEBUG>[getImageCount] Large and signed rom
</DEBUG></T223327>
<T223327><DEBUG>getImageCount, nHR: 24
</DEBUG></T223327>
<T223327><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223327>
<T223327><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223327>
<T223327><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223327>
<T223327><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223327>
<T223329><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223329>
<T223329><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223329>
<T223329><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223329>
<T223329><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223329>
<T223330><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223330>
<T223330><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223330>
<T223331><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223331>
<T223331><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223331>
<T223332><DEBUG><OUT>boot-mode: FASTBOOTExecution time is 138(ms)</OUT>
</DEBUG></T223332>
<T223332><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX oem rebootRUU</CMD>
</DEBUG></T223332>
<T223332><DEBUG><OUT>... (bootloader) Start Verify: 3OKAYExecution time is 19(ms)</OUT>
</DEBUG></T223332>
<T223332><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223332>
<T223332><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223332>
<T223333><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223333>
<T223333><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223333>
<T223334><DEBUG><OUT />
</DEBUG></T223334>
<T223335><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223335>
<T223335><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223335>
<T223336><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223336>
<T223336><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223336>
<T223337><DEBUG><OUT />
</DEBUG></T223337>
<T223337><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223337>
<T223337><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223337>
<T223338><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223338>
<T223338><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223338>
<T223339><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223339>
<T223339><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223339>
<T223340><DEBUG><OUT>boot-mode: RUUExecution time is 11(ms)</OUT>
</DEBUG></T223340>
<T223340><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX erase cache</CMD>
</DEBUG></T223340>
<T223341><DEBUG><OUT>erasing 'cache'... OKAYExecution time is 50(ms)</OUT>
</DEBUG></T223341>
<T223341><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T223341>
<T223341><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T223341>
<T223341><DEBUG>[getImageCount] Large and signed rom
</DEBUG></T223341>
<T223341><DEBUG>getImageCount, nHR: 24
</DEBUG></T223341>
<T223341><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX -d flash zip C:\Users\Niru\AppData\Local\Temp\{1CD2F576-83BE-4A6B-9BFE-6C43DF2AD8E6}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T223341>
----------------------------------------------------------------
redpoint73 said:
That would be my recommendation. Good luck!
Click to expand...
Click to collapse

---

selva_rag said:
I tried to run in the windows 7 several times. However, the Exe file is not moving after the first screen (After i agree to the terms & condition). Attmpted to run in the compatibility mode...still it is not working.
Click to expand...
Click to collapse
Hmmm, I've seen this issue repoorted several times for Win10 (maybe Win8) but don't know if I've seen it happen on Win7.
Do you have USB 3.0 on your ports? This has also been known to not play well with the RUU.
selva_rag said:
Also, i copied the ROM.ZIP to my downloads folder. Is it possible to flash this ROM.ZIP manually?
Click to expand...
Click to collapse
From what has been posted on here, yes. I've never done it myself.
I think you need to rename the file 0P6BIMG.zip and put it on the top directory (not in a folder) of internal storage.

---

Also, I believe the phone's identifier (FA...) after each line "fastboot devices" in the log you posted, is your phone's serial number.
So you should delete those.

---

redpoint73 said:
Also, I believe the phone's identifier (FA...) after each line "fastboot devices" in the log you posted, is your phone's serial number.
So you should delete those.
Click to expand...
Click to collapse
Hi,
Thank you so much for your help. I think the problem is with the RUU file itself. I received a new version of the RUU file from my friend in US. It worked fine in Windows 10 without modifying anything. Now my phone is back with Stock 5.0.1.
Appreciate all your help.

---

selva_rag said:
Thank you so much for your help.
Click to expand...
Click to collapse
No problem, and there is a button for that!