yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] echo92:
Which blankflash have you tried? I see you hard bricked in June of last year around the time we got this newer blankflash, so try this Oreo blankflash: https://xdaforums.com/showpost.php?p=79714477&postcount=778

(After using this blankflash, and if your device boots to the bootloader, you will have an Oreo bootloader. Even if you flash the Nougat firmware, you'll still have an Oreo bootloader. DO NOT use OTA updates if you have flashed stock Nougat or Marshmallow.)

Also, try the tips I provided in an above post - make sure your USB cable is an original Motorola cable or a high quality data and charge cable, try different USB ports (USB 2.0, 3.0 etc) and different computers.
[Moto G4 Plus Guides, News, & Discussion] Bhavik kaila:
Thanks it's working...but some more problems..when I m update my phone it's restarting for installing.after my phone is in dead boot....what's wrong with my phone sir...can u help me....

Thanks in advance
[Moto G4 Plus Guides, News, & Discussion] Bhavik kaila:
This is my phone info.
[Moto G4 Plus Guides, News, & Discussion] echo92:
What do you mean you're in dead boot? I understand English may not be your native language, do you mean your device hard bricks again?

From your post, you've got the December 2016 Nougat firmware. Your bootloader would likely be on the Oreo version. Thus, using OTA updates will brick your phone. I mentioned that in my last post,

do not use OTA updates.

the only way you can update now is to flash the stock firmware, because you're trying to use old OTA updates which keep corrupting your Oreo bootloader.

The best and only way to update, if you really want to use stock firmware, is to flash the whole latest Oreo stock firmware. I would recommend this as you seem to keep hard bricking.

If you do not wish to update to Oreo , then either flash the latest stock Nougat firmware, or stay on the firmware you have. If you stay on Nougat, you will want to disable your OTA updates.

Alternatively, use the TWRP flashables of the stock firmwares, which do not have update capability but have most of the firmware.

https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 for Nougat and Oreo firmwares

https://xdaforums.com/moto-g4-plus/help/how-disable-notification-update-t3459587 possible ways for disabling OTA updates.

https://xdaforums.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 for the TWRP flashables of stock firmware
[Moto G4 Plus Guides, News, & Discussion] Bhavik kaila:
OK can I flash this Oreo stock?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Which one, the Oreo stock firmware or the TWRP flashable?

You can flash either one (of course with the TWRP flashable you need TWRP).
[Moto G4 Plus Guides, News, & Discussion] Bhavik kaila:
https://xdaforums.com/mot...rch-1-t3608138

Can I use this oreo firmware sir?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Yes, that's the page I linked to. You can use the firmware, up to you if you want to lock your bootloader.

Also, no need to call me sir.
[Moto G4 Plus Guides, News, & Discussion] Bhavik kaila:
Thank you.

---------- Post added at 01:40 PM ---------- Previous post was at 01:33 PM ----------

Can I face after this stock flashing imei null problem?
[Moto G4 Plus Guides, News, & Discussion] echo92:
I thought you had fixed that issue? I don't think stock Oreo causes the issue, unless there's a problem with your device already.
[Moto G4 Plus Guides, News, & Discussion] Bhavik kaila:
Yes my device already face this problem.....so I m worried for this problem
[Moto G4 Plus Guides, News, & Discussion] echo92:
That's my question, did you get it fixed? It looks like you had it fixed, because your baseband looks okay and you've got both SIM signals displaying on your phone.
[Moto G4 Plus Guides, News, & Discussion] Bhavik kaila:
Yes I m already fixed it by root my device....

---------- Post added at 06:06 PM ---------- Previous post was at 06:04 PM ----------

When I m using nougat version in my device...I m get new oreo version update by Motorola official....after upgrading my imei null...after I m flashing nougat and imei problem fix by root.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Wait, so every time you update to Oreo, you lose your IMEI? That should not happen, and if it keeps happening when you update, I would therefore suggest you stay on Nougat and disable the OTA updater.
[Moto G4 Plus Guides, News, & Discussion] Bhavik kaila:
OK thank you.
[Moto G4 Plus Guides, News, & Discussion] Bhavik kaila:
Can u send me nougat latest stock link?
[Moto G4 Plus Guides, News, & Discussion] echo92:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
[Moto G4 Plus Guides, News, & Discussion] Bhavik kaila:
Thanks brother....?
[Moto G4 Plus Guides, News, & Discussion] echo92:
That error you're getting with preflash validation error is from trying to flash bootloader firmware older than your bootloader. You cannot downgrade your bootloader, and as such your device will report a 'security version downgrade' message. From the evidence, it looks like your device used to be on Nougat (B1:07 bootloader version, so December 2017 security patch or newer), and you downgraded to Marshmallow as identified by your device's build fingerprint. Thus, I'm guessing you took the December 2016 Nougat OTA update and hard bricked?

If you tried the flash file, you likely have a basic bootloader, and now require a full firmware flash of newer firmware than you currently are trying to use. You could flash only the GPT and bootloader from a newer firmware than you have (I recommend flashing the most recent Nougat firmware to get around that error message, NPJS25.93-14-18, April 2018 firmware), however, if you proceed to use stock OTA updates without full flashing you will likely hard brick again.

I would strongly recommend you download at least the most recent Nougat firmware from here https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and use that to flash. If you do not wish to erase your existing data, you can follow the following flashing commands instead of those in the mentioned thread, however, I would prepare to factory reset your device if you do encounter instability.

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 reboot
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, looks like that flash didn't update your device. Though the flashing commands reported okay, the getvar info indicates you still have marshmallow on your device ( bootloader) ro.build.fingerprint[1]: MPJ24.139-63/64:user/release-keys

I'd try flashing again, this time including the fastboot erase userdata command. If you can, input the commands one by one (copy and paste sequentially and press enter to execute). You could try the Oreo firmware, however the fact your device appears not to update after a stock firmware flash is concerning.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Thanks for trying the flash - I don't know the exact reason for the flash not writing properly to your device, or if it is, your device is not recognising the updated firmware. From what I've seen, this could indicate a hardware failure, which usually requires a motherboard replacement. You could try seeing if a JTAG or mobile repair centre could try to flash to the memory directly. If not, then that may require a service centre replacement and given the age of the device, I leave it up to you if you choose to repair or spend your money on a newer device.
[Moto G4 Plus Guides, News, & Discussion] Rover094:
Hello, I've been trying this solution but my phone is not getting detected in device manager. I tried installing qualcomm drivers and also tried to do some troubleshooting steps. It looks like the device is completely dead
[Moto G4 Plus Guides, News, & Discussion] echo92:
What device do you have? How did your device hardbrick? This procedure will generally only work if your device hard bricked after using an old OTA update (i.e. you downgraded your device with old stock firmware and bricked from flashing an old OTA update). For other reasons, including sudden failures not involving updates, this procedure may not work.
[Moto G4 Plus Guides, News, & Discussion] Rover094:
Oh okay. It's moto g4plus and no I haven't used any updates. It happened all of a sudden after I put it for charging. Maybe it's time to buy a new one. Thanks for your response :good:
[Moto G4 Plus Guides, News, & Discussion] Vikas Badhe:
It has worked wonders for me... My Moto G4 Plus was dead since 2018. I tried multiple solutions ... but no luck.

Finally today (22-Sep-2020), I came accross this article and it was panacea for my phone!!!

Thanks a ton ... Outfield303 :)
[Moto G4 Plus Guides, News, & Discussion] vinay lucy:
Anybody would share me the link for Blankflash zip would be helpful.

Google drive has been taken down.
[Moto G4 Plus Guides, News, & Discussion] manjaroid:
Hope this helps: https://androidfilehost.com/?w=files&flid=175273
[Moto G4 Plus Guides, News, & Discussion] vinay lucy:
Yo Bro,

Thanks a lot:)
[Moto G4 Plus Guides, News, & Discussion] subhash8765:
i have a strange problem. the phone video is choppy (laggy) ( its like 1fps) audio is fine. touch response is like 1000ms . initially i thought it might be a software issue or a replacement screen issue . i flashed the latest official rom via bootloader. the problem was still there. next i thought it is the problem with the lcd and digitizer which could be faulty. so i decided to troubleshoot it by screen mirroring via USB. now the issue is even the mirrored images on the desktop is choppy ( if i play a video on youtube the audio is fine but the video skips the frames ) now is this a problem with the adreno GPU?
[Moto G4 Plus Guides, News, & Discussion] auroraguy123:
I have a LG Qstylus plus phone, and it was bricked. My problem is my phone was in black screen and won't be rebooted again, even in fastboot mode because the bootloader was locked. I have seen a light after I saw your method to boot the phone. Can you help me ? The original post is https://xdaforums.com/t/my-lg-q-stylo-plus-bricked-please-help-save.4223161/
[Moto G4 Plus Guides, News, & Discussion] thoughtpolice:
Registered to thank the OP. Info in this thread allowed me to take my G4 Plus XT1644 from LineageOS to stock.

