I've never hard bricked a phone. I've never seen one either. But hard bricking is everyone's worst nightmare.

I wan't to know what exactly happens when you hard brick your phone. What happens that makes it irrecoverable without professional help?

To find this out, I needed to know how flashing of ROMs work. For this, I downloaded the data sheet for my phone's chipset (an MTK6589, whose datasheet can be found here) and then found out that:

  • The USB data lines D+ and D- and VCC goes directly to the application processer.
  • There is an external PMIC for application processor that handles the power ON and OFF of the handset. On this IC there are two pins(KP_KOL0 and KP_ROM0) which when are 0, triggers USB download without battery.
  • The memory (eMMC or NAND Flash) to which the files are downloaded is also connected to the Processor via a External Memory Interface (EMI).

So this is what (I think) happens when you flash a wrong ROM:

Though I don't know what results in 0V on pins KP_KOL0 and KP_ROM0, but this happens when you want to download a new ROM, and the application processor switches/starts in Download mode.

I've googled what happens when you hard brick a phone. All I get are noob posts telling how or how not to hard brick your phone. Most of the posts say that when you flash the wrong ROM, the phone may get hard bricked. My question is,

What happens when you flash a wrong ROM that makes the phone hard bricked?

Or why does the processor become not responding at all when you hard brick it?

2 Answers 2


It has nothing to do with the processor, unless you've fried it.

Usually, the only software-based hard brick that is possible is when you overwrite the bootloader. Without a (working) bootloader, the phone (a) cannot get to the point where it would load the operating system and/or (b) cannot have working software loaded onto it.

If you get into this state you need to access the hardware more directly to write a new bootloader, often using JTAG.

  • Or you could just backup your bootloader and then restore it using dd Sep 11, 2015 at 18:38
  • 10
    @vishalbiswas Yeah, and how are you going to restore it with dd if the bootloader isn't working?
    – Léo Lam
    Sep 11, 2015 at 20:51
  • @vishalbiswas See Android Boot Process. (Source)
    – Firelord
    Sep 11, 2015 at 22:24
  • 2
    @vishalbiswas I think OP intended "hard brick" to mean the recovery / secondary boot loader is not intact. forums.androidcentral.com/android-4-1-4-2-4-3-jelly-bean/…
    – rakslice
    Sep 12, 2015 at 3:19
  • 1
    To expand on point (b). As there is no program loaded to communicate over a USB connection, you can never flash anything else using the resources on the phone. All "soft" methods require the phone's CPU to write to its own NAND, even when connected to a PC.
    – jiggunjer
    Nov 6, 2015 at 17:24

For it to be possible to hard brick a phone, some of the software that the phone has to run to boot and flash itself -- something from the point where it's a just-powered-on processor running address 0 to the point where the phone is writing a new image to flash -- needs to be itself in flash that the phone can write. Usually this is something like a secondary boot loader. If you erase that, then you can't reflash anymore. Hard bricked.

On a phone where you can write something new with only the aid of whatever software is in ROM that the phone can't write, whether or not it's by shorting a couple of pins and there's USB straight into the processor, you can't truly "hard brick" the phone. Unbricking would always be possible at least in theory, provided you can feed it the firmware in whatever format it needs.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .