Database Users

Moto x play com hard brick

People need help. Sorry if'm posting in the wrong place, I'm new here.
I have a Moto X Play (XT1563) And after I flash it to the stock rom 6.0 he installed it right more at the time of restart he did not call more, no charges and no starts in fastboot.
The bootloader it was unlocked, and the battery was at 20% load.
When I plug it in the PC it is recognized as UNKNOWN DEVICE. What I do to try to recover it? as seen videos of people recovering MOTO G1 AND 2, MOTO X 1 and 2. Thank you in advance!​

Rwaan said:
People need help. Sorry if'm posting in the wrong place, I'm new here.
I have a Moto X Play (XT1563) And after I flash it to the stock rom 6.0 he installed it right more at the time of restart he did not call more, no charges and no starts in fastboot.
The bootloader it was unlocked, and the battery was at 20% load.
When I plug it in the PC it is recognized as UNKNOWN DEVICE. What I do to try to recover it? as seen videos of people recovering MOTO G1 AND 2, MOTO X 1 and 2. Thank you in advance!​
Click to expand...
Click to collapse
1st thing is please Charge your moto x play First ,it must be charged at least 50%
2nd I cant understand what u want to say .
So, Please calm Down and Explain It.

xpectedme094 said:
1st thing is please Charge your moto x play First ,it must be charged at least 50%
2nd I cant understand what u want to say .
So, Please calm Down and Explain It.
Click to expand...
Click to collapse
My bike x play does not turn over and not charge or enter the fastboot mode, I was in the custom rom RR 6.0 went back to the stock and the battery was only 20% used the following commands FlashFile file in cmd ...
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
* q in the last command is to restart it hung up and did not care anymore.

Rwaan said:
My bike x play does not turn over and not charge or enter the fastboot mode, I was in the custom rom RR 6.0 went back to the stock and the battery was only 20% used the following commands FlashFile file in cmd ...
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
* q in the last command is to restart it hung up and did not care anymore.
Click to expand...
Click to collapse
If its not charging then there might be problem in your Charging Jack.
First press power Button ( Around 10 sec ) When Screen Off Immediately press Power and Volume less Button.
Bootloader Mode opens .
Connect Your Charger and Check whether Charger Connected or Not ??
Now
I
Came To Your Question * q in the last command is to restart it hung up and did not care anymore. ??
When You Command " fastboot reboot " it hang up to " Bootloader unlock Screen" Its Because might be While Flashing TWRP You by mistakely Remove Your "Boot Image" and Thats Why your Mobile Hang Up.
You should Also Note That All Moto X Play dont have same Boot Image .
You First Need To Download Boot Image Flash It Then Your Problem will sohrtout For Sure.

xpectedme094 said:
If its not charging then there might be problem in your Charging Jack.
First press power Button ( Around 10 sec ) When Screen Off Immediately press Power and Volume less Button.
Bootloader Mode opens .
Connect Your Charger and Check whether Charger Connected or Not ??
Now
I
Came To Your Question * q in the last command is to restart it hung up and did not care anymore. ??
When You Command " fastboot reboot " it hang up to " Bootloader unlock Screen" Its Because might be While Flashing TWRP You by mistakely Remove Your "Boot Image" and Thats Why your Mobile Hang Up.
You should Also Note That All Moto X Play dont have same Boot Image .
You First Need To Download Boot Image Flash It Then Your Problem will sohrtout For Sure.
Click to expand...
Click to collapse
Yes, he hung up and did not care anymore. when I command "Fastboot reboot" he simply hung up and now does not care and neither starts in fastboot and also does not charge. It kind "put out the fastboot mode system" and is being recognized the computer as "unknown device" and has no way gives the flash rom stock because does not start in fastboot mode. He got hardbrick.
more where I download the boot image of it? 're Almost impossible to find a solution to this problem.
* Very need your help, Thank you!:crying:

Rwaan said:
Yes, he hung up and did not care anymore. when I command "Fastboot reboot" he simply hung up and now does not care and neither starts in fastboot and also does not charge. It kind "put out the fastboot mode system" and is being recognized the computer as "unknown device" and has no way gives the flash rom stock because does not start in fastboot mode. He got hardbrick.
more where I download the boot image of it? 're Almost impossible to find a solution to this problem.
* Very need your help, Thank you!:crying:
Click to expand...
Click to collapse
Try Flashing Firmware through RSD Lite ( Note RSD Lite Cant support Window 10)
and Please Give me Some more information .
1. Do Bootloader Mode Open or Not.
2. What Command You Exactly use when your cell Bricked .
and please reply fast.

