yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] echo92:
What happened before this, were you flashing an update or firmware? If you've used this blankflash, then did you flash the GPT and bootloader?

If your device was hard bricked, you'd see Qualcomm HS-USB 9008 as you mentioned earlier. The fact you see the correct device recognised or fastboot Athene s does suggest your bootloader is still working.

If you power up your device to the bootloader (turn off your device, then hold down power and volume down key) them connect your device to your computer, do you see your device in the ADB terminal? If you have minimal ADB installed, then open an ADB terminal and type 'fastboot devices' without quotes. Do you see your device respond with a serial number?

It's possible it could be a screen issue or another hardware failing, let's see if we can communicate with your device and possibly try to flash it first.
[Moto G4 Plus Guides, News, & Discussion] kykinvc:
I don't know what happened with the phone before, but surely the person who owned it didn't mess with the firmware or tried to flash it. I can't use the blankflash because the phone is not recognized as qualcomm.

When the phone is recognized as Moto g(4) the ADB commands "adb devices" and "fastboot devices" don't respond anything, and when it is recognized as athene_13mp S, "adb devices" command doesn't show anything and "fastboot devices" command shows this serial number "ZY223KRNGX fastboot".

Thank you for your support echo92.
[Moto G4 Plus Guides, News, & Discussion] Jasman singh:
Then connect your phone to PC( Your phone should Be detected as QualcommLoader or something like that in device manager under the ports section )

Once connected, extract the Blankflash zip and run Blank-Flash.bat

the problem that i have encountered is my pc does not recogonize my device it does not show QualcommLoader it says unknow device or something and i have a bricked g4 plus what to do??? and thanks in advance.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, that suggests the bootloader is working properly - if you need this blankflash, you would not be able to boot to the bootloader and no fastboot commands would work (as your bootloader would be corrupted). I'm wondering if you're experiencing a bad firmware flash or a hardware fault.

When your device is booted, only ADB commands work (or should work) - fastboot commands only should work when your device is booted to the bootloader. You getting a response from fastboot devices is expected, though I wonder why adb devices doesn't work... - did you have USB debugging turned on your device before this?

Are you able to boot to the bootloader and pull the getvar info from it? That should tell us some information about the device.

1)Boot to the bootloader. Connect your device to your computer with a high quality USB data cable or the original USB cable.

2)Open up an ADB terminal on your computer. Type 'fastboot getvar all' without quotes into the terminal. Press Enter.

3)Please post or paste the info into a text file and upload that here, you may wish to omit your IMEI.

Given you have access to fastboot/bootloader commands, you should be able to flash fastboot stock images to your device.

---------- Post added at 02:23 AM ---------- Previous post was at 02:17 AM ----------

Have you installed the Motorola drivers? https://support.motorola.com/us/en/drivers Also, check you have driver signature enforcement disabled if you're running Windows 10 or 8.1, since that appears to interfere with loading the drivers if your device is booted in fastboot/bootloader mode. https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
[Moto G4 Plus Guides, News, & Discussion] kykinvc:
fastboot getvar all

I don't know if the USB debugging was turned on, but I don't think so. I couldn't find how to upload the text file but here is a link to see it, many thanks for your support echo92.

https://drive.google.com/file/d/1_J1rLWZ5FK9Fi_WhsuZvMKZeitloqAIt/view?usp=sharing
[Moto G4 Plus Guides, News, & Discussion] AlexBMoto:
Is my device super bricked

My phone started behaving very strangely, turning on/off randomly and freezing for long periods. I used twrp to wipe my phone in a desperate attempt to get it working again, but unfortunately it only made my device worse. I tried to flash stock firmware since it started acting up but the device isn't able to connect to my computer as I have usb debugging switched off, the phone is in such a state where I can't get past my sim pin screen as it freezes then turns itself off each time. I really cannot afford another phone just now so I would like to know if it is salvageable or if it's completely over for my device?
[Moto G4 Plus Guides, News, & Discussion] sanemi:
Hey guys, i need help with a G4 Plus a friend of mine gave me to see if i can unbrick it or something. Currently the device just keeps bootlooping with the Motorola logo over and over again. I got the unlock ID for the bootloader but since i can't boot into system, i can't check 'Allow OEM Unlocked' so that's not an option. I don't have any TWRP or recovery mode that i can access, only Fastboot. I tried to flash the stock rom, the bootloader and GPT from the first post and everything, but nothing changes the behaviour. The rom i believe was successfully installed since the logo changed to a newer one, but the loop keeps happening and i have no way of accessing the system/android.

When i try to install TRWP for example i get "(bootloader) Image boot failed validation | (bootloader) Preflash validation failed | FAILED (remote failure)", which i think it's expected since my OEM is locked and i can't install any imgs. Does anyone have any suggestions? Anything could be useful at this point, as i'm running out of ideas.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Try flashing this April 2018 fastboot ROM if you've not tried it already https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

Else, it may be a hardware issue that you'd need a service centre to look at.
[Moto G4 Plus Guides, News, & Discussion] sanemi:
Unfortunately that is the only ROM i tried so far, which updated the motorola logo to a different one, but the loop keeps happening, it's like the 'M' appears for 3 seconds and then automatically reboots. I'm still hoping to find a way to unbrick it without going to a service centre, which would cost a lot.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, do you have a flash log, I'd like to confirm that the flash was successful; i recall you mentioned there was a logo change, just want to make sure the system was flashed too. I guess you've tried a factory reset (or flashed with fastboot erase userdata)?
[Moto G4 Plus Guides, News, & Discussion] sanemi:
Hmmm i think i closed the cmd i had when i installed the new rom (i used the OEM Flash file included in the ZIP) , i still have the latest one where i tried to install the bootloader, GPT, and i even tried to install the rom again but manually using the commands in the first post, would that be useful? I can try to install it again as well.
[Moto G4 Plus Guides, News, & Discussion] AlexBMoto:
What have I done?

I just managed to fix my phone using your method but after updating it to Nougat, it became bricked again. I can't even retry your method that worked lasted time.
[Moto G4 Plus Guides, News, & Discussion] jontysaggu:
Thank you sooo much!!!!!

thanks you soooo much for this method. I just have one question that i have upgraded to December patch and i am having a notification of system update, i don't know the security patch for update but should i update it??? Will it be safe or will it again brick the device?
[Moto G4 Plus Guides, News, & Discussion] echo92:
That log would be useful, or another flash attempt would be useful. Sometimes using the OEM flash file may flash too quickly for any issues to be observed, but let's see what the log says.

---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------

Depends on what firmware you had previously - and if you saw security downgrade errors whilst flashing the bootloader or GPT. If so, then using the OTA update may be risky and may hard brick your device again. Which GPT/bootloader files did you flash? If they're December 2017 or newer, (NPJS25.93-14-13 or newer) then you may be okay. Older GPT/bootloader files may lead you to hard brick again. Without knowing how you hard bricked your device, it's tricky to say otherwise.

