[Q] [help]Bootloader Bricked - Moto G Q&A, Help & Troubleshooting

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.

Related

Moto G hardbricked

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?

Moto G Hard Brick after Lollipop

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?

[Q] Moto G shown as Qualcomm HS-USB QDLoader 9008 (COM6)

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?

Moto g dead :( help me please

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?!

systemupdate and empty battery - bricked?!?

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

Categories

Resources