HELP Full Brick for updating with the OTA option to the oreo version 8.1 of nougat

hagensz

New member
Feb 25, 2019
4
0
0
Someone has some solution for a Moto G4 PLUS was upgraded via OTA to android oreo 8.1 and it stayed fullbrick no longer enters or fastboot mode only flashes a winged light sensor footprint, look here in XDA, google and YouTube but I only found one solution that is the "BLANKFLASH" but only works for those who did update via OTA from Android 6.0 MM to Nougat, but for OREO there is nothing, I do not know if you can use another BLANKFLASH from another model like a Moto Z for example to be able enter fastboot mode :crying::crying:
 

Shreyas17

Senior Member
Sep 25, 2017
88
22
8
22
Someone has some solution for a Moto G4 PLUS was upgraded via OTA to android oreo 8.1 and it stayed fullbrick no longer enters or fastboot mode only flashes a winged light sensor footprint, look here in XDA, google and YouTube but I only found one solution that is the "BLANKFLASH" but only works for those who did update via OTA from Android 6.0 MM to Nougat, but for OREO there is nothing, I do not know if you can use another BLANKFLASH from another model like a Moto Z for example to be able enter fastboot mode :crying::crying:
You will need to wait till latest blankflash files are released orelse try various blankflash available
try this:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
 
  • Like
Reactions: ebol94

hagensz

New member
Feb 25, 2019
4
0
0

adnpagani

Member
Jan 23, 2013
6
0
0
You can try the blankflash files provided in the link to unbrick your device
https://forum.xda-developers.com/mo...k-rom-npjs25-93-14-4-march-1-t3608138/page102
That blankflash dont work on this case. My phone brick on the nougat to oreo uopdate and I was trying to unbrick for almost 10 hours!
I already try a lot of diferent "blankflash" files but no one seems work.

The lastest blankflash only shows a message "[ 0.328] Waiting for firehose to get ready"

**** Log buffer [000001] 2019-04-28_22:47:34 ****

[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 2418 (0x972)
[ 0.000] ...cpu.sn = 15720246 (0xefdf36)
[ 0.000] Opening singleimage
[ 0.063] Loading package
[ 0.063] ...filename = singleimage.pkg.xml
[ 0.063] Loading programmer
[ 0.063] ...filename = programmer.mbn
[ 0.063] Sending programmer
[ 0.313] Handling things over to programmer
[ 0.313] Identifying CPU version
[ 0.328] Waiting for firehose to get ready
[ 60.845] Waiting for firehose to get ready
[121.424] ...MSM8952 unknown
[121.424] Determining target secure state
[121.424] Waiting for firehose to get ready
[181.929] ...secure = no
[181.967] Flashing GPT...
[181.968] Flashing partition:0 with gpt_main0.bin
[181.969] Initializing storage
[181.973] Waiting for firehose to get ready
[242.508] Configuring device...
[242.508] Waiting for firehose to get ready
[303.039] Waiting for firehose to get ready
[363.394] Waiting for firehose to get ready
[423.688] Waiting for firehose to get ready
[484.234] 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
[484.234] Check qboot_log.txt for more details
[484.234] Total time: 484.234s
[484.234]
[484.234] qboot version 3.40
[484.234]
[484.234] DEVICE {
[484.234] name = "\\.\COM3",
[484.234] flags = "0x64",
[484.234] addr = "0x61FE4C",
[484.234] sahara.current_mode = "0",
[484.234] api.buffer = "0x12E3020",
[484.234] cpu.serial = "15720246",
[484.234] cpu.id = "2418",
[484.234] cpu.sv_sbl = "0",
[484.234] cpu.name = "MSM8952",
[484.234] storage.type = "eMMC",
[484.234] sahara.programmer = "programmer.mbn",
[484.234] module.firehose = "0xF98FB8",
[484.234] cpu.ver = "0",
[484.234] cpu.vername = "unknown",
[484.234] api.bnr = "0xE88C18",
[484.234] }
[484.234]
[484.234]
[484.234] Backup & Restore {
[484.234] num_entries = 0,
[484.234] restoring = "false",
[484.234] backup_error = "not started",
[484.234] restore_error = "not started",
[484.234] }
[484.234]
 
Last edited:

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
That blankflash looks to be the same OPJ28.72 blankflash as linked earlier in the thread. Unfortunately, that's the latest blankflash we've got leaked to us and if that does not work, then the other options are to consult a service centre (possibly for an expensive motherboard replacement) or to purchase a new device.
 

adnpagani

Member
Jan 23, 2013
6
0
0

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
Ty for the reply, but this version I already tested and it did not work, I think to repair in this case only if it leaks a new blankflash
I am not hopeful for a new blankflash, given that Oreo update was likely the last update for our device.

If you really need a working device now, pay for a motherboard repair (or use insurance if you have it) or buy a new device. I'm sorry, there's currently no other options.
 

adnpagani

Member
Jan 23, 2013
6
0
0
I am not hopeful for a new blankflash, given that Oreo update was likely the last update for our device.

If you really need a working device now, pay for a motherboard repair (or use insurance if you have it) or buy a new device. I'm sorry, there's currently no other options.
The time for xiaomi has come.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone