Develop Bugs

[Q] Dsire HD Boot-Loop S-ON

My HTC Desire HD has developed the dreaded Boot Loop. Suddenly went this way whilst on charge in car.
I can get into HBoot - USB and Fastboot - USB menus, but if I select Recovery, it goes back into boot loop.
I can't see the phone on my laptop but can see my HD card when attached in a holder.
The following info is visible:
ACE PUT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011, 19:06:24
I am not a developer, but with detailed instructions, I did manage to wipe my other phone and install a new RUU. Trouble is that I am in a dodgy reception area and that phone gets no signal here, so I'm dependent upon getting this one sorted.
Could any considerate chap out there help me, without using shorthand terms like "just flash xxx in yyy mode and then zzz using this link, which turns out to be dead. I have searched high and low, but the S-ON designation means, I understand, that "easy" options are off. Of course, I cannot enable USB debugging, or enable connection to PC as I can't complete the boot process.
I'll be very grateful for any help.

Did you relock your boot loader?

Hook up your device in Fastboot and run last official gingerbread update(2.3.5) from pc.
***RUU selection goes to the carrier that device came with. I hope these covers x > y > z

marknoll said:
Did you relock your boot loader?
Click to expand...
Click to collapse
This is an untouched phone.
Hook up your device in Fastboot and run last official gingerbread update(2.3.5) from pc.
Click to expand...
Click to collapse
I can't see my PC when USB'd to phone. Could I put it on the SD card, which I can see when in a USB holder, with any hope that it would work from there when replaced in phone?

Install min adb and fastboot. Run it and install it then plug in your phone. Let PC recognize it. Then open a cmd and type fastboot getvar all

marknoll said:
Install min adb and fastboot. Run it and install it then plug in your phone. Let PC recognize it. Then open a cmd and type fastboot getvar all
Click to expand...
Click to collapse
Thanks for that.....Just returned completely knackered from windsurfing so will have a go tomorrow when I'm less likely to foul it up!

marknoll said:
Install min adb and fastboot. Run it and install it then plug in your phone. Let PC recognize it. Then open a cmd and type fastboot getvar all
Click to expand...
Click to collapse
OK. done that and this is the result
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.12.405.1
(bootloader) serialno:
(bootloader) imei: 352668041228402
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4199mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.037s
"Hook up your device in Fastboot and run last official gingerbread update(2.3.5) from pc"
I have downloaded this gingerbread update but have no idea how to run it from my pc. I have put it in the root directory but it has no exe file and the Cmd prompt doesn't seem to help. I still can't see the phone in explorer.
Probably a simple process but I have no previous experience to guide me.

You have latest hboot
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
Run the update that has baseband 12.69a. You're not supercid nor unlocked BL nor s offed.. This should help. Make sure u back up all u need as this will wipe the device with a clean slate.
---------- Post added at 01:51 PM ---------- Previous post was at 01:44 PM ----------
http://forum.xda-developers.com/showthread.php?t=2635479

marknoll said:
You have latest hboot
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
Run the update that has baseband 12.69a. You're not supercid nor unlocked BL nor s offed.. This should help. Make sure u back up all u need as this will wipe the device with a clean slate.
---------- Post added at 01:51 PM ---------- Previous post was at 01:44 PM ----------
http://forum.xda-developers.com/showthread.php?t=2635479
Click to expand...
Click to collapse
Sorry. I understand S - off but that's all. I'm not a developer. Just a fairly computer literate Desire HD user with a problem!
I see the term baseband in your message and in my getvar report, but have no idea what it is. Could you be kind and give me a link to what I need to use, and explain where the .exe file is or whatever I need to run it? Much appreciated.

Don't panic...
Quick notes and probably last reply from me, I'll try to cover every aspect of your problem.
-RUU is a Stock ROM which should be in .exe format to run through pc while device is connected.
-To play around with device,doesn't necessary to be a developer.
-I'm also not a dev but if you spend more time here,you'll learn a lot.
So cut the crap and head over your issue.
now i don't know which carrier your device is locked Or from where you bought the device. But RUU should be from that carrier origin or at least country origin.
Check here: http://www.shipped-roms.com/index.php?category=android&model=Ace
These are stock rom for our device(Ace-code name of Desire HD/Inspire 4g)
Choose one with ending of .exe and according to your carrier or country from where you bought it.
As earlier you've mentioned that you may able to get into Fastboot,then put your device in fastboot mode and it should be in Hboot USB ,now to go into such way you need to connect your device through USB and wait a second or so then press power button and it will show you in RED color.
After that run RUU file through pc by double clicking on file. It will prompt you that it will upgrade your device hboot version,go ahead and click next. and let the process complete. But before all make sure your device has more than 30% of battery. If you encountered any problem,then head over to htc.com and ask for help regarding it. I'm just saying because your device is in Stock mode,nothing has been changed according their standard. Or you may look at here in forum regarding error that you get while running RUU.
If you successfully go through all steps,then your device probably back to life again,unless there isn't any hardware issue. Once you deal with this you may now able to unlock bootloader and root your device. But that's only when you actually done with above mentioned steps.
If some point you don't understand what i'm saying,then from my side i'm SORRY. But you've to spent more time with your device in order to learn it properly.

dr.patron99 said:
Quick notes and probably last reply from me, I'll try to cover every aspect of your problem.
-RUU is a Stock ROM which should be in .exe format to run through pc while device is connected.
-To play around with device,doesn't necessary to be a developer.
-I'm also not a dev but if you spend more time here,you'll learn a lot.
So cut the crap and head over your issue.
now i don't know which carrier your device is locked Or from where you bought the device. But RUU should be from that carrier origin or at least country origin.
Check here: http://www.shipped-roms.com/index.php?category=android&model=Ace
These are stock rom for our device(Ace-code name of Desire HD/Inspire 4g)
Choose one with ending of .exe and according to your carrier or country from where you bought it.
As earlier you've mentioned that you may able to get into Fastboot,then put your device in fastboot mode and it should be in Hboot USB ,now to go into such way you need to connect your device through USB and wait a second or so then press power button and it will show you in RED color.
After that run RUU file through pc by double clicking on file. It will prompt you that it will upgrade your device hboot version,go ahead and click next. and let the process complete. But before all make sure your device has more than 30% of battery. If you encountered any problem,then head over to htc.com and ask for help regarding it. I'm just saying because your device is in Stock mode,nothing has been changed according their standard. Or you may look at here in forum regarding error that you get while running RUU.
If you successfully go through all steps,then your device probably back to life again,unless there isn't any hardware issue. Once you deal with this you may now able to unlock bootloader and root your device. But that's only when you actually done with above mentioned steps.
If some point you don't understand what i'm saying,then from my side i'm SORRY. But you've to spent more time with your device in order to learn it properly.
Click to expand...
Click to collapse
Thanks for your forbearance. My phone is PAYG so not tied to anyone. Thank you for the link. I went searching round the forum and was trying something that had no .exe, so couldn't fathom where to go. I'm quite happy if I can find that, and even happier if it fixes the problem.
With considerate help, I rooted another phone so am confident to push the margins as you implore me to do. I'll get on with it!
Thanks again

