Related
Just got a XT1789-01 from a friend whos daughters phone just abruptly stopped working. No signs of life, except when plugged in to a computer I see the QLoader 9008 driver load. I tried some blank flash that says to bring the booloader back but it did nothing but say Generic Error. The tool does seem to detect the phone though.
Any ideas? The girl that uses this phone is like 10 so I know its not been tampered with software wise to cause this.
Motorola devices are not my cup of tea when it comes to flashing.
Thanks!
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
At the bottom of the post is a link for qualcomm diag drivers, signed for windows.
Attached is the unbrick.zip, use the drivers mentioned above though. Basically unplug your phone and install the drivers, reboot pc and plug in, wait for the drivers to recognize and settle, then blankflash. Afterwards you'll be in a clean bootloader. Flash the latest firmware for your variant. This thread has instructions and links for flashing firmwares, just make sure it's for your variant. You can also try using the lmsa tool mentioned in post #275 to flash the firmware needed.
41rw4lk said:
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
At the bottom of the post is a link for qualcomm diag drivers, signed for windows.
Attached is the unbrick.zip, use the drivers mentioned above though. Basically unplug your phone and install the drivers, reboot pc and plug in, wait for the drivers to recognize and settle, then blankflash. Afterwards you'll be in a clean bootloader. Flash the latest firmware for your variant. This thread has instructions and links for flashing firmwares, just make sure it's for your variant. You can also try using the lmsa tool mentioned in post #275 to flash the firmware needed.
Click to expand...
Click to collapse
Thanks. But I still get "FAILED General error" on the blank flash.
C:\1>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.004] ...cpu.sn = 3695693525 (0xdc47ced5)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.007] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.016] ReadFile() failed, GetLastError()=0
[ 0.342] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.344] ERROR: sahara_download()->general error
[ 0.344] Check qboot_log.txt for more details
[ 0.345] Total time: 0.346s
FAILED: qb_flash_singleimage()->sahara_download()->general error
C:\1>pause
Press any key to continue . . .
hyelton said:
Thanks. But I still get "FAILED General error" on the blank flash.
C:\1>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.004] ...cpu.sn = 3695693525 (0xdc47ced5)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.007] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.016] ReadFile() failed, GetLastError()=0
[ 0.342] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.344] ERROR: sahara_download()->general error
[ 0.344] Check qboot_log.txt for more details
[ 0.345] Total time: 0.346s
FAILED: qb_flash_singleimage()->sahara_download()->general error
C:\1>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Try holding pwr+vol down, then execute the bat file
Same exact error
hyelton said:
Same exact error
Click to expand...
Click to collapse
I've only had to use that once and I didn't run into problems. Double check that the right driver is installed in your device manager, make sure you're running admin prompt (best from the folder so the path is all set). Try executing the command then plug in your phone. Make sure you're using a 2.0 usb port off the mobo and not a hub or 3+ port. Outside of those suggestions I can't help, I don't know the error correlation. I know some had issues getting to to go, but ultimately it was "things just clicked and worked this time" scenario.
The post where you got the drivers has links to unbricking guides, check those if needed.
41rw4lk said:
I've only had to use that once and I didn't run into problems. Double check that the right driver is installed in your device manager, make sure you're running admin prompt (best from the folder so the path is all set). Try executing the command then plug in your phone. Make sure you're using a 2.0 usb port off the mobo and not a hub or 3+ port. Outside of those suggestions I can't help, I don't know the error correlation. I know some had issues getting to to go, but ultimately it was "things just clicked and worked this time" scenario.
The post where you got the drivers has links to unbricking guides, check those if needed.
Click to expand...
Click to collapse
Yeah drivers are correct, laptop and desktop both usb 2.0 and 3.0 has been tried. Different usb cables, I’m assuming something has went wrong with this phone. As it’s never been tampered with. So I’ll give it a few more goes before giving up on it.
Sent from my iPhone using Tapatalk
which blank flash did you try N or O?
Same here, I think we need an updated blankflash
**** Log buffer [000001] 2019-03-14_20:10:40 ****
[ 0.000] Opening device: \\.\COM3
[ 0.004] Detecting device
[ 0.008] ...cpu.id = 94 (0x5e)
[ 0.008] ...cpu.sn = 4062057235 (0xf21e1313)
[ 0.009] Opening singleimage
[ 0.015] Loading package
[ 0.027] ...filename = pkg.xml
[ 0.037] Loading programmer
[ 0.040] ...filename = programmer.elf
[ 0.040] Sending programmer
[ 0.100] ReadFile() failed, GetLastError()=0
[ 0.370] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.454] ERROR: sahara_download()->general error
[ 0.457] Check qboot_log.txt for more details
[ 0.475] Total time: 0.489s
[ 0.485]
[ 0.485] qboot version 3.85
[ 0.485]
[ 0.485] DEVICE {
[ 0.485] name = "\\.\COM3",
[ 0.485] flags = "0x64",
[ 0.485] addr = "0x28FD64",
[ 0.485] sahara.current_mode = "0",
[ 0.485] api.buffer = "0x2525020",
[ 0.485] cpu.serial = "4062057235",
[ 0.485] cpu.id = "94",
[ 0.485] cpu.sv_sbl = "15",
[ 0.485] cpu.name = "MSM8998",
[ 0.485] storage.type = "UFS",
[ 0.485] sahara.programmer = "programmer.elf",
[ 0.485] api.bnr = "0x475FF8",
[ 0.485] }
[ 0.485]
[ 0.485]
[ 0.485] Backup & Restore {
[ 0.485] num_entries = 0,
[ 0.485] restoring = "false",
[ 0.485] backup_error = "not started",
[ 0.485] restore_error = "not started",
[ 0.485] }
[ 0.485]
Same problem here!
I think that I need some updated blankflash files. I have tried to found in 4PDA, but the link was removed, the file name was "blankflash_SPRINT_8.0.0_OCXS27.109-48-6.zip" or " blankflash_VZW_8.0.0_ODXS27.109-34-12_12.zip". I have a xt1789-05, dual sim, but I think these files can save me! Anyone have these files? Thanks.
i have this error, can you help me?
[ 0.000] Opening device: \\.\COM5
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
[ 0.001]
[ 0.001] qboot version 3.85
[ 0.001]
[ 0.001] DEVICE {
[ 0.001] name = "\\.\COM5",
[ 0.001] flags = "0x60",
[ 0.001] addr = "0x62FD54",
[ 0.001] api.bnr = "0x1D2D70",
[ 0.001] }
[ 0.001]
[ 0.001]
[ 0.001] Backup & Restore {
[ 0.001] num_entries = 0,
[ 0.001] restoring = "false",
[ 0.001] backup_error = "not started",
[ 0.001] restore_error = "not started",
[ 0.001] }
[ 0.001]
XxeAgLeAnGeLxX said:
i have this error, can you help me?
[ 0.000] Opening device: \\.\COM5
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
[ 0.001]
[ 0.001] qboot version 3.85
[ 0.001]
[ 0.001] DEVICE {
[ 0.001] name = "\\.\COM5",
[ 0.001] flags = "0x60",
[ 0.001] addr = "0x62FD54",
[ 0.001] api.bnr = "0x1D2D70",
[ 0.001] }
[ 0.001]
[ 0.001]
[ 0.001] Backup & Restore {
[ 0.001] num_entries = 0,
[ 0.001] restoring = "false",
[ 0.001] backup_error = "not started",
[ 0.001] restore_error = "not started",
[ 0.001] }
[ 0.001]
Click to expand...
Click to collapse
I was experiencing this exact same issue when running the blankflash. I ran it several times only to receive the same error over and over.
Did you put your device into EDL Mode or did it happen after a bad flash?
Do you know if your bootloader is still intact? Do you know how to exit EDL Mode to get back to the bootloader?
Here is what you do...
Since you are in EDL Mode trying to run the blankflash, get everything set up like you are about to run the blankflash again. Connect your device and verify it is connected in the Device Manager. Press and Hold Volume Down + Power and double-click the file to run the blankflash. Continue holding the Volume Down + Power while attempting to run the blankflash and if your bootloader is still intact this will take you back into the bootloader. It may take a few attempts to get back. Just keep holding the Volume Down + Power and double clicking the blankflash file until it takes you back to the bootloader.
Now, this is assuming that your bootloader is still intact. If it is and you can get back to the bootloader then you can run a flash-all for your device that matches the software you were running and get your device back to an operational state. Good luck.
pekenolucas said:
I think that I need some updated blankflash files. I have tried to found in 4PDA, but the link was removed, the file name was "blankflash_SPRINT_8.0.0_OCXS27.109-48-6.zip" or " blankflash_VZW_8.0.0_ODXS27.109-34-12_12.zip". I have a xt1789-05, dual sim, but I think these files can save me! Anyone have these files? Thanks.
Click to expand...
Click to collapse
Follow this guide it has worked for many. Make sure you read it all first, and make sure your phone is in edl mode. Your phone will have a blank screen but you'll see HS-USB QLoader 9008 in your device manager when connected to your pc.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Blank flash after reomal of battery works
hyelton said:
Just got a XT1789-01 from a friend whos daughters phone just abruptly stopped working. No signs of life, except when plugged in to a computer I see the QLoader 9008 driver load. I tried some blank flash that says to bring the booloader back but it did nothing but say Generic Error. The tool does seem to detect the phone though.
Any ideas? The girl that uses this phone is like 10 so I know its not been tampered with software wise to cause this.
Motorola devices are not my cup of tea when it comes to flashing.
Thanks!
Click to expand...
Click to collapse
Dear remove battery and then blank flash it will work
Hi. Sorry my english)
I bought a phone on Ali. I tried to install LOS16, but after flashing the phone became a black screen and QUSB_BULK.
The phone was Android 8.0.0 retcn.
When I try to restore blankflash_oreo, I get the following errors:
Code:
**** Log buffer [000001] 2019-05-01_23:10:10 ****
[ 0.000] Opening device: \\.\COM7
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 94 (0x5e)
[ 0.005] ...cpu.sn = 2549234984 (0x97f23d28)
[ 0.005] Opening singleimage
[ 0.006] Loading package
[ 0.009] ...filename = pkg.xml
[ 0.011] Loading programmer
[ 0.012] ...filename = programmer.elf
[ 0.012] Sending programmer
[ 0.084] ReadFile() failed, GetLastError()=0
[ 0.390] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.390] ERROR: sahara_download()->general error
[ 0.391] Check qboot_log.txt for more details
[ 0.391] Total time: 0.391s
[ 0.391]
[ 0.391] qboot version 3.85
[ 0.391]
[ 0.391] DEVICE {
[ 0.391] name = "\\.\COM7",
[ 0.391] flags = "0x64",
[ 0.391] addr = "0x28FD64",
[ 0.391] sahara.current_mode = "0",
[ 0.391] api.buffer = "0x2145020",
[ 0.391] cpu.serial = "2549234984",
[ 0.391] cpu.id = "94",
[ 0.391] cpu.sv_sbl = "0",
[ 0.391] cpu.name = "MSM8998",
[ 0.391] storage.type = "UFS",
[ 0.391] sahara.programmer = "programmer.elf",
[ 0.391] api.bnr = "0x2085FF8",
[ 0.391] }
[ 0.391]
[ 0.391]
[ 0.391] Backup & Restore {
[ 0.391] num_entries = 0,
[ 0.391] restoring = "false",
[ 0.391] backup_error = "not started",
[ 0.391] restore_error = "not started",
[ 0.391] }
[ 0.391]
Please share blankflash on 1789-05 for 8.0.0
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Thanks, but not work
Code:
F:\1789-05\blankflash_from_NDX26.183-15_17>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ 0.000] Opening device: \\.\COM6
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.004] ...cpu.sn = 2549234984 (0x97f23d28)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.008] ...filename = pkg.xml
[ 0.010] Loading programmer
[ 0.011] ...filename = programmer.elf
[ 0.011] Sending programmer
[ 0.164] Handling things over to programmer
[ 0.164] Identifying CPU version
[ 0.166] Waiting for firehose to get ready
[ 29.142] ReadFile() failed, GetLastError()=0
[ 45.246] ReadFile() failed, GetLastError()=0
[141.851] ReadFile() failed, GetLastError()=0
[156.494] Waiting for firehose to get ready
[174.054] ReadFile() failed, GetLastError()=0
[190.155] ReadFile() failed, GetLastError()=0
[206.257] ReadFile() failed, GetLastError()=0
[217.966] ...MSM8998 unknown
[217.966] Determining target secure state
[217.968] Waiting for firehose to get ready
[222.356] ReadFile() failed, GetLastError()=0
Make sure you have the drivers installed, use a 2.0 usb port off the mobo. It can be finicky, so check your cable, check your drivers, use another port. It'll work. Some have had luck by unplugging the phone, starting the script, holding vol dwn, and replugging the phone. It can be finicky, just try it again.
I try more and more, but still not work.
I try: win vista x32, win 8.1 x64, win 10 x 64,
two cables, stock and other,
drivers qualcomm x32 and x64,
desktop and notebook, other port.
I try:
blankflash_from_NDX26.183-15_17
blankflash_oreo
blankflash_SPRINT_8.0.0_OCXS27.109-48-6
I don't know what to try yet.
MarkNsk87 said:
I try more and more, but still not work.
I try: win vista x32, win 8.1 x64, win 10 x 64,
two cables, stock and other,
drivers qualcomm x32 and x64,
desktop and notebook, other port.
I try:
blankflash_from_NDX26.183-15_17
blankflash_oreo
blankflash_SPRINT_8.0.0_OCXS27.109-48-6
I don't know what to try yet.
Click to expand...
Click to collapse
Idk if anyone has been successful using the oreo blankflash, the one I linked to has been used successfully many times, so use that one. Verify that the proper driver is assigned to the phone in your device manager, and make sure you're using an administrator cmd prompt. Might try uninstalling the drivers, reboot pc, reinstall drivers, reboot pc, plug in the phone and let everything recognize and settle, verify drivers in device manager, open admin prompt and go for it with the ndx (nougat) blankflash.
I reinstalled the driver, rebooted and tried to execute the command under the administrator, the log changed a little, but still unsuccessfully
Code:
**** Log buffer [000001] 2019-05-02_13:23:28 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 12.844] ReadFile() failed, GetLastError()=0
[ 13.372] ...cpu.id = 94 (0x5e)
[ 13.372] ...cpu.sn = 2549234984 (0x97f23d28)
[ 13.372] Opening singleimage
[B][ 13.372] ERROR: error opening singleimage[/B]
[ 13.388] Check qboot_log.txt for more details
[ 13.388] Total time: 13.388s
[ 13.388]
[ 13.388] qboot version 3.85
[ 13.388]
[ 13.388] DEVICE {
[ 13.388] name = "\\.\COM3",
[ 13.388] flags = "0x64",
[ 13.388] addr = "0x28FD64",
[ 13.388] sahara.current_mode = "3",
[ 13.388] api.buffer = "0x25DB020",
[ 13.388] cpu.serial = "2549234984",
[ 13.388] cpu.id = "94",
[ 13.388] cpu.sv_sbl = "0",
[ 13.388] api.bnr = "0x5D2F78",
[ 13.388] }
[ 13.388]
[ 13.388]
[ 13.388] Backup & Restore {
[ 13.388] num_entries = 0,
[ 13.388] restoring = "false",
[ 13.388] backup_error = "not started",
[ 13.388] restore_error = "not started",
[ 13.388] }
[ 13.388]
Blankflash did not work because of the Motorola_Mobile_Drivers_v6.4.0 drivers, I don’t know how they interfere, but because of them there were errors reading the device and the blankflash did not work.
I worked on my body with blankflash_from_NDX26.183-15_17 - and this is a Verizon bout campaign, judging by the information in the bootloader.
Important all have brick: uninstall Motorola_Mobile_Drivers, before you start blankflash!
Don't wory Mark. I think I have the same gold retcn version of 1789-05. I tried flash some versions of LOS 15 and 16, always ends with Qualcomm mode. For me works blankflash from nougat, but only when battery is less than 10%. When my phone is fully charged, when I try blankflash the phone reconnect to pc. Take me a few evenings to figure it out. Works with Motorola drivers and Qualcomm certificate driver installed in the same time.
Now I have stock EU 8.0 and radio from retcn.
Works everything except Smart lock.
Good luck.
Wysłane z mojego Moto Z (2) przy użyciu Tapatalka
I get this error, can someone help me?
[ 0.000] Opening device: \\.\COM7
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 94 (0x5e)
[ 0.007] ...cpu.sn = 2357123697 (0x8c7eda71)
[ 0.007] Opening singleimage
[ 0.008] Loading package
[ 0.013] ...filename = pkg.xml
[ 0.015] Loading programmer
[ 0.017] ...filename = programmer.elf
[ 0.017] Sending programmer
[ 0.181] Handling things over to programmer
[ 0.182] Identifying CPU version
[ 0.185] Waiting for firehose to get ready
[ 3.642] ...MSM8998 2.1
[ 3.804] Determining target secure state
[ 3.987] ...secure = yes
[ 4.334] Configuring device...
[ 4.361] Skipping UFS provsioning as target is secure
[ 4.362] Configuring device...
[ 5.938] Target NAK!
[ 5.939] ...ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 1
[ 5.939] ...ERROR: Failed to open the device 3 slot 0 partition 1
[ 5.940] ...INFO: Device type 3, slot 0, partition 1, error 0
[ 5.940] ...WARN: Set bootable failed to open 3 slot 0, partition 1, error 0
[ 5.940] ERROR: do_package()->do_recipe()->NAK
[ 5.942] Check qboot_log.txt for more details
[ 5.943] Total time: 5.946s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->NAK
Thank you
41rw4lk said:
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
thanks this method heleped me
you need a blank flash updated for your bootloader, theres at least 5 updates on oreo (OTA UPDATES), then you will need the latest blankflash compatible, maybe the Oreo blank flash that you found here is older than your bricked bootloader. (Sorry for my bad english)
iurd2007 said:
you need a blank flash updated for your bootloader, theres at least 5 updates on oreo (OTA UPDATES), then you will need the latest blankflash compatible, maybe the Oreo blank flash that you found here is older than your bricked bootloader. (Sorry for my bad english)
Click to expand...
Click to collapse
This is a bit of an old post, and I assume those issues are resolved, not sure who you're addressing. As far as oreo blankflash, there is one but as far as I know no one has had success with it. The one that I post frequently uses nougat believe it or not, but it has worked many many times even on oreo and there is no reason to mess with what works. Especially when it comes to blankflashing, it's usually your last chance to resolve the problem.
41rw4lk said:
This is a bit of an old post, and I assume those issues are resolved, not sure who you're addressing. As far as oreo blankflash, there is one but as far as I know no one has had success with it. The one that I post frequently uses nougat believe it or not, but it has worked many many times even on oreo and there is no reason to mess with what works. Especially when it comes to blankflashing, it's usually your last chance to resolve the problem.
Click to expand...
Click to collapse
To blankflash Oreo , you need oreo blankflash, but the last version. There is a oreo (soak test) but not the official stock. But recently someone post the final blankflash for the latest OTA.
iurd2007 said:
To blankflash Oreo , you need oreo blankflash, but the last version. There is a oreo (soak test) but not the official stock. But recently someone post the final blankflash for the latest OTA.
Click to expand...
Click to collapse
You're mistaken. I won't argue the point, by all means do what you will.
41rw4lk said:
You're mistaken. I won't argue the point, by all means do what you will.
Click to expand...
Click to collapse
Ok...
this phone is XT1789-3, its unlocked ,and im replaced it the 6GB RAM chip.Then it can only boot to bootloader,and can not refresh new Bootloader.so i need to flash a new GPT and bootloader .
i successed puted into EDL 9008 Model.but blank-flash faild.its said that:
[ -0.000] Opening device: \\.\COM10
[ 0.001] Detecting device
[ 34.008] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.008] Check qboot_log.txt for more details
[ 34.009] Total time: 34.011s
[ 34.009] qboot version 3.85
[ 34.009] DEVICE {
[ 34.009] name = "\\.\COM10",
[ 34.009] flags = "0x64",
[ 34.009] addr = "0x28FD74",
[ 34.009] api.bnr = "0x5B2898",
anyone know how to do it?
which 9008 should i need ?
did you reslove this? im having the same issue
Hi,
At the risk of sounding retarded or like I have not searched and read through so many forums I could almost quote them verbatim... I am having trouble unbricking my Moto G7 Play... I've followed dadgum near every guide I've found here and other places... Somewhere along the path to unbricking my device the CPU board ID of my device changed which has a few phone guru friends scratching their heads... Now instead of getting communication errors I am getting the following from the blank-flash.bat when I run it... Maybe I've overlooked the issue in my weeks of searching... Any leads or ideas would be greatly appreciated.
C:\G7PlayBlankFlash>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM5
[ 0.016] Detecting device
[ 17.442] ReadFile() failed, GetLastError()=0
[ 19.255] ...cpu.id = 186 (0xba)
[ 19.255] ...cpu.sn = 1196350551 (0x474edc57)
[ 19.255] Opening singleimage
[ 19.271] Loading package
[ 19.271] Failed identify board. Wrong package?
[ 19.271] ERROR: error loading package
[ 19.286] Check qboot_log.txt for more details
[ 19.286] Total time: 19.286s
FAILED: qb_flash_singleimage()->error loading package
The following is the original device information obtained by LMSA which is the root cause for my phone being bricked in the first place.
[ 11.065] name = "\\.\COM5",
[ 11.065] flags = "0x64",
[ 11.065] addr = "0x62FD54",
[ 11.065] sahara.current_mode = "0",
[ 11.065] api.buffer = "0x29D0020",
[ 11.065] cpu.serial = "255476381",
[ 11.065] cpu.id = "204",
[ 11.065] cpu.sv_sbl = "0",
[ 11.065] cpu.name = "SDM636",
[ 11.065] storage.type = "eMMC",
[ 11.065] sahara.programmer = "programmer.elf",
[ 11.065] api.bnr = "0x2911CA8",
Thanks again in advance for any assistance that could be provided.
Wes Satterwhite
NinjaMonkey1183 said:
Hi,
At the risk of sounding retarded or like I have not searched and read through so many forums I could almost quote them verbatim... I am having trouble unbricking my Moto G7 Play... I've followed dadgum near every guide I've found here and other places... Somewhere along the path to unbricking my device the CPU board ID of my device changed which has a few phone guru friends scratching their heads... Now instead of getting communication errors I am getting the following from the blank-flash.bat when I run it... Maybe I've overlooked the issue in my weeks of searching... Any leads or ideas would be greatly appreciated.
C:\G7PlayBlankFlash>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM5
[ 0.016] Detecting device
[ 17.442] ReadFile() failed, GetLastError()=0
[ 19.255] ...cpu.id = 186 (0xba)
[ 19.255] ...cpu.sn = 1196350551 (0x474edc57)
[ 19.255] Opening singleimage
[ 19.271] Loading package
[ 19.271] Failed identify board. Wrong package?
[ 19.271] ERROR: error loading package
[ 19.286] Check qboot_log.txt for more details
[ 19.286] Total time: 19.286s
FAILED: qb_flash_singleimage()->error loading package
The following is the original device information obtained by LMSA which is the root cause for my phone being bricked in the first place.
[ 11.065] name = "\\.\COM5",
[ 11.065] flags = "0x64",
[ 11.065] addr = "0x62FD54",
[ 11.065] sahara.current_mode = "0",
[ 11.065] api.buffer = "0x29D0020",
[ 11.065] cpu.serial = "255476381",
[ 11.065] cpu.id = "204",
[ 11.065] cpu.sv_sbl = "0",
[ 11.065] cpu.name = "SDM636",
[ 11.065] storage.type = "eMMC",
[ 11.065] sahara.programmer = "programmer.elf",
[ 11.065] api.bnr = "0x2911CA8",
Thanks again in advance for any assistance that could be provided.
Wes Satterwhite
Click to expand...
Click to collapse
It says you're using a snapdragon 636 which, the only device in our family with that CPU is the Moto G7 Plus. Try using the blank flash file for the "Lake". I've attached it below.
Spaceminer said:
It says you're using a snapdragon 636 which, the only device in our family with that CPU is the Moto G7 Plus. Try using the blank flash file for the "Lake". I've attached it below.
Click to expand...
Click to collapse
Still receiving error...
C:\G7PlayBlankFlash>blank-flash.bat
C:\G7PlayBlankFlash>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM5
[ 0.003] Detecting device
[ 24.989] ReadFile() failed, GetLastError()=0
[ 26.743] ...cpu.id = 186 (0xba)
[ 26.754] ...cpu.sn = 1196350551 (0x474edc57)
[ 26.758] Opening singleimage
[ 26.764] Loading package
[ 26.780] Failed identify board. Wrong package?
[ 26.786] ERROR: error loading package
[ 26.795] Check qboot_log.txt for more details
[ 26.803] Total time: 26.805s
FAILED: qb_flash_singleimage()->error loading package
C:\G7PlayBlankFlash>pause
Press any key to continue . . .
C:\G7PlayBlankFlash>
Its as if my cpu id changed and qboot is not recognizing the cpu as snapdragon 636 any longer.
Thanks again,
Wes
NinjaMonkey1183 said:
Still receiving error...
C:\G7PlayBlankFlash>blank-flash.bat
C:\G7PlayBlankFlash>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM5
[ 0.003] Detecting device
[ 24.989] ReadFile() failed, GetLastError()=0
[ 26.743] ...cpu.id = 186 (0xba)
[ 26.754] ...cpu.sn = 1196350551 (0x474edc57)
[ 26.758] Opening singleimage
[ 26.764] Loading package
[ 26.780] Failed identify board. Wrong package?
[ 26.786] ERROR: error loading package
[ 26.795] Check qboot_log.txt for more details
[ 26.803] Total time: 26.805s
FAILED: qb_flash_singleimage()->error loading package
C:\G7PlayBlankFlash>pause
Press any key to continue . . .
C:\G7PlayBlankFlash>
Its as if my cpu id changed and qboot is not recognizing the cpu as snapdragon 636 any longer.
Thanks again,
Wes
Click to expand...
Click to collapse
Try reflashing the bank flash for the G7 Play and see if it works now.
Spaceminer said:
Try reflashing the bank flash for the G7 Play and see if it works now.
Click to expand...
Click to collapse
E:\UNBRICK G7 Play\blankflashg7play\blankflash>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM5
[ 0.003] Detecting device
[ 0.007] ...cpu.id = 186 (0xba)
[ 0.008] ...cpu.sn = 1196350551 (0x474edc57)
[ 0.009] Opening singleimage
[ 0.024] Loading package
[ 0.030] Failed identify board. Wrong package?
[ 0.031] ERROR: error loading package
[ 0.032] Check qboot_log.txt for more details
[ 0.032] Total time: 0.033s
FAILED: qb_flash_singleimage()->error loading package
E:\UNBRICK G7 Play\blankflashg7play\blankflash>pause
Press any key to continue . . .
Same results over and over... anymore Ideas? is there a way I can completely reformat the phone completely?
NinjaMonkey1183 said:
E:\UNBRICK G7 Play\blankflashg7play\blankflash>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM5
[ 0.003] Detecting device
[ 0.007] ...cpu.id = 186 (0xba)
[ 0.008] ...cpu.sn = 1196350551 (0x474edc57)
[ 0.009] Opening singleimage
[ 0.024] Loading package
[ 0.030] Failed identify board. Wrong package?
[ 0.031] ERROR: error loading package
[ 0.032] Check qboot_log.txt for more details
[ 0.032] Total time: 0.033s
FAILED: qb_flash_singleimage()->error loading package
E:\UNBRICK G7 Play\blankflashg7play\blankflash>pause
Press any key to continue . . .
Same results over and over... anymore Ideas? is there a way I can completely reformat the phone completely?
Click to expand...
Click to collapse
The best thing I can think of is, reinstall Motorola's USB drivers, then try following this post. The blank flash files need to be in the same folder as the qpst binaries.
Esperimenta este amigo??
https://forum.xda-developers.com/attachment.php?attachmentid=4985183&d=1585912069
Solution!!!
I finally managed to get back to fastboot...
I believe I used the .rar blankflash above (spanish post)
I had no luck with linux nor windows, what I finally did that worked:
---Extract that .rar, "BlackFlash-MotoG7Power"... to the Desktop (Windows 10)
------ That's right. G7 Power. Yet - I'm giving instructions for the g7 PLAY. Infuriating.
---Open command prompt as administrator
---CD to the Desktop
---Run blank-flash.bat
This worked the first time I tried it. I literally was at something like 60 hours of effort towards unbricking my xt1952-4, and this is what worked. I'm relieved, very relieved, but I'm so fed up with everything that didn't work/not knowing WHY it didn't work... Eh, I guess I ought to just take the win...
New rescue tool from Motorola (LMSA) fixes hard bricks
Google search LMSA download and get the new rescue tool from Moto..it wrjs great. I used it to save my G7 play
devine3035 said:
Google search LMSA download and get the new rescue tool from Moto..it wrjs great. I used it to save my G7 play
Click to expand...
Click to collapse
This is now called rescue and smart assistant but you have to be on stock software or it wont work
krbzzr said:
Solution!!!
I finally managed to get back to fastboot...
I believe I used the .rar blankflash above (spanish post)
I had no luck with linux nor windows, what I finally did that worked:
---Extract that .rar, "BlackFlash-MotoG7Power"... to the Desktop (Windows 10)
------ That's right. G7 Power. Yet - I'm giving instructions for the g7 PLAY. Infuriating.
---Open command prompt as administrator
---CD to the Desktop
---Run blank-flash.bat
This worked the first time I tried it. I literally was at something like 60 hours of effort towards unbricking my xt1952-4, and this is what worked. I'm relieved, very relieved, but I'm so fed up with everything that didn't work/not knowing WHY it didn't work... Eh, I guess I ought to just take the win...
Click to expand...
Click to collapse
Holy crap!!!! Your post just saved my new G7! Yes that's right. It's a G7 and I used that blankflash from the spanish post which is for the G7 Power. And why did I try that? Because your G7 Play and my G7 both showed a CPU id of 186 in blankflash mode. So it was like ... what else do I have to lose at that point?
And like with your device, it worked on mine the first time I tried it!
NinjaMonkey1183 said:
E:\UNBRICK G7 Play\blankflashg7play\blankflash>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM5
[ 0.003] Detecting device
[ 0.007] ...cpu.id = 186 (0xba)
[ 0.008] ...cpu.sn = 1196350551 (0x474edc57)
[ 0.009] Opening singleimage
[ 0.024] Loading package
[ 0.030] Failed identify board. Wrong package?
[ 0.031] ERROR: error loading package
[ 0.032] Check qboot_log.txt for more details
[ 0.032] Total time: 0.033s
FAILED: qb_flash_singleimage()->error loading package
E:\UNBRICK G7 Play\blankflashg7play\blankflash>pause
Press any key to continue . . .
Same results over and over... anymore Ideas? is there a way I can completely reformat the phone completely?
Click to expand...
Click to collapse
I HAVE BLACKFLASHED THE MOBILE STILL FASTBOOT MODE IS NOT DISPLAYING IN MY MOBILE PLEASE
SUGGEST ME SOLUTION.
C:\Users\sreep\Downloads\blankflash_capri_RRBS31.Q1-3-68-1-4>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM4
[ 0.028] Detecting device
[ 0.030] ...cpu.id = 310 (0x136)
[ 0.030] ...cpu.sn = 1870415363 (0x6f7c4603)
[ 0.030] Opening singleimage
[ 0.031] Loading package
[ 0.036] ...filename = pkg.xml
[ 0.039] Loading programmer
[ 0.041] ...filename = programmer.elf
[ 0.041] Sending programmer
[ 0.195] Handling things over to programmer
[ 0.195] Identifying CPU version
[ 0.195] Waiting for firehose to get ready
[ 3.325] ...SM_KAMORTA 1.0
[ 3.325] Determining target secure state
[ 3.333] ...secure = yes
[ 3.392] Configuring device...
[ 3.406] Flashing GPT...
[ 3.406] Flashing partition with gpt.bin
[ 3.413] Initializing storage
[ 3.487] ...blksz = 512
[ 3.740] Re-initializing storage...
[ 3.740] Initializing storage
[ 4.011] Flashing bootloader...
[ 4.012] Flashing abl_a with abl.elf
[ 4.093] Flashing devcfg_a with devcfg.mbn
[ 4.138] Flashing hyp_a with hyp.mbn
[ 4.216] Flashing keymaster_a with keymaster.mbn
[ 4.300] Flashing tz_a with tz.mbn
[ 4.717] Flashing storsec_a with storsec.mbn
[ 4.765] Flashing prov_a with prov64.mbn
[ 4.821] Flashing rpm_a with rpm.mbn
[ 4.903] Flashing qupfw_a with qupfw.elf
[ 4.950] Flashing uefisecapp_a with uefi_sec.mbn
[ 5.182] Flashing xbl_config_a with xbl_config.elf
[ 5.235] Flashing xbl_a with xbl.elf
[ 5.766] Rebooting to fastboot
[ 5.783] Total time: 5.787s
C:\Users\sreep\Downloads\blankflash_capri_RRBS31.Q1-3-68-1-4>pause
Press any key to continue . . .
After this completed my mobile screen is still black no fastboot mode showing