Database Develop

[Q] How to start over?

I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.

atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv

Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.

Redownload?

Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?

I would redownload everything and try agian

littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?

atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?

I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App

http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium

wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.

Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.

i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721

I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!

i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.

How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).

i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop

Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.

re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used

Downgrade Atrix HD to ICS using RSD

Here i have finally found the way after a long search in forums to downgrade Atrix HD using RSD.
It is simple.
Download your required firmware from here : Fastboot files
or
Mirror
Download rsd lite from here : RSD lite 5.4.4
now extract the firmware zip file and open the .xml file with notepad. here you need to do 2 things.
1) remove the two lines containing "getvar.step operation=”getvar” var=”max-download-size”
2) remove the line "<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="5EE7E4CB385C3487F97E7B0431F6B297" />"
now save the .xml file, zip it again and flash with RSD lite.:victory:

http://forum.xda-developers.com/showthread.php?t=2283788
Really..
Sent from my PACMAN MATRIX HD MAXX

I posted a way in the general forum while back plus the Myth tools do this really easily as well. I don't think you searched the forums enough.

Neither of y'all looked around the forums.. I posted your link.
Sent from my PACMAN MATRIX HD MAXX

To be fair, in an age where people are looking for a one-click type solution to handle things I wanted to learn the longer way of doing something and just shared my result. Like all things computer-related, there is more than one way to skin a cat. Next someone will do a "one-click" where every process of rooting and unlocking the bootloader is automated, right down to installing the ROM and all you have to do is press Enter once the device has hit the specific state. Myth still requires you to back out and return to the menu.
Not saying one-clicks aren't handy. They are. Not saying I couldn't have searched the forums more. I could have, but I took a longer way of doing something and learned in the process. Good for me, I'll get myself a cookie.

wamsille said:
To be fair, in an age where people are looking for a one-click type solution to handle things I wanted to learn the longer way of doing something and just shared my result. Like all things computer-related, there is more than one way to skin a cat. Next someone will do a "one-click" where every process of rooting and unlocking the bootloader is automated, right down to installing the ROM and all you have to do is press Enter once the device has hit the specific state. Myth still requires you to back out and return to the menu.
Not saying one-clicks aren't handy. They are. Not saying I couldn't have searched the forums more. I could have, but I took a longer way of doing something and learned in the process. Good for me, I'll get myself a cookie.
Click to expand...
Click to collapse
Learning by doing is the best way to achieve something I'm not a coder officially and all I made was learned from google Just want to make a tools to decrease the number of steps/command lines which I must type (I'm very lazy )

you just saved my life thank you so very much

Downgrade
I have been trying for a while now to get rsd to flash me back to stock but every firmware I have tried dosn't work and myth tools don't work either would this possibly do the trick? Thank you for your answers.

Thanks but I'm just curious. Why you guys want to downgrade to ICS?

mm166 said:
Thanks but I'm just curious. Why you guys want to downgrade to ICS?
Click to expand...
Click to collapse
HDMI mirroring works better on ICS, that's the only reason I can see so far.

atrix2 hacker said:
I have been trying for a while now to get rsd to flash me back to stock but every firmware I have tried dosn't work and myth tools don't work either would this possibly do the trick? Thank you for your answers.
Click to expand...
Click to collapse
you have to remove the 2 lines mentioned in the op (original post) after you download the rom make sure to extract the .xml file and do exactly as mentioned in the OP that's what i did and it worked 100% and then replace the old .xml file with the new one and let rsd lite do the rest.

aliamin86 said:
you have to remove the 2 lines mentioned in the op (original post) after you download the rom make sure to extract the .xml file and do exactly as mentioned in the OP that's what i did and it worked 100% and then replace the old .xml file with the new one and let rsd lite do the rest.
Click to expand...
Click to collapse
after not using this phone for a couple of months this thread saved my life again thanks op

This should be in q&a/ troubleshooting or atrix HD general. This forum is for development only. The reason I say this is because I get notifications from the development forum but not the others, so I don't want to be notified by "downgrade Matrix HD to ICS" (a topic that has been covered numerous times) in the Dev forum, when that isn't news. Read before you post. Search before you post. And when you do post, put it in the right place. It keeps everything clean and everyone happy.
Sent from my MB886 using Tapatalk

RSD Lite problem when returning to stock

I have been trying for a while now to flash the stock VZW 4.4.2 firmware with RSD Lite. I have deleted the "<step operation="getvar" var="max-download-size" />" line from the XML file. However, when I get it going with flashing stuff, I still see a "getvar max-download-size" before every operation, and once it gets to system.img, it will only download the "max" of 805,306,368 bytes, instead of the entire file.
I have done all this twice before and had no problems, so I have no idea what is going on this time. It is probably something stupid, but any help would be appreciated.

Which version of Android are you currently running?

ShaneRitz said:
I have been trying for a while now to flash the stock VZW 4.4.2 firmware with RSD Lite. I have deleted the "<step operation="getvar" var="max-download-size" />" line from the XML file. However, when I get it going with flashing stuff, I still see a "getvar max-download-size" before every operation, and once it gets to system.img, it will only download the "max" of 805,306,368 bytes, instead of the entire file.
I have done all this twice before and had no problems, so I have no idea what is going on this time. It is probably something stupid, but any help would be appreciated.
Click to expand...
Click to collapse
Yep, just flashed it yesterday exactly the way you did, and that appears appears on the phone's screen, but you need to wait and it should finish flashing without any problems.

[Q] XT861 - Problems with Fastboot / RSDlite?

Hi, newb here, I'm having some trouble.
So I'm not positive what device I have, it claims to be a Droid 3 when I look up the IMEI, it tells me it's a Motorola Milestone 3, it seems to have a similar kind of Radio Lock to the Droid 2 Global, and it's carrier information is PCTI.
I'm trying to flash Solana 2.3.6-5.5.1.1 and, whenever I go through the normal XML and try to flash, it gets done with MBM and the other stuff, but when it starts to try and flash Image files (anything .img) it hangs, and fails. Then the Bootloader has the title AP Fastboot Flash Mode (S) (Flash Failure)
Now, from another post (http://forum.xda-developers.com/showthread.php?t=2174433) I got the awesome idea to remove any references to .img in the XML, and just do the beginning part, it looks like this:
Code:
<steps interface="AP">
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="072e86d6f0bf608d36d68e8a6a167a88" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="f402e5e66e6267a2e416decc1b827268" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="97706c215fce01e8ac9f7d9428a035fd" />
<step operation="flash" partition="cdt.bin" filename="cdt.bin" MD5="c2ebfc5cd02bf87b372f818a871712d5" />
<step operation="reboot-bootloader" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="flash" partition="lbl" filename="lbl" MD5="b7714d7ed32ae556201405e239d43447" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="06c07c2970460a4e656a3206859a3617" />
<step operation="flash" partition="ebr" filename="ebr" MD5="820ca594391b56282485bbf1af20da99" />
<step operation="flash" partition="mbr" filename="mbr" MD5="ad0d2e66dd6770bd9fb77fc2f0c8d154" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="40435eaf876d217734cbab91c234f9d1" />
<step operation="reboot-bootloader" />
Now I know this is not the whole thing, it's just to show you part of it and what "actually works."
This removes the (flash failure) tag and allows me to reboot the phone without it hanging on the bootloader, this might help other people too, so, hopefully it does!
Now, I try to flash in the individual image files (See, I tried to do that with the chinese radio.img to try and unlock my radio) but every time I try to use an image file in fastboot (I'm using the moto-fastboot.exe) it always hangs, and fails to flash the file. It'll just sit there for hours doing nothing.
To explain above better, the program output for the cmd moto-fastboot flash radio radio.img is:
sending 'radio' (14406 KB)...
And it just sits there, I eventually use ctrl-c to break the program out and get back to the command line. Quickly tapping the button to shut the phone off then back on puts it back at the bootloader with (Flash Failure) like written above.
This is all on an old Windows XP Professional machine using maybe usb2.0? Maybe? I doubt it, lets assume its not. Unless the phone wouldn't connect and interface at all with something prior to usb2.0, then I must have it because it connects and works with the moto drivers.
Can anybody help me out? I just would like to get this phone working on my cheep walmart gsm plan. Expensive phones make me cry because I'm poor :crying:

Did you root 1st?
Sent from my LT30p using Tapatalk

Don't need to root to flash stock firmware
Sent from my Amazon Kindle Fire using Tapatalk
---------- Post added at 10:07 AM ---------- Previous post was at 10:03 AM ----------
Is there a label under battery? If so what model number xt861?
Sent from my Amazon Kindle Fire using Tapatalk
---------- Post added at 10:27 AM ---------- Previous post was at 10:07 AM ----------
I would flash it with moto-fastboot.exe
see my Unbrick Moto device with moto-fastboot.exe

Durteedee said:
Did you root 1st?
Sent from my LT30p using Tapatalk
Click to expand...
Click to collapse
Yes I did, I believe I'm still rooted, I'll have to double check, I remember doing it with, I think the motofail exploit using a .jar file I picked up, it worked right off the bat.
sd_shadow said:
Don't need to root to flash stock firmware
Sent from my Amazon Kindle Fire using Tapatalk
---------- Post added at 10:07 AM ---------- Previous post was at 10:03 AM ----------
Is there a label under battery? If so what model number xt861?
Sent from my Amazon Kindle Fire using Tapatalk
---------- Post added at 10:27 AM ---------- Previous post was at 10:07 AM ----------
I would flash it with moto-fastboot.exe
see my (I cannot post external links, sorry! Had to modify the quote)
Click to expand...
Click to collapse
Yes there is, I'll find that for you in a second:
Right beside the model field it has the following: XT861, need any other numbers from there?
I've tried to do any kind of flashing with Fastboot and run into the same problem, but I will review the document you're linking to and try the process step by step again, I'll post results in a reply.

Sorry @sd_shadow , it doesn't seem to be working, I'm waiting on the flash to go through but it's not, I literally put in moto-fastboot flash boot boot.img, the output is sending 'boot' (8192 KB)... and there's no change in output on the phone in the fastboot screen, no progress bar, nothing, just, white letters on black, battery ok, ok to program, Transfer Mode: USB connected. If it doesn't make any progress in a few minutes I'll probably ctrl-c out like I have been so I can reboot the phone and use that method I found to get out of the fastboot loop.

Don't think there is anything that happens on phones screen, just sending and writing on pc.
Sent from my XT894 using Tapatalk
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------
If pc doesn't say writing, file likely is not compatible
Sent from my XT894 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:14 PM ----------
You shouldn't need to flash boot, preinstall, system...just radio and then fix or replace /system/build.prop that matches radio
Sent from my XT894 using Tapatalk

sd_shadow said:
Don't think there is anything that happens on phones screen, just sending and writing on pc.
Sent from my XT894 using Tapatalk
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------
If pc doesn't say writing, file likely is not compatible
Sent from my XT894 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:14 PM ----------
You shouldn't need to flash boot, preinstall, system...just radio and then fix or replace /system/build.prop that matches radio
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
That's a little disturbing, if the file isn't compatable, then what file do I need? Lets say I wanted to flash on stock firmware again, there's not too many options for the xt861 for 2.5.6 firmware... and I tried to flash the radio, same problem, from both the supposed original firmware from the firmware site, and the chinese one, both just hang and do nothing. ADB works, but Fastboot seems to never go past sending. RSD does a sending step, hangs, and then fails, just using fastboot fails too. The only thing that works sending through to fastboot, is if I remove all of the commands that contain .img in the xml from the original firmware, that stops the fastboot loop bug.
Is there perhaps somehow I can use the shell in ADB in SU to do what Fastboot is trying to do?

saadow said:
That's a little disturbing, if the file isn't compatable, then what file do I need? Lets say I wanted to flash on stock firmware again, there's not too many options for the xt861 for 2.5.6 firmware... and I tried to flash the radio, same problem, from both the supposed original firmware from the firmware site, and the chinese one, both just hang and do nothing. ADB works, but Fastboot seems to never go past sending. RSD does a sending step, hangs, and then fails, just using fastboot fails too. The only thing that works sending through to fastboot, is if I remove all of the commands that contain .img in the xml from the original firmware, that stops the fastboot loop bug.
Is there perhaps somehow I can use the shell in ADB in SU to do what Fastboot is trying to do?
Click to expand...
Click to collapse
I may have found an answer, I did a little bit of digging on Google, and I may have been barking up the wrong tree the entire time, nTelos is also related to PTCI, so it may stand to reason that I want the nTelos version of the firmware and not the other one, I didn't even think of that as a possibility until I mulled over what you were saying Shadow. Thanks for kicking a few neurons in the rear end and helping me think. If this doesn't work though, is there any other reason why a file in fastboot wouldn't send a file? I did find out I don't have USB 2.0 ports, I have one somewhere on the computer but I don't know where, and it wasn't a well documented machine when I got it. It was built by a local company.

Yep, okay, that was just the ticket, everything from the nTelos firmware is flashing in RSD, that's a good sign! If I can't succeed with this, I can unroot it and flash it back to stock, then sell it as a sim unlocked phone. Unless selling it rooted might be better. I'd rather it work though. So now that I did this, I need to figure out how to flash the radio.img.
Learning moment for anyone who is newbish like me, if you don't see your carrier included in the name on a firmware for your device, search the name of the carrier in your phone and the name of one of the carriers responsible for that particular firmware you're looking up. It will save you a lot of aggravation!

Okay, got it!
The start of my whole problem had to be the firmware, whoever I bought it from had some manner of yokel firmware on there that didn't behave the way it should have, it didn't ever want to flash and so finally I found the right firmware, got it on, and then every step worked like it was supposed to
So everyone knows, the nTelos version of the phone works with the simple method of flashing the chinese radio.img
I used this link here: http://forum.xda-developers.com/showthread.php?t=1406812
I also made sure to change the following lines to my build.prop:
Code:
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.default_network=7
to
Code:
ro.mot.phonemode.vzwglobalphone=0
ro.telephony.default_network=3
You'll want to reboot the phone into fastboot first (the instructions don't include that, but it would be self explanatory to anybody but a newb) and then follow their instructions to the letter, it'll go quick and painlessly (so much more painlessly than the droid 2 global was)
Thanks everybody for the help!

Moto X XT1052 Stock ROM Request.

Hello,
Guys i have got Moto X XT1052 from a friend for few days. To mainly fix it. Actually, whenever i turn phone on. It keeps on crashing all apps, like Unfortunately, Launcher has stopped, calender and so on. It's not allowing me to touch anywhere else. So i would like to restore it. I checked all threads and found fine solution for flashing. I can do it. But those who uploaded ROMs on filefactory, it's kinda old. And downloading speed is really slow. Even when my net speed is double of it. I should get 300 KB/s some. But i am getting 50KB/s from their site. So i need help on this. If anyone can upload that ROM(XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip) on any other site like mediafire, Google files or torrent. I will really appreciate it. Please i urgently need it. Let me know if anything else to be done too. Because on current bootloader showing Device is Lock. And i saw youtube videos, most of them had Device is unlock. I am using this method, please take a look and let me know. Thanks. http://forum.gsmhosting.com/vbb/f78...to-x-2nd-gen-firmware-flashing-guide-1877668/

You can try to look here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola/XT1052/
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X/XT1052/
+
4.4.4 Retail GB (XT1052_RETAIL-​GB_4.4.4_KXA21​.12-L1.26_56_c​id7_CFC_1FF.xm​l.zip)
4.4.4 Retail DE (XT1052_RETAIL-​DE_4.4.4_KXA21​.12-L1.26_54_c​id7_CFC_1FF.xm​l.zip)
4.4.4 Retail EU (XT1052_RETAIL-​EU_4.4.4_KXA21​.12-L1.26_54_c​id7_CFC_1FF.xm​l.zip)

http://forum.xda-developers.com/showthread.php?t=2976596

Here you go - https://mega.co.nz/#!U8NkgQqA!2yUsrJlNp0j_8ttzjJmHS4C4hh9cQ__vXtNKfmlm8cg
Sent from my Moto X using XDA Free mobile app

Guys, stuck in mid. Can you tell me, that do i need to unlock device first to get back to stock ROM? I tried manual flashing and RSD method too. But both failed to do anything. All apps still crashing. :l Please help me on this? New for Moto X. :l Thanks.

DarKrypton said:
Guys, stuck in mid. Can you tell me, that do i need to unlock device first to get back to stock ROM? I tried manual flashing and RSD method too. But both failed to do anything. All apps still crashing. :l Please help me on this? New for Moto X. :l Thanks.
Click to expand...
Click to collapse
First you dont need to unlock or lock your bootloader. Have you already tried to just go into recovery mode and factory reset the phone? How did the error start? What did your friend try to do, when he got the error first? What is the EXACT error message you get, while flashing?
Sent from my XT1052 using XDA Free mobile app

N00BY0815 said:
First you dont need to unlock or lock your bootloader. Have you already tried to just go into recovery mode and factory reset the phone? How did the error start? What did your friend try to do, when he got the error first? What is the EXACT error message you get, while flashing?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
When i do factory option in recovery mode, it just boot up phone normally. And then it shows "Unfortunately, the process com.google.process.gapps has stopped". Then it keeps poping up with more crashes, like launcher, google play services. It hardly let me touch somewhere else. And if i tap "Ok" quickly, phone just shut down. Even in recovery mode, i tried selecting "Recovery" option, and it shown me "Boot up failed". And actually my friend don't know much about phones and all this. He said it just started happening. :l Maybe he installed some weird app. And i don't get any error while flashing. Everything went fine. But when i check phone it doesn't change anything else. Same as old. Even when i erased all user data. Will just erasing data will fix it? Then after that i can do full stock ROM flashing.

Why i am not getting back to stock guys. Everything going fine. Just i checked a thread, where a guy said he is getting that "Variable not supported" something. I am getting same thing. So what can i do? :l Please help me to get back to stock ROM. I really need to fix it. Thanks.

Try motofirmware.center to try and see if they have the ROM you're looking for. I went to this site for the stock ROM for my XT1060 Developer Edition and was able to find it there. It saved me when I messed up my phone earlier this week. When you flash the stock ROM using the RSDLite program, it will do a wipe on your phone as it flashes it to your phone. When you boot up the phone after flashing the stock ROM, your programs should reinstall just fine on the phone once you log on to your Google Play account.
Cindy

DarKrypton said:
So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
Click to expand...
Click to collapse
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
copy and paste the terminal output here using code tags.
Click to expand...
Click to collapse
You have been asked multiple times for the exact error messages. We don't know why your computer wont work... But your computer pretty much tells you each time with a specific message. You need to give us those messages.
Consider the fact that there MAY be someone here who doesn't care about you or your phone, but knows the answer. If you make it easy that person MAY help you. If you post paragraph after paragraph of text describing the error message, rather then the 1 line error message they probably wont read. Be as direct as possible, show us what you have done (I didn't really flow many of you links, why should we have to chase down this information to give you free tech support?)
Like this:
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash _____ rom using _____ tool, but recivied the following error message
Code:
word for word error message
I found this thread: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 on returning to stock using RDS light, and used
RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip from http://motofirmware.center/files/category/9-ghost/
There was an error durring fasboot, and there seem to be no changes to the phone.
Code:
130 [email protected] ~ % fastboot oem fb_mode_set :(
< waiting for device >
^C
130 [email protected] ~ %
Click to expand...
Click to collapse
Someone can drop in, and with out much work tell what I have done, and see that it is not working because fastboot cannot find the device.

scryan said:
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I am not sure why you follow other peoples tutorials, then ask US about them. For help with your tutorial, ask the people who wrote that tutorial. If you want help here, try first with OUR tutorials. I don't say this to be mean, but we are unfamiliar with other tutorials and can only really support ours.... It gives us a standard to reference back to.
From the first page, "Returning to 100% stock with RDS or manual"
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 about downgrading, shouldn't be an issue but not a bad idea to double check what bootloader you have.
Also make SURE you have the right firmware.
Read those threads, and if you still have an issue copy and paste the terminal output here using code tags.
Rather then downloading it from random websites, you know Moto hosts the official firmwares, at least for DE phones on their website so you can get the most recent, verified version direct from the official source rather then going through random unofficial mirrors...
Click to expand...
Click to collapse
Actually mate, i have been using that link only. But when that didn't worked. I tried others. :l But they failed too. This link shown perfect method. But i have no idea why it's keep happening. This seems more confusing that flashing ROMs on my Canvas HD. It was easy. But this is getting crazy. Please help me with this. I tried from fresh. But it's still same. Maybe you could help me with team viewer or something? Plus one thing i would like to tell you. On most tutorials they said, delete a line "<step operation="getvar" var="max-download-size" />" even it's written in that link too, which you posted. But thing is that, i extracted my firmware, and it's already not in XML file. So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.

You have a locked bootloader, your not just flashing a rom, you need to use fastboot, a standard android tool, to restore your phone.
Your not going to flash a rom, you will be downloading that SBF you have been linked to, unzipping it and flashing each partition, AS STATED IN THE RSD THREAD.
DarKrypton said:
So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
Click to expand...
Click to collapse
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
copy and paste the terminal output here using code tags.
Click to expand...
Click to collapse
You have been asked multiple times for the exact error messages. We don't know why your computer wont work... But your computer pretty much tells you each time with a specific message. You need to give us those messages.
Consider the fact that there MAY be someone here who doesn't care about you or your phone, but knows the answer. If you make it easy that person MAY help you. If you post paragraph after paragraph of text describing the error message, rather then the 1 line error message they probably wont read. Be as direct as possible, show us what you have done (I didn't really flow many of you links, why should we have to chase down this information to give you free tech support?)
Like this:
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash _____ rom using _____ tool, but recivied the following error message
Code:
word for word error message
I found this thread: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 on returning to stock using RDS light, and used
RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip from http://motofirmware.center/files/category/9-ghost/
There was an error durring fasboot, and there seem to be no changes to the phone.
Code:
130 [email protected] ~ % fastboot oem fb_mode_set :(
< waiting for device >
^C
130 [email protected] ~ %
Click to expand...
Click to collapse
Someone can drop in, and with out much work tell what I have done, and see that it is not working because fastboot cannot find the device.

Ok, let me clear everything to you.
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash Moto X XT1052 (XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml) rom posted above by "athulele" using "fastboot" tool, but recivied the following error message. This is first error, with fresh installing. Trying with first command. "fastboot oem fb_mode_set"
Code:
"fastboot" is not recognized as an internal or external command, operable program or batch file.
It's obviously because "fastboot" and ADB are not present in ROM folder. So i guess i need to copy all files from a software i installed "Minimal ADB and Fastboot" as per other tutorials. Which made me more confused. So i want to go with your tutorial.
Second thing, if i make copy of files in ROM folder. It starts taking commands, but with another error. Which is :
Code:
C:\Users\(Username)\Desktop\XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.x
ml>fastboot flash partition fpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
error: cannot load 'fpt.bin': No error
After that, i think i should not continue. After this maybe please take a look. Let me know where i am doing wrong. Must be totally wrong where i copied those files in ROM folder. I couldn't continue without them. Because of that error. Let me know if i am missing any driver. Because as fasr i know i installed all latest drivers. Let me know. Thanks.
Click to expand...
Click to collapse

DarKrypton said:
Ok, let me clear everything to you.
Click to expand...
Click to collapse
Try the commands without "fastboot OEM mode set". Also if your friend had completely stock system, you can try flashing only system.img, boot.img, recovery.IMG
After you flash this, erase data by " fastboot erase userdata" this will erase everything including sdcard .
After that "fastboot erase modemst1" and "fastboot erase modemst2" to clear modem cache. Then try rebooting into system.
Also, you had typed fpt instead of gpt. That's why you got the error
Sent from my Moto X using XDA Free mobile app

athulele said:
Try the commands without "fastboot OEM mode set". Also if your friend had completely stock system, you can try flashing only system.img, boot.img, recovery.IMG
After you flash this, erase data by " fastboot erase userdata" this will erase everything including sdcard .
After that "fastboot erase modemst1" and "fastboot erase modemst2" to clear modem cache. Then try rebooting into system.
Also, you had typed fpt instead of gpt. That's why you got the error
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
No no, sorry my bad. Typing mistake here. I did gpt.bin. This time i did mistake, that's why got "error: cannot load 'fpt.bin'". Otherwise it's only "(bootloader) Variable not supported!" And status at end "OKAY" then next command. And i can't take risk for flashing few files only. Because my friend have no idea on this. It's all on me, what can be done. I need to flash full ROM to match up future OTA updates. It's somewhere wrong in copying files in ROM folder. I tried those commands, as per tutorial. So it didn't worked. :l

DarKrypton said:
No no, sorry my bad. Typing mistake here. I did gpt.bin. This time i did mistake, that's why got "error: cannot load 'fpt.bin'". Otherwise it's only "(bootloader) Variable not supported!" And status at end "OKAY" then next command. And i can't take risk for flashing few files only. Because my friend have no idea on this. It's all on me, what can be done. I need to flash full ROM to match up future OTA updates. It's somewhere wrong in copying files in ROM folder. I tried those commands, as per tutorial. So it didn't worked. :l
Click to expand...
Click to collapse
I don't exactly know whether you need an unlocked bootloader to flash via fastboot. But if you don't want to, then you can try factory reset from stock recovery or from the bootloader. There's plenty of guides all around for stock recovery.
Sent from my Moto X using XDA Free mobile app

athulele said:
I don't exactly know whether you need an unlocked bootloader to flash via fastboot. But if you don't want to, then you can try factory reset from stock recovery or from the bootloader. There's plenty of guides all around for stock recovery.
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
Naw, fastboot works with locked boot loader. It should be able to reflash on locked as long as the files are signed.
athulele, I think he said he tried factory reset...
Dark, your correct that you need to be in the same directory as that fastboot command (note there is also a mfastboot command. Motorola modified the stock android fastboot tool so it could flash larger partitions, at least from my understanding). If your not in the directory that executable is your OS will not be able to find it (unless you add it to your systems path, but if you don't know how or what that is easier to just make sure the EXE is in the folder your working out of)
The second time you tried to run it it looked like it worked perfectly right? but the correct command is
Code:
fastboot flash partition gpt.bin
Note the syntax is
fastboot [operation] [partition name] [file], so when you gave it the wrong file it correctly said it can't do it. Everything fine here.
again MAKE SURE your flashing the right files, double check your typing the command correctly (Copy and paste is good, but make sure you don't copy any extra characters at the begining or end of the line before you press enter to run the command)
About the worry over only flashing some paritions: You right to worry, you don't want to do this. HOWEVER, if you have the right files they should work. Go through that list of commands one by one. Figure out why any one command fails and get it to work before moving on... But if your flashing the same thing as is already on the phone, your not going to miss match partitions because your flashing the same version of each partition back over itself just trying to fix what ever one is messed up...
But yeah, make sure you got those files, run through those fastboot commands and post the output here. Copying too much of the console output is probably better then too little.

scryan said:
Naw, fastboot works with locked boot loader. It should be able to reflash on locked as long as the files are signed.
athulele, I think he said he tried factory reset...
Dark, your correct that you need to be in the same directory as that fastboot command (note there is also a mfastboot command. Motorola modified the stock android fastboot tool so it could flash larger partitions, at least from my understanding). If your not in the directory that executable is your OS will not be able to find it (unless you add it to your systems path, but if you don't know how or what that is easier to just make sure the EXE is in the folder your working out of)
The second time you tried to run it it looked like it worked perfectly right? but the correct command is
Code:
fastboot flash partition gpt.bin
Note the syntax is
fastboot [operation] [partition name] [file], so when you gave it the wrong file it correctly said it can't do it. Everything fine here.
again MAKE SURE your flashing the right files, double check your typing the command correctly (Copy and paste is good, but make sure you don't copy any extra characters at the begining or end of the line before you press enter to run the command)
About the worry over only flashing some paritions: You right to worry, you don't want to do this. HOWEVER, if you have the right files they should work. Go through that list of commands one by one. Figure out why any one command fails and get it to work before moving on... But if your flashing the same thing as is already on the phone, your not going to miss match partitions because your flashing the same version of each partition back over itself just trying to fix what ever one is messed up...
But yeah, make sure you got those files, run through those fastboot commands and post the output here. Copying too much of the console output is probably better then too little.
Click to expand...
Click to collapse
One thing i would like to ask mate. I am gonna start fresh installation. From laptop now. I noticed one thing, that on
Code:
"fastboot erase modemst1" and
"fastboot erase modemst2"
commands. On boot screen, it just keep showing
Code:
"erasing modemst1..."
for a long time. Does it take that long, or it gets "done" text in a sec? Let me know. I am starting now. Thanks.

Not sure how long it should take tbh. I would let it run, and give it a good while before worrying about it. Maybe open up some kind of system resource monitor on the side (on your computer) so you can see that things are still happening?
There are definitely times that these types of tools will look like its just sitting there though... It should go through eventually, give 10+ minutes before assuming it is not working.

scryan said:
Not sure how long it should take tbh. I would let it run, and give it a good while before worrying about it. Maybe open up some kind of system resource monitor on the side (on your computer) so you can see that things are still happening?
There are definitely times that these types of tools will look like its just sitting there though... It should go through eventually, give 10+ minutes before assuming it is not working.
Click to expand...
Click to collapse
Alright, i am on that command. I am gonna paste whole console commands. Because i think this time it won't work too. :l After every command it's showing
Code:
<bootloader> Variable not supported!
then "OKAY" like it went correct. Plus can you tell me what exactly my variant name is? I can't figure out, as for that OP, it was VZW. But for me, it must be different. I need it for second last command. Thanks.
EDIT : 25 minutes passed. Still same.