yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Questions & Answers] echo92:
Security patch level of the custom ROM is not relevant in this case. Custom ROMs generally do not touch your device firmware. Stock Motorola firmware and Motorola OTAs do touch your device firmware.

What matters is the patch level of the stock ROM firmware from Motorola, which means both the firmware on your device and what you flashed. They must match or the firmware you're flashing could be newer. Can you remember if you had June or September 2017 stock Motorola firmware on your device, with the bootloader B1:06, before you flashed RR? If you did, then going back to an older (not even June, as you mentioned) version of stock is inadvisable - and as you found out, taking OTA updates caused a hard brick.

That likely happened because you had a newer bootloader (e.g. June 2017) but downgraded your system to an older stock (e.g. December 2016). Thus, when you took the OTA, the OTA flashed assuming your entire device was on December 2016, which is not a correct assumption. Because of the mismatch between your bootloader and system, the OTA may have patched your bootloader and thus corrupted it.

Delete your old stock ROM, and download a fresh copy of the latest stock ROM. https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 When you flash custom ROMs, try to note which stock firmware you had so you can flash the same version, and double check that you have the correct firmware on your computer.
[Moto G4 Plus Questions & Answers] rohitpaul9000:
pls help for moto x play
[Moto G4 Plus Questions & Answers] echo92:
Hrm, if you downgraded from the soak test 7.1.1 to MM as I'm reading from your posts, then you'll need to wait for a blankflash for 7.1.1. We've only been able to get them from leaks, so maybe the 7.1.1 stock ROM might have them?

Else, as others have suggested, you may have to pay to replace your motherboard. That's why downgrading is so risky, especially with newer updates...
[Moto G4 Plus Questions & Answers] AashuST:
moto g turbo blank flash needed ...

can anyone create one for moto g turbo?
[Moto G4 Plus Questions & Answers] strongst:
Until moto doesn't release/leak one, there will be no files. Please ask in the specific device forum.
[Moto G4 Plus Questions & Answers] horizonnn007:
my moto g4 plus is not even detected on pc as anything.

just white led light beeps.

i have installed all drivers.

kindly help....
[Moto G4 Plus Questions & Answers] MotoG4PlusQ:
Need help unbricking my phone

Hi All,

My phone is XT1644 and it bricked today when I tried to upgrade to the Nougat update from Mashmallow. So basically I followed the guidelines on blank flashing and on my first run I got the following...

-Flashing GPT...

-Flashing partition:0 with gpt_main0.bin

-Initializing storage

-Configuring device...

and then i got an error message after configuring device...its basically the same error as shown here https://dl.xda-developers.com/thumbs/4/2/8/9/9/3/3/4289933.png for another user.

now after this trial, I tried to run it again and for the past 2 hours this is what I got no matter what I did

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

[ 0.001] Detecting device

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

[ 4.009] Check qboot_log.txt for more details

[ 4.009] Total time: 4.010s

[ 4.009]

[ 4.009] qboot version 3.40

[ 4.009]

[ 4.009] DEVICE {

[ 4.009] name = "\\.\COM13",

[ 4.009] flags = "0x64",

[ 4.009] addr = "0x28FE6C",

[ 4.009] api.bnr = "0x3C8EE0",

[ 4.009] }

[ 4.009]

[ 4.009]

[ 4.009] Backup & Restore {

[ 4.009] num_entries = 0,

[ 4.009] restoring = "false",

[ 4.009] backup_error = "not started",

[ 4.009] restore_error = "not started",

[ 4.009] }

[ 4.009]

I have tried to use latest blank flash files but nothing is happening now. I have even used different usb slots on my computer (even rebooted the computer). Its basically not detecting the device since its not even showing the Phone cpu IDs. Any bright ideas out there? Oh by the way, my phone doesnt have a power button, so power+vol down doesnt work for me...what am I missing here :confused: ?

I would also like to know if its imperative that my windows computer be in test mode?
[Moto G4 Plus Questions & Answers] echo92:
Have you tried the blank flash in this thread here? This is the newest one we have currently (supporting B1:06 bootloaders) https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

As you're on the XT1644, you may have to repair your device with the US June 2017 stock ROM rather than the one linked in the above thread. https://xdaforums.com/showpost.php?p=73765316&postcount=208

By having no power button, do you mean the button's fallen out or doesn't work?

You may have to put your computer into test mode or at least disable driver signature enforcement if you're running Windows 8.1 or 10.

One last thing, delete that marshmallow stock ROM and replace it with the latest stock ROM or at least the stock ROM matching your device firmware, else you'll hard brick again. If you really want marshmallow, do not use OTA updates.
[Moto G4 Plus Questions & Answers] MotoG4PlusQ:
Hi Echo92 :)

Yeah I tried that one too. I even modified the batch file to let it run after 5 second intervals on errors cuz continuous clicking of the file was getting tediously annoying.

Yeah the power button has fallen out.

I will keep trying. Is there any reason why the program is not detecting the device even though the device manager sees the phone?
[Moto G4 Plus Questions & Answers] echo92:
Hmm, that blankflash should be working, as it's the latest one we have available...

Just asking, have you got the fastboot drivers, Motorola drivers and have driver signature enforcement disabled on your computer? I recall having driver enforcement active can block fastboot and maybe the blank flash.

Can you delete the blank flashes you've been trying, then download and use the one from the thread I linked, please? Just want to confirm that it's the right blank flash as they all look the same... Which USB cable are you using?
[Moto G4 Plus Questions & Answers] MotoG4PlusQ:
Yup I do. Its just weird that on the first run it was working with the blankflash1 until an error, and then after that all the other blankflash versions ( and the latest) dont work. Even the blankflash1 dont work now.

Yeah i did as you asked and I am running the latest. I get the same result.

[ 0.000] Opening device: \\.\COM14

[ 0.016] Detecting device

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

[ 4.087] Check qboot_log.txt for more details

[ 4.087] Total time: 4.087s

[ 4.087]

[ 4.087] qboot version 3.40

[ 4.087]

[ 4.087] DEVICE {

[ 4.087] name = "\\.\COM14",

[ 4.087] flags = "0x64",

[ 4.087] addr = "0x28FE6C",

[ 4.087] api.bnr = "0x508EE0",

[ 4.087] }

[ 4.087]

[ 4.087]

[ 4.087] Backup & Restore {

[ 4.087] num_entries = 0,

[ 4.087] restoring = "false",

[ 4.087] backup_error = "not started",

[ 4.087] restore_error = "not started",

[ 4.087] }

[ 4.087]

I am using the USB cable that came with the phone. I also have another USB from another phone and they both yield the same. When I view properties for device Qualcomm HS-USB QDLoader 9008 (COM14) , the port settings are:

Bits per second: 9600

Data bits: 8

Parity: None

Stop bits: 1

Flow control: None

Are you thinking that data stream thru usb cable might be to blame? should I try using a different computer and usb cable?
[Moto G4 Plus Questions & Answers] MotoG4PlusQ:
So I put the phone on a wall charger for 1 hour and then I got this message when I ran blankflash...

**** Log buffer [000001] 2017-10-09_08:33:03 ****

[ 0.000] Opening device: \\.\COM14

[ 0.001] Detecting device

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

[ 0.004] ...cpu.sn = 14518310 (0xdd8826)

[ 0.004] Opening singleimage

[ 0.024] Loading package

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

[ 0.037] Loading programmer

[ 0.038] ...filename = programmer.mbn

[ 0.038] Sending programmer

[ 0.260] Handling things over to programmer

[ 0.261] Identifying CPU version

[ 0.265] Waiting for firehose to get ready

[ 60.273] Waiting for firehose to get ready

[121.054] ...MSM8952 unknown

[121.054] Determining target secure state

[121.054] Waiting for firehose to get ready

[182.035] ...secure = no

[182.050] Flashing GPT...

[182.050] Flashing partition:0 with gpt_main0.bin

[182.050] Initializing storage

[182.050] Waiting for firehose to get ready

[243.031] Configuring device...

[243.031] Waiting for firehose to get ready

[304.012] Waiting for firehose to get ready

[364.992] Waiting for firehose to get ready

[426.082] Waiting for firehose to get ready

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

[487.062] Check qboot_log.txt for more details

[487.062] Total time: 487.062s

[487.530]

[487.530] qboot version 3.40

[487.530]

[487.530] DEVICE {

[487.530] name = "\\.\COM14",

[487.530] flags = "0x64",

[487.530] addr = "0x28FE6C",

[487.530] sahara.current_mode = "0",

[487.530] api.buffer = "0x1F70020",

[487.530] cpu.serial = "14518310",

[487.530] cpu.id = "2418",

[487.530] cpu.sv_sbl = "0",

[487.530] cpu.name = "MSM8952",

[487.530] storage.type = "eMMC",

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

[487.530] module.firehose = "0x610910",

[487.530] cpu.ver = "0",

[487.530] cpu.vername = "unknown",

[487.530] api.bnr = "0x65E620",

[487.530] }

[487.530]

[487.530]

[487.530] Backup & Restore {

[487.530] num_entries = 0,

[487.530] restoring = "false",

[487.530] backup_error = "not started",

[487.530] restore_error = "not started",

[487.530] }

[487.530]

I will keep doing this until I get a result I guess. Put phone on charger and then connect to computer.
[Moto G4 Plus Questions & Answers] MotoG4PlusQ:
Sahara Error solved on my phone

So if you read my previous posts you will know that I had problems with this type of error below:

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

[ 0.001] Detecting device

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

[ 4.001] Check qboot_log.txt for more details

[ 4.001] Total time: 4.002s

[ 4.001]

[ 4.001] qboot version 3.40

[ 4.001]

[ 4.001] DEVICE {

[ 4.001] name = "\\.\COM14",

[ 4.001] flags = "0x64",

[ 4.001] addr = "0x28FE6C",

[ 4.001] api.bnr = "0x8E8EE0",

[ 4.001] }

[ 4.001]

[ 4.001]

[ 4.001] Backup & Restore {

[ 4.001] num_entries = 0,

[ 4.001] restoring = "false",

[ 4.001] backup_error = "not started",

[ 4.001] restore_error = "not started",

[ 4.001] }

[ 4.001]

Well Echo92 suggested there might be a problem with usb cable etc etc. So I decided to reduce the resistance in the cables by putting the phone and the usb cable in the freezer for about 1 minute or 60 seconds. It worked like a charm, it took less than 6 seconds to do the whole thing. And I used the latest blankflash we discussed previously,
[Moto G4 Plus Questions & Answers] Bi0w0lf:
G4 Plus Stock

Hi guys,

Maybe someonу can help me with this stuff?

Tried to install last update on XT1642 stock, which was

Started to play with recovery and boot and came to the black screen with blinking LED.

Some ideas, how to fix this stuff?

c:\Users\andry\Downloads\blankflash1\blankflash>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

[ 0.000] Opening device: \\.\COM9

[ 0.001] Detecting device

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

[ 0.006] ...cpu.sn = 43812192 (0x29c8560)

[ 0.006] Opening singleimage

[ 0.069] Loading package

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

[ 0.084] Loading programmer

[ 0.084] ...filename = programmer.mbn

[ 0.084] Sending programmer

[ 0.319] Handling things over to programmer

[ 0.320] Identifying CPU version

[ 0.325] Waiting for firehose to get ready

[ 60.419] Waiting for firehose to get ready

[122.003] ...MSM8952 unknown

[122.003] Determining target secure state

[122.009] Waiting for firehose to get ready

[183.046] ...secure = no

[183.069] Flashing GPT...

[183.069] Flashing partition:0 with gpt_main0.bin

[183.069] Initializing storage

[183.075] Waiting for firehose to get ready

[243.220] Configuring device...

[243.225] Waiting for firehose to get ready

[303.330] Waiting for firehose to get ready

[363.523] Waiting for firehose to get ready

[423.676] Waiting for firehose to get ready

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

[483.808] Check qboot_log.txt for more details

[483.808] Total time: 483.819s

FAILED: qb_flash_singleimage()->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
[Moto G4 Plus Questions & Answers] xToRMyy:
I don't know about others, but for me the latest blankflash worked (2 times in like a million tries). I just connected the phone to PC using USB, pressed the power + volume down button and simultaneously opened the blankflash file multiple times. Repeat this until one of them eventually works. It requires a lot of patience for sure.
[Moto G4 Plus Questions & Answers] sanrajbhar:
Please any of you give me link for blankflash for Moto g3 XT1550?
[Moto G4 Plus Questions & Answers] strongst:
Same answer: https://xdaforums.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016/post74055398
[Moto G4 Plus Questions & Answers] Bi0w0lf:
This worked great for my phone, after the first try.

https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

Just flashed it in 2 steps.
[Moto G4 Plus Questions & Answers] sanrajbhar:
Moto G3 XT1550

please give us blnakFlash for Moto g3 XT1550. My phone is dead not powering on since after updating Flashing some cwm recovery. my phone was having root and boot-loader unlocked with AOSP Rom Android N.

Please help .. I tried every possible key combination but no success. I believe It can show the life with Right BlankFlash. please help
[Moto G4 Plus Questions & Answers] strongst:
I already give you the answer https://xdaforums.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016/post74155536 please read it and don't spam here with your question again. It's wrong forum where you asked and nobody here has those files! Read my post please. Follow the forum rules. Thanks!
[Moto G4 Plus Questions & Answers] saurav8275:
error reading packet

i did as u can give but nothing happens plase bro do something for me plzz

it showing like it

C:\Users\xyz\Downloads\hardbricked\blankflash2>.\qboot.exe blank-flash

opening device: \\.\COM13

OKAY [ 0.000s]

greeting device for command mode

opening device: \\.\COM13

OKAY [ 0.005s]

greeting device for command mode

opening device: \\.\COM13

OKAY [ 0.006s]

greeting device for command mode

opening device: \\.\COM13

OKAY [ 0.007s]

greeting device for command mode

opening device: \\.\COM13

OKAY [ 0.000s]

greeting device for command mode

opening device: \\.\COM13

OKAY [ 0.002s]

greeting device for command mode

opening device: \\.\COM13

OKAY [ -0.000s]

greeting device for command mode

opening device: \\.\COM13

OKAY [ -0.000s]

greeting device for command mode

opening device: \\.\COM13

OKAY [ -0.000s]

greeting device for command mode

opening device: \\.\COM13

OKAY [ 0.000s]

greeting device for command mode

opening device: \\.\COM13

OKAY [ -0.000s]

greeting device for command mode

FAILED (blank-flash:greet-device:error reading packet)

C:\Users\xyz\Downloads\hardbricked\blankflash2>pause

Press any key to continue . . .
[Moto G4 Plus Questions & Answers] n_sameem:
Got device to Generic bootloader

Hi [MENTION=2949556]vijayjadhav_143[/MENTION],

I have reached till the point to boot my device(Moto G4 Plus-1643) into Generic bootloader. However, I noticed that the Serial number now displayed on the botloader is not the same as before. Is that something to worry about?

Also, while running the commands to flash gpt.bin and bootloader.img i get the following response on cmd:

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot reboot-bootloader

C:\Program Files\Minimal ADB and Fastboot>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.034s]
writing 'partition'...
(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

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

C:\Program Files\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.i
mg
(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.139s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.261s

C:\Program Files\Minimal ADB and Fastboot>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s

Is this because I'm using an older version of the stock img or is it due to something else I'm doing wrong?

Any help is highly appreciated.

Thanks,

n_sameem
[Moto G4 Plus Questions & Answers] echo92:
Which blankflash have you used, and which stock ROM are you attempting to flash to repair your device?

I'm concerned the blankflash may have flashed the wrong instructions to your device. I'm wondering if the newest blankflash we have, or the latest stock ROM (which for XT1643 appears to be the September 2017 stock ROM) might help: https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
[Moto G4 Plus Questions & Answers] n_sameem:
I got my device working again!

The blankflash was installed successfully. So I think nothing was wrong there.

The problem was with the stock ROM I was trying to flash. Before the hard brick I was on the build number NPJS25.93-14.8 and I tried to flash the NPJS25.93-14 build which is an older version.

Eventually I downloaded the latest ROM with build number NPJS25.93-14.10 and it worked fine. The Serial Number also has reverted to the original one!

Thanks,

n_sameem
[Moto G4 Plus Questions & Answers] echo92:
Glad to hear you got your device working.

Might be worth deleting that NPJ25.93-14 stock ROM though, as you'd likely hard brick again if you attempt to flash that and then update with OTA updates. Generally, it's safer to flash the same or newer stock firmware than what is on your device. That means only September 2017 stock firmware (NPJS25.93-14-10) or newer from now on.
[Moto G4 Plus Questions & Answers] n_sameem:
Yep, I've deleted that.
[Moto G4 Plus Questions & Answers] ankitnandgavia:
sorry bro but this is not working in my device plz help me . ........Mod Edit: removed personal info....... is my contact and whatsapp number please do anything
[Moto G4 Plus Questions & Answers] echo92:
What device have you got and how did you hard brick?

Did you try the blankflash from this thread? https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

The blankflashes in the main post of this thread are quite old, and it'd be nice for the original poster to update the thread, but doesn't look like they've been around for a while...

Also, please do not post your personal contact number on forums like XDA - else you might get spam calls...
[Moto G4 Plus Questions & Answers] janmejay bhoi:
Help!!

hello,,,,

im shownig this type of issue...

plz suggest me>>>>>>

C:\Users\ayush\Desktop\blankflash1\blankflash>.\qboot.exe blank-flash

< waiting for device >

Motorola qboot utility version 3.40

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

[ 0.001] Detecting device

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

[ 0.003] ...cpu.sn = 7553914 (0x73437a)

[ 0.003] Opening singleimage

[ 0.003] Loading package

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

[ 0.006] Loading programmer

[ 0.007] ...filename = programmer.mbn

[ 0.007] Sending programmer

[ 0.234] Handling things over to programmer

[ 0.234] Identifying CPU version

[ 0.236] Waiting for firehose to get ready

[ 56.529] ReadFile() failed, GetLastError()=0

[ 56.530] ReadFile() failed, GetLastError()=0

[ 60.536] Waiting for firehose to get ready

[ 63.537] WriteFile() failed, GetLastError()=0

[ 65.660] ReadFile() failed, GetLastError()=0

[ 65.661] ReadFile() failed, GetLastError()=0

[ 75.170] ReadFile() failed, GetLastError()=0

[ 75.171] ReadFile() failed, GetLastError()=0

[ 84.301] ReadFile() failed, GetLastError()=0

[ 84.302] ReadFile() failed, GetLastError()=0

[ 93.811] ReadFile() failed, GetLastError()=0

[ 93.812] ReadFile() failed, GetLastError()=0

[102.944] ReadFile() failed, GetLastError()=0

[102.944] ReadFile() failed, GetLastError()=0

[121.586] ReadFile() failed, GetLastError()=0

[121.587] ReadFile() failed, GetLastError()=0

[122.587] ...MSM8952 unknown

[122.587] Determining target secure state

[122.589] Waiting for firehose to get ready

[131.095] ReadFile() failed, GetLastError()=0

[131.096] ReadFile() failed, GetLastError()=0

[158.869] ReadFile() failed, GetLastError()=0

[158.869] ReadFile() failed, GetLastError()=0

[168.379] ReadFile() failed, GetLastError()=0

[168.380] ReadFile() failed, GetLastError()=0

[177.238] ReadFile() failed, GetLastError()=0

[177.239] ReadFile() failed, GetLastError()=0

[177.510] ReadFile() failed, GetLastError()=0

[177.511] ReadFile() failed, GetLastError()=0

[183.517] ...secure = no

[183.526] Flashing GPT...

[183.526] Flashing partition:0 with gpt_main0.bin

[183.527] Initializing storage

[183.531] Waiting for firehose to get ready

[187.022] ReadFile() failed, GetLastError()=0

[187.022] ReadFile() failed, GetLastError()=0

[243.873] Configuring device...

[243.875] Waiting for firehose to get ready

[303.949] Waiting for firehose to get ready

[306.951] WriteFile() failed, GetLastError()=0

[364.028] Waiting for firehose to get ready

[367.029] WriteFile() failed, GetLastError()=0

[424.108] Waiting for firehose to get ready

[427.108] WriteFile() failed, GetLastError()=0
[Moto G4 Plus Questions & Answers] Outfield303:
This thread is no longer working, all the files are old