xpectedme094 said:
Try Flashing Firmware through RSD Lite ( Note RSD Lite Cant support Window 10)
and Please Give me Some more information .
1. Do Bootloader Mode Open or Not.
2. What Command You Exactly use when your cell Bricked .
and please reply fast.
Click to expand...
Click to collapse
1. He does not enter the bootloader mode. You can not use RSD Lite to be able to give him the flash, the RSD does not recognize him because he does not enter the fastboot mode, moto x play he does nothing're completely off. when I connect the computer it is always recognized as "unknown device" so I can not give it flash or the cmd and not by RSD Lite.
2.I used all of the commands but did not pay attention had given error in any command more in the last it is simply reset the device he hung up and did not care anymore. Ai can not do anything it just know that he ta working as it appears on the computer when I connect it, the following NOTIFICATION ...
"USB Device Not Recognized,
* installing drivers ... failure.
* Unknown device. "
Every time I connect it to the computer appears such reports and have all the drivers installed and already uninstalled and installed back more not decided.

someone there gives me the file "bootloader singleimage.bin" Moto X Play (XT1563) and drivers "Qualcomm HS-USB qdloader 9008 (com12)" for me to recover my device a Hard Brick. Thanks in advance.

I have the same problem
Rwaan said:
someone there gives me the file "bootloader singleimage.bin" Moto X Play (XT1563) and drivers "Qualcomm HS-USB qdloader 9008 (com12)" for me to recover my device a Hard Brick. Thanks in advance.
Click to expand...
Click to collapse
I have the same problem, Can you send me the files? please. do you advance with the thing? (sorry for my poor english)

laloraptor said:
I have the same problem, Can you send me the files? please. do you advance with the thing? (sorry for my poor english)
Click to expand...
Click to collapse
I have the files that can fix my machine, since'm two months without any solution. I need the files to resurrect my Moto X Play With HardBrick.
Who has the files please makes a uploud and I send. My Gmail is [email protected].
thank you!

I have same problem, my moto x play is hard bricked and gets only detected as qdloader Q9008. I am looking for the blank flash files, something like prog_emmc_firehose_8939.mbn

i also have hard bricked ( Qloader 9008 )

Did someone find a solution? Mine is also hard bricked the exact same way.

hi there I am in the same situation! any solution? any ideas?

gilbertoperezx1 said:
hi there I am in the same situation! any solution? any ideas?
Click to expand...
Click to collapse
It can be revived either by Blank flash files or by easy jtag emmc flash.. Unfortunately no one is having blank flash files.. Hopefully someone will come up with a blank flash file.. If you want to fix it quicky, then only way is flashing emmc by easy jtag box.. Like the video below..
https://www.youtube.com/watch?v=t7ZzeRGOoEw&feature=youtu.be

Moto x play hard brick
Moto x play turned off after an update and did not turn on nor does it give a precise signal of the files BlankFlash for XT1563

alexmota00 said:
Moto x play turned off after an update and did not turn on nor does it give a precise signal of the files BlankFlash for XT1563
Click to expand...
Click to collapse
Its hard bricked and no blank files aren't working as of now.. We have started a telegram group of those who got their MXp's hard bricked.. You can join too if like.. Here is the link : https://t.me/Unbrick_MXP

i have the same problem hardbrick please send me file. my mail [email protected]

david livingstone said:
i have the same problem hardbrick please send me file. my mail [email protected]
Click to expand...
Click to collapse
There is no working files available as of now..

share to me please have the same problem
Have the same problems please share to me this files
[email protected]

Complicated problem, never came across in the whole lifetime of my android usage.

