Good night ... I have a Moto g2 lte xt1078. it does not start, no fastboot, no booting... they tried to install lolipop and did root procedure. already tried several tutorials, as the blankflash, but without results. I removed the battery several times; Full battery; when connected to PC without battery the LED flashes once; all drivers installed. current driver Qualcomm HS-USB QDloader 9008. The result of the blankflash this in content below.
help please.
sorry bad english.
C:\Users\Claus\Desktop\blankflash_lollipop>.\qboot.exe blank-flash
opening device: \\.\COM9
OKAY [ 0.002s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x7B72F04
...chip-id = 0x805 (MSM8926)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer_8926.mbn
...singleimage = singleimage_8926.bin
OKAY [ 0.005s]
validating files
OKAY [ 0.001s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
OKAY [ 0.012s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
C:\Users\Claus\Desktop\blankflash_lollipop>pause
Pressione qualquer tecla para continuar. . .
tested: MBM-CI 4.3; 4.4.2; 4.4.4; 5.0.
It's the same error:
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
motherboard is dead.
Moto G 2014 xt1068/xt1069/xt1078
Is there any tool that can get the Moto G 2014 xt1068 / xt1069
/ Xt1078 hardblick in the development? if not I humbly ask that the group managed to get the g1 moto hardblick can also take other cell line motorola umm thanks to @ilikered for its beautiful job with the bike g1 parabens it stays that way and that can help us not only to me but to several people who are in the same situation , thanks
Hey, I've been trying to follow a guide on how to unbrick my Moto G but I keep getting the same error:
C:\Users\perdi\Desktop\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
OKAY [ 0.003s]
identifying device
...serial = 0x66CB552
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.009s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.006s]
validating files
OKAY [ 0.010s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
OKAY [ 0.013s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
C:\Users\perdi\Desktop\blankflash>pause
Press any key to continue . . .
Everything goes well until I have to do that, and I would like some help.
(The guide: http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788)
Thanks in advance.
opening device: \\.\COM14
OKAY [ 0.016s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x6A19B4B
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.016s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.031s]
validating files
OKAY [ 0.016s]
switching to download mode
OKAY [ 0.000s]
greeting device for image downloading
OKAY [ 0.016s]
sending programmer
OKAY [ 0.016s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
this is showing when i did blank flash ...
plz help!!!!!!!!!!!!
Welcome to the club.
zman01 said:
Welcome to the club.
Click to expand...
Click to collapse
plz suggest solution as soon as possible.............
For this i m very greatful to you
http://www.mobileunbrick.com/ contact them!, they can fix your Moto G2. Send them your model name(XT1068..) and send him your phone. Its located in India and costs ca. 10 Dollars for everything.
I bought a new Mainboard instead of this, because I didn't know from mobileunbrick.com.
Good Luck
EDIT: https://www.youtube.com/watch?v=WynBaVyW0oU
I am using QFIL to try and revive my X4, but I have no idea how to get into EDL mode when I cannot do anything with the device. Computer recognizes it when I plug it in as Quectel QDLoader 9008 in Ports, but that's it.
Any suggestions would be appreciated. I don't want to have to pay MOTO to fix it if possible.
I've exhausted every resource I have.
Thank you anyone that can help or at least point me in the right direction.\
EDIT: When I was eMMC Software Download app, phone shows in COM3 Download mode, but I need an XML file to flash with that tool and don't know how to get that.
I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?
Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?
DustArma said:
Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?
Click to expand...
Click to collapse
No, my power went out in the middle of fastboot flashing and screwed up all the partitions. I am stuck without the blankflash.. Thank you for replying to try to help.
christopher68369 said:
I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?
Click to expand...
Click to collapse
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.
johnjingle said:
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.
Click to expand...
Click to collapse
you can not take it to the Moto warranty? you do not have to know how the phone went blank...
bookworth said:
you can not take it to the Moto warranty? you do not have to know how the phone went blank...
Click to expand...
Click to collapse
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Bro! It's works! Thanks for blank-flash for my soft bricked moto x4.
O link não funciona
LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Please guy, this link not work! Help me Please. Thanks
silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
It does, if you follow his instructions stated after the link.
Consegui agora!
jhedfors said:
It does, if you follow his instructions stated after the link.
Click to expand...
Click to collapse
Thanks Very much! work perfectly
Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error:
**** Log buffer [000001] 2018-07-26_14:55:02 ****
[ 0.000] Opening device: \\.\COM6
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 172 (0xac)
[ 0.004] ...cpu.sn = 2293722822 (0x88b76ec6)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.007] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.196] Handling things over to programmer
[ 0.197] Identifying CPU version
[ 0.197] Waiting for firehose to get ready
[ 3.212] ...SDM630 1.0
[ 3.213] Determining target secure state
[ 3.215] ...secure = yes
[ 3.238] Configuring device...
[ 3.243] Flashing GPT...
[ 3.243] Flashing partition with gpt.bin
[ 3.247] Initializing storage
[ 4.421] Target NAK!
[ 4.421] ...ERROR: Failed to open the SDCC Device slot 0 partition 0
[ 4.422] ...ERROR: Failed to open the device 1 slot 0 partition 0
[ 4.423] ...INFO: Device type 1, slot 0, partition 0, error 0
[ 4.423] ...WARN: Get Info failed to open 1 slot 0, partition 0, error 0
[ 4.424] ...ERROR: Failed to get device info slot:0artition:0
[ 4.424] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 4.424] ...ERROR 14: Line 1283: HANDLE_STORAGE_INFO_FAILURE
[ 4.424] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 4.424] Check qboot_log.txt for more details
[ 4.425] Total time: 4.426s
[ 4.425]
[ 4.425] qboot version 3.86
[ 4.425]
[ 4.425] DEVICE {
[ 4.425] name = "\\.\COM6",
[ 4.425] flags = "0x144",
[ 4.425] addr = "0x62FD64",
[ 4.425] sahara.current_mode = "0",
[ 4.425] api.buffer = "0x2B15020",
[ 4.425] cpu.serial = "2293722822",
[ 4.425] cpu.id = "172",
[ 4.425] cpu.sv_sbl = "1",
[ 4.425] cpu.name = "SDM630",
[ 4.425] storage.type = "eMMC",
[ 4.425] sahara.programmer = "programmer.elf",
[ 4.425] module.firehose = "0x2A51630",
[ 4.425] api.firehose = "0xF2EF68",
[ 4.425] cpu.ver = "256",
[ 4.425] cpu.vername = "1.0",
[ 4.425] fh.max_packet_sz = "1048576",
[ 4.425] fh.storage_inited = "1",
[ 4.425] provisioning_may_hang = "true",
[ 4.425] }
[ 4.425]
silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
You mean you can't download ?
waltwittman1 said:
Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error: (log text omitted)
Click to expand...
Click to collapse
I got a similar error when I tried the blank-flash on my bricked Moto X4. @waltwittman1 please let me know if you find a solution.
serial_write() Error
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB1
[ 0.000] Detecting device
[ 21.382] ...cpu.id = 172 (0xac)
[ 21.382] ...cpu.sn = 4247084357 (0xfd255d45)
[ 21.382] Opening singleimage
[ 21.382] Loading package
[ 21.384] ...filename = pkg.xml
[ 21.385] Loading programmer
[ 21.385] ...filename = programmer.elf
[ 21.385] Sending programmer
[ 21.570] Handling things over to programmer
[ 21.570] Identifying CPU version
[ 21.570] Waiting for firehose to get ready
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error
ttyUSB Permissions Linux
mistryous said:
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error
Click to expand...
Click to collapse
While I was running as root on my Linux system, this was solved as an issue between the device showing up on /dev/ttyUSB0 initially. I set permissions correctly there, but it reconnects with VolDown+Power on /dev/ttyUSB1 which had limited permissions. While udev rules could solve it, I was lucky to catch the device correctly in time to manually change the permissions and have blankflash progress all the way through. [Upon further thought root should have solved this, so it is likely just an issue with how devices/permissions are set up on my system].
Owner trashed the blankflash file. Can anyone hook me up please?
Here you go.
luvcustom said:
Owner trashed the blankflash file. Can anyone hook me up please?
Click to expand...
Click to collapse
This is the one I use. This is my first post to the XDA forums so they prevented me from linking to my dropbox. So, replace the [dot] with a . and you should be good.
.dropbox [dot] com/s/3xi85sy207x3vs6/blankflash.zip?dl=0[/url]
Win 10 waiting for device message and nothing more.
and no 9008 port
moved
Hi all,
My girlfriend's Moto G6 XT1925-6 (purchased via Best Buy, never rooted/modded) got slow one day, I recommended rebooting and then it never came back. The only signs of life are that when plugged into a computer or charger. the white light blinks every second or so, and the phone shows up as the following USB device (port):
Qualcomm HS-USB QDLoader 9008 (COM4)
I have tried 3-4 different blankflash files numerous times (including the two from https://mirrors.lolinet.com/firmware/moto/ali/blankflash/) and always get an IO error. The phone would have been fully updated as of 11/1, it was being used on Cricket Wireless if that matters. Lenovo Moto Smart Assistant was no help unfortunately since the phone cannot boot into fastboot.
I tried again today since one 'fix' seemed to be to let the battery discharge. It was unplugged for ~5 days and no change.
Any other tips/tricks or am I SOL? She was somewhat due for an upgrade anyways, but thought I'd try one last time to look for other solutions.
Thanks!
timing is absolutely critical in EDL mode - i.e., you don't have long to start the flashing once you plug the USB cable in. sounds like you have the correct drivers, given that the phone shows up properly in device manager. try the following in quick succession:
0. plug the USB cable into the computer (not the phone, yet)
1. start the blankflash script from lolinet
2. depress and hold the power and volume_down buttons
3. connect the USB cable
4. script will do its magic (release the buttons) and reboot the phone to the bootloader
hope this helps!
armrbackthrsday said:
timing is absolutely critical in EDL mode - i.e., you don't have long to start the flashing once you plug the USB cable in. sounds like you have the correct drivers, given that the phone shows up properly in device manager. try the following in quick succession:
0. plug the USB cable into the computer (not the phone, yet)
1. start the blankflash script from lolinet
2. depress and hold the power and volume_down buttons
3. connect the USB cable
4. script will do its magic (release the buttons) and reboot the phone to the bootloader
hope this helps!
Click to expand...
Click to collapse
Exactly when are you supposed to release the buttons? No matter when I do, I get:
ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
Heat84 said:
Exactly when are you supposed to release the buttons? No matter when I do, I get:
ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
Click to expand...
Click to collapse
hmm, sounds like the blankflash script is not recognizing the correct COM port. does the device show up as "Qualcomm HS-USB QDLoader 9008" in device manager?
armrbackthrsday said:
hmm, sounds like the blankflash script is not recognizing the correct COM port. does the device show up as "Qualcomm HS-USB QDLoader 9008" in device manager?
Click to expand...
Click to collapse
I fixed that problem by rebooting the phone while qflash was running. Now I have a different error that you see below at 3. 485.
Code:
[ -0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 286 (0x11e)
[ 0.002] ...cpu.sn = 1010000641 (0x3c336301)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.009] ...filename = programmer.elf
[ 0.009] Sending programmer
[ 0.131] Handling things over to programmer
[ 0.131] Identifying CPU version
[ 0.131] Waiting for firehose to get ready
[ 3.213] ...SM_SAIPAN 2.0
[ 3.214] Determining target secure state
[ 3.219] ...secure = yes
[ 3.307] Configuring device...
[ 3.317] Skipping UFS provsioning as target is secure
[ 3.317] Configuring device...
[ 3.483] Flashing GPT...
[ 3.483] Flashing partition with gpt.bin
[ 3.485] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->find_first_package()->not found
[ 3.486] Check qboot_log.txt for more details
[ 3.486] Total time: 3.487s
[ 3.487]
[ 3.487] qboot version 3.86
[ 3.487]
[ 3.487] DEVICE {
[ 3.487] name = "\\.\COM11",
[ 3.487] flags = "0x144",
[ 3.487] addr = "0x28FD74",
[ 3.487] sahara.current_mode = "0",
[ 3.487] api.buffer = "0x2570020",
[ 3.487] cpu.serial = "1010000641",
[ 3.487] cpu.id = "286",
[ 3.487] cpu.sv_sbl = "0",
[ 3.487] cpu.name = "SM_SAIPAN",
[ 3.487] storage.type = "UFS",
[ 3.487] sahara.programmer = "programmer.elf",
[ 3.487] module.firehose = "0x24D1248",
[ 3.487] api.firehose = "0x67D948",
[ 3.487] cpu.ver = "512",
[ 3.487] cpu.vername = "2.0",
[ 3.487] fh.max_packet_sz = "1048576",
[ 3.487] fh.storage_inited = "1",
[ 3.487] }
[ 3.487]
I don't actually have to worry about this any more because I was tired of playing around and took the phone(a Motorola Edge plain 2020) back to Best Buy where I got it, and they couldn't fix it, but they did offer to exchange it for a new one. I chose an "open box" one that probably was returned the day after it was bought by the first owner for some stupid reason. I also got a $74 refund to even the exchange(I would've had to wait a week for a new one or choose a different make and/or model phone available in store otherwise). But don't let that stop you from offering a translation to this error message if you have one. I'm curious and you may help someone else.
Why would the developer of Qboot not have any documentation of what the error messages mean? What's the point of writing error messages if you don't tell anybody what they mean? Was that done out of arrogance or stupidity? Also, when it says to check qboot log for details, that BS. Everything you see during the flash attempt on screen is all you see in the log. Nothing more.
By the way if you're interested, I started a thread about my problem before I found this one: https://forum.xda-developers.com/t/...hard-hard-bricked-edge.4341829/#post-85717539
By the way 2: It seems to be a weird coincidence that you resurrected this thread almost a year after the last (and only) post at the SAME TIME I was having the same issue they were. Even though you didn't help me and I don't need the help anymore, you gotta admit that that's a little creepy. lol