Hello, I have a Moto G first generation, and when I was upgrading to kitkat he hung up and did not call more when put to load it flashes the LED and not out place and not enter into fastboot can help me?
Result MotoFlasher Tool
SYSTEM: Device Selected: Moto G v1, Android 4.4.2
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: < waiting for device >
OUTPUT: opening device: \\.\COM14
OUTPUT: OKAY [ 0.020s]
OUTPUT: greeting device for command mode
OUTPUT: OKAY [ 0.001s]
OUTPUT: identifying device
OUTPUT: ...serial = 0x236D843
OUTPUT: ...chip-id = 0x800 (MSM8226)
OUTPUT: ...chip-rev = 0x0
OUTPUT: ...sv-sbl = 0x0
OUTPUT: OKAY [ 0.006s]
OUTPUT: finding files
OUTPUT: ...programmer = programmer.mbn
OUTPUT: ...singleimage = singleimage.bin
OUTPUT: OKAY [ 0.017s]
OUTPUT: validating files
OUTPUT: OKAY [ 0.026s]
OUTPUT: switching to download mode
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for image downloading
OUTPUT: OKAY [ 0.002s]
OUTPUT: sending programmer
OUTPUT: OKAY [ 0.042s]
OUTPUT: flashing singleimage
OUTPUT: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT:
OUTPUT:
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
Motorola Moto G
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Moto G Q&A, Help & Troubleshooting
Good luck!
KaHJonas said:
Hello, I have a Moto G first generation, and when I was upgrading to kitkat he hung up and did not call more when put to load it flashes the LED and not out place and not enter into fastboot can help me?
Result MotoFlasher Tool
SYSTEM: Device Selected: Moto G v1, Android 4.4.2
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: < waiting for device >
OUTPUT: opening device: \\.\COM14
OUTPUT: OKAY [ 0.020s]
OUTPUT: greeting device for command mode
OUTPUT: OKAY [ 0.001s]
OUTPUT: identifying device
OUTPUT: ...serial = 0x236D843
OUTPUT: ...chip-id = 0x800 (MSM8226)
OUTPUT: ...chip-rev = 0x0
OUTPUT: ...sv-sbl = 0x0
OUTPUT: OKAY [ 0.006s]
OUTPUT: finding files
OUTPUT: ...programmer = programmer.mbn
OUTPUT: ...singleimage = singleimage.bin
OUTPUT: OKAY [ 0.017s]
OUTPUT: validating files
OUTPUT: OKAY [ 0.026s]
OUTPUT: switching to download mode
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for image downloading
OUTPUT: OKAY [ 0.002s]
OUTPUT: sending programmer
OUTPUT: OKAY [ 0.042s]
OUTPUT: flashing singleimage
OUTPUT: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT:
OUTPUT:
Click to expand...
Click to collapse
You can't enter fastboot? Can you enter bootloader mode?
...
itouchables said:
You can't enter fastboot? Can you enter bootloader mode?
Click to expand...
Click to collapse
No!:crying:
Related
can someone help me ?my moto g XT1033(AS)flashed to be a brick.
my PC sys is win8.1 update,link moto g just like this:
Qualcomm HS-USB QDLoader 9008(COM5)
excuse my poor english,i'm a guy must use goagent to link to XDA...:crying:
Checkout this: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
dedeep said:
Checkout this: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
thank u！but it was not work。。。just like this：
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x2621621
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.006s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.004s]
validating files
OKAY [ 0.001s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
OKAY [ 0.010s]
flashing singleimage
ReadFile() failed, error=5
FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
or like this：
opening device: \\.\COM3
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 2.336s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
How to ？thank u！
dedeep said:
Checkout this: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
NOW，I know that，the only thing i can do now is just wait for MBM-CI，5.0 official。
thank you very much！
Can you boot into recovery mode or all that you get is a blank screen?
Can you post a photo of the cellphone screen?
Cheers!
Hey,
I have a huge problem with my phone right now. When I made a software update from 4.4.2 to 4.4.4 my phone shutted down while being in recovery and installing the new software. It shutted down, because the battery was low.
So now if I connect my phone to my computer, my computer detects it as Qualcomm HS-USB QDLoader 9008 (COM6).
I already tried this: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
But when I open the flash-blank.bat I get this message: FAILED (blank-flash:greet-device:error reading packet)
The whole log:
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
Is there any hope to get it back to life?
Did you try This
Hit THANKS if I helped you!
@LasseWolpmann00 after you blank-flash you should be able to flash Stock ROM via fastboot
I'm having the same problems,. I think it has something to do with the MBM-CI of Lollipop.
I flash XT1032 Firmware on my XT1031 device,and It's on 9008 mode(QHSUSB_BULK),and i try this,It failed!
Code:
C:\Users\Andy\Desktop\blankflash\blankflash>qboot.exe blank-flash
opening device: \\.\COM10
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.016s]
identifying device
...serial = 0x34F16F6
...chip-id = 0x801 (MSM8626)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.016s]
finding files
...programmer = programmer_8626.mbn
...singleimage = singleimage_8626.bin
OKAY [ -0.000s]
validating files
OKAY [ 0.016s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
OKAY [ 0.016s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
:crying::crying::crying:.Who can help me?
Hello friends , I saw that forum several people are crying for MOTO G with hard brick , plus my MOTO G xt1033 different happened I was in 4.3 GPE and updated it to 4.4 and eventually bricked already tried every way to refresh it more up now nothing .
Sorry My English , im Brazillian
This is the error I get after trying flasher the bootloader already tried with 4.3 and 4.4 more is always the same mistake
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: FAILED (blank-flash:greet-device:error reading packet)
The phone (XT1031, 16GB, Republic Wireless, 4.4.4) is low use and nothing different was done the day it developed the problem. It worked Monday, on Wednesday it flashed indicator and the screen wouldn't power. It was hard-powered off (held power) and it wouldn't turn on again. The computer does not detect it. I have installed the 64-bit driver for my Windows 7 and am attempting to 'blank-flash' without success. Can anyone assist? Attached is the log. Thanks in advance.
C:\Users\Test\Desktop\blankflash>qboot.exe blank-flash
opening device: \\.\COM3
OKAY [ 0.016s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x3598E90
...chip-id = 0x801 (MSM8626)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.016s]
finding files
...programmer = programmer_8626.mbn
...singleimage = singleimage_8626.bin
OKAY [ 0.031s]
validating files
OKAY [ -0.000s]
switching to download mode
OKAY [ 0.016s]
greeting device for image downloading
OKAY [ 0.016s]
sending programmer
OKAY [ 0.047s]
flashing singleimage
Target LOG: Open multi failed, unknown error
Target ERROR: 7 - Open multi failed, unknown error
FAILED (sdl-transfer-image:send-image:sdl-open-multi:target error)
Anyone? Can anyone supply a copy of the corrupted file? Ideas? Any help would be appreciated.
Have a look here: http://forum.xda-developers.com/moto-g/development/guide-qhsusb-dload-workaround-t3182477
I have a moto g XT-1033 8GB running with 4.4.4 kitkat while installing system software update onit become hard brick. The computer recognize it as a Qualcomm device but I get a Blank-Flash Reading error("after blank flash at 12.14 hrs dt.24/7/2016
C:\Users\SrinivasaRao\Desktop\blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM11
OKAY [ 0.016s]
greeting device for command mode
OKAY [ 0.016s]
identifying device
...serial = 0x2FDF6F7
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.036s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.016s]
validating files
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.016s]
greeting device for image downloading
OKAY [ 0.016s]
sending programmer
OKAY [ 0.016s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error reading packet)
C:\Users\SrinivasaRao\Desktop\blankflash\blankflash>pause
Press any key to continue . . . reading device"). I have tried with the blank-flash PL.GIVE a SOLUTION FOR RESTORATION.
by bsrao npalli , [email protected]
Hello and thank you for using XDA Assist,
please create an account and ask in our Android Q&A section:
Moto G Q&A, Help & Troubleshooting
The experts there should be able to help you.
Best regards & good luck
Trafalgar Square from XDA Assist