TLR: Phone boots up and says. Launcher has stopped working, contacts has stopped working and etc.
Ok so i bought Moto G4 XT1625, yesterday. Was very happy with the device. It came with Android 6.0.1, i updated it to nougat 7.0.
But in android 6.0 and 7.0 both i noticed the phone giving random apps freezes and randomly even restarting on 7.0. The problem was minimal so i rebooted the phone 2,3 times and made it working. Then i received another update "NPJS25.93-14-4" on that update the phone got successful but bootlooped when booting for the first time on that update. I thoughts its ok so rebooted to bootloader and booted the phone from bootloader. the phone booted. after that another update came "NPJS25.93-14- (5 or 8) i dont remember properly" in this update the update failed during the installation. Keep in mind that i did not touch anything before this update. The phone was totally stock with stock recovery and everything. On this update the phone failed the update and i got constant bootloop no matter if i factory reset or erase cache it kept bootlooping, now i unlocked the bootloader and installed twrp and flashed a custom stock rom it crash on the boot. Again the random app has stopped working error came continously making the phone unusable. Then i flashed the stock rom correct firmware and everything it bootlooped again, then i rebooted numerous times the phone booted fine. Installed apps. This time did not get any app has stopped working error. Then rebooted the phone to install the sim card phone bootlooped again. Im 99% sure this is a hardware issue. Can somebody enlighten me? Whats going on in here? Thanks. I never faced this kind of problem ever in my life, i have bought more than 100 devices.

@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.

strongst said:
@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.
Click to expand...
Click to collapse
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!

whizinc said:
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!
Click to expand...
Click to collapse
Good luck:good:

UPDATE
It did not get past the "Checking Network" thing and after pressing the power button screen went black but i could see nav bar and status bar only. The phone has faulty hardware. Im now sure. Going to get it back tomorrow from where i bought it. Lets hope i get a refund or replacement. I bought it from a local mobile mall.

strongst said:
Good luck:good:
Click to expand...
Click to collapse
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working

whizinc said:
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working
Click to expand...
Click to collapse
Have you installed any third-party apps or restored them?

strongst said:
Have you installed any third-party apps or restored them?
Click to expand...
Click to collapse
nope, not a single app. Everything is clean and properly flashed.

whizinc said:
nope, not a single app. Everything is clean and properly flashed.
Click to expand...
Click to collapse
Snapchat is pre-installed?

strongst said:
Snapchat is pre-installed?
Click to expand...
Click to collapse
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.

whizinc said:
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.
Click to expand...
Click to collapse
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?

strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
posted in a new thread because the problem did not belong to the rom's thread, im sorry did i do something wrong? No. I did not flash the stock custom rom before all of this. I never wanted to flash a custom rom. The thing is the phone failed an OTA update which let me to come to this decision. The phone failed ".5" update and after that it bootlooped. So i thought flashing twrp and flash a custom rom with a clean install would fix it but even the custom rom the " xxx app stopped working error" came continously.
After that i followed echo92's guide and flashed the whole stock rom through fastboot. Still same issue. Random apps crashing.
I think this is hardware issue. Because every idea has been fail till now.
What do u say?
edit: note: when the phone failed ".npj25.93-14-5" update it was completely stock and i did not even touch anything, i dont know why it failed on the first place?

strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.

I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.

echo92 said:
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.
Click to expand...
Click to collapse
No no, You got the story wrong. Let me make it correct.
1: Bought the phone from a local mobile mall i have 3 days warranty left. (Phone was on Android 6.0 update)
2: Did not touch the phone. Just installed my daily apps. i.e: whatsapp,facebook and stuff.
3hone started doing odd things like auto touch while charging and apps saying "force stopped" error
4:Then i thought that this is Android 6.0 bug on Moto g4, so i should update it via OTA.
5: Updated to 7.0 same issues.
6:I saw another update did it as well 14-4 update. This update caused bootloop but i managed to make it through by booting from bootloader.
7: Then saw another update 14-5 and that update failed. (WHILE THE WHOLE PHONE WAS ON STOCK STATE) Why did the update fail? I didnt even touch the recovery or anything at that time.
8: Then i flashed the custom rom and the rest of the story goes on as u mentioned in the post.
And yes i cleaned flash the rom with the OEMlock.bat script that the guy above gave to me. It included all things such as boot,modem and all stuff. So it was def a clean install.
"fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot"
This was the script i used to flash the fastboot rom which is 14-4.
Then again got force stop errors and the 14-5 update failed causing bootloop again.
I just have 2 hours to check the devices further or else im gonna return it today. Thanks

MisterSteve said:
I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.
Click to expand...
Click to collapse
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.

whizinc said:
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.
Click to expand...
Click to collapse
Oh, you didn't mention that you have bought a used device! Bring it back to the shop and buy another/new one. Who knows what's wrong with that device or which history it has...

