[Solved] Unbrick (Hard Bricked/Dead) Motorola G 4 plus or any Qualcomm mobile Device
- Thread starter vijayjadhav_143
- Start date
blankflash for xt1556
Do you have blankflash for xt1556 moto 3g 3 turbo edition?
Thanks!
Do you have blankflash for xt1556 moto 3g 3 turbo edition?
Thanks!
Another Blankflash
Your method works perhaps, any of the blank flash works I have to use another that some one send to me.
[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 2418 (0x972)
[ 0.000] ...cpu.sn = 26899456 (0x19a7400)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.000] ...filename = singleimage.pkg.xml
[ 0.000] Loading programmer
[ 0.000] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 0.231] Handling things over to programmer
[ 0.231] Identifying CPU version
[ 0.231] Waiting for firehose to get ready
[ 3.255] ...MSM8952 1.1
[ 3.255] Determining target secure state
[ 3.255] ...secure = yes
[ 3.255] Flashing GPT...
[ 3.255] Flashing partition:0 with gpt_main0.bin
[ 3.255] Initializing storage
[ 3.271] Configuring device...
[ 3.286] ...blksz = 512
[ 3.355] Re-initializing storage...
[ 3.355] Initializing storage
[ 3.402] Flashing bootloader...
[ 3.402] Flashing aboot with emmc_appsboot.mbn
[ 3.686] Flashing rpm with rpm.mbn
[ 3.754] Flashing tz with tz.mbn
[ 3.954] Flashing hyp with hyp.mbn
[ 4.001] Flashing cmnlib with cmnlib.mbn
[ 4.054] Flashing keymaster with keymaster.mbn
[ 4.133] Flashing sbl1 with sbl1.mbn
[ 4.254] Rebooting to fastboot
[ 4.270] Total time: 4.270s
Here is the file that works, MOTO G4 plus recovered
https://mega.nz/#!RXJjAQ7Z!SRVdrGbtDFPbmSbajOf15bPyyb7DZt3OeqFqFjaQ8Rg
I have successfully recovered my dead/hard brick moto g4 plus mobile using below process.
To give you background, I have hard bricked my new moto g4 plus mobile. To do that, I have unlocked boot loader which void my warranty, then I have rooted yet and got root access. Till that it was working. After that I have installed custom rom cyanogenmod 14.1 . It was still working for some days. Now As I came from blackberry z10 to moto, I was missing blackberry hub features, so I downloaded BlackBerry android OS(Blackberry Priv) and tried to flash it. that's it, it stopped working. I know it was stupid things to do
My mobile was dead for almost 1 month, I tried lots of option, including MI flash tool, QPST(QFIL) etc. but didn't get it thought it. For current options also I was working for couple days, after that I got the solution.
Let start work now.....
------------------------------------------------------
There are two parts for this tutorial,
Part1 - make your device bootable/softbrick/start in recovery mode. This is difficult part and most of us stuck here only. We need to make device from hard brick to soft brick. Should work for all Qualcomm devices(except hardware failure).
Part2 - Flash ROM to your device. This is easy part and there are lots tutorial/information available to flashing ROM into device. It will be dependent on individual devices.
Part1:- -
Make your PC into Test Mode.
Then run “CMD” or “Windows Terminal” as administrator and type:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Download QualcommDrv.zip from here , extract to an empty folder, then open the folder according to your Windows type (x64 or x86) and double click dpinst64.exe (if you have 64-bit Windows) to install the Qualcomm driver
now please connect your Qualcomm Mobile to PC or laptop Your phone should now being detected as “Qualcomm HS-USB QDLoader 9008” and the driver version 2.0.8.7 (please check it through Windows’ “Device Manager”). If its not detected, then you can keep mobile connecting to computer and press power button and volume down button.( This is for motorola g4 plus and can be different for your mobile. )
Now you have your mobile connected to computer, now follow the below steps.
Please download zip " blankflash1.zip" from location here extract it your computer and goto extracted folder and click blank-flash.bat
It will start in command prompt and detect device on your computer port(eg. COM5, COM8 etc).
If process completed successful then your mobile will restart into bootloader screen and your hard brick problem has been resolved. after that you can reboot into recovery by pressing power and volume down button again if required. Once you are in recovery mode then you can flash correct stock ROM into your mobile. Refer below Part2 for this.
If above didn't work and you are getting error like below..
Or any other error, then its little tricky to solve this.Code:C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash Motorola qboot utility version 3.40 [ -0.000] Opening device: \\.\COM5 [ -0.000] Detecting device [ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error [ 4.072] Check qboot_log.txt for more details [ 4.072] Total time: 4.072s FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello() ->IO error
Follow the below steps.
1. Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
4. keep trying step 3 unless you dont see below logs.
5. once this is complete then you mobile will boot in bootloader/recovery mode, or you can go to recovery mode using volume up/down button.Code:C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash Motorola qboot utility version 3.40 [ -0.000] Opening device: \\.\COM5 [ -0.000] Detecting device [ 2.059] ReadFile() failed, GetLastError()=0 [ 2.563] ...cpu.id = 2418 (0x972) [ 2.563] ...cpu.sn = 28194769 (0x1ae37d1) [ 2.563] Opening singleimage [ 2.563] Loading package [ 2.563] ...filename = singleimage.pkg.xml [ 2.563] Loading programmer [ 2.563] ...filename = programmer.mbn [ 2.563] Sending programmer [ 2.793] Handling things over to programmer [ 2.793] Identifying CPU version [ 2.793] Waiting for firehose to get ready [ 5.800] ...MSM8952 1.1 [ 5.800] Determining target secure state [ 5.800] ...secure = yes [ 5.816] Flashing GPT... [ 5.816] Flashing partition:0 with gpt_main0.bin [ 5.816] Initializing storage [ 5.816] Configuring device... [ 5.832] ...blksz = 512 [ 6.331] Re-initializing storage... [ 6.331] Initializing storage [ 6.362] Flashing bootloader... [ 6.362] Flashing aboot with emmc_appsboot.mbn [ 6.721] Flashing rpm with rpm.mbn [ 6.783] Flashing tz with tz.mbn [ 7.033] Flashing hyp with hyp.mbn [ 7.080] Flashing cmnlib with cmnlib.mbn [ 7.158] Flashing keymaster with keymaster.mbn [ 7.236] Flashing sbl1 with sbl1.mbn [ 7.392] Rebooting to fastboot [ 7.392] Total time: 7.392s
After this, your mobile would be detected using adb(android driver), and you can execute fastboot commands.
Note: blankflash1.zip file is working for motorola moto g 4 plus, it should work for other mobiles also. If that doesn't work with your mobile then try with blankflash2.zip and blankflash3.zip files. download here
blankflash1.zip -- is for latest mobile above android lollipop,
blankflash2.zip -- for android lollipop.
blankflash3.zip -- for Kitkat devices.
please try with 1,2 and 3 in order.
Step3 is the key for whole process. you may need to try multiple times while blank-flash.bat is running.
Once you reached here, Congratulations, your mobile is saved and back to life. next part flashing stock rom is very easy. I will try to find url for that.
you just need correct ROM for your mobile and steps to flash it.
Part 2 :
Below is url for motorola, you will get idea how to do it for your mobile by going through it.
Alternative, now you can give your mobile to service center or mobile repair shop to flash ROM.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Other link for flashing ROM into any android mobile:
https://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
https://forum.xda-developers.com/showthread.php?t=2131284
https://www.xda-developers.com/how-to-install-custom-rom-android/
Let me know if you have any doubts/questions, I will try to update.
Also let me know if it helps you and you can also Donate
Your method works perhaps, any of the blank flash works I have to use another that some one send to me.
[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 2418 (0x972)
[ 0.000] ...cpu.sn = 26899456 (0x19a7400)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.000] ...filename = singleimage.pkg.xml
[ 0.000] Loading programmer
[ 0.000] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 0.231] Handling things over to programmer
[ 0.231] Identifying CPU version
[ 0.231] Waiting for firehose to get ready
[ 3.255] ...MSM8952 1.1
[ 3.255] Determining target secure state
[ 3.255] ...secure = yes
[ 3.255] Flashing GPT...
[ 3.255] Flashing partition:0 with gpt_main0.bin
[ 3.255] Initializing storage
[ 3.271] Configuring device...
[ 3.286] ...blksz = 512
[ 3.355] Re-initializing storage...
[ 3.355] Initializing storage
[ 3.402] Flashing bootloader...
[ 3.402] Flashing aboot with emmc_appsboot.mbn
[ 3.686] Flashing rpm with rpm.mbn
[ 3.754] Flashing tz with tz.mbn
[ 3.954] Flashing hyp with hyp.mbn
[ 4.001] Flashing cmnlib with cmnlib.mbn
[ 4.054] Flashing keymaster with keymaster.mbn
[ 4.133] Flashing sbl1 with sbl1.mbn
[ 4.254] Rebooting to fastboot
[ 4.270] Total time: 4.270s
Here is the file that works, MOTO G4 plus recovered
https://mega.nz/#!RXJjAQ7Z!SRVdrGbtDFPbmSbajOf15bPyyb7DZt3OeqFqFjaQ8Rg
Last edited:
A few things:
1) Please don't quote the entirety of the opening post - it takes up space and we may lose your message scrolling through. Please edit your post to remove the quoted opening post.
2)Your Google Drive link is requesting permission to access.
3)What is different between the blankflash you've linked and the one described in this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 and from an earlier post in this thread? https://forum.xda-developers.com/showpost.php?p=73430127&postcount=266
Solucionado
Espero ser de gran ayuda.
Hola, amigo... yo usé este archivo y me sirvió. Mi equipo es un XT1641. Este es el link del archivo: drive.google.com/file/d/0B9rhtqQ4ZTDnTWdpX3ZaVk1pNk0/view
Espero ser de gran ayuda.
after flashing previous build in moto g4 plus, i got update and then everything went wrong. it didnt start at all. just led blinking on usb connection or charging..
gave to moto centre they kept for 7days and returned saying its rooted give back to amazon if they take back.
i tried various methods here in xda but didnt work. then after overnight charging i could switch on the fone but now i am facing these probs...:-
1. fone is not being detected in pc on usb connection. tried all methods to uninstall/install usb drivers, manually indtalled drivers, etc... but still not detected. BUT FONE IS IN CHARGING MODE AS SOON AS I CONNECT TO PC. cant switch to MTP mode.
.
2. wifi is not working at all. cant turn on. in mac address it says.. "02-00-00-00-00-00"
.
3. sounds not working in speaker. no ringtones no keypad tones,etc.. through headfones i can hear everything music, vdo etc...
.
in short i am stuck very badly with my fone on and so many things not working.
.
plz help me out here.
gave to moto centre they kept for 7days and returned saying its rooted give back to amazon if they take back.
i tried various methods here in xda but didnt work. then after overnight charging i could switch on the fone but now i am facing these probs...:-
1. fone is not being detected in pc on usb connection. tried all methods to uninstall/install usb drivers, manually indtalled drivers, etc... but still not detected. BUT FONE IS IN CHARGING MODE AS SOON AS I CONNECT TO PC. cant switch to MTP mode.
.
2. wifi is not working at all. cant turn on. in mac address it says.. "02-00-00-00-00-00"
.
3. sounds not working in speaker. no ringtones no keypad tones,etc.. through headfones i can hear everything music, vdo etc...
.
in short i am stuck very badly with my fone on and so many things not working.
.
plz help me out here.
Off topic here, discussed at other place. Please look at Q&A Section. There are already 2 topics about Android O at the top.
cmd is showing waiting for device...please help @leo88sandy
please give your contact number or anything to contact u....
please..
please give your contact number or anything to contact u....
please..
Have you tried unplugging your device and then reattaching your device to your computer? https://forum.xda-developers.com/showpost.php?p=73433267&postcount=299
This might help fastboot sense your device again, have you also loaded the adb (e.g. the minimal adb/fastboot drivers) or the Motorola drivers as well?
still not able to unbrick the blankflash file not working
i flashed Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63_Stock_Img to downgrade to marshmellow and after that there was an ota update while installing which my phone got bricked
the error that i am getting is in the file attached please reply quickly
i flashed Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63_Stock_Img to downgrade to marshmellow and after that there was an ota update while installing which my phone got bricked
the error that i am getting is in the file attached please reply quickly
Attachments
Is this with the latest blankflash we have access to? https://forum.xda-developers.com/showpost.php?p=73430127&postcount=266
Downgrading to MM and then taking an OTA is super risky with the June 2017 update (too late now, I know..) Hopefully the above blankflash will rescue your device and consult this guide too: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Which blank flash file did you use.?
Try the latest one : https://drive.google.com/file/d/0B9rhtqQ4ZTDnTWdpX3ZaVk1pNk0/view
thank you friends i just restarted my pc and tried again and it worked right now in fastboot mode i used this guide https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
to flash the bootloader and right now downloading the latest stock firmware whose link was provided in above thread
i hope everything goes fine further
btw thankyou so much @echo92 and @ganeshkmr21 for your replies
to flash the bootloader and right now downloading the latest stock firmware whose link was provided in above thread
i hope everything goes fine further
btw thankyou so much @echo92 and @ganeshkmr21 for your replies
[edit]
I wanted to come here and say "Thank you" as this nifty tool helped me out of a real jam.
I wanted to come here and say "Thank you" as this nifty tool helped me out of a real jam.
Last edited:
Getting Error plz Help...
Motorola qboot utility version 3.40
[ 0.041] Opening device: \\.\COM4
[ 0.042] Detecting device
[ 0.044] ...cpu.id = 2418 (0x972)
[ 0.045] ...cpu.sn = 17238413 (0x107098d)
[ 0.045] Opening singleimage
[ 0.208] Loading package
[ 0.213] ...filename = singleimage.pkg.xml
[ 0.217] Loading programmer
[ 0.264] ...filename = programmer.mbn
[ 0.266] Sending programmer
[ 0.488] Handling things over to programmer
[ 0.488] Identifying CPU version
[ 0.492] Waiting for firehose to get ready
[ 60.580] Waiting for firehose to get ready
[120.682] ...MSM8952 unknown
[120.682] Determining target secure state
[120.684] Waiting for firehose to get ready
[180.775] ...secure = no
[181.052] Flashing GPT...
[181.093] Flashing partition:0 with gpt_main0.bin
[181.093] Initializing storage
[181.099] Waiting for firehose to get ready
[241.191] Configuring device...
[241.196] Waiting for firehose to get ready
[301.288] Waiting for firehose to get ready
[361.390] Waiting for firehose to get ready
[421.490] Waiting for firehose to get ready
[481.621] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage
()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read(
)->device_read()->IO error
[481.622] Check qboot_log.txt for more details
[481.622] Total time: 481.647s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash
()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure(
)->buffer_read()->device_read()->IO error
Motorola qboot utility version 3.40
[ 0.041] Opening device: \\.\COM4
[ 0.042] Detecting device
[ 0.044] ...cpu.id = 2418 (0x972)
[ 0.045] ...cpu.sn = 17238413 (0x107098d)
[ 0.045] Opening singleimage
[ 0.208] Loading package
[ 0.213] ...filename = singleimage.pkg.xml
[ 0.217] Loading programmer
[ 0.264] ...filename = programmer.mbn
[ 0.266] Sending programmer
[ 0.488] Handling things over to programmer
[ 0.488] Identifying CPU version
[ 0.492] Waiting for firehose to get ready
[ 60.580] Waiting for firehose to get ready
[120.682] ...MSM8952 unknown
[120.682] Determining target secure state
[120.684] Waiting for firehose to get ready
[180.775] ...secure = no
[181.052] Flashing GPT...
[181.093] Flashing partition:0 with gpt_main0.bin
[181.093] Initializing storage
[181.099] Waiting for firehose to get ready
[241.191] Configuring device...
[241.196] Waiting for firehose to get ready
[301.288] Waiting for firehose to get ready
[361.390] Waiting for firehose to get ready
[421.490] Waiting for firehose to get ready
[481.621] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage
()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read(
)->device_read()->IO error
[481.622] Check qboot_log.txt for more details
[481.622] Total time: 481.647s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash
()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure(
)->buffer_read()->device_read()->IO error
restart your pc and try once again and also try different usb port coz i was also having same problem but worked fine after restarting pc
Last edited by a moderator:
I am done from this method...
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Hard Bricked Moto G4 Plus
Read the post carefully and then only start the process.
I have faced this problem during an update from Motorola. My device turned off in the middle of update and didn’t turn on. I visited service centre, local shops but none of them has the solution. The only solution was to replace the motherboard of my device. After doing a lot of research work, watching many tutorials, reading xda posts and other blogs, I found the solution on Facebook.
Facebook Group – “[RESUELTO] HARD BRICK MOTO G4/G4 PLUS”
Link : https://www.facebook.com/groups/700524370155129/
There is a solution on xda developers too, but they had not explained the proper procedure to be followed.
XDA Solution Link: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Symptoms of a hard bricked Moto G4 Plus: You can conclude that your Moto G4 Plus is hard bricked when the screen of the device does not turn on at all and when you plug in your charger, the white notification light starts blinking. There is no vibration or kind of activity in the phone.
How to fix this problem?
This process involves various steps. Please proceed accordingly, do not skip any step and do not try flashing any other ROM or Firmware in the device until it is fully recovered. I have used the official Motorola Firmware with June 2017 security match and Android Nougat.
I have fixed my XT1643 Moto G4 Plus 32/3 GB Variant.
Step 1:
Check if your device can be fixed or not. To check, connect your phone to PC first.
Right Click on My Computer Icon -> Manage -> Device Manager -> Ports
You should see something like this “qualcomm hs-usb qdloader 9008” or it can also be a unrecognised qualcom device.
If you are seeing anything like this, then you can proceed with further steps.
Step 2:
Now unplug your phone from PC and download this Qualcom Driver.
Link: https://drive.google.com/open?id=0B6TKJzgog8cjTVREaEdWRWk3UDQ
Install as per your Windows OS version 32/64 bit. You can check your OS version by right clicking on My Computer icon -> Properties
Step 3:
Download Motorola Device Driver from link below and install it.
Link: https://drive.google.com/open?id=0B6TKJzgog8cjeUNsZjk0ekxMeG8
Step 4:
Set your PC into test mode.
You can do this by going to start screen and search “cmd”. Now right click on option displayed and click on Run as Administrator.
Now copy and paste the following commands on by one and press enter after each command.
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Step 5:
Restart your PC
Step 6:
Download Blank Flash file from link given below.
Link: https://drive.google.com/open?id=0B6TKJzgog8cjdmZYQVB2VDkyQTg
Right click on Blank Flash Zip file and extract it.
Now click on blank-flash.bat and you’ll see command prompt pop up displaying “waiting for device”.
Now plug in your device with USB to PC and wait. If it shows some error, repeat Step 6 again and again until the Blank Flash process completes successfully.
Step 7:
Now download minimal adb setup from link given below.
Link: https://drive.google.com/open?id=0B6TKJzgog8cjMXY2WXNSaXdEOXM
Install it
Step 8:
Download the official Motorola Firmware from link given.
Link: https://drive.google.com/open?id=0B6TKJzgog8cjYWZseC1JSTBDd1k
Extract the file name “ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml”, then open the extracted folder and copy all the files. Now Right Click on desktop adb fastboot icon. Go to Properties -> File Location and paste all the files here.
Step 9:
Now click on adb fastboot icon on desktop. Command prompt will open. Now enter the following command.
fastboot devices
Your device serial number will be displayed. Then enter the following commands one by one and press enter after each command.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
Step 9:
Now again enter the command “fastboot devices” and press enter.
Now copy all the commands below and go to the fastboot command prompt and right click at black area anywhere on the command window.
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
Wait for some time till the process gets completed and then press enter in the last when everything finishes.
Hurray !! Your device will restart as earlier and everything will be fine.
The list of commands required during the whole process can also be download from link below.
Link: https://drive.google.com/open?id=11chsCAVQ44MatGv95jeGo-EKbEFG4sFn9U6OQuYOP7A
Read the post carefully and then only start the process.
I have faced this problem during an update from Motorola. My device turned off in the middle of update and didn’t turn on. I visited service centre, local shops but none of them has the solution. The only solution was to replace the motherboard of my device. After doing a lot of research work, watching many tutorials, reading xda posts and other blogs, I found the solution on Facebook.
Facebook Group – “[RESUELTO] HARD BRICK MOTO G4/G4 PLUS”
Link : https://www.facebook.com/groups/700524370155129/
There is a solution on xda developers too, but they had not explained the proper procedure to be followed.
XDA Solution Link: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Symptoms of a hard bricked Moto G4 Plus: You can conclude that your Moto G4 Plus is hard bricked when the screen of the device does not turn on at all and when you plug in your charger, the white notification light starts blinking. There is no vibration or kind of activity in the phone.
How to fix this problem?
This process involves various steps. Please proceed accordingly, do not skip any step and do not try flashing any other ROM or Firmware in the device until it is fully recovered. I have used the official Motorola Firmware with June 2017 security match and Android Nougat.
I have fixed my XT1643 Moto G4 Plus 32/3 GB Variant.
Step 1:
Check if your device can be fixed or not. To check, connect your phone to PC first.
Right Click on My Computer Icon -> Manage -> Device Manager -> Ports
You should see something like this “qualcomm hs-usb qdloader 9008” or it can also be a unrecognised qualcom device.
If you are seeing anything like this, then you can proceed with further steps.
Step 2:
Now unplug your phone from PC and download this Qualcom Driver.
Link: https://drive.google.com/open?id=0B6TKJzgog8cjTVREaEdWRWk3UDQ
Install as per your Windows OS version 32/64 bit. You can check your OS version by right clicking on My Computer icon -> Properties
Step 3:
Download Motorola Device Driver from link below and install it.
Link: https://drive.google.com/open?id=0B6TKJzgog8cjeUNsZjk0ekxMeG8
Step 4:
Set your PC into test mode.
You can do this by going to start screen and search “cmd”. Now right click on option displayed and click on Run as Administrator.
Now copy and paste the following commands on by one and press enter after each command.
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Step 5:
Restart your PC
Step 6:
Download Blank Flash file from link given below.
Link: https://drive.google.com/open?id=0B6TKJzgog8cjdmZYQVB2VDkyQTg
Right click on Blank Flash Zip file and extract it.
Now click on blank-flash.bat and you’ll see command prompt pop up displaying “waiting for device”.
Now plug in your device with USB to PC and wait. If it shows some error, repeat Step 6 again and again until the Blank Flash process completes successfully.
Step 7:
Now download minimal adb setup from link given below.
Link: https://drive.google.com/open?id=0B6TKJzgog8cjMXY2WXNSaXdEOXM
Install it
Step 8:
Download the official Motorola Firmware from link given.
Link: https://drive.google.com/open?id=0B6TKJzgog8cjYWZseC1JSTBDd1k
Extract the file name “ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml”, then open the extracted folder and copy all the files. Now Right Click on desktop adb fastboot icon. Go to Properties -> File Location and paste all the files here.
Step 9:
Now click on adb fastboot icon on desktop. Command prompt will open. Now enter the following command.
fastboot devices
Your device serial number will be displayed. Then enter the following commands one by one and press enter after each command.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
Step 9:
Now again enter the command “fastboot devices” and press enter.
Now copy all the commands below and go to the fastboot command prompt and right click at black area anywhere on the command window.
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
Wait for some time till the process gets completed and then press enter in the last when everything finishes.
Hurray !! Your device will restart as earlier and everything will be fine.
The list of commands required during the whole process can also be download from link below.
Link: https://drive.google.com/open?id=11chsCAVQ44MatGv95jeGo-EKbEFG4sFn9U6OQuYOP7A
Last edited by a moderator:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone