I got it !!!
Bootloader screen
And now?
Which ROM install 8 or 7?
Where do I get the roms?
I want to stay with rom 7, but how to do it so that there is no more problem?
Last edited:
[Solved] Unbrick (Hard Bricked/Dead) Motorola G 4 plus or any Qualcomm mobile Device
- Thread starter vijayjadhav_143
- Start date
Bootloader screen
And now?
Which ROM install 8 or 7?
Where do I get the roms?
I want to stay with rom 7, but how to do it so that there is no more problem?
Though I would personally recommend flashing back to stock Oreo, since you want to be on Nougat 7.0, I would recommend you flash the latest stock Nougat firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to lock your bootloader (and indeed, the oem lock commands would likely fail since you still have an Oreo bootloader), so omit the oem lock begin and oem lock commands. I would recommend you clean flash - include fastboot erase userdata.
Once you have flashed the Nougat firmware (and I hope you still have your IMEI and signal), you will want to disable OTA updates since you'll likely get notifications to the Oreo OTA. Have a look in this thread for ideas on how to do so: https://forum.xda-developers.com/moto-g4-plus/help/how-disable-notification-update-t3459587
He came back alone with Android 7, did not need to install, but no signal and imei.
How do I install OREO?
Your device is indeed on Nougat, but you're likely still on the firmware before or during the OTA update when you hard bricked. If you try to use another old OTA update without updating, you'll likely hard brick again. Hence why I suggested updating to the actual newest Nougat firmware.
If you're having IMEI issues, you could update to Oreo using the guide I mentioned: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Again, up to you if you want to lock your bootloader.
Alternatively, if you want to stay on Nougat (and do NOT use OTA updates), have a look at this guide for repairing your IMEI: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
Personally, I would update to Oreo and forget about downgrading unless you're very careful. As you're now aware, downgrading can be very risky if you're not aware of the risks involved.
Bro. I recommend you to install Lineage 14.1 custom rom. With Nougat you will ota update at any time and you will kill your phone again. With custom roms you'll not have this risk anymore
Thanks @echo92
I installed OREO.
But now it has a problem with audio, sometimes it works and sometimes it does not.
Hmm, did you flash OPJ28.111-22 or OPJ28.111-22-1 (the latter supposedly has audio fixes)? https://forum.xda-developers.com/showpost.php?p=79737114&postcount=1368
Failing that, you could flash the NPJS25.93-14-18 April 2018 firmware and disable OTA updates as previously mentioned if you still wanted to stay with stock firmware.
Search for ota update. They release one update that "solve" sound issues
I am with the latest version installed 8.1.0
It starts with Hello Moto sound, but after some time the sound disappears.
Which Oreo version is that then? Is that OPJ28.111-22 or OPJ28.111-22-1?
If you're on OPJ28.111-22, try flashing the OPJ28.111-22-1 OTA from here: https://forum.xda-developers.com/showpost.php?p=79737114&postcount=1368
Last edited:
1)Download the OTA update to your device, make sure it's on Internal Storage.
2)Go to Settings>Apps and Notifications
3)Tap See all apps under 'Recently opened apps'
4)In the top right corner, tap the 3 vertical dots and select Show System.
5)Find Motorola Update Services and select. Allow storage permissions.
6)Go back to Settings>System. Tap on System updates to check for updates.
Else, install the update via stock recovery - more info here https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-g4-oreo-soak-test-update-t3871136
Version OPJ28.111-22-1, but still no audio!
It works sometimes!
Try running the Moto help app and the speaker test within. If that doesn't work, then downgrade to NPJS25.93-14-18 using the firmware from the same thread as the Oreo firmware or you could install TWRP and use the TWRP flashable here: https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 . As I mentioned previously, you should disable OTA updates. Alternatively, as others have suggested, use custom ROMs.
Last edited:
Unfortunately it does not work with any version of ROM the sound.
The test also did not work!
One thing to try is to flash TWRP to your device (if your bootloader is still unlocked) and try the TWRP flashable of Nougat - see if that solves your sound issue: https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367
please help me moto g4 plus how to repair dead boot
C:\Users\USER\Desktop\Blankflash MG4P\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.016] Detecting device
[ 0.016] ...cpu.id = 2418 (0x972)
[ 0.016] ...cpu.sn = 30865131 (0x1d6f6eb)
[ 0.016] Opening singleimage
[ 0.062] Loading package
[ 0.078] ...filename = singleimage.pkg.xml
[ 0.078] Loading programmer
[ 0.094] ...filename = programmer.mbn
[ 0.094] Sending programmer
[ 0.312] Handling things over to programmer
[ 0.312] Identifying CPU version
[ 0.328] Waiting for firehose to get ready
[ 60.328] Waiting for firehose to get ready
[120.328] ...MSM8952 unknown
[120.328] Determining target secure state
[120.328] Waiting for firehose to get ready
[180.328] ...secure = no
[180.359] Flashing GPT...
[180.375] Flashing partition:0 with gpt_main0.bin
[180.375] Initializing storage
[180.375] Waiting for firehose to get ready
[240.375] Configuring device...
[240.375] Waiting for firehose to get ready
[300.375] Waiting for firehose to get ready
[347.406] ReadFile() failed, GetLastError()=0
[361.406] Waiting for firehose to get ready
[421.406] Waiting for firehose to get ready
[481.406] 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.406] Check qboot_log.txt for more details
[481.406] Total time: 481.406s
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
C:\Users\USER\Desktop\Blankflash MG4P\blankflash>pause
Press any key to continue . . .
C:\Users\USER\Desktop\Blankflash MG4P\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.016] Detecting device
[ 0.016] ...cpu.id = 2418 (0x972)
[ 0.016] ...cpu.sn = 30865131 (0x1d6f6eb)
[ 0.016] Opening singleimage
[ 0.062] Loading package
[ 0.078] ...filename = singleimage.pkg.xml
[ 0.078] Loading programmer
[ 0.094] ...filename = programmer.mbn
[ 0.094] Sending programmer
[ 0.312] Handling things over to programmer
[ 0.312] Identifying CPU version
[ 0.328] Waiting for firehose to get ready
[ 60.328] Waiting for firehose to get ready
[120.328] ...MSM8952 unknown
[120.328] Determining target secure state
[120.328] Waiting for firehose to get ready
[180.328] ...secure = no
[180.359] Flashing GPT...
[180.375] Flashing partition:0 with gpt_main0.bin
[180.375] Initializing storage
[180.375] Waiting for firehose to get ready
[240.375] Configuring device...
[240.375] Waiting for firehose to get ready
[300.375] Waiting for firehose to get ready
[347.406] ReadFile() failed, GetLastError()=0
[361.406] Waiting for firehose to get ready
[421.406] Waiting for firehose to get ready
[481.406] 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.406] Check qboot_log.txt for more details
[481.406] Total time: 481.406s
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
C:\Users\USER\Desktop\Blankflash MG4P\blankflash>pause
Press any key to continue . . .
The blankflashes included in this thread are far too old. Try the Oreo blankflash https://forum.xda-developers.com/showpost.php?p=79714477&postcount=778
If you do rescue your device, do not use OTA updates until you have updated your firmware formally.
My phone's led blinks when connected but doesn't show up on the Device Manager, I assume it's hardware fail?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
You need to install Qualcomm drivers, your phone will show as Qualcomm 9008 in device manager. Something like this. Then you need to use a blankflash. Then flash a stock firmware via fastbootI 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.
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.
My phone's led blinks when connected but doesn't show up on the Device Manager, I assume it's hardware fail?
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