yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
If nothing was flashed or installed when this happened, it would seem some partitions have become corrupted, including recovery and radio baseband.

If your files were that important to you, you should have been backing them up (SD card, computer, cloud, etc.). Waiting for a disaster to happen and hoping you can recover your files, is not a good plan.

You can keep trying to flash TWRP. If you can flash/boot TWRP, then you should be able to browse/copy internal storage (if that has not also been corrupted).

Is it saying TWRP installed properly? What version TWRP did you try? Maybe try slightly different build numbers, while sticking with the most recent builds.

You can also try the command: fastboot boot recovery TWRP.img

Where "TWRP.img" above should be replaced with whatever file name the version of TWRP you are trying.

This command

boots

to TWRP, without actually flashing it. Which sometimes works for folks that have issues flashing TWRP.

If all attempts to flash/boot TWRP fail; my next suggestion would be to flash RUU or signed firmware.zip. Hopefully, this will fix the baseband issue, as well as fix the recovery partition (but will put it back to stock recovery). You will need to relock the bootloader to flash either RUU or firmware.zip; which will wipe all personal data on the phone.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Sorry, I gave you the wrong command syntax. It should be: fastboot boot twrp.img

Try that, and see if you it helps at all.

But to be honest, spontaneous corruption of OS and recovery, plus inability to relock bootloader, to me indicates you probably have emmc failure (hardware failure).
[One (M8) Q&A, Help & Troubleshooting] Salar.m:
thanks for reply,

it seems that I'm getting the same errors this user had got:

https://xdaforums.com/htc-one-m8/help/help-fastboot-t3288949

and you mentioned emmc failure to be the reason of the problem for his device too

Can it be fixed with hardware replacement? "What part" of old devices should I search for to replace with mine?

if I find a healthy ( lest say eMMC ), can it be replaced with my broken eMMC? and after that, will the problem be solved? (I'm not sure if that broken part's name is actually eMMC or not,) or maybe other hardware parts might be dead too?

Can I find eMMC on old devices or Could it be bought online?

---------- Post added at 10:59 PM ---------- Previous post was at 10:53 PM ----------

BTW, the correct command didn't work neither:

C:\adb>fastboot boot twrp.img

downloading 'boot.img'...

OKAY [ 2.143s]

booting...

OKAY [ 0.004s]

finished. total time: 2.206s

C:\adb>fastboot boot twrp3.img

downloading 'boot.img'...

OKAY [ 2.138s]

booting...

OKAY [ 0.004s]

finished. total time: 2.151s

but nothing happens on phone...
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
I'm not really a "hardware" repair guy, so I try to stick to software type questions. But I'm pretty sure the emmc is not replaceable, without having to replace the whole motherboard. Which aside from the screen and battery, and a few other things, is basically like replacing the whole phone.

I'd also mention that unless you are experienced taking these device apart, it is not for faint of heart, and can go poorly. I've seen folks on this forum, damage the antenna or something else while trying to repair the device, and you can end up trading one problem for another. That is one reason I don't like messing with hardware repairs.
[One (M8) Q&A, Help & Troubleshooting] Salar.m:
So just to be sure about my device not booting up again:

-Are we sure that the problem is with eMMC?

-isn't there any software trick e.g. any FASTBOOD repartiotion command or something that would fix all these errors?

or any diagnostic command to show partitions size, and their status: whether they are healthy or broken?

Can we be sure that my m8 is now completely useless??
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
I don't know if I can say I am 'sure'. But the preponderance of the evidence would point to emmc failure. And I don't have any other working theories, and I don't know if you will find any other fixes.

No recovery, no radio, and not being able to lock bootloader are big problems. If you could lock bootloader, you can at least flash firmware or RUU, which the hope that it fixes partitions. But personally, I have no other ideas for you.
[One (M8) Q&A, Help & Troubleshooting] Salar.m:
thanks for your replies, after all, I'm still suspicious to ARHD Rom if it contains some software bug or sth causing this hardware failure; because since the problem started I've searched and seen some users getting caught in bootloader having the same problem; I think mike should be informed of it maybe he can fix the problem...

some one even mentioned it with the same scenario I had: "...after battery finished..."

thanks anyway
[One (M8) Q&A, Help & Troubleshooting] Einwod:
There's nothing wrong with the ARHD ROM. I've been using it since it came out and still have it on my M8. The problem is your device, NOT the ROM.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
I'm stuck at the image below, ihave backup of original rom, but removed the installed custom rom, cannot enter into recovery (starts to enter into recovery but nothing happens)

Not booting any further from this screen. Any help

Recently changed the battery by myself.

Phone info I don't remember, kept img of getvarall in other laptop.

Tried to search in my old posts, but not successfull.

I want to start the phone whatever back to stock rom or twrp (then I can install some custom rom)

I need full step by step instructions (forgot everything after changing the phone)
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Lots of gaps of info here. Makes it nearly impossible to help, unless you fill those gaps (see my comments below in red font):
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
First of all Thanks for trying to help.

The earlier twrp was 3.2.1.

When from the shared img screen, I try to go to recovery, the next screen top mesg pops, entering twrp recovery , then phone get off, doesn't boot.

I have downloaded latest twrp.img 3.2.3

How to flash latest twrp via fastboot commands, steps and prerequisite links (adb drivers etc) is my requirement.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
I pretty much already figured that out. But you aren't being clear about, is (I assume/guess) everything worked fine (working ROM, working TWRP?) until you changed the battery, but now no working ROM and not working TWRP?

You see, changing the battery is kind of important thing you neglected to mention in your (too) brief description above.

You also did not answer half my questions, so I'm not sure how you expect to get help; if you can't provide all the info requested.

You aren't in the position to make "requirements". We aren't paid tech support, you know? We just give up our free time to help others in the community. If you want to get the phone working, you need to put the time and effort. Not expect strangers to spoon feed you things you can look up yourself. You just sound lazy, and now

entitled

as well! You didn't even say "please" so you are coming off as arrogant and bossy. So I'm being charitable here (don't push your luck):

You only need fastboot/adb drivers, if you never used those tools on your (new?) laptop ever. For good easy fastboot driver install, just use the xda search function, with the search term "easy adb" and you will get a couple good results.

After that, the commands are simple:

fastboot erase cache

fastboot flash recovery twrp.zip

The first command is often helpful, in instances (like yours) where TWRP is not installing or booting correctly.

More info here: https://twrp.me/htc/htconem8gsm.html
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Sorry for not writing the "please" word.

"requirement" word I used just (in my thinking) to clarify a per my little knowledge.

Thanks again for the help you are providing (I know you are not paid for that)

I was not at all arrogant from my side, again sorry if you felt like that.

It was working before battery replacement, but little unstable,,,,, detail is that "people stopped working" was the continuous pop up. It was S. Rom jw 5.4 version (not 100 percent sure as I tried different versions due to pop up ? issue)

Now

I have followed the link you provided, installed the drivers as per the given links, but "first command is working fastboot erase cache

but

fastboot flash recovery twrp.img

tells cannot load twrp.img

(already twrp-3.2.3-1-m8.img downloaded and kept in the same folder with rename twrp.img)
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
You probably aren't running the command from the proper directory. You need to run it from the directory when adb.exe and fastboot.exe were installed. Where exactly that is, will depend on which installer you used.

Once you've found those executables, a nice shortcut to open the command prompt in that directory, is to (assuming Windows):

1) Have the correct folder open in a window.

2) Hover the cursor over that window.

3) Shift+right mouse, which will bring up a dialogue box. Select "Open command window here"
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
now recovery flashing was successful as per the command prompt but when i tried reboot to recovery in mobile , it does the same,,

entering recovery pops up

then doesn't boot up ,just shutdown.

(can be the new battery charging issue ? i kept the charger connected 1 hr in sd condition ,it shows battery icon without charging animation or percentage)
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Possibly. I would suggest leaving it on charger for a few hours, and see if the condition changes at all.

Also when you have a chance, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Ok will do both and will update, tomorrow
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
1.charging kept 4hrs but same , flashing on battery icon with bottom red txt (5 sec on then 4 sec off)

2.power button alone pressing, starts to boot but again off after white screen for 2 seconds.

3.again tried to flash recovery , it is successful but does not boot into recovery.

4. see getvar all result
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
I'm waiting for help, since last 24hrs ,,,,,, anyone please read previous conversation and help

I think [MENTION=660462]redpoint73[/MENTION] is the only one helping?

Please someone help atleast to go back to stock from above condition.
[One (M8) Q&A, Help & Troubleshooting] Einwod:
You are demanding help when help here is given freely by people who have the time and are willing to help. Stop demanding, nobody HAS to help you. That's already been pointed out.

This thread, https://xdaforums.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

should be able to get you back to stock. Only problem is, if you can't flash TWRP then you're stuck. Make sure you flash the correct version. Everything you need is in the first 5 posts. Read carefully and follow the instructions. One final thought, are you absolutely sure your bootloader is unlocked?
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
I'm sure bootloader is unlocked.

The above linked post only possible if I can boot to twrp, but latest 3.2.3 recovery is flashing successful via pc fastboot, but still mobile cannot boot into recovery,,,,

So i am stuck? but i can boot into fastboot,,,,, and this screen remains on always, means power is there in battery.

any ideas that it can be about battery replacement, any connector issue?

oh just now observed that in my above screenshot , battery status is good but voltage is 0mV. so what to do?
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Bootloader is unlocked ?

shall i relock the bootloader & flash RUU?

(i just need my phone working please)
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
If I were you, that's what I would do. Flashing the RUU should fix everything.

You can download it from here
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
It will need relock bootloader right?

Same file I just Finished download but extract giving error for corrupt.

I'll try redownload in the morning.
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
Yes you have to relock your bootloader since you are S-On

No, you don't extract anything from the RUU.zip, you just flash the .zip itself

fastboot oem lock to relock your bootloader

put the RUU.zip into your fastboot folder

fastboot oem rebootRUU

fastboot flash zip **drag and drop the RUU.zip here**

Or another way to do it after you have relocked your bootloader is to delete everything in the name of the .zip except for 0P6BIMG (and .zip of course), put that onto your extSD card, and boot to bootloader. Your phone will detect the renamed .zip and will initiate the flash. All you'll need to do is press volume up to confirm the flash, and press the power button to reboot after the flash is complete.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Ok thanks, I'll try

Just one more question (silly I think)

fastboot flash zip and then I have to drag and drop zip file into the command prompt window?

Or this **drag and drop **is also part of command ?
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
Drag and drop the .zip file. Otherwise you'll have to type out the whole name of it.

Alternatively, you can rename the file to something simple like "ruu.zip" and enter: fastboot flash zip ruu.zip

Personally, I find that dragging and dropping the .zip is easiest.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Zip flash success, but again it's coming back to fastboot, not booting to system.

Bootloader signature checking is failing as in command prompt.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
The RUU did

NOT

flash. "Sending 'zip' . . . OKAY" simply means that fastboot was able to send the RUU.zip to the phone, in preparation to flash it. The "writing . . FAILED" means it did

not

install.

You sure you locked the bootloader successfully? It would say RELOCKED near the top of the bootloader screen. This is the usual reason for signature checking failure, when the correct RUU has been attempted.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
]

Yes I reconfirmed it, again relocked as well to be sure.

Top of screen now mentioned "relocked"
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Try the htc_fastboot from here (instead of the "generic" Android fastboot): https://xdaforums.com/showpost.php?p=64926626&postcount=6

No need to download the RUU again. Just the htc_fastboot.exe, and the command is slightly different.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Tried

only difference is now charging animation working(80% it was & now 100%) , & top most in boot loader software status earlier it was mentioned :modified:, now i observed mentioned "official:.

but after finish, the command given fastboot reboot, it tries to start upto white screen but then gets off, then i tried to run that setup exe file(normal & as admin) , that file also not opening more than 1 sec,

power on button pressing, comes to white start screen & gets off again, not booting.

power plus volume down results in same fastboot mod.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
The RUU installed correctly, and wrote all partitions, with no errors.

I'm puzzled why the device still won't start, after RUU.

I have no idea what you are talking about when you mention "that setup exe file". It would be much more helpful to include the actual file name, instead of some vague description, which doesn't correspond to anything I can think of.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
I'm worried that you are puzzled, as you are the hope for me,,,,,

Set up means

htc_fastboot.exe which you provided link.

I attached that linked page screenshot which is asking to run setup file (htc_fastboot.exe) after RUU flash and reboot , but in my case no proper reboot. So I tried to run that setup but that set up also not loading (looks like command prompt window trying to open by that setup).

Main issue is device not booting to system.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Could not attach in previous post
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
tried to flash ruu with your provided link way again & same successful flash result, not booting to system.

now this time taken get var all result to compare with first beginning of the issue,,,

earlier

version-main: (it was empty)

now

version-main: 6.12.401.4
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
XDA is killing me today. I had a whole long reply typed out, and then clicked "Submit" and got an error, so I've got to type it again!

htc_fastboot.exe is not a "setup file". No reason to believe that it is.

htc_fastboot.exe is just what allows the htc_fastboot command to work, which you already did (to allow the RUU to install).

In the screenshot/instructions you refer to, it is simply saying that after you run the RUU and the Android OS starts up (which you haven't gotten that far yet!) the "setup" is simply the Android startup where you enter you Google login, etc. This is not some separate file you need to execute.

---------- Post added at 10:19 AM ---------- Previous post was at 10:14 AM ----------

I'm running out of ideas. Only other idea I have, is to go back to the path of trying to flash TWRP. You will need to unlock the bootloader again, then flash TWRP with fastboot, then see if it will boot into TWRP.

My hope is that the RUU fixed whatever was preventing you from booting to TWRP before. But it is puzzling (and troubling) that the phone won't boot to OS after flashing RUU.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Today I was also thinking almost same,,,, but Afraid to try until your reply.

Now I'll try the same.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Done , recovery flashing successfull after bootloader unlock,. but device behaviuor same,only booting to fastboot, not into recovery or system.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
fastboot erase cache, then fastboot flash TWRP again. As I suggested in a previous post. May not be any difference. But doesn't hurt to try.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Already tried same as well,,, ,, worry increasing,,,,

Can be hardware issue? But device is behaving normal in fasboot.,,,,

I'm thinking to remove and reinsert battery,,,, (headache job).

---------- Post added at 01:19 AM ---------- Previous post was at 01:04 AM ----------

Another idea is that, after flashing recovery, I should flash custom rom via fastboot,,,,, (I'm not sure its possible)?
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
You could try fastboot booting TWRP.

Put the recovery into your fastboot folder and rename the .img to something easy to type out like twrp.img (or just twrp if your file extensions are hidden).

Then from bootloader/fastboot:

fastboot boot twrp.img

You'll need to have the ROM you want to flash on your phone's storage, so load it onto an SD card and insert that into your phone. Or transfer it to your internal if you want/can.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
I'll try and report.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
tried after putting Rom into SD card

but the above command also resulting in device shutdown only, not booting to recovery or system.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
what next i should try?

another RUU (older one) or try removing /inserting battery?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Device behaving normal in fastboot doesn't exclude the possibility of hardware issue. We've seen emmc failure prevent flashing recovery, as well as other symptoms.

What makes your case puzzling, is that the problems seem to be caused by battery replacement. I can't figure out why the issues (failure to boot OS, failure to boot TWRP) are related to battery replacement.

Further, emmc failure is usually accompanied by inability to flash various partitions (error messages when flashing RUU) so again, your symptoms don't seem to match.

You can't flash a custom ROM with fastboot. If you could flash custom recovery (TWRP) you could flash a custom ROM, or restore stock TWRP backup. Flashing/booting TWRP is the key.

---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------

This is really odd, not being able to boot TWRP (which was my next thought, but xunholyx beat me to it.

Again, I can't figure out how this is related to battery replacement.

---------- Post added at 09:12 AM ---------- Previous post was at 09:11 AM ----------

You can't flash an older RUU while s-on. And not worth getting s-off, to try something that might not work, anyway.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Any suggestions?
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
He said before he changed the battery himself.

The not booting problem is maybe due to some cable not properly fit or damaged, especially the first cable on left side of the battery/motherboard. (the hardest to put back in my experience)

My only suggestion is to recheck all cables are properly fit to their slots. There are 7 flex cables & 4 wired - the wired ones also tricky to put back, must feel the "click" when properly fit to its slot.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
I'll try the same now.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Yes, I know. My statement could have been phrased more clearly, such as: "I don't know why the battery replacement you performed, could be causing these specific issues (no boot to OS, no boot to TWRP)."

Which you gave a possible answer to. Your theory seems plausible, and would explain what is going on.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
Just reopened and boxed up to ensure all the connections are intact and result is same.

Q:RUU flashing was successful but in the beginning it was telling Signatures verification failed, next command line mentioned bypassed, next full process all steps successful.

Any idea?
[One (M8) Q&A, Help & Troubleshooting] Einwod:
A question, if I may. Has this device been owned by you from the beginning? Has the device ever had S-OFF? Easy to check with Sunshine. I have a feeling, just a feeling, that this device has been modified in some way. Either the MID, CID has been modified and then S-OFF removed leaving you with signature failures. It's only a thought on my part. May explain the failures.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
This device owned by myself since beginning, done rooting, custom roms, never had s-off. Once battery replacement done by repair person and then software as well (used by friend during battery replacement and software Issue)

By software I mean I'm not sure that time that repair person did RUU or custom rom.

When I received the phone it was continuously pop up

People has stopped responding, then I flashed S.Rom jw version, but I don't exactly remember that I did RUU before custom rom or not.

.

It's showing s-on in get var all.
[One (M8) Q&A, Help & Troubleshooting] Einwod:
I really think you have tried to change the CID/MID on this device and messed it up. See the getvar output from this thread and it does not match yours. Download and try to run the Sunshine apk. If it has been S-OFF before, there is no need to pay for it. The MID/CID that you have does not match and that is why there are errors when you try to flash the RUU.zip.
[One (M8) Q&A, Help & Troubleshooting] wasim9283:
I'm 100 percent sure that ihave never ever tried that, but may be that repair person did,,,,, anyway

Thanks for providing logical idea.

But now my device is not booting into system or recovery except fastboot , how to check by sunshine apk?
[One (M8) Q&A, Help & Troubleshooting] Einwod:
Unfortunately you need to be in the OS for Sunshine to work. There's no other way to check.