If you're getting the NPJS25.93-14-13 update, you may wish to re-flash with the latest stock firmware, NPJS25.93-14-18, which is the April 2018 security patch firmware. That way you don't have to worry about OTA updates and you'll update your device to the latest security patch in one go. https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
[Moto G4 Plus Guides, News, & Discussion] sanemi:
I tried to flash the stock ROM again and i saw several preflash validation failed for the bootloader. I don't think i got those before, i don't know if i made it worse :(
[Moto G4 Plus Guides, News, & Discussion] echo92:
Pre-flash validation errors usually are a sign that you're flashing an older stock ROM to your device on a locked bootloader. The locked bootloader is not a surprise as that's what your device/friend's device was in before.

Can you confirm that you are flashing the NPJS25.93-14-18 stock ROM to your device? If need be, delete any stock ROM files from your computer's minimal ADB folder, then extract the April 2018 security patch NPJS25.93-14-18 firmware and try again.
[Moto G4 Plus Guides, News, & Discussion] sanemi:
Just to be sure, i downloaded the Stock N Firmware from https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and created a new folder with the ADB files. I'm attaching the results again. The behaviour is the same, i see the new motorola logo (now blue and red, before it was white and light blue, for 3 seconds, then the screen goes black and the same keeps happening over and over again).
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hrm, unfortunately it looks like you may have to visit a service centre. This behaviour with a locked bootloader is looking more likely due to a hardware fault, which only a physical repair can fix. Just as a final thought, is this happening whilst the device is connected to power as well?
[Moto G4 Plus Guides, News, & Discussion] sanemi:
Yes, it happens while the device is connected to power as well. It seems like the only thing left is to take it to a service centre. Thank you for your help :)
[Moto G4 Plus Guides, News, & Discussion] jontysaggu:
Last time I tried to install lineage os but because of that I bricked my device and I have used December ROM and the gpt/bootloader files to bring back the device so, as per your saying if I try to flash the April patch directly so if it installs then it won't brick? Right and even I won't be getting any OTA notification as per the latest patch, but if it doesn't installs then? Will my device will continue to work on the older patch i.e December.?
[Moto G4 Plus Guides, News, & Discussion] jontysaggu:
I successfully updated to April Patch i.e NPJS25.93-14-18, thanks...:good:
[Moto G4 Plus Guides, News, & Discussion] DlickSeals:
Anyone else having issues just getting the blank flash to find the device? I did a complete system wipe and installed the update, (from stock 6.0), and it bricked during the reboot. I'm able to see the device in Device Manager, but I continue receiving a lot of ReadFile errors until the script eventually times out. I'm also noticing the MSM8952 comes back as unknown:

Any help is greatly appreciated!
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, is this with the original USB cable or another high quality data cable? Can you verify that you have driver signature enforcement disabled as well? https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/ you may also wish to flash the Qualcomm drivers from here https://xdaforums.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

Also, if you do get your device working, please delete any old stock ROMs and formally update your device to the latest stock firmware; for EU, UK, Brazil, India and Canada devices, amongst others, the latest is the NPJS25.93-14-18 firmware https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 if you don't flash firmware, then you may keep hard bricking with OTA updates until you do so.
[Moto G4 Plus Guides, News, & Discussion] Tengakallan:
Once again this thread saved my g4 plus .Thanks.
[Moto G4 Plus Guides, News, & Discussion] HumanSadness:
Help

Hello, I have a bricked G4 plus and this thing brought some life to it, the blank files stuff seemed to work, but when i try to insert the codes for the Bootloader and GPT files i get this:

C:\Users\Admin\Desktop\NPJS25_93_14_10_Sept2017_GPT_bootloader>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s

I dont know what to do, any help? :(
[Moto G4 Plus Guides, News, & Discussion] echo92:
That pre-flash validation error suggests the GPT/bootloader you're trying to flash (which is the Sept 2017 files) is too old. Try the April 2018 GPT/bootloader - https://drive.google.com/open?id=13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI and also flash the April 2018 stock firmware if you can: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
[Moto G4 Plus Guides, News, & Discussion] HumanSadness:
My phone owns you and the main post its life. Thank you.
[Moto G4 Plus Guides, News, & Discussion] AmberKat:
I did every step.

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:partition: not found

target reported max download size of 536870912 bytes

sending 'partition' (32 KB)...

OKAY [ 0.005s]

writing 'partition'...

(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.074s

C:\Users\User\Desktop\NPJS25_93_14_8_June2017>fastboot flash bootloader bootloader.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:bootloader: not found

target reported max download size of 536870912 bytes

sending 'bootloader' (3651 KB)...

OKAY [ 0.126s]

writing 'bootloader'...

(bootloader) validating: bootloader.default.xml ...

(bootloader) Invalid partition name aboot

(bootloader) will fail: flash:aboot

FAILED (remote failure)

finished. total time: 0.232s

Please help me with this.

the bootloader is locked and i cant unlock it.

the firmware is all wiped.

and i accidentally copied the wrong thing from the commands i saved for it in notepad.

how do i unlock it without getting "allow oem unlock in system" message when there is NO SYSTEM

-----------------------------------------------------------------------------------------------------

C:\Users\User\Desktop\NPJS25_93_14_8_June2017>fastboot oem unlock Z(BLANKXXXXXXXXXXX)P

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

...

(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer

(bootloader) Options

OKAY [ 0.012s]

finished. total time: 0.014s
[Moto G4 Plus Guides, News, & Discussion] fullwave66:
hi guys i tried anything but i my computer, with windows 10 x64 cant recognize the QDloader drivers, i cant see in device manager the driverd qualcomm device, i tried in other pc with windows 7 32 bits and is the same problem, i cant use blankflash mg4p in the command promp i see waiting for device, i know the problem is the drivers, but i dont know what is the problem why the pc cant recognize my moto g4 plus xt1641

my moto g4 is in AP fastboot mode (secure) the patch is 2017-06-01

somebody can help me???
[Moto G4 Plus Guides, News, & Discussion] Luke1212:
after getting in fastboot mode, an unexpected error arises now..

fastboot flash partition gpt.bin

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:partition: not found

target reported max download size of 536870912 bytes

sending 'partition' (32 KB)...

OKAY [ 0.008s]

writing 'partition'...

(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.080s

what to do now?
[Moto G4 Plus Guides, News, & Discussion] fullwave66:
well now i install manually the driver, i have now in device manager Qualcomm HS_USB QDloader 9008 (COM10) but i try to run blankflash MG4P but the console shows only waiting device, i try a lot of times and nothing, reboot the pc and nothing, i have windows 10 x64, and i disable windows defender, someone can help me with any idea??
[Moto G4 Plus Guides, News, & Discussion] echo92:
Are you using the original USB cable or a high quality USB data cable to connect to your device? Do you have driver signature enforcement disabled?

Which blankflash are you using - is it the one from this guide?

Have you seen and tried the tips here: https://xdaforums.com/showpost.php?p=73434849&postcount=2
[Moto G4 Plus Guides, News, & Discussion] fullwave66:
i use a original cable motorola is a high quality usb cable, and yes i have disable driver signature, i use blankflash MG4P the ultimate version i think, i login windows in proof mode, i have the moto g4 plus in AP fastbool flash mode (secure) the BL version shows 2017-06-01 i try a lot of things also windows 7 32 bits but the drivers dont work good in 32 bits i cant install manually the qdloader drives, and automatic install Motorola ADB drivers only.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Thanks - how did your device get into this bricked state, by the way?

What happens if you try the blankflash on the Windows 32 bit computer? Are you using USB 2 or USB 3 ports? It seems that USB 2 may be more reliable in getting the blankflash to work.

What bootloader version do you see (should start with B , Dec 2017 to April 2018 firmware should have B1:07, June 2017-Sept 2017 should have B1:06 etc)?
[Moto G4 Plus Guides, News, & Discussion] fullwave66:
in windows 7 32 bits the problem is the same, blankflash shows waiting device, i use USB 2.0 is a desktop PC i use the back usb ports the version of bootloader shows BL: B1.06 (sha-0edfb0d, 2017-06-01 12:10:43) the brick i think came well try to unlock sim port, the BL version i think is june 2017, in device manager i have drivers installed see the pic.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, trying to unlock SIM port, I'm not sure what you mean, can you elaborate? What firmware were you running before the brick, and was it a downgrade at any point?

What happens if you open the blankflash, then unplug and connect your device to your computer? I'm wondering if getting the device loading whilst the blankflash is running would work.
[Moto G4 Plus Guides, News, & Discussion] fullwave66:
well the firmware what running before are android 7 and i not try to downgrade, and when i try to open blankflash, the command line open and shows WAITING FOR DEVICE, and yes when i run the blankflash the phone charge the battery, and in the device manager open the com port 10, but blankflash dont recognize the com port, i try too with the phone in the device manager how ADB INTERFACE, but the problem is the same, blankflash waiting for device only.

edit i read in some thread try to push power buttom for 3 minutes, and then reconect the usb cable, but nothing, blankflash only waiting device.
[Moto G4 Plus Guides, News, & Discussion] echo92:
I'm not sure you understood what I wrote. My suggestion was to:

1)Open the blankflash.

2)Unplug your device from your computer.

3)Re-connect your device.

Or you could try powering off your device and then turning it on whilst connected and the blankflash is open.

Do you have a computer with a licenced copy of Windows btw? I'm just wondering if there's a restriction due to the Windows licence.

Try another USB port or another computer if you can.
[Moto G4 Plus Guides, News, & Discussion] fullwave66:
thank you i try in another pc, i try with windows 7 64 bits or windows 8.1 64 bits well thanks again.
[Moto G4 Plus Guides, News, & Discussion] fullwave66:
well guys i think the thread is so confused, the blankflash works when the phone dont turn on, after use the blankflash, the moto g4+ turn on in ap fastboot(secure) in this moment, i usted the gpt and fastboot image, flashing in fastboot, and the phone reboot in fastboot original mode, after i flash the rom and the phone turn on fine.

thank you for the thread but the steeps they are not well explained. thank you, moto g4 plus works fine now.
[Moto G4 Plus Guides, News, & Discussion] fullwave66:
guys i have other problem, the g4+ works fine, but the imei is 0, works in some carriers, but i want to restore the original imei, i try install lineage os 15.1 but the imei is 0 too, someone can help me to restore the original imei?
[Moto G4 Plus Guides, News, & Discussion] jrock77420:
Didn't get very far

Got as far as flashing the blankflash.bat file and got this on my command prompt

C:\Users\J-Rock\Desktop\New folder (4)\ADB and Fastboot>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

[-0.000] Opening device: \\.\COM6

[ 0.001] Detecting device

[ 4.002] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error

[ 4.002] Check qboot_log.txt for more details

4.002] Total time: 4.005s

FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error

C:\Users\J-Rock\Desktop\New folder (4)\ADB and Fastboot>pause

Press any key to continue . . .

log said this

[IMG="log error messege"]http://tinypic.com/r/29g0d9w/9[/IMG]
[Moto G4 Plus Guides, News, & Discussion] echo92:
What device are you using this blankflash on, and have you tried running the blankflash multiple times? Sometimes, the G4 blankflash requires a few tries to connect.

Also, please delete the whole opening post that's been quoted, it's not necessary and makes it difficult to find your post.
[Moto G4 Plus Guides, News, & Discussion] jrock77420:
Moto E4 Plus Xt1766
[Moto G4 Plus Guides, News, & Discussion] echo92:
Ah, this blankflash only works on G4 or G4 Plus devices with a Snapdragon 617 CPU. As your device has a Mediatek chipset (my bad, only for the E4 variant), this blankflash likely won't work. You'd have to find a E4 plus specific blankflash or a blankflash for another Motorola device family running the same chipset.
[Moto G4 Plus Guides, News, & Discussion] jrock77420:
Okay but if it's mediatek, why does it install the qualcomm driver when plugged into usb?

---------- Post added at 09:00 AM ---------- Previous post was at 08:53 AM ----------

its the Owens version, so it has to be Qualcomm, doesn't it?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Ah, that's a good point - so you've got the variant with the Qualcomm Snapdragon 427 (what confused me was the model number written in a previous post - Xt1766 instead of XT1776?)

Either way, unfortunately, this blankflash still won't likely work - you've got a different CPU (and also different bootloader) to the G4/Plus.