Thanks OP!
[Moto G4 Plus Guides, News, & Discussion] chouhanprem:
My Device is Model Moto_G4_Plus_XT1643 yese i reflash the june 2017 stock Rom after using Blankflash.

It brick while on updating NPJS25.93-14-4 rom.

I follow step by step which after the complete flash it reboot n again n again its rebooting..

Plz help ,me
[Moto G4 Plus Guides, News, & Discussion] echo92:
At what stage is it rebooting? Is it rebooting at the Moto logo, or after the unlocked bootloader warning?

Did you use the flashing commands in the opening post to flash your device with the June 2017 stock ROM and did you verify each flash was flashed okay?

Can you:

Hold down the power button for 20-30 seconds (sometimes it's a minute to 2 minutes) until your device hard powers off, then press the power button to reboot?

Alternatively, with your device powered off, press the power and volume down keys - does your device boot and stay in the bootloader menu? Can you boot to stock recovery?

I'm just wondering if the 2 steps above could break the bootloop.
[Moto G4 Plus Guides, News, & Discussion] chouhanprem:
Is it rebooting at the Moto logo continously and i use the flashing commands in the opening post to flash your device with the June 2017 stock ROM properly but its say "bootloader slot count not found moto g4 plus:

I hold power button for 20-30 seconds until your device hard powers off, then press the power button to reboot but still its looping on Moto logo and yes it boot on Bootloader menu but not in stock Recovery plz help me guys ..
[Moto G4 Plus Guides, News, & Discussion] echo92:
That bootloader slot count message, as I recall, is normal because our devices do not have A/B partitions, like the Google Pixel has.

Sounds like your first flash did not work properly, if it's failing to boot to recovery.

I'd suggest repeating the flash of the June 2017 stock ROM:

Ensure you have minimal adb 1.4.2 or similar (link here https://www.androidfilehost.com/?fid=745425885120698566) and, if you wish, have the Motorola device drivers installed on your computer. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/79106/p/30,75,27,

Delete the stock ROM currently in your adb folder. Extract a fresh copy of the June 2017 stock ROM and copy that to your adb folder (if your adb folder is in Program Files, you may not be able to extract directly to the adb folder).

Reboot your device to bootloader and attach to your computer.

In adb, confirm your device is communicating to your device by typing 'fastboot devices' (without the quotes), you should be getting your device's serial number as a response.

If communicating, use the commands in the opening post to flash the June 2017 fastboot firmware. Each command should report [OKAY] at the end if it's properly flashed.

The fastboot ROM should flash entirely with reporting [OKAY] at each stage, let us know if you encounter any different messages. Also, reflashing this may wipe your device again.
[Moto G4 Plus Guides, News, & Discussion] chouhanprem:
i have atttached fastboot getvarall
[Moto G4 Plus Guides, News, & Discussion] echo92:
Yeah, that getvar all suggests that the June 2017 fastboot flash didn't work.

You've got a bootloader version of B1:06 (June 2017)

Your system is NPJ25.93-14/16 - the December 2016 build.

This is supported by the baseband ending in .62R (December 2016 and March 2017 builds), and your kernel having a build date of 6th Jan 2017.

Thus, your device is likely still on the December 2016 firmware.

I strongly recommend attempting to reflash the June 2017 NPJS25.93-14-8 firmware.
[Moto G4 Plus Guides, News, & Discussion] chouhanprem:
Thanks for Your Support i am going to do it again.. just now and reply here

---------- Post added at 02:03 PM ---------- Previous post was at 01:49 PM ----------

I have apply the procedure again but still same condition . ?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Have you still got the output of your flashing commands from ADB? I'd like to see if there was anything amiss with the flash.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Thanks, and just to clarify - you cleared out your adb folder and copied over a new copy of the June 2017 fastboot ROM? Just want to make sure that the right ROM was flashed. Does the info.txt file mention NPJS25.93-14-8?
[Moto G4 Plus Guides, News, & Discussion] chouhanprem:
Yese i clear out all old files and copy all new fresh June 2017

BUILD REQUEST INFO:

SW Version: athene-user 7.0 NPJS25.93-14-8 8 release-keysM8952_70030.25.03.62.01R

MBM Version: B1.06

Modem Version: M8952_70030.25.03.62.01R

FSG Version: FSG-8952-05.30.01

Build Fingerprint: motorola/athene/athene:7.0/NPJS25.93-14-8/8:user/release-keys

VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:

System Version: 25.211.8.athene.retail.en.US

Model number: Moto G (4)

Android Version: 7.0

Baseband Version: M8952_70030.25.03.62.01R

Build Number: athene-user 7.0 NPJS25.93-14-8 8 release-keys

Build Date: Thu Jun 8 05:01:36 CDT 2017

OTHER MISC VERSION INFO:

Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm

Regulatory Info (eLabel): regulatory_info_default.png

Blur Version: Blur_Version.25.211.8.athene.retail.en.US

Version when read from CPV: athene-user 7.0 NPJS25.93-14-8 8 release-keys
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hrm, I'm going to think on this, but it looks like downgrading and then attempting to update your device by OTA has seriously corrupted something that even a re-flash of the stock ROM can't fix. This unfortunately could be one of the results of downgrading :( It's also possible that your internal flash memory may have failed inadvertently.

If you can't afford to wait, you could visit a service centre and ask them to attempt to re-flash the firmware for you. If that doesn't work, it might mean a motherboard replacement (expensive), or saving up for another device. You may wish to wait and see if anyone else suggests any other ideas.
[Moto G4 Plus Guides, News, & Discussion] chouhanprem:
Ok I wait for it hope i u got some me..anyways thanks for your support.:good:
[Moto G4 Plus Guides, News, & Discussion] xCALIFIER:
Thanks it solved my problem after dead by OTA update. For me flashing the stock rom was not necessary. just Reboot.
[Moto G4 Plus Guides, News, & Discussion] chouhanprem:
One problem it i find when i charge my phone in switch off condition it restart direct.
[Moto G4 Plus Guides, News, & Discussion] chouhanprem:
Is there any solution for my moto g plus
[Moto G4 Plus Guides, News, & Discussion] n.v.:
Blank Flash FAILS... is my G4 Plus beyond hope?

Yesterday, my G4 Plus (NOT rooted, running June 1 security patch ) was working perfectly, as it has been for months. No unusual behaviors or stresses to the phone (excessive heat/moisture/etc.). Then, suddenly, as I was streaming some audio, the phone simply went dead. Pretty sure I had plenty of charge in the battery. But then I could not turn it on again and only got the blinking white LED light when plugged into a charger. UGH! I've tried every version of leaving the phone on the charger, button push combinations, varying time of button pushes (sometimes over 2 mins) and... NOTHING.

That led me here, and I was so excited to find a solution that looked so promising! Unfortunately, however, I have run into what seems like an insurmountable problem. When I plug my phone into my PC (Win 10), it is recognized as Qualcomm HS-USB QDLoader 9008 but then when I run the blank flash utility, it fails. I've tried it twice now and here's the result (image attached).

[IMG="CMD Log"]https://i.imgur.com/sh6LFb9.jpg[/IMG]

Can anyone recommend a way to get around this, or do I have an unrecoverable brick on my hands? If I can't get this up and running within 24 hours, I'll simply have to buy a new phone, darn it. Does anyone have any clue what would cause a perfectly working stock phone to simply die like this? I can only imagine some kind of hardware/motherboard failure.

In any event, I would be TREMENDOUSLY grateful for any help!
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
If your phone suddenly went blank and IF your phone was running June security patch then I think you need to press vol down and power button for about 20-30 sec. make sure your phone is not connected to pc or charger. then it will reboot your phone to boot-loader mode and then simply flash the Stock Rom with June security patch from pc. this was happened to me some months ago when my phone was running Stock rom with march security patch. it suddenly turned off and it was not turning on. PC was detecting as Qualcomm 9008 mode but this trick worked for me at that time. give it a try :good:
[Moto G4 Plus Guides, News, & Discussion] n.v.:
Oh, do I wish it were that simple! That was one of the first things I tried... long before I found your thread that has helped so many people. But unfortunately, it just doesn't work - whether plugged into the charger or not. (I just tried it again, with the same result.)

I'm now going to try the steps in this post, in hopes that it might have a positive result.

Anyone else have ideas?
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
I checked, and I can clearly see that it has the same files that are posted on this thread with more extra spicing like booting your pc in test mode blah blah blah.

but all files are same
[Moto G4 Plus Guides, News, & Discussion] n.v.:
Yes, I believe you are right. "Extra spicing!"

Even so, I've followed that method as well (reboot PC in test mode, etc.) and I'm still getting hung up at the same place: the Blank Flash ends in failure. The device is clearly recognized, but for some reason, the blank flash process won't complete successfully, so I can't proceed to the next steps. SO FRUSTRATING!! And of course my phone is out of warranty :crying:

I'll keep monitoring this thread in hopes that someone recognizes a way to solve my problem.
[Moto G4 Plus Guides, News, & Discussion] chouhanprem:
Is There any solution for my device moto g plus
[Moto G4 Plus Guides, News, & Discussion] codGmer:
I have moto g4 plus xt1642 and it is bricked. I want to follow your guide but i can't get my phone to go into this:

. My phone just boots into a locked bootloader and i cant do anything anymore, even unlocking bootloader is impossible.
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
Flash gpt and bootloader files

It will unlock the bootloader

Follow the guide
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
Because those files are signed by Motorola and do not required unlocked bootloader and after flashing them your bootloader will be unlocked automatically then you can simply flash the stock ROM
[Moto G4 Plus Guides, News, & Discussion] codGmer:
i just get the message 'cannot find partition gpt'.

bootloader info:

(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: 74f9d6fa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: A420B70000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.147s
[Moto G4 Plus Guides, News, & Discussion] vikkyv:
Volte Flag gone after flashing the rom

After flashing the stock rom which you provided phone working well :D :D :D thanks to you but now volte flag is gone can please provide me any solution

my device is moto g4 plus xt1643 :confused: :confused:
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
Make sure your sim is in 1st slot and enhanced LTE mode is turned on.
[Moto G4 Plus Guides, News, & Discussion] ilnaidu:
Thanks bro. My phone back to life.
[Moto G4 Plus Guides, News, & Discussion] FelipeCadal:
Thank you very much! It finally works (after thousand times trying and geting milions of errors). You guy are awesome!
[Moto G4 Plus Guides, News, & Discussion] Draconfla:
Many thanks .. I did the tutorial and revived my g4 ..