Recently by accident I downgraded the operating system on my Moto G7 Plus device (XT1965-3) and hard bricked my phone. :crying:
It took me some days on checking different threads to come to a solution. I managed to create a blankflash file that finally recovered my bootloader so that I could get into fastboot mode and flash the latest OS.
For those who are faced with the same problem, I'd like to share my solution and hope it works for you as well.
When the phone is hard bricked, it do not boot, it stays in black screen. The good thing though is that by default it goes into Qualcomms EDL (Emergency DownLoad) mode.
When connecting your phone to the PC (e.g. Windows 10) you should see in the device manager under COM the following device:
Qualcomm HS-USB QDLoader 9008 (COM..)
If this do not show up, unplug the phone, press Power + VolumeDown for about 30 seconds and connect the device again.
If it still not works, you might search for the correct drivers.
Assuming you see the device as mentioned above, then you can do the blankflash.
Open a cmd window (ideally with Administrator rights)
Unzip the blankflash.zip View attachment blankflash.zip
Run blank-flash.bat
This should download the bootloader and your phone should get back to live (in fastboot mode)
After you have fixed the bootloader you can flash the latest OS with fastboot mode.
Download the latest version from: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the ROM and add the following files to the same directory View attachment FastBootAddOnFiles.zip
Connect the phone in fastboot mode
Run flashfile.bat from a cmd window
Now the ROM is flashed to the phone
Hope this helps recovering your phone!
Does it work for the power of Moto g7?
Anyway this works on unlocked g7? I need a blank flash or something to revive my hard bricked device
is it possible to restore previously unlocked phone to out-of-the-box software and behaviour? specifically I would like to get rid of the bootloader warning and verity disabled message at boot. I wouldn't mind locking again
"Waiting for device"
Hi WinnieH.
First off, i would like to thank you for explaining the necessity of the blankflash to recover the bootloader.
But when i try the steps you suggested, nothing happens. I get stuck in the message "Waiting for device..."
I noticed that the main command in the bat file is just: ".\qboot.exe blank-flash %*".
Wouldn't be necessary a reference to the singleimage.bin file in this command? Or maybe is a file missing in the zip.
I appreciate some suggestion.
Thanks,
Marcos
mrufino said:
Hi WinnieH.
First off, i would like to thank you for explaining the necessity of the blankflash to recover the bootloader.
But when i try the steps you suggested, nothing happens. I get stuck in the message "Waiting for device..."
I noticed that the main command in the bat file is just: ".\qboot.exe blank-flash %*".
Wouldn't be necessary a reference to the singleimage.bin file in this command? Or maybe is a file missing in the zip.
I appreciate some suggestion.
Thanks,
Marcos
Click to expand...
Click to collapse
Sorry for late response.
if the message "Waiting for device ..." comes, then your phone is not recognized correctly. Your device when bricked should connect in Emergency Download (EDL) mode. You could see this when you go to the Windows Device Manager. Under the COM devices your phone should show up with the Qualcomm. If not, disconnect the phone for a minute and try it again.
If you have the driver not installed it, the installation video might help: https://www.youtube.com/watch?v=ezQJlBKN9hk
PS: The blank-flash.bat is fine. It will automatically use the singleimage.bin file
Hope you get your way
Thank you WinnieH for the response. (that was not late at all!).
I will try to install the driver; I was unable to connect in Emergency Download Mode.
mrufino said:
Thank you WinnieH for the response. (that was not late at all!).
I will try to install the driver; I was unable to connect in Emergency Download Mode.
Click to expand...
Click to collapse
Well, first of all thanks to WinnieH for this useful thread. It worked fine for my phone.
@mrufino Maybe you have to install the moto drivers. Or try a different pc. The phone was not detected on my first pc, on my other pc it was detected immediately.
WinnieH said:
Recently by accident I downgraded the operating system on my Moto G7 Plus device (XT1965-3) and hard bricked my phone. :crying:
It took me some days on checking different threads to come to a solution. I managed to create a blankflash file that finally recovered my bootloader so that I could get into fastboot mode and flash the latest OS.
For those who are faced with the same problem, I'd like to share my solution and hope it works for you as well.
When the phone is hard bricked, it do not boot, it stays in black screen. The good thing though is that by default it goes into Qualcomms EDL (Emergency DownLoad) mode.
When connecting your phone to the PC (e.g. Windows 10) you should see in the device manager under COM the following device:
Qualcomm HS-USB QDLoader 9008 (COM..)
If this do not show up, unplug the phone, press Power + VolumeDown for about 30 seconds and connect the device again.
If it still not works, you might search for the correct drivers.
Assuming you see the device as mentioned above, then you can do the blankflash.
Open a cmd window (ideally with Administrator rights)
Unzip the blankflash.zip View attachment 4810965
Run blank-flash.bat
This should download the bootloader and your phone should get back to live (in fastboot mode)
After you have fixed the bootloader you can flash the latest OS with fastboot mode.
Download the latest version from: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the ROM and add the following files to the same directory View attachment 4810964
Connect the phone in fastboot mode
Run flashfile.bat from a cmd window
Now the ROM is flashed to the phone
Hope this helps recovering your phone!
Click to expand...
Click to collapse
Great post. Where did you find the singleimage for your phone? i've tryed to do with my G7 RIVER bricked, but unsuccessful need some help!
diegovmsouza said:
Great post. Where did you find the singleimage for your phone? i've tryed to do with my G7 RIVER bricked, but unsuccessful need some help!
Click to expand...
Click to collapse
Hello,
I did the image by myself. I used a older image of a G6 device and replace a number of elements in the image from the stockrom. With "star" you can delete and add files to the "singleimage.bin" archive. It took me some trials. Check on the latest STOCK ROM "XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" from https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/ and you should find the most important files (such as partition table: gpt.bin).
Hope it works for you
Regards
Winnie
WinnieH said:
Hello,
I did the image by myself. I used a older image of a G6 device and replace a number of elements in the image from the stockrom. With "star" you can delete and add files to the "singleimage.bin" archive. It took me some trials. Check on the latest STOCK ROM "XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" from https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/ and you should find the most important files (such as partition table: gpt.bin).
Hope it works for you
Regards
Winnie
Click to expand...
Click to collapse
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
diegovmsouza said:
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
Click to expand...
Click to collapse
Just use "star list bootloader.img" and you get all the relevant file.
Code:
star list ..\..\XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\bootloader.img
1 339968 md5:e4c77bb1f8862444bedb908067d5063d abl.elf
2 519296 md5:4b8eaa75b77eae4981604f7893bf7279 cmnlib.mbn
3 519296 md5:ac35656340c5f87037a64ce4f937b16c cmnlib64.mbn
4 2722 md5:d3ee34bff4d352a045b7e42b447666a7 default.xml
5 126080 md5:4590a7b21b0d70d4403fa95ad23a6e9d devcfg.mbn
6 38400 md5:27ba16d71e0d16c86423192d5615a25c gpt.bin
7 519296 md5:0582b648798303e0441930fd84a39b9a hyp.mbn
8 519296 md5:2686fd49e16e78a0e9ef2335104e96bc keymaster.mbn
9 125 md5:c3a63b25166c5fcac0cc1426bf44a271 pkg.xml
10 519296 md5:1437d90bab43816d4a3541b18edac61c pmic.elf
11 257152 md5:5e3b6f2cf09747bd3bac33023c2014a7 prov64.mbn
12 519296 md5:31ab4015a996f2ad6dd61c94076fea98 rpm.mbn
13 126080 md5:5054d3c7863d09d6333c509003548e4d storsec.mbn
14 2092160 md5:44a6f561bab5d2822066574e3d0116eb tz.mbn
15 3665024 md5:a2a5945cf2ae44cd95da3ee180480662 xbl.elf
16 172 md5:1fd033214e7e36c4134a927f1ce944f0 index.xml
17 606400 md5:4b6e1345d3fb9b347ce7fc6357def85a programmer.elf
Extract the files from the bootloader and replace them on the singleimage.bin and thats it.
e.g.
Code:
star delete abl.elf
star add abl.elf
Pressing thumbs
WinnieH said:
Just use "star list bootloader.img" and you get all the relevant file.
Code:
star list ..\..\XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\bootloader.img
1 339968 md5:e4c77bb1f8862444bedb908067d5063d abl.elf
2 519296 md5:4b8eaa75b77eae4981604f7893bf7279 cmnlib.mbn
3 519296 md5:ac35656340c5f87037a64ce4f937b16c cmnlib64.mbn
4 2722 md5:d3ee34bff4d352a045b7e42b447666a7 default.xml
5 126080 md5:4590a7b21b0d70d4403fa95ad23a6e9d devcfg.mbn
6 38400 md5:27ba16d71e0d16c86423192d5615a25c gpt.bin
7 519296 md5:0582b648798303e0441930fd84a39b9a hyp.mbn
8 519296 md5:2686fd49e16e78a0e9ef2335104e96bc keymaster.mbn
9 125 md5:c3a63b25166c5fcac0cc1426bf44a271 pkg.xml
10 519296 md5:1437d90bab43816d4a3541b18edac61c pmic.elf
11 257152 md5:5e3b6f2cf09747bd3bac33023c2014a7 prov64.mbn
12 519296 md5:31ab4015a996f2ad6dd61c94076fea98 rpm.mbn
13 126080 md5:5054d3c7863d09d6333c509003548e4d storsec.mbn
14 2092160 md5:44a6f561bab5d2822066574e3d0116eb tz.mbn
15 3665024 md5:a2a5945cf2ae44cd95da3ee180480662 xbl.elf
16 172 md5:1fd033214e7e36c4134a927f1ce944f0 index.xml
17 606400 md5:4b6e1345d3fb9b347ce7fc6357def85a programmer.elf
Extract the files from the bootloader and replace them on the singleimage.bin and thats it.
e.g.
Code:
star delete abl.elf
star add abl.elf
Pressing thumbs
Click to expand...
Click to collapse
thanks for listening. When I list the bootloader.iso file it returns me the following error: "Failed: simg_open () -> IO error". already extract the rom stock again, already downloaded it from scratch and the result is the same. When I extract the bootloader.iso file the same error occurs. what could it be? Can you help me extract these files? I am attaching the bootloader file of moto g7 river, if you can help me I will be immensely grateful.
diegovmsouza said:
thanks for listening. When I list the bootloader.iso file it returns me the following error: "Failed: simg_open () -> IO error". already extract the rom stock again, already downloaded it from scratch and the result is the same. When I extract the bootloader.iso file the same error occurs. what could it be? Can you help me extract these files? I am attaching the bootloader file of moto g7 river, if you can help me I will be immensely grateful.
Click to expand...
Click to collapse
Hello,
you are right. I should have written down how I created the singleimage.bin file. I replaced the following files in the singleimage.bin from the river stock rom version: XT1962-6_RIVER_RETEU_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (loaded from: https://mirrors.lolinet.com/firmware/moto/river/official/RETEU/)
gpt.bin
And changed the index.xml to the right CPU 632
You might to play around with the board id if it do not work (board id="204"). I hope the programmer file is the same for the G7 (processor type is slightly different: Snapdragon 632 instead of 636).
Give it a try with attached blankflashRiver.zip
WinnieH said:
Hello,
you are right. I should have written down how I created the singleimage.bin file. I replaced the following files in the singleimage.bin from the river stock rom version: XT1962-6_RIVER_RETEU_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (loaded from: https://mirrors.lolinet.com/firmware/moto/river/official/RETEU/)
gpt.bin
And changed the index.xml to the right CPU 632
You might to play around with the board id if it do not work (board id="204"). I hope the programmer file is the same for the G7 (processor type is slightly different: Snapdragon 632 instead of 636).
Give it a try with attached blankflashRiver.zip
Click to expand...
Click to collapse
Thanks for the help. the Programmer file isn't the same. After to work arround and beat my head over and over on the wall, I've took my phone to an authorized Motorola. For my surprise, as my phone shows oem_lock, they accepted on warranty. LOL. Now it's on repair and I'll catch tomorrow or another. Thanks for all. Thumbs up!
Rooting with patch security agost 2019
Hello
does this method work for the security patch of august 1, 2019?
does it works in moto g7 power? or others ways that qualcomm port not send error
I tryed in windows 7x64,10x64 without response, it shows me an error port just every time, qualcom usb drivers are shows correct ,
I cant continues with the fastboot part, people any advice?
diegovmsouza said:
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
Click to expand...
Click to collapse
Greetings Winnieh !, thanks for all the time and good information that you post,
I have doubts I would appreciate some advice, I have a motorola g7 power (ocean) tha's in hardbrick mode, I have already installed the correct qualcom drivers, the com port recognizes my device, but I cannot get the file blankflash.bat to load the phone to the moment executing it gives me an error:
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 2.218] ReadFile() failed, GetLastError()=0
[ 11.019] ERROR: sahara_greet_device()->device_open()->error opening device
[ 11.019] Check qboot_log.txt for more details
[ 11.019] Total time: 11.019s
FAILED: qb_flash_singleimage()->sahara_greet_device()->device_open()->error open
ing device
I realize that the blankflash.bat for the motog7 + version (river)
based on the blankflash file that you attached
I extracted the bootloader.img files from the stockrom of the motog7 power (ocean) XT1955-2 XT1955-2_OCEAN_AMX_9.0_PPO29.80-79_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml , so also delete and add all the files to the singleimpt.bin file - the gpt.bin file from stock rom copy and replace the one I saw in singleimage.bin
what you notice that index.xml refers to as "cpu.name: msm8953"
it also appears the same in the gpt.bin file, finally with the new singleimage.bin file compiled try to run the blankflash.bat again
unsuccessfully....
Could you tell me what are the mistakes that I can't solve?
i'm not a programmer just a bad lucky pal. if by chance have you a blankflash.bat for ocean version?, i'll really appreciate
Thank you! for your time
Hi WinnieH, I have a similar problem with a Moto G7 Power, can you tell me how I can create a blankflash for my specific model?
Lupask said:
is it possible to restore previously unlocked phone to out-of-the-box software and behaviour? specifically I would like to get rid of the bootloader warning and verity disabled message at boot. I wouldn't mind locking again
Click to expand...
Click to collapse
I have this exact same situation. did you find a solution to it?
Finally UNBRICK NUBIA Z20 in QDL MODE.
1. Extract Required Files from Original ROM:
abl.elf
xbl.elf xbl
config.elf
tz.mbn
2 Create a folder and paste the Rom files and the two downloaded files. (firehose)
DOWNLOAD:
https://drive.google.com/file/d/1zlwKSX_MKK1b2QtTTSrIgzmUCrt9LcYg/view
3 Download an active version of Qfil and follow the video.
Here is the video demonstration of the processes:
https://drive.google.com/folderview?id=1inlHKYyh4V3O23iRjG-yauLfCxplCjTJ
VIDEO:
<Mod edit: Link removed>
4 Upon completion press the Power, volume down and volume up buttons for 15 seconds.
Voalaaaa.
note when using what qfil turn off the computer wifi.
This apply only if he has flashed a rom via twrp or via fastboot... but with reformated phone , messed up partition table and maybe wrong LUNs .... will not do the trick.
credits to friend: @demonical
I'm do mad I send it for repair now, I still don't know how you guys found those firehose file
RomanLeFrais said:
I'm do mad I send it for repair now, I still don't know how you guys found those firehose file
Click to expand...
Click to collapse
i can see that the programmer for the sdm855 and sdm855+ are the same (the firehose)
justo download that file , and with QFIL from tools -> partition manager , restore the abl.elf xbl.elf xbl_config.elf and tz.mbn from orginal rom!
Broken links.
All the links are broken.
Cheako said:
All the links are broken.
Click to expand...
Click to collapse
OK NOW
This looks suspicious! Looks like it's a violation of the GPL, files the size of boot.img and rescue.img are encrypted. The included executable is also obfuscated.
Cheako said:
This looks suspicious! Looks like it's a violation of the GPL, files the size of boot.img and rescue.img are encrypted. The included executable is also obfuscated.
Click to expand...
Click to collapse
theese are the orignal issued by ZTE - NUBIA files.....
P.P. where did you saw a boot.img or rescue.img .? in the post or archive there is none of them?!
demonical said:
theese are the orignal issued by ZTE - NUBIA files.....
P.P. where did you saw a boot.img or rescue.img .? in the post or archive there is none of them?!
Click to expand...
Click to collapse
In order to get around being a violation things like this should contain a script that pulls the offending content from ZTE. Failing that links to where these "original" files come from would be an olive branch. As is, it's illegal to distribute these files.
They are published publicly by nubia.
demonical said:
P.P. where did you saw a boot.img or rescue.img .? in the post or archive there is none of them?!
Click to expand...
Click to collapse
Identified by size. Assuming some form of encryption... A violation of the GPL unless you share the private keys used to construct the image.
Can someone please walk me through this? i accidentally booted with no os.
Lusorocaba said:
Finally UNBRICK NUBIA Z20 in QDL MODE.
I just need a walkthrough please my phone is corrupted and wont boot for anything just only goes to edl mode and i need help installing things and getting the right files.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nubia-z20/how-to/tool-nubia-z20-unbirck-tool-t4009227
This works in "boot the edload" mode
Please i need firehose file for nubia z20. My phone is blank. Nothing shows on the screen, but my pc somehow detects it as "Qualcomm HSD QD Loader 9008". I want to try QFIL. Please any other suggestions on how to solve this would be appreciated.
how i Download an active version of Qfil
[email protected] said:
Please i need firehose file for nubia z20. My phone is blank. Nothing shows on the screen, but my pc somehow detects it as "Qualcomm HSD QD Loader 9008". I want to try QFIL. Please any other suggestions on how to solve this would be appreciated.
Click to expand...
Click to collapse
There's a tutorial on this forum.
Lusorocaba said:
Finally UNBRICK NUBIA Z20 in QDL MODE.
1. Extract Required Files from Original ROM:
abl.elf
xbl.elf xbl
config.elf
tz.mbn
2 Create a folder and paste the Rom files and the two downloaded files. (firehose)
DOWNLOAD:
https://drive.google.com/file/d/1zlwKSX_MKK1b2QtTTSrIgzmUCrt9LcYg/view
3 Download an active version of Qfil and follow the video.
Here is the video demonstration of the processes:
https://drive.google.com/folderview?id=1inlHKYyh4V3O23iRjG-yauLfCxplCjTJ
VIDEO:
<Mod edit: Link removed>
4 Upon completion press the Power, volume down and volume up buttons for 15 seconds.
Voalaaaa.
note when using what qfil turn off the computer wifi.
This apply only if he has flashed a rom via twrp or via fastboot... but with reformated phone , messed up partition table and maybe wrong LUNs .... will not do the trick.
credits to friend: @demonical
Click to expand...
Click to collapse
Unable to find anything in links. Please help
Dear All,
My Lg G8 Stuck in Qualcomm Hs-USB QBLoader
I am trying to restore back My G8 Via QFIL Method but I Need rawprogram
After Extract KDZ Via Python, I manged to get gpt.bin (For List of gtp.bin please find the attachment)
By using the Extracted gpt.bin from KDZ I am not able to get the partition list
Can any one guide me the proper method to create Rawprogram & patch file to restore my phone
vikramanananda said:
Dear All,
My Lg G8 Stuck in Qualcomm Hs-USB QBLoader
I am trying to restore back My G8 Via QFIL Method but I Need rawprogram
After Extract KDZ Via Python, I manged to get gpt.bin (For List of gtp.bin please find the attachment)
By using the Extracted gpt.bin from KDZ I am not able to get the partition list
Can any one guide me the proper method to create Rawprogram & patch file to restore my phone
Click to expand...
Click to collapse
Well I think you still need the firehose unless you've got a modded so, butt if you can use the xiaomi firehose, I can't help you sorry. I would join the v40 telegram group and ask there (or v30)
i can create rawprogram for you if u send me extracted lg g8 firmware (extracted dz whole data)
If your LG g8 is completely empty you erased everything without raw program file you can restore it use netmsm method in xda
Hi,
Can anyone upload me a Scatter File for the ZTE Axon 11 MTK version works with the scatter file App from the store or SP flash tools
if anyone has a rom for SP Flash Tools or the vendor Partition img would be awesome since mine is broke or w/e
i will spend u a coffee for that minutes
i cant get a scatter file out of mine using mtk droid tool, do you know a fix for this?
error message says something like couldnt read file system.
extracted from the android 10 downgrade package on ztes website
about as close as i can get to a proper scatter file for now