• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[NEED] Moto G4 Play XT16XX Blank Flash [HARD BRICK]

Search This thread

jdgrath17

Member
Mar 13, 2018
5
0
Hello,

I flashed nougat rom then tried to revert back to MM rom and lost the IMEI and now the bootloader is updated to a new version with january 2018 security patch. So now I cant perform downgrade as it doesn't fix the IMEI.
I tried blank flash and many other ways possible but either the device is not detected and even if I manage to install the qualcomm HS USB drivers still it install the driver efficiently and RSD Lite doesnt detect anything in anyway.
I did the twrp backup but its of no use as restoring doesnt fix the IMEI and still shows 0. So I was wondering if I can edit the boot.img and other files to revert to stock marshmallow by updating bootloader info and files. Please help if its possible. Somehow it seems possible through QPST but the driver configuration plus I dont have the qcn backup. And I dont know much about QPST for this variant.
So kindly help
This is my 2nd post because developers seems like they arent interested until its a 40k device.
Well if you cant fix this one then whats the point of being a developer.
 

Mati Maglia

New member
Apr 2, 2017
3
0

Hi, i have the moto g4 play xt1607 and it is in full brick.
I tried your file but I get the following error:

**** Log buffer [000001] 2021-12-03_19:13:15 ****

[ 0.000] Opening device: \\.\COM9
[ 0.001] Detecting device
[ 0.003] ...cpu.id = 1797 (0x705)
[ 0.003] ...cpu.sn = 475720655 (0x1c5aebcf)
[ 0.003] Opening singleimage
[ 0.054] Loading package
[ 0.056] ...filename = singleimage.pkg.xml
[ 0.057] Loading programmer
[ 0.058] ...filename = programmer.mbn
[ 0.058] Sending programmer
[ 0.059] ERROR: sahara_download()->Invalid ELF header received
[ 0.059] Check qboot_log.txt for more details
[ 0.059] Total time: 0.060s
[ 0.059]
[ 0.059] qboot version 3.40
[ 0.059]
[ 0.059] DEVICE {
[ 0.059] name = "\\.\COM9",
[ 0.059] flags = "0x64",
[ 0.059] addr = "0x61FE4C",
[ 0.059] sahara.current_mode = "0",
[ 0.059] api.buffer = "0xFD7020",
[ 0.059] cpu.serial = "475720655",
[ 0.059] cpu.id = "1797",
[ 0.059] cpu.sv_sbl = "0",
[ 0.059] cpu.name = "MSM8916",
[ 0.059] storage.type = "eMMC",
[ 0.059] sahara.programmer = "programmer.mbn",
[ 0.059] api.bnr = "0x6E3FF0",


could you help me?
Thanks and sorry for my english
 

Trey n

Senior Member
Nov 12, 2014
359
89
23
Motorola Droid RAZR M
Samsung Galaxy S5
Hi, i have the moto g4 play xt1607 and it is in full brick.
I tried your file but I get the following error:

**** Log buffer [000001] 2021-12-03_19:13:15 ****

[ 0.000] Opening device: \\.\COM9
[ 0.001] Detecting device
[ 0.003] ...cpu.id = 1797 (0x705)
[ 0.003] ...cpu.sn = 475720655 (0x1c5aebcf)
[ 0.003] Opening singleimage
[ 0.054] Loading package
[ 0.056] ...filename = singleimage.pkg.xml
[ 0.057] Loading programmer
[ 0.058] ...filename = programmer.mbn
[ 0.058] Sending programmer
[ 0.059] ERROR: sahara_download()->Invalid ELF header received
[ 0.059] Check qboot_log.txt for more details
[ 0.059] Total time: 0.060s
[ 0.059]
[ 0.059] qboot version 3.40
[ 0.059]
[ 0.059] DEVICE {
[ 0.059] name = "\\.\COM9",
[ 0.059] flags = "0x64",
[ 0.059] addr = "0x61FE4C",
[ 0.059] sahara.current_mode = "0",
[ 0.059] api.buffer = "0xFD7020",
[ 0.059] cpu.serial = "475720655",
[ 0.059] cpu.id = "1797",
[ 0.059] cpu.sv_sbl = "0",
[ 0.059] cpu.name = "MSM8916",
[ 0.059] storage.type = "eMMC",
[ 0.059] sahara.programmer = "programmer.mbn",
[ 0.059] api.bnr = "0x6E3FF0",


could you help me?
Thanks and sorry for my english
I just got done reading the g4 plus unbrick guide and they say you have to try 10 to 20 times if it falls the first time, make sure you use a great working USB cable
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    please be aware that the partitions the op is requesting contain personal, sensitive data, like your google password, and imei, which can not be deleted with a standard recovery wipe. It is not recommended anyone who does no understand what information any partition backup contains, refrain from responding, for your own protection. with the collective partitions the op is requesting, they can have a 100% duplicate of your device, including your personal information.