[tut][update] How to Unbrick and revive a totally lifeless Xiaomi Mi-Pad

Search This thread

prahladyeri

Senior Member
Jun 2, 2013
79
34
India
prahladyeri.github.io
Be warned: Your Warranty will become void by using this method

Last week, my brand new Xiaomi Mi-Pad arrived via Flipkart and no sooner did I have it in my hands, I started installing useful apps like Greenify, ES File Explorer, etc. Two days went by and I was disappointed to learn that it doesn’t support a USB Dongle (Data Card) which is a very common method of Internet access in India. The only way I could have it was to root the tablet. And it was while rooting using SuperSU app that I foolishly selected a wrong click and ended up bricking my brand new tablet.

The Problem


It was a hard brick, meaning my tablet showed no signs of life when switched on or connected to a PC through a USB cable. Had it been a soft brick, meaning that I were able to boot to MIUI Recovery by pressing Power+UpVolume or to FastBoot Recovery by pressing Power+DnVolume button, it would have been easy to recover. But my tablet was totally dead. Even after charging for next 6 hours, all it did was light up a black LED screen for a second or two and then vanished for any combination of those buttons.
The problem was that the wrong click that I made had caused the tablet bootloader to be corrupted. And in the android world, if the bootloader is lost, then your device is literally as useful as a brick! Unlike 8086 PCs, android tablets don’t have a hard-wired BIOS to recover things from, the bootloader is as good as the BIOS.

The Research

Now obviously, I was disappointed and annoyed. After spending ₹10,999 on a brand new tablet, this was not what I was hoping for. Getting service from a Xiaomi service center was not an option as they are very rare in India. Besides, OEMs hardly provide warranty/support to people who try and root their devices, do they? So naturally, I had to myself find a way out of this. My research finally led me to a post by a Russian hacker who had successfully revived the tablet from this very situation. In this article, I’ll note down exactly what steps I had taken to revive it and hope that someone might find it useful.

The Solution


Though the solution is easy and straight-forward, there are some tricky areas where you might run into trouble. If you don’t have the confidence to open up an electronic device using a screwdriver or flash a stock ROM, just say quits and if possible, ask help from someone you know who is used to do it. Basically, the process involves this:


  • Open the back-cover by separating it from the screen (fingernails or a sharp object will do) and unscrew the plastic panel that covers the top area of the motherboard.
  • Disconnect the battery by slowly pulling the power belt (using a flat-head screwdriver or any sharp object).
  • Connect the USB cable to Mi-Pad end (but not the PC end yet).
  • Create a short circuit between the two tiny pads inside the MicroSD card slot using a metal object or wire.
  • Connect the USB cable to the PC end.

If done properly, the PC will detect a Nvidia Boot Recovery for Mobile USB device and then you can flash your stock ROM using Xiaomi’s flashing software, Mi Flash Tool, thus putting the life back into your tablet.

The Magic


The most tricky and magical aspect of this whole process is the short-circuiting in step four. Firstly, it is not easily diagnosable. The Nvidia USB driver is in fact detected by the PC even if you don’t create the short-circuit (but the battery needs to be disconnected of course), but then it will disappear instantly and you won’t get the time to flash your stock ROM. For some unknown laws of electricity (or maybe the laws coded inside this Nvidia driver), the short-circuit may not work instantly the first time. You’ll create the short-circuit, connect to the USB port and hear the Windows beep sound for USB connection, but moments later you will hear another beep of disconnection. If that happens, you’ll have to disconnect the USB cable and repeat from step-4: Create the short-circuit again and reconnect to the USB port - I had to do this about 50 times before the connection was stable enough for me to flash the ROM.
Some forum posts advice you to plug in the power belt at exactly the same time as the USB connection is detected in the PC. However, I’ve found that its not true. Not once did I put the power belt back in the whole process until the ROM had been flashed completely.


The Weapon


You can use any metallic object to create the short circuit, even a tiny wire could be used. The important thing is that those two minuscule pads inside the MicroSD slot are connected by a metal. Personally, I used this tiny pin that came with the booklet along with the Mi-Pad itself!

