• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help HTC M8 soft or hard brick?

yup.. fastboot usb..

IMAG0513.jpg
 
Ok, download the fastboot/adb tools from this post (also has set-up guide) here just in case the version you have is older:

ADB Guide (updated 2014/11/11)

plus the universal adb driver from this post:

ADB Guide (updated 2014/11/11)

Make sure that fastboot is connecting to your phone, type:

fastboot devices

should return a string of letters/numbers, which is the phone's serial number.

Yes, both RUU methods need a locked bootloader unless you are s-off :( - but given it's pretty messed up it might, just might, be showing an incorrect state.
 
just came across my mind. am i supposed to put a RUU into the same folder with fastboot?

concerning drivers, yesterday i installed htc sync manager, so it has to be the newest version
 
Last edited:
Good point, RUU does I think need access to fastboot - I have it set up with the folder path added to my PC's environment variables so I can run from anywhere. Can do that or run the RUU from your fastboot/adb folder.

Ok, those are the HTC drivers - different from the universal adb driver set-up. The uni adb driver can help if you have problems with manufacturer pre-packaged adb drivers. Does 'fastboot devices' command return the serial number string?
 
yes it does.
C:\sdk-tools>fastboot devices
HT45YWM01368 fastboot

actually when i run uni adb installer it said i already had it, so i uninstalled it and installed again.

EDIT:
tried with new fastboot/adb tools and uni adb drivers, with RUU placed in fastboot folder and still the same message.
 
Just wonder if it's worth trying to fastboot flash TWRP again, did you re-download TWRP and check the md5sum so you could try it and rule it out as a possible solution?
 
:(

C:\sdk-tools>fastboot flash recovery twrp.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.434s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.512s
 
It's s-on, so I believe the lock command is -

fastboot oem relock

This will take it to RELOCKED and the RUU will be fine with that at least that part of it.

Someone seriously screwed up the phone, as noted earlier - it's s-on with unknown baseband.
 
Tnx for your reply.

after this command nothing happens on the phone:
C:\sdk-tools>fastboot oem relock
...
(bootloader) [ERR] Command error !!!
OKAY [ -0.000s]
finished. total time: -0.000s

EDIT:
on official HTC dev webpage it says command is fastboot oem lock
 
Last edited:
Problem is exactly as @Hadron and @saltire said, I'll say it a different way - the storage partitions on that phone have been obliterated. Tinkering with bootloader options will get you nowhere.

I've not seen one this bad in a long time.

If the phone can't be locked and an RUU applied then almost a certainty that you've got a paperweight.
 
guys do this numbers mean something? i dont know how i managed to change them but does it mean i can write to storage somehow?

C:\sdk-tools>fastboot flash recovery twrp.img
target reported max download size of 1830719488 bytes <--------
sending 'recovery' (16086 KB)...
OKAY [ 1.436s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.498s

C:\sdk-tools>fastboot flash recovery twrp.img
target reported max download size of 1830727680 bytes <--------
sending 'recovery' (16086 KB)...
OKAY [ 1.428s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.506s
 
It means that your partition table - defining the size of each installable and usable component - is completely shot and conventional fastboot flash installation attempts won't work.

The RUU not only flashes each one, it rebuilds that table so that you can.

I've not seen jtag used for this sort of thing so going back to your previous question, I've no idea.

Perhaps @scotty85 would know.
 
jtag could be an option, as is selling for parts. Do you know when your mate got the phone? I'd still consider contacting HTC, although we do have different consumer protection in place in the UK so not sure how second ownership affects warranty where you are. At the moment though the bootloader doesn't show tampered (eg no custom recovery installed) so only current evidence of modification is the bootloader being unlocked - you never know.
 
I saw a guy recently - with the help of the Internet - try to use dd to install recovery and software on the One M7. Same thing, obliterated his partitions.

The phone may not say tampered - but unlocked and completely unreadable firmware is not likely to go well for any claims. Just saying...
 
It's a direct disk write utility sometimes used for various mods or writing or extracting partition information.

Very dangerous unless you're experienced in Unix systems level work.

And therefore one of the things that people doing Internet searches find and often experiment with - almost always with disastrous results.

Zero need to ever go near an M8 with it. Zero.

My speculation is that may have been used to get the phone that screwed up. No way to be sure - but whatever was done was artful.
 
You must log in or register to reply here.
Back
Top Bottom