Database Users

[Q] Moto Milestone X (Any way to root/custom rom's) ?

Hello, I just got a Motorola Milestone X. Its running on ACS alaska network. From reading I've done this phone appears to be the moto x but just not the vws branded phone? My question does anyone know of a way to root it and or any custom roms for it? Its filled with bloatware and no way to remove it and the stock rom is very ugly.
Ive tried z4root, superoot, androot and various other rooting guides that were supposed to work on the Moto X but all have failed me. Its running 2.2.1 and from what I gather this might be the problem?
Any help or info from anyone else familiar with this phone would be greatly appreciated as I hate it in its current stock form and would like to at least be able to remove the bloatware and crap I dont use even if there arent any custom roms for it. Thank you

Possible root
I also have a milestone x from a local carrier, and was able to root it.
I downloaded and installed all the Motorola drivers.
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Hooked the phone up and went through each mode to ensure all the drivers were installed.
I then installed the latest version of SuperOneClick from http://forum.xda-developers.com/showthread.php?t=803682
I then extracted and ran SuperOneClick, chose the psneuter exploit and clicked root. This was able to root the phone. I did need to reboot the phone before the superuser application would work though.
I haven't looked into custom roms yet.

thank you very much for the information. I tried super one click but it would always lock up but maybe i'll give it another try. Is your phone running 2.2.1? Thanks again for the reply.

Inciner8Fire said:
I also have a milestone x from a local carrier, and was able to root it.
I downloaded and installed all the Motorola drivers.
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Hooked the phone up and went through each mode to ensure all the drivers were installed.
I then installed the latest version of SuperOneClick from http://forum.xda-developers.com/showthread.php?t=803682
I then extracted and ran SuperOneClick, chose the psneuter exploit and clicked root. This was able to root the phone. I did need to reboot the phone before the superuser application would work though.
I haven't looked into custom roms yet.
Click to expand...
Click to collapse
I must have used a older version of SuperOneClick before. This one you linked worked with no problems at all. Thank you so much!

No prob, glad it worked for ya.

Thanks for the post. I was going through the same frustrations with my new ACS Milestone X. I see now that there is a new version of SuperOneClick ... anybody else trying to make this work, make sure you use v1.7.

So back to JDinAZ74's second question ... now that we've rooted are there custom roms for our CDMA version of this phone? I see tons of roms but none that I've noticed specify GSM or CDMA, which usually means it's GSM. Anybody know for sure?

the dx is on verizon, so its all cdma. i not sure it would matter though...

Yeah I'm not sure it matters either ... I know on my HTC Desire it mattered. If I flashed it with a GSM rom it would not boot.
Okay so somewhat unrelated ... i've got bootstrap installed and was able to do a rom backup via clockwork recovery. Is there a way to boot into recovery from the device being off? I tried every combination of buttons while pressing the on button but nothing works. I've looked all over the forum (and googled) but can't find anything.
I want to start installing custom roms but am affraid of something going wrong and me not being able to reflash my backup.
Then again maybe I'm just confused because I'm coming from a Desire which I've discovered Motorola and HTC modding differs significantly.

Im still looking for roms as well and kinda afraid to just start trying things like you said. If you come across anything that works let me know and ill do the same.

to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.

mattmartin77 said:
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
Click to expand...
Click to collapse
Wouldn't the SBf only work on a Droid x?

mattmartin77 said:
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
Click to expand...
Click to collapse
Fantastic! Thank you.

I don't know that they could do an sbf being on a non Verizon carrier. The sbf files out are all for Verizon. If you do screw up your phone you would have to take it into the store and have them sbf it. And they might not. I think you guys just need to be a little careful. Unless you can find an sbf file from your carrier. Try apex, rubix, or liberty roms for flashing. All the roms are cdma. Good luck and be careful.
Sent from my DROIDX using XDA App

The milestone x uses the same RSA key for its bootloader as the original Droid X. You CAN flash a Verizon SBF into it and it will work, HOWEVER, it will NO LONGER work with your carrier. It is also important to note that ANY SBF will overwrite the baseband AND the baseband configuration (unless specifically noted NOT to do so) rendering the phone useless, requiring re-programming, which for the voice part is no big deal, but to get EVDo working again you'll need to edit some non-user accessible parameters with QPST and what not to get it to connect back to the non verizon carrier.
What you CAN do with this phone is non-baseband patching updates/roms. If you've got a Milestone X you're not on verizon, so you're not able to use the leaked SBF's and what not, which removes a decent safety net. So flash with caution. If your carrier is small enough they are likely to re-sbf your phone for you if you brick it.
One last word of caution.. Verizon's DX on leaked GB's updates the BL to a newer version than is on the Milestone X. This will turn your phone into a Droid X, with no ability to go backwards until the same BL is available on the Milestone X.
In short, we non VZW DX owners have a lot less fun..
Bollocks to that.

really wish I knew if someone had tried, I really want to try that leaked gingerbread.

went ahead and took the plunge with... SUCCESS. I installed Liberty 2.0.1 and nothing went wrong, you just got to be more careful than others who have the sbf backup.

Went to ACS today because i'm considering this phone, ACS is partnering with Verison(GSM), and GCI is partnering with Sprint (CDMA).
Just incase it's not clear i'm sure roms for Verizon will work for ACS and roms for sprint should work with GCI.
Double check incase i have the two "bands mixed up" i know i have the carrier relationships right.

Does anyone know if we can overclock with out romming?

I tried droid overclock a few times which always sent the phone into a boot loop. Id have to pull the battery and do a factory reset to get it running again.

[HELP]Droid X running 4.5.602.MB810.Verizon.en.US

Here is the quick and dirty,
My dad has a Droid X. It was running Froyo rooted happily. It got updated to OTA GB (version in topic). It is now not rooted. Superuser.apk is still present. I cannot sbf through either windows or linux (no clue why, it always fails). I have tried the one click root that is supposed to work for the Droid 3 (and X running GB) - it thinks it worked but it is not rooted (verified few different ways).
Help please as I need to get my dad's droid x rooted. Need responses ASAP as they are going out of town in the morning.

You need to describe the exact steps you have taken and the exact error you get in order to get good help. Screenshots are great too.

They are back out of town now until Thanksgiving, but in windows I was getting a 0x7100 error. In linux I was getting a whole bunch of errors followed by a line saying flash failed.

A sbf shouldn't be effected by software version, as it just removes everything and starts over. I would say it was an error in setup for the sbf. Since the D3 method failed aswell, it seems that the phone isn't getting the message from the computer. But that's my two cents. You really just need to try again with the sbf.
Dispatched at the Speed of Light from my XOOM

I tried SBF from both linux and windows MANY times. Same with D3 root method. ADB works like a champ though......

Did you do a factory reset before attempting to sbf? Since there seems to be a problem with removing GB from the phone, maybe there's some error on that system that's effecting rsd's process.
Transmitted from Droid X

Tried the method on rootzwiki? I don't think I can post links yet but I had the TBH 2 part gb on my phone but I messed up and did the recent ota update and lost root.
Found this method from following a droid life link. Also a way to get rid of the old SU using adb shell if it doesn't root properly on the DX ( which happened to me)
Sent from my DROIDX using XDA App

I will look into those methods at Thanksgiving when I get another shot at that phone.

Any Success @ SBF 2.2.2 Cellular South Milestone X (FROYO)?

As the title asks...
Has anyone been able to SBF back to 2.2.2 Froyo from the OTA update? If so, please advise all details. Thanks.
Much of the software conveniences I use, are better working in 2.2.2 especially screen lockers, unlockers, blockers, and Wireless Tethering.
W/ 2.3.5, I change the hotspot info to that of Wireless-Tether's and use it, but that's annoying...
Feels like two different setups.

i tried once... didn't go so well, ended with warranty replacement.
downloaded sbf that indicated it was for cell south(cspire) from here. everything appeared to go just fine. until the phone rebooted. gave me a message that said something like MEM_BLANK or something similar. i will admit that i am not very proficient with motorola's yet, and may have done something wrong, but i followed the steps that i found posted here on xda. if you find any more information i would love to hear it.

I had the same issue come up with no success as well. This happened when I tried flashing Liberty3 after doing full wipes and installing the Droid 2 bootstrapper. After the flash, I kept getting stuck on the bootloader with some error codes. At that point, I tried flashing the sbf using rsd lite and sbf_flash on ubuntu, but those ended up giving me more error codes with the MEM_BLANK and SERVICE REQ'D outputs. Meh, guess I'll just have to stick with stock rooted.

Rocheforte said:
I had the same issue come up with no success as well. This happened when I tried flashing Liberty3 after doing full wipes and installing the Droid 2 bootstrapper. After the flash, I kept getting stuck on the bootloader with some error codes. At that point, I tried flashing the sbf using rsd lite and sbf_flash on ubuntu, but those ended up giving me more error codes with the MEM_BLANK and SERVICE REQ'D outputs. Meh, guess I'll just have to stick with stock rooted.
Click to expand...
Click to collapse
exactly. i came to the same conclusion. makes me wonder why the motorola roms aren't more like the htc roms where they are not carrier specific.
edit: did you manage to get past the MEM_BLANK and SERVICE REQ'D errors on your own? and if so, how?

No success, anytime I tried to sbf it would output a slightly different error with MEM_BLANK and Service Req'd. I eventually just replaced it, but now I'm likely going to return this one because it won't update to 2.3 and wifi doesn't work.

Rocheforte said:
No success, anytime I tried to sbf it would output a slightly different error with MEM_BLANK and Service Req'd. I eventually just replaced it, but now I'm likely going to return this one because it won't update to 2.3 and wifi doesn't work.
Click to expand...
Click to collapse
did u install the bootstrapper? it changes the logwrapper file, however changing it back and removing the bootstrapper all together still yeilds the same problem. update fails after about 1 minute.
here is a strange morsel of info, when i was trying. (before warranty replc) even tho the update would fail, it did change the system info on the phone, it would indicate that .602 was installed on the phone even tho it had failed.

ngholson said:
did u install the bootstrapper? it changes the logwrapper file, however changing it back and removing the bootstrapper all together still yeilds the same problem. update fails after about 1 minute.
here is a strange morsel of info, when i was trying. (before warranty replc) even tho the update would fail, it did change the system info on the phone, it would indicate that .602 was installed on the phone even tho it had failed.
Click to expand...
Click to collapse
Yeah, I had used the Droid 2 bootstrapper at that point. Has anyone tried using the Verizon Droid X sbf's since apparently they are supposed to be very similar to the Milestone X's?
Sent from my Milestone X using xda premium

[Q] I've Bricked another one!

Night before last my Droid X was upgraded via OTA from Froyo 2.2.1 to Gingerbread 2.3.4 , at which I lost my Root. So I started searching YouTube for videos on taking my phone back to Froyo. And I found just what I was looking for. Return your Droid back to Froyo. So I followed the instructions to the letter, I downloaded - RDS Lite 4.9 - Motorola Helper_2.1.40_5.5.0 - VRZ_M810_2.3.34_IFF_01 . According to RSD Lite the flash was successful. Droid X reboots, and this is what I was left with.
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program'Transfer Mode:
USB
I have tried SBFing twice and RSD Lite sees the phone, goes thru the flash, reboots the phone but I get the same responce on the phone as stated above. Although in my computer, the Droid is not detected.
In your opinions, have I done an unrecoverable bricking to my Droid?
Go ahead, I can take it.
TIA

I used 4.5.621 SBF file, and was able to bring my phone back to the way it was before I got in a bind (Droid X SBF Files - Motorola SBF Files). It is alive with all of my Apps, so I'm not sure just what happened to it. But to whoever is responsible for the web site, I think P3 Thanks

Great job on getting back to .621.
Unfortunately, being on .621 makes it impossible to flash back to Froyo.
However, you can root and install custom roms.
Sent from my DROIDX using Tapatalk 2

yeah I know, but at this point I'm just happy to have my phone back in good working order. I had just bricked my Droid X2 @ 2 weeks ago, so now I don't have to face my wife with another $200.00 paper weight.

I have the same issue. Someone pointed me to this forum so I'll just include my text.
So I just got my first droid yesterday, it's a droidx from motorola. I initially factory reset it and cache cleared and it was working like a charm. Anyways, today I got the idea after reading over cyanogenmod following these instructions. Since I didn't have much on it I didn't backup. I remember vaguely updating the system previous to this, I think I was at 2.34. Anyways, I get done with flashing it- as far as I know it was successful- rdslite said it was complete. I try to do another factory reset, can't get into it. Just the bootloader comes up saying : Bootloader30.04 Err:A5,70,70,00,1F and a few things about to plug usb in and that it needs service...
I see something on cyanogen's page that I overlooked before:
WARNING: The 2.3.4 OTA release, the bootloader was patched to version 30.04. If an attempt is made to downgrade to an earlier version through the SBF method below, the bootloader will throw an error and the phone will not boot.
FLICK.
I tried the 1kds cd and it says it installed properly, I turn it on only to see same bootloader issue. I tried another rom and same thing. The last one I used was apparantly a 2.34 one and now my phone says code corrupt on the bootloader screen.
I need to find a way to charge the battery. I feel bad because it was a present to me from my girlfriends sister, and I don't want to see her and tell her I broke it already
But, can you guys help me with this? I don't really know where to go from here.

Sbf

Sbf is the only way. And from what I understand if you did the. 621, you won't be able to do previous releases.
I could be wrong.
When it comes yo moto flashing, donkey skip reading anything lol
Sent from my DROIDX using xda premium

[Q] Want to re-root, can you help?

So here's my deal. The other day I was doing fine, and I had a version of CM9 that I got from here. I tried the dev's latest version and it was a little wonky so I tried to restore my ClockworkMod backup if his previous version that worked better. And I bumped the cable while it was in process, and that stopped the flash and got me stuck with a non-booting system.
So then I decided I'd reset the phone, re-root, and then I could restore a backup. The first part went good, and then without thinking I accepted Verizon's update.
I found someone saying that I could flash this non-Verizon SBF to it, and it worked but it's for some "nTelus" carrier that apparently isn't here in Michigan and I can't figure out how to put Verizon on it. I tried *228 and it gave me the "Activating your phone" screen but the robovoice on the phone just told me that I wasn't authorized to do something and then said something in Spanish.
I know I can just put Verizon's new ROM on there and it'll work but I prefer to have CM7 or CM9, and either way I definitely don't want their crapware. ClockworkMod is the only backup I have but it obviously does me no good when the phone isn't rooted so I can install ClockworkMod.
So my question is this: is there a way I can root Verizon's new ROM, or revert to an old ROM, and if not then is there a way to make the nTelus ROM know that it should be using Verizon's network?

You have to flash the non Verizon SBF (version .604) but you cannot use RSD Lite, you just use the Linux method.
Now you need to use RSD Lite to return your phone to stock Verizon .621. This will fix your activation problem.
Then, download 1KDS's .604 Live Linux CD and use it to flash the rootable SBF.
Sent from my DROIDX using Tapatalk 2

Thanks, I'll try that when I get home.
Anyways, something I'm about to try, I'll let you know the results. I've found a small section of text in these files that appears to have the Access Point Names and connection data for the carriers. In the nTelos file there's only one carrier, in the Verizon file there's Verizon, ATT, and others. So I'm going to copy-paste-pray and I'll let you know how it works. If it goes smoothly I'll post the resulting file somewhere.
EDIT: Nope, it didn't work. C'est la vie.

OK so it sorta worked... I guess. But now I have no data connection...
Great.