short.jpg



All I did was place that pin inside the MicroSD slot, so it created a bridge on top of those two pads, and supported the pin using any available object (in this case a screwdriver).
You’ll also need a 2.0mm screwdriver to open the back-panel above the motherboard. Please remember that opening those screws are going to void your warranty (which is going to happen in any case since you either tried to root or used the dd command to rewrite partitions in order to reach this stage!).
On your Windows PC, you need the following installed:
  1. Latest version of Mi Flash Tool (Can be downloaded here).
  2. Latest version of Mi Phone Manager PC Suite for the Nvidia drivers (Can be downloaded here).
Alternatively, you can download the whole bundled software from here that comes with Mi Flash Tool, NVidia Drivers and ADB Drivers too.

You’ll also need to download the latest MIUI stock ROM for Mi-Pad from here and extract somewhere on your PC to flash it later.

Once your short-circuit works and the connection stays stable, waste no more time. Just fire up the Mi Flash tool and select the path to the ROM image you just extracted and click the flash button. Once the flash is successful, assemble back your Mi-Pad and on pressing the power button, you should see this:

MIUI.jpg



Summary

Keep a cool mind and do it, it can be done! If you can’t do it, try and find a mobile repair shop nearby or catch a tech enthusiast in your circle who can do it.

References


Edit

As noted elsewhere, this is not a sure-shot or guaranteed way to recovery. Depending on other factors like what you originally did to cause the hard-brick and whether or not you were flashing the correct ROM, you may or may not be able to resuscitate this device. Apparently, based on the observations and discussions on the Xiaomi support forums, Xiaomi motherboards (and especially the eMMC) are known to get damaged under the following situations:


1. You tried to alter existing partitions using the parted tool.
2. You tried to flash an incorrect ROM.


So, if you had done such a thing and caused yourself a hard-brick, the better idea is to hand it over to a Xiaomi service center directly (or hand it to your local service center and they will send it to China). However, this seems to be specific to Xiaomi and Nvidia - I've altered partitions and flashed ROMs with several MediaTek SoC based phones before and never had such an issue, so Nvidia might be having answers to lots of our woes here.
 
Last edited:

chetzrao

Member
Mar 2, 2010
6
0
Louisville
Thank you for the instructions. Will try them out over the weekend.
I am in the same boat... an incorrect recovery flash bricked my device.
However, can you please point out which one is the power belt to be pulled out?
 

prahladyeri

Senior Member
Jun 2, 2013
79
34
India
prahladyeri.github.io
can you please point out which one is the power belt to be pulled out?

Have a look at this original post. There is an green arrow above the battery area where the power-belt is marked. However, I hope you didn't try to flash the ROM of an entirely different device? If that happens, hope of recovery is little as Xiomi devices are known to get their motherboards damaged in that case.
 
  • Like
Reactions: Kamal Nagula

chetzrao

Member
Mar 2, 2010
6
0
Louisville
Tried all the steps after shorting the two pins (stable)... MiFlash said operation completed successfully in 93s. But, the battery had completely died so the device didn't boot... charging it now...
However, I think the MiPad is now resuscitated. Many thanks for your post. Saved a great device.
 
Last edited:

prahladyeri

Senior Member
Jun 2, 2013
79
34
India
prahladyeri.github.io
Tried all the steps after shorting the two pins (stable)... MiFlash said operation completed successfully in 93s. But, the battery had completely died so the device didn't boot... charging it now...
However, I think the MiPad is now resuscitated. Many thanks for your post. Saved a great device.
Great! Let us know whether you were able to start the device and what had caused the brick originally? (Will be useful for documentation).
 

prahladyeri

Senior Member
Jun 2, 2013
79
34
India
prahladyeri.github.io
If NVIDIA drivers are connected and the USB connection is stable, you should just flash the latest ROM for MiPAD and be done.

If the connection is not stable, check whether you are doing the short-circuit properly? Refer to the original diagram I've attached for creating the short circuit.
 

chetzrao

