yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] cooldude1598:
Blank flash failed Moto g4 plus

tried re-inserting cable but blankflash is showing failed.

It detected my device as ******Dloader 9008

Link for pic -https://ibb.co/c4Cr7c

here is the log

**** Log buffer [000001] 2018-02-25_15:30:54 ****

[ -0.000] Opening device: \\.\COM7
[ -0.000] ERROR: device_open()->error opening device
[ -0.000] Check qboot_log.txt for more details
[ -0.000] Total time: -0.000s
[ -0.000]
[ -0.000] qboot version 3.40
[ -0.000]
[ -0.000] DEVICE {
[ -0.000] name = "\\.\COM7",
[ -0.000] flags = "0x60",
[ -0.000] addr = "0x28FE6C",
[ -0.000] api.bnr = "0x602FC8",
[ -0.000] }
[ -0.000]
[ -0.000]
[ -0.000] Backup & Restore {
[ -0.000] num_entries = 0,
[ -0.000] restoring = "false",
[ -0.000] backup_error = "not started",
[ -0.000] restore_error = "not started",
[ -0.000] }
[ -0.000]

**** Log buffer [000001] 2018-02-25_15:32:21 ****

[ -0.000] Opening device: \\.\COM8
[ -0.000] ERROR: device_open()->error opening device
[ -0.000] Check qboot_log.txt for more details
[ -0.000] Total time: -0.000s
[ -0.000]
[ -0.000] qboot version 3.40
[ -0.000]
[ -0.000] DEVICE {
[ -0.000] name = "\\.\COM8",
[ -0.000] flags = "0x60",
[ -0.000] addr = "0x28FE6C",
[ -0.000] api.bnr = "0x702FC8",
[ -0.000] }
[ -0.000]
[ -0.000]
[ -0.000] Backup & Restore {
[ -0.000] num_entries = 0,
[ -0.000] restoring = "false",
[ -0.000] backup_error = "not started",
[ -0.000] restore_error = "not started",
[ -0.000] }
[ -0.000]

Please Help Me[IMG="CMD blank flash failed"]https://ibb.co/c4Cr7c[/IMG]
[Moto G4 Plus Guides, News, & Discussion] echo92:
If you're running Windows 8.1 or 10, can you check if driver signature enforcement is disabled, please?

The blankflash may require several tries to get it working, and you may have to try this sequence as well.

Credit to: https://xdaforums.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

How did your device get into a hardbrick?

Also, please verify that the cable you're using is a high quality data USB cable or the original Motorola USB cable.
[Moto G4 Plus Guides, News, & Discussion] kakukkmarci:
You are a genius!

Save my life :D!
[Moto G4 Plus Guides, News, & Discussion] Blueman1990:
this method work in latest december security patch any try please tell me ?
[Moto G4 Plus Guides, News, & Discussion] echo92:
It's not conclusive if this blankflash works with the latest December 2017 patch - there've been a few reports that suggest this blankflash does, and there have been others which have struggled to rescue their device with this blankflash.

If you've hard bricked, you could try this blankflash with the December 2017 GPT and bootloader, and report back. If you've not hardbricked, then please do not flash old stock firmware (older than the most recent stock firmware on your device) and then accept OTA updates.
[Moto G4 Plus Guides, News, & Discussion] ZaidFaris:
Error opening device

I am having moto g4 plus I recently rooted my device and unlocked the bootloader then I installed some custom roms and then installed the adroid 6 stock rom and later updated my phone toh android 7.. and my phone is hard bricked I tried a lot of time woth diffrrent blank flash files but still the same message error opening device... also my pc motherboard is 32 bits is that the reason???.... please reply this asap... I would be very thankful to you.... pls help me out... my device is moto g4 plus XT1643
[Moto G4 Plus Guides, News, & Discussion] echo92:
Are you using the blankflash from this thread? This is the latest blankflash we have access to - the ones in the opening post of the other thread you posted in may not work (as you've found out).

Try this blankflash and be aware it may take several attempts to connect to your device. Also, use the original USB cable if you can or a high quality USB data cable. Your PC motherboard should not matter - 32 bit or 64 bit architecture shouldn't matter.

As a warning to others, if you do flash older stock firmware (older than the stock firmware on your device), please do not use OTA updates. Only update with stock firmware until your device is on the newest firmware for your device region.
[Moto G4 Plus Guides, News, & Discussion] ZaidFaris:
Thanks for the reply.... Yes. I used blankflash from this thread but it didnt worked... I borrowed my friends laptop and it was successful and now i am typing this message from my moto g4 plus thanks to all you guys... I dont Know what's the problem with my pc... Any ways its done and i am happy all thanks to you guys... And i didnt install the stock from i just went into the recovery mode and my phone turned on and the update continued and it was completed... And when it turned on my phones battery was 1% so i think my battery wasn't charged and may be that's the reason behind opening device error
[Moto G4 Plus Guides, News, & Discussion] acetheapurva:
I initially had February update for Motog4 plus, then i added a custom rom of 64 bit, due to some things i thought of going back to stock rom [December Update], that is also done, after that I got an OTA update for my phone, while it was getting installed, screen went off and nothing till now.

I had my volume button broken so i tried this method

I entered the bootloader but while flashing gpt.bin i get the following error

(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.004s]
writing 'partition'...
(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

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

I know it is due to older firmware and OP it was mentioned that this is for older version, where do i get new versions of GPT and BlankFlash
[Moto G4 Plus Guides, News, & Discussion] echo92:
Which December stock ROM did you flash? If you flashed the December 2017 stock ROM (NPJS25.93-14-13), I don't think we have an OTA update yet (I've not seen any mention of the February 2018 stock ROM security patch released yet), and since this stock ROM build is possibly the one directly before the Feb 2018 security patch, taking an OTA from this build would not likely brick your device. However, if you flashed the December 2016 (NPJ25.93-14) stock ROM, then yeah, you may have likely hard bricked when you took the OTA.

Which GPT and bootloader are you using? That error as you mentioned is from trying to flash a GPT/bootloader older than your current bootloader version (you cannot downgrade bootloaders usually). All the recent GPT and bootloaders from the stock firmware are mentioned in the opening post, or here's the direct Google Drive link to that folder: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M I've pulled the GPT and bootloader files from their respective stock firmwares, with NPJS25.93-14-13 (Dec 2017) being the latest stock firmware that has been leaked.

However, if you genuinely had the February 2018 stock ROM security patch (custom ROMs do not matter in this regard), then these files won't work as they're too old, and you'll have to wait for the leaked Feb 2018 stock ROM to rescue your device. Try the Dec 2017 GPT/bootloader and see how you get on.
[Moto G4 Plus Guides, News, & Discussion] acetheapurva:
Looks like I got lucky, I was using files of June, browsing through the thread I got December Update's gpt and bootloader, which worked. Sorry for posting I should have browsed through the thread first.

Thank You :D :D
[Moto G4 Plus Guides, News, & Discussion] echo92:
Good to hear your device is working again :)

I would recommend you flash the December 2017 stock ROM (NPJS25.93-14-13) in full to fully repair your device. At the moment, you've got a Dec 2017 GPT/bootloader and Dec 2016/March 2017 system. Attempts to take OTAs again will likely result in more hard bricks, unless you either do not use and remember not to use OTA updates or formally and fully update your device to the same firmware patch level as your bootloader, after which OTA updates should be safe to use.

If you wish to, in the fastboot flashing commands, you can omit 'fastboot erase userdata' to save your data, but if you've re-flashed back to stock ROM, your device may be clean anyway, so it's up to you if you wish to keep or omit that command.
[Moto G4 Plus Guides, News, & Discussion] acetheapurva:
Hi again,

The guide did work for me, I got stock ROM back again, then i started to root it again, flashed TWRP, was rooting using MAGISK 16, I didn't knew we needed to use a custom kernel for flashing that. So I ended up bricking my phone again.

This time it's not detecting the device but the LED notifications light is still glowing,

Last time when i did lsusb[A command that lists your actively listed usbs] the device was showing there but this time its not showing any Qualcom%, How do I get it detected .. Pls. Help :(
[Moto G4 Plus Guides, News, & Discussion] acetheapurva:
Okay now even sad, i kept my phone connected to my pc for like 3 hours, still device is not found, but now when i removed the data cable from phone, I pressed the power button it showed no battery symbol. Help Me pls.... Thanks In advance...
[Moto G4 Plus Guides, News, & Discussion] echo92:
Ah, that's not good - normally, we'd suggest booting to the bootloader, then going to recovery and restoring the backup you made in TWRP (you did make a backup?) or re-flashing the stock ROM. However, as you mentioned your volume button is damaged, I'm not sure how you'd be able to boot into the bootloader at this stage :(

If you're certain you cannot use the volume keys and power keys to boot to the bootloader or TWRP, then the only way I can see is a service repair (of the physical volume keys, then a stock ROM reflash), or you could try to replace the volume keys yourself if it's the plastic keys rather than the motherboard contacts.
[Moto G4 Plus Guides, News, & Discussion] Hemanth_007:
Start Up Failed:

Hi Brother My device is showing Fastboot Mode But when i hit start it is showing the following message

Start Up Failed:

Your device didn't start up successfully.

Use the Software Repair Assistant on computer

to repair your device.

Connect your device to your computer to get

the Software Repair Assistant.

does this method work's for me[can i solve this problem with this method] My Device:Moto g4 plus.Xtl643.

Hope i will get the reply.

Thank you.
[Moto G4 Plus Guides, News, & Discussion] echo92:
I wouldn't use this method to repair your device. If you can still boot into fastboot, then you may wish to attempt to re-flash the latest stock ROM for XT1643 (NPJS25.93-14-13) https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Bear in mind that you do not have to re-lock your bootloader, but you may have to use the 'fastboot erase userdata' command, which will erase your data.

If a full firmware flash of the stock ROM does not work, then try flashing each command manually and in sequence (copy paste each command individually, starting with the first command, into the ADB terminal. Press Enter and wait for [OKAY] to appear. Continue down the sequence of commands in order until you reach the bottom).

If that still doesn't work, you may have to submit your device for a service repair.
[Moto G4 Plus Guides, News, & Discussion] Hemanth_007:
Thank you very much brother This Guide is working.

Now i got my Device Working .

Earlier i got Startup Failed message then i followed the guide skipping blankflash then it worked.

Question:can any one please tell me how to relock my boot loader .

Thanks .
[Moto G4 Plus Guides, News, & Discussion] echo92:
If you want to re-lock your bootloader:

a)Locking your bootloader will erase your data. Also will mean you cannot flash anything custom (no TWRP/root/custom ROMs). If you want to unlock your bootloader at a later date, again, you will erase your device.

b)Locking your bootloader will not restore your warranty. Depending on your local consumer laws, this may mean you have to pay for a warranty repair.

c)You do not need a locked bootloader to receive OTA updates, OTA updates will work on unlocked (flashing_unlocked on the bootloader screen) and locked (OEM_locked) bootloaders.

If you're okay with a) and b) then:

1)Boot to system, then go to Settings>Developer Options. Turn on OEM unlocking. If you do not have Developer Options, go to Settings>About Phone, then tap the build number 7 times.

2)On your computer, ensure you have the latest stock ROM, or at least the same stock ROM build as the latest firmware on your device, on your computer. For most devices this is NPJS25.93-14-13 (Dec 2017 security patch). Note, this firmware will not work for the latest NPJS25.93-14-15 (Feb 2018 security patch) until we get the Feb 2018 firmware. Verify the firmware is extracted and copied to the ADB directory (which it should be if you repaired your device)

3)Boot your device to the bootloader and flash with the full OEM locking instructions as in this guide: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Up to you if you use the script or flash manually.
[Moto G4 Plus Guides, News, & Discussion] RaphaBraga23:
Someone. Already. Got the rom with the February patch to flash? Well my g4 bike is bricked so he made the update via February February and the previous roms can not flash, only gets in the ice of bootloader, and still got blocked
[Moto G4 Plus Guides, News, & Discussion] jobs1992:
guys please, help me! i'm going crazy.

my moto g 4 xt 1626 updated and brinked

i did the post proceduce, but he presented this mistake,issui, error,failed

C:\Users\ana paula\Downloads\blankflash>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

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

[ 0.019] Detecting device

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

[ 4.059] Check qboot_log.txt for more details

[ 4.060] Total time: 4.060s

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

->IO error

C:\Users\ana paula\Downloads\blankflash>pause

Pressione qualquer tecla para continuar. . .

