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.
Related
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
silversonic1 said:
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
Click to expand...
Click to collapse
Think you're boned. Shoulda read some of the thread at mydroid before taking this on. Most ppl are bricking, with it. You appear to fall into that category.
Go Back to TBH there maybe some help now.
But the 23.15 may also big the big bone.
ouch
This is awful. I'm a guide on another forum for androids and I'm telling people not to try the new update until there is a full sbf available. I'm so sorry. You are stuck..for now.
Well, Verizon's gonna let me swap, so I'll just have to wait until Tuesday and root the new phone.
I'm preparing to root my X and am trying to get a rescue plan in place prior to rooting. The one thing I can't find is a list of what SBF files can safely be used for a given bootloader revision. I posted this in a thread at another forum. Does what I'm asking for not make sense? Or am I completely missing something?
There should be some sort of sticky for SBF'ing the X. I realize that sbf links cannot be posted but it would sure be nice to know which files are needed to properly sbf a semi bricked phone, especially if using the wrong one will fully brick a phone.
What I've gleaned from this thread...
"No if you were stuck on the M that shows that you should already be updated, put your phone into flash mode and make sure (turn of your phone press the camera down volume and power button). It should say boot loader 30.04 if it shows 30.03 then dont use the link provided. If it is 30.04 go download the sbf from ncdubs link and run it using RSD 4.8 and that should be enough for the phone to get past the M logo. Dont it asap because you never know when that link will be dead. Man I was so scared yesterday because i thought my phone was bricked haha but that link that i found in another forum did the job."
"If you are on 2.3.20, use the 2.3.15 SBF.
If you are on 2.3.320, use the SBF's from TBH"
It would be nice to have a running list detailing which sbf file needs to be used for a given bootloader,
i.e. if bootloader is 30.03 use the 2.3.15 sbf or the x.x.xx sbf
if bootlader is 30.04 you can safely use the x.x.xx sbf
and so on.
Surely this won't be in violation of anyone's terms of service would it?
I'm not rooted yet but I'm trying to wade through multiple posts at multiple sites to put together a rescue package prior to rooting and can't find what I believe to be concise information anywhere.
Click to expand...
Click to collapse
http://www.mydroidworld.com/forums/...rikes-back-2-3-320-update-must-rooted-69.html
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
bricked, verizon is overnighting one, should have a good clean one tomorrow.
SerialKilla said:
.....link deleted, as this forum won't allow me to post outside links..... yet...
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
Click to expand...
Click to collapse
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
edthesped said:
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
Click to expand...
Click to collapse
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
SerialKilla said:
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
Click to expand...
Click to collapse
Sorry, it was the system only sbf, I d/l'ed it as a backup and judging by it's size it isn't a full system sbf. Hopefully you'll be rocking again by this time tomorrow.
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
tenbeau said:
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
Click to expand...
Click to collapse
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
bobsbbq said:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
Click to expand...
Click to collapse
yes I a sure am. I trusted the Dorid-Life site and should not have. Thanks for the swift response...
setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Please post questions in Q&A section.
I did the same thing. I flashed the .zip file from droid life forum and got a success message when I installed it through recovery and mine never bootlooped. I didn't get the gingerbread keyboard but it didn't bootloop either
Sent from my HTC Glacier using XDA App
tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
I think you mean bootloader? You only have 1 recovery. If you flashed clockwork you no longer have stock recovery. Vol Down + Pwr gets you to bootloader or SPL where it shows S=off.
I did not flash the zip (sounds like an overkill to flash a zip for new KB). I ADB pushed both files and got a FC on multi-touch KB... oh well, I like HTC_IME better anyway
tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
make sure fastboot is checked off otherwise you cant get into the bootloader. to make sure it is off go to: menu, settings, applications and uncheck fastboot. you're good to go then. to get into recovery, you can do it thru bootloader or by opening up rom manager and clicking on the "reboot to recovery" option
setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
the website was not specific enough. the port at the current moment is for motorola droid devices. they should have been more specific instead of saying any rooted 2.2 android phone. even if you do get it on your phone, its only going to force close every time you try and type something. thats what happened to me, so after about 24 hours i said **** it and removed it. swype in my opinion is better anyway. im trying to port the g2 swype to our phone so we can have a swype with a mic on the keyboard. oddly, ours didnt come with one.
A month go I installed the leaked Gingerbread. everything has been fine until I decided to get back to Froyo for the OTA. Rooted this morning through Gingerbreak. Still OK. Made a back up through Bootstrapper. Booted into recovery and installed .zip from sd card. Used Maderstock zip. it made it through almost the entire process then when it got to update Radio it aborted. I cleared all the cache and data and all...still nothing. Hit reboot and now it is stuck in bootloop at the droid logo. The font with the circles under the "r" Can not hold home and power to get into recovery. can not turn on phone at all. only get charge screen when plugged in (and yes I was 90-100% charged when attempting this) and red moto logo goes black when attempting recovery boot.
I assume I need to SBF through RSD Lite. Problem is- It wont recognize my device. (yes I have downloaded the Moto drivers.)
At this point I am totally stumped. Noob here, but with LOTS of research and reading over the last weeks.
Help?
check out how to sbf using a linux virtual machine. You can just boot it up within windows. As far as I know, you will not need the drivers for this to work.
Try this. Hopefully it helps.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
After weeks of reading forums and posts, I have successfully SBFd my phone back to stock Froyo. I wish I could remember everyones names from every post I read, and thank them personally, but a BIG THANK YOU to the Android community and to anyone that has offered their time and service to helping out. THANK YOU ALL! My experience as little as it might be might now be valuable to others as well.
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Fixing a bricked Droid X
beeper10 said:
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Many thanks to all those that have spent countless hours helping users like myself find solutions to Droid X problems. At one point in this process I basically bricked (maybe soft briked is the term) my phone. I could do nothing but get a bootload screen. No moto logo, no droid eye, NOTHING.
Long story short, and to help anyone that needs it, here is my solution.
Download FULL SBF file from file share somewhere (VRZ_MB810_2.3.34_1FF_01.sbf)
Download RSD Lite 4.8
Download Moto Drivers
Power Off Droid X- Make sure it is fully charged when attempting any SBF Flashing.
Power on into Bootload mode. I held Power and Volume rocker simultaneously until a quick flash then Bootload appeared. (version 30.4)
Open RSD Lite as an administrator. (hold shift and right click. use "run as") In my case Windows 7 -64bit
Plug phone into computer via USB
Locate device in RSD. Click the little box that has "..." in it and select the SBF file you previously downloaded.
Start.
Let it work its entire process and Voila you will have stock Froyo back on your phone in no time.
I then went in under settings and received the OTA for Gingerbread. My phone works like a champ now.
The steps are clear as day in my head, and I will be able to troubleshoot many of you through the steps. The further from today it gets it might get foggier, so ask away if you are having problems.
It seems like everything had to be VERY specific to work just right.
Good luck and happy Bricking! :/
It happened to more people than you think. I DLed RSD 4.9, 4.8 didnt work for some reason. That was like a month ago, I'm on froyo now, rooted with Liberty. Now I have to SBF again to get the official GB...lol!
My story the same just different thread, (soft bricked) lol my phone, all i got was the bootloader, on win7 64bit as well, only thing different was ive my win7 tuned up to my preferences so i didnt have to ask or run as anything. The steps used in this thread were identical however and many many hours of reading done as well. Just putting this info up here to let you know that you can get your dead bootloading phone back so even though it feels like you have a bowl of something nasty in your stomach as you stare at your DX with nothing but a bootload screen on it and seemingly no other options, read thoroughly, pay attention, be specific and youll have your DX running like a champ in no time. THANK YOU Devs/Community
I posted this elsewhere but I would like a answer faster.
I like to think I am rather educated in regards to how to root and all that. I just got my replacement Evo today and of course it is updated to 2.3.3. So I can't use unrevoked, but I was hoping to flash over to a older backup I made on 2.2 on my old phone.
Except, when I do the whole hold the volume down + power button and eventually choose recover, all that happens is a image of a phone and a exclamation point appears and it never leaves here.
I know in order for me to be able to use ClockwordMod I need to root the phone, which can't happen on 2.3
So what are my options? How do I flash over my old rom???? Even if it doesnt let me get back to 2.2 its still better than redownloading all my apps.
Rapture Veteran said:
I posted this elsewhere but I would like a answer faster.
I like to think I am rather educated in regards to how to root and all that. I just got my replacement Evo today and of course it is updated to 2.3.3. So I can't use unrevoked, but I was hoping to flash over to a older backup I made on 2.2 on my old phone.
Except, when I do the whole hold the volume down + power button and eventually choose recover, all that happens is a image of a phone and a exclamation point appears and it never leaves here.
I know in order for me to be able to use ClockwordMod I need to root the phone, which can't happen on 2.3
So what are my options? How do I flash over my old rom???? Even if it doesnt let me get back to 2.2 its still better than redownloading all my apps.
Click to expand...
Click to collapse
Well, you have a couple problems here.....if I am not mistaken, your first problem seems to be that your recovery may either be corrupt or not installed. I saw this issue back in my TP2 days. Not with the evo though. If this is a replacement EVO and you cannot properly get to your recovery, then I would suggest contacting sprint on this issue. It should at least go into the stock recovery. As for your rooting issue...you can't do anything untill root is provided for the update.....best of luck to you!
His recovery is not corrupt. That's stock recovery
HipKat said:
His recovery is not corrupt. That's stock recovery
Click to expand...
Click to collapse
thats what i thought. so i have to just update the drivers by installing the provided unrevoked drivers/method? id like it but im new and it wont let me. well...
unrevoked dot com/rootwiki/doku.php/public/windows_hboot_driver_install
Well, as we've seen in the 10 million posts about this, there is no root for 2.3.3 yet.
No root, no recovery. No nothing, but stock and that's that.
Rapture Veteran said:
I posted this elsewhere but I would like a answer faster.
I like to think I am rather educated in regards to how to root and all that. I just got my replacement Evo today and of course it is updated to 2.3.3. So I can't use unrevoked, but I was hoping to flash over to a older backup I made on 2.2 on my old phone.
Except, when I do the whole hold the volume down + power button and eventually choose recover, all that happens is a image of a phone and a exclamation point appears and it never leaves here.
I know in order for me to be able to use ClockwordMod I need to root the phone, which can't happen on 2.3
So what are my options? How do I flash over my old rom???? Even if it doesnt let me get back to 2.2 its still better than redownloading all my apps.
Click to expand...
Click to collapse
Are you s-on or s-off ?
HipKat said:
His recovery is not corrupt. That's stock recovery
Click to expand...
Click to collapse
If I member right once in stock recovery you push vol up + power button to get the menu up.
sent from my locked EVO via tapatalk
Recently I bought a Bravo which came with 2.2.2 "Blur_Version.38.6.0.MB520.Generic.en.US", there was a different kernel too.
I was trying to root it and install custom recovery but I installed custom recovery twice and then I had to flash sbf because it went into bootloop, nothing beyond moto logo.
after installing sbf 2.2.1 again, when I go to system updates, it says its up to date.
I was trying to backup system to have it.
Did anybody here get this update?
josuearisty said:
Recently I bought a Bravo which came with 2.2.2 "Blur_Version.38.6.0.MB520.Generic.en.US", there was a different kernel too.
I was trying to root it and install custom recovery but I installed custom recovery twice and then I had to flash sbf because it went into bootloop, nothing beyond moto logo.
after installing sbf 2.2.1 again, when I go to system updates, it says its up to date.
I was trying to backup system to have it.
Did anybody here get this update?
Click to expand...
Click to collapse
No, but I haven't been on the actual Bravo factory system to know if an update would even be available. I've always suspected that there were more Bravo systems than our one sbf, but with all our users instantly upgrading to CM7 I can easily see it being overlooked. The other/maybe newer kernel intrigues me since it might be more compatible\similar to the Defy kernel since the Defy's last official update was a 2.2.2 Froyo. While officially the Bravo is listed as a US ATT Phone, all the Chinese and non American users makes it very obvious that this isn't the case. I'd love to get my hands on a Chinese SBF for the Bravo.
While you weren't able to get past the Moto logo, were you able to root it? Or access 2nd-init? If so, then why the hell didn't you do a dd on the bootloader? :silly: I'd of gladly dumped that dump onto my Bravo. If you happen to come across one again then for the love of God don't sbf it.
Knowing that there's another Bravo system and kernel I can't try makes me a very sad panda.
/Now I gotta sbf to stock and fire up cheesecake and see if anything happens. If cheesecake even still works.
skeevy420 said:
No, but I haven't been on the actual Bravo factory system to know if an update would even be available. I've always suspected that there were more Bravo systems than our one sbf, but with all our users instantly upgrading to CM7 I can easily see it being overlooked. The other/maybe newer kernel intrigues me since it might be more compatible\similar to the Defy kernel since the Defy's last official update was a 2.2.2 Froyo. While officially the Bravo is listed as a US ATT Phone, all the Chinese and non American users makes it very obvious that this isn't the case. I'd love to get my hands on a Chinese SBF for the Bravo.
While you weren't able to get past the Moto logo, were you able to root it? Or access 2nd-init? If so, then why the hell didn't you do a dd on the bootloader? :silly: I'd of gladly dumped that dump onto my Bravo. If you happen to come across one again then for the love of God don't sbf it.
Knowing that there's another Bravo system and kernel I can't try makes me a very sad panda.
/Now I gotta sbf to stock and fire up cheesecake and see if anything happens. If cheesecake even still works.
Click to expand...
Click to collapse
Uuuuuuups, I alredy SBF it, the phone belong to my father and I had to give it to him yesterday
There was another kernel yes, side applications was enabled, it was faster than 2.2.1, there were less bloatware
And the most important thing is that the phone didnt say AT&T down the home button.
I am very sad because I couldnt even create a backup for system, I forgot about dd codes for backing up too, but as I told you before, I had to act inmediatly.
I thought that flashing 2.2.1 again, I was able to update it via system update, but it wasnt possible.
josuearisty said:
Uuuuuuups, I alredy SBF it, the phone belong to my father and I had to give it to him yesterday
There was another kernel yes, side applications was enabled, it was faster than 2.2.1, there were less bloatware
And the most important thing is that the phone didnt say AT&T down the home button.
I am very sad because I couldnt even create a backup for system, I forgot about dd codes for backing up too, but as I told you before, I had to act inmediatly.
I thought that flashing 2.2.1 again, I was able to update it via system update, but it wasnt possible.
Click to expand...
Click to collapse
I've looked a bit on Google and haven't seen anything about a Bravo 2.2.2 system . And that includes translating a few Russian, Spanish, and Chinese sites. I sbf'd back to stock so I'm gonna install try looking on the cheesecake servers (hopefully they still work for us) and hope something happens.
Other than AT&T, what other carrier uses the Bravo? If we knew that then all we'd need to do is take a sim unlocked stock Bravo, connect to that network, and check for a system update. Bravo 2.2.2 might be carrier exclusive, and that carrier isn't AT&T. If it weren't for the different kernel version, I'd almost think that it came with a Defy 2.2.2 T-Mobile port (same way to port as CM7).
skeevy420 said:
I've looked a bit on Google and haven't seen anything about a Bravo 2.2.2 system . And that includes translating a few Russian, Spanish, and Chinese sites. I sbf'd back to stock so I'm gonna install try looking on the cheesecake servers (hopefully they still work for us) and hope something happens.
Other than AT&T, what other carrier uses the Bravo? If we knew that then all we'd need to do is take a sim unlocked stock Bravo, connect to that network, and check for a system update. Bravo 2.2.2 might be carrier exclusive, and that carrier isn't AT&T. If it weren't for the different kernel version, I'd almost think that it came with a Defy 2.2.2 T-Mobile port (same way to port as CM7).
Click to expand...
Click to collapse
I hope you get something, maybe you can ask somebody at AT&T, the answer maybe its there, maybe it was approved by AT&T.
I would like to help with that, but after flashing our SBF, you know there is no way to go back. Do you know anybody at motorola?
But there is no use now, we almost have jelly bean 4.2.2 with custom kernel.
Speaking about it, there have not been anything new with that, do you know something about?
2.2.2 = Consumer Cellular
Guys, I'm on Consumer Cellular and getting wife fixed up with Bravo that they sell/support. First one I bought had 2.2.1 on it and couldn't get MMS working. Found another on ebay listing says it was used on Consumer Cellular and photo of About Page shows version 2.2.2 and Version.38.6.0.MB520.Generic.en.US. I plan to buy the phone and will be glad to backup the rom and share it with you. Just need pointer to process to follow. I'm somewhat of a newbie (with android phones) but have flashed CM7 to the bravo and reflashed back to 2.2.1 sbf using rsdlite.
Toby
Making an SBF file is not an easy task. I think Consumer Cellular clients may ask their carrier for any help with stock rom.
bohdan4ik13 said:
Making an SBF file is not an easy task. I think Consumer Cellular clients may ask their carrier for any help with stock rom.
Click to expand...
Click to collapse
I see that now. If/when I get the phone, I'm willing to backup the 2.2.2 rom if a nandroid backup would be helpful.
tobewan said:
I see that now. If/when I get the phone, I'm willing to backup the 2.2.2 rom if a nandroid backup would be helpful.
Click to expand...
Click to collapse
Its not just to make a nandroid backup, we would like to get the bootloader too.
skeevy can help you getting the backup we need, using dd codes, I dont remember which were these codes, lets wait for him.
Thanks!
tobewan said:
Guys, I'm on Consumer Cellular and getting wife fixed up with Bravo that they sell/support. First one I bought had 2.2.1 on it and couldn't get MMS working. Found another on ebay listing says it was used on Consumer Cellular and photo of About Page shows version 2.2.2 and Version.38.6.0.MB520.Generic.en.US. I plan to buy the phone and will be glad to backup the rom and share it with you. Just need pointer to process to follow. I'm somewhat of a newbie (with android phones) but have flashed CM7 to the bravo and reflashed back to 2.2.1 sbf using rsdlite.
Toby
Click to expand...
Click to collapse
Well I'll be damned...someone actually still has the Stock 2.2.2 . The most important partitions we'll need are bootloader, devtree, and system. A nandroid backup will work for the system, but the bootloader and devtree should be dd off the phone. Make sure you have at least a gig of free sd space. I'm gonna be thorough and have you dump more than needed.
To make the copies you'll need to root the phone and have a PC handy with ADB working....PC not necessary but makes it much easier. Any of the adb shell commands can be done from Android Terminal Emulator.
For adb, open up a Terminal Window\Command Prompt
type "adb shell" to access the phones terminal environment
then "su" to be root user
For Android Terminal Emulator
Just open it and type "su"
Code:
Do all these commands as root with adb or Terminal Emulator.
dd if=/dev/block/mmcblk1p0 /mnt/sdcard/dump/mbr
dd if=/dev/block/mmcblk1p1 /mnt/sdcard/dump/mbmloader
dd if=/dev/block/mmcblk1p2 /mnt/sdcard/dump/mbm
dd if=/dev/block/mmcblk1p3 /mnt/sdcard/dump/mbmbackup
dd if=/dev/block/mmcblk1p4 /mnt/sdcard/dump/ebr
dd if=/dev/block/mmcblk1p5 /mnt/sdcard/dump/bploader
dd if=/dev/block/mmcblk1p6 /mnt/sdcard/dump/cdt.bin
dd if=/dev/block/mmcblk1p7 /mnt/sdcard/dump/pds
dd if=/dev/block/mmcblk1p8 /mnt/sdcard/dump/lbl
dd if=/dev/block/mmcblk1p9 /mnt/sdcard/dump/lbl_backup
dd if=/dev/block/mmcblk1p10 /mnt/sdcard/dump/logo.bin
dd if=/dev/block/mmcblk1p11 /mnt/sdcard/dump/sp
[B]dd if=/dev/block/mmcblk1p12 /mnt/sdcard/dump/devtree[/B]
dd if=/dev/block/mmcblk1p13 /mnt/sdcard/dump/devtree_backup
dd if=/dev/block/mmcblk1p14 /mnt/sdcard/dump/bpsw
[B]dd if=/dev/block/mmcblk1p15 /mnt/sdcard/dump/boot[/B]
[B]dd if=/dev/block/mmcblk1p16 /mnt/sdcard/dump/recovery[/B]
dd if=/dev/block/mmcblk1p17 /mnt/sdcard/dump/cdrom
dd if=/dev/block/mmcblk1p18 /mnt/sdcard/dump/misc
dd if=/dev/block/mmcblk1p19 /mnt/sdcard/dump/cid
dd if=/dev/block/mmcblk1p20 /mnt/sdcard/dump/kpanic
[B]dd if=/dev/block/mmcblk1p21 /mnt/sdcard/dump/system[/B]
dd if=/dev/block/mmcblk1p22 /mnt/sdcard/dump/prek
dd if=/dev/block/mmcblk1p23 /mnt/sdcard/dump/pkbackup
**don't upload these two unless you factory reset and don't enter any personal data**
dd if=/dev/block/mmcblk1p24 /mnt/sdcard/dump/cache
dd if=/dev/block/mmcblk1p25 /mnt/sdcard/dump/userdata
**************************************************************************************************
After that, mount your sdcard over USB and zip up the entire "dump" directory (/mnt/sdcard/dump) and upload that somewhere, preferably anywhere without a bandwidth cap. Should be around 350-400mb total.
The most important ones needed are in bold, though all could possible help. Other than system and cdrom, most should be under 4mb, 2mb, or 512k.
I tried to make this as easy as possible. You should be able to just go down the line and copy\paste everything.
Thank you. Even if its old, we'd still like any stock Bravo system that's not AT&T -- especially if it comes with a different kernel .
PM me if you need to get my attention since I'm not around the Bravo forums as much as I once was.
EDIT--Can you get a better screenshot of the kernel version? From the picture the kernel is the same as the stock one...I need the bottom line to verify.
Help: I bricked the consumer cellular mb520
I bought a Consumer Cellular version of Motorola Bravo MB520, and the device was sim-locked, so I was trying to do "soft-unlocking" using the defy method (http://forum.xda-developers.com/showthread.php?t=1483297).
I successfully rooted the phone, and flashed one of GB roms, WhateRabbitNextGen-2.1.1.
Then I flashed Baseband_change(EP93_U_00.59.01).zip to match the baseband version.
After that it booted straight to bootloader recovery every time.
So I flashed the sbf (p4_kobe_umts_kobe_user_3.4.2-125_KOB_FFW-4_product-keys-ATT-US_ATT-signed.sbf) to start over again.
But it kept rebooting, even worse now I can not load a CWM recovery mode.
The only thing I can access is sbf.
Is it possible to make a custom sbf to recover this phone?
If I buy another same phone, then can I make a restore file to flash this phone back to the stock status?
Solved
purpleid said:
I bought a Consumer Cellular version of Motorola Bravo MB520, and the device was sim-locked, so I was trying to do "soft-unlocking" using the defy method (http://forum.xda-developers.com/showthread.php?t=1483297).
I successfully rooted the phone, and flashed one of GB roms, WhateRabbitNextGen-2.1.1.
Then I flashed Baseband_change(EP93_U_00.59.01).zip to match the baseband version.
After that it booted straight to bootloader recovery every time.
So I flashed the sbf (p4_kobe_umts_kobe_user_3.4.2-125_KOB_FFW-4_product-keys-ATT-US_ATT-signed.sbf) to start over again.
But it kept rebooting, even worse now I can not load a CWM recovery mode.
The only thing I can access is sbf.
Is it possible to make a custom sbf to recover this phone?
If I buy another same phone, then can I make a restore file to flash this phone back to the stock status?
Click to expand...
Click to collapse
I found that I can still access stock recovery and could factory reset and solved the problem.
======
Note: If you bootloop and are stuck at the red M logo, you need to wipe data in stock recovery. To do that, hold the volume down button and continue holding it when you power up the phone. Then, once you see the triangle and android, press both volume buttons at the same time. After that, scroll down and select wipe data/factory reset.
=======
BTW, I am still looking for a solution to sim unlock this device.
I tried to buy an unlock code from ebay, but I got
IMEI: *********** Code: Code not found. (Rejected)
I guess the seller was doing for AT&T IMEI only.
You couldn't have hooked it up with a system dump first? Consumer Cellular phones are the only source for Motorola Bravo 2.2.2 factory system and different stock kernel\devtree. Us old school Bravo users really, really want that.
skeevydude said:
You couldn't have hooked it up with a system dump first? Consumer Cellular phones are the only source for Motorola Bravo 2.2.2 factory system and different stock kernel\devtree. Us old school Bravo users really, really want that.
Click to expand...
Click to collapse
Unfortunately I did not back up the system, but I reordered another one. I will upload it once I get it.
But why Defy soft-unlocking method does not work with Bravo?
Even with the same baseband version(EPU93_U_00.59.01)'s CM72 did not work for me.
After applying soft-unlock patch, it kept rebooting, and factory reset made the device not detect any sim.
Radio.img seems to be different from Defy, or maybe need just some simple tweaks.
purpleid said:
Unfortunately I did not back up the system, but I reordered another one. I will upload it once I get it.
But why Defy soft-unlocking method does not work with Bravo?
Even with the same baseband version(EPU93_U_00.59.01)'s CM72 did not work for me.
After applying soft-unlock patch, it kept rebooting, and factory reset made the device not detect any sim.
Radio.img seems to be different from Defy, or maybe need just some simple tweaks.
Click to expand...
Click to collapse
That would be awesome.
Soft sim unlock doesn't work because of radio.img. The soft sim patch replaces a few files under /system. You'll have to reinstall whatever rom you were previously using to get the radio working again. Factory reset shouldn't be necessary.
It's August of 2013. Needing more room on my SD card, I decide to delete my Consumer Cellular 2.2.2 backup. A week passes, and I find this thread. I originaly deleted it because I thought nothing of it, I figured all Bravo's had 2.2.2 froyo. Boy was I wrong. If I still had it, I sure as hell would have uploaded all that I could to help you guus out. If only I had found this a week earlier.
Just felt like I had to share that little story with the world, how I was so close to actually doing something monumental in the developing community.
---------- Post added at 10:18 PM ---------- Previous post was at 09:59 PM ----------
*BUMP*
You know, if anyone out there has 80 bucks they are willing to put forth to the good cause of 2.2.2...
http://www.amazon.com/gp/aw/d/B00B8B3G9W/ref=mp_s_a_1_1?qid=1398305766&sr=8-1&pi=SY200_QL40
Sent from my Rugby Smart SGH-I847 on the official XDA app!
Apologies for bumping an old thread, but I have two bravos: 2.2.2 and 2.2.1 ..Do you guys still need backups? I have no idea what's going on here or why it's considered so monumental in the developing community, but I'd like to know and I'm willing to help you guys out if it's still needed.
I also have a system dump and a CWM backup of an original 2.2.2 Consumer Cellular Bravo. Let me know if you guys still want it.
Markus
Well, most of us have move to newer phones, I have a Droid Ultra and a Razr M and with gingerbread working 100%, any froyo version its not very useful at this time.