Member
Mar 2, 2010
6
0
Louisville
Great! Let us know whether you were able to start the device and what had caused the brick originally? (Will be useful for documentation).

Sorry for the delayed response.

YES. The device is now fully back to normal... thank you once gain for the instructions... getting the short between the pins is the tricky bit... I managed it by twisting the ends of a safety pin and wedging them under the MicroSD frame.
The original cause of the brick was flashing a wrong version of CWM.
 

prahladyeri

Senior Member
Jun 2, 2013
79
34
India
prahladyeri.github.io
Sorry for the delayed response.

YES. The device is now fully back to normal... thank you once gain for the instructions... getting the short between the pins is the tricky bit... I managed it by twisting the ends of a safety pin and wedging them under the MicroSD frame.
The original cause of the brick was flashing a wrong version of CWM.
Great! Glad to know that.
 
  • Like
Reactions: RahulTheVirus

l0stb0t

New member
Sep 29, 2014
1
0
Code:
[00000468]CreateManagedObject(1261): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1305): Unspecified error(0x80131604)
[00000468]CreateManagedObject(1261): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1305): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00000468]GetSearchPath(1381): The specified service does not exist.(0x800704db)
[00001308]0	0.00	execute C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\nvflash_all.bat
[00001308]0	0.03	
[00001308]0	0.03	$pushd C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\images 
[00001308]0	0.03	
[00001308]0	0.03	$nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go 
[00001308]0	1.80	Nvflash 4.13.0000 started
[00001308]0	1.80	chip uid from BR is: 0x34001001740d01480800000001ff0080
[00001308]0	1.80	rcm version 0X400001
[00001308]0	1.80	Skipping BoardID read at miniloader level
[00001308]0	1.80	System Information:
[00001308]0	1.80	   chip name: unknown
[00001308]0	1.80	   chip id: 0x40 major: 1 minor: 1
[00001308]0	1.80	   chip sku: 0x0
[00001308]0	1.80	   chip uid: 0x00000000000000000000000000000000
[00001308]0	1.80	   macrovision: disabled
[00001308]0	1.80	   hdcp: disabled
[00001308]0	1.80	   jtag: disabled
[00001308]0	1.80	   sbk burned: false
[00001308]0	1.80	   board id: 0
[00001308]0	1.80	   warranty fuse: 0
[00001308]0	1.80	   dk burned: false
[00001308]0	1.80	   boot device: emmc
[00001308]0	1.80	   operating mode: 3
[00001308]0	1.80	   device config strap: 0
[00001308]0	1.80	   device config fuse: 0
[00001308]0	1.80	   sdram config strap: 0
[00001308]0	1.80	
[00001308]0	1.80	RCM communication completed
[00001308]0	1.80	BCT sent successfully
[00001308]0	1.80	odm data: 0x49c000
[00001308]0	1.80	downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
[00001308]0	1.80	sending file: bootloader.bin
[00001308]0	1.80	
[00001308]0	1.80	- 1048576/4194304 bytes sent
[00001308]0	1.80	\ 2097152/4194304 bytes sent
[00001308]0	1.80	| 3145728/4194304 bytes sent
[00001308]0	1.80	/ 4194304/4194304 bytes sent
[00001308]0	1.80	bootloader.bin sent successfully
[00001308]0	1.80	waiting for bootloader to initialize
[00001308]0	1.80	bootloader downloaded successfully
[00001308]0	1.80	ML execution and Cpu Handover took 1 Secs
[00001308]0	1.80	setting device: 2 3
[00001308]0	1.80	creating partition: BCT
[00001308]0	1.80	failed executing command 17 NvError 0x120002
[00001308]CScriptReport::DoWork(413): Unspecified error(0x80004005)
[00001308]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00001308]SaveFlashResult(1347): The specified service does not exist.(0x800704db)
[00000468]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00000468]GetSearchPath(1381): The specified service does not exist.(0x800704db)
[000004BC]0	0.00	execute C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\nvflash_all.bat
[000004BC]0	0.03	
[000004BC]0	0.03	$pushd C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\images 
[000004BC]0	0.05	
[000004BC]0	0.05	$nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go
Please help!
 
Last edited:

anware

Member
Jun 24, 2011
10
5
Thank you!! It worked!

Finally after 4 hours of effort, got my Mi Pad working! The process does work! Had to log in and post and reply. Thank you @prahladyeri. :D :good:

What had happened:
Wrong click during SuperSU update. After that no boot. Screen lights up, but stays blank. No MI logo. No Fastboot. No Recovery. No battery charging/LED indication.

What worked for me
Here's the step by step of what worked for me after a lot of trial and error.
  1. Downloaded all necessary files. Downloaded MiFlashTool from Xiaomi Tips (v20160830) - did not install. Downloaded Fastboot ROM (MiPad Global). Had already installed Mi PC Suite.
  2. Uninstalled everything installed earlier (excluding MI PC Suite).
  3. Restarted Windows 10 and disabled driver signature verification. Just hold shift when clicking restart in the windows power menu.
  4. Installed MiFlash. Checked log in <the drive you installed Mi Flash in>:\XiaoMi\XiaoMiFlash\Log. Verified whether the result for all driver installation is 'true'.
  5. Removed back cover and panel. Disconnected battery belt. Took a regular paper clip and created a small 'v' shaped object. Bent the ends to look like the paws of a dog's front legs when standing on its hind legs (sorry, not really a great description, but there it is :p). Created a short circuit using the clip.
  6. Connected to PC. PC beeps for connection. Thankfully connection remains stable (I did not connect the power belt; let the clip stay).
  7. Dev Manager shows 'APX'. Update driver by pointing to MiFlash folder. Driver installs successfully.
  8. Open MiFlash. Select ROM.
  9. Refresh MiFlash. Device shows '0'. I say what the heck and click Flash. Starts flashing but shows device busy and pauses. At this point I am about to give up again. But suddenly the Gods of Android smile on me, and it flashes.
  10. 73s later I see a successful message and a sigh of relief escapes my lips.
  11. Remove clip. Connect battery. Reassemble pad.
  12. Turn on Pad and Voila! MI logo!

Hope this helps or at least encourages ('coz I know how frustrating it was to get it to work).
 

Epipong

Member
Mar 21, 2015
7
0
30
Paris
Thanks very much, I fixed my MiPad 1 year later !

I succeed to using aluminum foil (easiest way) and when I connected my MiPad to the PC I directly reconnected the battery and flash without disconnect device and it's worked !

I used MiFlash 20151028 instead of 20160830 and download ROM like this mocha_images_4.11.21_4.4_cn_7352dcd481.tgz
 
Last edited:

jobinslmn

New member
Dec 20, 2014
3
2
Just a small point for clarity, my MI pad got bricked with the wrong click in supersu. I did not unlock my MI pad ever since I bought it with MI unlocked tool provided by MI. But did root the tab with kingroot desktop app which showed fastboot logo in between the rooting process. Sould I be worried because I'm planning to do the same procedure. Waiting for your approva
Thanks
 

prahladyeri

Senior Member
Jun 2, 2013
79
34
India
prahladyeri.github.io
Try all the "soft-unbrick" methods first before trying this out

Just a small point for clarity, my MI pad got bricked with the wrong click in supersu. I did not unlock my MI pad ever since I bought it with MI unlocked tool provided by MI. But did root the tab with kingroot desktop app which showed fastboot logo in between the rooting process. Sould I be worried because I'm planning to do the same procedure. Waiting for your approva
Thanks

Make sure you try the usual "soft-unbrick" methods first (like recharging it overnight and various power button combinations(power+up, power+dn, etc)). This method has to be the last resort. Though there isn't anything specific you need to worry about and usually it works, the short-circuit is tricky and needs to be done very correctly so that the USB connection stays stable which is essential to flash the MiPad.
 
  • Like
Reactions: jobinslmn

prahladyeri

Senior Member
Jun 2, 2013
79
34
India
prahladyeri.github.io
Code:
[00000468]CreateManagedObject(1261): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1305): Unspecified error(0x80131604)
[00000468]CreateManagedObject(1261): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1305): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00000468]GetSearchPath(1381): The specified service does not exist.(0x800704db)
[00001308]0	0.00	execute C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\nvflash_all.bat
[00001308]0	0.03	
[00001308]0	0.03	$pushd C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\images 
[00001308]0	0.03	
[00001308]0	0.03	$nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go 
[00001308]0	1.80	Nvflash 4.13.0000 started
[00001308]0	1.80	chip uid from BR is: 0x34001001740d01480800000001ff0080
[00001308]0	1.80	rcm version 0X400001
[00001308]0	1.80	Skipping BoardID read at miniloader level
[00001308]0	1.80	System Information:
[00001308]0	1.80	   chip name: unknown
[00001308]0	1.80	   chip id: 0x40 major: 1 minor: 1
[00001308]0	1.80	   chip sku: 0x0
[00001308]0	1.80	   chip uid: 0x00000000000000000000000000000000
[00001308]0	1.80	   macrovision: disabled
[00001308]0	1.80	   hdcp: disabled
[00001308]0	1.80	   jtag: disabled
[00001308]0	1.80	   sbk burned: false
[00001308]0	1.80	   board id: 0
[00001308]0	1.80	   warranty fuse: 0
[00001308]0	1.80	   dk burned: false
[00001308]0	1.80	   boot device: emmc
[00001308]0	1.80	   operating mode: 3
[00001308]0	1.80	   device config strap: 0
[00001308]0	1.80	   device config fuse: 0
[00001308]0	1.80	   sdram config strap: 0
[00001308]0	1.80	
[00001308]0	1.80	RCM communication completed
[00001308]0	1.80	BCT sent successfully
[00001308]0	1.80	odm data: 0x49c000
[00001308]0	1.80	downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
[00001308]0	1.80	sending file: bootloader.bin
[00001308]0	1.80	
[00001308]0	1.80	- 1048576/4194304 bytes sent
[00001308]0	1.80	\ 2097152/4194304 bytes sent
[00001308]0	1.80	| 3145728/4194304 bytes sent
[00001308]0	1.80	/ 4194304/4194304 bytes sent
[00001308]0	1.80	bootloader.bin sent successfully
[00001308]0	1.80	waiting for bootloader to initialize
[00001308]0	1.80	bootloader downloaded successfully
[00001308]0	1.80	ML execution and Cpu Handover took 1 Secs
[00001308]0	1.80	setting device: 2 3
[00001308]0	1.80	creating partition: BCT
[00001308]0	1.80	failed executing command 17 NvError 0x120002
[00001308]CScriptReport::DoWork(413): Unspecified error(0x80004005)
[00001308]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00001308]SaveFlashResult(1347): The specified service does not exist.(0x800704db)
[00000468]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00000468]GetSearchPath(1381): The specified service does not exist.(0x800704db)
[000004BC]0	0.00	execute C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\nvflash_all.bat
[000004BC]0	0.03	
[000004BC]0	0.03	$pushd C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\images 
[000004BC]0	0.05	
[000004BC]0	0.05	$nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go
Please help!

Did you ever try to re-partition the MiPad any time? If that happens or you tried to flash a wrong version of the ROM, there is the danger of MiPad mother-board getting damaged. Better take it to your nearest Xiaomi service center or send it to China.
 

vchoi13

New member
Oct 8, 2016
2
0
Hi, please help. I managed to get to the part my PC can detect the APX device with Nvidia driver installed. The connection is stable, but I am unable to detect the device on my MIFlash tool version 2016.08.30.0 (I spam Refresh/Flash button but it's not helping). I have disabled driver signature enforcement too.

Do I need to manually enter fastboot mode by pressing the power and volumn down button? I find it very difficult to do that with the casing off.

Let me know if there is anything else I could be missing. Thanks!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 20
    Be warned: Your Warranty will become void by using this method

    Last week, my brand new Xiaomi Mi-Pad arrived via Flipkart and no sooner did I have it in my hands, I started installing useful apps like Greenify, ES File Explorer, etc. Two days went by and I was disappointed to learn that it doesn’t support a USB Dongle (Data Card) which is a very common method of Internet access in India. The only way I could have it was to root the tablet. And it was while rooting using SuperSU app that I foolishly selected a wrong click and ended up bricking my brand new tablet.

    The Problem


    It was a hard brick, meaning my tablet showed no signs of life when switched on or connected to a PC through a USB cable. Had it been a soft brick, meaning that I were able to boot to MIUI Recovery by pressing Power+UpVolume or to FastBoot Recovery by pressing Power+DnVolume button, it would have been easy to recover. But my tablet was totally dead. Even after charging for next 6 hours, all it did was light up a black LED screen for a second or two and then vanished for any combination of those buttons.
    The problem was that the wrong click that I made had caused the tablet bootloader to be corrupted. And in the android world, if the bootloader is lost, then your device is literally as useful as a brick! Unlike 8086 PCs, android tablets don’t have a hard-wired BIOS to recover things from, the bootloader is as good as the BIOS.

    The Research

    Now obviously, I was disappointed and annoyed. After spending ₹10,999 on a brand new tablet, this was not what I was hoping for. Getting service from a Xiaomi service center was not an option as they are very rare in India. Besides, OEMs hardly provide warranty/support to people who try and root their devices, do they? So naturally, I had to myself find a way out of this. My research finally led me to a post by a Russian hacker who had successfully revived the tablet from this very situation. In this article, I’ll note down exactly what steps I had taken to revive it and hope that someone might find it useful.

    The Solution


    Though the solution is easy and straight-forward, there are some tricky areas where you might run into trouble. If you don’t have the confidence to open up an electronic device using a screwdriver or flash a stock ROM, just say quits and if possible, ask help from someone you know who is used to do it. Basically, the process involves this:


    • Open the back-cover by separating it from the screen (fingernails or a sharp object will do) and unscrew the plastic panel that covers the top area of the motherboard.
    • Disconnect the battery by slowly pulling the power belt (using a flat-head screwdriver or any sharp object).
    • Connect the USB cable to Mi-Pad end (but not the PC end yet).
    • Create a short circuit between the two tiny pads inside the MicroSD card slot using a metal object or wire.
    • Connect the USB cable to the PC end.

    If done properly, the PC will detect a Nvidia Boot Recovery for Mobile USB device and then you can flash your stock ROM using Xiaomi’s flashing software, Mi Flash Tool, thus putting the life back into your tablet.

    The Magic


    The most tricky and magical aspect of this whole process is the short-circuiting in step four. Firstly, it is not easily diagnosable. The Nvidia USB driver is in fact detected by the PC even if you don’t create the short-circuit (but the battery needs to be disconnected of course), but then it will disappear instantly and you won’t get the time to flash your stock ROM. For some unknown laws of electricity (or maybe the laws coded inside this Nvidia driver), the short-circuit may not work instantly the first time. You’ll create the short-circuit, connect to the USB port and hear the Windows beep sound for USB connection, but moments later you will hear another beep of disconnection. If that happens, you’ll have to disconnect the USB cable and repeat from step-4: Create the short-circuit again and reconnect to the USB port - I had to do this about 50 times before the connection was stable enough for me to flash the ROM.
    Some forum posts advice you to plug in the power belt at exactly the same time as the USB connection is detected in the PC. However, I’ve found that its not true. Not once did I put the power belt back in the whole process until the ROM had been flashed completely.


    The Weapon


    You can use any metallic object to create the short circuit, even a tiny wire could be used. The important thing is that those two minuscule pads inside the MicroSD slot are connected by a metal. Personally, I used this tiny pin that came with the booklet along with the Mi-Pad itself!

    short.jpg



    All I did was place that pin inside the MicroSD slot, so it created a bridge on top of those two pads, and supported the pin using any available object (in this case a screwdriver).
    You’ll also need a 2.0mm screwdriver to open the back-panel above the motherboard. Please remember that opening those screws are going to void your warranty (which is going to happen in any case since you either tried to root or used the dd command to rewrite partitions in order to reach this stage!).
    On your Windows PC, you need the following installed:
    1. Latest version of Mi Flash Tool (Can be downloaded here).
    2. Latest version of Mi Phone Manager PC Suite for the Nvidia drivers (Can be downloaded here).
    Alternatively, you can download the whole bundled software from here that comes with Mi Flash Tool, NVidia Drivers and ADB Drivers too.

    You’ll also need to download the latest MIUI stock ROM for Mi-Pad from here and extract somewhere on your PC to flash it later.

    Once your short-circuit works and the connection stays stable, waste no more time. Just fire up the Mi Flash tool and select the path to the ROM image you just extracted and click the flash button. Once the flash is successful, assemble back your Mi-Pad and on pressing the power button, you should see this:

    MIUI.jpg



    Summary

    Keep a cool mind and do it, it can be done! If you can’t do it, try and find a mobile repair shop nearby or catch a tech enthusiast in your circle who can do it.

    References


    Edit

    As noted elsewhere, this is not a sure-shot or guaranteed way to recovery. Depending on other factors like what you originally did to cause the hard-brick and whether or not you were flashing the correct ROM, you may or may not be able to resuscitate this device. Apparently, based on the observations and discussions on the Xiaomi support forums, Xiaomi motherboards (and especially the eMMC) are known to get damaged under the following situations:


    1. You tried to alter existing partitions using the parted tool.
    2. You tried to flash an incorrect ROM.


    So, if you had done such a thing and caused yourself a hard-brick, the better idea is to hand it over to a Xiaomi service center directly (or hand it to your local service center and they will send it to China). However, this seems to be specific to Xiaomi and Nvidia - I've altered partitions and flashed ROMs with several MediaTek SoC based phones before and never had such an issue, so Nvidia might be having answers to lots of our woes here.
    4
    Thank you!! It worked!

    Finally after 4 hours of effort, got my Mi Pad working! The process does work! Had to log in and post and reply. Thank you @prahladyeri. :D :good:

    What had happened:
    Wrong click during SuperSU update. After that no boot. Screen lights up, but stays blank. No MI logo. No Fastboot. No Recovery. No battery charging/LED indication.

    What worked for me
    Here's the step by step of what worked for me after a lot of trial and error.
    1. Downloaded all necessary files. Downloaded MiFlashTool from Xiaomi Tips (v20160830) - did not install. Downloaded Fastboot ROM (MiPad Global). Had already installed Mi PC Suite.
    2. Uninstalled everything installed earlier (excluding MI PC Suite).
    3. Restarted Windows 10 and disabled driver signature verification. Just hold shift when clicking restart in the windows power menu.
    4. Installed MiFlash. Checked log in <the drive you installed Mi Flash in>:\XiaoMi\XiaoMiFlash\Log. Verified whether the result for all driver installation is 'true'.
    5. Removed back cover and panel. Disconnected battery belt. Took a regular paper clip and created a small 'v' shaped object. Bent the ends to look like the paws of a dog's front legs when standing on its hind legs (sorry, not really a great description, but there it is :p). Created a short circuit using the clip.
    6. Connected to PC. PC beeps for connection. Thankfully connection remains stable (I did not connect the power belt; let the clip stay).
    7. Dev Manager shows 'APX'. Update driver by pointing to MiFlash folder. Driver installs successfully.
    8. Open MiFlash. Select ROM.
    9. Refresh MiFlash. Device shows '0'. I say what the heck and click Flash. Starts flashing but shows device busy and pauses. At this point I am about to give up again. But suddenly the Gods of Android smile on me, and it flashes.
    10. 73s later I see a successful message and a sigh of relief escapes my lips.
    11. Remove clip. Connect battery. Reassemble pad.
    12. Turn on Pad and Voila! MI logo!

    Hope this helps or at least encourages ('coz I know how frustrating it was to get it to work).
    2
    Thanks a ton for the guide.

    My Mi Pad got hard bricked by pressing the wrong button on the update su binary.
    this method is by far the best way to bring mi pad back to life.

    Searched for the method, found this thread,
    i thank the member who came up and guided us by creating this post, also to anyone else whom i left to thank if any. thanks to all the guys without whom this thread was incomplete. you saved my life
    Do the process with a cool mind. it takes time and efforts. so only start to do this when you are free.

    Download :
    Mi pad miui "fast boot" Rom

    Mi flash tool 2015. there's a reason why only any 2015 one. mentioned in the post when you reach that step.

    Mi phone suit.

    that's it. now the process i did.

    preparation Steps:

    (i)go to the Mi pad miui fast boot Rom file. unpacked the tar.gz and then the tar file and keep the folder ready for flash.

    (ii)First disable the "device driver certificate signature check" enforcement by booting using the advanced startup mode. there are other ways to disable it too, for that google it.
    (either restart your PC by pressing Shift+restart button and selecting advanced startup mode or by pressing F8 on boot and selecting advanced start up and then selecting "Disable device driver certificate signature check enforcement mode" by pressing F7.)

    then when you boot install Mi flash 2015 tool and accept the warning for installing unsigned drivers.

    (iii)install Mi phone software suit.

    now comes the actual part :

    (1)opened the mi pad back panel.

    (2)unscrewed all the screws covering the main board and camera area.

    (3)removed the battery cable as indicated in the picture (the middle one).

    (4) best way to create a short circuit is to use a piece of wire. it has much higher rate of success than paper clip and other stuffs.
    creating a short circuit is quite tricky. so if you have an extra hand who could connect the usb plug to the computer for you, while you create a short, then short circuit would be successful on the first time itself.( i got mine successful at 3rd time as i realized that i wont be able to do both things at once. :) ). when the device connects to the PC wait for 15-20 secs with the short circuit for safer side. then you can remove the short circuit.

    Caution : "Mi pad doesn't get detected in Mi flash tool released in 2016 or further. try the 2015 one ;) .

    (5) got the device registered as an APX device. updated the drivers to "nvidia mobile recovery USB drivers" from the Mi flash drivers folder.

    (6)after it has been successfully registered as an nvidia mobile recovery USB device, open up the mi flash tool without wasting time and select the folder that u unzipped in step 1 check the device list again in the tool.
    don't panic if the device shows "0" just flash it. after all you don't have anything to loose even if the flash is unsuccessful. (i thought the same way. after all it was worth a shot.)

    (7) it would take some time between 30 seconds-120 seconds or even more depending the file you selected for flashing, so don't panic just leave it there itself. if there's an error then do the short process again and flash the files.

    (8) after some time when the green bar is full you will receive a message on the right as Rom flashed success or something like that . that means your device is now alive after this long revival treatment from the death. :D

    (9)so plug that battery cable that you removed, place the main board cover back to its place and screw it up, put back the back panel. and voila startup your device . it should show the MI logo.

    if possible keep your device for charging as soon as possible.
    sorry for such a long post.

    Hope this helps. :)
    best of luck!!
    1
    can you please point out which one is the power belt to be pulled out?

    Have a look at this original post. There is an green arrow above the battery area where the power-belt is marked. However, I hope you didn't try to flash the ROM of an entirely different device? If that happens, hope of recovery is little as Xiomi devices are known to get their motherboards damaged in that case.
    1
    I finally got it working after a few hours trying different tools to short the circuit and trying to drivers to work.
    This tool works for me and made the connection stable.
    I had an old Windows 7 laptop so I used that with old MiFlash 2015
    If you get it to stage where it detects as APX device then install Miflash above and it will install the new driver automatically. You have to press "install anyway" on the driver. Windows 10 has higher driver signature enforcement so you need to disable it
    best way is enter advanced options in restart and disable..
    I'm happy to have my old MiPad 1 back. Thank you for the guide and to prahladyeri

    I hard bricked mine by accidently installing CWM bootloader zip file so dont do it.

    Anyone want help can PM me I will try to help as best I can