Apologies for getting the story mixed up, the information you provided in your corrected post and subsequently makes the situation worse though. Sounds like you bought a device exhibiting ghost touching or the beginnings of ghost touch and possibly was hard bricked/had the incorrect firmware flashed previously. As strongst mentioned, return that device. It sounds like it'll be more trouble than it's worth... especially for a used device.

UPDATE
I returned the handset to the shop guy, he was skeptical at first but then he gave it to another guy who said that the phone would go in used market claim and then after that he'll either return me the money or give me a new G4 device. I'll have to wait till monday. It sucks. Anyways Thanks alot guys for the help i appreciate it alot.
Feel free to lock the thread @ moderators.

Brick moto g4 xt1622

Hi, yesterday i have unlock bootloader of my moto g4, xt 1622 , i have flashed twrp and this is perfect, but after i have flashed zip of magisk.zip for root permission, when i reboot i obtain only black screen and led white ( intermittence led) .
The device is recognize by windows 10 (in test mode and no signature driver verify ) but not in tray bar..
Mode recognized by pc are:
in fast boot like " fastboot athene_13mp S " in "other device"
In adb mode " sideload" ( from stock recovery) like "Moto g4 plus " in device manager/usb devices"
I have stock recovery and can't start blank flash because the device isn t recognized by pc like qualcomm device..
What can i do??? Thanks a lot my friends!!

The problem is that magisk is not compatible with the Stock kernel, so if you want magisk you need to flash a custom kernel, i recomend this: https://elementalx.org/devices/moto-g4/ you need to flash the kernel and after this flash magisk.
Regards

Wow! So the phone is save? ?
And what can i flash pther kernel, can i have a guide plz? Can i flash with sideload? Thanks!

Yes, you need to enter un recovery, conect your phone to pc and with adb put in the cmd adb sideload nameofyourzip.zip and then flash magisk with sideload if hoy wanr

Unfortunately i recive this error.. what can i do? Thanks!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Ok, first you need to install twrp: https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Then you need to go in twrp to avanced and adb sideload and flash it.

Hmm, can you confirm if you have stock Marshmallow (6.0.1) or Nougat (7.0) on your device? I see from the stock recovery version that it's 6.0.1/MPJ24.139-23-4 (a really old build of Marshmallow).

Thanks ismael! I m going to try it
@ECHO first of this mods, the smartphone have nougat full stock. When i have installed twrp the sistem started normally, but when i flashed magisk the sistem started with black screen, before this i ve factory reset and flash a zip of stock rom.. and start a very problem!!
Thaks a lot to all for help me and sorry for my bad english.
David

scossa1994 said:
Thanks ismael! I m going to try it
@ECHO first of this mods, the smartphone have nougat full stock. When i have installed twrp the sistem started normally, but when i flashed magisk the sistem started with black screen, before this i ve factory reset and flash a zip of stock rom.. and start a very problem!!
Thaks a lot to all for help me and sorry for my bad english.
David
Click to expand...
Click to collapse
Thanks, as Ismael034202 pointed out above, if you were on stock Nougat, then you will need to flash a custom kernel, as rooting on the stock Motorola Nougat kernel will cause a boot failure. If you were still on Nougat, then you could have followed this guide https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 with flashing magisk instead of SuperSU.
As you've re-flashed the old Marshmallow stock ROM, then you do not need a custom kernel (Marshmallow stock ROM kernels are less strict about rooting), flashing TWRP and then flashing magisk should work on Marshmallow.
However, you need to be very careful if you revert back to full stock - as you've appeared to have downgraded from Nougat, taking OTA updates may hard brick your device. If you can remember what Nougat stock ROM you had before unlocking your device, I would recommend downloading a copy of that stock ROM and using the stock ROM to update. Try not to use stock OTA updates.

Very well explained echo92. +1 ?

what can i flash somethings?? because usb debug is off after wipe dataa, and i can t enter in android to activate it!! plz help
i think that android is stock nougat, with old stock recovery and magisk(the real problem) and stock kernel.
what can i solve?
thanks

