Related
Method tested and used with succes by @kalyansundhar on xt1795
Thanks for his detailed tutorial for unbrick the phones!
https://forum.xda-developers.com/showpost.php?p=76747247&postcount=258
Also please read the post's after that before posting your question
can be already answered to it
Tutorial for using Windows 7(language Brasilian & English, Thanks to @caikehenrique)
becouse flashing process can be done on Windows too
Thanks to @Thi_os
i made a video presentation to help the users wich dont
know how to do it
video for users with windows OS
video for extracting the.tar.gz archive in windows
sorry for my english
Oreo 8.1 mmcblk0.img thanks to @meltbanana
Nougat 7.1 mmncblk0.img xt1794(102-49-8) with md5-code by @hanshu43
Nougat 7.1 mmncblk0.img xt1795 with md5-code and tool to verify it
Thanks to @echo92 for providing md5-code of a working file
Tips & tricks!
The BEST method to flash the sdcard with mmcbk0.img file is to use LINUX!
Windows user have no need to install Linux in pc, you can run Linux from a bootable usb-stik or pendrive by 8Gb at least
0)put the moto g5s in wall charger till finish flashing sdcard to be charged on boot test!
1) run linux, preferable cinnamon or mate versions of linux Mint or Ubuntu(for ubuntu dont use LTS version)
2)insert the sdcard in pc or card reader and opend "Disks" apk
3)in "Disks"apk select sdcard and you will see the sdcard partitions
4) press "-" to delete the partition(delete al partitions if are more than one)
5)press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6)press "Play"button to mount the sdcard, look to see what path sdcard have(/dev/sd??) the and close the "Disks"apk
7)go to Desktop, opend "Computer" and navigate to the location when the img file is extracted(mmcblk0.img)
8)opend the window where img file is with root(right click on window and select "opend as root")
9)in root window opend the Terminal(right click on window and select "opend terminal")
no need to type "su" in terminal, it have already root
10)type in terminal the comand writed below and dont forget to eliminate that "1" from the sdcard path,
that "1"can make the differnce betwen phone boot or not!!!!!
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal aply that comand:
dd bs=4M if=mmcblk0.img of=/dev/sdb status=progress oflag=sync
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal aply that comand:
dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
and flashing process should start
when it finish, test the sdcard in phone and it should boot!
IF you get an size error of the sdcard in terminal you have to change the sdcard and try again!
This is the last edit of sdcard flashing tutorial, i cant make better than that!!
Thankyou!
thanks bro! i have my device hard bricked,but device manager detects it as "quectel QDLoader 9008" but not Qulacomm dloader husb 9008 now what to do ?
pardhav said:
thanks bro! i have my device hard bricked,but device manager detects it as "quectel QDLoader 9008" but not Qulacomm dloader husb 9008 now what to do ?
Click to expand...
Click to collapse
i resume you flashed a wrong image files.
did you try to use blankflash with montana image files?
:/
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
Marceloaps said:
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
Click to expand...
Click to collapse
Thankyou very much for your report!
can you provide the qboot_log.txt saved to chech it?
also can you try the singleimage.bin atached?
rename it from singleimage.bin.txt to singleimage.bin(delete .txt from name)
Thankyou!
here
**** Log buffer [000001] 2018-03-19_14:40:38 ****
[ -0.000] Opening device: \\.\COM3
[ -0.000] Detecting device
[ 4.032] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.032] Check qboot_log.txt for more details
[ 4.032] Total time: 4.032s
[ 4.032]
[ 4.032] qboot version 3.40
[ 4.032]
[ 4.032] DEVICE {
[ 4.032] name = "\\.\COM3",
[ 4.032] flags = "0x64",
[ 4.032] addr = "0x22FE6C",
[ 4.032] api.bnr = "0x3A2FE8",
[ 4.032] }
[ 4.032]
[ 4.032]
[ 4.032] Backup & Restore {
[ 4.032] num_entries = 0,
[ 4.032] restoring = "false",
[ 4.032] backup_error = "not started",
[ 4.032] restore_error = "not started",
[ 4.032] }
[ 4.032]
**** Log buffer [000001] 2018-03-19_14:41:06 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.049] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.049] Check qboot_log.txt for more details
[ 4.049] Total time: 4.049s
[ 4.049]
[ 4.049] qboot version 3.40
[ 4.049]
[ 4.049] DEVICE {
[ 4.049] name = "\\.\COM3",
[ 4.049] flags = "0x64",
[ 4.049] addr = "0x22FE6C",
[ 4.049] api.bnr = "0x372FE8",
[ 4.049] }
[ 4.049]
[ 4.049]
[ 4.049] Backup & Restore {
[ 4.049] num_entries = 0,
[ 4.049] restoring = "false",
[ 4.049] backup_error = "not started",
[ 4.049] restore_error = "not started",
[ 4.049] }
[ 4.049]
**** Log buffer [000001] 2018-03-19_14:51:30 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.047] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.047] Check qboot_log.txt for more details
[ 4.047] Total time: 4.047s
[ 4.047]
[ 4.047] qboot version 3.40
[ 4.047]
[ 4.047] DEVICE {
[ 4.047] name = "\\.\COM3",
[ 4.047] flags = "0x64",
[ 4.047] addr = "0x22FE6C",
[ 4.047] api.bnr = "0x7D2FE8",
[ 4.047] }
[ 4.047]
[ 4.047]
[ 4.047] Backup & Restore {
[ 4.047] num_entries = 0,
[ 4.047] restoring = "false",
[ 4.047] backup_error = "not started",
[ 4.047] restore_error = "not started",
[ 4.047] }
[ 4.047]
**** Log buffer [000001] 2018-03-19_15:11:44 ****
[ -0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.007] Total time: 4.008s
[ 4.051]
[ 4.051] qboot version 3.40
[ 4.051]
[ 4.051] DEVICE {
[ 4.051] name = "\\.\COM3",
[ 4.051] flags = "0x64",
[ 4.051] addr = "0x22FE6C",
[ 4.051] api.bnr = "0x582FE8",
[ 4.051] }
[ 4.051]
[ 4.051]
[ 4.051] Backup & Restore {
[ 4.051] num_entries = 0,
[ 4.051] restoring = "false",
[ 4.051] backup_error = "not started",
[ 4.051] restore_error = "not started",
[ 4.051] }
[ 4.051]
Marceloaps said:
**** Log buffer [000001] 2018-03-19_14:40:38 ****
[ 4.051] }
[ 4.051]
Click to expand...
Click to collapse
Thankyou, is not very clear!
did you test the singleimage.bin posted above?
help me
Unable to download file
call me on facebook and pass qboot.log
https://www.facebook.com/
---------- Post added at 08:06 PM ---------- Previous post was at 08:04 PM ----------
help me :/ :crying:
sorry for all!
the file dont work
i will keep looking for a working file
Thankyou!
also thanks to @Marceloaps for patience to test and test and test.......
Pls help me ;(
Can u upload new singleimage.bin to any filehost? or help me differently please.
**** Log buffer [000001] 2018-03-19_22:15:26 ****
[ -0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.053] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.053] Check qboot_log.txt for more details
[ 4.053] Total time: 4.055s
[ 4.053]
[ 4.053] qboot version 3.40
[ 4.053]
[ 4.053] DEVICE {
[ 4.053] name = "\\.\COM10",
[ 4.053] flags = "0x64",
[ 4.053] addr = "0x61FE5C",
[ 4.053] api.bnr = "0x2F92E28",
[ 4.053] }
[ 4.053]
[ 4.053]
[ 4.053] Backup & Restore {
[ 4.053] num_entries = 0,
[ 4.053] restoring = "false",
[ 4.053] backup_error = "not started",
[ 4.053] restore_error = "not started",
[ 4.053] }
[ 4.053]
**** Log buffer [000001] 2018-03-19_22:28:48 ****
[ 0.000] Opening device: \\.\COM10
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 79 (0x4f)
[ 0.016] ...cpu.sn = 868549579 (0x33c503cb)
[ 0.016] Opening singleimage
[ 0.187] ERROR: error opening singleimage
[ 0.187] Check qboot_log.txt for more details
[ 0.187] Total time: 0.266s
[ 0.187]
[ 0.187] qboot version 3.40
[ 0.187]
[ 0.187] DEVICE {
[ 0.187] name = "\\.\COM10",
[ 0.187] flags = "0x64",
[ 0.187] addr = "0x61FE5C",
[ 0.187] sahara.current_mode = "3",
[ 0.187] api.buffer = "0x3245020",
[ 0.187] cpu.serial = "868549579",
[ 0.187] cpu.id = "79",
[ 0.187] cpu.sv_sbl = "1",
[ 0.187] api.bnr = "0x2EF2FE8",
[ 0.187] }
[ 0.187]
[ 0.187]
[ 0.187] Backup & Restore {
[ 0.187] num_entries = 0,
[ 0.187] restoring = "false",
[ 0.187] backup_error = "not started",
[ 0.187] restore_error = "not started",
[ 0.187] }
[ 0.187]
**** Log buffer [000001] 2018-03-19_22:29:02 ****
[ 0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.047] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.047] Check qboot_log.txt for more details
[ 4.047] Total time: 4.049s
[ 4.047]
[ 4.047] qboot version 3.40
[ 4.047]
[ 4.047] DEVICE {
[ 4.047] name = "\\.\COM10",
[ 4.047] flags = "0x64",
[ 4.047] addr = "0x61FE5C",
[ 4.047] api.bnr = "0x2F02EE0",
[ 4.047] }
[ 4.047]
[ 4.047]
[ 4.047] Backup & Restore {
[ 4.047] num_entries = 0,
[ 4.047] restoring = "false",
[ 4.047] backup_error = "not started",
[ 4.047] restore_error = "not started",
[ 4.047] }
[ 4.047]
I'm counting on you.
It was nothing, so we improved more and we moved slowly, I need to be here.
anyone, has a OTAupdate saved?
to share it here please!
Thankyou!
vaserbanix said:
After many searching's, i think i managed to create a singleimage.bin for montana
it is made on xt1793 modell and it (maybe) can work on all montana version's
i cant test it! sorry, my phone is not bricked and hope to do not brick it in near future
so the singleimage.bin file is not tested
you will do test on your own risk
please think twice or more many times before act
Download the "Blankflash" zip, (link removed)
extract it in your pc(Windows or Linux)
in Windows opend the blankflash folder and do double-click on blank-flash.bat
a cmd window will opend and it will wait for your device to be conected
connect the phone and the process should start
in Linux opend the blankflash folder, opend terminal and tipe:./blank-flash.sh and hit enter
after you will see "<waiting for device>" line, connetct the phone and the process should start
hope singleimage.bin to be good for all versions of montana and to work helping you to restore the phone
What is a Forum without users?
Thankyou!
in case of ERRors please post along your coment a screenshot with cmd or terminal
or copy-paste all lines from it here
Thankyou again!
Click to expand...
Click to collapse
Where is the files why linked removed haven't tried yet. Is there any other file.
ASHDCBZ said:
Where is the files why linked removed haven't tried yet. Is there any other file.
Click to expand...
Click to collapse
i removed the link becouse the file is corupted or not valid, blankflash cant open it!
i have to get other method to get singleimage.bin for montana
Thankyou!
Sent from my Moto G5s using Tapatalk
vaserbanix said:
i removed the link becouse the file is corupted or not valid, blankflash cant open it!
i have to get other method to get singleimage.bin for montana
Thankyou!
Sent from my Moto G5s using Tapatalk
Click to expand...
Click to collapse
ok thank you for trying pls. find any other way as service center not helping and not doing anything about it.
ASHDCBZ said:
ok thank you for trying pls. find any other way as service center not helping and not doing anything about it.
Click to expand...
Click to collapse
I'm working on that.
Thankyou!
Sent from my Moto G5s using Tapatalk
Good work and thanks. My device I left for maintenance in a specialized store. Unfortunately they called me saying it could not be fixed. So as soon as I search I will participate in the forum and help develop it to help others. Leave your work as soon as I will part of it.
hey... plz help me i m alo facing this problem my device moto g5s got hard brickes
xdanielmonster said:
Can u upload new singleimage.bin to any filehost? or help me differently please.
**** Log buffer [000001] 2018-03-19_22:15:26 ****
[ -0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.053] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.053] Check qboot_log.txt for more details
[ 4.053] Total time: 4.055s
[ 4.053]
[ 4.053] qboot version 3.40
[ 4.053]
[ 4.053] DEVICE {
[ 4.053] name = "\\.\COM10",
[ 4.053] flags = "0x64",
[ 4.053] addr = "0x61FE5C",
[ 4.053] api.bnr = "0x2F92E28",
[ 4.053] }
[ 4.053]
[ 4.053]
[ 4.053] Backup & Restore {
[ 4.053] num_entries = 0,
[ 4.053] restoring = "false",
[ 4.053] backup_error = "not started",
[ 4.053] restore_error = "not started",
[ 4.053] }
[ 4.053]
**** Log buffer [000001] 2018-03-19_22:28:48 ****
[ 0.000] Opening device: \\.\COM10
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 79 (0x4f)
[ 0.016] ...cpu.sn = 868549579 (0x33c503cb)
[ 0.016] Opening singleimage
[ 0.187] ERROR: error opening singleimage
[ 0.187] Check qboot_log.txt for more details
[ 0.187] Total time: 0.266s
[ 0.187]
[ 0.187] qboot version 3.40
[ 0.187]
[ 0.187] DEVICE {
[ 0.187] name = "\\.\COM10",
[ 0.187] flags = "0x64",
[ 0.187] addr = "0x61FE5C",
[ 0.187] sahara.current_mode = "3",
[ 0.187] api.buffer = "0x3245020",
[ 0.187] cpu.serial = "868549579",
[ 0.187] cpu.id = "79",
[ 0.187] cpu.sv_sbl = "1",
[ 0.187] api.bnr = "0x2EF2FE8",
[ 0.187] }
[ 0.187]
[ 0.187]
[ 0.187] Backup & Restore {
[ 0.187] num_entries = 0,
[ 0.187] restoring = "false",
[ 0.187] backup_error = "not started",
[ 0.187] restore_error = "not started",
[ 0.187] }
[ 0.187]
**** Log buffer [000001] 2018-03-19_22:29:02 ****
[ 0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.047] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.047] Check qboot_log.txt for more details
[ 4.047] Total time: 4.049s
[ 4.047]
[ 4.047] qboot version 3.40
[ 4.047]
[ 4.047] DEVICE {
[ 4.047] name = "\\.\COM10",
[ 4.047] flags = "0x64",
[ 4.047] addr = "0x61FE5C",
[ 4.047] api.bnr = "0x2F02EE0",
[ 4.047] }
[ 4.047]
[ 4.047]
[ 4.047] Backup & Restore {
[ 4.047] num_entries = 0,
[ 4.047] restoring = "false",
[ 4.047] backup_error = "not started",
[ 4.047] restore_error = "not started",
[ 4.047] }
[ 4.047]
I'm counting on you.
Click to expand...
Click to collapse
plz reply me please its too urgent I lost my device I mean device hard bricked I need a working blank flash file for my montana sory for my bad English but I m very worried about my device plz someone help me anyway.....plz reply me on [email protected] its been too long there is no solution I found on internet ....plz help mee guys to get my device backon track...its hard bricked and only a notification light is blinking ...I can nor go to fastboot mode as well.....plz help and rplyyy..than you
For few days i have to fix some my heathy problems, my possibilities right now are limited(i have only the phone with me).
When I'll go back home, I'll continue to try to get a working singleimage.bin for unbrick the phones(or others method if exist)
Sorry and thanks for understanding!
Also please dont add other post's under this for now so everyboby can see it!
Thankyou again!
XT1792
> Unlocked bootloader + twrp + root
> accidentally removed stock rom by twrp
> installing new stock rom by adb fastboot
> BRICKED
> only selfie flash light blinkin when I put on charger or USB
> I installed qualcom drivers and worked, tried others blankflash
but I'm stucked and can't revive G5S by those blankflash
> Please, help me
Hi,
Last night, my Moto G6's battery died during an update. I put it on the charger and the LED came on flashing and did that overnight.
This morning, the light had stopped flashing, which means the battery is no longer discharged completely, but the phone isn't booting. No bootloader, so this is clearly a hardbrick. I plugged my phone into my computer, and it came up as "Qualcomm HS-USB QDLoader 9008". I've heard of this, but I've never personally dealt with it. So, I tried to flash a blankflash and I'm having trouble with it. The log below is the farthest I've gotten:
Code:
**** Log buffer [000001] 2019-03-01_16:42:26 ****
[ -0.000] Opening device: \\.\COM4
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 154 (0x9a)
[ 0.006] ...cpu.sn = 2061065993 (0x7ad95f09)
[ 0.006] Opening singleimage
[ 0.007] Loading package
[ 0.010] ...filename = singleimage.pkg.xml
[ 0.013] Loading programmer
[ 0.013] ...filename = programmer.mbn
[ 0.014] Sending programmer
[ 1.018] ERROR: sahara_download()->IO error
[ 1.019] Check qboot_log.txt for more details
[ 1.019] Total time: 1.021s
[ 1.020]
[ 1.020] qboot version 3.40
[ 1.020]
[ 1.020] DEVICE {
[ 1.020] name = "\\.\COM4",
[ 1.020] flags = "0x64",
[ 1.020] addr = "0x61FE4C",
[ 1.020] sahara.current_mode = "0",
[ 1.020] api.buffer = "0x135A020",
[ 1.020] cpu.serial = "2061065993",
[ 1.020] cpu.id = "154",
[ 1.020] cpu.sv_sbl = "0",
[ 1.020] cpu.name = "MSM8953",
[ 1.020] storage.type = "eMMC",
[ 1.020] sahara.programmer = "programmer.mbn",
[ 1.020] api.bnr = "0x843EE8",
[ 1.020] }
[ 1.020]
[ 1.020]
[ 1.020] Backup & Restore {
[ 1.020] num_entries = 0,
[ 1.020] restoring = "false",
[ 1.020] backup_error = "not started",
[ 1.020] restore_error = "not started",
[ 1.020] }
[ 1.020]
Can someone help me out with this?
Hello friend!
I have exactly the same problem.
I can't flash BlankFlash_PPS29.26.bat for my XT1925-5, the entire chain of loaders.
Returns exactly the same I/o error.
After talking with wise people, I realized that blankflash can't flash the original bootloader, since its version is later than the version that is installed in the internal memory of the phone.
I tried experimenting with blankflash.bat for different devices with the same security updates.(Motorola Moto G5Plus, Moto G6 Plus,Moto G7 Plus, etc.) But to no avail.
Here you need the help of a smart encoder that can "patch" our SingleImage.bin for our firmware version and updated security system.
Please email me if you have any results on our common problem.
JoeGatto said:
Hi,
Can someone help me out with this?
Click to expand...
Click to collapse
Faced a similar problem.I will be glad of any help.
My Moto G6 Ali got hardbricked also plzzz help anyone solved it or have blankflash HE
Do anyone have a proper solution
My device -XT1925-13:crying::crying::crying::crying::crying::crying:
Hello guys, I bought a motorola g6 some time ago. It was rooted. I went back to rom stock to remove root and installed it normally, but the phone updated, and after didn't turn on anymore, even pressing the power and volume buttons. It only turns on a led light when plugged into the computer.. I already followed the steps from the topic below, but my phone is G6, not G6 Plus
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
This is the blankflash error
*** Log buffer [000001] 2019-08-17_19:01:29 ****
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 154 (0x9a)
[ 0.005] ...cpu.sn = 2421618069 (0x9056f595)
[ 0.005] Opening singleimage
[ 0.052] Loading package
[ 0.056] ...filename = singleimage.pkg.xml
[ 0.058] Loading programmer
[ 0.058] ...filename = programmer.mbn
[ 0.059] Sending programmer
[ 1.063] ERROR: sahara_download()->IO error
[ 1.063] Check qboot_log.txt for more details
[ 1.063] Total time: 1.063s
[ 1.064]
[ 1.064] qboot version 3.40
[ 1.064]
[ 1.064] DEVICE {
[ 1.064] name = "\\.\COM5",
[ 1.064] flags = "0x64",
[ 1.064] addr = "0x61FE4C",
[ 1.064] sahara.current_mode = "0",
[ 1.064] api.buffer = "0x1400020",
[ 1.064] cpu.serial = "2421618069",
[ 1.064] cpu.id = "154",
[ 1.064] cpu.sv_sbl = "0",
[ 1.064] cpu.name = "MSM8953",
[ 1.064] storage.type = "eMMC",
[ 1.064] sahara.programmer = "programmer.mbn",
[ 1.064] api.bnr = "0x1345FF8",
[ 1.064] }
[ 1.064]
[ 1.064]
[ 1.064] Backup & Restore {
[ 1.064] num_entries = 0,
[ 1.064] restoring = "false",
[ 1.064] backup_error = "not started",
[ 1.064] restore_error = "not started",
[ 1.064] }
[ 1.064]
I don't know if an upgrade could damage the motherboard.
I really hope you can help me, I'm realy sad, new phone
davigiolo said:
Hello guys, I bought a motorola g6 some time ago. It was rooted. I went back to rom stock to remove root and installed it normally, but the phone updated, and after didn't turn on anymore, even pressing the power and volume buttons. It only turns on a led light when plugged into the computer.. I already followed the steps from the topic below, but my phone is G6, not G6 Plus
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
This is the blankflash error
*** Log buffer [000001] 2019-08-17_19:01:29 ****
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 154 (0x9a)
[ 0.005] ...cpu.sn = 2421618069 (0x9056f595)
[ 0.005] Opening singleimage
[ 0.052] Loading package
[ 0.056] ...filename = singleimage.pkg.xml
[ 0.058] Loading programmer
[ 0.058] ...filename = programmer.mbn
[ 0.059] Sending programmer
[ 1.063] ERROR: sahara_download()->IO error
[ 1.063] Check qboot_log.txt for more details
[ 1.063] Total time: 1.063s
[ 1.064]
[ 1.064] qboot version 3.40
[ 1.064]
[ 1.064] DEVICE {
[ 1.064] name = "\\.\COM5",
[ 1.064] flags = "0x64",
[ 1.064] addr = "0x61FE4C",
[ 1.064] sahara.current_mode = "0",
[ 1.064] api.buffer = "0x1400020",
[ 1.064] cpu.serial = "2421618069",
[ 1.064] cpu.id = "154",
[ 1.064] cpu.sv_sbl = "0",
[ 1.064] cpu.name = "MSM8953",
[ 1.064] storage.type = "eMMC",
[ 1.064] sahara.programmer = "programmer.mbn",
[ 1.064] api.bnr = "0x1345FF8",
[ 1.064] }
[ 1.064]
[ 1.064]
[ 1.064] Backup & Restore {
[ 1.064] num_entries = 0,
[ 1.064] restoring = "false",
[ 1.064] backup_error = "not started",
[ 1.064] restore_error = "not started",
[ 1.064] }
[ 1.064]
I don't know if an upgrade could damage the motherboard.
I really hope you can help me, I'm realy sad, new phone
Click to expand...
Click to collapse
I believe you can enter download mode, or fastboot mode by doing the following:
1. First of all, turn off your phone – press power button and then select “power off”.
2. The USB cord must be near you, as a connection between your device and your computer must be established at some point.
3. Press and hold the volume down button on your Moto G.
4. While pressing the mentioned key also press Power button.
5. Now connect your Moto G with your computer by plugging in the USB cable.
6. Download mode / bootloader mode should now be installed – some drivers might be installed automatically.
From here you can reflash the stock rom. As long as your bootloader is unlocked, its ALMOST impossible to hardbrick your phone.
davigiolo said:
Hello guys, I bought a motorola g6 some time ago. It was rooted. I went back to rom stock to remove root and installed it normally, but the phone updated, and after didn't turn on anymore, even pressing the power and volume buttons. It only turns on a led light when plugged into the computer.. I already followed the steps from the topic below, but my phone is G6, not G6 Plus
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
This is the blankflash error
*** Log buffer [000001] 2019-08-17_19:01:29 ****
[ -0.000] Opening device: \.\COM5
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 154 (0x9a)
[ 0.005] ...cpu.sn = 2421618069 (0x9056f595)
[ 0.005] Opening singleimage
[ 0.052] Loading package
[ 0.056] ...filename = singleimage.pkg.xml
[ 0.058] Loading programmer
[ 0.058] ...filename = programmer.mbn
[ 0.059] Sending programmer
[ 1.063] ERROR: sahara_download()->IO error
[ 1.063] Check qboot_log.txt for more details
[ 1.063] Total time: 1.063s
[ 1.064]
[ 1.064] qboot version 3.40
[ 1.064]
[ 1.064] DEVICE {
[ 1.064] name = "\.\COM5",
[ 1.064] flags = "0x64",
[ 1.064] addr = "0x61FE4C",
[ 1.064] sahara.current_mode = "0",
[ 1.064] api.buffer = "0x1400020",
[ 1.064] cpu.serial = "2421618069",
[ 1.064] cpu.id = "154",
[ 1.064] cpu.sv_sbl = "0",
[ 1.064] cpu.name = "MSM8953",
[ 1.064] storage.type = "eMMC",
[ 1.064] sahara.programmer = "programmer.mbn",
[ 1.064] api.bnr = "0x1345FF8",
[ 1.064] }
[ 1.064]
[ 1.064]
[ 1.064] Backup & Restore {
[ 1.064] num_entries = 0,
[ 1.064] restoring = "false",
[ 1.064] backup_error = "not started",
[ 1.064] restore_error = "not started",
[ 1.064] }
[ 1.064]
I don't know if an upgrade could damage the motherboard.
I really hope you can help me, I'm realy sad, new phone
Click to expand...
Click to collapse
Sahara is the g7....
What the heck are talking g6 stuff for? Wrong phone, firmware, forum, everything.
madbat99 said:
Sahara is the g7....
What the heck are talking g6 stuff for? Wrong phone, firmware, forum, everything.
Click to expand...
Click to collapse
What the heck... ??
1. G7 is called "river"
2. There isn't any Moto device which is called "sahara"
3. Sahara is a GUI tool for working with devices in Qualcomm DLOAD mode (bricked devices)!! So the "sahara_downloader" doesn't stand in any relationship to the Moto G7!!!
WoKoschekk said:
What the heck... ??
1. G7 is called "river"
2. There isn't any Moto device which is called "sahara"
3. Sahara is a GUI tool for working with devices in Qualcomm DLOAD mode (bricked devices)!! So the "sahara_downloader" doesn't stand in any relationship to the Moto G7!!!
Click to expand...
Click to collapse
Yep, I misread "Sahara"
There are some g7's called "lake(plus) and River"
My mistake.
Same problem
davigiolo said:
Hello guys, I bought a motorola g6 some time ago. It was rooted. I went back to rom stock to remove root and installed it normally, but the phone updated, and after didn't turn on anymore, even pressing the power and volume buttons. It only turns on a led light when plugged into the computer.. I already followed the steps from the topic below, but my phone is G6, not G6 Plus
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
This is the blankflash error
*** Log buffer [000001] 2019-08-17_19:01:29 ****
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 154 (0x9a)
[ 0.005] ...cpu.sn = 2421618069 (0x9056f595)
[ 0.005] Opening singleimage
[ 0.052] Loading package
[ 0.056] ...filename = singleimage.pkg.xml
[ 0.058] Loading programmer
[ 0.058] ...filename = programmer.mbn
[ 0.059] Sending programmer
[ 1.063] ERROR: sahara_download()->IO error
[ 1.063] Check qboot_log.txt for more details
[ 1.063] Total time: 1.063s
[ 1.064]
[ 1.064] qboot version 3.40
[ 1.064]
[ 1.064] DEVICE {
[ 1.064] name = "\\.\COM5",
[ 1.064] flags = "0x64",
[ 1.064] addr = "0x61FE4C",
[ 1.064] sahara.current_mode = "0",
[ 1.064] api.buffer = "0x1400020",
[ 1.064] cpu.serial = "2421618069",
[ 1.064] cpu.id = "154",
[ 1.064] cpu.sv_sbl = "0",
[ 1.064] cpu.name = "MSM8953",
[ 1.064] storage.type = "eMMC",
[ 1.064] sahara.programmer = "programmer.mbn",
[ 1.064] api.bnr = "0x1345FF8",
[ 1.064] }
[ 1.064]
[ 1.064]
[ 1.064] Backup & Restore {
[ 1.064] num_entries = 0,
[ 1.064] restoring = "false",
[ 1.064] backup_error = "not started",
[ 1.064] restore_error = "not started",
[ 1.064] }
[ 1.064]
I don't know if an upgrade could damage the motherboard.
I really hope you can help me, I'm realy sad, new phone
Click to expand...
Click to collapse
I have de same problem, only blinking led when you plug it to usb, nothing else.
Did you figure out how to solve it?
nibx said:
I have de same problem, only blinking led when you plug it to usb, nothing else.
Did you figure out how to solve it?
Click to expand...
Click to collapse
Hello dear happy owners of Moto G6 bricks.
Please, would you be so kind as to accept me into your team of elite owners of useless nutcrackers based on the Motorola Moto G6.
My XT1925-5 device was also hardbricked, after upgrading to Android 9.0 Pie and installing the latest security updates.
Also, when trying to flash the blankflash_PPS29.26 utility.bat receive
error: Sahara Download IO Error.
Email me if there are any positive results when getting a smartphone memory dump and creating a new blankflash for the latest OTA.
This is my contact email ([email protected]) if there are people willing to collaborate to write a new Blank Flash together.
ZulC_Silence said:
Hello dear happy owners of Moto G6 bricks.
Please, would you be so kind as to accept me into your team of elite owners of useless nutcrackers based on the Motorola Moto G6.
My XT1925-5 device was also hardbricked, after upgrading to Android 9.0 Pie and installing the latest security updates.
Also, when trying to flash the blankflash_PPS29.26 utility.bat receive
error: Sahara Download IO Error.
Email me if there are any positive results when getting a smartphone memory dump and creating a new blankflash for the latest OTA.
This is my contact email ([email protected]) if there are people willing to collaborate to write a new Blank Flash together.
Click to expand...
Click to collapse
Flash the latest RETAIL (PPSS29.55...) from here: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ with RSD Lite 6.2.4, this happened to me days ago with a XT1925-2 RETLA and this was the way to recover it.
pdloud said:
Flash the latest RETAIL (PPSS29.55...) from here: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ with RSD Lite 6.2.4, this happened to me days ago with a XT1925-2 RETLA and this was the way to recover it.
Click to expand...
Click to collapse
I do not understand, please tell me the algorithm of actions?
I have the official firmware for XT1925-5 for Android 9 Pie ,you can get SBL1 from it.bin, SingleImage.Bin.
And redo BlankFlash_from_29. 26 for my firmware version?
ZulC_Silence said:
I do not understand, please tell me the algorithm of actions?
I have the official firmware for XT1925-5 for Android 9 Pie ,you can get SBL1 from it.bin, SingleImage.Bin.
And redo BlankFlash_from_29. 26 for my firmware version?
Click to expand...
Click to collapse
I have an XT1295-2 RETLA and there is no official Pie firmware for this model, so what happened to me was that I've received an update and the OTA bricked my device, what I did was:
1.- Downloaded de latest RETAIL Pie firmware from the link I've posted before.
2.- Flashed this firmware with RSDLite (I've tried to flash it manually but no luck).
3.- Nothing else, the device booted without problems.
pdloud said:
I have an XT1295-2 RETLA and there is no official Pie firmware for this model, so what happened to me was that I've received an update and the OTA bricked my device, what I did was:
1.- Downloaded de latest RETAIL Pie firmware from the link I've posted before.
2.- Flashed this firmware with RSDLite (I've tried to flash it manually but no luck).
3.- Nothing else, the device booted without problems.
Click to expand...
Click to collapse
thank you for your answer.
ZulC_Silence said:
I do not understand, please tell me the algorithm of actions?
I have the official firmware for XT1925-5 for Android 9 Pie ,you can get SBL1 from it.bin, SingleImage.Bin.
And redo BlankFlash_from_29. 26 for my firmware version?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/ali/official/RETRU/
XT1925-5_ALI_RETRU_9.0_PPSS29.55-37-7-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Thats the image you want to flash. As long as you can still boot into fastboot mode you can recover.
theseeker2654 said:
https://mirrors.lolinet.com/firmware/moto/ali/official/RETRU/
XT1925-5_ALI_RETRU_9.0_PPSS29.55-37-7-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Thats the image you want to flash. As long as you can still boot into fastboot mode you can recover.
Click to expand...
Click to collapse
I can 't boot in any way at all.
Fastboot doesn 't see the device.
It is only defined as Qualcomm HS-USB QDloader 9008.
Neither fastboot nor Qfill.exe does not see the device.
Here you need a working blank flash.bin, specifically for my version of the SOFTWARE (PPSS29.55-37-4-3), which will be kindly merged with Motorola's technical servers .
Otherwise, there is no way to restore the loader Chains.
Hallo Moto Users
Last few days, it was a nightmare to find some ready and working solution on hardbricked Motorola. After 5 or 6 days finally bootloader screen appeared
Just to mention - until one week ago I was just and only Samsung user for last 6-7 years. So I clearly admit I am a n00b regarding other brands/systems. (probably someone who is PRO user for ages, would solve that 'at the fly', however I digged whole entire Internet and found only ONE TIP how-to).
To be clear - below I share a link to the orginal poster of the method which resurrected my Moto - all I have done was to read, understand and follow...
https://www.reddit.com/r/MotoG/comments/k73n66
I am pretty sure this could also be a way for many Motorola models. Hope it will help someone in the future to save some valuable time (and money as the local worshops have 99% predictions that it is DEAD MOTHERBOARD signs and evidence!).
Enjoy the New Started Year Ladies and Gents!
my moto g52 is not starting (hardbrick), I tried the method informed but the flahs always gives an error
my model is xt2221-2 RETBR
LOG qboot:
*** Log buffer [000001] 2022-09-05_22:21:13 ****
[ 0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 0.004] ...cpu.id = 440 (0x1b8)
[ 0.004] ...cpu.sn = 233431865 (0xde9e339)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.007] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.009] Sending programmer
[ 11.192] ERROR: sahara_download()->IO error
[ 11.193] Check qboot_log.txt for more details
[ 11.194] Total time: 11.195s
[ 11.194]
[ 11.194] qboot version 3.86
[ 11.194]
[ 11.194] DEVICE {
[ 11.194] name = "\\.\COM3",
[ 11.194] flags = "0x64",
[ 11.194] addr = "0x62FD54",
[ 11.194] sahara.current_mode = "0",
[ 11.194] api.buffer = "0x2BD9020",
[ 11.194] cpu.serial = "233431865",
[ 11.194] cpu.id = "440",
[ 11.194] cpu.sv_sbl = "0",
[ 11.194] cpu.name = "SM_DIVAR",
[ 11.194] storage.type = "UFS",
[ 11.194] sahara.programmer = "programmer.elf",
[ 11.194] api.bnr = "0xFF1E50",
[ 11.194] }
[ 11.194]
[ 11.194]
[ 11.194] Backup & Restore {
[ 11.194] num_entries = 0,
[ 11.194] restoring = "false",
[ 11.194] backup_error = "not started",
[ 11.194] restore_error = "not started",
[ 11.194] }
[ 11.194]
cmd message
[ 0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 0.004] ...cpu.id = 440 (0x1b8)
[ 0.004] ...cpu.sn = 233431865 (0xde9e339)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.007] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.009] Sending programmer
[ 11.192] ERROR: sahara_download()->IO error
[ 11.193] Check qboot_log.txt for more details
[ 11.194] Total time: 11.195s
FAILED: qb_flash_singleimage()->sahara_download()->IO error
I had my moto G6 in storage as I had upgraded and no longer needed it till today. I pulled it out and noticed it wouldn't turn on. I figured it was dead and plugged it in when I was promptly greeted with a fastboot menu and logs complaining the hab image couldn't be verified. Tried rebooting a couple times hoping for a fluke and alas, my luck is not good.
So I followed the recommendation on the screen and got the lovely Lenovo Rescue and Smart Assistant to reprogram my phone. It tried the first time and my phone ended up with a black screen and white LED blinking at 1Hz. After a time the Lenovo tool gave up and errored out. I held the power button for a minute and I was able to get back to the fastboot screen and figured I would just try again.
I tried a second time and it progressed further into the process before it did the same thing again. I am now with a phone that does little more than blink the white LED. But I do see that the CPU is in a EDL mode and enumerates as a COM port. I found this thread for the G6 Plus and was able to get some luck but the blankflash errored out (not surprised as it was for the plus and not the 'regular' G6).
[ULTIMATE GUIDE] How To Unbrick your Moto G6 Plus
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY AND IT'S NOT 100% GUARANTEED TO WORK. WORKED ON MY G6 PLUS (XT1926-7) AND SOME OTHER USERS ON WINDOWS. THINGS YOU WILL NEED: Motorola and Qualcomm Drivers; BlankFlash file; Stock ROM; STEPS: PART...
forum.xda-developers.com
I spent some time online and found this link:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
I downloaded the PDS29.118-15-11-14 and gave that a try. I produced some results but ultimately ended in an error.
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 154 (0x9a)
[ 0.004] ...cpu.sn = 1862624572 (0x6f05653c)
[ 0.004] Opening singleimage
[ 0.012] Loading package
[ 0.015] ...filename = singleimage.pkg.xml
[ 0.017] Loading programmer
[ 0.018] ...filename = programmer.mbn
[ 0.018] Sending programmer
[ 0.265] Handling things over to programmer
[ 0.266] Identifying CPU version
[ 0.268] Waiting for firehose to get ready
[ 60.504] Waiting for firehose to get ready
[121.584] ...MSM8953 unknown
[121.584] Determining target secure state
[121.586] Waiting for firehose to get ready
[184.162] ...secure = no
[184.177] Waiting for firehose to get ready
[244.227] Configuring device...
[244.229] Waiting for firehose to get ready
[306.781] Waiting for firehose to get ready
[370.379] Waiting for firehose to get ready
[431.463] Waiting for firehose to get ready
[494.029] ERROR: do_package()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[494.029] Check qboot_log.txt for more details
[494.029] Total time: 494.032s
[494.029]
[494.029] qboot version 3.40
[494.029]
[494.029] DEVICE {
[494.029] name = "\\.\COM3",
[494.029] flags = "0x64",
[494.029] addr = "0x61FE4C",
[494.029] sahara.current_mode = "0",
[494.029] api.buffer = "0x802020",
[494.029] cpu.serial = "1862624572",
[494.029] cpu.id = "154",
[494.029] cpu.sv_sbl = "0",
[494.029] cpu.name = "MSM8953",
[494.029] storage.type = "eMMC",
[494.029] sahara.programmer = "programmer.mbn",
[494.029] module.firehose = "0x6A1D30",
[494.029] cpu.ver = "0",
[494.029] cpu.vername = "unknown",
[494.029] api.bnr = "0x6AAAA8",
[494.029] }
[494.029]
[494.030]
[494.030] Backup & Restore {
[494.030] num_entries = 0,
[494.030] restoring = "false",
[494.030] backup_error = "not started",
[494.030] restore_error = "not started",
[494.030] }
[494.030]
I think the exact blankflash I am looking for might be called: PPS29.118_15_11_16_cid18
The reason I suspect this is because the image that the Lenovo tool was trying to download and install to the phone has a full name of:
ALI_AMZ_PPS29.118_15_11_16_cid18_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
Does anyone happen to have any suggestions? Would be cool to get this phone back from the dead, no matter what ROM ends up on it.
Thanks in advance