[Solved] Unbrick (Hard Bricked/Dead) Motorola G 4 plus or any Qualcomm mobile Device
- Thread starter vijayjadhav_143
- Start date
Bro, I successfully recovered my device. But the problem is I am still in March security patch level. And my phone is showing its update. What should I have to do?Okay, so for those trying the new blankflash we have (https://forum.xda-developers.com/mo...icked-dead-t3585016/post73430127#post73430127 if you've not seen it already), I've uploaded the NPJS25.93-14-4, March 2017 and NPJS25.93-14-8, June 2017 GPT and bootloader files to here: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M
You'll see 2 separate zips, each with the appropriate files for each build, extracted from their fastboot files directly. The following file sizes and checksums should match when the files are expanded (ensure you download the GPT and bootloader you want!)
March 2017 -
GPT: 32 KB, md5: be97a48f5ab36009b8c5e5bd55453f1e
bootloader: 3.56 MB, md5: 2f7a44bba145811bb6cd4267d6d19805
June 2017 -
GPT: 32 KB, md5: 88bc92ebbb172dc2c17321a4b6b10aea
bootloader md5: 3.56 MB, md5: 1e82257d86c0211283775e2572b26a2f
Use these files as in the post linked by baunthiyal https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 As lCrD512 notes in that post, be aware that you should use the latest firmware (so you may opt to use the June 2017 GPT/bootloader above).
EDIT - if you see the 'waiting for device' command whilst attempting to flash GPT and bootloader, try un-plugging and re-connecting your device to fastboot and see if it senses your device. Credit to https://forum.xda-developers.com/showpost.php?p=73433267&postcount=299
A personal request, if you do get your device working, please be really careful if you downgrade next time and try not to, or if you do downgrade, don't update via OTA? This time we were lucky...
EDIT - baunthiyal is too quick for me
Sorry for bad english
I'd suggest using the fastboot June 2017 firmware to formally update your device to the same patch level: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Up to you if you choose to re-lock your bootloader or just update (flash GPT and bootloader).
I'd suggest don't accept the OTA, it might brick your device again depending on which GPT/bootloader you flashed in the unbrick recovery. Also, when you flash the June 2017 update, don't downgrade please.
After that may I use ota update normally for future updates?
Provided you've fully flashed the fastboot ROM (GPT/bootloader, modem etc) and your device is on the same update level, then your system should be okay to update via OTA. If you're not confident, then you could wait for the fastboot ROM to come out, which should be safer to flash.
It's possible that at some point that the blankflash may not work for future OTAs, so remember that you've updated and be careful. We were lucky this time.
thank uOh ****! My phone just booted into the bootloader!
---------- Post added at 04:52 AM ---------- Previous post was at 04:24 AM ----------
XT1643 Oh yes, it works like a boss. G4 Plus recovered.
Sent from my ZUK Z2131 using Tapatalk
I'm slightly confused by your question?
You should be able to take OTA updates. If you wish to be more careful, then wait for the fastboot ROM, as this has the complete files. The OTA only applies patches and code changes (hence why it can brick devices), whereas the fastboot ROM will flash the complete relevant files.
If you're confident your device is properly running and flashed to the most recent update including GPT and bootloader, then OTAs shouldn't cause you issues (and should be safe as long as you're updating from a fully flashed build and have not downgraded). Perhaps wait to see if other users have issues with the update before flashing.
If you want to be really safe, then wait for the fastboot ROM and then update your GPT/bootloader too.
It's up to you, your device, but with either, as Motorola is tightening up security, downgrades are increasingly risky. Therefore, it might be safest, if you're into flashing custom ROMs or reverting to stock, to wait for the latest fastboot ROM to come out or have a TWRP backup to fall back to.
Bro I flashed the gpt and bootloader of June update,as you mentioned in the post of unbricking. Does it mean that my gpt and bootloader is up to date to latest version? Does it mean that I can install the ota update for June security patch level without having hardbrick again? If my gpt and bootloader is up to date. Can I install ota update of june security level? What would you suggest me?
Plzz bro reply fast if possible.
Last edited:
Thanks for the clarification (not sure how you're on the March 2017 patch unless you flashed the March 2017 fastboot ROM).
Does it mean that my gpt and bootloader is up to date to latest version? Yes, if you flashed the June GPT and bootloader, your bootloader should be version B1:06.
Does it mean that I can install the ota update for June security patch level without having hardbrick again? I would not recommend updating using the June OTA at this time (though it may be okay to use, you've still got a mismatch between the GPT/bootloader - which is June - and your system - which is March).
I'd recommend downloading the June 2017 fastboot ROM and flashing that in fastboot as I first suggested https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. Flash including GPT and bootloader - it's up to you to re-lock. This fastboot ROM will formally update your device to the June 2017 update level. Yes, it's a 1 GB download, and you'll need a PC, but it's safer than the OTA at this point.
After you've used the fastboot ROM to fully update your device, then future OTAs should be okay, but as I mentioned earlier, you may wish to wait for a fastboot ROM of that OTA to update.
Last edited:
I flashed the Dec. Security patch level. Then I updated and got bricked.I think therefore I am in March security patch level.
I think that I should attempt the ota as an experiment. In case I got bricked then blabkflash we have is of latest version. I think it can save me if I get bricked again. May I attempt the ota as an experiment?
Why u flashed old firmware, u should flash latest with June update, I did the same
Ah, so when you used the blankflash, you just used it to get your device running again, you did not flash the latest stock ROM?
In that case, I cannot stop you from trying the OTA, but I can't suggest it. From what you mentioned, you downgraded to Dec 2016, then flashed the March 2017 patch. In theory, flashing the June GPT/bootloader should have replaced the damaged versions, but I'd still want to formally fully update to ensure the device is properly flashed (and all your other firmware is properly updated, else you may be storing problems up for the future). There's no guarantee that your device was properly flashed by the March update before it bricked.
I'd do a full fastboot flash properly now with the June 2017 stock fastboot ROM - if not, there's no telling if the next future OTA will be okay or cause problems. Yes, it might mean you having to backup and wipe your device, but given you've just rescued it, wouldn't you want to clean flash and start over?
Last edited:
Tell me how to remove the old stock rom which is installed in my device or should I directly flash the June firmware?
What is the best way of flashing? By running flash script or by typing commands one by one? Plz bro reply fast.
Last edited:
Directly flash the June 2017 stock update. I don't think you can remove the old stock ROM and at any rate you might wipe key partitions like where your IMEI is stored.
It's up to you, if you want to make sure each command goes through, then you could copy the commands one by one (do not manually type them), though you'll have to verify the commands are the right ones and in the right order. It might be easier to use the OEM flashing scripts included in the fastboot ROM threads. Have a look here for the flashing commands you'll want - they're all similar: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
This should be familiar given you've flashed the fastboot ROM in the past.
made my day
A huge thanks to @marcelofilgueira for providing us with the updated blankflash files and @echo92 for always being there with us.
Was just returning back home from college and just as always wanted to browse Xda for some updates regarding the blankflash.
And #boom the replies in this thread increased from 257 to 313 and that was the time I just couldn't believe my eyes reading comments about athenes going live again.
That made my day, and I rushed back home to get my device backk up again and was relieved to see the bootloader.
Many many thanks everyone
#xdarocks
A huge thanks to @marcelofilgueira for providing us with the updated blankflash files and @echo92 for always being there with us.
Was just returning back home from college and just as always wanted to browse Xda for some updates regarding the blankflash.
And #boom the replies in this thread increased from 257 to 313 and that was the time I just couldn't believe my eyes reading comments about athenes going live again.
That made my day, and I rushed back home to get my device backk up again and was relieved to see the bootloader.
Many many thanks everyone
#xdarocks
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