[Q] Fastboot isn't working, neither is recovery...

[cojomojo]

Some logs

@jball @redpoint73

Here are some logs i have dug up from the system. maybe they can help. I notice that there is quite a few errors.

"fastboot oem dmesg" = http://pastebin.com/qN1NMN0W
"cat /proc/last_kmsg" = http://pastebin.com/dCvkRBvg -- command run while in TWRP
"dmesg" = http://pastebin.com/ub77Xrub -- command run while in TWRP

"dmesg" has multiple occurrences of:

....
 AXI: msm_bus_cl_get_pdata(): Error getting bus pdata!
....
<4>[    0.620274] c1      1 mdss_dsi_ctrl: probe of fd922e00.qcom,mdss_dsi failed with error 48
....
<6>[    0.640342] c0     38 [MHL]get_device_id:3281 I2C error 0xfffffffb

 

[cojomojo]

So I started investigating to see if I have some bad nand. Here is one the kernel_message_log i posted earlier but with "grep mmcblk".

I also ran fsck on /system and got:

/dev/block # e2fsck -fv /dev/block/mmcblk0p45
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p45: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes

e2fsck: unable to set superblock flags on /dev/block/mmcblk0p45

I am not super familiar with what the above means, but I do know that its not good

 

[redpoint73]

Maybe try and get s-off???

I don't see how that would help or be part of the issue. And I hesitate to recommend something that costs $25 and which I'm not confidant will help at all.

---------- Post added at 09:28 AM ---------- Previous post was at 09:25 AM ----------

"Fast Boot" is turned on in battery/power settings. However, I turned it off, rebooted, and its back on. Tried multiple times and it won't stick.

I doubt the "Fast Boot" setting would make much of a difference. The only reason you see this sometimes mentioned in relation to adb/fastboot, as that it might prevent some folks from properly getting into bootloader is they try to do so by powering off, then on again (but choosing "Restart" after holding the power button will work fine regardless of whether the "Fast boot" setting is selected or not).

I don't have any other ideas at this time, either.

I don't know much about the logs you posted, but bad emmc was a thought of mine, as well.

There are certainly folks here that know a lot more than I do, so hopefully some of them can chime in.

 

[Krix]

So I started investigating to see if I have some bad nand. Here is one the kernel_message_log i posted earlier but with "grep mmcblk".

I also ran fsck on /system and got:

/dev/block # e2fsck -fv /dev/block/mmcblk0p45
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p45: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes

e2fsck: unable to set superblock flags on /dev/block/mmcblk0p45

I am not super familiar with what the above means, but I do know that its not good

Any update on this? I'm having the exact same issue.. ROM doesn't get affacted by no matter what I do.

 

[toysoldierq]

Any update on this? I'm having the exact same issue.. ROM doesn't get affacted by no matter what I do.

If your pc has only 3.0 usb might be the problem you could try a 2.0 usb and check, as for suggesting s-off i dont know if it would help being that with or without s-off he still has a fastboot issue so flashing anything is pointless.

 

[Krix]

If your pc has only 3.0 usb might be the problem you could try a 2.0 usb and check, as for suggesting s-off i dont know if it would help being that with or without s-off he still has a fastboot issue so flashing anything is pointless.

My laptop is about 6 years old. I wonder if USB 3.0 Technology was discovered then? I am trying it in Ubuntu though.. Could that be an issue? I flashed the exact same devices with the same computer about a year ago and that worked fine. It just went in to a boot loop and NOTHING seems to be working. I believe even the factory reset in the recovery too doesn't put any effect on anything. The device remains exactly as it is.. Its so upsetting.

 

[toysoldierq]

My laptop is about 6 years old. I wonder if USB 3.0 Technology was discovered then? I am trying it in Ubuntu though.. Could that be an issue? I flashed the exact same devices with the same computer about a year ago and that worked fine. It just went in to a boot loop and NOTHING seems to be working. I believe even the factory reset in the recovery too doesn't put any effect on anything. The device remains exactly as it is.. Its so upsetting.

Im running windows 8.1 64bit never had a problem, i think your device can be fix i would have to see what your device manager is saying when your on windows to make sure u have the latest drivers.

 

[Krix]

Im running windows 8.1 64bit never had a problem, i think your device can be fix i would have to see what your device manager is saying when your on windows to make sure u have the latest drivers.

I am primarily on Linux. I tried Windows with visualization only.

 

[Krix]

Im running windows 8.1 64bit never had a problem, i think your device can be fix i would have to see what your device manager is saying when your on windows to make sure u have the latest drivers.

Also if it was an issue with Windows or the USB port, then the flash from the recovery should have worked. That isn't working either.

 

[cojomojo]

Any update on this? I'm having the exact same issue.. ROM doesn't get affacted by no matter what I do.

Never found a fix. I stopped trying when my dad (it was his device) got a new phone.

 

[saiyansection]

Never found a fix. I stopped trying when my dad (it was his device) got a new phone.

same issues i am facing and this veterans even not trying to help me out?

what happened to HTC one m8 community , looks like its dead already!

better i change motherboard and delete account from here -_-

nobody is helping except 1 or 2 people :v

 

[jerryspring]

same issues i am facing and this veterans even not trying to help me out?

what happened to HTC one m8 community , looks like its dead already!

better i change motherboard and delete account from here -_-

nobody is helping except 1 or 2 people :v

Download htc sync manager and chose repair