scossa1994 said:
what can i flash somethings?? because usb debug is off after wipe dataa, and i can t enter in android to activate it!! plz help
i think that android is stock nougat, with old stock recovery and magisk(the real problem) and stock kernel.
what can i solve?
thanks
Click to expand...
Click to collapse
Hmm, in that case, the easiest way may be to flash the latest stock ROM to your device and start over again. As an alternative, do you have a TWRP backup of your device?
For XT1622, you'll likely want NPJS25.93-14-13 (Nougat, 7.0 stock, December 2017 security patch) firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Download and extract as directed in the post, and to flash to repair your device, use the following flashing commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
This should not re-lock your bootloader. Next, download TWRP, ElementalX and magisk and flash as I suggested in the guide above. The basic guide for rooting on Nougat is:
a)Flash/boot TWRP. Backup your device.
b)Flash ElementalX.
c)Flash magisk or SuperSU.
d)Wipe cache/Dalvik in TWRP.
e)Reboot and wait for boot.
f)Any issues, revert to your backup made in a)

Can i use fastboot within debug usb off? Because i recive an error, i m tryng and post a pic.
Thanks
This is my situation after try to use fastboot

Hace you installed Motorola drivers for pc, you can use fastboot without USB debugging
https://mobilesupport.lenovo.com/rola/es/solution/MS89882 This os the link for the fastboot drivers

Thanks guys!! I had write the stock 7.0!! Now the phone is perfect!! Thanks!!
I had wrong driver and pc not recognized the phone!! Now yes ??

Now install twrp, elementalX Kernel, magisk and enjoy

Hi i need urgent help. My Moto g4 plus is not starting anymore. I was using it and but suddenly switched off and nithing works now. Only the led light comes two times when charging cable is connected. Please help help
It was rooted.

Moto Singh said:
Hi i need urgent help. My Moto g4 plus is not starting anymore. I was using it and but suddenly switched off and nithing works now. Only the led light comes two times when charging cable is connected. Please help help
It was rooted.
Click to expand...
Click to collapse
Can you enter in bootloader pressing vol - and power?? If is possible is not problem because you can flash stock rom in fastboot.

scossa1994 said:
Can you enter in bootloader pressing vol - and power?? If is possible is not problem because you can flash stock rom in fastboot.
Click to expand...
Click to collapse
No nothing is working.

Moto Singh said:
No nothing is working.
Click to expand...
Click to collapse
I don t know.. the problem is the corrupted bootloader ( i think..)

Moto G6 Plus - No bootable A/B slot, device not detected with adb.

Hi,
I installed the PPW29.116-20 FIRMWARE for pie 9, it was working fine until I uninstalled magisk and now it will only boot to Fastboot mode saying "No bootable A/B slot".
The problem however it the device it no longer detected in adb to reinstall. adb devices returns no devices. This is odd as it was working fine before.
I have tried with both moto and universal adb drivers, changed cables and even changed computers - nothing it making it appear.
Any help would be much appreciated

