I'm rooted, unlocked, have xposed and a an EQ system mod installed. Downloaded stock Tmo 4.4 firmware, used stillthisguy's toolkit, failed to flash. I tried RSD lite, it won't show my phone (I'm using windows 8.1). Any help is greatly appreciated.
Sent from my Nexus 7 using XDA Premium 4 mobile app
eggydrums said:
I'm rooted, unlocked, have xposed and a an EQ system mod installed. Downloaded stock Tmo 4.4 firmware, used stillthisguy's toolkit, failed to flash. I tried RSD lite, it won't show my phone (I'm using windows 8.1). Any help is greatly appreciated.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which firmware are you running , what boot loader are on? Which ROM are you currently on, the more info the better chance someone can help you
Sent on my Gummy running Lenoto X
the first thing you have to do is make your computer to recognice your phone, do you install the motorola device drivers installation???if you do, unninstall it, and make everything again....you should start from there
eggydrums said:
Downloaded stock Tmo 4.4 firmware
Click to expand...
Click to collapse
Is the stock firmware an xml.zip file? If so, what about using mfastboot?
I can't get adb to recognize my phone but mfastboot does.
In this link they give detailed instructions on how to use mfastboot to return the Moto G to stock and they include a link to mfastboot.exe.
Moto G Restore Stock Firmware
I was planning on trying to do that for my Verizon Moto X using mfastboot, since I can't get anything else to recognize my phone.
Sounds like you have a driver issue just like me. I had the same problem with my GNex.
---------- Post added at 03:43 AM ---------- Previous post was at 03:42 AM ----------
rivas1981 said:
the first thing you have to do is make your computer to recognice your phone, do you install the motorola device drivers installation???if you do, unninstall it, and make everything again....you should start from there
Click to expand...
Click to collapse
I have the same problem. No matter how many times I uninstall and reinstall drivers and Motorola Device Manager, I cannot get adb to recognize my device.
mfastboot and fastboot do recognize my device. Can't figure it out.
You can't advance if this is not fixed...its. Computer problem
Enviado desde mi XT1058 mediante Tapatalk
Cozume said:
Is the stock firmware an xml.zip file? If so, what about using mfastboot?
I can't get adb to recognize my phone but mfastboot does.
In this link they give detailed instructions on how to use mfastboot to return the Moto G to stock and they include a link to mfastboot.exe.
Moto G Restore Stock Firmware
I was planning on trying to do that for my Verizon Moto X using mfastboot, since I can't get anything else to recognize my phone.
Sounds like you have a driver issue just like me. I had the same problem with my GNex.
---------- Post added at 03:43 AM ---------- Previous post was at 03:42 AM ----------
I have the same problem. No matter how many times I uninstall and reinstall drivers and Motorola Device Manager, I cannot get adb to recognize my device.
mfastboot and fastboot do recognize my device. Can't figure it out.
Click to expand...
Click to collapse
That's because your using windows 8.1, can you get your hands on a windows 7 machine?
Also if you using 3.0 USB it won't be recognized?
Sent on my Gummy running Lenoto X
flashallthetime said:
That's because your using windows 8.1, can you get your hands on a windows 7 machine?
Also if you using 3.0 USB it won't be recognized?
Click to expand...
Click to collapse
I was using Windows 7 but my laptop only has USB 3.0 ports.
I'm using OTA 4.4. I've nothing other than unlocking and rooting. My PC is recognizing the device, but I fear it may be the mfastboot not working. When I attempt to flash, there is an error
Sent from my Nexus 7 using XDA Premium 4 mobile app
rivas1981 said:
You can't advance if this is not fixed...its. Computer problem
Click to expand...
Click to collapse
Can't he try mfastboot like you can do for the Moto G?
He may be able to get mfastboot to recognize his device. I can get fastboot and mfastboot to recognize my device but have trouble with everything else.
Cozume said:
Can't he try mfastboot like you can do for the Moto G?
He may be able to get mfastboot to recognize his device. I can get fastboot and mfastboot to recognize my device but have trouble with everything else.
Click to expand...
Click to collapse
Yes but its got to be mfastboot
Sent on my Gummy running Lenoto X
eggydrums said:
I'm using OTA 4.4. I've nothing other than unlocking and rooting. My PC is recognizing the device, but I fear it may be the mfastboot not working. When I attempt to flash, there is an error
Click to expand...
Click to collapse
click on that link I posted for the Moto G - there is a link to download version 2 of mfastboot.exe. download it and put your device in bootloader mode, connect it to your PC and at the command prompt type mfastboot devices and see if it recognizes your device.
Which error are you getting
Sent on my Gummy running Lenoto X
flashallthetime said:
Yes but its got to be mfastboot
Click to expand...
Click to collapse
yes, that is what I said. There are instructions on how to do it for the Moto G that I posted. Wouldn't it just be the same for the Moto X, just use the Moto X firmware.
Cozume said:
yes, that is what I said. There are instructions on how to do it for the Moto G that I posted. Wouldn't it just be the same for the Moto X, just use the Moto X firmware.
Click to expand...
Click to collapse
Close but system spapablah wording is not need, you open the XML and that gives you the commands
mfastboot flash system system.img
Sent on my Gummy running Lenoto X
flashallthetime said:
Close but system spapablah wording is not need, you open the XML and that gives you the commands
mfastboot flash system system.img
Click to expand...
Click to collapse
So don't do this:
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
Instead just do this:
mfastboot flash system system.img
Why do you have to do it the other way for the Moto G?
OK we're trying to help this guy, we're getting off track
Pm me
To op
What error did you get when you used mfastboot?
Sent on my Gummy running Lenoto X
flashallthetime said:
OK we're trying to help this guy, we're getting off track
Click to expand...
Click to collapse
I thought I was helping him if he can do it with mfastboot.
Cozume said:
So don't do this:
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
Instead just do this:
mfastboot flash system system.img
Why do you have to do it the other way for the Moto G?
Click to expand...
Click to collapse
Its mfastboot flash system system.img, just open the XML file and it gives you all the commands
Sent on my Gummy running Lenoto X
Something about memory limit. But IIRC, normal android fastboot has a limit on flashing size and mfastboot's is larger correct?
Sent from my XT1053 using XDA Premium 4 mobile app
eggydrums said:
normal android fastboot has a limit on flashing size and mfastboot's is larger correct?
Click to expand...
Click to collapse
yes, this was why I was saying to use mfastboot. From what I can tell mfastboot does everything that fastboot does but doesn't have the file size limitations that fastboot has so I only use mfastboot. I don't see any reason to use fastboot.
Sounds like you have a driver issue just like I do. I can't get adb to recognize my device. But fastboot and mfastboot do recognize my device so unless I can debug my driver issue (and I have tried) I am limited to using mfastboot.
Also, FATT implied USB 3.0 port may be the problem. I only have USB 3.0 ports on my laptop so I can't test to see if that is or is not the issue.
Related
i was recently rooted and successfully flashed the recovery through fastboot but when trying to run install the 4.4 update i get an error message during the install. i tried to completely wipe the device but im having a problem flashing the system.img. when trying to manually flash the system.img in fastboot on windows 8.1, i keep getting an error message where fastboot stops working. anyone know what to do?
try to use fastboot in win7 compatibility mode (right click -> properties -> compatiility)
waiflih said:
try to use fastboot in win7 compatibility mode (right click -> properties -> compatiility)
Click to expand...
Click to collapse
That stopped it from crashing but the flash fails. The phone says the package is too small
did you try with mfastboot? i really don't know what's the difference, but in other threads they suggest that. A link was posted in one of those threads:
https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit?usp=sharing
waiflih said:
did you try with mfastboot? i really don't know what's the difference, but in other threads they suggest that. A link was posted in one of those threads:
https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit?usp=sharing
Click to expand...
Click to collapse
Yea just got it from another thread and it worked. What is the difference with mfastboot? Edit: nm you stated you don't know.
Running the install for the update now hopefully it doesn't error
Edit: it worked thanks for your help
yw, i'm charging the phone to flash the vzw
I used mfastboot to flash system and boot, but when I tried flashing recovery I got the error preflash validation failed. Any help with that?
Jelps said:
I used mfastboot to flash system and boot, but when I tried flashing recovery I got the error preflash validation failed. Any help with that?
Click to expand...
Click to collapse
same. trying to flash it with mfastboot ended up with a failed flash for me and wouldn't boot. got it going again, but still without a recovery. hopefully somebody who has experienced this also comes along.
Tanknspank said:
same. trying to flash it with mfastboot ended up with a failed flash for me and wouldn't boot. got it going again, but still without a recovery. hopefully somebody who has experienced this also comes along.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2534438
so that's the problem you're having?
alex94kumar said:
http://forum.xda-developers.com/showthread.php?t=2534438
so that's the problem you're having?
Click to expand...
Click to collapse
not to that extent, no. My device works fine, I just can't reflash recovery to have the update pass through.
Tanknspank said:
not to that extent, no. My device works fine, I just can't reflash recovery to have the update pass through.
Click to expand...
Click to collapse
Worse comes to worse you could try RSD. That should restore recovery. Just make sure you RSD with the correct fastboot files (i.e. the ones that match the version you are running)
piccit said:
Worse comes to worse you could try RSD. That should restore recovery. Just make sure you RSD with the correct fastboot files (i.e. the ones that match the version you are running)
Click to expand...
Click to collapse
Tried, but couldn't get RSD to recognize my Moto X on Windows 8.1. I can access my X through fastboot, adb and storage but it will not show in RSD to save my life. Tried compatibility modes, older versions... just about everything short of another computer which I wont be able to try until my roommate gets back.
EDIT: I can honestly say that this worked, and with a combination of mfastboot and the recovery.img from the latest sbf, I'm updating along just fine. http://forum.xda-developers.com/showpost.php?p=47635914&postcount=10
Tanknspank said:
Tried, but couldn't get RSD to recognize my Moto X on Windows 8.1. I can access my X through fastboot, adb and storage but it will not show in RSD to save my life. Tried compatibility modes, older versions... just about everything short of another computer which I wont be able to try until my roommate gets back.
EDIT: I can honestly say that this worked, and with a combination of mfastboot and the recovery.img from the latest sbf, I'm updating along just fine. http://forum.xda-developers.com/showpost.php?p=47635914&postcount=10
Click to expand...
Click to collapse
If for some reason that doesn't work out this is what I did and was able to at least flash recovery. flash partition gpt.bin flash motoboot motoboot.IMG flash boot boot.img flash recovery recovery.IMG flash system system.IMG *not sure if motoboot is necessary. Still got an error trying to install though. First 410 and then 252. Ugh.
I bought Moto x -XT 1053 from ebay.com thinking that it was US T Mobile version. On recieving the phone I found out that it was Mexico edition of Xt 1053 with 4.2.2 jellybean rom with no kitkat update. I unlocked the bootloader by getting the key from Motorola site and installed TMobile 4.4.2 rom from SBF DROID DEVELOPER site using the following commands
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
Everything is working fine except the camera which is not at all working. When I launch the app I get a camera error message. Sometimes i can switch to the front camera which seems to be working at times.But rear camera is not at all working
I could not get it to work even one time. Tried rebooting , erasing cache ,safemode etc. I have not installed any 3rd party apps from playstore also.
What could be the reason for this ?Please help me. I am attaching the necessary screenshots and log file.
You should try flashing the t mobile image with rsd
Sent from my XT1053 using Tapatalk
edit: Also, did the camera work before or did the fastboot flashes "break" it? I'm using a 1056 with the 1053 ODIN flashed onto it right now and the camera works fine.... (As you can see even Tapatalk and mtp think this phone is a 1053)
thundercles said:
You should try flashing the t mobile image with rsd
Sent from my XT1053 using Tapatalk
edit: Also, did the camera work before or did the fastboot flashes "break" it? I'm using a 1056 with the 1053 ODIN flashed onto it right now and the camera works fine.... (As you can see even Tapatalk and mtp think this phone is a 1053)
Click to expand...
Click to collapse
Tried with RSD Lite also but facing the same problem.
Also I did not check whether the camera was working initially with the Mexican Rom. Flashed the new KitKat Rom as soon as I got the phone.
It sounds like the camera might have a physical issue like a loose connector...
Sent from my XT1053 using Tapatalk
thundercles said:
It sounds like the camera might have a physical issue like a loose connector...
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Is there anything else which i can try? Can you share the rom which you have installed?
I've flashed all kinds of Roms stock and aosp of all moto x versions onto this 1056 trying to see if any of them knock out that Sim lock and I have never had trouble with the camera. That being said I have kept just under 4.4.2 because ability to have root is critical for me at this time so most everything I have put on here has been 4.4/4.4.1 I have had some issues getting the phone to take 4.2.2 roms sometimes but never camera issues just sometimes the phone just refuses to be flashed with parts of or a whole 4.2.2 Rom.
Edit: oh an easy potential culprit could be permission issues. In your custom recovery select "fix permissions" and clear the data and cache partitions. An rsd flash does NOT clear these out, I still have pretty much all the crap I had when I was running the sprint Rom earlier today on my phone even though I used rsdlite to flash the stock t Mobile ODIN a few hours ago.
Sent from my XT1053 using Tapatalk
Tried clearing the data and cache partitions but in vain. This could most probably be some hardware issue as you mentioned may be like a loose connector.
Anyways thanks for your suggestions.
I unlocked my bootloader, but when I try to flash twrp-2.6.3.1-ghost-4.4.img method using mfastboot, I get an error message. Anyone else have this problem?
motoxnoob said:
I unlocked my bootloader, but when I try to flash twrp-2.6.3.1-ghost-4.4.img method using mfastboot, I get an error message. Anyone else have this problem?
Click to expand...
Click to collapse
maybe try renaming the recovery image to something simpler, like "recovery_twrp.img"? my guess is you aren't getting the filename completely right.
motoxnoob said:
I unlocked my bootloader, but when I try to flash twrp-2.6.3.1-ghost-4.4.img method using mfastboot, I get an error message. Anyone else have this problem?
Click to expand...
Click to collapse
I had an error a while back with TWRP & mFastboot. I had to update my Android SDK and then all was good! (just a thought)
Dburgessme2 said:
I had an error a while back with TWRP & mFastboot. I had to update my Android SDK and then all was good! (just a thought)
Click to expand...
Click to collapse
Can you clarify what you mean by "updating" Android SDK? thanks
I don't have PC around me now and don't use adb often enough to know exactly. But you should have the. Android SDK on your computer and correct drivers, etc for fastboot & mFastboot to work (as far as I know). It seems like the platform tools were old. But, it actually told me that when I opened it.
DB's Moto X
motoxnoob said:
Can you clarify what you mean by "updating" Android SDK? thanks
Click to expand...
Click to collapse
Are you verifying the device is detected and connected in the fastboot command prompt? It should show your device s/n or name or whatever. Is the recovery in the same folder you are issuing the commands from?
Sent from my XT1060 using XDA Free mobile app
To upgrade android adb/platform tools see the bottom of ->http://mark.cdmaforums.com/ADB.htm
And while there, grab the mfastboot. I've seen people have problems flashing logo.bin and recovery because they didn't have the latest mfastboot.
Hi all - just tried again and this is the error message I am getting:
FAILED (data transfer failure (unknown error))
My device is being recognized. I saved "mfastboot" and the TWRP recovery img file in the SDK platform tools folder. Is this the correct place to save these two files in?
Figured it out. Of all things, I switched from USB 3 to USB 2 and it flashed fine. Now rooted! Thanks everyone!
Now that I have an unlocked bootloader I was trying to update to the newest stock version. I had modded by /system so I was unable to do an easy OTA update. I was trying to flash a system.img from here for 4.4 since that is what I was running but then fastboot threw me an error. I think it was an issue with the file since I got this error
Anyone know where I can the sbf file for our phone? I need +4.4 since that is what I was running last.
Side Question: When using TWRP to back up what format does the usb drive need to be so I can put back ups on it? FAT32?
Thanks in advance for all help
Are you using motos custom fastboot to flash the system image? The image is too large for regular fastboot, moto fastboot breaks it up into chunks to flash properly
Sent from my XT1060
rocketsaucev2 said:
Are you using motos custom fastboot to flash the system image? The image is too large for regular fastboot, moto fastboot breaks it up into chunks to flash properly
Sent from my XT1060
Click to expand...
Click to collapse
So I was using the fastboot that comes with the sdk. Where can I download motos custom fastboot? Are there any important differences from regular fastboot?
Nitro made a zip that has everything you need including the mfasboot.exe
You will need to flash the system.img with the mfastboot command instead of fastboot.
https://www.elementalxdesigns.com/e...-Edition-install-TWRP-and-how-to-flash-images
Icon000 said:
So I was using the fastboot that comes with the sdk. Where can I download motos custom fastboot? Are there any important differences from regular fastboot?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B28ubovBBGskTnBlUl9reGFzQ1E/view?usp=sharing
heres a copy of mine. Make sure you put it in the same folder as your adb or regular fastboot and use the command 'mfastboot' when flashing
rocketsaucev2 said:
https://drive.google.com/file/d/0B28ubovBBGskTnBlUl9reGFzQ1E/view?usp=sharing
heres a copy of mine. Make sure you put it in the same folder as your adb or regular fastboot and use the command 'mfastboot' when flashing
Click to expand...
Click to collapse
I tried using that it seems to have worked but now I have an issue with my system.img. It will not turn wifi on and it will not update to 4.4.4. Where can I find a good copy of 4.4.2 sbf
Icon000 said:
I tried using that it seems to have worked but now I have an issue with my system.img. It will not turn wifi on and it will not update to 4.4.4. Where can I find a good copy of 4.4.2 sbf
Click to expand...
Click to collapse
Did you flash back the original boot.img so it matches your system.img?
adm1jtg said:
Did you flash back the original boot.img so it matches your system.img?
Click to expand...
Click to collapse
I tired a whole bunch of things ended up finding 4.4.4 and using rsdlite to put it on my phone.
Thanks anyway.
hi guys
have some problem here and it s serious
so my man locked the bootloader with a tutorial from a Moto g and write wrong
locked the bootloader then flash it the system then erases the userdata and all cache etc
so no recovery,no boot.
now when is trying to unlock the bootloader says OEM allowed unlock or something similar
i was trying to flash 4..4.4 RETBR but got some errors
bootloader invalid sytem img
bootloader invalid prefailed flash
how can i make it work?
the phone stays in fastboot always
can t boot to recovery
please some help here
i was thinking 3 solutions.
unlocking the bootloader but how?
waiting for Lollipop img
or calling Motorola to unlock the bl
thank u
why would you relock your bootloader?
solution its simple, if you dont want to unlock it again, use rsd lite 6.2.9 and flash the firmware from the country of your moto maxx, if its a mexican moto maxx flash mexico ,if its puerto rico, PR or if its brasil, then brasil. you can flash them, those are flasheable with locked bootloader because they are signed, just the one where your phone was
Jaocagomez said:
why would you relock your bootloader?
solution its simple, if you dont want to unlock it again, use rsd lite 6.2.9 and flash the firmware from the country of your moto maxx, if its a mexican moto maxx flash mexico ,if its puerto rico, PR or if its brasil, then brasil. you can flash them, those are flasheable with locked bootloader because they are signed, just the one where your phone was
Click to expand...
Click to collapse
But RSD doesnt recognize the phone
guivalli said:
But RSD doesnt recognize the phone
Click to expand...
Click to collapse
You need your phone on fastboot and use rsd 6.2.4
Jaocagomez said:
You need your phone on fastboot and use rsd 6.2.4
Click to expand...
Click to collapse
Yes!! rsd 6.2.4 recognize!
But result fail gpt.bin
---------- Post added at 04:33 AM ---------- Previous post was at 03:48 AM ----------
guivalli said:
Yes!! rsd 6.2.4 recognize!
But result fail gpt.bin
Click to expand...
Click to collapse
i replace gpt.bin than lollipop OTA and its ok!
but fail in boot.img, recovery.img and system.img_sp...0,1,2,3,4 fail too
guivalli said:
Yes!! rsd 6.2.4 recognize!
But result fail gpt.bin
---------- Post added at 04:33 AM ---------- Previous post was at 03:48 AM ----------
i replace gpt.bin than lollipop OTA and its ok!
but fail in boot.img, recovery.img and system.img_sp...0,1,2,3,4 fail too
Click to expand...
Click to collapse
Please don't do that, lollipop it's supposed to install via recovery and not thru fastboot, please check that you downloaded the retail version of your Moto maxx and not carrier one.
Jaocagomez said:
Please don't do that, lollipop it's supposed to install via recovery and not thru fastboot, please check that you downloaded the retail version of your Moto maxx and not carrier one.
Click to expand...
Click to collapse
i tired both and same errors
before that problem in my moto, i was in lollipop...
do u think thats the problem?
guivalli said:
i tired both and same errors
before that problem in my moto, i was in lollipop...
do u think thats the problem?
Click to expand...
Click to collapse
First things first, it's your Moto maxx from mexico, puerto rico or Brasil?
Jaocagomez said:
First things first, it's your Moto maxx from mexico, puerto rico or Brasil?
Click to expand...
Click to collapse
Brasil
guivalli said:
Brasil
Click to expand...
Click to collapse
It's retail version or from claro or another company?
Jaocagomez said:
It's retail version or from claro or another company?
Click to expand...
Click to collapse
Retail
guivalli said:
Retail
Click to expand...
Click to collapse
Download this firmware and then flash it with rsd lite
https://mega.co.nz/#!KtYX2A7S!LTexE6weRap6e2g9l_ve8aBdShW-sGMpp2ZI4-xT_EA
Jaocagomez said:
Download this firmware and then flash it with rsd lite
https://mega.co.nz/#!KtYX2A7S!LTexE6weRap6e2g9l_ve8aBdShW-sGMpp2ZI4-xT_EA
Click to expand...
Click to collapse
i tried this one...
Failed everytime... i think its cause i used a Lolli before
guivalli said:
i tried this one...
Failed everytime... i think its cause i used a Lolli before
Click to expand...
Click to collapse
Then you have to manually flash all the files with fastboot, unzip all the contents to your fastboot folder and flash them one by one let me look for the fastboot commands
Jaocagomez said:
Then you have to manually flash all the files with fastboot, unzip all the contents to your fastboot folder and flash them one by one let me look for the fastboot commands
Click to expand...
Click to collapse
Jaocagomez,
i tried flash manual, 2danger try to me too
But with bootloader locked + impossible unlock cause lolli demand check one option in settings to unlock... all failed
guivalli said:
Jaocagomez,
i tried flash manual, 2danger try to me too
But with bootloader locked + impossible unlock cause lolli demand check one option in settings to unlock... all failed
Click to expand...
Click to collapse
You flash those files in fastboot mode, lollipop has nothing to do with it
This is fastboot mode:
http://forum.xda-developers.com/showthread.php?t=3011311
Jaocagomez said:
You flash those files in fastboot mode, lollipop has nothing to do with it
This is fastboot mode:
http://forum.xda-developers.com/showthread.php?t=3011311
Click to expand...
Click to collapse
Yes, my Moto doesnt exit fastboot mode
guivalli said:
Yes, my Moto doesnt exit fastboot mode
Click to expand...
Click to collapse
Do you have android sdk installed on your pc? You need that to flash without rsd
Jaocagomez said:
Do you have android sdk installed on your pc? You need that to flash without rsd
Click to expand...
Click to collapse
I have fastboot, mfastboot, adb... everything =/
guivalli said:
I have fastboot, mfastboot, adb... everything =/
Click to expand...
Click to collapse
ok unzip all the contents of firmware you downloaded on the fastboot folder.
using cmd write
Code:
fastboot devices
if a device show with any code like d654654
then your phone its detected
after that write this in cmd:
you can copy and paste it:
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot erase clogo
fastboot oem fb_mode_clear
and your phone will work.