I have non-dev Verizon Moto X 4.4.2 unlocked using the chinese method.
I'm in fastboot right now and it says "Device is UNLOCKED. Status Code: 3" if that means anything.
Every time I tried to flash TWRP and I reboot to recovery...it's still the stock android recovery.
I also tried to erase the stock recovery but i get this message:
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.094s
My motox is unlocked..so why doesn't it say permission denied and why can't i flash a custom recovery??
please help.
I'm not root btw.
Did you go into TWRP after flashing it?
You have to boot straight to recovery or it gets written over by the stock recovery
bigv5150 said:
You have to boot straight to recovery or it gets written over by the stock recovery
Click to expand...
Click to collapse
i thought i did but it boot straight into the OS instead of recovery...let me try again...
*edit*
ok wow i guess i didn't do it when i thought i did but i'm in TWRP now.
Thank you guys!
You probably hit the power button instead of volume+ the first time around.
having some flashing issues
I can confirm good file download, drivers on PC are good, I'm using a back USB port, USB cable is BRAND NEW! lol, have Write protection off as well. Tried both fastboot and mfastboot just for good measure. Any thoughts? Do I NEED to have an unlocked bootloader for this? please say no
Also the file shows up as a different size on the fastboot screen, it's over 10mb.
C:\Users\Ivan Lee\Downloads\Android\adt-bundle-windows-x86-20131030\sdk\platform
-tools>mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
sending 'recovery' (9854 KB)...
OKAY [ 0.850s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.250s
Click to expand...
Click to collapse
You need a unlocked bootloader to flash twrp. If you are locked then you must use safestrap recovery.
Travisdroidx2 said:
You need a unlocked bootloader to flash twrp. If you are locked then you must use safestrap recovery.
Click to expand...
Click to collapse
Was afraid of that... sucks. Would that mean only certain partitions have R/W access with "MotoWpNoMo"?
No the entire system has r/w access the only difference is you can flash a kernel with an unlocked boot loader. As a matter of fact safstrap is made from twrp they look and function the same. Only difference is SS has ROM slots for kexek kernels. Unlocked bootloaders don't need these slots we can flash just about anything within reason.
If you're on 4.4.2 you won't get root now tho. You'd have had to be rooted before upgrading.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
bigv5150 said:
No the entire system has r/w access the only difference is you can flash a kernel with an unlocked boot loader. As a matter of fact safstrap is made from twrp they look and function the same. Only difference is SS has ROM slots for kexek kernels. Unlocked bootloaders don't need these slots we can flash just about anything within reason.
Click to expand...
Click to collapse
I'll assume by system you mean system partition, I figured that since we can get root on 4.4 Write protection has to be removed from at the very least the system partition. Also, Yeah I know a little about safestrap and it's features but may not bother with it, had 3 Moto-x's so far, all have the same MMS issue so I'm probably def refunding it, that issue aside great phone. also, i don't want to unlock my bootloader (no warranty) especially since Moto's stock firmware has bugs in it.
kj2112 said:
If you're on 4.4.2 you won't get root now tho. You'd have had to be rooted before upgrading.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
No 4.4.2 stuff here. I mentioned having write protection off so I'm def rooted already thanks for the replies guys
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.
I'm trying to convert my Moto X 1097 to 1095 pure. When I try flashing files with mfastboot I get hab check failed for boot and hab check failed for recovery. It's running 4.4.4 pure but I assume still has old recovery as it won't boot into recovery. I have abd all and downloaded mfastboot v2. Why am I getting these errors? Bootloader unlocked.
Are you trying to flash 4.4.4 or 5.0?
Motoboot and gpt can never be downgraded, some files will always show they failed the hab check even though they are ok as they aren't the original files.
If you flash the entire 4.4.4 or 5.0 Pure firmware package you will have no radio at all and will need to use the original NON-HLOS.bin from the matching Telus package to get it back.
If you want to try the Pure 5.1 soak/leak then flash the full Pure 5.0 package and then apply the soak update via stock recovery. At that point your radios will work as the 5.1 soak appears to include a modem/radio that works with the XT1097.
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple.
matt1515 said:
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple. Also so what do I have to do to make these commands work [fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img. Only flash these when it's the exact version? /QUOTE]
Click to expand...
Click to collapse
matt1515 said:
matt1515 said:
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple. Also so what do I have to do to make these commands work [fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img. Only flash these when it's the exact version? /QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Stop using the power button to try to select recovery like you would on a Nexus device - use the volume up button and you'll be fine
Hahah dang I feel dumb
So just to conclude if I did want to go back to fresh stock Telus. Would these [fastboot flash partition gpt.bin and fastboot flash motoboot motoboot.img still not work and not be needed? I understand motoboot is bootloader but what is got.bin?
If you go back to Telus firmware those two files likely won't update. I recommend you always go through the motions and if they fail it is fine to continue with the other files. When Telus 5.1 is released you will likely be able to update those two files again - it doesn't seem to really matter though with the 2014 Moto X.
Ok good information one question I have to ask. Does it really matter what fastboot I use and if so what is the best one to use for this phone?
Do you mean fastboot versus mfastboot(motorola specific version) ?
It only matters with the system image which is too large for regular fastboot and required the Motorola specific version which can handle the larger files and/or the sparse files.
Exactly the answer I was looking for. Thanks a lot!
Sent from my XT1095 using XDA Free mobile app
nexus 6 can not run the system, only the logo on the screen does not move
I tried to brush oem unlock firmware but failed.
I guess I broke the Recovery partition.
How can I do it? Help me!:angel::angel:
Please give a bit more detail about your setup and what happened before this
rootSU said:
Please give a bit more detail about your setup and what happened before this
Click to expand...
Click to collapse
I installed android 5.1.
root
Installed TWRP Recovery
Then I run "fastboot oem lock" this time we can not normally enter the system.
I found that running fastboot -w can enter the system, so I entered the "TWRP Recovery" to restore the backup method used to restore a backup Recovery partition.
So, let me get it straight...
You unlocked the bootloader
You then rooted
Installed recovery
THEN relocked the boot loader?
...why?
You won't be able to do anything to any partition until the boot loader is unlocked again - try that. Unlock the boot loader (make sure to enable it in Dev settings) and then it should all work again.
Good job, I think you bricked yourself.
Not sure if anyone found a work around for this.
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
Leo D said:
nexus 6 can not run the system, only the logo on the screen does not move
I tried to brush oem unlock firmware but failed.
I guess I broke the Recovery partition.
How can I do it? Help me!:angel::angel:
Click to expand...
Click to collapse
If you have TWRP recovery installed and ONLY if you have TWRP installed, boot into bootloader. Issue the fastboot commands:
fastboot format userdata
fastboot format cache
If you do have TWRP installed, this should allow you to boot to TWRP recovery.
See if you can accomplish this and let us know.
Evolution_Freak said:
If you have TWRP recovery installed and ONLY if you have TWRP installed, boot into bootloader. Issue the fastboot commands:
fastboot format userdata
fastboot format cache
If you do have TWRP installed, this should allow you to boot to TWRP recovery.
See if you can accomplish this and let us know.
Click to expand...
Click to collapse
I went into recovery mode, nothing happens.
View Bootloader logs
Invalid boot image size!
failed to validate recovery image
Boot up failed
iRub1Out said:
So, let me get it straight...
You unlocked the bootloader
You then rooted
Installed recovery
THEN relocked the boot loader?
...why?
You won't be able to do anything to any partition until the boot loader is unlocked again - try that. Unlock the boot loader (make sure to enable it in Dev settings) and then it should all work again.
Click to expand...
Click to collapse
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
Options appear before acceptance and rejection does not appear on the phone screen.
You probably bricked it.
It's been known to happen after 5.1 if you're not careful (or, in this case, relock the BL after modifying)
Why did you relock it? I still can't wrap my head around any reason for doing that?
Sent from my Nexus 6
Leo D said:
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
Options appear before acceptance and rejection does not appear on the phone screen.
Click to expand...
Click to collapse
The phone is bricked. RMA to Motorola
Or if you're feeling adventurous: http://forum.xda-developers.com/showthread.php?t=3059518
brando56894 said:
Or if you're feeling adventurous: http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
Thanks for your help. But there are some questions I still do not understand.
Now the phone connected to the computer and did not see QHSUSB_BULK in Device Manager. In the Device Manager to see BootLoader interface or adb interfaces.
How can I make the phone run QHSUSB_BULK state?