Related
I am having a problem after rooting my phone... i want to flash the 'recovery-RA-passion-v2.2.1-CM.img but it does not allow me to.. I am using the Command Promp:
fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
this is the command..but what happens it this:
error: cannot load 'recovery-RA-passion-v2.2.1-CM.img'
Please help!
PS: phone is rooted.
ChortiRok said:
I am having a problem after rooting my phone... i want to flash the 'recovery-RA-passion-v2.2.1-CM.img but it does not allow me to.. I am using the Command Promp:
fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
this is the command..but what happens it this:
error: cannot load 'recovery-RA-passion-v2.2.1-CM.img'
Please help!
PS: phone is rooted.
Click to expand...
Click to collapse
Assuming the device is seen by fastboot, you need to specify the path to the recovery img
have you unlocked ur bootloader to run fastboot commands?
Sent from my Nexus One using Tapatalk
taodan said:
Assuming the device is seen by fastboot, you need to specify the path to the recovery img
Click to expand...
Click to collapse
Same opinion here, most likely the cause is the missing path to the file.
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 Can't flash recovery for my moto x, I have unlocked the bootloader and appears to me on fastboot: Device is UNLOCKED. Status Code:3
I don't know if this is right, but I can't flash a recovery in it.
Error:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8030 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.116s
I tested various recovery's but don't work.
Sorry for my bad english
Murilo900 said:
I Can't flash recovery for my moto x, I have unlocked the bootloader and appears to me on fastboot: Device is UNLOCKED. Status Code:3
I don't know if this is right, but I can't flash a recovery in it.
Error:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8030 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.116s
I tested various recovery's but don't work.
Sorry for my bad english
Click to expand...
Click to collapse
Are you using mfastboot? You should be..
Sent From Droid Ultra
In addition to mFastboot, make sure your battery is charged more than 80%
Caseyk621 said:
Are you using mfastboot? You should be..
Sent From Droid Ultra
Click to expand...
Click to collapse
KidJoe said:
In addition to mFastboot, make sure your battery is charged more than 80%
Click to expand...
Click to collapse
Yes,
I did on mfastboot and appears the same thing, and the battery is full, when I try to flash on moto x appears : getvar-download-size
Murilo900 said:
Yes,
I did on mfastboot and appears the same thing, and the battery is full, when I try to flash on moto x appears : getvar-download-size
Click to expand...
Click to collapse
What ROM is on your phone right now? Which recovery are you trying to flash?
What state was your phone in when you started trying to flash recovery?
KidJoe said:
What ROM is on your phone right now? Which recovery are you trying to flash?
What state was your phone in when you started trying to flash recovery?
Click to expand...
Click to collapse
The ROM on my phone is 4.4.2 KitKat, I tried to flash twrp recovery 2.6.3.1 and cwm recovery for motox
The state was the same, I unlocked bootloader, following tutorials on internet but I'm stuck on flash the recovery because this problem, I get this error and on my phone appears getvar-download-size, and Download Failed.
Murilo900 said:
The ROM on my phone is 4.4.2 KitKat, I tried to flash twrp recovery 2.6.3.1 and cwm recovery for motox
The state was the same, I unlocked bootloader, following tutorials on internet but I'm stuck on flash the recovery because this problem, I get this error and on my phone appears getvar-download-size, and Download Failed.
Click to expand...
Click to collapse
Ok.
Try the mfastboot from inside -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip (will have to rename fastboot.exe to mfastboot.exe).. or from -> http://mark.cdmaforums.com/X-STUFF/ADB-MFASTBOOT.zip they are the ones I use and they have worked for me.
and is this the twrp you are using? -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Oh god! Thanks, this mfastboot you just send works!, I don't know if the problem was my mfastboot that I have here, but finally I flashed! Leveraging the topic can you suggest me some roms for moto x, and if you know some way to take off the boot the sign that the bootloader is unlocked blablabla, Anyway thank you.
Murilo900 said:
Oh god! Thanks, this mfastboot you just send works!, I don't know if the problem was my mfastboot that I have here, but finally I flashed! Leveraging the topic can you suggest me some roms for moto x, and if you know some way to take off the boot the sign that the bootloader is unlocked blablabla, Anyway thank you.
Click to expand...
Click to collapse
I run stock, unlocked and rooted, so I can't suggest an alternate roms.
As for the unlocked bootloader warning message... sure. there is a big thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961 start around post 150 of that thread for how to make your own... in a couple of hours I'll refresh this file -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip adding even more logo.bin files (i have about 7 or 8 more to test before I can re-zip and upload it)
HELP!!
I am at a loss. No matter what fastboot/mfastboot I use, no matter what YouTube video I follow, I can not flash recovery.
I get the same error as the OP. I tried the links posted a few posts up, it wont work.
I type the commands, I get the top error message (among others depending on the mfastboots I try) and then nothing.
I am truly at a loss.
Verizon Developer Moto X
4.4.2
Device is: Unlocked
Status Code: 3
In one video I watched it said that I needed to have it say Status Code:1. Is that where I am going wrong?
Any help would be greatly appreciated.
Thanks!!
n99hockey said:
I am at a loss. No matter what fastboot/mfastboot I use, no matter what YouTube video I follow, I can not flash recovery.
I get the same error as the OP. I tried the links posted a few posts up, it wont work.
I type the commands, I get the top error message (among others depending on the mfastboots I try) and then nothing.
I am truly at a loss.
Verizon Developer Moto X
4.4.2
Device is: Unlocked
Status Code: 3
In one video I watched it said that I needed to have it say Status Code:1. Is that where I am going wrong?
Any help would be greatly appreciated.
Thanks!!
Click to expand...
Click to collapse
What recovery are you trying to flash? Stock or other? Unlocked Status Code 3 is needed to flash an alternate or 3rd party recovery.
Besides the error listed in the first post, exactly what "others" do you see as error codes?
Things to try... (in no special order)
this mfastboot -> mfastboot-442.zip
re-download the recovery you are trying to flash
update your ADB and Platform Tools
There are several versions of TWRP that can work.
Unofficial TWRP 2.6.3.1 for 4.4 -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Unofficial TWRP 2.7.0.0 -> http://androidhosting.org/Devs/Dhacker29/MotoX/TWRP-2.7.0.0-moto_msm8960dt.img
Official TWRP 2.7.1.1 -> http://techerrata.com/browse/twrp2/ghost
of those, I've only used the 2.6.3.1 on my VZW Dev X with 4.4.2 and below.
KidJoe said:
What recovery are you trying to flash? Stock or other? Unlocked Status Code 3 is needed to flash an alternate or 3rd party recovery.
Besides the error listed in the first post, exactly what "others" do you see as error codes?
Things to try... (in no special order)
this mfastboot -> mfastboot-442.zip
re-download the recovery you are trying to flash
update your ADB and Platform Tools
There are several versions of TWRP that can work.
Unofficial TWRP 2.6.3.1 for 4.4 -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Unofficial TWRP 2.7.0.0 -> http://androidhosting.org/Devs/Dhacker29/MotoX/TWRP-2.7.0.0-moto_msm8960dt.img
Official TWRP 2.7.1.1 -> http://techerrata.com/browse/twrp2/ghost
of those, I've only used the 2.6.3.1 on my VZW Dev X with 4.4.2 and below.
Click to expand...
Click to collapse
Thanks for the reply.
However I should have known better, I changed the USB port and it worked just fine with the mfastboot I downloaded longer than I would like to admit before I posted my question.
</sigh>
Still can't flash custom recovery
I have a Verizon XT1060 Developer Edition. Unlocked bootloader. Drivers seem to be installed correctly, "Fastboot devices" identifies the phone. Battery is 90%+. Fastboot menu says "Device is unlocked. Status Code 3". I have tried different USB ports on the PC, different cables to connect the phone and just about every other variable that I can think of.
I have followed all of the suggestions listed in this post and I still cannot flash a custom recovery. I have tried multiple versions of TWRP, Fastboot, Mfastboot etc.. Here is the error message...
(bootloader) Variable not supported!
error: cannot open 'twrp-2.6.3.1-ghost-4.4.img'
Actually depending on the method I am trying at the time, fastboot mfastboot etc., I may get a couple of additional lines that mention Max download size etc. but it always starts with the bootloader comment and ends with "Cannot open......"
Searching for "(bootloader) Variable not supported!" returns a lot of hits but I have not found anything to clear the issue. Any help would be appreciated.
Ric214 said:
....Here is the error message...
(bootloader) Variable not supported!
error: cannot open 'twrp-2.6.3.1-ghost-4.4.img'
...
Click to expand...
Click to collapse
That usually means that mFastboot (or fastboot) can't find the IMG file on your PC.
My first question would be... does that file exist in your current directory/folder?
i.e... at the command prompt.. type dir *.img is the twrp file listed there? If no, that is your issue. change to the folder (directory) where the TWRP IMG file is, and try it.
It is there. Here is what I got.
C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86
_64-20140321\sdk\platform-tools>dir *.img
Volume in drive C is OS
Volume Serial Number is 76F9-C97B
Directory of C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bund
le-windows-x86_64-20140321\sdk\platform-tools
06/13/2014 10:54 PM 8,417,280 openrecovery-twrp-2.7.1.1-ghost.img
06/03/2014 11:10 PM 10,090,496 twrp-2.6.3.1-ghost-4.4.img
2 File(s) 18,507,776 bytes
0 Dir(s) 426,324,336,640 bytes free
Since this has been driving me crazy for a couple of days I have several folders with different versions of Fastboot and Mfastboot in them along with some different versions of TWRP and CWM and I am getting the same error with all of them. This last time I just stuck the TWRP file in my platform -tools folder to try and make sure I had a good Fastboot file.
Thanks for the reply. If you have any other ideas I am eager to hear them.
Ric214 said:
It is there. Here is what I got.
C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86
_64-20140321\sdk\platform-tools>dir *.img
Volume in drive C is OS
Volume Serial Number is 76F9-C97B
Directory of C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bund
le-windows-x86_64-20140321\sdk\platform-tools
06/13/2014 10:54 PM 8,417,280 openrecovery-twrp-2.7.1.1-ghost.img
06/03/2014 11:10 PM 10,090,496 twrp-2.6.3.1-ghost-4.4.img
2 File(s) 18,507,776 bytes
0 Dir(s) 426,324,336,640 bytes free
Since this has been driving me crazy for a couple of days I have several folders with different versions of Fastboot and Mfastboot in them along with some different versions of TWRP and CWM and I am getting the same error with all of them. This last time I just stuck the TWRP file in my platform -tools folder to try and make sure I had a good Fastboot file.
Thanks for the reply. If you have any other ideas I am eager to hear them.
Click to expand...
Click to collapse
Had you made ANY prior modifications to your unit before now? Any possibility you used one of the previous root/write protect disable exploits, and THEN got the bootloader unlocked?
I've seen alot of users in this situation recently -thanks to middleman
I suggest you follow the 'return to stock' thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You should flash the 4.4.2 VZW SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
SBFing back to stock is very different from a Factory Reset in that it can actually repair a damaged filesystem, and even un-do any previous exploits you may have used.
There are 2 methods - many report that the "Manual Method" is easier than using RSD Lite. Either should work equally well, but pay close attention to the steps.
You will want to do a couple of things just a little bit differently. First, use mfastboot as suggested by KidJoe for ALL flashing commands.
Second, once your phone has been placed into bootloader mode (AP Fastboot), before you proceed with the fastboot commands listed under Manual Method, do this first:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Your device should reboot back to the bootloader. NOW, proceed with the entire list of commands (using mfastboot for all of them). Yes, you will be flashing partition and motoboot again...don't worry. It is intentional.
After you have completed the rest of the steps, you will likely be able to flash TWRP (or custom recovery of your choice) without issue.
Let us know if this fixes your issues.
samwathegreat said:
Had you made ANY prior modifications to your unit before now? Any possibility you used one of the previous root/write protect disable exploits, and THEN got the bootloader unlocked?
I've seen alot of users in this situation recently -thanks to middleman
I suggest you follow the 'return to stock' thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You should flash the 4.4.2 VZW SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
SBFing back to stock is very different from a Factory Reset in that it can actually repair a damaged filesystem, and even un-do any previous exploits you may have used.
There are 2 methods - many report that the "Manual Method" is easier than using RSD Lite. Either should work equally well, but pay close attention to the steps.
You will want to do a couple of things just a little bit differently. First, use mfastboot as suggested by KidJoe for ALL flashing commands.
Second, once your phone has been placed into bootloader mode (AP Fastboot), before you proceed with the fastboot commands listed under Manual Method, do this first:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Your device should reboot back to the bootloader. NOW, proceed with the entire list of commands (using mfastboot for all of them). Yes, you will be flashing partition and motoboot again...don't worry. It is intentional.
After you have completed the rest of the steps, you will likely be able to flash TWRP (or custom recovery of your choice) without issue.
Let us know if this fixes your issues.
Click to expand...
Click to collapse
I had not done any modifications prior to unlocking the bootloader but going back to stock is about the only thing that I could think of that I have not already tried. I will give this a shot tomorrow night and let you know how it went. Thanks for your help.
Ric214 said:
I had not done any modifications prior to unlocking the bootloader but going back to stock is about the only thing that I could think of that I have not already tried. I will give this a shot tomorrow night and let you know how it went. Thanks for your help.
Click to expand...
Click to collapse
One last thing I can suggest before return to stock:
Are you trying to flash the recovery -while booted into Android-? If so, you have to have USB Debugging enabled. Some users have experienced difficulty using fastboot while booted into Android even with USB debugging enabled.
----------------
You can try flashing from bootloader (AP Fastboot Mode) instead.
To do this, unplug the phone from USB. Power off the phone. Hold down VOL DOWN and power the phone back on. You should now be booted into bootloader.
Now plug the USB back in, and try:
mfastboot flash recovery twrp_filename.img
samwathegreat said:
One last thing I can suggest before return to stock:
Are you trying to flash the recovery -while booted into Android-? If so, you have to have USB Debugging enabled. Some users have experienced difficulty using fastboot while booted into Android even with USB debugging enabled.
----------------
You can try flashing from bootloader (AP Fastboot Mode) instead.
To do this, unplug the phone from USB. Power off the phone. Hold down VOL DOWN and power the phone back on. You should now be booted into bootloader.
Now plug the USB back in, and try:
mfastboot flash recovery twrp_filename.img
Click to expand...
Click to collapse
Thanks for the advice but I am not booted into Android. I started with the phone off and got into the bootloader exactly as you suggested. I will have some time over the next few days to flash back to stock and start over again. I will post the results. In the meantime if you think of anything else, let me know. Thanks for your help.
Ric214 said:
Thanks for the advice but I am not booted into Android. I started with the phone off and got into the bootloader exactly as you suggested. I will have some time over the next few days to flash back to stock and start over again. I will post the results. In the meantime if you think of anything else, let me know. Thanks for your help.
Click to expand...
Click to collapse
try shortening the path the IMG resides in...
i.e. make a folder off the root of drive C call it FLASH... drop the TWRP.img into c:\flash and try flashing it from there.
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.
I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Raistlin1 said:
I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Click to expand...
Click to collapse
I would get into bootloader mode and reflash the system.img.
JulesJam said:
I would get into bootloader mode and reflash the system.img.
Click to expand...
Click to collapse
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
I even tried using someone's toolkit to return completely stock u rooted 4.4 but that doesn't work either.
Been reading tons of threads on here but can't seem to get it to flash.
Raistlin1 said:
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
Click to expand...
Click to collapse
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
JulesJam said:
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
Click to expand...
Click to collapse
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Raistlin1 said:
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Click to expand...
Click to collapse
I would try flashing the sparsechunks if you can't flash the single file image.
JulesJam said:
I would try flashing the sparsechunks if you can't flash the single file image.
Click to expand...
Click to collapse
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
I am really screwing myself, now while in bootloader and I try to boot or recovery I get failed to validate. Never had these problems flashing my N5, oh well.
Raistlin1 said:
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
Click to expand...
Click to collapse
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
JulesJam said:
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
Click to expand...
Click to collapse
I am getting bootloader failed to erase partition, failed remote failure.
MDM says phone is on latest version. mfastboot is the size you stated.
Raistlin1 said:
I am getting bootloader failed to erase partition, failed remote failure.
Click to expand...
Click to collapse
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
JulesJam said:
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
Click to expand...
Click to collapse
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Raistlin1 said:
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Click to expand...
Click to collapse
Can you reflash stock recovery?
Your bootloader is locked correct?
JulesJam said:
Can you reflash stock recovery?
Your bootloader is locked correct?
Click to expand...
Click to collapse
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Raistlin1 said:
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Click to expand...
Click to collapse
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
I am spent, going to bed and will pick up again tomorrow. Thanks for helping out.
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Raistlin1 said:
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Click to expand...
Click to collapse
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
JulesJam said:
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
Click to expand...
Click to collapse
As of now I can only get into fastboot mode, I don't believe the phone can even cycle through trying to boot any more. I tried rebooting from fastboot mode but there was an error and it failed.
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Raistlin1 said:
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Click to expand...
Click to collapse
http://www.graffixnyc.com/motox.php
JulesJam said:
http://www.graffixnyc.com/motox.php
Click to expand...
Click to collapse
Downloaded the 5.0 file from there, started flashing those files and it worked up until recovery, then I got the same bootloader message I was getting previously. Tried them over again and they all failed.
When in recovery adb devices starts the daemon and then says list of devices attached but I don't see anything after that.
I think it is fubar`d, going to have to file a warrant claim or use the moto care I purchased.