yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] erica butson:
1. Yes, I miss typed few times. :P

3. When the flashing is completed. I clicked on start the device is just stucked with white led light blinking for like 30 minutes. When i remove the usb connected to the system. The phone turns off it doesn't not turn on back untill i manually boot it into fastboot.

When the phone is booted to fastboot i used volume keys to select recovery mode but it's just stucked.

Here is the fastboot getvar all

C:\Users\jay\Downloads\Compressed\ADB+and+Fastboot\ADB and Fastboot>fastboot devices

ZY2238L75Q fastboot

C:\Users\jay\Downloads\Compressed\ADB+and+Fastboot\ADB and Fastboot>fastboot getvar all

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(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: 4

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007

(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B

(bootloader) cpu: MSM8952

(bootloader) serialno: ZY2238L75Q

(bootloader) cid: 0x0032

(bootloader) channelid: 0xc0

(bootloader) uid: 9CEB7F0000000000000000000000

(bootloader) securestate: flashing_unlocked

(bootloader) iswarrantyvoid: yes

(bootloader) max-download-size: 536870912

(bootloader) reason: Last time flashing failed

(bootloader) imei: 358187070533255

(bootloader) meid:

(bootloader) date: 06-02-2016

(bootloader) sku: XT1643

(bootloader) battid: SNN5970A

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time: "Thu Apr 21 1:40:54 UTC 2016"

(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:6.0.1/M

(bootloader) ro.build.fingerprint[1]: PJ24.139-63/64:user/release-keys

(bootloader) ro.build.version.full[0]: Blur_Version.24.31.64.athene.reta

(bootloader) ro.build.version.full[1]: il.en.US

(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0

(bootloader) version-baseband[0]: M8952_70009.08.03.48R ATHENE_INDIA_DSD

(bootloader) version-baseband[1]: S_CUST

(bootloader) kernel.version[0]: Linux version 3.10.84-g061c37c (hudsoncm

(bootloader) kernel.version[1]: [MENTION=387459]ilc[/MENTION]lbld87) (gcc version 4.9.x-google 20

(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM

(bootloader) kernel.version[3]: PT Thu Aug 4 19:33:05 CDT 2016

(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343

(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead

(bootloader) tz.git: git=69dd24b-dirty

(bootloader) hyp.git: git=69dd24b-dirty

(bootloader) keymaster.git: git=69dd24b-dirty

(bootloader) cmnlib.git: git=69dd24b-dirty

(bootloader) aboot.git: git=MBM-NG-VB1.06-0-g0edfb0d

(bootloader) qe: qe 0/0

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

(bootloader) ro.carrier: retin

all: listed above

finished. total time: 0.339s
[Moto G4 Plus Guides, News, & Discussion] echo92:
Ah, the getvar all info indicates the flash did not work at all.

1)Bootloader still at version B1:06 (June/Sept 2017). If you'd flashed the Dec 2017 stock bootloader, it'd be at B1:07.

2)Bootloader reports that you're booting into the bootloader because of a failed flash.

3)Your system and baseband are still on Marshmallow.

If you can, try a different computer to flash with, ensure you're using a high quality USB cable (preferably the original Motorola cable), and try flashing again. Try flashing with the September 2017 stock ROM. I guess you could try flashing with the Marshmallow stock ROM but do not take OTA updates whatsoever. https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 As with changing ROMs, ensure you delete the old stock ROM before replacing the old ROM with the new stock ROM, and verify all the files have copied successfully.

If none of those work, you may have to consider submitting the device for an expensive service repair (likely motherboard replacement) or put the money towards a new device.
[Moto G4 Plus Guides, News, & Discussion] erica butson:
Thank you so much for guiding me to pin point the exact problem. I will try to flash with good USB wire. I have already downloaded the stock rom updated signed t3460695 and flashed, didn't work too. I don't want to give up. I will keep trying and post if i get something new.

Meanwhile bitcoin has gone down.

Thanks.
[Moto G4 Plus Guides, News, & Discussion] vaas kr:
Moto G4 plus XT1643 model.

My bro tried to install an OTA on starting of Dec-2017 then it lead to bricked condition..

I ran this blankflash, then i got this MSM8952 unknown error, I cant get over this.

How to solve this?

I tried ur's

""Apparently the fix to get into fastboot was to press & hold the power & volume down key & then let go after you get the Waiting for firehose to get ready command which then you must release."" still im getting the same.

**** Log buffer [000001] 2018-01-18_20:44:30 ****

[ 0.000] Opening device: \\.\COM12

[ 0.004] Detecting device

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

[ 0.007] ...cpu.sn = 17824113 (0x10ff971)

[ 0.007] Opening singleimage

[ 0.008] Loading package

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

[ 0.023] Loading programmer

[ 0.025] ...filename = programmer.mbn

[ 0.025] Sending programmer

[ 0.258] Handling things over to programmer

[ 0.258] Identifying CPU version

[ 0.265] Waiting for firehose to get ready

[ 60.607] Waiting for firehose to get ready

[120.691] ...MSM8952 unknown

[120.691] Determining target secure state

[120.698] Waiting for firehose to get ready

[180.850] ...secure = no

[180.886] Flashing GPT...

[180.886] Flashing partition:0 with gpt_main0.bin

[180.887] Initializing storage

[180.897] Waiting for firehose to get ready

[240.934] Configuring device...

[240.942] Waiting for firehose to get ready

[301.090] Waiting for firehose to get ready

[361.166] Waiting for firehose to get ready

[421.234] Waiting for firehose to get ready

[481.357] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->get_fh()->no response

[481.358] Check qboot_log.txt for more details

[481.359] Total time: 481.362s

[481.360]

[481.360] qboot version 3.40

[481.360]

[481.360] DEVICE {

[481.360] name = "\\.\COM12",

[481.360] flags = "0x64",

[481.360] addr = "0x28FE6C",

[481.360] sahara.current_mode = "0",

[481.360] api.buffer = "0x2100020",

[481.360] cpu.serial = "17824113",

[481.360] cpu.id = "2418",

[481.360] cpu.sv_sbl = "0",

[481.360] cpu.name = "MSM8952",

[481.360] storage.type = "eMMC",

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

[481.360] module.firehose = "0x2061770",

[481.360] cpu.ver = "0",

[481.361] cpu.vername = "unknown",

[481.361] api.bnr = "0x2069680",

[481.361] }

[481.361]

[481.361]

[481.361] Backup & Restore {

[481.361] num_entries = 0,

[481.361] restoring = "false",

[481.361] backup_error = "not started",

[481.361] restore_error = "not started",

[481.361] }

[481.361]

How to solve this??

Is it is recoverable??
[Moto G4 Plus Guides, News, & Discussion] echo92:
What firmware was your brother's device on before the hard brick? You mentioned December 2017 (B1:07 bootloader, NPJS25.93-14-13)? What OTA did you try to flash?

Try running the blankflash a few times. Check that you're connected via USB using the original USB cable or a high quality USB cable.
[Moto G4 Plus Guides, News, & Discussion] vaas kr:
That firmware details he hasn't noted that.. I asked him android version too.. but hes not sure on which version he was...

He usually don't do the OTA update as he knew it ll create problem... however accidentally install ota button was pressed from notification ... this was happened at starting of dec 2017..

he don't have any other details... then led flashing problem started...

usb cable used is Moto C plus usb cable ... is it is ok?

I have tried 10 times.. but same output..

today noon also by surprise, charging indication screen also showed, as well as bootloader too came.. I rebooted mobile once, and then again, only led flashes coming no charging indication now showin...

suppose if mobile was on marshmallow or lollipop then wat wil be solution ?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Right, not a problem if he can't remember what firmware/what version.

OTA updates are usually only a problem if you've downgraded your stock device firmware at any point in the past.

By the bootloader showing, you mean the bootloader screen, with the green Android and the options to start or boot to recovery? Did you see what bootloader version (for example B1:03) the device had?

If so, that could mean a partial corruption of the bootloader or a possible hardware failure (e.g. flash memory failure). Does the device get detected if you connect via USB when it does boot properly? The Moto C cable should be okay.

Our devices do not have lollipop, only marshmallow (6.0.1) or Nougat (7.0). The latest build is the Nougat 7.0, Dec 2017 security patch NPJS25.93-14-13 https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 try flashing that if you can reliably get the device to boot.

If the device keeps blinking, then you could try holding the power button down for 1-2 minutes, which should force shutdown the device. Try powering on after that.
[Moto G4 Plus Guides, News, & Discussion] vaas kr:
s screen had the options for scrolling

reboot, recovery, power off, like that...

I didnt notice tat number..

I failed to take photo of that bootloader screen as I thought it was ok as bootloader came, and planned for flashing stock rom..

pressed power off and then tried again.. thats it ... now only led flashing., nothing more than tat...

then after tried blankflash., stuck in msm8952 unknown..

:rolleyes:

wen I connect to laptop it detectedb as qualcomm loader 9008 COM12 in devicemanager... with no exclamation mark... means driver installed ok...

if its a partial corruption means can it be solve?

if its a hardware error means it can't be solved without spending large amount...right ?

---------- Post added at 06:35 PM ---------- Previous post was at 06:30 PM ----------

user icesmash too got the same error as I hav got... he got it resolved..

so I have hope that mine also can get work.. :rolleyes::rolleyes:
[Moto G4 Plus Guides, News, & Discussion] echo92:
If it's in the Qualcomm loader mode 9008, that suggests the bootloader had failed on that boot, so the device went into an emergency mode.

As you've mentioned the device can unreliably boot, it suggests the bootloader could be repaired. However, if the blankflash isn't working, it could be too old (you're using the blankflash at the start of the thread?), or there's more serious corruption in the flash memory. Without knowing what happened in detail, it's difficult to know.

If it is a hardware fault, then if you've got warranty, it should be covered. If not, the likely fix would be a motherboard repair, which seems to cost about 7000-8000 rupees or your regional equivalent.

Just asking, the screen is still the original screen, it's not been replaced?

I'd try to see if you can get the device booting again and if so, flash the latest stock ROM, but if not, then you may have to send it for service or put the money toward a new device.
[Moto G4 Plus Guides, News, & Discussion] vaas kr:
s I'm using blankflash at start of the thread.. is it is old ?
[Moto G4 Plus Guides, News, & Discussion] echo92:
No, that's the latest blankflash we managed to get leaked from Motorola. As they're cryptographically signed by Motorola, we are unlikely to make them ourselves. It should work on Moto G4/Plus devices patched up to at least the September 2017 stock security patch.

If the CPU is still not being recognised (e.g. MSM8952 unknown instead of MSM8952 1.1) and the firehose is being waited on (so after the programmer is sent, it's waiting for a reply from your device to permit flashing), then that suggests the blankflash didn't work.

However, it appears that multiple tries are needed to get the device to connect. As you've already tried multiple times, then I can only suggest waiting for another newer blankflash (if one gets leaked) or the options I mentioned above.
[Moto G4 Plus Guides, News, & Discussion] vaas kr:
will check few more times by doing all combinations like reinstalling qualcomm, moto drivers.. changing pc/laptop... :confused:

btw I think the mobile might be patched with latest update dec 17 ... as it bricked on doing ota update on dec2017.. :confused:
[Moto G4 Plus Guides, News, & Discussion] echo92:
It could have bricked on the Dec 2017 OTA if the device ran out of power whilst updating. Usually updating with OTAs aren't an issue, only if there was a stock firmware downgrade involved as well, or if the device ran out of power mid flash.

What's perplexing is that you can still get to the bootloader, a hard brick would not normally let you do that.

If your brother's device is patched to the December 2017 update, that might explain the blankflash not working, or it's not a normal hard brick. I wonder if the battery might be at fault... Does the device boot if connected to power?

In the bootloader, December 2017 bootloader will be B1:07. Sept and June 2017 stock bootloader will be B1:06.

June, Sept and December 2017 basebands end in .62.01R.

If you can boot the device to the bootloader and get a getvar info, that'd be useful.

1) boot the device to the bootloader screen.

2) connect to your computer.

3) in the ADB terminal, type 'fastboot getvar all' without quotes. Press enter.

4) copy paste the output here in a post. You may wish to edit out the IMEI.
[Moto G4 Plus Guides, News, & Discussion] vaas kr:
battery is healthy only...

and device doesn't boot to bootloader/boots if connected to power... just led blinks..

is there any chance that i can get any latest blank flash for dec 17 update.. ?

or am I having any issue with Qualcomm drivers ?:rolleyes:

---------- Post added at 03:14 PM ---------- Previous post was at 02:48 PM ----------

or..

is there anyway by using QFIL/QPST tools to bring back the mobile from my condition? :rolleyes:
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, you could look into the Qualcomm drivers.

We don't have a newer blankflash than the one in this thread, which should work on B1:06 and earlier bootloaders. These blankflashes are not made by XDA members - they are leaked from Motorola, either through contacts at the engineering teams or a friendly face. As such, they are rare commodities which we're lucky to have and Motorola, in my opinion, is unlikely to release them officially - they'd refer you to the service centre.

Blankflashes contain files that are cryptographically signed by Motorola, presumably to ensure that what you flash onto your device is genuine and maintains the secure bootloader environment. For QFIL/QPST, you'd need similar files to load into the programs, else the device would reject any old and/or unsigned files as unsafe to flash. I am not aware of any new MSM8952 (Snapdragon 617) Motorola specific files to load into QFIL/QPST.

You could try making a loader image, effectively a partition level copy of a working device, then hope the bootloader falls back to that image and boots. There's an example here on the Moto X https://xdaforums.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860

Alternatively, wait for a newer blankflash to be leaked (maybe when Oreo is released, a stock factory firmware with a newer blankflash is available).
[Moto G4 Plus Guides, News, & Discussion] Icesmash:
The main issue is that when you got into bootloader mode you should have known the device was broken & needed that you needed to flash the official firmware ASAP. You powered off the device instead which resulted in you not being able to get back into the bootloader interface. When I first got into the bootloader I took no chances & Flashed the official firmware that echo92 kindly provided me. (I missed school that day but it was worth it since it's my primary device) :laugh:

Also in my case I had downgraded my bootloader to the December 2016 edition (accidentally flashed the old december firmware) however if your bootloader is updated to the latest version & you cannot load into the bootloader then you must wait for the next blankflash. Your MAIN goal should be to get back into bootloader from there recovery is possible.

Encouraging Story:

I just recently fixed a Moto E XT1528 that had been soft bricked by me by flashing a firmware for a completely different device in an attempt to root it. With that device as soon as you plugged in it would load into the bootloader immediately, the hard part was that it was/is bootloader locked. So I waited 2 years to get an official software rom or "firmware" leaked. Since its bricked due to the latest update you may only have to wait a few months or none at all if you can get back into bootloader & flash the latest firmware.
[Moto G4 Plus Guides, News, & Discussion] vaas kr:
the device was kept idle by my bro for around a month as he didnt get device to boot in bootloader...

then three days bfr, I tried and it went into bootloader surprisingly... I got a false believing tat mobile will boot into bootloader even for next time... so rebooted , but went dead again..

if I had known previously I would hav flashed latest stock rom right away tat time..

is there any time , when its going to be released ?
[Moto G4 Plus Guides, News, & Discussion] Icesmash:
It will take a long time to get the latest blankflash expect a wait of 1-3 Months minimum.

However Keep trying to load back into bootloader it took me about 12 tries to get into bootloader using the blankflash & doing the special steps to actually get into the bootloader.

My advice is keep trying to get into the bootloader you might get lucky but this time don't take it for granted.

Just Keep trying the blankflash at least 15 times & unplugging the usb & replugging it back in. Also make sure you have the special driver installed to make sure you have the qualcomm drivers from this post.

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

Hope this helps! ;)
[Moto G4 Plus Guides, News, & Discussion] Mikxx:
please help me, mo pc or laptop dont recognise my phone i tried to flash twrp inside another twrp, 64x -> 84x did so before, but this time i think something went wrong when i try to go in recovery it says:

------

start up failed:

your device didn't start up successfully.

use the software repair assistant on computer

to repair your device.

connent your device to your computer to get

the software repair assistant.

ap fastboot flash mode (secure)

fastboot reason: volume down key pressed

error: failed to pass validaton, backup to fastboot

boot up failed

-----

i dont have the repair tool, and cant find it and no devices detect my phone whatsoever,

please help
[Moto G4 Plus Guides, News, & Discussion] Ayan Uchiha Choudhury:
[MENTION=7843165]siddhesh9146[/MENTION] thanks for this guide really helped me a lot. I had flashed the September security update but when I opened the phone it was showing December update with another update. I thought there was a new update for the phone and so went on with it and hard bricked my device. No bootloader, no TWRP , nothing. Only continuous glowing of the led when connected to computer. This guide helped me save a few hundred rupees from Lenovo service center!!
[Moto G4 Plus Guides, News, & Discussion] Abrarandroid:
my phone is not detecting any Sims.

Friend I successfully unbricked my device but my phone is not reading any Sims in both sim trays.. What should I do.. Pls help
[Moto G4 Plus Guides, News, & Discussion] echo92:
What device do you have and which firmware did you flash?

Do you have IMEI and or SV codes present under settings > about phone > status >sim status or IMEI information?

Are your SIMs working in another device?
[Moto G4 Plus Guides, News, & Discussion] Abrarandroid:
'' HOPE'' ?

No bro in Status its showing unavailable and not available for all things except serial number and uptime

---------- Post added at 07:13 AM ---------- Previous post was at 07:12 AM ----------

I think I flashed some wrong things. Now imei and others things are not showing

---------- Post added at 07:15 AM ---------- Previous post was at 07:13 AM ----------

And tried many Sims but none are working.. The problem is in phone
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, what is your baseband showing, is it showing DFLT_FSG at the end or something similar?

Can you remember what you've flashed?
[Moto G4 Plus Guides, News, & Discussion] Abrarandroid:
Solved

Thank you bro.. I flashed the right firmware this time and it solved.
[Moto G4 Plus Guides, News, & Discussion] joaopaulo_:
Which firmware you used? My xt1626 have a same problem, but flash firmware doesn't solve. :/
[Moto G4 Plus Guides, News, & Discussion] Abrarandroid:
I flashed this

https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
[Moto G4 Plus Guides, News, & Discussion] joaopaulo_:
Not solved. I need a specific firmware or another method. :/
[Moto G4 Plus Guides, News, & Discussion] echo92:
What isn't solved, are you not able to boot or are you having trouble with your SIM cards?
[Moto G4 Plus Guides, News, & Discussion] joaopaulo_:
https://imgur.com/a/54H5P

Only SIM 1 is recognized. But "no service".

SIM 2 are off. Digital TV app too.

I only use this rom: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

This time occured this error.

I flashed modem and fsg but not solve this.

There's no specific firmware for xt1626 (Brazil rom)
[Moto G4 Plus Guides, News, & Discussion] Sky Sonu:
after flashing blank flash then dummy bootloader has installed but when flashing stock rom it shows error failure in cmd please help me out﻿

---------- Post added at 11:16 AM ---------- Previous post was at 11:10 AM ----------

same problem with me also:(:(:(
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
Make sure you're flashing the correct GPT and Bootloader. If you're flashing older files then you'll probably get that error.

Download the Latest GPT and Bootloader files from above Thanks to [MENTION=7970352]echo92[/MENTION] https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80

Give it a try and see what you come up with...

Good luck!
[Moto G4 Plus Guides, News, & Discussion] echo92:
If the Dec 2017 GPT and bootloader doesn't work, please post what errors you're getting with the stock ROM flash and which stock ROM you're using and what commands you're using to flash the software.
[Moto G4 Plus Guides, News, & Discussion] satyamspot:
Moto G4 plus Blank flash error --device not detecting

I was upgrading to Nougat from Marshmallow, because of low battery phone switched off while updating. Now phone LED is blinking when I am charging and I have almost done all the things which are to be done. The only response I got is the LED light stop blinking and nothing happens then. Help me please, I have already charged it for 2-3 hours but still, it is not turning on.

I tried for blank flash but it showing the error msg. [Error opening device].

[ 0.000] Opening device: \\.\COM3

[ 0.000] ERROR: device_open()->error opening device

[ 0.000] Check qboot_log.txt for more details

[ 0.000] Total time: 0.001s

[ 0.000]