Use Fastboot!
Ezcorpia said:
Hi,
I installed the PPW29.116-20 FIRMWARE for pie 9, it was working fine until I uninstalled magisk and now it will only boot to Fastboot mode saying "No bootable A/B slot".
The problem however it the device it no longer detected in adb to reinstall. adb devices returns no devices. This is odd as it was working fine before.
I have tried with both moto and universal adb drivers, changed cables and even changed computers - nothing it making it appear.
Any help would be much appreciated
Click to expand...
Click to collapse
Requirements:
Fastboot (because you're in Fastboot mode, lol) download links for Windows, Linux, Mac.
fastboot images for your ROM e.g. from this thread
fastboot flash file (contains flash commands, see in thread above)
Just unpack the zip file then open cmd/terminal, navigate to that folder and enter:
Code:
fastboot devices
When output looks like this your phone is detected:
Code:
XXXXXXXXX fastboot
'XXXXXXXXX' is your phone's serial number.
Unpack and copy the images and flash file into the same folder as fastboot. The folder contains following files:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On Windows double-click 'flashfileNoErase.bat' (ROM thread).
Check for errors, press enter and the phone will reboot.

had the same issue before
i had the same issue happen to me i about freaked out because i thought i had really jacked my phone up but i found this app called Lenovo Moto Smart Assistant it is a life saver trust me. if this happens to you then just download this app and it will walk you through the rest it has a upgrade and a rescue option the rescue option reinstalls the stock rom and and restores evrything back to normal on your phone. definite must have when flashing roms to your phone. :good:

lassemacchiato said:
Requirements:
Fastboot (because you're in Fastboot mode, lol) download links for Windows, Linux, Mac.
fastboot images for your ROM e.g. from this thread
fastboot flash file (contains flash commands, see in thread above)
Just unpack the zip file then open cmd/terminal, navigate to that folder and enter:
Code:
fastboot devices
When output looks like this your phone is detected:
Code:
XXXXXXXXX fastboot
'XXXXXXXXX' is your phone's serial number.
Unpack and copy the images and flash file into the same folder as fastboot. The folder contains following files:
On Windows double-click 'flashfileNoErase.bat' (ROM thread).
Check for errors, press enter and the phone will reboot.
Click to expand...
Click to collapse
I just want to thank you for this, I have been crying all night because I bricked my phone just a few hours before buying it, please know that you helped a stranger greatly-

#Starlord37# said:
i had the same issue happen to me i about freaked out because i thought i had really jacked my phone up but i found this app called Lenovo Moto Smart Assistant it is a life saver trust me. if this happens to you then just download this app and it will walk you through the rest it has a upgrade and a rescue option the rescue option reinstalls the stock rom and and restores evrything back to normal on your phone. definite must have when flashing roms to your phone. :good:
Click to expand...
Click to collapse
Phone of a friend suddenly died without any reason and wouldn't boot anymore. Tried this software out and it worked straight away. Requires a quick account registration however, but no biggie.
Thank you so much!

lassemacchiato said:
Requirements:
Fastboot (because you're in Fastboot mode, lol) download links for Windows, Linux, Mac.
fastboot images for your ROM e.g. from this thread
fastboot flash file (contains flash commands, see in thread above)
Just unpack the zip file then open cmd/terminal, navigate to that folder and enter:
Code:
fastboot devices
When output looks like this your phone is detected:
Code:
XXXXXXXXX fastboot
'XXXXXXXXX' is your phone's serial number.
Unpack and copy the images and flash file into the same folder as fastboot. The folder contains following files:
On Windows double-click 'flashfileNoErase.bat' (ROM thread).
Check for errors, press enter and the phone will reboot.
Click to expand...
Click to collapse
I dont finding the flashfilenoeraser.bat
But i found...
see bellow
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit

flashfileNoErase.bat
chptr0 said:
I dont finding the file "Flashfilenoeraser". Can u help me?
Click to expand...
Click to collapse
It's an attachment to the ROM thread I linked to.
Here's the direct link (download G6PlusFlashPieOfficial_NoErase.zip, just unpack and you have the right file):
G6PlusFlashPieOfficial.zip
G6PlusFlashPieOfficial_NoErase.zip

lassemacchiato said:
It's an attachment to the ROM thread I linked to.
Here's the direct link (download G6PlusFlashPieOfficial_NoErase.zip, just unpack and you have the right file):
G6PlusFlashPieOfficial.zip
G6PlusFlashPieOfficial_NoErase.zip
Click to expand...
Click to collapse
Thanks for your help!!!

[FIX] Fastboot bootloop fix for Xiaomi Mi Pad 1 (Mocha)

I have flashed so many custom roms on this device and usually never encountered a problem, but just a few days ago,
I flashed a Android 8.1 ROM, with Gapps , Shield Blobs and TOS.
After this my device was stuck in a bootloop and it could never boot into recovery, the Volume + and Power button never really respond,
the only mode working was Fastboot,
But funnily enough, when i entered fastboot, i tried flashing all versions of the Stock Fastboot ROMs, but it never booted into the system, it just stayed in the MI logo screen and continued to either boot again into the MI logo or again to the Fastboot screen.
I tried using all versions of the MI flash tool, thinking maybe it was something wrong with the tool, and since im on Windows 10, tried multiple compatibility modes, such as Windows 7 and 8 but nothing worked.
I thought i had screwed up the partitions in the system since i merged the system 1 and 2 partitions for installing custom roms, but it was not possible to flash a zip file using only fastboot,
Since i was not able to enter recovery i couldnt use ADB.
But today morning,
I was looking at some of the documentations for the Nvidia SOC and found some very valuable instructions, will post them down below,
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra<version>.dtb
The stock ROMs do NOT contain the stock blob file which is needed to actually flash and boot the ROM properly,
So, i downloaded the stock blob file for MI Pad 1 mocha and tried doing it manually by using CMD in fastboot,
Below are the steps which i did,
Firstly, Erase the existing partitions using these commands(order is not important)
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase bootloader
fastboot erase recovery
fastboot erase tos
Then installing the fastboot rom which you can get online, download them and extract them, then go to the image folder inside the ROM folder, and you'll find all the files necessary for the commands below EXCEPT the stock blobs, for which ill add a link here or attach the file.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash tos tos.img
fastboot flash dtb tegra124-mocha.dtb
For the last command, just copy and paste the name of dtb file which you're going to flash and continue normally.
Of all the steps only the 5th and 7th step are really important, which is highlighted.
After finishing flashing all these commands ONE BY ONE ,
Boot your device back into fastboot mode and use the available MI flash tool and continue to flash the fastboot rom again,
After all these steps, if you're lucky, you can successfully boot into your new stock rom,
If you're still experiencing boot loops, as a last resort you can try to short your device using the memory card slot, but be careful you have to disassemble the battery first.
I'll attach all the sources at the end of this thread.
Good luck!
Sources:-
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/shield-tablet/general/adb-fastboot-shield-recovery-image-t2860340
https://forum.xda-developers.com/mi-pad/how-to/tut-how-to-unbrick-revive-totally-t3417604
https://forum.xda-developers.com/mi-pad/how-to/mi-pad-1-hard-brick-revival-how-t3878311

Hi, it feels so good to see that I'm not the only one suffering (suffered in your case) with this problem. I just have a doubt.
We are erasing bootloader in your steps but while again installing all these files we are neither installing any bootloader img nor it is there in the rom package. Now I that that if your bootloader is gone, your device is as good as a brick, for real. Could you shed some light on this?
Awaiting your reply.
Thanks and regards.
EDIT:
I think my tab just died, while flashing tos from minimal adb and fastboot, I noticed the screen was pulsing, fastboot logo was still there but like flickering and fastboot message came back that it failed to write. I disconnected usbcable and reconnected and tab isnt detected, fastboot says target didnt report max download size and windows doesnt see the tab.
I switched off and tried to reboot to fastboot but the tab wont respond anymore. Screen doesnt come on.
What to do?

It is working
The guide was working, although flashing the dtb file wasn't succesfull its working. Later I will update to Custom ROM.

Thanks a lot, got my Pado back to life. As Guy.brush said dtb fails but it still works.

Failed Flashing DTB
I got this error flashing dtb:
C:\adb>fastboot flash dtb C:\adb\mipad\tegra124-mocha.dtb
target reported max download size of 645922816 bytes
sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))
finished. total time: 0.031s
---------- Post added at 03:31 PM ---------- Previous post was at 03:01 PM ----------
C4DXYZ-XDA said:
I got this error flashing dtb:
C:\adb>fastboot flash dtb C:\adb\mipad\tegra124-mocha.dtb
target reported max download size of 645922816 bytes
sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))
finished. total time: 0.031s
Click to expand...
Click to collapse
but it still work.. my mipad is back to life..

