Database Develop

Hard Bricked, how can enter Emergency Download Mode?

I am using QFIL to try and revive my X4, but I have no idea how to get into EDL mode when I cannot do anything with the device. Computer recognizes it when I plug it in as Quectel QDLoader 9008 in Ports, but that's it.
Any suggestions would be appreciated. I don't want to have to pay MOTO to fix it if possible.
I've exhausted every resource I have.
Thank you anyone that can help or at least point me in the right direction.\
EDIT: When I was eMMC Software Download app, phone shows in COM3 Download mode, but I need an XML file to flash with that tool and don't know how to get that.

I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?

Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?

DustArma said:
Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?
Click to expand...
Click to collapse
No, my power went out in the middle of fastboot flashing and screwed up all the partitions. I am stuck without the blankflash.. Thank you for replying to try to help.

christopher68369 said:
I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?
Click to expand...
Click to collapse
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.

johnjingle said:
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.
Click to expand...
Click to collapse
you can not take it to the Moto warranty? you do not have to know how the phone went blank...

bookworth said:
you can not take it to the Moto warranty? you do not have to know how the phone went blank...
Click to expand...
Click to collapse
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)

LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Bro! It's works! Thanks for blank-flash for my soft bricked moto x4.

O link não funciona
LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Please guy, this link not work! Help me Please. Thanks

silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
It does, if you follow his instructions stated after the link.

Consegui agora!
jhedfors said:
It does, if you follow his instructions stated after the link.
Click to expand...
Click to collapse
Thanks Very much! work perfectly

Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error:
**** Log buffer [000001] 2018-07-26_14:55:02 ****
[ 0.000] Opening device: \\.\COM6
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 172 (0xac)
[ 0.004] ...cpu.sn = 2293722822 (0x88b76ec6)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.007] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.196] Handling things over to programmer
[ 0.197] Identifying CPU version
[ 0.197] Waiting for firehose to get ready
[ 3.212] ...SDM630 1.0
[ 3.213] Determining target secure state
[ 3.215] ...secure = yes
[ 3.238] Configuring device...
[ 3.243] Flashing GPT...
[ 3.243] Flashing partition with gpt.bin
[ 3.247] Initializing storage
[ 4.421] Target NAK!
[ 4.421] ...ERROR: Failed to open the SDCC Device slot 0 partition 0
[ 4.422] ...ERROR: Failed to open the device 1 slot 0 partition 0
[ 4.423] ...INFO: Device type 1, slot 0, partition 0, error 0
[ 4.423] ...WARN: Get Info failed to open 1 slot 0, partition 0, error 0
[ 4.424] ...ERROR: Failed to get device info slot:0artition:0
[ 4.424] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 4.424] ...ERROR 14: Line 1283: HANDLE_STORAGE_INFO_FAILURE
[ 4.424] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 4.424] Check qboot_log.txt for more details
[ 4.425] Total time: 4.426s
[ 4.425]
[ 4.425] qboot version 3.86
[ 4.425]
[ 4.425] DEVICE {
[ 4.425] name = "\\.\COM6",
[ 4.425] flags = "0x144",
[ 4.425] addr = "0x62FD64",
[ 4.425] sahara.current_mode = "0",
[ 4.425] api.buffer = "0x2B15020",
[ 4.425] cpu.serial = "2293722822",
[ 4.425] cpu.id = "172",
[ 4.425] cpu.sv_sbl = "1",
[ 4.425] cpu.name = "SDM630",
[ 4.425] storage.type = "eMMC",
[ 4.425] sahara.programmer = "programmer.elf",
[ 4.425] module.firehose = "0x2A51630",
[ 4.425] api.firehose = "0xF2EF68",
[ 4.425] cpu.ver = "256",
[ 4.425] cpu.vername = "1.0",
[ 4.425] fh.max_packet_sz = "1048576",
[ 4.425] fh.storage_inited = "1",
[ 4.425] provisioning_may_hang = "true",
[ 4.425] }
[ 4.425]

silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
You mean you can't download ?

waltwittman1 said:
Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error: (log text omitted)
Click to expand...
Click to collapse
I got a similar error when I tried the blank-flash on my bricked Moto X4. @waltwittman1 please let me know if you find a solution.

serial_write() Error
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB1
[ 0.000] Detecting device
[ 21.382] ...cpu.id = 172 (0xac)
[ 21.382] ...cpu.sn = 4247084357 (0xfd255d45)
[ 21.382] Opening singleimage
[ 21.382] Loading package
[ 21.384] ...filename = pkg.xml
[ 21.385] Loading programmer
[ 21.385] ...filename = programmer.elf
[ 21.385] Sending programmer
[ 21.570] Handling things over to programmer
[ 21.570] Identifying CPU version
[ 21.570] Waiting for firehose to get ready
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error​

