[HELP THREAD] HTC One M8 - Ask any questions here!

[wasim9283]

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.

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?

 

[Einwod]

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?

Unfortunately you need to be in the OS for Sunshine to work. There's no other way to check.

 

[redpoint73]

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.

From what I can tell from ckpv5's stock TWRP backup thread, CID HTC__J15 can have MID 0P6B10000 or 0P6B67000. So maybe not conclusive that the device has been modified by s-off or not?

https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

---------- Post added at 10:15 AM ---------- Previous post was at 10:13 AM ----------

But now my device is not booting into system or recovery except fastboot , how to check by sunshine apk?

You can't check, and you can't s-off the phone (even if it was previously made s-off), since your device won't boot to OS (and therefore, can't use the sunshine app).

 

[wasim9283]

You can't check, and you can't s-off the phone (even if it was previously made s-off), since your device won't boot to OS (and therefore, can't use the sunshine app).

So no hope?
Device dead?
But but but It's booting to fastboot,,,,,,,, :crying:

 

[redpoint73]

So no hope?
Device dead?
But but but It's booting to fastboot,,,,,,,, :crying:

You tried different versions TWRP, and same result? Anything back to TWRP 2.8.7 should be okay with your current firmware.

Only other thing I can think of, if try to lock bootloader again (sorry to make you do that again) then flash firmware 6.12.401.4. Then flash RUU again, and see if any change.

You can get the firmware on the following post, including instructions on how to flash at the end of that post: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5

Note that firmware is not the same as RUU or a ROM, but includes hboot, radio, etc. needed the ROM to work (but does not include the ROM itself). Typically firmware is flashed with the RUU. Just a shot in the dark, really. No reason to believe flashing firmware, then RUU, would have any different result than the RUU flash you already did. But worth a try, and no harm in doing so.

 

[wasim9283]

You tried different versions TWRP, and same result? Anything back to TWRP 2.8.7 should be okay with your current firmware.

Only other thing I can think of, if try to lock bootloader again (sorry to make you do that again) then flash firmware 6.12.401.4. Then flash RUU again, and see if any change.

You can get the firmware on the following post, including instructions on how to flash at the end of that post: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5

Note that firmware is not the same as RUU or a ROM, but includes hboot, radio, etc. needed the ROM to work (but does not include the ROM itself). Typically firmware is flashed with the RUU. Just a shot in the dark, really. No reason to believe flashing firmware, then RUU, would have any different result than the RUU flash you already did. But worth a try, and no harm in doing so.

older twrps tried , result exactly same.
Found old getvarall from old laptop, some differences found, please guide

 

[mrrocketdog]

damn , i miss my m8.

err on the side of kindness

 

[wasim9283]

You tried different versions TWRP, and same result? Anything back to TWRP 2.8.7 should be okay with your current firmware.

Only other thing I can think of, if try to lock bootloader again (sorry to make you do that again) then flash firmware 6.12.401.4. Then flash RUU again, and see if any change.

You can get the firmware on the following post, including instructions on how to flash at the end of that post: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5

Note that firmware is not the same as RUU or a ROM, but includes hboot, radio, etc. needed the ROM to work (but does not include the ROM itself). Typically firmware is flashed with the RUU. Just a shot in the dark, really. No reason to believe flashing firmware, then RUU, would have any different result than the RUU flash you already did. But worth a try, and no harm in doing so.

done firmware flashing, finally completed after some initial failed commands, same RUU flashing result as earlier,now bootloader is relocked.
all screen shots attached.
i am concerned about start of RUU flashing , in start some failed commands appears but very fast it proceeeds next steps which are successful till end.

 

[redpoint73]

Found old getvarall from old laptop, some differences found, please guide

I don't see any differences, except what would be expected to change after flashing the Marshmallow RUU or firmware (radio number, version-main number).

I also see what is listed for "commitno-bootloader" is different. I don't actually know what that one is. But I also suspect it will normally change with new RUU/firmware.

In any case, I don't see anything in the old getvar (versus more recent one) that would warrant any concern, nor give any clues to the present issues>

---------- Post added at 09:50 AM ---------- Previous post was at 09:44 AM ----------

done firmware flashing, finally completed after some initial failed commands.

Error which says to "flush again immediately" is normal and expected. Should say "flash again immediately", don't know why it always says "flush"! If you ran the command again to flash the firmware, you did the right thing.

Any other errors when flashing firmware, are not normal, and should be noted to us.