Androidruu.com. I already told ya
---------- Post added at 01:09 AM ---------- Previous post was at 01:07 AM ----------
marknoll said:
You have latest hboot
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
Run the update that has baseband 12.69a. You're not supercid nor unlocked BL nor s offed.. This should help. Make sure u back up all u need as this will wipe the device with a clean slate.
---------- Post added at 01:51 PM ---------- Previous post was at 01:44 PM ----------
http://forum.xda-developers.com/showthread.php?t=2635479
Click to expand...
Click to collapse
The ruu is in the second post... 3.20xxxx. That's what you need
---------- Post added at 01:13 AM ---------- Previous post was at 01:09 AM ----------
Baseband explanation.
http://www.droidforums.net/threads/what-is-a-baseband.36959/

dr.patron99 said:
Quick notes and probably last reply from me, I'll try to cover every aspect of your problem.
-RUU is a Stock ROM which should be in .exe format to run through pc while device is connected.
-To play around with device,doesn't necessary to be a developer.
-I'm also not a dev but if you spend more time here,you'll learn a lot.
So cut the crap and head over your issue.
now i don't know which carrier your device is locked Or from where you bought the device. But RUU should be from that carrier origin or at least country origin.
Check here: http://www.shipped-roms.com/index.php?category=android&model=Ace
These are stock rom for our device(Ace-code name of Desire HD/Inspire 4g)
Choose one with ending of .exe and according to your carrier or country from where you bought it.
As earlier you've mentioned that you may able to get into Fastboot,then put your device in fastboot mode and it should be in Hboot USB ,now to go into such way you need to connect your device through USB and wait a second or so then press power button and it will show you in RED color.
After that run RUU file through pc by double clicking on file. It will prompt you that it will upgrade your device hboot version,go ahead and click next. and let the process complete. But before all make sure your device has more than 30% of battery. If you encountered any problem,then head over to htc.com and ask for help regarding it. I'm just saying because your device is in Stock mode,nothing has been changed according their standard. Or you may look at here in forum regarding error that you get while running RUU.
If you successfully go through all steps,then your device probably back to life again,unless there isn't any hardware issue. Once you deal with this you may now able to unlock bootloader and root your device. But that's only when you actually done with above mentioned steps.
If some point you don't understand what i'm saying,then from my side i'm SORRY. But you've to spent more time with your device in order to learn it properly.
Click to expand...
Click to collapse
Your instructions were very welcome and gave me the knowledge I needed to proceed, paricularly a sourcs of .exe RUUs rather than the .zip I had found that had no .exe file within.
According to the on screen info, I have installed the Rom I selected successfully. Unfortunately the boot loop remains and it still goes into that when I click on recovery. Seems that this phone is probably cooked.

Whiskeymac said:
Your instructions were very welcome and gave me the knowledge I needed to proceed, paricularly a sourcs of .exe RUUs rather than the .zip I had found that had no .exe file within.
According to the on screen info, I have installed the Rom I selected successfully. Unfortunately the boot loop remains and it still goes into that when I click on recovery. Seems that this phone is probably cooked.
Click to expand...
Click to collapse
Okie. Good sign,that RUU successfully installed. Now time for next step.
-Do you able to boot your device? Or still has bootloop after installing appropriate RUU.
-If you can go into bootloader then just show everything what's mentioned there from top to bottom( hboot version,radio version etc. everything)
Well if stock recovery doesn't work then will try to Unlocked the bootloader and make it Flash custom recovery then.

Right, back at the coal face:
dr.patron99 said:
Okie. Good sign,that RUU successfully installed. Now time for next step.
-Do you able to boot your device? Or still has bootloop after installing appropriate RUU.
-If you can go into bootloader then just show everything what's mentioned there from top to bottom( hboot version,radio version etc. everything)
Well if stock recovery doesn't work then will try to Unlocked the bootloader and make it Flash custom recovery then.
Click to expand...
Click to collapse
It's still not booting. Just loops with a buzz every 10 secs or so, with a white screen and green HTC. Same when I hit recovery. When I plug it switched off into the PC, it switches on by itself into the boot loop.
Bootloader info:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011,19:06:24
RUU that I think I installed: RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe

Whiskeymac said:
Right, back at the coal face:
It's still not booting. Just loops with a buzz every 10 secs or so, with a white screen and green HTC. Same when I hit recovery. When I plug it switched off into the PC, it switches on by itself into the boot loop.
Bootloader info:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011,19:06:24
RUU that I think I installed: RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe
Click to expand...
Click to collapse
Get yourself a New Phone. I believe it's a hardware failure. Or if you want to play around more with it,nothing gonna harm it much since device doesn't know when should boot properly. So i advise you either you unlocked the bootloader! not by htcdev but using chinese tool. It does same thing unless if you want to go through long process of typing and creating account sort of troublesome method.
First of all, you need to use Chrome Browser to translate page automatically unless you chinese. then go to www.mgyun.com , Once site loads up completely first thing you'll notice a white box with monitor sign in circle with version 3.4.8, download and install it in your pc. Once that done. Connect your device in what ever stat it is. Or try putting it in bootloader mode,since it doesn't reboot on bootloader. It should detect your device if you have HTC Sync installed.
Once it gets detected,in that program go to settings > look for lock sign > click on it. It will load another window hit yes or follow on screen instructions.After a minute or so your device should reboot with prompt message that you're about to unlock bootloader. Use volume down to select and Power button to confirm. After that it will reboot again. And that's it later on you may go to bootloader you'll see ***UNLOCKED****
Well, If your device let's complete whole process then there is still some life left. I'm saying it because i do have same issue as yours. And solution to it only by replacing motherboard of the device. Which means time to buy a new device!

Well it can do no harm to try this as you say. I am not very impressed with the reliability of this model, or at least its robustness. I still have my original HD. That works, but HTC say it has "something wrong with the motherboard and will pack up in time". This after I sent it back when it was behaving like a mad thing, carrying out all sorts of actions without me touching it.. After hours and weeks rooting it from zero knowledge, and I mean absolute zero, the same problem was there. Only when I changed the charger which was plugged in, did it function normally. The other phone, the one with the boot loop, I bought second hand, when HTC said the first one needed a new motherboard. I told them to destroy the phone, not send it back for another wad of money. They sent it back for free. It works but does not receive weak signals as well as the replacement, and I'm in a weak signal area which means it doesn't work at home at all.
This boot loop problem started when, once again, it was being float charged in my car. I'm coming to the conclusion that they just don't like being on charge for a long time. Also possible that it may have overheated by being in the sun whilst charging.
Another thing I've discovered is that it starts the boot loop also when it is plugged into a charger even when the phone was switched off.
Anyway, thanks for this latest advice, I'm just about to drive across England to pick up a puppy and will be busy getting him settled in at home for a few days, so the phone will have wait until I have the time to focus properly on what I'm doing. I'll report back when I've ploughed through that, downloaded Chrome etc. I think, as you say, it's time to buy a new phone, but I'll still give it a bit of last ditch resuscitation in the hope that I can breath a bit of life back into it.
Thanks again. WM
dr.patron99 said:
Get yourself a New Phone. I believe it's a hardware failure. Or if you want to play around more with it,nothing gonna harm it much since device doesn't know when should boot properly. So i advise you either you unlocked the bootloader! not by htcdev but using chinese tool. It does same thing unless if you want to go through long process of typing and creating account sort of troublesome method.
First of all, you need to use Chrome Browser to translate page automatically unless you chinese. then go to www.mgyun.com , Once site loads up completely first thing you'll notice a white box with monitor sign in circle with version 3.4.8, download and install it in your pc. Once that done. Connect your device in what ever stat it is. Or try putting it in bootloader mode,since it doesn't reboot on bootloader. It should detect your device if you have HTC Sync installed.
Once it gets detected,in that program go to settings > look for lock sign > click on it. It will load another window hit yes or follow on screen instructions.After a minute or so your device should reboot with prompt message that you're about to unlock bootloader. Use volume down to select and Power button to confirm. After that it will reboot again. And that's it later on you may go to bootloader you'll see ***UNLOCKED****
Well, If your device let's complete whole process then there is still some life left. I'm saying it because i do have same issue as yours. And solution to it only by replacing motherboard of the device. Which means time to buy a new device!
Click to expand...
Click to collapse

[Q] Lost, confused and in need of HELP! Please...

