[REF]The Complete Moto X Guides/Information Thread

1dtms · Feb 18, 2014

I'm still unable to boot into recovery properly, when I do I keep getting the Bootloader unlocked warning screen and it stays there for 5min before booting as normal.
I double checked I enabled USB debugging and unsure on what else to do.
Attached is a screenshot of my working folder and the log from the cmd

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\HTD>cd c:\program files\android\sdk\platform-tools

c:\Program Files\Android\sdk\platform-tools>mfastboot flash recovery twrp-2.6.3.
1-ghost-4.4.img
sending 'recovery' (5902 KB)...
OKAY [ 0.600s]
writing 'recovery'...
OKAY [ 0.829s]
finished. total time: 1.430s

c:\Program Files\Android\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s

c:\Program Files\Android\sdk\platform-tools>fastboot reboot recovery
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable

c:\Program Files\Android\sdk\platform-tools>

http://imgur.com/nzoYZGP

Cozume · Feb 18, 2014

1dtms said:
c:\Program Files\Android\sdk\platform-tools>fastboot reboot recovery
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable

This is the command that is not working. When you get a list like that, what DOS is telling you is that there is a problem with your command syntax. Don't use this command:

fastboot reboot recovery

Use my instructions on the previous page of this thread instead.

Unlocking and Rooting a Dev Ed Moto X

1dtms · Feb 18, 2014

Cozume said:
This is the command that is not working. When you get a list like that, what DOS is telling you is that there is a problem with your command syntax. Don't use this command:

fastboot reboot recovery

Use my instructions on the previous page of this thread instead.

Unlocking and Rooting a Dev Ed Moto X

Yea I was following your instructions also. I tried going into recovery via the phone by using volume down to highlight and volume up to select and thats when it reboots into the bootloader warning screen.

When I boot into recovery my USB is still attached, does that make a difference?

Cozume · Feb 18, 2014

1dtms said:
When I boot into recovery my USB is still attached, does that make a difference?

yes, I think it does. So disconnect from your PC after Step 8.

Cozume · Feb 18, 2014

1dtms said:
Yea I was following your instructions also. I tried going into recovery via the phone by using volume down to highlight and volume up to select and thats when it reboots into the bootloader warning screen.

When I boot into recovery my USB is still attached, does that make a difference?

Did you get rooted?

1dtms · Feb 18, 2014

Cozume said:
yes, I think it does. So disconnect from your PC after Step 8.

So I tried disconnecting the USB after that and reboot to recovery via volume buttons and still nothing. Got to the Warning bootloader unlocked screen again

Cozume said:
Did you get rooted?

I thought that's the process I'm trying to do right now?
I am unlocked though, got my code from motorolla and entered it in

Cozume · Feb 18, 2014

1dtms said:
So I tried disconnecting the USB after that and reboot to recovery via volume buttons and still nothing. Got to the Warning bootloader unlocked screen again

For some reason, TWRP is not "sticking" for you.

You are using mfastboot to flash TWRP, correct? Then booting back into the bootloader then disconnecting from the computer and using the buttons to get into recovery?

1dtms · Feb 18, 2014

Cozume said:
For some reason, TWRP is not "sticking" for you.

You are using mfastboot to flash TWRP, correct? Then booting back into the bootloader then disconnecting from the computer and using the buttons to get into recovery?

Yes, from the screenshot and command line, as far as I know I am using the mfastboot.exe.
What do you mean by booting back into the the bootloader?

because I never exit out of there after i flash TWRP

Cozume · Feb 18, 2014

1dtms said:
Yes, from the screenshot and command line, as far as I know I am using the mfastboot.exe.
What do you mean by booting back into the the bootloader?

because I never exit out of there after i flash TWRP

Try this:

1) Put device in bootloader mode while not connected to PC using the buttons (Volume Down + Power);
2) Connect device to PC using USB cord;
3) mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
4) fastboot reboot-bootloader
5) Disconnect device from PC;
6) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and then pressing the Volume Up button to select the recovery mode; and
7) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.

If that doesn't work, repeat but omit step 4.

---------- Post added at 09:11 PM ---------- Previous post was at 08:45 PM ----------

1dtms said:
after i flash TWRP

if it still isn't working, perhaps your copy of TWRP is corrupted and you should try to download it again?

dray_jr · Feb 19, 2014

Cozume said:
Try this:

1) Put device in bootloader mode while not connected to PC using the buttons (Volume Down + Power);
2) Connect device to PC using USB cord;
3) mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
4) fastboot reboot-bootloader
5) Disconnect device from PC;
6) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and then pressing the Volume Up button to select the recovery mode; and
7) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.

If that doesn't work, repeat but omit step 4.

added to the OP because i think it is the best step by step i have seen for this issues. but i think you might be on to something i think his download or TWRP might be Corrupt like you said it is really the only thing i can think of.

Jayrod76 · Feb 19, 2014

