yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] Jack881:
Something moving...I repeated every single command, now I have on the phone Fastboot reason: Sticky bit factory_fastboot

What should I do now?

Thank you
[Moto X Q&A] samwathegreat:
Do this:

fastboot oem fb_mode_clear

fastboot reboot-bootloader

then start over with all the commands I previously listed

I recommend using copy / paste for all the commands just so none get messed up
[Moto X Q&A] Jack881:
I did it: fastboot oem fb_mode_clear and fastboot reboot-bootloader and repeated all the commands, but now I have Partition (boot) Security version Downgraded. Fastboot reason: boot failure. Thank you
[Moto X Q&A] samwathegreat:
OK!

It looks like when you were on one of the other roms, you accepted an OTA to 4.4.3 or 4.4.4.....did this happen?

anyways, do this:

fastboot reboot-bootloader

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 erase cache

fastboot erase userdata

fastboot erase customize

fastboot erase clogo

fastboot oem fb_mode_clear

fastboot reboot

Does it boot?? Hopefully at this point, you boot into android. Fingers crossed.... :fingers-crossed:
[Moto X Q&A] Jack881:
No, gosh! maybe I have to repeat everything? now I have Partition (boot) Security version Downgraded Fastboot reason: Boot failure
[Moto X Q&A] samwathegreat:
I will have to continue helping you later tonight. Have to leave for a bit. I'm still hoping we will be able to recover you but it will take some more work, and we have to run the commands perfect. I'll post back here when I return.
[Moto X Q&A] Jack881:
Thank you! you are an angel! I will wait...
[Moto X Q&A] samwathegreat:
That didn't take too long. OK, let me know when you are ready to resume. Here is next try:

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot erase userdata

fastboot erase cache

fastboot oem fb_mode_clear

fastboot reboot-bootloader

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 erase cache

fastboot erase userdata

fastboot erase customize

fastboot erase clogo

fastboot reboot

Any errors?
[Moto X Q&A] Gus194:
Maybe he should try using Mfastboot on all of the commands instead of just using it on flashing the system...
[Moto X Q&A] Restola:
Samwathegreat... Who are you you amazing person you....
[Moto X Q&A] samwathegreat:
That's certainly valid input and it couldn't hurt. We will try that if the most recent commands don't work. I've helped dozens unbrick, and I've never had to use mfastboot for all commands yet, but again, I see absolutely no reason not to try.

See my sig.....I'm "the most interesting man in the world"..... LMFAO! The dos equis guy cracks me up. I hope everyone gets the humor that my sig is supposed to express...

[MENTION=3269809]Restola[/MENTION] : Just in case you never saw the commercial....here it is: https://www.youtube.com/watch?v=br-svZuja84
[Moto X Q&A] Gus194:
Hmm..that's weird. I have always had to use mfastboot. Normal fastboot just doesn't work for me. Weird lol.
[Moto X Q&A] Gus194:
Try using Mfastboot instead of normal fastboot for all the commands.
[Moto X Q&A] jadeddjay:
if all else fails, did you make a backup?

i ran into a similar problem when i was trying to revert to stock to take the 4.4.4 OTA on vzw. i was trying to flash the original backup that i had and forgot that i had taken on some OTA updates since then. so i got the errors, and the phone kept booting into recovery.

i decided to trying flashing twrp back to try a nandroid or one of the custom roms. lo and behold, after twrp, i was able to boot the phone. not sure if this will work, but worth a try.

twrp can be found here

download it to your adb folder, then

fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
[Moto X Q&A] Jack881:
I tried,,,but the same result...
[Moto X Q&A] Jack881:
Sorry I don't understnd anything...I'm completely ignorant, the only thing I could was flashing using RSD lite. You can help me if you are very specific...Thank you
[Moto X Q&A] g.kohei:
hai

May be You must wait New sprint Firmware 4.4.4 for your moto x.

If new firmware lunched, You can restore moto x.

I'm sorry if I'm mistaken.
[Moto X Q&A] KidJoe:
[MENTION=5972573]Jack881[/MENTION] Pardon my jumping in... there has been a lot that has been suggested and tried... and with the back and forth, I'm hoping I didn't miss anything...

Your device is a Sprint X (XT1049), right? And the newest firmware you had tried flashing was the UK 4.4.2, now you are trying to get back to "stock" Sprint 4.4.2 using Android 4.4.2 Blur_Version.161.44.32.ghost_sprint.Sprint.en.US,

[MENTION=2509024]samwathegreat[/MENTION] has been very successful at helping people in this situation, and I know it could get frustrating trying things again and again, but just hang in there!

Just a few things on my mind after reading every post of this thread...

is this a new install, or existing install of Android SDK, Platform-Tools, and ADB? If existing, can you make sure its up to date? (based on your posts, use C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\SDKManager.exe When it opens, for SHOW, ensure the boxes for Updates/New and Installed are checked. Ensure only those listed as Update Available under Status column are selected. Click the install button. Accept any licenses and install. Follow any on-screen prompts to complete the install)

Do you have the latest Moto drivers installed? Get them from -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

If you properly installed Android SDK, Platform-Tools, ADB and mFastboot, they should be in your windows PATH variable and executable from anywhere on your pc. (Test by opening a command prompt, type... CD \ {press enter} then type mFAstboot and see if you get "unknown command" or if you get the mfastboot help screen.)

create a folder off the root of drive C, and unzip the Sprint 4.4.2 SBF there, rather than under that long path of C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools (so the img, bin and other files of the SBF are in something like c:\sprintrom ) and run mfastboot from there.

Keeping that stuff in mind, use mfastboot for all commands and repeat what [MENTION=2509024]samwathegreat[/MENTION] suggested in Post #12

And finally, you may end up just needing to wait until the Sprint 4.4.4 SBF/FXZ leaks and gets posted.
[Moto X Q&A] samwathegreat:
Thanks KidJoe...

The Sprint variant is XT1056 -- the RW variant is XT1049. Yeah this one is confusing for me as well. The should be very easy once Sprint releases the 4.4.4 SBF - but I would hate to have to wait for that.

What is really confusing to me is why fastboot is throwing an error "security version downgraded" on boot.img -- the Kernel! I've only seen this once before and it was on an early prototype Moto X that had firmware signed with *test-keys*!!

[MENTION=5972573]Jack881[/MENTION] -- KidJoe's advice is all solid, and I recommend trying what he has mentioned here. I'd really hate for you to have to put your phone away in a drawer until the full 4.4.4 SBF is released -- especially considering the OTA isn't even out yet! It could be a while...

If you continue to have issues - there is another method we could try, but it is RISKY. It involves intentionally corrupting the bootloader, forcing the phone into emergency download mode "QHSUSB_DLOAD", and re-flashing the bootloader to re-gain access to fastboot. It is a complicated procedure and one mistake could turn your phone in to a permanent paperweight. I'd really prefer to save this as a last-resort. If it were me, I would be more willing to simply wait until the release of 4.4.4 firmware rather than try this risky procedure.

Hopefully KidJoe's suggestions help and we are able to get you booted into android. I'm still wondering if there's any possibility that either a 4.4.3 or 4.4.4 rom was flashed, or if an OTA was taken to one of these versions. But even that doesn't explain the error you are getting trying to flash boot.img (Kernel).

Please try all methods as suggested, and report back.

Good Luck.
[Moto X Q&A] KidJoe:
[MENTION=2509024]samwathegreat[/MENTION] question.. I know its risky, and I hate to suggest it, but if all else fails... could a work around possibly be to flash the motoboot.img, gpt.bin from the VZW 4.4.4 SBF (the only 4.4.4 we have currently), followed by the rest of the Sprint 4.4.2 parts, then rename 3C_OTA.APK and .ODEX to block OTA? Then when the sprint 4.4.4 sbf finally leaks, fully flash it to get to being consistent?

Like I said, its risky! And I know its not ideal. But it just might do the trick, without taking more drastic steps.
[Moto X Q&A] samwathegreat:
Honestly......there is no reason he couldn't just flash the entire VZW 4.4.4 SBF.... AFAIK, the baseband is fully compatible with the Sprint Moto X and since he is using my GSM SIM-CRACK in order to use the phone on GSM, it shouldn't really be an issue (he's not even using sprint service). Worst case scenario, he might have to flash the baseband from the Sprint Moto X, but even that is probably unnecessary (only if there are radio issues).

Once the Sprint 4.4.4 SBF is released, he could go back to his proper firmware.

He will DEFINITELY have to re-do my entire SIM-Crack procedure since he has already erased modemst1/modemst2 partitions.

I agree that something like this -- neither of us would *normally* recommend, but considering the situation, I don't see that he has much to lose. At the very least, it should boot into android. AND, he *should* be able to perform the entire procedure with RSD Lite.

My opinion: this is FAR less risky than intentionally bricking the BL, and then trying to recover. (Albeit DOES have some risk, and [MENTION=5972573]Jack881[/MENTION] : you will be doing this at your own risk, should you choose to do so). [MENTION=1165307]KidJoe[/MENTION] and I are just trying to help since your phone is in an unusable state - we don't want to be responsible for anything else that goes wrong....I think you understand this since you were already in a pickle when we started attempting to help you.
[Moto X Q&A] KidJoe:
That was my first thought... flashing the full VZW 444 SBF, and if needed the sprint 442 modem files.. But I wasn't sure how compatible they would be (especially as it pertains to the CDMA authentication pieces), so I didn't suggest it. Then again, if he is using the phone in UK, and GSM only it shouldn't matter.
[Moto X Q&A] Jack881:
Hi, first of all thank you for helping, I try to answer your observations:

1)I have both update/new and installed checked, then I clicked on Install 8 packages, I think that's all and now it should be fine

2) Yes I do have the latest Motorola drivers

3) I can't execute mfastboot from c:/> Idk why, but only from the folder platform-tool

4) you mean I should unzip the Sprint 4.4.2 not in platform-tool? should I remove the files I unzipped from platform-tool?

Thank you

[/LIST]
[Moto X Q&A] Jack881:
Anyway since I'm pretty desperate for this new telephone, do u know anyone in San Francisco who is expert and can try the unbrick for me? I went to some shop and even left the device for some hour, but they don't want even try when they see it's bricked...
[Moto X Q&A] Jack881:
Yes indeed I used your SIM unlock procedure since I need the telephone in Europe and I'm here only for a couple of months. Without unlocking the SIM this device for me is useless...

I will do everything you suggest me because anyway this device is useless right now, but you have to consider that I'm not expert at all, really...

Thank you for helping!
[Moto X Q&A] samwathegreat:
OK. I think [MENTION=1165307]KidJoe[/MENTION] and I are both in agreement that you should proceed with trying to flash the FULL Verizon 4.4.4 SBF. You can download it here: http://sbf.droid-developers.org/download.php?device=0&file=940

Try flashing with RSD Lite. If successful, you will need to re-do my ENTIRE SIM-Crack procedure from Step 1.

Hopefully we can at LEAST get you booted into android.

Let us know as to the status.
[Moto X Q&A] Jack881:
Do I have to flash removing the getvar string?
[Moto X Q&A] samwathegreat:
Probably. Do it anyways.
[Moto X Q&A] Jack881:
It says failed to hab check for boot:0x56 preflash validation failed for boot

not good...
[Moto X Q&A] Jack881:
and now I restarted the device and is has the same error...
[Moto X Q&A] samwathegreat:
Ok, please edit the XML and also remove the line containing "oem fb_mode_set"

Turn the device off, boot back into bootloader, and start over with RSD Lite. Advise as to status.
[Moto X Q&A] Jack881:
It say failed to hab check for boot:0x56 preflash validation failed for boot...like before...

Any new ideas?
[Moto X Q&A] Jack881:
Reading in other posts here in XDA, and as I said I'm not an expert, but I was wondering if I have to unlock my bootloader...this guy here fixed this way...http://xdaforums.com/moto-x/general/q-help-moto-x-steps-to-briked-phone-t2550548/page4 it's an idea obviously, andanyway I can't unlock the boot loader if you don't tell me how to do...Thank you!
[Moto X Q&A] KidJoe:
Looking back at the thread, you never said if your bootloader is unlocked or not.

BUT If your bootloader is LOCKED, you should not have been able to flash the UK ROM, of if you attempted it you should have received the preflash validation error when flashing an X rom meant for another carrier. Saying you did flash a UK ROM, makes us think your bootloader is already unlocked.

At this point, I need to ask you... Exactly what model X do you have? What does it say on the back of the device (in the really tiny print)??? Is the bootloader unlocked or not?

---------- Post added at 08:22 AM ---------- Previous post was at 08:02 AM ----------

#3... If you can only execute it from platform-tools folder, then you haven't completely installed it. You need to add the full location of your platform tools folder to the PATH environment variable.

While you are at it, consider moving your SDK folder to the root of Drive C too.

See -> http://www.droidrzr.com/index.php/t...et-up-adb-and-fastboot-for-your-windows-7-pc/ Start at step 4.

The idea behind those steps is two fold... 1. make the path to the platform tools folder shorter (less characters, under less folders), and 2. Add that location to the Windows Path variable so the commands can be executed from any folder.

#4... make a folder off the root of C... such that it would be C:\Sprint (or something else short like C:\ROM) and unzip the SBF there. You want to be able to open a command prompt, change to \SPRINT (CD \SPRINT) and when you type DIR, you see system.img, recovery.img, gpt.bin, etc. then run fastboot flash from there.

And Yes, you can remove the files from the platform-tools folder.
[Moto X Q&A] Jack881:
No, I think my bootloader is locked right now. My model is XT1056 and I typed fastboot oem get_unlock_data to get the code from Motorola and the site says it's unlockable.
[Moto X Q&A] ipodcar:
259

hello

im in this problem too

i think the only thing to do now is wait for update from moto... , if u use the update motorola device manager its going to show you that you have the lastest version.

for me, brasil 4.4.3 , try to install a verizon 4.4.4 , and brick it like you.

i think when brasil 4.4.4 come it fix for me with the moto manager.

try it and tell me it shows your phone. :crying:
[Moto X Q&A] KidJoe:
Even if you already got your code from Moto, their web site will tell you its unlockable.

Boot into FastbootAP/Bootloader mode on the phone. It will tell you the status.
[Moto X Q&A] Jack881:
It says the device is locked. Status code:0
[Moto X Q&A] driike:
First, let me say thanks for the precise and clear instructions. I was having the same problems as these guys were and i could get not get my phone to boot to anything but twrp and bootloader after flashing http://xdaforums.com/moto-x/orig-development/rom-variants-unlocked-bootloader-t2744700

i tried everything hereand nothing would work, adb wouldn't even recognize my phone, i had to install the moto drivers like 3 times for it to pick it up, not sure if that could help these guys, but it let me get back to sprint 4.4.2 :laugh::good:
[Moto X Q&A] Jack881:
I've installed SDK as u said now...
[Moto X Q&A] Jack881:
tried do flash manually, but it doesn't work...
[Moto X Q&A] samwathegreat:
OK, frustrating that you still aren't having success, I know...

Lets try this (using ONLY the files from the 4.4.4 verizon fxz you downloaded):

mfastboot flash partition gpt.bin

mfastboot reboot-bootloader

mfastboot flash motoboot motoboot.img

mfastboot flash logo logo.bin

mfastboot flash boot boot.img

mfastboot flash recovery recovery.img

mfastboot flash system system.img

mfastboot flash modem NON-HLOS.bin

mfastboot erase modemst1

mfastboot erase modemst2

mfastboot flash fsg fsg.mbn

mfastboot erase cache

mfastboot erase userdata

mfastboot erase customize

mfastboot erase clogo

mfastboot reboot
[Moto X Q&A] Jack881:
Do I have to sue the edited string file (without getvar...) or the original?
[Moto X Q&A] samwathegreat:
Why would you need to edit anything? You are flashing manually. This doesn't use the XML file, nor does it use RSD Lite. It uses command prompt and mfastboot binary.
[Moto X Q&A] ipodcar:
help

i did it , but the mfastboot flash partition gpt.bin give an error always, its like an safe to not downgrade

now i have an error thay says

no valid pip block is sp for system

i know there a tons of info of this, but can u say to me here how to fix this one?

i will donate to you if u can help me

thanks
[Moto X Q&A] samwathegreat:
First, those instructions were not intended for you. You really should ask for instructions for your particular scenario before you try something. GOSH! I hope you didn't flash the 4.4.4 vzw rom that I was suggesting Jack to flash.

Anyways, I have another idea for you. BOTH of you, actually.

This will only work if you are unlocked (bootloader). I want you to FIRST flash TWRP custom recovery from here: http://techerrata.com/browse/twrp2/ghost

you will do this by:

mfastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img

NEXT, type this:

mfastboot reboot-bootloader

Now, use the VOL DOWN key to highlight "recovery", and press VOL UP to boot into recovery.

Once in TWRP Recovery

DOWNLOAD The ROM located in this thread with your PC:

http://xdaforums.com/moto-x/development/rom-stock-flashable-t-mobile-t2773675

Now, in TWRP Recovery, Click "Advanced", then "ADB Sideload", then move the slider from left to right to activate ADB Sideload mode.

Put the ZIP file you downloaded in the same folder as the "adb" binary.

Now, in a command prompt, type "adb sideload tmo_4.4.3_flashable.zip"

The zip file should install, and the device should give you the option to reboot. Reboot at this time, and see if you boot into android....

This is relatively safe, because the flashable file ONLY contains the system, and boot.img partitions.

I'm hoping it will at least allow you to get booted successfully, at which time you can consider trying to restore back to your proper ROM.

Let me know how/if it works for you.
[Moto X Q&A] ipodcar:
i put the verizon firware one day after reading this post, i was on 4.4.3 brasil.

the motorola manager says that i have the 260... brasil

now it says partition boot security dowgrade when trying to boot

not bootloader unlocked :crying:

and cant unlock it

any other idea?:confused:
[Moto X Q&A] samwathegreat:
You can attempt to unlock your bootloader and then try the method I have suggested above. You should have NEVER flashed the VZW firmware to your phone. I'm guessing you followed the advice in this thread: http://xdaforums.com/moto-x/general/update-moto-x-mexico-to-4-4-4-vzn-firm-t2828190

If so, you can ask the OP of that thread for suggestions. Myself and other members tried to warn users in that thread that it was a terrible idea, and shouldn't have ever been suggested. You can blame the Original Poster of that thread for not giving any kind of disclaimer what-so-ever. He claims to work for Motorola and has said that his method is perfectly safe - even though we know that not to be true. Myself and others even reached out to him and requested that he put a disclaimer in his original post, but he did not. I suggest reaching out to that individual to help you since you followed his advice and now your phone is in an unusable state.

You can attempt to unlock your bootloader -- just search the forum for how to unlock bootloader. That is not what this thread is about so please search and ask for help in the threads regarding that subject - this isn't the place to discuss bootloader-unlock.

Good Luck
[Moto X Q&A] Jack881:
I have an error when I type mfastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img

does it means I have to unlock the bootloader? Indeed as I wrote above the device says: Device is LOCKED. Status Code: 0

Thank you again for everything.
[Moto X Q&A] samwathegreat:
Yes! No wonder this hasn't worked for you. I thought we already asked you to do that...

Once you unlock follow the manual method I suggested a couple posts back.

The one with the mfastboot commands...
[Moto X Q&A] Jack881:
The error is "invalid image size for partition recovery"

Thanks
[Moto X Q&A] samwathegreat:
Have you unlocked? And did you follow the most recent post in which I provided you with "mfastboot" commands?
[Moto X Q&A] Travisdroidx2:
You have a lot of patience my friend!
[Moto X Q&A] Jack881:
how can I unlock if the 5 strings trick on motorola site says my device isn't eligible to be unlocked? are there tutorials?

Thank you
[Moto X Q&A] Jack881:
I agree with you...
[Moto X Q&A] samwathegreat:
According to your initial posts, you have a Sprint device, correct? The XT1056?

If so, they can all be unlocked. If you are having issues using Motos official unlock site, here are a couple suggestions:

Re-read the instructions, and ensure that you are pasting in the correct "unlock data" with all spaces and [bootloader] messages removed. It should be one single, contiguous string of characters.

Use a different broswer. Others have reported that they had success when trying another browser.

If you DO have an XT1056, there is no reason at all that you shouldn't be able to unlock the Bootloader.

---------- Post added at 11:56 AM ---------- Previous post was at 11:52 AM ----------

Haha! Lots of "patience", AND "patients" ;) (pun intended) Although Mr. Ipodcar was able to successfully de-brick following my advice.

I've helped literally dozens un-brick at this point. I would prefer for them not to brick in the first place, however.

If anyone has suggestions on how to make it more clearly known than it already is about not downgrading or flashing other carrier's roms without knowing the possible consequences, PLEASE let me know....

:D
[Moto X Q&A] Jack881:
yes I have XT1056, I read it on the back.

The string I have is this 9900029318599600#54303633323034384E3800585431303536000000#7478886F2BEDA73B2DFE185E38C4F448E28

3FCFE#1CF71F040C0001000000000000000000

do you see any errors?
[Moto X Q&A] Travisdroidx2:
When entering your unlock string are you removing the spaces? I believe it was 4 spaces.
[Moto X Q&A] Jack881:
Yes, I do. Since you have the string could you kindly try from your pc? I tried both chrome and explorer, but the same result...
[Moto X Q&A] jadeddjay:
you have spaces in there, bro...

9900029318599600#54303633323034384E3800585431303536000000#7478886F2BEDA73B2DFE185E38C4F448E283FCFE#1CF71F040C0001000000000000000000

it worked for me