ttyUSB Permissions Linux
mistryous said:
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error​
Click to expand...
Click to collapse
While I was running as root on my Linux system, this was solved as an issue between the device showing up on /dev/ttyUSB0 initially. I set permissions correctly there, but it reconnects with VolDown+Power on /dev/ttyUSB1 which had limited permissions. While udev rules could solve it, I was lucky to catch the device correctly in time to manually change the permissions and have blankflash progress all the way through. [Upon further thought root should have solved this, so it is likely just an issue with how devices/permissions are set up on my system].

Owner trashed the blankflash file. Can anyone hook me up please?

Here you go.
luvcustom said:
Owner trashed the blankflash file. Can anyone hook me up please?
Click to expand...
Click to collapse
This is the one I use. This is my first post to the XDA forums so they prevented me from linking to my dropbox. So, replace the [dot] with a . and you should be good.
.dropbox [dot] com/s/3xi85sy207x3vs6/blankflash.zip?dl=0[/url]

Win 10 waiting for device message and nothing more.
and no 9008 port

moved

Hard Brick caused by incorrect flashing of mmcblk from adb shell using dd

My G6 has been in qhusb 9008 (qdload mode) for a couple of months. i took a full backup with dd which i have still in both mmcblk0.img form and ive got it broken down into separate partitions on my c drive and even on an sd card. ive tried linux using a sahara program from github that almost works(at least they communicate and the phone requests files) but no luck completing a download. ive tried qpst and qfil on windows many different builds to no avail. ive got a blankflash i found on lolinet that is under the ali section and is labeled blankflash_from_PPS29.26 and the closest i can get to making it work reports the following in the qboot_log.txt:
**** Log buffer [000001] 2019-02-18_13:37:04 ****
[ -0.000] Opening device: \\.\COM6
[ 0.004] Detecting device
[ 0.004] ...cpu.id = 154 (0x9a)
[ 0.004] ...cpu.sn = 2821547254 (0xa82d64f6)
[ 0.004] Opening singleimage
[ 0.040] Loading package
[ 0.040] ...filename = singleimage.pkg.xml
[ 0.044] Loading programmer
[ 0.044] ...filename = programmer.mbn
[ 0.044] Sending programmer
[ 0.128] ReadFile() failed, GetLastError()=0
[ 0.128] ERROR: sahara_download()->IO error
[ 0.128] Check qboot_log.txt for more details
[ 0.128] Total time: 0.128s
[ 0.128]
[ 0.128] qboot version 3.40
[ 0.128]
[ 0.128] DEVICE {
[ 0.128] name = "\\.\COM6",
[ 0.128] flags = "0x64",
[ 0.128] addr = "0x61FE5C",
[ 0.128] sahara.current_mode = "0",
[ 0.128] api.buffer = "0x13B7020",
[ 0.128] cpu.serial = "2821547254",
[ 0.128] cpu.id = "154",
[ 0.128] cpu.sv_sbl = "0",
[ 0.128] cpu.name = "MSM8953",
[ 0.128] storage.type = "eMMC",
[ 0.128] sahara.programmer = "programmer.mbn",
[ 0.128] api.bnr = "0x12F5D80",
[ 0.128] }
[ 0.128]
[ 0.128]
[ 0.128] Backup & Restore {
[ 0.128] num_entries = 0,
[ 0.128] restoring = "false",
[ 0.128] backup_error = "not started",
[ 0.128] restore_error = "not started",
[ 0.128] }
[ 0.128]
can anyone help point me in the right direction here?

how did you get your device to this point?

blowingoff said:
how did you get your device to this point?
Click to expand...
Click to collapse
I was trying different treble gsi's. after a soft brick, instead of flashing stock or using one of ten backups i have on my sd card, i decided to try restoring from a dd backup i had taken, mmcblk0.img. i think i typed the command incorrectly and loaded the backup starting at the wrong address. ill be first to admit i should have been more careful when doing something id never done before. i have tried a billion things, lots of them older, generic qualcomm solutions. i got a new phone, moto x4, but i loved the g6 and it has become more of a learning experience that i want to finish badly. any ideas? im pretty intelligent and read a lot before asking for help. help?

ChefGeoff said:
I was trying different treble gsi's. after a soft brick, instead of flashing stock or using one of ten backups i have on my sd card, i decided to try restoring from a dd backup i had taken, mmcblk0.img. i think i typed the command incorrectly and loaded the backup starting at the wrong address. ill be first to admit i should have been more careful when doing something id never done before. i have tried a billion things, lots of them older, generic qualcomm solutions. i got a new phone, moto x4, but i loved the g6 and it has become more of a learning experience that i want to finish badly. any ideas? im pretty intelligent and read a lot before asking for help. help?
Click to expand...
Click to collapse
dude, your situtation is really difficult. at this point i dont think we have a proper blankflash for g6 and I could only help you if had access to your bootloader. anyway i'll do some researching
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
also, did you check the qboot log to see if theres something there?

ChefGeoff said:
I was trying different treble gsi's. after a soft brick, instead of flashing stock or using one of ten backups i have on my sd card, i decided to try restoring from a dd backup i had taken, mmcblk0.img. i think i typed the command incorrectly and loaded the backup starting at the wrong address. ill be first to admit i should have been more careful when doing something id never done before. i have tried a billion things, lots of them older, generic qualcomm solutions. i got a new phone, moto x4, but i loved the g6 and it has become more of a learning experience that i want to finish badly. any ideas? im pretty intelligent and read a lot before asking for help. help?
Click to expand...
Click to collapse
There are updated versions of firehose and sahara that work for the moto g6 and blank flash files over on the gsmhosting forums. You'll have to do some digging though. I know they're there but I couldn't relocate them last night. I had them on my PC at one point but I think I deleted them because they only work on Linux or windows 7. I'll dig around my files later and check the forums again.
Edit: Try UFS_1058.7 it's probably your best bet and should have everything you need.

blowingoff said:
dude, your situtation is really difficult. at this point i dont think we have a proper blankflash for g6 and I could only help you if had access to your bootloader. anyway i'll do some researching
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
also, did you check the qboot log to see if theres something there?
Click to expand...
Click to collapse
Blankflash here for ALI
mirrors.lolinet.com/firmware/moto/ali/blankflash/

blowingoff said:
dude, your situtation is really difficult. at this point i dont think we have a proper blankflash for g6 and I could only help you if had access to your bootloader. anyway i'll do some researching
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
also, did you check the qboot log to see if theres something there?
Click to expand...
Click to collapse
In the op I included the qboot _log.txt. that's the most info I can get sometimes the log reports much less. If I hold vol down and power for like twenty seconds it makes the reconnect sound on windows and then I can get blank flash to to report all the way to sending programmer.mbn So our chipset is sdm450 while I also see msm8953. I can actually interact with Sahara programmer using Ubuntu and a Sahara GUI I compiled from github. I am fascinated by this stuff but have no one to teach me what I'm doing. I would like to figure or how to utilize the fill 30gb IMG file that I've also split into partitions of the mmcblk0 I fell like that's an advantage I've got. I all also have another back up of each partition that I took using an app called partition backup https://play.google.com/store/apps/details?id=ma.wanam.partitions
Thanks for there responses I really fell like in getting closer maybe I should have made this post months ago but I wanted to get it on my own

vinny_silveira said:
Blankflash here for ALI
mirrors.lolinet.com/firmware/moto/ali/blankflash/
Click to expand...
Click to collapse
For some reason the blank flash gives me the results I posted in op

I have been also searching for blank flash file for moto G6 but didnt found. If you gyz found it than please live with link except of that lolinet because it didint work for me as well.

would you please provide me mmcblk0.img ?

A similar problem.
Short description:
Hello dear gurus.
I got myself a smartphone Motorola (Lenovo) moto G6 on the Anroid 8.0 Oreo platform.
Carried out OTA updates - security systems. After that it was proposed to update to Anrdroid 9.0 Pie. Updated.
Next, I installed a custom recovery (TeamWin Recovery Project (TWRP)) on a new bootloader, created a backup system for this recovery.
Then I tried to upload a new custom (amateur) firmware (ViperOS), but TWRP refused to install this firmware.
So I tried about 10 different firmwares, including official ones, that were compatible with my Moto G6 device.
In the end, through trial and error, I turned a brand new phone into a Hard Brick, Hard Brick.
Now, neither the recovery, nor the system, nor even the (bootloader) chain of bootloaders PBL, aboot, SBL are starting.
The only thing how the phone is detected (after installing specific drivers for my device and processor) in the system is Qualcomm HS-USB Qload 9008. That is, Emergency Download mode (EDL mode).
To convert the device to SoftBrick (9006) - light brick. I need to restore the entire chain of bootloaders, starting with the SBL of the secondary bootloader.
For my device, there is a special utility BlankFlash_PPS29.26 (see Attachment), which automatically, when Blank_Flash.bat starts, re-partitioning MBR partitions, creating a partition table and restoring the entire boot chain.
But there is one significant "BUT", this utility completely refuses to reflash the chain of device loaders, displaying an I / O error in the logs (see Attachment).
After talking with smart people with forPDA, I realized that the same OTA security update is not suitable for the successful firmware of my device, what is in the utility is later, but what is newer and more secure on the device and the configuration file singleimage.bin located in this utility does not fit.
If there are people who are able to write the correct script for .bash for my firmware version and security system and build this whole economy into singleimage.bin, then please respond.
Click to expand...
Click to collapse

another moto x4 hard bricked, need help, please.

So my phone was working well, i left it on the table ,half hour later, phone its off, and i tried to turn it on to no good luck, so i followed 2 or 3 sugestions i found in here but i dont get lucky. So far i have downloaded a moto x4 blank flash zip with the qualcom 9008 stuff with the correct driver but i fail everytime, i have found several blank files and even one identified as motox4 blank file but non of them seem to work, i have tried to set up the bat file and any aplication on admin mode too and no luck. heres my log of the error i get, thanks for any help and pardon my bad english. PS i had latest rom on an amazon x4 with april patch not modified in any way, it was just pure motorola software. no root, no unlocked bootloader, nothing, plain original stuff. thanks again .
C:\Users\Shaggy\Downloads\blankflash1\blankflash>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM11
[ 0.003] Detecting device
[ 0.007] ...cpu.id = 172 (0xac)
[ 0.007] ...cpu.sn = 2881831708 (0xabc5431c)
[ 0.008] Opening singleimage
[ 0.009] Loading package
[ 0.012] Failed identify board. Wrong package?
[ 0.012] ERROR: error loading package
[ 0.028] Check qboot_log.txt for more details
[ 0.030] Total time: 0.031s
FAILED: qb_flash_singleimage()->error loading package
Click to expand...
Click to collapse

try this blankflash and don't forget to hold vol+ or vol- for a few seconds before running the script. good luck!

Thanks, I tried it this morning and it didn't work, I got an extra hard drive and I ma install Windows 7 on it as I believe somehow it has something with windows 10 not letting applications do they're job. It's not the first time this happens to me. I'll post results later on .

blank flash file did not worked for me, i tried in windows 7 and live ubuntu with no luck. Perhaps is it because im on android 9 with april patch? can anyone supply a newer blank flash please, thanks for the help.

so acording to a diferent topic on the same thing, but for a moto z, i need the blank flash file that goes according to my bootloader wich is the newest one for the amazon prime moto x4 , so hopefully someone would step up and help.

[ULTIMATE GUIDE] How To Unbrick your Moto G7 Plus

​THIS GUIDE IS FOR THE MOTO G7 PLUS ONLY AND IT'S NOT 100% GUARANTEED TO WORK.
WORKED ON MY G7 PLUS (XT1965-2) AND SOME OTHER USERS ON WINDOWS.
THINGS YOU WILL NEED:
Motorola and Qualcomm Drivers;
Blankflash file;
Stock ROM;
STEPS:
PART 1: PREPARING YOUR PC!!!​
STEP 1: Install Motorola and Qualcoom Drivers (Install the Qualcomm Driver according to your Windows version. Example: Win x64-> driver 64 bits, win x86-> driver 86 bits) (To find out which version of your windows you have, press the WIN + Pause Break keys and see System type session for the version.);
STEP 2: After installing drivers, put your PC into test mode.
Open "CMD " as Administrator and run following commands:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
STEP 3: Reboot your pc.
PART 2: RECOVERING PHONE!!!​
STEP 1: Extract blankflash zip file to a folder;
STEP 2: With Phone plugged into your PC, hold "Vol-" + "Power" buttons for about 15 to 30 seconds, when you hear a sound like USB stick being plugged, run immediately "blank-Flash.bat" file, when CMD window opens, immediately release the buttons and wait to finish the process. (You need to be quick in this step.) (If it does not work, repeat this step until the CMD does not display errors or the phone boot.)
Your device should now enter FastBoot mode.
STEP 3: Follow the walkthrough that I left in the LINK of the stock ROM, there teaches how to install the stock ROM on your phone.
OBS: Flash the stock ROM with the computer still in test mode!!!
PART 3: RECONFIGURING THE PC!!!​
STEP 1: Let's now take the PC out of the test mode and get back to normal.
Open the "CMD " as Administrator and run the following commands:
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
STEP 2: Reboot your pc.
​​​THE END!​
​
SPECIAL THANKS TO:
@vache by Blankflash file;
Thanks to @Allexwin50 for testing the tutorial and the Blankflash file.
And for everyone in the group Moto G7 Plus - Discussion on Telegram https://t.me/g7plus

Thank you very very much for your work !
Could you help me with one more thing?
I can´t find the Flash-the-stock-ROM-walkthrough that you left in the link

Man, you saved the day for me with this. Thank you so much!!!

Work for unlocked g7 or no?

Buenas tardes, amigo, no consigo que el blankflash me reconozca el moto g7 plus, el telefono bootea bootloader, pero tiene una rom lineage os, y bootloader bloqueado, no me deja desbloquearlo ni tampoco flashear la ultima version

"waiting for device"
my phone is soft bricked and has no operating system. tried your blankflash file and when I release the vol - +power key after clicking on blankfish.bat file in the command window it just says waiting for devices.
am I doing something wrong? any other way to get a stock rom on my phone? bootloader unlocked, attempeted to install lineage os for lake but after wiping davlik /cache, system, data now stuck with no os!!!
Help please!!

For those of you that have a Fubar bootloader that won't let you flash or do anything use the following command to enter the Qualcomm connection with your PC.
"fastboot oem blankflash"
Once you run this, your screen will go black on phone and windows will reconnect under the other port. You may have to wait a minute for it to find the qualcomm drivers from luiz_neto post. You can check your Device Manager when it is done.
Run at command line the blank-Flash.bat file and follow the rest of luiz_neto instructions.

arachniac1 said:
"waiting for device"
my phone is soft bricked and has no operating system. tried your blankflash file and when I release the vol - +power key after clicking on blankfish.bat file in the command window it just says waiting for devices.
am I doing something wrong? any other way to get a stock rom on my phone? bootloader unlocked, attempeted to install lineage os for lake but after wiping davlik /cache, system, data now stuck with no os!!!
Help please!!
Click to expand...
Click to collapse
For those of you that have a Fubar bootloader that won't let you flash or do anything use the following command to enter the Qualcomm connection with your PC.
"fastboot oem blankflash"
Once you run this, your screen will go black on phone and windows will reconnect under the other port. You may have to wait a minute for it to find the qualcomm drivers from @luiz_neto post. You can check your Device Manager when it is done you'll have a new connection under a "Ports (COM & LPT)".
I have a XT1692-1 and used this file to blankflash.
blankflash_RIVER_RETAIL_PPOS29.114-134-10.zip
Zippyshare.com - Free File Hosting
www87.zippyshare.com
Run at command line the "blank-Flash.bat" file and follow the rest of @luiz_neto instructions.

@Natas899 Hey brother just noticed the blankflash.zip.you uploaded is not for lake?? It says River so did you mistakenly download wrong file?....could be tragic

KtownJeff said:
@Natas899 Hey brother just noticed the blankflash.zip.you uploaded is not for lake?? It says River so did you mistakenly download wrong file?....could be tragic
Click to expand...
Click to collapse
I have River XT1692-1 model of the Moto G7 which take a different blankflash file.

I should have clarified more that I have a River Moto G7. But the threads instructions still applied and fixed my phone with using a different blankflash file and the correct ROM for my phone.

Stuck in Part1 after the "TESTSIGNING" command, I get this error:
"The value is protected by Secure Boot policy and cannot be modified or deleted." I did run with Admin privilege and the "IntegrityCheck" passed fine.
UPDATE: Got it to work. Had to disable Secure Boot protection.
BIG THANK YOU and Happy New Year

I've got a factory unlocked xt1965-t g7 plus lake I bought directly from Moto. Unlocked bootloader no problem. When I tried to flash TWRP got some errors saying could not access 2 or 3 partitions and I had chosen to back up the existing and received a second error saying could not access 3 or 4 partitions. Hard brick. I've tried every blankflash I can find supposedly for this version. Tried executing it, then plugging in the usb or holding vol+ and pwr same time until USB registers on comm port and then let go. I always get the following. Same on Linux or WIndows:
C:\Source\blankflash3>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM10
[ -0.000] Detecting device
[ 34.310] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.310] Check qboot_log.txt for more details
[ 34.310] Total time: 34.310s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
C:\Source\blankflash3>pause
Press any key to continue . . .
Log doesn't say much:
**** Log buffer [000001] 2021-01-30_01:36:11 ****
[ -0.000] Opening device: \\.\COM10
[ -0.000] Detecting device
[ 34.310] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.310] Check qboot_log.txt for more details
[ 34.310] Total time: 34.310s
[ 34.310]
[ 34.310] qboot version 3.86
[ 34.310]
[ 34.310] DEVICE {
[ 34.310] name = "\\.\COM10",
[ 34.310] flags = "0x64",
[ 34.310] addr = "0x28FD64",
[ 34.310] api.bnr = "0x3C2E18",
[ 34.310] }
[ 34.310]
[ 34.310]
[ 34.310] Backup & Restore {
[ 34.310] num_entries = 0,
[ 34.310] restoring = "false",
[ 34.310] backup_error = "not started",
[ 34.310] restore_error = "not started",
[ 34.310] }
[ 34.310]
Seems to me I might just not have a blankfile that's compatible ? Question: Do these blankfiles just write to existing partitions or do they rewrite the partitions ? If the former and you have a damaged partition, then I suppose the blankfile won't work.
Any ideas much appreciated. Thanks!

escondidohiker said:
I've got a factory unlocked xt1965-t g7 plus lake I bought directly from Moto. Unlocked bootloader no problem. When I tried to flash TWRP got some errors saying could not access 2 or 3 partitions and I had chosen to back up the existing and received a second error saying could not access 3 or 4 partitions. Hard brick. I've tried every blankflash I can find supposedly for this version. Tried executing it, then plugging in the usb or holding vol+ and pwr same time until USB registers on comm port and then let go. I always get the following. Same on Linux or WIndows:
C:\Source\blankflash3>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM10
[ -0.000] Detecting device
[ 34.310] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.310] Check qboot_log.txt for more details
[ 34.310] Total time: 34.310s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
C:\Source\blankflash3>pause
Press any key to continue . . .
Log doesn't say much:
**** Log buffer [000001] 2021-01-30_01:36:11 ****
[ -0.000] Opening device: \\.\COM10
[ -0.000] Detecting device
[ 34.310] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.310] Check qboot_log.txt for more details
[ 34.310] Total time: 34.310s
[ 34.310]
[ 34.310] qboot version 3.86
[ 34.310]
[ 34.310] DEVICE {
[ 34.310] name = "\\.\COM10",
[ 34.310] flags = "0x64",
[ 34.310] addr = "0x28FD64",
[ 34.310] api.bnr = "0x3C2E18",
[ 34.310] }
[ 34.310]
[ 34.310]
[ 34.310] Backup & Restore {
[ 34.310] num_entries = 0,
[ 34.310] restoring = "false",
[ 34.310] backup_error = "not started",
[ 34.310] restore_error = "not started",
[ 34.310] }
[ 34.310]
Seems to me I might just not have a blankfile that's compatible ? Question: Do these blankfiles just write to existing partitions or do they rewrite the partitions ? If the former and you have a damaged partition, then I suppose the blankfile won't work.
Any ideas much appreciated. Thanks!
Click to expand...
Click to collapse
You are trying to flash "sahara" and your phone is "lake"

Usernameisnotavailable said:
You are trying to flash "sahara" and your phone is "lake"
Click to expand...
Click to collapse
I'm not sure I remember how I figured it was 'lake'. I think it said so on the recovery screen. Doesn't 'lake' mean it's the "-t" version of the xt1956 ? Pontodevista on the Moto board unbricked his -t model using the 'saraha' file he posted. I dunno. Maybe I need a different blankflash file that doesn't exist yet ? There's another thread on XDA where someone explained how they made what seems to be the basis of the blankflash everyone else using for the G7 and theoretically I could make one for the G7 Plus (-t) , but I'm not sure I follow his instructions very clearly. Anyone else had luck unbricking the -T of the XT1965 ? What is 'lake" ? Is that all "plus" versions ?
Thanks!

escondidohiker said:
I'm not sure I remember how I figured it was 'lake'. I think it said so on the recovery screen. Doesn't 'lake' mean it's the "-t" version of the xt1956 ? Pontodevista on the Moto board unbricked his -t model using the 'saraha' file he posted. I dunno. Maybe I need a different blankflash file that doesn't exist yet ? There's another thread on XDA where someone explained how they made what seems to be the basis of the blankflash everyone else using for the G7 and theoretically I could make one for the G7 Plus (-t) , but I'm not sure I follow his instructions very clearly. Anyone else had luck unbricking the -T of the XT1965 ? What is 'lake" ? Is that all "plus" versions ?
Thanks!
Click to expand...
Click to collapse
Each software build has an official name (lake, river, sahara....etc) that should match each specific model number. The -T doesn't mean anything; it's part of the model number. You should easily find the build name using the complete model number. There are also a few variations of the same build based on where the phone was originally sold. (carrier name, unlocked, etc) And use the official Motorola flash file, no need to build your own. If you are able to boot into the recovery screen, just use the official Motorola Rescue and Smart Assistant to flash

Usernameisnotavailable said:
Each software build has an official name (lake, river, sahara....etc) that should match each specific model number. The -T doesn't mean anything; it's part of the model number. You should easily find the build name using the complete model number. There are also a few variations of the same build based on where the phone was originally sold. (carrier name, unlocked, etc) And use the official Motorola flash file, no need to build your own. If you are able to boot into the recovery screen, just use the official Motorola Rescue and Smart Assistant to flash
Click to expand...
Click to collapse
HEY... Sarah is referring to the firehose programmer part of the Qualcom execution of the on board bootloader.... now I've had success with blankflash with other devices.. haven't personally tried this on g7 plus but my question is how in the world did you hard brick...I've flashed over and over and tried to brick mine so I can bring it back to life and I haven't had the success.... we don't have a direct command to EDL mode unless you short the board... i seen something about running OEM commands from Fast boot to override secure boot but I don't know how full of **** he was because it seems like ALOT here lately that we have had this surge of trolls trying to give XDA traffic... and honestly I don't believe You have exhausted your researching skills because if you can put a hit piece post about bricking with all the info you shared then you should probably be well vested with reading other threads and using your head.... QUALCOM SNAP DRAGON IS UNBRICKABLE.....that's why QPST and QFIL are for ....and if you can root flash and mod use magisk fake your location tunnel audio backchannels and track bitcoin miners then you should be fine... Oh when you search the web for answers don't use CHROME OR GOOGLE OR EDGE because the main search engines are full of bots that keep you in a circle that try to bring you through other countries servers backwards to collect data and lie for the globilst agenda so I recommend duck duck go and tor and the guide at the top of the g7plus form about asking any question noob friendly....

and why you bricked in one thread and got it in another.....SMH....same day posted
damn hacks what you want network traffic...to jump on the mine train or something....thats why i quit screwing with this app....they need boot bots like telegram here

KtownJeff said:
and why you bricked in one thread and got it in another.....SMH....same day posted
damn hacks what you want network traffic...to jump on the mine train or something....thats why i quit screwing with this app....they need boot bots like telegram here
Click to expand...
Click to collapse
Sounds like you know a lot more than me... I was just trying to help answer this guy's question. And I did manage to brick my G7 and it's pretty easy to do that because it uses 2 partitions. But it wasn't too difficult for me (a newbie) to recover.

I did get this working. The blankflash is just tricky. There's a timing issue where you have to issue the command at what seems to be right after the computer recognized the device. You have to get it just right. Might take you 20 tries. It's a little easier on windows because you hear that sound when it recovnizes the USB device, but at this point, I've done it a few times on linux also. If you get stuck trying to do the blankflash, just hold the volume- and pwr simultaneously and keep issuing the command in the terminal. It might take you many tries but eventually you'll snag it. Thanks to all for you help !

Moto G6 XT1925-6 "bricked" from normal use--blankflash not working