what can i do next?:crying:
[Moto G4 Plus Guides, News, & Discussion] echo92:
Try the blankflash a few times - also check you're using the original Motorola USB cable or a high quality USB data cable.

Which firmware did you have on your device before you hard bricked?
[Moto G4 Plus Guides, News, & Discussion] jobs1992:
this here

ATHENE_NPJ25.93-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info

i'm using de genuine cable of motorola and blankflash is here

https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
[Moto G4 Plus Guides, News, & Discussion] echo92:
That's a really old firmware (from December 2016) - the latest is NPJS25.93-14-13 (Dec 2017). I imagine you downgraded from a newer Nougat stock firmware and then accepted an OTA, which is a main cause of hard bricks.

You may have to use this trick: credit to https://xdaforums.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hrm, that's troubling - can you try the blankflash in this thread again please? That's the latest blankflash we have access to for Moto G4/Plus athene devices. I see from blankflash 1 it's suggesting it's too old to communicate with your device, whereas blankflash 2 and 3 are for the wrong device.

If that doesn't work, then unfortunately you'd either have to wait for a newer blankflash to be leaked (Motorola does not give these out as they are internal engineering tools) or pay for a new motherboard...
[Moto G4 Plus Guides, News, & Discussion] Emmglory:
Very unfortunate for me. My phone is not detected in my laptop to perform this process.

Only the led light is blinking forever while connecting via usb.

1. My windows 7 is upto date.

2. Latest Moto Drivers installed.

3. checked with different USB ports and with different cables.

No hope is seen till now.

Is there still a chance of hope for me?

I am really frustrated. Need nelp.
[Moto G4 Plus Guides, News, & Discussion] Hitpraja:
Big thanks

Huge thanks buddy.. u made my phone alive. Even Motorola official service center aaked me to replace mother board which coast equivalent to new phone. Hats off to u. :):good:
[Moto G4 Plus Guides, News, & Discussion] jadeilson777:
help
[Moto G4 Plus Guides, News, & Discussion] echo92:
Can you describe what happened to your device? I would like some more information...

Also, could you post clearer photos please? The contrast is not helping in reading the error messages.
[Moto G4 Plus Guides, News, & Discussion] Samuel Selvaraj:
Thank you so much, the last GPT file worked for me. It was awesome to see my phone back to life.
[Moto G4 Plus Guides, News, & Discussion] gourav343:
i used to get almost same error as you have got. after several tries i was able to bring back my moto alive using Blankflash mentioned in #1 post. trick is to be patient and try several time. This is exactly what i did (nothing new really)

t
[Moto G4 Plus Guides, News, & Discussion] Okahuma:
Hi guys. I was trying to get Magisk to work, so I was flashing a couple different stock ROMs. I took an OTA update. No dillydalling around it.

Newest Blankflash worked. Blankflash-1 didn't. Tried flashing the gpt.bin from june, then sept, then dec. All gave (bootloader) Security Version Downgrade.

Shouldn't that be impossible? Didn't the Blankflash substitute the gpt.bin for it's own?

Bootloader screen says BL is 1.06.

Seems like my hang is the gpt.bin version? Any help is appreciated.

Edit: var dump from fastboot

>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: moto-msm8952-B1.06(*)

(bootloader) product: athene_16mp

(bootloader) board: athene_16mp

(bootloader) secure: yes

(bootloader) hwrev: P2A

(bootloader) radio: 6

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG QX13MB 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: 37eae7c2

(bootloader) cid: 0x0032

(bootloader) channelid: 0x09

(bootloader) uid: 0B815F0100000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: yes

(bootloader) max-download-size: 536870912

(bootloader) reason: Volume down key pressed

(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.06-0-g0edfb0d

(bootloader) qe:

(bootloader) frp-state: no protection (err)

(bootloader) ro.carrier:

all: listed above

finished. total time: 0.172s

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

Update.

I managed to flash the gpt.bin from the OTA Feb 2018. Tried all the others before it. Then I flashed all other files from NPJS25.93-14-10. It bloody worked. Now I am stuck with the gpt.bin from the Feb 2018 update? Is there any way to downgrade this so I can have everything on the same page?
[Moto G4 Plus Guides, News, & Discussion] Damarcio:
Solution

I'm having this problem, please, some solution is beyond that step.
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
Until we get another BlankFlash Which is Compatible with The Latest February Patch, Its Impossible to get the Devices Back. And its not anytime soon because probably next Bankflash leak will be after Oreo update.. Until then Fingers Crossed..
[Moto G4 Plus Guides, News, & Discussion] Blueman1990:
December Patch blackflash is leak or not ?
[Moto G4 Plus Guides, News, & Discussion] Emmglory:
my phone is not detected in the laptop after installing the latest update of Moto drivers, I am desperate.. can anyone help me.? I have tried all what is instructed here..... since the phone is not detected in the laptop I am unable to do any further.....
[Moto G4 Plus Guides, News, & Discussion] Hellcho:
That blankflash worked pretty fine for me in a XT1641

Thanks a lot, that blackflash file saved my day, you're great!
[Moto G4 Plus Guides, News, & Discussion] Blueman1990:
with dec. patch 14.13?
[Moto G4 Plus Guides, News, & Discussion] Blueman1990:
please someone tell me this method work with December security patch(14-13) or not ?
[Moto G4 Plus Guides, News, & Discussion] Hellcho:
It worked with that 14.3 patch hard bricked instaling OTA Update

I had a hard brick when I allow the Febrary 2018 OTA update to install it, the backflash I've quoted allow me to break the hard brick into a soft brick, then I've flashed the NPJS25.93-14-15 ROM (The one with the last security update) and is working pretty fine. Have luck bringing it to life! :good:

---------- Post added at 08:06 AM ---------- Previous post was at 08:03 AM ----------

Hi there I've just found and test a newer stock ROM the NPJS25.93-14-15 proved on a mexican G4 Plus (I think it works well for all Latin America, don't know if it will in another regions), hope it'll be useful; the link is here (I didn't uploadead it, you will have to see 2 ******* screens before reaching the actual download) The guy's youtube channel from where I found the ROM is here. It includes gpt.bin bootloader.img for that version (with this file I avoid downgrading)

The Rom info is:

BUILD REQUEST INFO:

SW Version: athene-user 7.0 NPJS25.93-14-15 5 release-keysM8952_70030.25.03.62.02R

MBM Version: B1.07

Modem Version: M8952_70030.25.03.62.02R

FSG Version: FSG-8952-05.30.01

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

VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:

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

Model Number: Moto G (4)

Android Version: 7.0

Baseband Version: M8952_70030.25.03.62.02R

Build Id: NPJS25.93-14-15

SW Display Build ID: NPJS25.93-14-15

Build Date: Sat Feb 3 12:00:07 CST 2018

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.231.5.athene.retail.en.US

Version when read from CPV: athene-user 7.0 NPJS25.93-14-15 5 release-keys

AB Update Enabled: False

Full Treble Enabled: False

Hope it will be useful! :good:
[Moto G4 Plus Guides, News, & Discussion] echo92:
What errors are you getting if you try to flash the stock ROM? Do you detect your device on your computer if your device is in the bootloader mode?

Also, which stock ROM are you trying to flash?
[Moto G4 Plus Guides, News, & Discussion] Shreekarg:
I'm trying to flash <Moto G4 Plus XT1640-43 ATHENE NPJ25.93-14 Stock Img>

Device is detected perfectly but writing is failure. The main error is termed as remote failure.

https://imgur.com/C7G3Kd1
[Moto G4 Plus Guides, News, & Discussion] echo92:
You're flashing a really old stock ROM - that's the December 2016 stock ROM. Looks like your device has newer firmware on it (either from the firmware before the brick or the flash to repair your GPT and bootloader). I'd try flashing a much newer stock ROM that we have: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

I would recommend deleting the NPJ25.93-14 stock ROM you've got as that may cause you more problems in the future and lead to more hard bricks. Please only flash stock ROM firmware that's as new or newer than your bootloader. If your bootloader is B1:06 for example, then you will want June/Sept 2017 firmwares or newer.
[Moto G4 Plus Guides, News, & Discussion] Shreekarg:
Is the write error due to the old version i have ?

Or is it some other reason ?

Also can you provide Gdrive link? Android file host link is down.

https://xdaforums.com/showpost.php?p=76045343&postcount=318

This is the exact same error im having