Hi, mi moto G suddently dead... i will try to share the history
Suddently my moto g don't start after doing a downgrade, only if i plug on my pc show a driver (qhsusb_bulk) on xda very people have this problem so i download the qualcomm drivers... in the firmware folder for my stock phone, have some things (...)\mbm\blankflash
so i run blankflash.bat and my phone now go to the fastboot :victory:
but show as locked, they dont let me flash nothing and i can't unlock, my imei is 00000000000000000000
and don't start (Failed to initialize partition table)
anyone can help me?
here some pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after 30 attempts using the same method (via fastboot) the same firmware the same pc. the phone reboot bootloader and show unlocked, let me flash all the system and work good ._. really i don't know what is going on...
but works :highfive:
EDIT:
yes, work using the .bat on 4.4.2 not 4.3 so the problem is the bootloader who i can't downgrade... maybe i make a guide to save the phone
EDIT2:
found the problem, never, NEVER flash the .mbn files on the firmware folder, only flash motoboot who take care of these flash files
I've had my shares of problems with that mbn files myself.
And after I was searching more things about them - I did notice that Moto X users have the same problems. The thing is that once you upgrade those files, you can't downgrade them.
moto g bricked
hi, i'm sorry, but i need help urgently. I unlocked the bootloader and flashed an international firmware so i can update to 4.4.2, since kitkat is not available in my country yet. then i tried to root my phone using superboot-windows.bat, and when the phone restarted it showd the moto logo, but it faded to black. so i turned it off, but now it doesn't turn on. is there a way to turn it on via adb or fastboot from windows?
please help i'm panicking...
darkeingel said:
I've had my shares of problems with that mbn files myself.
And after I was searching more things about them - I did notice that Moto X users have the same problems. The thing is that once you upgrade those files, you can't downgrade them.
Click to expand...
Click to collapse
u cant downgrade them until you blank-flash the bootloader... the problem is you really dont need to flash the .mbn files because motoboot file do that and is downgradable
cancheritos said:
hi, i'm sorry, but i need help urgently. I unlocked the bootloader and flashed an international firmware so i can update to 4.4.2, since kitkat is not available in my country yet. then i tried to root my phone using superboot-windows.bat, and when the phone restarted it showd the moto logo, but it faded to black. so i turned it off, but now it doesn't turn on. is there a way to turn it on via adb or fastboot from windows?
please help i'm panicking...
Click to expand...
Click to collapse
view if in the pc show as qhsusb_bulk and i will explain how to unbrick
open multi failed
hi everytime i tried the blank-flash.bat it shows this log:
from Boss442 to XDA
opening device: \\.\COM40
OKAY [ 0.002s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM40
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM40
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM40
OKAY [ 0.004s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM40
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM40
OKAY [ 0.002s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM40
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM40
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.974s]
identifying device
...serial = 0x1D18785
...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.002s]
switching to download mode
OKAY [ 0.006s]
greeting device for image downloading
OKAY [ 0.004s]
sending programmer
OKAY [ 0.013s]
flashing singleimage
Target LOG: Open multi failed, unknown error
Target ERROR: 7 - Open multi failed, unknown error
Failed to open multi image, status = 7
FAILED (sdl-transfer-image:send-image:sdl-open-multi:error opening multi image)
Presione una tecla para continuar . . .
someone can help me?
Boss442 said:
after 30 attempts using the same method (via fastboot) the same firmware the same pc. the phone reboot bootloader and show unlocked, let me flash all the system and work good ._. really i don't know what is going on...
but works :highfive:
EDIT:
yes, work using the .bat on 4.4.2 not 4.3 so the problem is the bootloader who i can't downgrade... maybe i make a guide to save the phone
EDIT2:
found the problem, never, NEVER flash the .mbn files on the firmware folder, only flash motoboot who take care of these flash files
Click to expand...
Click to collapse
Did you get back you data(like photoes、music)?Please tell me because I'm facing the same problem.Thank you!
gavinft said:
Did you get back you data(like photoes、music)?Please tell me because I'm facing the same problem.Thank you!
Click to expand...
Click to collapse
The data is formatted when you clean userdata partition
Enviado desde mi Moto G mediante Tapatalk
I hope it will be solved soon.
Minervamc said:
I hope it will be solved soon.
Click to expand...
Click to collapse
i forgot to mark as solved, sorry
will be lesson in here.......
i have problem...boot loop on flash cm11
Boss442 said:
i forgot to mark as solved, sorry
Click to expand...
Click to collapse
No problem.
xkorex said:
hi everytime i tried the blank-flash.bat it shows this log:
from Boss442 to XDA
opening device: \\.\COM40
OKAY [ 0.002s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM40
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM40
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM40
OKAY [ 0.004s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM40
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM40
OKAY [ 0.002s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM40
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM40
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.974s]
identifying device
...serial = 0x1D18785
...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.002s]
switching to download mode
OKAY [ 0.006s]
greeting device for image downloading
OKAY [ 0.004s]
sending programmer
OKAY [ 0.013s]
flashing singleimage
Target LOG: Open multi failed, unknown error
Target ERROR: 7 - Open multi failed, unknown error
Failed to open multi image, status = 7
FAILED (sdl-transfer-image:send-image:sdl-open-multi:error opening multi image)
Presione una tecla para continuar . . .
someone can help me?
Click to expand...
Click to collapse
Did you get your problem sloved?I've met the familar error "FAILED (sdl-transfer-image:send-image:sdl-open-multi:error reading packet)".What did you do next?
gavinft said:
Did you get your problem sloved?I've met the familar error "FAILED (sdl-transfer-image:send-image:sdl-open-multi:error reading packet)".What did you do next?
Click to expand...
Click to collapse
Same problem here. My Moto G is dead
Hello !!! Some solution to problem moto g ?
Boss442 said:
Hi, mi moto G suddently dead... i will try to share the history
Suddently my moto g don't start after doing a downgrade, only if i plug on my pc show a driver (qhsusb_bulk) on xda very people have this problem so i download the qualcomm drivers... in the firmware folder for my stock phone, have some things (...)\mbm\blankflash
so i run blankflash.bat and my phone now go to the fastboot :victory:
but show as locked, they dont let me flash nothing and i can't unlock, my imei is 00000000000000000000
and don't start (Failed to initialize partition table)
anyone can help me?
here some pics:
Click to expand...
Click to collapse
do you have MBM_CI files? as i can see by your moto g bootlaoder version which is 41.19. correct me if i wrong... how did you flashed i mean there is no such solution for Lollipop, how did you do it? if you have solution why don't you share it with others?
@sahir1993 - V41.19 is the Bootloader version included with GPE 5.1. It's available as motoboot.img in the GPE 5.1 Factory Firmware Images.
Hello @Boss442
Can you explain better how do you unbrick your moto g i got the same problem with mine, you can pm me and we can speak on spanish.
Enviado desde mi XT1063 mediante Tapatalk
lost101 said:
@sahir1993 - V41.19 is the Bootloader version included with GPE 5.1. It's available as motoboot.img in the GPE 5.1 Factory Firmware Images.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
see this you 'll know what i'm asking for?
AYUDAAA
Hola!
Cada vez que ejecuto el archivo blankflash.bat me dice: "FAILED <sdl-transfer-image:send-image:sdl-open-multi:error reading packet>" y no puedo reestablecer el bootloader
Ayuda por favor
Moto G 1032 :crying:
Hello,
I tried to update my xt1033 from GPE 4.4.2 to 4.4.4, it didnt boot. My bootloader was bricked.
I tried the moto flasher , to flash the bootloader, I got this message.
Any solutions?
**** BASIC INFORMATION ****
SYSTEM: Aplication Started at: 12-12-14 04:48
SYSTEM: OS: Microsoft Windows NT 6.1.7601 Service Pack 1
ASSEMBLY: MotoFlasher Version: 1.6.1.1
WARNING: No Python 2.7.x detected on "C:\Python27", Moto X flashing Disabled
****DETECTION STARTED:****
OUTPUT*: \\.\COM5 "Qualcomm HS-USB QDLoader 9008 (COM5)"
OUTPUT*:
OUTPUT:
SYSTEM: Device Selected: Moto G v1, Android 4.4.2
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: FAILED (blank-flash:device-open:serial-open:could not open device)
Press your power button for 10 second before perform a blank-flash. Do it every time you want to blank-flash. Make sure you choose 4.4.4 MBM-CI.
damnedivan said:
Press your power button for 10 second before perform a blank-flash. Do it every time you want to blank-flash. Make sure you choose 4.4.4 MBM-CI.
Click to expand...
Click to collapse
Thanks man, I got through that obstacle, now I get this error :/
OUTPUT*: switching to download mode
OUTPUT*: OKAY [ 0.001s]
OUTPUT*: greeting device for image downloading
OUTPUT*: OKAY [ 0.001s]
OUTPUT*: sending programmer
OUTPUT*: OKAY [ 0.014s]
OUTPUT*: flashing singleimage
OUTPUT*: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT*:
OUTPUT:
anirudhbs1996 said:
Thanks man, I got through that obstacle, now I get this error :/
OUTPUT*: switching to download mode
OUTPUT*: OKAY [ 0.001s]
OUTPUT*: greeting device for image downloading
OUTPUT*: OKAY [ 0.001s]
OUTPUT*: sending programmer
OUTPUT*: OKAY [ 0.014s]
OUTPUT*: flashing singleimage
OUTPUT*: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT*:
OUTPUT:
Click to expand...
Click to collapse
Were you on Lollipop before 4.4.2?
Myrtana said:
Were you on Lollipop before 4.4.2?
Click to expand...
Click to collapse
I tried switching to it, but I failed.
Should I wait for the stock lollipop images?
Or is there another solution to this?
anirudhbs1996 said:
I tried switching to it, but I failed.
Should I wait for the stock lollipop images?
Or is there another solution to this?
Click to expand...
Click to collapse
I guess we should wait now
anirudhbs1996 said:
I tried switching to it, but I failed.
Should I wait for the stock lollipop images?
Or is there another solution to this?
Click to expand...
Click to collapse
We have the same problem, we need to wait for 5.0 MBM-CI. Maybe the new release of Motoflasher will be on January.
damnedivan said:
We have the same problem, we need to wait for 5.0 MBM-CI. Maybe the new release of Motoflasher will be on January.
Click to expand...
Click to collapse
Oh, thanks for helping me out man, I'll try to go the the Motorola service center and make up some sob story to see if they'll replace it.
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?
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
Is my moto g xt1032 dead?
i started an systemupdate on my device not really reading what im clicking on, but it started to update.
the little android was lying there and the update goes on
when i wanted to look for progress after a while the moto g was black
nothing worked
i think the battery went down and the update couldnt complete
the only thing is that the led is blinking for a while when i put it on usb cable to load the battery, but after hours of loading nothing happens
can someone tell me how to turn it on again?
Try this: http://forum.xda-developers.com/showpost.php?p=63831563&postcount=2
lost101 said:
Try this: http://forum.xda-developers.com/showpost.php?p=63831563&postcount=2
Click to expand...
Click to collapse
i tried all types of button pressing but nothing works
so after reading many posts on different forums i came to jtag
and i tried this : http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
but Motorola qboot utility v2.4 only shows me this message:
opening device: \\.\COM3
OKAY [ -0.000s]
greeting device for command mode
OKAY [ 0.000s]
identifying device
...serial = 0x1F48A61
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.000s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.000s]
validating files
OKAY [ 0.000s]
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)
Click to expand...
Click to collapse
These may help: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 - but if your Bootloader has been updated then there is no working solution at this time.
lost101 said:
These may help: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 - but if your Bootloader has been updated then there is no working solution at this time.
Click to expand...
Click to collapse
fine that people are READING my posts^^
its the same link ive already posted