Hi all,
My girlfriend's Moto G6 XT1925-6 (purchased via Best Buy, never rooted/modded) got slow one day, I recommended rebooting and then it never came back. The only signs of life are that when plugged into a computer or charger. the white light blinks every second or so, and the phone shows up as the following USB device (port):
Qualcomm HS-USB QDLoader 9008 (COM4)
I have tried 3-4 different blankflash files numerous times (including the two from https://mirrors.lolinet.com/firmware/moto/ali/blankflash/) and always get an IO error. The phone would have been fully updated as of 11/1, it was being used on Cricket Wireless if that matters. Lenovo Moto Smart Assistant was no help unfortunately since the phone cannot boot into fastboot.
I tried again today since one 'fix' seemed to be to let the battery discharge. It was unplugged for ~5 days and no change.
Any other tips/tricks or am I SOL? She was somewhat due for an upgrade anyways, but thought I'd try one last time to look for other solutions.
Thanks!

timing is absolutely critical in EDL mode - i.e., you don't have long to start the flashing once you plug the USB cable in. sounds like you have the correct drivers, given that the phone shows up properly in device manager. try the following in quick succession:
0. plug the USB cable into the computer (not the phone, yet)
1. start the blankflash script from lolinet
2. depress and hold the power and volume_down buttons
3. connect the USB cable
4. script will do its magic (release the buttons) and reboot the phone to the bootloader
hope this helps!

armrbackthrsday said:
timing is absolutely critical in EDL mode - i.e., you don't have long to start the flashing once you plug the USB cable in. sounds like you have the correct drivers, given that the phone shows up properly in device manager. try the following in quick succession:
0. plug the USB cable into the computer (not the phone, yet)
1. start the blankflash script from lolinet
2. depress and hold the power and volume_down buttons
3. connect the USB cable
4. script will do its magic (release the buttons) and reboot the phone to the bootloader
hope this helps!
Click to expand...
Click to collapse
Exactly when are you supposed to release the buttons? No matter when I do, I get:
ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error

Heat84 said:
Exactly when are you supposed to release the buttons? No matter when I do, I get:
ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
Click to expand...
Click to collapse
hmm, sounds like the blankflash script is not recognizing the correct COM port. does the device show up as "Qualcomm HS-USB QDLoader 9008" in device manager?

armrbackthrsday said:
hmm, sounds like the blankflash script is not recognizing the correct COM port. does the device show up as "Qualcomm HS-USB QDLoader 9008" in device manager?
Click to expand...
Click to collapse

I fixed that problem by rebooting the phone while qflash was running. Now I have a different error that you see below at 3. 485.
Code:
[ -0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 286 (0x11e)
[ 0.002] ...cpu.sn = 1010000641 (0x3c336301)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.009] ...filename = programmer.elf
[ 0.009] Sending programmer
[ 0.131] Handling things over to programmer
[ 0.131] Identifying CPU version
[ 0.131] Waiting for firehose to get ready
[ 3.213] ...SM_SAIPAN 2.0
[ 3.214] Determining target secure state
[ 3.219] ...secure = yes
[ 3.307] Configuring device...
[ 3.317] Skipping UFS provsioning as target is secure
[ 3.317] Configuring device...
[ 3.483] Flashing GPT...
[ 3.483] Flashing partition with gpt.bin
[ 3.485] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->find_first_package()->not found
[ 3.486] Check qboot_log.txt for more details
[ 3.486] Total time: 3.487s
[ 3.487]
[ 3.487] qboot version 3.86
[ 3.487]
[ 3.487] DEVICE {
[ 3.487] name = "\\.\COM11",
[ 3.487] flags = "0x144",
[ 3.487] addr = "0x28FD74",
[ 3.487] sahara.current_mode = "0",
[ 3.487] api.buffer = "0x2570020",
[ 3.487] cpu.serial = "1010000641",
[ 3.487] cpu.id = "286",
[ 3.487] cpu.sv_sbl = "0",
[ 3.487] cpu.name = "SM_SAIPAN",
[ 3.487] storage.type = "UFS",
[ 3.487] sahara.programmer = "programmer.elf",
[ 3.487] module.firehose = "0x24D1248",
[ 3.487] api.firehose = "0x67D948",
[ 3.487] cpu.ver = "512",
[ 3.487] cpu.vername = "2.0",
[ 3.487] fh.max_packet_sz = "1048576",
[ 3.487] fh.storage_inited = "1",
[ 3.487] }
[ 3.487]
I don't actually have to worry about this any more because I was tired of playing around and took the phone(a Motorola Edge plain 2020) back to Best Buy where I got it, and they couldn't fix it, but they did offer to exchange it for a new one. I chose an "open box" one that probably was returned the day after it was bought by the first owner for some stupid reason. I also got a $74 refund to even the exchange(I would've had to wait a week for a new one or choose a different make and/or model phone available in store otherwise). But don't let that stop you from offering a translation to this error message if you have one. I'm curious and you may help someone else.
Why would the developer of Qboot not have any documentation of what the error messages mean? What's the point of writing error messages if you don't tell anybody what they mean? Was that done out of arrogance or stupidity? Also, when it says to check qboot log for details, that BS. Everything you see during the flash attempt on screen is all you see in the log. Nothing more.
By the way if you're interested, I started a thread about my problem before I found this one: https://forum.xda-developers.com/t/...hard-hard-bricked-edge.4341829/#post-85717539
By the way 2: It seems to be a weird coincidence that you resurrected this thread almost a year after the last (and only) post at the SAME TIME I was having the same issue they were. Even though you didn't help me and I don't need the help anymore, you gotta admit that that's a little creepy. lol