So I have been out of the XDA loop for a while as I had to send my shiny rooted Verizon HTC One (m7) back for warranty exchange because the sound card went out. The phone they replaced it with was refurbished and already was running KK 4.4. so I was stuck with the POS, until recently, when it took the sense 6 update all by itself, and broke itself!
Celebrate!!! Because they replaced that with a NEW HTC One (m7) that is fully stock, but running all OG software, see below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0731
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: X
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97af273845
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
However, now that I have been attempting to get my root back (I've missed it sooo much!!!!) I have realized I may have celebrated too soon.
SO my question is: Even though this is the first release version on this phone variant for Verizon (still not able to HTCdev unlock), did they patch the exploits to perm Root, unlock bootloader, S-off all that? Or is it just on the much later versions of the Android OS?
I apologize if this has been discussed elsewhere, but I simply have spent days searching the forums and internet looking for an answer to this, and simply cannot find one. :crying:
I have tried both firewater (weaksauce gains temp root fine, and the temp root method gains root just fine) but when I run firewater it hangs, and rumrunner, which seems like its running just fine, then ends up saying something along the lines of "Failed.....F*&% It!" and begins to run lines and lines of dots. Which I know usually is related to a security or firewall issue, but I have made sure multiple times all of that is absolutely off on my PC, and I have NO android related software (besides adb & fastboot) installed on my PC.
The only other thing I can think of to do is to roll back my HTC drivers to those which would have been the latest when 4.2.2 sense 5 HBoot 1.54 etc.etc. came out, and see if that makes a difference, but I cannot find info as to which drivers those would be either!
So I turn to the trusted community for some help and hopefully answers.
Thanks guys, pre-help, it's always nice to know I can ask!
***********************
UPDATE
***********************
I thought I would run rumrunner again to just give people an exact copy of what it says, every time I run it:
----------------------------------------------------------------------------------------------------------------------------
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (15/120)
Waiting
Test 2: Booting device
Waiting for ADB (29/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: [email protected] it
.....................
----------------------------------------------------------------------------------------------------------------------------
Also, forgot to mention, that since I can use firewater with the temproot method partially sucessfully, I now have a bootloader that is still locked and S-on, but has a ***Tampered*** flag at the top in black.

Try running the 1.10.605.10 signed ruu from the below thread.
http://forum.xda-developers.com/showthread.php?t=2485319
After you do that try rumrunner again. Ensure all firewalls are off (even windows firewall) and any antivirus is disabled (anti malware also). Be sure you download the correct version of rumrunner.
Sent from my One using XDA Free mobile app

Uzephi said:
Try running the 1.10.605.10 signed ruu from the below thread.
http://forum.xda-developers.com/showthread.php?t=2485319
After you do that try rumrunner again. Ensure all firewalls are off (even windows firewall) and any antivirus is disabled (anti malware also). Be sure you download the correct version of rumrunner.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Ok I will try that.
Would I run it in bootloader RUU mode as if I were S-off and Unlocked or just install like an .apk?
Thanks for the quick response! I will let you know how it all turns out

xenacick said:
Ok I will try that.
Would I run it in bootloader RUU mode as if I were S-off and Unlocked or just install like an .apk?
Thanks for the quick response! I will let you know how it all turns out
Click to expand...
Click to collapse
Just like if you were s-off.
"fastboot oem rebootRUU" be sure to type exactly like that. Caps matter when running oem fastboot commands.
Reason why I suggest running the signed ruu (signed ruus work whilst s-on) is firewater or weaksauce could have modified something that made rumrunner fail. "Tampered" means something in /system or deeper got modified while s-on.
Sent from my One using XDA Free mobile app

Uzephi said:
Just like if you were s-off.
"fastboot oem rebootRUU" be sure to type exactly like that. Caps matter when running oem fastboot commands.
Reason why I suggest running the signed ruu (signed ruus work whilst s-on) is firewater or weaksauce could have modified something that made rumrunner fail. "Tampered" means something in /system or deeper got modified while s-on.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
I just wanted to be sure I was going to flash it in the right area
Doing it right now, crossing fingers!
Thanks!

Whelp....
That did the exact same thing. No go
I'm wondering if it has to do with something with when it gets to this part of the process-
after it says:
Device detected.....................
[-------------------------------------------------**********] <-------------
Where the asterisks turn into underscores/dashes is it supposed to do something else after this? Because when it finishes turning all the asterisks it goes back to this dialogue:
Rebooting into bootloader (again)
Waiting for fastboot (7/120) <----------- Hangs on count 7 for about 60-90 seconds before moving on to the next line-
FATAL: [email protected] it

xenacick said:
Whelp....
That did the exact same thing. No go
I'm wondering if it has to do with something with when it gets to this part of the process-
after it says:
Device detected.....................
[-------------------------------------------------**********] <-------------
Where the asterisks turn into underscores/dashes is it supposed to do something else after this? Because when it finishes turning all the asterisks it goes back to this dialogue:
Rebooting into bootloader (again)
Waiting for fastboot (7/120) <----------- Hangs on count 7 for about 60-90 seconds before moving on to the next line-
FATAL: [email protected] it
Click to expand...
Click to collapse
I know this may seems like a silly troubleshooting question: are you using a USB 2.0 port and stock USB cable? USB 3.0 can cause issues.
Sent from my One using XDA Free mobile app

Uzephi said:
I know this may seems like a silly troubleshooting question: are you using a USB 2.0 port and stock USB cable? USB 3.0 can cause issues.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Nope, I've seen enough posts on this site to know why that question is warranted....
However, I'm all good in both ways.
Have used, at this point, all 3 USB ports I have available to me on my laptop, have tried both HTC OEM cables, have uninstalled/installed outdated/current drivers, and made doubly sure I have no traces of any HTC Sync, PDANet, or anything else phone=software related where it may enable talking during the process. I'm running soju.exe as admin, with all security on my system OFF, firewall, anti-malware, even am using a guest network I created off my secured network just in case.
Probably missed other things too....

xenacick said:
Nope, I've seen enough posts on this site to know why that question is warranted....
However, I'm all good in both ways.
Have used, at this point, all 3 USB ports I have available to me on my laptop, have tried both HTC OEM cables, have uninstalled/installed outdated/current drivers, and made doubly sure I have no traces of any HTC Sync, PDANet, or anything else phone=software related where it may enable talking during the process. I'm running soju.exe as admin, with all security on my system OFF, firewall, anti-malware, even am using a guest network I created off my secured network just in case.
Probably missed other things too....
Click to expand...
Click to collapse
"Support
#rumrunners on andirc or freenode
Please don't clutter this thread with support issues, it's MUCH easier to help on IRC."
From the rumrunner thread.
Few other things to ensure:
Fast boot disabled. USB debugging enabled.
Other than that, I suggest going to their support on andirc or freenode, because I am lost on what is causing the issue
Sent from my One using XDA Free mobile app

Make sure this is unchecked:
Settings > security > Device administrator > Android Device Manager

santod040 said:
Make sure this is unchecked:
Settings > security > Device administrator > Android Device Manager
Click to expand...
Click to collapse
I did have the device manager, de-selected...
Well just thought I would update you guys who tried to help me :*(
After running rumrunner again, and again, and again trying different settings with regards to different HTC cords, USB ports, re-downloads, reinstall of adb, fastboot, and HTC drivers, and a few others, I'm still stuck.
At this point I have also had to flash the stock signed RUU twice, again, as rumrunner get's somewhere because it will sometimes during the rebooting check start process of sojo.exe get to the fastboot screen and if I glance over, it will have the black ***tampered*** flag!
I mean considering this is so OG, I am startled at how much trouble it's been giving me. When I rooted my first HTC One (m7) still Verizon, I got it to go S-off and unlocked first attempt.
So I have considered trying something new, and wanted to run it by you to see what you thought.
What would potentially happen if I downloaded the signed stock RUU for 2.10.605.1 and tried rumunner again?? Would my current config even allow me to do so? Thoughts? Related ideas?
THANKS!

xenacick said:
I did have the device manager, de-selected...
Well just thought I would update you guys who tried to help me :*(
After running rumrunner again, and again, and again trying different settings with regards to different HTC cords, USB ports, re-downloads, reinstall of adb, fastboot, and HTC drivers, and a few others, I'm still stuck.
At this point I have also had to flash the stock signed RUU twice, again, as rumrunner get's somewhere because it will sometimes during the rebooting check start process of sojo.exe get to the fastboot screen and if I glance over, it will have the black ***tampered*** flag!
I mean considering this is so OG, I am startled at how much trouble it's been giving me. When I rooted my first HTC One (m7) still Verizon, I got it to go S-off and unlocked first attempt.
So I have considered trying something new, and wanted to run it by you to see what you thought.
What would potentially happen if I downloaded the signed stock RUU for 2.10.605.1 and tried rumunner again?? Would my current config even allow me to do so? Thoughts? Related ideas?
THANKS!
Click to expand...
Click to collapse
I think 2.10 is firewater and weaksauce.
Edit- ...... You are right clicking and running as admin, right? Also, you are running win7?
Sent from my HTC6500LVW using XDA Free mobile app

Uzephi said:
I think 2.10 is firewater and weaksauce.
Edit- ...... You are right clicking and running as admin, right? Also, you are running win7?
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Well I have tried Firewater/Weaksauce & Firewater/TempRoot methods too, I gain temp root no problem in either case, just can't get firewater to get anywhere, it hangs and hang and hangs, and I have to do a hard reboot to retry.
And,
Yep, running everything, every time as admin...and yes am on Windows 7 SP1, Home Premium.
So just to throw $H!T to the wall to see if it sticks, I have been throwing some of these ideas/questions around my head all day.
With regards to the OS version of windows, I do have firewall, defender, and anti-malware all OFF/disabled when I am make any attempt, but just in case have also added soju.exe to the allowed lists. With the exception of the newer Microsoft Security Essentials, as it's newish to me and I don't know how to add exceptions to it yet. I've just been turning it off.
Everything I can find about the point where it stops each time, say it's because of a security issue on the OS or network, anybody have ideas about any OTHER security type programs which may be running services in the background which may prevent the connection from being able to communicate each reboot?
Another thought I had was, would it be worth running it in compatibility mode for say XP SP2 along WITH the ADMIN permissions?
What about turning on network sharing (on the phone) to use the PC network connection for internet? My thinking being with the phone supplying the connection (with all the reboots and such), its causing some kind of hiccup because of reconnection timeout or something?
Lastly, I realized I hadn't asked probably one of the most obvious of questions, as I assumed the where. But I have been downloading and extracting the zipped package directly into my adb/fastboot folder. So when it runs, it does so from inside that environment, and I don't know if it would matter? Or even if the locale matters or not? Could it be the part of the problem too, having the other files in the zipped package extracted and in the same folder, along with the still zipped package when trying to run the exploit?
I appreciate your responses in advance! I feel like each day that passes I get another grey hair!
F#^$*(@)&*% VERIZON!!!!!
GURRRRRRR

Make an ubuntu Linux boot disc and run rumrunner using Linux.

disconnecktie said:
Make an ubuntu Linux boot disc and run rumrunner using Linux.
Click to expand...
Click to collapse
disconnecktie,
I would be fine and willing to try this, however I have never attempted to run any Linux as an OS, HD or otherwise (as you suggest with a boot disc). Could you point me in the right direction on where to find a good tutorial on how to create and run such a disk? Also, which ubuntu Linux version would you suggest that would have the best chance of success alongside my HTC phone version and the Rumunner exploit?
Thanks in advance!!

The ubuntu website has all the info you need for making a boot disc. I personally use 14.04. You should only have to boot into ubuntu from the disc. I don't think you should have to take it much further than that. Put rumrunner on a usb drive or something and then follow the instructions for running it in Linux.
xenacick said:
disconnecktie,
I would be fine and willing to try this, however I have never attempted to run any Linux as an OS, HD or otherwise (as you suggest with a boot disc). Could you point me in the right direction on where to find a good tutorial on how to create and run such a disk? Also, which ubuntu Linux version would you suggest that would have the best chance of success alongside my HTC phone version and the Rumunner exploit?
Thanks in advance!!
Click to expand...
Click to collapse

disconnecktie said:
The ubuntu website has all the info you need for making a boot disc. I personally use 14.04. You should only have to boot into ubuntu from the disc. I don't think you should have to take it much further than that. Put rumrunner on a usb drive or something and then follow the instructions for running it in Linux.
Click to expand...
Click to collapse
Ok I will give it a try in the AM and update the thread on here after to let ya know how it went! ;P

This might be a long shot, but are you using a router that may have built in security? can you temporarily bypass your router and hook your PC straight into the modem?

xenacick said:
Ok I will give it a try in the AM and update the thread on here after to let ya know how it went! ;P
Click to expand...
Click to collapse
Any word on how this went? I just recently got around to trying to get S-Off, and I'm in an extremely similar situation as you. I'm on 1.10.605.10 firmware, but rumrunner is failing in the same exact way as you and I've disabled and even uninstalled all antivirus/firewall software on my Windows 7 PC. I did try running the linux version of rumrunner using an Ubuntu boot disc/Live CD/whatever I made, but rumrunner still failed exactly the same way (i.e. "FATAL: [email protected] it" and then dots after the second "Waiting for fastboot"). Both adb and fastboot seem to be working because I can see my device with both the "adb devices" and "fastboot devices" commands. Just today I used weaksauce to gain root, but haven't yet tried firewater for S-Off. I'll try later tonight, but based on your post, I'm not feeling confident. If you figured it out, would appreciate it if you could post what worked for you.

Not to hijack the thread, but I was able to finally achieve S-Off, unlocked bootloader, the whole shebang, after running into similar walls as OP. Just thought I'd post my full efforts here if OP or anyone else comes looking for info.
As stated before, I was on some old software (kept declining software updates since I'd get around to S-Off/unlock/etc. sooner or later). I was on the 1.10.605.10 firmware. Since rumrunner wasn't working for me, I did the risky thing and took a software update, hoping it would be an incremental update and not a huge rollup of everything VZW has pushed so far, so I could try a different rumrunner version or maybe firewater. I was right, and I ended up on the 1.10.605.15 firmware. So I tried the *.15 version of rumrunner. I did get a little further in the process (messages like "must ferment longer" and "skunky rum is nasty") but it still failed, giving a message about downloading the latest packages from www.rumrunner.us. Obviously, that was not helpful. Also, for some unknown reason, my PC was no longer letting me boot from CD/DVD, so I couldn't try it in linux under the *.15 firmware. As a last ditch effort, I rooted with weaksauce, and tried the firewater method based on a single post/suggestion I found digging through the rumrunner thread. Bingo! I confirmed unlocked and S-Off in hboot. Hope this helps OP or anyone else!

My phone is either in Safe Mode or in Bootloader plus buttons are bugged

My Android phone has always been working fine, it has no ROMs.
It is even not unlucked.
So suddenly my phone got in to a very weird state where the following problems occured.
- When I turn on my phone by holding the Power Button, it will go straight to Bootloader.
- When I turn on my phone by holding the Power Button + Volume Up, it will run in Safe Mode.
- There is no way for me to start my phone up normally.
- My Volume Down button stopped working.
- My Power button to select commands in bootloader doesn't work.
- In Bootloader my Volume Up button, acts as the Volume Down button. So it will scroll down.
- In Bootloader my Volume Down button does nothing at all.
- To Exit Bootloader I have to hold my Power Button for at least 10 seconds to shut off my phone.
- I can't Unluck my phone since I can't select the " Yes" option when it asks if I want to Unlock Bootloader.
All these problems occured at the same time.
I am not really experienced with ROMs and stuff and I tried several fixes from throughout the web, but nothing has worked for me so far.
I really hope someone can help me, because I can't live without my mobile.
And Safe mode is awful, since I can't use installed apps from the app store, only the pre-installed apps.
Cheers,
Joris
-Edit: HTC One M8_UL

I think you have a hardware fault, that is causing your vol down button to register as being pressed, when its not (or its physically stuck). This would explain booting to hboot and safe mode, as vol down is used for both (depending on the timing of when they are pressed) and the behavior when in bootloader.
What carrier version (CID) of the M* do you have?
Does the phone have any valid warranty?

redpoint73 said:
I think you have a hardware fault, that is causing your vol down button to register as being pressed, when its not (or its physically stuck). This would explain booting to hboot and safe mode, as vol down is used for both (depending on the timing of when they are pressed) and the behavior when in bootloader.
What carrier version (CID) of the M* do you have?
Does the phone have any valid warranty?
Click to expand...
Click to collapse
I am sorry, I am very new to this.
What is a carrier version (CID) ?
Do you mean M8_UL?
Edit: Found it : HTC_E11

I managed to get some info on the phone.
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main: 4.16.401.13
version-misc: PVT SHIP S-ON
serialno: ***********
imei: *************
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__E11
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f063fb42
hbootpreupdate: 11
gencheckpt: 0

Need to delete you IMEI and serial number from the above post. Those are personal data, which should never be posted online.
I asked if you still have a valid warranty, and you never answered.

redpoint73 said:
Need to delete you IMEI and serial number from the above post. Those are personal data, which should never be posted online.
I asked if you still have a valid warranty, and you never answered.
Click to expand...
Click to collapse
I am sorry, I do not have an insurance for it and no warranty.

jorissvd said:
I am sorry, I do not have an insurance for it and no warranty.
Click to expand...
Click to collapse
I'd suggest to see if there is an RUU for your CID, and and run it (backup your personal data before RUU, the phone will be wiped). The RUU will completely re-image the phone, and eliminate the possibility that a software issue is the cause of your problem (but I'm pretty sure its a hardware issue).
From there, you may want to take apart the casing, and see if you can "free" the vol button, clean the contacts, etc., as it may be physically stuck. I think I've seen at least a couple cases here of folks who were able to fix a stuck volume or power button this way. Although, be aware that taking this phone apart is not a trivial task; and its possible you may do more damage than good. So do the proper research, use your judgement (if its something that you can accomplish), and be very careful.
Aside from that, I'm not sure if there is much else that can be done.

redpoint73 said:
I'd suggest to see if there is an RUU for your CID, and and run it (backup your personal data before RUU, the phone will be wiped). The RUU will completely re-image the phone, and eliminate the possibility that a software issue is the cause of your problem (but I'm pretty sure its a hardware issue).
From there, you may want to take apart the casing, and see if you can "free" the vol button, clean the contacts, etc., as it may be physically stuck. Although, be aware that taking this phone apart is not a trivial task; and its possible you may do more damage than good. So do the proper research, use your judgement (if its something that you can accomplish), and be very careful.
Aside from that, I'm not sure if there is much else that can be done.
Click to expand...
Click to collapse
I have tried several times to use a RUU.
But in the setup it keeps Staying at Updating... Sending...
for hours and hours while it should only take 10 minutes.
I don't know what RUU is the correct one for my phone.

jorissvd said:
I have tried several times to use a RUU.
But in the setup it keeps Staying at Updating... Sending...
for hours and hours while it should only take 10 minutes.
I don't know what RUU is the correct one for my phone.
Click to expand...
Click to collapse
Try the RUU again. Getting stuck the first time is not unusual.
But, if you have Win10 or USB3.0 on your PC, you may need to try another computer.
Wrong RUU will give you an error message. Getting stuck sending is a connectivity issue.
What RUU did you try?

redpoint73 said:
Try the RUU again. Getting stuck the first time is not unusual.
But, if you have Win10 or USB3.0 on your PC, you may need to try another computer.
Wrong RUU will give you an error message. Getting stuck sending is a connectivity issue.
What RUU did you try?
Click to expand...
Click to collapse
I will try it again.
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed

Currently trying again.
Instead of (0/8)
It is now stuck at (1/8)
with the same " Updating... (1/8) Sending..." status

Uninstalled HTC Sync Manager, It seemed to get stuck everytime HTC Sync Manager popped up.
It is now updating my phone and I seem to be making alot of progress.
I will let you know the results.
Thank you in advance, this is already a huge step to figuring out the solution.

jorissvd said:
Uninstalled HTC Sync Manager, It seemed to get stuck everytime HTC Sync Manager popped up.
It is now updating my phone and I seem to be making alot of progress.
I will let you know the results.
Thank you in advance, this is already a huge step to figuring out the solution.
Click to expand...
Click to collapse
Sadly, this did not work.
My phone did reset, but it started in Safe Mode and rebooting it makes it go to bootloader with the same issues.
I am out of ideas.

HTC__E11 that's a Dutch CID. You should have 2 year manufacturer warranty, as its standard for all electrical equipment. I bet the phone isn't 2 years old yet as its been out since what ? April last year ?
I would take it to the seller/shop or even higher up.

jorissvd said:
I will try it again.
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
Click to expand...
Click to collapse
The main version (as shown in getvar output) ends in .13 and a higher (never) version than the RUU, which ends in .10
You can't run an older/lower number RUU ("downgrade") with s-on. You will fail version check.
But as I already mentioned, this probably is not the reason for the RUU stopping while sending. It would probably give you an error message. You have a general connectivity issue. But even if you solve that, this RUU will fail with an error message.

It is a hardware fault. Had in in a dual sim m8 and warranty covered it. The problem lies on the volume button/sd card reader flex but they won't replace it cuz its hidden under the LCD, so they replace they while LCD panel instead.
Στάλθηκε από το HTC One_M8 μου χρησιμοποιώντας Tapatalk

Tool to check for bad NAND/EMMC?

Hi!
Does anyone know about a tool to check (and maybe also fix) a bad NAND/EMMC? This is my story:
This Friday I was sitting in my couch and browsing the web on my M9 (HTC__Y13, Europe version) and suddenly it just reboots itself.
This is normal behavior (at least with my phone, happens now and then), but this time it just kept rebooting itself.
I can boot to FASTBOOT but not to "Download Mode" or "Recovery Mode". If I choose Download/Recovery-Mode, it starts to load but just to reboot itself
again.
Pressing VolUp+VolDwn+Pwr takes me to the FASTBOOT menu.
Choosing "Download Mode" takes me to a black screen with HTC logo in silver. After a couple of seconds, it reboots itself.
Choosing "Recovery Mode" takes me to a black screen with HTC logo in silver. After a couple of seconds it reboots itself.
Pressing VolDwn+Pwr takes me to a black screen with HTC logo in silver. After a couple of seconds, it reboots itself.
Trying to boot to RUU-mode (fastboot oem rebootRUU) gives me the same behavior.
S-ON: YES
Relocked: YES
Thanks in advance!
From getvar-command (looks pretty strange to me)
Code:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT**********
I modified the value on row "(bootloader) serialno:" for this post, value is proper.

I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like, from my sherlock skills, it may have an m8 software on there as the serial starts HT where as I'm sure m9's are FA..
Beamed in by telepathy.

shivadow said:
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like it may have been slowly dying over time.
If you live in the USA or taiwan, or have a warranty you can get a replacement from HTC free of charge.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you so much for your response!
As I suspected
Unfortunately I'm live (and has bought the phone) in Sweden, so I think an unlocked/relocked bootloader = f*cked. But I will contact HTC support anyway.

shivadow said:
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like, from my sherlock skills, it may have an m8 software on there as the serial starts HT where as I'm sure m9's are FA..
Beamed in by telepathy.
Click to expand...
Click to collapse
I agree with you that the EMMC is probably broken. However, the "HT" has nothing to do with the model of the device. (How to read Serialnumbers)

Very creepy. I'm having the same exact bootloop issue as the OP. Friday evening, got stuck on the bootloop. Earlier in the week, I thought I was stuck but hooked it up to my pc and was able to reboot fine. Now I'm most certainly screwed.
I'm ***software status: Official*** ***UNLOCKED*** ***S-OFF***.
Now I'm not sure my phone is even showing up when connected to my PC. When I'd run "adb devices" no devices would show up, but if I did "htc_fastboot getvar all" I had an output similar or same as the OP. I tried to uninstall/re-install HTC Sync Manager, and install the latest Minimal ADB, and now I can't even get that output as seen above.
Where do I go from here? I had the hardest time putting ViperOne on my phone a year ago. I spent three or four weekends studying the forums here. I need detailed instructions or I'll get lost. Thank you all for your work so far here in the forums. If you want to experiment on my phone to get it functional again please feel free to point me in the right direction. I had hoped this post would help, but like I said, I can't see my phone in task manager. (Also, I'm not sure about step 4., I don't see an MAF32 file in what I extracted from the latest minimal adb files.). Please help!

Download mode and then htc_fastboot getvar all.
Qualcomm makes publicly available software that controls the raw hardware so that the manufacturer can upload their firmware. I can't remember where I saw it but it was only a short google search to find it.
It may help. It may not help.
Beamed in by telepathy.

I left the phone on the bootloader screen, plugged in to the PC. I think it got a solid charge overnight, and I am now able to boot normally. In the interest of making my phone more stable, I've tried the No wipe.zip method as seen here to go from 3.35.401.12 to the M9_4.14.401.7_NoWipe_TWRP3030.zip, followed by a TWRP wipe. My Venom ROM would still be based on the older firmware. Also, download mode screen shows the older firmware OS version. Will this cause problems? What can I do to make my phone stable again?

Joining the flock
Hello all. My first post here. I have the same issue on my m9
Status modified, s-on, locked, security warning.
Can't access download mode or recovery. It gives me the green logo on white background with red warning text ('failed to load... This build is for...').
Adb can't see device.
Issue appeared after cracked display started ghost touching all over. Changed system language and such before I turned it off. I went to unofficial service to replace display/frame set and they said it's locked on bootloader.
From what I see here, others with screwed up NAND experience bootloop and can't access download mode..
I just want to be 100% shure it's bricked forever before selling it for parts. I want to fight for my 'baby' to the very end.
So how can I test this or are there any there any tricks I can use to make it boot/get to download mode?
Thank you!
Later edit: don't know if this means anything, but if I select Reboot to Bootloader, the security warning is missing. It just appears if I user the other options.

Well I see that im not the only one, same model, same problems, I was able to boot twrp using "fastboot boot twrp.img", but it shows 0 mb for internal storage, also trying to repair any partition using e2fsck results on "proces ended with ERROR: 8 unable to reapir data", I also was able to adb push the whole bad_boys custom rom zip without a problem but unfortunately i just recive errors while trying to install it.

groxack said:
Well I see that im not the only one, same model, same problems, I was able to boot twrp using "fastboot boot twrp.img", but it shows 0 mb for internal storage, also trying to repair any partition using e2fsck results on "proces ended with ERROR: 8 unable to reapir data", I also was able to adb push the whole bad_boys custom rom zip without a problem but unfortunately i just recive errors while trying to install it.
Click to expand...
Click to collapse
It seems that I have the same problems as you. Also booted into TWRP and tried to restore various 401 back-up options but without success; partly restores then get lots of red text about unable or failed to mount.....etc.
Did you find a solution to the problem?

ludemon said:
It seems that I have the same problems as you. Also booted into TWRP and tried to restore various 401 back-up options but without success; partly restores then get lots of red text about unable or failed to mount.....etc.
Did you find a solution to the problem?
Click to expand...
Click to collapse
Further to the above, whilst in TWRP I used the command adb shell getprop and in the result noticed that there are references to OmniROM. The main one being [ro.modversion]: [OmniROM-6.0.1-20171209-hima-HOMEMADE]. I assume that someone has previously flashed OmniROM and this has caused the brick.
As far as I know HTC devices are not supported by OmniROM.
Does anyone know if the phone is recoverable from this condition?

No sound when answering/making calls

Hi,
I have just discovered that I can hear no sound when I use my HTC M8 dual sim phone for phone calls (I don't use it for calls very often so it could have been like this for a while?).
It seems this is a common problem but I have not managed to find what the solution is so any advice would be very welcome.
I have resetting to factory defaults, clearing the cache, plugging headphones in and out, turned blue-tooth on then off but still the same.
I have LineageOS v15.1 on it with no Google apps but I have tried going back to v15.0 (it definitely used to work ok with this version) but no change.
btw - sound works ok with through the headphones or on speaker but nothing from the inbuilt ear piece speaker.

Adnl info:
I have installed some software which records phone conversations but this records silence which I think confirms my suspicion it is a software problem (if it were a faulty speaker this would still record the audio being sent to it)
I have also tried an app which sends all audio to the earpiece but still no sounds comes from it

Anyone got a solution to this?
It seems a very common problem so I am guessing there is a fix
I have ordered a replacement speaker but I am reluctant to fit it as it is a difficult task and I am pretty convinced it is a software problem but at the moment this is the only option I can think of before consigning this phone to land fill.......

Did you try going back to stock Sense to see if the issue persists? Did it work correctly (sound when on calls) when on stock ROM?

redpoint73 said:
Did you try going back to stock Sense to see if the issue persists? Did it work correctly (sound when on calls) when on stock ROM?
Click to expand...
Click to collapse
I did consider that but wasn't confident I knew how to do it and hoped someone somewhere would know a simple fix (with it seemingly being a very common problem).
This morning I gave it a try, but I proved myself right in that I failed - lol
When I try to install the stock foirmware (with the command "fastboot flash zip xxx.zip") after a few mins it returns the error "FAILED-remote: 32 header error".

alanes said:
When I try to install the stock foirmware (with the command "fastboot flash zip xxx.zip") after a few mins it returns the error "FAILED-remote: 32 header error".
Click to expand...
Click to collapse
Not enough detail to know what you did wrong here. Always give exact file names (and where you got it from); since the term "stock firmware" can literally mean dozens of different things, and we have no idea what you flashed if you are not specific.
Also, if it is an RUU, using the "generic" fastboot is likely not going to work (need htc_fastboot). But given the header error, I don't think you even have the right file for your device.
---------- Post added at 09:28 AM ---------- Previous post was at 09:20 AM ----------
Did you put Lineage on the device, or was it already on there when you got the phone? Since you never answered my question whether calls worked correctly when on stock ROM. Always do your best to answer all questions posed to you, if you want us to try to help.
If you flashed Lineage, you should know how to go back to the stock ROM. Best practice and a basic golden rule of modding phones (whether it be flashing custom ROMs, root, etc.): never do anything you don't know how to reverse. Always have an escape plan. You should know how to go back to stock, before doing any mods. If you don't know, ask. But waiting until there is a problem, to try figure out how to return to stock.
Did you make a TWRP backup before flashing Lineage? Again, another basic golden rule of phone modding: always make a nandroid (TWRP) backup of the stock ROM before root, custom ROM, etc.

Thanks for your replies. Sorry for not giving enough info., I think I am getting too frustrated with the whole thing....I could write a novel about the stress I have had with this phone.
I decided I wanted LineageOS but it was not available for the phone I had so after much research I decided the HTC M8 was the only phone supported with most of the features I wanted (especially dual sim) so I bought one and set about putting Lineage on it. Turned out to be much more difficult than the instructions suggested and I estimate I spent something like 200hrs on it before finally getting it working (with much help from this forum) - This included having to take the phone apart as it turned out a coax cable was missing for the GPS and then had to replace a button.
I finally had it all working and pretty pleased with it then suddenly after a month or so it stops working as a phone and so is now pretty much useless
When I had it all set up and updated with the HTC stock rom I did a TWRP backup but after installing Lineage I realised I had backed it up to the wrong place and so lost the backup
I took notes when I installed the stock rom and kept all the files (or so I though) so I had a backout plan but had never tested it and knowing the problems I had had always suspected I would have trouble if I tried it.
Calls always worked correctly with all the firmwares I have had on this phone, although I can't say for sure it ever worked when I upgraded to LineageOS v15.1 from 15.0
I thought I had seen this problem before but referring to my notes this was a different problem I had hanging up calls with LineageOS 14.
The RUU I used is the one I used when I first set up the phone:
0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F_release_428493_signed.zip
from https://easy-firmware.com/home/browse/category/id/7825/
I did not use the HTC Fastboot so this may well be the problem. I will give it a try and let you know...........
I don't think I used it originally but could be wrong.

Can you please do fastboot getvar all, and post the result (delete IMEI and serial number before posting)? I'd like to see more info about the phone.
To be clear, I don't have the dual SIM M8 (just the single SIM one). So my assistance may be limited. But some things are same/similar, so I'll try to help as much as I can.
Some comments below in red font:
alanes said:
This included having to take the phone apart as it turned out a coax cable was missing for the GPS and then had to replace a button.
I finally had it all working and pretty pleased with it then suddenly after a month or so it stops working as a phone and so is now pretty much useless
So the phone (earpiece sound) worked after you did the hardware repairs? But then stopped working about a month later? I'm suspicious of a hardware issue related to the repair. But flashing the stock RUU (if we can do it) will help determine whether it's a hardware or software problem.
When I had it all set up and updated with the HTC stock rom I did a TWRP backup but after installing Lineage I realised I had backed it up to the wrong place and so lost the backup
What does that mean "wrong place"? You backed up to internal storage, then wiped internal storage, thinking the backup was on SD card?
I did not use the HTC Fastboot so this may well be the problem. I will give it a try and let you know...........
I don't think I used it originally but could be wrong.
You definitely need to use htc_fastboot. The "generic" Google fastboot can't handle the large file size of an RUU. But in that case, it will usually give you an error message to that effect (file size too large); and not "header error". I have a feeling the error may have to do with the version number, but the getvar data will tell me more
Click to expand...
Click to collapse

redpoint73 said:
Can you please do fastboot getvar all, and post the result (delete IMEI and serial number before posting)? I'd like to see more info about the phone.
:
Click to expand...
Click to collapse
Yes, I thought I had backed up to SD card but was wrong
I have just discovered the microphone doesn't work either. I have software which records phone conversations but this now just records nothing, if it were a wire off the speaker or something I think this would still work.
I spent all this morning trying again but still getting the same error. I am wondering if it is because my phone was upgraded(via the HTC automatic updates) to version 6.16.401.101 and so now doesn't like going back to the older version?
Would it be a bad idea to try the file "0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.101_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465002_signed.zip"?
- although if this worked I guess it wont install the updates which is what I am hoping will get the phone working again as I keep reading that HTC released an update for what sounds like the problem I have.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.401.101
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxx
(bootloader) imei2: xxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

alanes said:
I spent all this morning trying again but still getting the same error. I am wondering if it is because my phone was upgraded(via the HTC automatic updates) to version 6.16.401.101 and so now doesn't like going back to the older version?
Click to expand...
Click to collapse
Since you have s-off, it should be okay to flash an older version; as long as it is the proper RUU for your CID and MID, which it appears to be. Unless HTC imposed some limitation on the M8s, that isn't present on M8 (meaning, at least on the M8, flashing older RUU is okay as long as you are s-off).
alanes said:
Would it be a bad idea to try the file "0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.101_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465002_signed.zip"?
- although if this worked I guess it wont install the updates which is what I am hoping will get the phone working again as I keep reading that HTC released an update for what sounds like the problem I have.
Click to expand...
Click to collapse
That should be the perfect RUU for you to flash, given the current main version you show in getvar. Verify it is a full RUU (>1 GB).
The RUU will include all partitions updated to version 6.16.401.101, including whatever was updated. And you should get any updates after that, if there are any. So I'm not sure what you are saying, that you don't think you will get updates.

Thanks, I will give it a try tomorrow (It won't let me download it as it says I have hit my daily limit for the site)
I was told when I first set up the phone that there are lots of partitions which I am not aware of which HTC updates will modify etc., which is why I had to do the official HTC updates to the latest version before I was able to install LineageOS (but I may well have misunderstood).

Gave it a try this morning but same error message as before
I even tried it on a different computer but no change
Just in case I am doing something wrong, what I do is:
First wipe all the partitions using TWRP (apart from sd card) then use htc-fastboot to try and send the RUU zip file
I have not removed TWRP although I did once try first uploading the HTC recovery file corresponding to the RUU version I was about to upload.
I have seen some instructions which say you have to re-lock the phone first but I don't think this is the case (I don't want to do this unless I have to as it is a pain to unlock again).
i.e. fastboot oem lock
Been experimenting with the phone and it turns out the other person can hear me but I can't hear them, but if I switch it to speaker phone then I can hear them but they can't hear me - lol
I guess this proves it is software related though.
--------------
Latest news: I have downloaded TWRP backups instead of using the RUU, this seems to be installing and I will let you know how it goes........

alanes said:
Gave it a try this morning but same error message as before
Just in case I am doing something wrong, what I do is:
First wipe all the partitions using TWRP (apart from sd card) then use htc-fastboot to try and send the RUU zip file
I have not removed TWRP although I did once try first uploading the HTC recovery file corresponding to the RUU version I was about to upload.
I have seen some instructions which say you have to re-lock the phone first but I don't think this is the case (I don't want to do this unless I have to as it is a pain to unlock again).
i.e. fastboot oem lock
Click to expand...
Click to collapse
Strange, I don't know what you are getting header error. Really, from what I can tell, either RUUs you tried should work.
No need to wipe anything in TWRP, nor install stock recovery, in order to RUU. But doing those things won't hurt anything, either (such as the header error).
Also, no need to relock the bootloader since you are s-off. Again, unless the dual SIM M8 has some difference from the "regular" single SIM M8. At least on the single SIM, I'm absolutely positive the RUU will flash with either bootloader locked/relocked or unlocked, as long as you are s-off.

Hi,
I spent much of today on it and managed using TWRP to install the stock HTC rom (6.16.401.101) and do the updates but still the same so tried 4.30.401.15 but still no joy.
Guess my only hope now is to try replacing the earpiece speaker but I still think it is software rather than hardware related.

I finally decided it is not a hardware problem so will consign this phone to the trash and I will give a Willeyfox phone a try, see if this works out any better (can't be much worse - lol)