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 !
Related
Hello guys, my Owens-Mobile Moto E4 Plus XT1776 msm8920 Was bricked now, and when I connect to my pc , it only Show it is qcom 9008, seems that I need blankflash to save my phone , so deos anyone who can find it, please help me , thx .
Heres a blankflash I used to recover my E4 Plus (XT1775). Took forever to find it. Pretty sure it'll work for the XT1776 as well, but I'm not positive and I don't have one to test on. Let me know if this helps.
XT1775 Blankflash
TheGuysGuysGuy said:
Heres a blankflash I used to recover my E4 Plus (XT1775). Took forever to find it. Pretty sure it'll work for the XT1776 as well, but I'm not positive and I don't have one to test on. Let me know if this helps.
XT1775 Blankflash
Click to expand...
Click to collapse
C:\Users\Sagar\Desktop\New folder\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM3
OKAY [ 46.779s]
greeting device for command mode
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
FAILED (blank-flash:device-open:serial-open:error reading device configuration)
aminsagar1 said:
C:\Users\Sagar\Desktop\New folder\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM3
OKAY [ 46.779s]
greeting device for command mode
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
FAILED (blank-flash:device-open:serial-open:error reading device configuration)
Click to expand...
Click to collapse
Did you only try the one time? And was COM3 the correct port? I had to try multiple times, with different connection states. Meaning starting the flash prior to plugging in, immediately after plugging in, etc...
C:\Users\Sagar\Desktop\blankflash>.\qboot.exe blank-flash
< waiting for device >
opening device: \\.\COM3
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x62BDCC0E
...chip-id = 0x86
...chip-rev = 0x0
...sv-sbl = 0x1
OKAY [ 0.016s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.016s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
FAILED (blank-flash:sahara-transfer-image:send-image:error reading packet)
C:\Users\Sagar\Desktop\blankflash>pause
Press any key to continue . . .
next probleme
not match cpu my create cpu msm8920 blankflash please help
[email protected]:~/Desktop/bflash$ sudo ./qboot blank-flash
< waiting for device >
opening device: /dev/ttyUSB0
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.000s]
identifying device
...serial = 0x42294519
...chip-id = 0x86
...chip-rev = 0x0
...sv-sbl = 0x1
OKAY [ 0.001s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.000s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
FAILED (blank-flash:sahara-transfer-image:send-image:error reading packet)
Getting this exact same error under linux and windows (flashing to xt1775). Are you sure this was the correct zip you used for your phone?
could someone revive the phone?
TheGuysGuysGuy said:
Heres a blankflash I used to recover my E4 Plus (XT1775). Took forever to find it. Pretty sure it'll work for the XT1776 as well, but I'm not positive and I don't have one to test on. Let me know if this helps.
XT1775 Blankflash
Click to expand...
Click to collapse
I got the phone to detect but when I run the command "blank-flash" it just loops saying "opening device: \\.\COM4 OKAY [ 10.038s] greeting device for command mode" do you have any idea what to do?
Jay De Anda said:
I got the phone to detect but when I run the command "blank-flash" it just loops saying "opening device: \\.\COM4 OKAY [ 10.038s] greeting device for command mode" do you have any idea what to do?
Click to expand...
Click to collapse
That blank flash supposedly just gets ya to fastboot capability, try flashing correct device firmware via fastboot
bcrichster said:
That blank flash supposedly just gets ya to fastboot capability, try flashing correct device firmware via fastboot
Click to expand...
Click to collapse
Well, we can't flash anything until we can get it to fastboot mode...
What I meant was.. Try in terminal:
fastboot devices
Jay De Anda said:
Well, we can't flash anything until we can get it to fastboot mode...
Click to expand...
Click to collapse
Then see if you get an alphanumeric response.. If so, try using fastboot cmds to install your FW. If it succeeds, you'll get normal fastboot mode back and you can do whatever ya need
Sent from my Moto E (4) Plus using Tapatalk
bcrichster said:
What I meant was.. Try in terminal:
fastboot devicesThen see if you get an alphanumeric response.. If so, try using fastboot cmds to install your FW. If it succeeds, you'll get normal fastboot mode back and you can do whatever ya need
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
Nope, nothing... just says "waiting for any device"...
bcrichster said:
What I meant was.. Try in terminal:
fastboot devicesThen see if you get an alphanumeric response.. If so, try using fastboot cmds to install your FW. If it succeeds, you'll get normal fastboot mode back and you can do whatever ya need
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
man could you help ud making the file that gets in a sd card and the phone boots up in fastboot? ivee read that it can be only made in a good phone via twrp
TheGuysGuysGuy said:
Heres a blankflash I used to recover my E4 Plus (XT1775). Took forever to find it. Pretty sure it'll work for the XT1776 as well, but I'm not positive and I don't have one to test on. Let me know if this helps.
XT1775 Blankflash
Click to expand...
Click to collapse
Do you know where we can access current / past version of this file?
Thank you!
nosoycamachis said:
man could you help ud making the file that gets in a sd card and the phone boots up in fastboot? ivee read that it can be only made in a good phone via twrp
Click to expand...
Click to collapse
I'm considering it but actually kinda intimidated.. I've got a lot going on ATM with local natural disasters and afraid of not having a device for emergencies. Everyone's somehow getting their devices messed up and/or bricked just by the stock July update and I'm not sure why yet.. I've basically been running custom ROMs since March/April and haven't really touched stock since..
Please help
Hello, we really need that file for unbrick they phone pls do it for all the people that have the phone bricked. Sorry my bad english
bcrichster said:
I'm considering it but actually kinda intimidated.. I've got a lot going on ATM with local natural disasters and afraid of not having a device for emergencies. Everyone's somehow getting their devices messed up and/or bricked just by the stock July update and I'm not sure why yet.. I've basically been running custom ROMs since March/April and haven't really touched stock since..
Click to expand...
Click to collapse
Pls bcrichster we need that file pls help us
hhhfac2 said:
Pls bcrichster we need that file pls help us
Click to expand...
Click to collapse
We don't only need the file... Apparently we also need a modified USB cable to be able to communicate with our devices... But no one seems to want to help us...
Jay De Anda said:
We don't only need the file... Apparently we also need a modified USB cable to be able to communicate with our devices... But no one seems to want to help us...
Click to expand...
Click to collapse
But i read about a method to recover the phone by microsd. What do you know about that?
Tryng to root my device (XT1929-6), I bricked the phone. After installing the motorola device manager, i tried to blankflash the phone, but thats the log
Motorola qboot utility version 3.37
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 204 (0xcc)
[ 0.000] ...cpu.sn = 3748563624 (0xdf6e8aa8)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.016] Failed identify board. Wrong package?
[ 0.016] ERROR: error loading package
[ 0.016] Check qboot_log.txt for more details
[ 0.016] Total time: 0.031s
FAILED: qb_flash_singleimage()->error loading package
Please help! I am not 100% certain where this thread must to be, if I am wrong tell me.
And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..
Willy33 said:
And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..
Click to expand...
Click to collapse
I tried to use SuperSU zip file to root. I wasn't able to install TWRP, for installing supersu I used "fastboot boot TWRP.img" beacause the phone doesn't have a recovery partition. When i tried to install supersu, it returned "Unable to mount /vendor (busy)" (not full message beacause i don't have acces to the logs), then y tried to fix "vendor using the repair tool of twrp, and after the restart it was full bricked. Actually windows sometimes detects the device if you press power button and vol down, but it can't recognise the type of device.
Teto Balsámico said:
I tried to use SuperSU zip file to root. I wasn't able to install TWRP, for installing supersu I used "fastboot boot TWRP.img" beacause the phone doesn't have a recovery partition. When i tried to install supersu, it returned "Unable to mount /vendor (busy)" (not full message beacause i don't have acces to the logs), then y tried to fix "vendor using the repair tool of twrp, and after the restart it was full bricked. Actually windows sometimes detects the device if you press power button and vol down, but it can't recognise the type of device.
Click to expand...
Click to collapse
I don’t understand why it was to invent with su when a working method for getting root rights using magisk and even without twrp was already described here, but this is not the point ... you need to install the necessary drivers for blankflash and the phone is defined as Qualcomm 9008 , and after that start blankflash. But as I said earlier, there is no blankflash file yet, just for our phone.
Willy33 said:
And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..
Click to expand...
Click to collapse
Willy33 said:
I don’t understand why it was to invent with su when a working method for getting root rights using magisk and even without twrp was already described here, but this is not the point ... you need to install the necessary drivers for blankflash and the phone is defined as Qualcomm 9008 , and after that start blankflash. But as I said earlier, there is no blankflash file yet, just for our phone.
Click to expand...
Click to collapse
And how do i get those drivers? And where i can see how the computer recognises the mobile as Qualcomm 9008? just for the time being.
Internet spaces help very well))) it is enough to drive in Qualcomm 9008 and that's it. And to look naturally in the windows device manager.
and on YouTube you can even find instructions on how to properly install these drivers.
Willy33 said:
Internet spaces help very well))) it is enough to drive in Qualcomm 9008 and that's it. And to look naturally in the windows device manager.
and on YouTube you can even find instructions on how to properly install these drivers.
Click to expand...
Click to collapse
Thanks for your help!
I have the same problem. Could you fix the error?
Do I have to do something else for linux to detect my moto z3? Windows detects it without problem, but it always shows an error when reading the storage
Help..
E:\Descargas\qualkom dri>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.002] Opening device: \\.\COM4
[ 0.238] Detecting device
[ 0.248] ...cpu.id = 204 (0xcc)
[ 0.248] ...cpu.sn = 2761611797 (0xa49ada15)
[ 0.249] Opening singleimage
[ 0.594] Loading package
[ 0.603] ...filename = pkg.xml
[ 0.606] Loading programmer
[ 0.637] ...filename = programmer.elf
[ 0.638] Sending programmer
[ 0.832] Handling things over to programmer
[ 0.833] Identifying CPU version
[ 0.833] Waiting for firehose to get ready
[ 4.132] ...SDM636 1.0
[ 4.134] Determining target secure state
[ 4.137] ...secure = yes
[ 4.200] Configuring device...
[ 4.211] Flashing GPT...
[ 4.212] Flashing partition with gpt.bin
[ 4.221] Initializing storage
[ 4.300] ...blksz = 512
[ 4.521] Target NAK!
[ 4.521] ...ERROR: SDCC Error 29 (3)
[ 4.521] ...ERROR: Write Failed sector 0, size 48
[ 4.522] ...ERROR: Failed to write 1 slot 0, partition 0, start_sector 48 num_sectors 0, error 3
[ 4.522] ...Finished programming start_sector 48 and TotalSectorsToProgram 48
[ 4.522] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->lun_write()->storage_write()->firehose_do_fmt()->do_recipe()->NAK
[ 4.523] Check qboot_log.txt for more details
[ 4.524] Total time: 4.538s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->lun_write()->storage_write()->firehose_do_fmt()->do_recipe()->NAK
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
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.
Hello dear gurus.
Purchased a Motorola (Lenovo) moto G6 smartphone on the Anroid 8.0 Oreo platform.
Performed OTA security updates.After that, it was suggested to upgrade to Anrdroid 9.0 Pie.Updated.
Next, I installed a custom recovery (TeamWin Recovery Project (TWRP)) on a new loader,and created a backup system for this recovery.
Next, I tried to fill in a new custom (Amateur) firmware (ViperOS), but TWRP refused to install this firmware.
So I tried about 10 different firmware versions,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.
Currently, neither the recovery, nor the system,nor even the PBL,aboot, and SBL bootloader chain is running.
The only way 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) - a light brick.I need to restore the entire loader chain, starting with the SBL of the secondary loader.
For my device, there is a special utility BlankFlash_PPS29. 26 (see Attachment), which is in automatic mode when you start Blank_Flash.bat, re-marks MBR partitions, creates a partition table, and restores the entire chain of loaders.
But there is one significant "BUT", this utility completely refuses to re-request the chain of device loaders, giving an I/o error in the logs (see Attachment).
After talking with smart people from the forward, I realized that for a successful firmware of my device, the OTA security update is not suitable,what is in the utility later, and what is newer and more secure on the device and the singleimage configuration file.the bin located in this utility is not suitable.
If there are people who can write the correct script for .bash for my firmware and security version and embed it all directly into singleimage.bin, then please respond.
I live in Russia, technical support for our country is not working well,if someone has access to Motorola's technical servers , then write in private messages, you need a new blankflash.bin for the firmware version PPSS29.55-37-4-3.
I guarantee confidentiality and payment.
BlankFlash.zip and qfill_log.txt
Here's Blankflash.zip for firmware PPS29. 25 and part of the log where the I /o error is visible
Code:
**** Log buffer [000001] 2020-02-14_11:38:04 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 154 (0x9a)
[ 0.000] ...cpu.sn = 2887117897 (0xac15ec49)
[ 0.000] Opening singleimage
[ 0.109] Loading package
[ 0.109] ...filename = singleimage.pkg.xml
[ 0.125] Loading programmer
[ 0.125] ...filename = programmer.mbn
[ 0.125] Sending programmer
[ 1.141] ERROR: sahara_download()->IO error
[ 1.141] Check qboot_log.txt for more details
[ 1.141] Total time: 1.141s
Having the same error need blankflash HELPPPPPLZZZZZZZZZZZ
Actually after reading your thread I realized that my security version was June 2019
So is there any way that I can be helped
Security update-June 2019
Device-moto G6 XT1925-13
Android version-9
hardbrick
I need it too PPS29.55-37-7-2 for that compilation
hellotheresunnyhere said:
Actually after reading your thread I realized that my security version was June 2019
So is there any way that I can be helped
Security update-June 2019
Device-moto G6 XT1925-13
Android version-9
Click to expand...
Click to collapse
Not yet.Sorry.
Jose Moyano said:
I need it too PPS29.55-37-7-2 for that compilation
Click to expand...
Click to collapse
How are you doing on the road to recovery?
ZulC_Silence said:
How are you doing on the road to recovery?
Click to expand...
Click to collapse
without result