When I originally unlocked my X , I msfastbooted TWRP..went in..etc. I made a backup a few minutes later . A few days later I was testing a deodexed build so prior to that flash, I made another backup. The deodexed build was slightly borked so I decided to wipe and restore my second backup. It failed so I decided to wipe again and restore first backup..it failed as well. I have had issues with fastbooting and RSD to stock on my laptop. Both freeze at different spots. RSD hangs on system. I have used this laptop to flash images on my Bionic,RAZR and M as well as using ODIN on my S4. After trying on a desktop that had not had any drivers,etc.installed prior..I was able to get back to stock. I believe that this may be a driver conflict between Sammy and Moto.
Just putting this out there for any other Sammy/Moto owners.

DEV X

Cozume · Feb 19, 2014

Jayrod76 said:
I believe that this may be a driver conflict between Sammy and Moto.
Just putting this out there for any other Sammy/Moto owners.

I had a GNex before my Moto X and I definitely have a driver problem. I need to just suck it up and get rid of all of the drivers and start from scratch.

Wool02 · Feb 19, 2014

Thank you for this. I did find one issue though when trying to return to stock and relock the bootloader. In order to relock the bootloader you must do the following:

1. fastboot oem lock begin
2. flash stock firmware (per OP)
3. fastboot erase userdata
4. fastboot erase cache
5. fastboot oem lock

If you do not begin with Step 1, relock will fail. If you do not first perform Step 3 and Step 4, relock will fail. SIAP!

Cozume · Feb 19, 2014

Wool02 said:
Thank you for this. I did find one issue though when trying to return to stock and relock the bootloader. In order to relock the bootloader you must do the following:

1. fastboot oem lock begin
2. flash stock firmware (per OP)
3. fastboot erase userdata
4. fastboot erase cache
5. fastboot oem lock

If you do not begin with Step 1, relock will fail. If you do not first perform Step 3 and Step 4, relock will fail. SIAP!

Relock your Moto X Bootloader

After downloading the image for your device:

Unzip the image.

Put your device in fastboot mode.

NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility

Follow the flashing steps in the .xml file that was included in the package.

A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:

fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot

You also have the option to erase all the data on your device with
fastboot erase userdata
fastboot erase cache

After performing this sequence, you can relock your device with
fastboot oem lock

Wool02 · Feb 19, 2014

Wool02 said:
Thank you for this. I did find one issue though when trying to return to stock and relock the bootloader. In order to relock the bootloader you must do the following:

1. fastboot oem lock begin
2. flash stock firmware (per OP)
3. fastboot erase userdata
4. fastboot erase cache
5. fastboot oem lock

If you do not begin with Step 1, relock will fail. If you do not first perform Step 3 and Step 4, relock will fail. SIAP!

Cozume said:
Relock your Moto X Bootloader

After downloading the image for your device:

Unzip the image.

Put your device in fastboot mode.

NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility

Follow the flashing steps in the .xml file that was included in the package.

A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:

fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot

You also have the option to erase all the data on your device with
fastboot erase userdata
fastboot erase cache

After performing this sequence, you can relock your device with
fastboot oem lock

Cool. My point was that relocking the bootloader using the OP info (and the same instructions above) did not work unless I started with 'fastboot oem lock begin'.

hellt · Feb 20, 2014

Guys, please, advise =)
I have a Dev ed moto x (so I assume my bootloader is already unlocked), I already have got the OTA 4.4.2 android and my build is KXA20.16-1.25
All I need is to get the root access to delete "emergemcy alerts" app

What is the most modern way to get the root access with less pain/bugs/etc?
To flash custom recovery (ie TWRP) or use the SlapMyMoto method?

mschumacher69 · Feb 20, 2014

hellt said:
Guys, please, advise =)
I have a Dev ed moto x (so I assume my bootloader is already unlocked), I already have got the OTA 4.4.2 android and my build is KXA20.16-1.25
All I need is to get the root access to delete "emergemcy alerts" app

What is the most modern way to get the root access with less pain/bugs/etc?
To flash custom recovery (ie TWRP) or use the SlapMyMoto method?

Your bootloader is not already unlocked. So first, you have to unlock your BL through the Moto website and then flash TWRP and then SuperSU. It's as easy as that.

SlapMyMoto is for devices with a bootloader that cannot be unlocked...

triton302 · Feb 20, 2014

Alright...

I followed the guide for the locked bootloader for my fiance's VZW locked X.

I've been dealing with bricking ever since. Now it's to the point where it's giving me the CID bullcrap, and I can't flash anything that doesn't fail.

So, am I f*cked to the point of no return for this damn thing?

Cozume · Feb 20, 2014

triton302 said:
Alright...

I followed the guide for the locked bootloader for my fiance's VZW locked X.

I've been dealing with bricking ever since. Now it's to the point where it's giving me the CID bullcrap, and I can't flash anything that doesn't fail.

So, am I f*cked to the point of no return for this damn thing?

This is the thread you need to be posting on:

Slap My Moto

mschumacher69 · Feb 20, 2014

triton302 said:
...my fiance's VZW locked X.

Ouch...

[REF]The Complete Moto X Guides/Information Thread

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts