yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] davagolo:
hello, tell them that I use a translator so I may write some nonsense, sorry for that, I have the bootloader unlocked, recover my motorola g4 from a brick, but after loading the blanckflash, install the firmware NPJS25.93-14-18, without loading the GPT and boot-loader files, now I get my compilation number is NPJ25.93-14-4 and security patch 1 March 2017, I get to update by ota to NPJ25.93-14-8, which I did not do for fear that my phone was bricked. Could you tell me how it would be the right way so you can update and then update by ota without problems. Thank you.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, if you flashed the NPJS25.93-14-18 (April 2018) firmware, how are you back on the March 2017 firmware? I suggest deleting stock ROM files from your ADB folder, downloading or extracting a fresh copy of the NPJS25.93-14-18 firmware to your ADB folder and try flashing again.

If your device is on the March 2017 firmware, I would really not use OTA updates, else you'll hard brick again as it's possible that your firmware is much older than your bootloader version - the mismatch between a newer bootloader and an older stock firmware is a common cause of hard bricks if you try to use OTA updates. This is especially the issue as you've not used the GPT/bootloader, so I don't know what bootloader version is on your device. Thus, I cannot recommend OTA updates at all until your device is on the same version of firmware as your bootloader. The easiest way is to flash the newest firmware available - please avoid flash older firmwares and then use OTA updates unless you know what version you're flashing/updating to.

Here's the link for the April 2018 firmware: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not need to use the OEM lock commands if you do not wish to re-lock your bootloader.
[Moto G4 Plus Guides, News, & Discussion] joaoggb:
Hello, I am getting the following error with blankflash

the log as follows

**** Log buffer [000001] 2018-10-10_19:24:32 ****

[ 0.000] Opening device: \\.\COM4

[ 0.031] Detecting device

[ 0.031] ...cpu.id = 2418 (0x972)

[ 0.031] ...cpu.sn = 42127117 (0x282cf0d)

[ 0.031] Opening singleimage

[ 0.375] Loading package

[ 0.375] ...filename = singleimage.pkg.xml

[ 0.391] Loading programmer

[ 0.406] ...filename = programmer.mbn

[ 0.406] Sending programmer

[ 0.625] Handling things over to programmer

[ 0.625] Identifying CPU version

[ 0.625] Waiting for firehose to get ready

[ 62.432] Waiting for firehose to get ready

[124.320] ...MSM8952 unknown

[124.320] Determining target secure state

[124.320] Waiting for firehose to get ready

[186.042] ...secure = no

[186.042] Flashing GPT...

[186.089] Flashing partition:0 with gpt_main0.bin

[186.089] Initializing storage

[186.089] Waiting for firehose to get ready

[247.944] Configuring device...

[247.944] Waiting for firehose to get ready

[309.707] Waiting for firehose to get ready

[371.762] Waiting for firehose to get ready

[433.540] Waiting for firehose to get ready

[495.422] 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

[495.422] Check qboot_log.txt for more details

[495.422] Total time: 495.438s

[495.422]

[495.422] qboot version 3.40

[495.422]

[495.422] DEVICE {

[495.422] name = "\\.\COM4",

[495.422] flags = "0x64",

[495.422] addr = "0x28FE5C",

[495.422] sahara.current_mode = "0",

[495.422] api.buffer = "0x5B2020",

[495.422] cpu.serial = "42127117",

[495.422] cpu.id = "2418",

[495.422] cpu.sv_sbl = "0",

[495.422] cpu.name = "MSM8952",

[495.422] storage.type = "eMMC",

[495.422] sahara.programmer = "programmer.mbn",

[495.422] module.firehose = "0x95D508",

[495.422] cpu.ver = "0",

[495.422] cpu.vername = "unknown",

[495.422] api.bnr = "0x468910",

[495.422] }

[495.422]

[495.422]

[495.422] Backup & Restore {

[495.422] num_entries = 0,

[495.422] restoring = "false",

[495.422] backup_error = "not started",

[495.422] restore_error = "not started",

[495.422] }

[495.422]

Any ideas? Thanks in advance
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, how did your device get in this state, and what device do you have?

I'd try the blankflash a few times, sometimes the blankflash doesn't communicate with your device properly (which looks to be the issue; the programmer isn't getting a response from your device, so can't open the firehose to begin flashing). Also check you're using a good quality USB data cable.
[Moto G4 Plus Guides, News, & Discussion] joaoggb:
Moto G4 Plus, XT1640. No idea how it happened, it just froze the other night and wouldn't turn on again, shows the same symptoms as some other bricked devices (screen doesn't turn on, white led blinking while connected in the charger) . USB cable is good, I'll keep trying the blankflash.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Thanks for that. Usually a blankflash is for rescuing devices bricked by bad firmware updates or installing old inappropriate OTA updates. From what you've mentioned, it seems like you may have a hardware fault. The blankflash is still worth a try; on your computer does your device present as a Qualcomm HSUSB 9008 or similar?

If the blankflash still has trouble communicating, you may have to consider a service centre visit.
[Moto G4 Plus Guides, News, & Discussion] joaoggb:
Yeah, it shows up as Qualcomm HS-USB 9008.

Forgot to mention, the phone managed to boot up once yesterday, was able to use it for a good few minutes before it just froze and died again.

Haven't messed with firmware or anything of the sort on this device.

Guess I'll take it to a repair shop.

Thanks for the help and the quick replies
[Moto G4 Plus Guides, News, & Discussion] MGrad92:
I'm having this same issue, but when I try to run blankflash, it gets stuck on "waiting for device" and that never goes away. I've loaded the Motorola drivers and my device DOES show up in the device manager as "Fastboot athene_13mp S" ... and I've tried multiple USB cables including others that seem to work for charging and communication with other devices.

Is there anything else I can do? I've also tried using the Software Repair tool from Lenovo, but that just says that it can't communicate with the device (I've tried about 80% of the devices listed under Motorola, and especially the actual one, XT1625, but it won't actually do anything).

EDIT: I think I've figured out the reason why the Lenovo repair tool isn't working ... when I look at the Switch Tools Mode screen in the fastboot menu of the phone, under Product/Variant, it shows "athene_13mp 00000000000000 32 P2A". According to what I've seen online, this SHOULD say my model number (XT1625) ... but it doesn't, so I don't think the Lenovo tool will recognize it.

Any idea how I can rectify this?
[Moto G4 Plus Guides, News, & Discussion] mohitsaini1611:
Please Help me

Hello Sir,

Please help me....

when I'm trying to flash gpt & bootloader it shows following getvar

C:\Users\mohit\Desktop\moto\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.007s]

writing 'partition'...

(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.083s

C:\Users\mohit\Desktop\moto\NPJS25_93_14_10_Sept2017_GPT_bootloader>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.121s]

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 what shall i do to Make my device back to life. :(
[Moto G4 Plus Guides, News, & Discussion] echo92:
You're likely seeing the 'security version downgrade' and 'preflash validation error' messages as you're attempting to flash a GPT/bootloader than the most recent one on your device.

Please try either the April 2018 GPT/bootloader from here: https://drive.google.com/open?id=13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI or flash the April 2018 stock firmware from here: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
[Moto G4 Plus Guides, News, & Discussion] NileshIndalkar:
Code:

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot reboot-bootloader

im getting error when try to execute above commands after blankflash

(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.010s]

writing 'partition'...

(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.093s

Even tried with sept , dec bootloader and gpt files.

Plesae help me!!!!!

On g4 screen showing

AP Fastboot Flash mode(secure)

oem_locked

software status : Modified

---------- Post added at 03:21 PM ---------- Previous post was at 03:20 PM ----------

Code:

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot reboot-bootloader

im getting error when try to execute above commands after blankflash

(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.010s]

writing 'partition'...

(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.093s

Even tried with sept , dec bootloader and gpt files.

Plesae help me!!!!!

On g4 screen showing

AP Fastboot Flash mode(secure)

oem_locked

software status : Modified
[Moto G4 Plus Guides, News, & Discussion] echo92:
The security downgrade error you're getting suggests you're attempting to flash too old GPT and bootloader files.

Please try flashing the April 2018 GPT and bootloader from either the stock ROM https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 or you can download just the GPT and bootloader April 2018 files from here: https://drive.google.com/open?id=13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI

After using the GPT/bootloader files, please full flash the latest April 2018 stock ROM. If you want to flash an older stock ROM (not matching your GPT/bootloader) avoid using OTA updates.
[Moto G4 Plus Guides, News, & Discussion] the_kumar_karma:
flashed every thing sucessfully.

writthen the laast code i.e fastboot reboot ..... then the phone didnt booted insted just white led blinking.

no fastboot no recovery also not getting recognised by pc.

help ploxx...
[Moto G4 Plus Guides, News, & Discussion] echo92:
I'd like to request some more information for us to better assist you:

1)What device do you have (model number too if possible), and what firmware did you have running before?

2)What happened to your device before your device failed (e.g. were you applying an update or did it fail randomly and suddenly without you doing anything)?

3)Which firmware did you flash to your device using the commands?
[Moto G4 Plus Guides, News, & Discussion] the_kumar_karma:
1. Model XT1643

2. I was applying OTA update. Then it suddenly died.

3. Was flashing the Same firmware given in the 1st post /op.

Pls. Help .
[Moto G4 Plus Guides, News, & Discussion] echo92:
What firmware or security patch were you applying? Sounds like an old OTA patch got applied to your device and that may have hard bricked it.

Did you use the blankflash before flashing the firmware?
[Moto G4 Plus Guides, News, & Discussion] the_kumar_karma:
Yes maybe.

Yes I blank flashed then it got into fastboot.

Then completed the whole procedure as on 1st post. Everything flashed fine. But at last phone didn't reboot.

Now only the light is blinking and device not getting recognised by pc.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Couple of things to try:

If your device is still on, hold the power button for 30 sec to 1 minute until it hard reboots. See if it boots then.

Else if your device is powered off, try to hold down both the power and volume down keys to see if you can boot to the bootloader.

What firmware did you flash to your device, can you give us the filename of the firmware? Was it the December 2017 patch firmware or the April 2018 firmware?
[Moto G4 Plus Guides, News, & Discussion] the_kumar_karma:
The phone is in dead condition right now.

Same it was earlier before the process.

I flashed this "ATHENE_NPJS25.93-14-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" firmware.

And sept2017 bootloader.

Also not able to boot into bootloader/recovery/fastboot.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, that's troubling; though you had an old bootloader, your device should have been updated to the B1:07 bootloader with the December 2017 patch. That means your device would have been flashing the February 2018 OTA, when it got hard bricked.

When you flashed the December 2017 firmware, can you confirm that you saw [okay] with each flash command? Did you use any command with OEM locking mentioned?

The fact you can't see fastboot or any connection is not good, however. I'm starting to wonder if there's a hardware failure. Was your device working normally before all this happened?
[Moto G4 Plus Guides, News, & Discussion] the_kumar_karma:
Yes. "OKAY" was shown after every command.

No. Not used any command mentioned OEM locking.

Yes It was working fine before all this trouble.

The main problem I see here is not getting detected by pc. If it was detected I would have tried the full process again.

P.s. Which hardware is responsible for such failure?

Pls. Help.
[Moto G4 Plus Guides, News, & Discussion] echo92:
I honestly have no idea at the moment what could be causing your issue; it could be the USB port, or a corrupted flash memory, or a bad bootloader flash. I'm trying to establish what you've done.

So your device doesn't even show up in device manager anymore (even if it is the Qualcomm HS-USB 9008)?

If you disconnect your device from your computer, power off your device by holding down the power button, then reconnect your device to your computer, does your computer detect your device (does it make a sound) when you turn your device back on?
[Moto G4 Plus Guides, News, & Discussion] the_kumar_karma:
Yes.Not showing in device manager anymore.

The phone is not switching on. So how could I check by turning power on/off.

When connected to PC no detection on the syestem , just the white light on the phone blinks as it's just getting power.
[Moto G4 Plus Guides, News, & Discussion] echo92:
When I plugged my device into power, in fastboot, the LED briefly blinks but for me it doesn't blink constantly. If I recall, that blinking LED is your device trying to boot (someone please correct me if there's other scenarios where the LED comes on )

But if you've already tried to hard reboot (holding down the power button), that should perform nearly the same task, and you've mentioned that hard reboot doesn't work.

Hmm, I'm running out of ideas here, because your computer doesn't detect your device. Have you tried unplugging and re-connecting your device, and changing USB cables/USB ports?
[Moto G4 Plus Guides, News, & Discussion] NileshIndalkar:
Ok so Flashing latest stock with latest gpt and bootloader can i install ota update.???

Thanks man my phone about to re born(:fingers-crossed::fingers-crossed:))
[Moto G4 Plus Guides, News, & Discussion] HeethJain21:
Yes you can install OTA update, as it has been observed by other users.

However, I wouldn't recommend installing OTA. Whenever you want to ipdate, please flash the Stock firmware using fastboot. Anyways, we wont be recieving any OTA updates except official Oreo unless Lenorola gets generous.
[Moto G4 Plus Guides, News, & Discussion] NileshIndalkar:
Thankyou so much my phone back to life.. ??
[Moto G4 Plus Guides, News, & Discussion] BananenKeks:
Hey Guys,

i am seeking for help. My phone died on Monday in my hands. I was browsing Reddit and then it just froze and a few seconds later it crashed. After that i couldn't boot or do anything. I get the blinking light when putting it on power cable though. I can connect my device on my PC and i can find it as Qualcomm HS-USB QDLoader 9008. I have tried the blankflash of this thread multiple times and always end at the same point:

[242.215] Configuring device...

[242.217] Waiting for firehose to get ready

[427.420] Waiting for firehose to get ready

[490.985] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error

[490.985] Check qboot_log.txt for more details

The Log says following:

[490.988] DEVICE {

[490.988] name = "\\.\COM4",

[490.988] flags = "0x64",

[490.988] addr = "0x61FE5C",

[490.988] sahara.current_mode = "0",

[490.988] api.buffer = "0x12D6020",

[490.988] cpu.serial = "42455443",

[490.988] cpu.id = "2418",

[490.988] cpu.sv_sbl = "0",

[490.988] cpu.name = "MSM8952",

[490.988] storage.type = "eMMC",

[490.988] sahara.programmer = "programmer.mbn",

[490.988] module.firehose = "0xF8D2C0",

[490.988] cpu.ver = "0",

[490.988] cpu.vername = "unknown",

[490.988] api.bnr = "0xEA59C8",

[490.988] }

[490.988]

[490.988]

[490.988] Backup & Restore {

[490.988] num_entries = 0,

[490.988] restoring = "false",

[490.988] backup_error = "not started",

[490.988] restore_error = "not started",

[490.988] }

OP wrote this:

does this have to do anything with my problem? If so, is there something i can do?
[Moto G4 Plus Guides, News, & Discussion] HeethJain21:
That was for earlier, did you upgraded to April 2018 update once before this??

Press the power button + volume button while using the blankflash. Also try this by removing sim cards and mircosd card.

It doesn't take this lon (490 seconds) for the blankflash. It generally takes less than 10 seconds always (I have used it 4 times). Sometimes its just difficult for the blankflash to work so you may need to try this a couppe of times.

But before that, were you installing a OTA update?? If no then just try pressing power button for about 2 minutes.
[Moto G4 Plus Guides, News, & Discussion] BananenKeks:
As far as I remember, i did an Update earlier this year. Though i could be wrong, my feeling for time is messy lately.

I will keep trying.

OTA stands for "Over the air" right? Then yes, i installed my System Updates over WLAN.

Here is the full Log, i case it could help:

**** Log buffer [000001] 2018-12-12_17:41:06 ****

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

[ 0.001] Detecting device

[ 0.002] ...cpu.id = 2418 (0x972)

[ 0.002] ...cpu.sn = 42455443 (0x287d193)

[ 0.002] Opening singleimage

[ 0.002] Loading package

[ 0.004] ...filename = singleimage.pkg.xml

[ 0.006] Loading programmer

[ 0.006] ...filename = programmer.mbn

[ 0.006] Sending programmer

[ 0.226] Handling things over to programmer

[ 0.226] Identifying CPU version

[ 0.228] Waiting for firehose to get ready

[ 60.461] Waiting for firehose to get ready

[122.026] ...MSM8952 unknown

[122.026] Determining target secure state

[122.028] Waiting for firehose to get ready

[182.093] ...secure = no

[182.101] Flashing GPT...

[182.102] Flashing partition:0 with gpt_main0.bin

[182.102] Initializing storage

[182.105] Waiting for firehose to get ready

[242.160] Configuring device...

[242.161] Waiting for firehose to get ready

[303.230] Waiting for firehose to get ready

[366.299] Waiting for firehose to get ready

[427.862] Waiting for firehose to get ready

[489.427] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error

[489.427] Check qboot_log.txt for more details

[489.429] Total time: 489.431s

[489.430]

[489.430] qboot version 3.40

[489.430]

[489.430] DEVICE {

[489.430] name = "\\.\COM4",

[489.430] flags = "0x64",

[489.430] addr = "0x61FE5C",

[489.430] sahara.current_mode = "0",

[489.430] api.buffer = "0x12E3020",

[489.430] cpu.serial = "42455443",

[489.430] cpu.id = "2418",

[489.430] cpu.sv_sbl = "0",

[489.430] cpu.name = "MSM8952",

[489.430] storage.type = "eMMC",

[489.430] sahara.programmer = "programmer.mbn",

[489.430] module.firehose = "0xE9D020",

[489.430] cpu.ver = "0",

[489.430] cpu.vername = "unknown",

[489.430] api.bnr = "0x12259C8",

[489.430] }

[489.430]

[489.430]

[489.430] Backup & Restore {

[489.430] num_entries = 0,

[489.430] restoring = "false",

[489.430] backup_error = "not started",

[489.430] restore_error = "not started",

[489.430] }

[489.430]
[Moto G4 Plus Guides, News, & Discussion] echo92:
Looking at your log, I'd try Heeth21's suggestions. The log suggests the blankflash is having trouble connecting to your device successfully - the blankflash is sending over the 'firehose' to your device to prepare for a rescue flash, but appears to get no response and times out. Sometimes, repeating the blankflash can get it to work.

However, if your device suddenly failed as you described, that might begin to suggest a hardware failure. Any chance if you can remember what update you had on your device? Also, did you unlock your bootloader at any point as well?
[Moto G4 Plus Guides, News, & Discussion] BananenKeks:
What kind of hardware error are you thinking of? I mean it never made me problems, i haven't dropped it recently or anything else, it just came out of nothing.

The last Version on my phone i can remember was Android 7.0. I haven't done any fancy with it, just Stock software and updates.

No i didn't unlock the bootloader.
[Moto G4 Plus Guides, News, & Discussion] echo92:
The sort of hardware failure I'm thinking of is possibly a flash memory or flash memory controller failure. Your device seems to be partially booting from the primary bootloader on the SoC (getting you to the Qualcomm HS-USB 9008 state), but the failure of the blankflash to connect may suggest it cannot flash to your flash memory (holding your bootloader). The sudden failure of your device also may suggest a rather bad hardware failure.

Again, I'd try using the blankflash - maybe try another USB port/cable or another computer. There are reports suggesting that USB 2.0 ports may have better luck in getting the blankflash to work. Hopefully I'm wrong that it's a hardware failure and that the blankflash can connect and flash to your device.

However, as you've got a locked bootloader, our repair options are limited. Since your device was just working prior to the hard crash, a motherboard replacement may be a repair option, or alternatively, a new device altogether if the motherboard cost is too high. Good luck whichever you decide.
[Moto G4 Plus Guides, News, & Discussion] BananenKeks:
Thank you for your help. I'm gonna try to blank it a bit and if i don't succeed, i switch plans and bring it back to the retailer (it's not even 2 years old).

Have a nice day :)