adi4u4882 said:
I have flashed so many custom roms on this device and usually never encountered a problem, but just a few days ago,
I flashed a Android 8.1 ROM, with Gapps , Shield Blobs and TOS.
After this my device was stuck in a bootloop and it could never boot into recovery, the Volume + and Power button never really respond,
the only mode working was Fastboot,
But funnily enough, when i entered fastboot, i tried flashing all versions of the Stock Fastboot ROMs, but it never booted into the system, it just stayed in the MI logo screen and continued to either boot again into the MI logo or again to the Fastboot screen.
I tried using all versions of the MI flash tool, thinking maybe it was something wrong with the tool, and since im on Windows 10, tried multiple compatibility modes, such as Windows 7 and 8 but nothing worked.
I thought i had screwed up the partitions in the system since i merged the system 1 and 2 partitions for installing custom roms, but it was not possible to flash a zip file using only fastboot,
Since i was not able to enter recovery i couldnt use ADB.
But today morning,
I was looking at some of the documentations for the Nvidia SOC and found some very valuable instructions, will post them down below,
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra<version>.dtb
The stock ROMs do NOT contain the stock blob file which is needed to actually flash and boot the ROM properly,
So, i downloaded the stock blob file for MI Pad 1 mocha and tried doing it manually by using CMD in fastboot,
Below are the steps which i did,
Firstly, Erase the existing partitions using these commands(order is not important)
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase bootloader
fastboot erase recovery
fastboot erase tos
Then installing the fastboot rom which you can get online, download them and extract them, then go to the image folder inside the ROM folder, and you'll find all the files necessary for the commands below EXCEPT the stock blobs, for which ill add a link here or attach the file.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash tos tos.img
fastboot flash dtb tegra124-mocha.dtb
For the last command, just copy and paste the name of dtb file which you're going to flash and continue normally.
Of all the steps only the 5th and 7th step are really important, which is highlighted.
After finishing flashing all these commands ONE BY ONE ,
Boot your device back into fastboot mode and use the available MI flash tool and continue to flash the fastboot rom again,
After all these steps, if you're lucky, you can successfully boot into your new stock rom,
If you're still experiencing boot loops, as a last resort you can try to short your device using the memory card slot, but be careful you have to disassemble the battery first.
I'll attach all the sources at the end of this thread.
Good luck!
Sources:-
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/shield-tablet/general/adb-fastboot-shield-recovery-image-t2860340
https://forum.xda-developers.com/mi-pad/how-to/tut-how-to-unbrick-revive-totally-t3417604
https://forum.xda-developers.com/mi-pad/how-to/mi-pad-1-hard-brick-revival-how-t3878311
Click to expand...
Click to collapse
Thanks, where could I find rom to get dtb file? Thanks

Wow it is working
Even i got the same error
"sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))"
then I did flash ,using Mi flash tool..
Now it is working fine..
after (2015-2019)so many years.. Today 31st May 2020 device came back to normal..
I tried many methods.. Nothing works..
Thank you so much for this post..
I went to three different MI service center..and many other mobile repair shop..no one did..
You did big help..
Thank you so much..

I followed all the instructions one by one. The process was completed successfully too, except dtb (which error many others have faced). Rebooted. Then flashed the same ROM using MiFlash tool. BUT still my tab is stuck in mi logo. I don't know what to do. Is there anything I am missing during following the instructions? I can still enter into fastboot mode and also recovery; so the tab isn't completely hardbricked though. Please help. I am just stuck in the mi logo.

In my case even it doesn't go to fastboot mode neither recovery. Stuck in mi logo. Please someone help me

While flashing I found that recovery.img and tos.img exists in both the fastboot file and the blobs file. Which one should I use? I tried using the fastboot files but it didn't work out and i'm stuck on the mi logo.
Also while flashing via miflash, got an error :
error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done.
which I found out is to be ignored and the flash will still work. It is just a checkpoint fail because the device wasn't locked during the flashing process. Could it be the issue ?

My Mipad is bricked now,,so I'm working on short mydevice using the memory card slot,.. its kind of tricky to get it back to life again,,hihihihhi,,

Just registered an account to say thank you. I tried flashing original fastboot rom thousands times but no luck. Your guide helped.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm trying like this,, and it worked..

It worked for me.
The "tegra124-mocha.dtb" file can be found within the fastboot rom package that I downloaded named "Xiaomi_Mi_Pad_V8.1.2.0.KXFCNDI_20161128_China_4.4_XFT"
via:
Xiaomi Mi Pad Stock ROM Firmware (Fastboot Flash File)
Download the official Xiaomi Mi Pad Stock ROM Firmware (Flash File) for your Xiaomi Smartphone. We also provide Stock ROM for other Xiaomi devices.
xiaomistockrom.com
Intend to move onto custom rom LOS15 or later...
Wish me luck, read that camera is broken in LOS15-16 for mocha
Now to reinstall TWRP
via:
Download twrp-3.4.0-0-mocha.img
Download page for twrp-3.4.0-0-mocha.img
dl.twrp.me
Then re-merge the partitions.
"Repartition_MI_Pad_1_2GB_zardMi3.zip"
via:
Repartition_MI_Pad_1_2GB_zardMi3.zip | by ANHTUAN9791 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Miui 8 : How To?
Hi, On the recent post, miui 8 is available for the mipad. But before update we need to merge the both partitions. "For Xiaomi MiPAD 1 is required to merge both system partitions" We are invite to follow à link : http://en.miui.com/thread-118294-1-1.html Ok.....but I just understand...
xiaomi.eu
[GUIDE][HOW TO]Flash TWRP And Merge Partitions on Mi Pad 1 (Mocha)
Screenshots will be added later on /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have...
forum.xda-developers.com
LineageOS 16.0 | 19.04.2020 | Shield blobs
LineageOS 16.0 Requirements: 1) active system1 2) merged system partition 3) BRAIN, READING SKILL and presence of basic knowledge about firmware (in the absence need learn to independently) Instruction 1) download TosForPSCI-0.1.zip...
forum.xda-developers.com

This thread & the blob saved my device. Thanks a lot.

Thank you sooo much! It helped to revive my Mi Pad!