i am concerned about start of RUU flashing , in start some failed commands appears but very fast it proceeeds next steps which are successful till end.

It does look weird (possibly concerning) that the output is showing the same bootloader (sbl1) being attempted multiple times: fail, successful fail

Not sure what that means, though. I have to think that this is still somehow connected to changing the battery (loose, damaged connector, etc.). Probably not a coincidence that the issues booting to OS or TWRP happened right after the repair.

 

[wasim9283]

I don't see any differences, except what would be expected to change after flashing the Marshmallow RUU or firmware (radio number, version-main number).

I also see what is listed for "commitno-bootloader" is different.

So now what next possible tries? Any suggestion /idea?

 

[wasim9283]

So now what next possible tries? Any suggestion /idea?

?
Any help @redpoint73

 

[redpoint73]

So now what next possible tries? Any suggestion /idea?

I don't really have any other ideas. Only thing I can think, is to unlock the bootloader again (which I know is a hassle), and try to flash/boot TWRP again. The difference being, maybe the firmware/RUU flash changed something. But it's pretty unlikely, I think. Just a shot in the dark, really. Don't be disappointed if you try it, and nothing changes.

 

[wasim9283]

I don't really have any other ideas. Only thing I can think, is to unlock the bootloader again (which I know is a hassle), and try to flash/boot TWRP again. The difference being, maybe the firmware/RUU flash changed something. But it's pretty unlikely, I think. Just a shot in the dark, really. Don't be disappointed if you try it, and nothing changes.

UNlocked the bootloadere & tried flashing two different versions of twrp, same result.

 

[redpoint73]

UNlocked the bootloadere & tried flashing two different versions of twrp, same result.

Any luck booting recovery (instead of flashing it)?

fastboot boot recovery whatever_name.img

 

[ddogg11]

Well, after 5 years of usage, camera on my m8 started making this buzzing noise and can't focus anymore. Same thing happens when I turn on flashlight. Is there any solution or I should change camera completely?

 

[Einwod]

Well, after 5 years of usage, camera on my m8 started making this buzzing noise and can't focus anymore. Same thing happens when I turn on flashlight. Is there any solution or I should change camera completely?

I'd say its time to change the device for a newer model. Or simply change the camera module if you're confident enough to do it yourself.

 

[wasim9283]

Any luck booting recovery (instead of flashing it)?

fastboot boot recovery whatever_name.img

Tried with same result,,,
Device trying to enter recovery, top side comes entering recovery, then device gets off, not booting.

 

[redpoint73]

Tried with same result,,,
Device trying to enter recovery, top side comes entering recovery, then device gets off, not booting.

I personally don't have any other guidance. We've tried everything I can possibly think of, including (some steps you did repeatedly):
- Flash RUU and signed firmware (with locked bootloader, as required)
- Flash TWRP, various versions (with unlocked bootloader, as required)
- Boot TWRP

From software/firmware standpoint, you are stuck. The phone won't boot after RUU and/or firmware flash, and TWRP won't boot. So there is no other way to get the phone booted to OS.

You can try to check the hardware connections again. I tend to think ckpv5 was onto something there. Especially since the issues arose after battery replacement (most likely not a coincidence). But personally, I know very little about the hardware side, and therefore try to stick with helping folks on the software/firmware issues. So I can't give any further guidance, unfortunately.

 

[wasim9283]

I personally don't have any other guidance. We've tried everything I can possibly think of, including (some steps you did repeatedly):
- Flash RUU and signed firmware (with locked bootloader, as required)
- Flash TWRP, various versions (with unlocked bootloader, as required)
- Boot TWRP

From software/firmware standpoint, you are stuck. The phone won't boot after RUU and/or firmware flash, and TWRP won't boot. So there is no other way to get the phone booted to OS.

You can try to check the hardware connections again. I tend to think ckpv5 was onto something there. Especially since the issues arose after battery replacement (most likely not a coincidence). But personally, I know very little about the hardware side, and therefore try to stick with helping folks on the software/firmware issues. So I can't give any further guidance, unfortunately.

I'm now thinking to get it checked by local repair person, for confirmation of hardware issues, but that can be done by June,,,, thanks for the help.
Surely will update here,,,,

 

[leelaw]

Can somebody help me out? I'm trying to fresh install this RUU file - RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined but I'm just stuck in Updating... (1/1) Sending...
Currently on Unlocked Bootloader, S-OFF