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:
Related
First I apologize, my English is horrible.
Recently I installed the update OTA for the XT1033 Powered model on the site, However I was not very satisfied and returned to the KitKat. And I began to notice some strange things, was facing some problems in fastboot and my screen was also esquesita. I managed to return to the STOCK rom, tried to install the GPE to test the Flyme OS that's also available here on the site. Only after installing the GPE and the OTA update my device did not call more. And I began to receive the driver installation message HSUSb_BULK searched on the internet and saw that the problem is in my bootloader, I tried to reinstall the bootloader with the Moto Flasher and always get the same message:
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT*: opening device: \\.\COM5
OUTPUT*: OKAY [ 14.254s]
OUTPUT*: greeting device for command mode
OUTPUT*: OKAY [ 0.021s]
OUTPUT*: identifying device
OUTPUT*: ...serial = 0x2A0D815
OUTPUT*: ...chip-id = 0x800 (MSM8226)
OUTPUT*: ...chip-rev = 0x0
OUTPUT*: ...sv-sbl = 0x0
OUTPUT*: OKAY [ 0.016s]
OUTPUT*: finding files
OUTPUT*: ...programmer = programmer.mbn
OUTPUT*: ...singleimage = singleimage.bin
OUTPUT*: OKAY [ 0.001s]
OUTPUT*: validating files
OUTPUT*: OKAY [ 0.129s]
OUTPUT*: switching to download mode
OUTPUT*: OKAY [ 0.002s]
OUTPUT*: greeting device for image downloading
OUTPUT*: OKAY [ 0.001s]
OUTPUT*: sending programmer
OUTPUT*: OKAY [ 0.026s]
OUTPUT*: flashing singleimage
OUTPUT*: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
I do not know what to do. I know the version of the bootloader of my device was 41.18
Topics visited to try to remedy the problem:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/showthread.php?t=2712755
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076/
http://forum.xda-developers.com/showthread.php?t=2620025
I need help! :crying::crying::crying:
Update link ota I used:
http://forum.xda-developers.com/moto-g/general/install-brazil-5-0-ota-xt1033-t2963800
I have the same problem with my 1032 since yesterday. Flashed Brazil 5.0 succesfully. But I was not impressed with performance so i flashed a 4.4.2 image. Everything worked fine, until it start updating to 4.4.4.
HSUSb_BULK driver is installed, but no succes. I'm charging the battery to 100% for one more try with MBM-CI_4.4.4, because now i get this errors:
{
"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"
}
or
NoobByn-tek said:
First I apologize, my English is horrible.
Recently I installed the update OTA for the XT1033 Powered model on the site, However I was not very satisfied and returned to the KitKat. And I began to notice some strange things, was facing some problems in fastboot and my screen was also esquesita. I managed to return to the STOCK rom, tried to install the GPE to test the Flyme OS that's also available here on the site. Only after installing the GPE and the OTA update my device did not call more. And I began to receive the driver installation message HSUSb_BULK searched on the internet and saw that the problem is in my bootloader, I tried to reinstall the bootloader with the Moto Flasher and always get the same message:
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT*: opening device: \\.\COM5
OUTPUT*: OKAY [ 14.254s]
OUTPUT*: greeting device for command mode
OUTPUT*: OKAY [ 0.021s]
OUTPUT*: identifying device
OUTPUT*: ...serial = 0x2A0D815
OUTPUT*: ...chip-id = 0x800 (MSM8226)
OUTPUT*: ...chip-rev = 0x0
OUTPUT*: ...sv-sbl = 0x0
OUTPUT*: OKAY [ 0.016s]
OUTPUT*: finding files
OUTPUT*: ...programmer = programmer.mbn
OUTPUT*: ...singleimage = singleimage.bin
OUTPUT*: OKAY [ 0.001s]
OUTPUT*: validating files
OUTPUT*: OKAY [ 0.129s]
OUTPUT*: switching to download mode
OUTPUT*: OKAY [ 0.002s]
OUTPUT*: greeting device for image downloading
OUTPUT*: OKAY [ 0.001s]
OUTPUT*: sending programmer
OUTPUT*: OKAY [ 0.026s]
OUTPUT*: flashing singleimage
OUTPUT*: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
I do not know what to do. I know the version of the bootloader of my device was 41.18
Topics visited to try to remedy the problem:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/showthread.php?t=2712755
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076/
http://forum.xda-developers.com/showthread.php?t=2620025
I need help! :crying::crying::crying:
Update link ota I used:
http://forum.xda-developers.com/moto-g/general/install-brazil-5-0-ota-xt1033-t2963800
Click to expand...
Click to collapse
Ota upgrades bootloader.
Updated bootloader means no downgrading.
Downgrading means brick
Unfortunately for you guys, just wait until new methods come out. Or return it to motorola or jtag the phone...
NoobByn-tek said:
First I apologize, my English is horrible.
Recently I installed the update OTA for the XT1033 Powered model on the site, However I was not very satisfied and returned to the KitKat. And I began to notice some strange things, was facing some problems in fastboot and my screen was also esquesita. I managed to return to the STOCK rom, tried to install the GPE to test the Flyme OS that's also available here on the site. Only after installing the GPE and the OTA update my device did not call more. And I began to receive the driver installation message HSUSb_BULK searched on the internet and saw that the problem is in my bootloader, I tried to reinstall the bootloader with the Moto Flasher and always get the same message:
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT*: opening device: \\.\COM5
OUTPUT*: OKAY [ 14.254s]
OUTPUT*: greeting device for command mode
OUTPUT*: OKAY [ 0.021s]
OUTPUT*: identifying device
OUTPUT*: ...serial = 0x2A0D815
OUTPUT*: ...chip-id = 0x800 (MSM8226)
OUTPUT*: ...chip-rev = 0x0
OUTPUT*: ...sv-sbl = 0x0
OUTPUT*: OKAY [ 0.016s]
OUTPUT*: finding files
OUTPUT*: ...programmer = programmer.mbn
OUTPUT*: ...singleimage = singleimage.bin
OUTPUT*: OKAY [ 0.001s]
OUTPUT*: validating files
OUTPUT*: OKAY [ 0.129s]
OUTPUT*: switching to download mode
OUTPUT*: OKAY [ 0.002s]
OUTPUT*: greeting device for image downloading
OUTPUT*: OKAY [ 0.001s]
OUTPUT*: sending programmer
OUTPUT*: OKAY [ 0.026s]
OUTPUT*: flashing singleimage
OUTPUT*: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
I do not know what to do. I know the version of the bootloader of my device was 41.18
Topics visited to try to remedy the problem:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/showthread.php?t=2712755
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076/
http://forum.xda-developers.com/showthread.php?t=2620025
I need help! :crying::crying::crying:
Update link ota I used:
http://forum.xda-developers.com/moto-g/general/install-brazil-5-0-ota-xt1033-t2963800
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2771636
Sent from my XT1033 using XDA Free mobile app
skr975 said:
http://forum.xda-developers.com/showthread.php?t=2771636
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
How can this help me friend, I have no way to access the device's bootloader?
Staff today when I connected the device to your computer no longer received the message QHSUS_BULK my device started to show a single sign of life. the notification LED flashes when I try to switch on the phone, I've tried to perform the procedures that the internet says to make these cases (Connect the original charger dodispositivo and hold the Power button and the Vol - 2 minutes) however nothing happens, how should I proceed?
So I think I have hardbricked my Moto G, so I went from Lollipop to 4.4.4 GPE and then to 4.4.2 Retail and after that I Updated via WLAN to 4.4.4 Retail.
Now my Phone doesn't turn on or anything.
I've followed this Guide:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
But with no success.
I'm always getting this error after using the blank flash:
C:\Users\Ricardo\Desktop\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM3
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x241047D
...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)
C:\Users\Ricardo\Desktop\blankflash>pause
Pls help me I dont want to buy a new Phone and I need this Phone, it is really important for me to get this Phone working.
xBiOTeCHx said:
So I think I have hardbricked my Moto G, so I went from Lollipop to 4.4.4 GPE and then to 4.4.2 Retail and after that I Updated via WLAN to 4.4.4 Retail.
Now my Phone doesn't turn on or anything.
I've followed this Guide:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
But with no success.
I'm always getting this error after using the blank flash:
C:\Users\Ricardo\Desktop\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM3
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x241047D
...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)
C:\Users\Ricardo\Desktop\blankflash>pause
Pls help me I dont want to buy a new Phone and I need this Phone, it is really important for me to get this Phone working.
Click to expand...
Click to collapse
You can't do anything at the moment. Waaay to many of us has the same problem. We needed to wait for the official motorola lollipop factory image. You can find more information at this thread.
tommark75 said:
You can't do anything at the moment. Waaay to many of us has the same problem. We needed to wait for the official motorola lollipop factory image. You can find more information at this thread.
Click to expand...
Click to collapse
But the Lollipop OTA for the Brazil Version is already out I think, so isn't it possible to get the MBM-CI from this OTA?
xBiOTeCHx said:
But the Lollipop OTA for the Brazil Version is already out I think, so isn't it possible to get the MBM-CI from this OTA?
Click to expand...
Click to collapse
No becasue it is an OTA not a factory image. If it was possible than the developers already did it. But sorry it is not possible, just wait until motorola publish it.
I have the same problem.
tommark75 said:
No becasue it is an OTA not a factory image. If it was possible than the developers already did it. But sorry it is not possible, just wait until motorola publish it.
Click to expand...
Click to collapse
I have the same problem.
I have flash GPE 5.0.1 -> ROM Stock Motorola 4.4.2 + update ota 4.4.4 = Bootloader brick and no startup / fastboot ( anything!)
If anybody know how to save my device (XT1032)...
Thank XDA
We already know the solution, but we are needed to wait for the official motorola frimware.
what is the solution?
tommark75 said:
We already know the solution, but we are needed to wait for the official motorola frimware.
Click to expand...
Click to collapse
what is the solution?
felicuchi1 said:
what is the solution?
Click to expand...
Click to collapse
The solution is to wait until more frimwares get leaked or gets released with the mbm_ci folder in it. If we found them the developers can do the programming stuff with it. They know how to do it, but we don't have the good files. So we are waiting at the moment. For more information go to THIS thread and follow it. But please don't ask for help there, you can see a lot of people complaining but if we found the files, that thread will be the first where it will be published.
any good news?
C:\Users\Disha\Desktop\blankflash\blankflash>.\qbo ot.exe blank-flash
opening device: \\.\COM8
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM8
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM8
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM8
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM8
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM8
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
C:\Users\Disha\Desktop\blankflash\blankflash>pause
Press any key to continue . .
Gpe 4.4 ?
Yes man i think so plz help me
VitorTGOF said:
Gpe 4.4 ?
Click to expand...
Click to collapse
Yes man i think so i try many firmeware on this time and i tried ota update then when phone restart it didn't work again
disha2010 said:
Yes man i think so i try many firmeware on this time and i tried ota update then when phone restart it didn't work again
Click to expand...
Click to collapse
But a new phone.
disha2010 said:
Yes man i think so i try many firmeware on this time and i tried ota update then when phone restart it didn't work again
Click to expand...
Click to collapse
You were in GPE 4.3 and went to 4.4 and gave brick ? If this was 'm having the same problem
Yes that was happend
VitorTGOF said:
You were in GPE 4.3 and went to 4.4 and gave brick ? If this was 'm having the same problem
Click to expand...
Click to collapse
Do you fix this?
No :/
So what can we do w lost out phones?!
VitorTGOF said:
No :/
Click to expand...
Click to collapse
!!!!
We have to wait out the mbn-ci lollipop 5.0
Ok
VitorTGOF said:
We have to wait out the mbn-ci lollipop 5.0
Click to expand...
Click to collapse
Iam waiting is this far?!
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
:crying::crying::crying::crying:
I have moto g 1st Gen XT1033 and it got hard bricked when I tried to reinstall Lolipop 5.1 (Now understood a wrong file for this phone). From then the device wont start, wont boot into boot loader mode, wont do anything. I tried many things which are suggested on internet but nothing worked. For now, if I long press power on button, LED flashes and nothing after that. Please help me in getting back my device into life. I tried doing a blank flash but getting below message
F:\sanjay phone\blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM11
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
F:\sanjay phone\blankflash\blankflash>pause
Press any key to continue . . .
I TRIED DISCONNECTING THE BATTERY AND CHARGING AND TRYING TO RE CONNECT AGAIN BUT THAT DIDN'T WORK TOO.
PLEASE HELP :crying::crying::crying::crying::crying:
please reply
can someone please reply. If this cant be repaired, I will stop looking for solution at least.
:crying::crying::crying::crying:
sanjayuv said:
can someone please reply. If this cant be repaired, I will stop looking for solution at least.
:crying::crying::crying::crying:
Click to expand...
Click to collapse
replacing the motherboard(which costs more than the cost of a smartphone currently) of your device is the solution other than that nothing can be done
sanjayuv said:
can someone please reply. If this cant be repaired, I will stop looking for solution at least.
:crying::crying::crying::crying:
Click to expand...
Click to collapse
no solution yet founf for for the bootloader of android 5.0 ..... I am facing same error and have been waiting for 1 month
wellcome in moto g hardbricked club
sign here
https://secure.avaaz.org/es/petitio..._completo_de_Android_5_para_Moto_G_2013/?copy
Reply
I have kept my moto g safe in locker and got xiomi note 3. If anyone find solution to this, do let me know