Database Users

Sbf for Motorola Bravo?

The Bravo is Bricked! I rooted it, got board, tried to install custom ROM through a Droid method (REALLY STUPID OF ME!!), and now my phone is stuck in boot loops. It goes into recovery and all, bootloader too, so I fugured I could just flash an sbf with RSD and get it back running again. The only problem is I can't find an sbf file for this phone ANYWHERE and it's driving me crazy!! So if anyone has any information on where you could find an sbf file for this phone or when it would maybe be available I would love it
Thanks

Unfortunately,
Since AT&T is the only carrier that has this phone, you will have to wait until an upgrade is released from AT&T
And it would have to be a major update such as 2.1 -> 2.2 where the SBF is available.
You could always try calling AT&T and see what they can do for you in terms of warranty....long shot

So, no?
Come on, I have got 400 viewers of this thread, nobody has any ideas?

Yea dude I have been wating for the same thing. I have been pretty hesitant to do any major modding to my bravo until I know I can get it back from the grave should I do anything to totally mess it up. Is there no way to get what we need untill an update is released for the phone. I am pretty new to android having previously being a jailbroken Iphone user for years, but is there no way to get what we need from the bravo somewhere in its file system. Like I said i am still learning the different aspects of modding android so if anyone does know a solution, I'm all ears. Thanks.

Haha
Yea, got a little to crazy with it. It's because I realized it's potential, and noticed at had roughly the same specs as the Droid X, not thinking I ran the Bootstrap thing that allows custom recovery, so I could use an awesome custom rom, and it died. I mean I could completely recover it, it goes to the bootloader and the recovery, but hey I think were in luck, 2.2 for this things coming 1st Q 2011, and it'l be floating around somewhere, someone will grab it.

Awesome news. thanks for the heads up.

hey, where did you hear that it was getting updated to 2.2 in Q1? I can't find any news about that on the web, although it'd make me really happy...

I feel bravo is the loneliest phone in the world.

I also haven't seen anything about a 2.2 upgrade. Checked the Motorola upgrade site and they don't show anything in any quarter of any year regarding upgrading to 2.2. Could be a pipe dream.
Have you tried Super One Click or z4root to see if you can recover your system.

may be because the Motoglam (similar if not almost identical to the Bravo) is getting an upgrade in Asia where someone thought that the Bravo is getting the upgrade... I hope it does, would be nice for it to happen...

dontbejeff said:
may be because the Motoglam (similar if not almost identical to the Bravo) is getting an upgrade in Asia where someone thought that the Bravo is getting the upgrade... I hope it does, would be nice for it to happen...
Click to expand...
Click to collapse
It's not similar at all.
Motoglam -> TI OMAP3430 (500 Mhz)
Bravo -> TI OMAP3610 (800 Mhz)

And similar doesn't mean that much, the Defy is 99% identical with only the addition of a flash and a search button on the face plate, but some of the things that can be done with modifying the defy can't be done (yet) on the Bravo.
Now the other major difference in he Defy and Bravo is that the Defy is is a non US phone, looks like mostly EU.
From what I can see here http://www.motorola.com/Support/US-EN/Android_Products/Software_Update_Landing_Page?vgnextoid=69fd5fc943dc0210VgnVCM1000008806b00aRCRD so far there are no plans for updates.

2.2 sbf..
ay killa...don't know if you knew this or not but there's a 2.2 SBF out now through Bandroidx. Works straight through Bootloader and RSD. Pretty automatic. Flash is sweet too.

brick?

i was running fission rc1 on my d2g, used frm to download stock d2g deodexed blah blsh, flashed it, stuck on motorola m screen. cant get it to boot to bootstrap recovery for ****. only regular recovery...i could cry
edit: omg im gonna throw up. please tell me theres something i can do.
EDIT: ok...so if it is bricked and i have the $1.99 or $2.99 insurance, whatever....can i get it replaced...and if not, what if hypothetically speaking...it was smashed by a car...could i then get it replaced?

I am no expert, but lets try this, start the phone and as soon as the M appears, immediately pull the battery, and the put back in and start the phone. Lets see if the phone goes into ClockworkMod, and if it does, you can do a restore. Let me know how you make out.
MICP1480

no luck dude. thanks tho
EDIT: just got off the phone with verizon, theyre sending me a new one. wasnt hard at all, i played dumb and acted like bootloader mode was a whole new world to me, she had me wipe the data and reboot, of course i had already done that to no avail so of course it didnt work this time either, she put me on hold and talked to a tech and then came back and said they'd send out a new one.

botnryan said:
no luck dude. thanks tho
EDIT: just got off the phone with verizon, theyre sending me a new one. wasnt hard at all, i played dumb and acted like bootloader mode was a whole new world to me, she had me wipe the data and reboot, of course i had already done that to no avail so of course it didnt work this time either, she put me on hold and talked to a tech and then came back and said they'd send out a new one.
Click to expand...
Click to collapse
They will check your phone to make sure there is no ROM's and that it is not rooted as that voids the warranty.

This just means moto needs to release the sbf for the D2G so we can fix them instead of moto/verizon getting a bunch of returned devices.
Sent from my DROID2 using XDA App

miketoasty said:
They will check your phone to make sure there is no ROM's and that it is not rooted as that voids the warranty.
Click to expand...
Click to collapse
really? and how will they know if its all messed up and wont even boot? plus i did a data and cache wipe of the phone thru the regular recovery, will that not kinda wipe away anything incriminating? Not to mention the last rom i flashed was the stock d2g rom, just deodexed and such

When you flash a custom ROM or root the phone, evidences remain in /system which survives data wipe.
It is another question how would they see that if phone is not booting.
If you sent it in already and you do not receive a nasty 600 dollar invoice in the following days/billing cycle stating you have voided the warranty, then they really do not check.
I guess all they do is to flash the oh-so-desired-by-everyone stock SBF and sell it as refurb or give it as replacement phone.

leobg said:
When you flash a custom ROM or root the phone, evidences remain in /system which survives data wipe.
It is another question how would they see that if phone is not booting.
If you sent it in already and you do not receive a nasty 600 dollar invoice in the following days/billing cycle stating you have voided the warranty, then they really do not check.
I guess all they do is to flash the oh-so-desired-by-everyone stock SBF and sell it as refurb or give it as replacement phone.
Click to expand...
Click to collapse
i havent sent it in yet as ill be recieving the replacement tomorrow...any ideas on how to prevent this? could a good strong magnet wipe the memory completely?

botnryan said:
i havent sent it in yet as ill be recieving the replacement tomorrow...any ideas on how to prevent this? could a good strong magnet wipe the memory completely?
Click to expand...
Click to collapse
without the sbf to get back in there isn't really much you can do. The stuff is on there and you don't have a way to get back in.
try to get into recovery by:
pulling battery (or powering down phone)
while completely off plug in to wall via charging cable
turn on phone while connected to power (if you get the battery screen press power again)
you should hopefully be in recovery (not sure if this method works on D2 G but it does wonders for the D2 but it's worth a try.)
unless you really flashed crazy and messed up recovery theoretically bootstrap should be there unless completely wiped it.

newk8600 said:
without the sbf to get back in there isn't really much you can do. The stuff is on there and you don't have a way to get back in.
try to get into recovery by:
pulling battery (or powering down phone)
while completely off plug in to wall via charging cable
turn on phone while connected to power (if you get the battery screen press power again)
you should hopefully be in recovery (not sure if this method works on D2 G but it does wonders for the D2 but it's worth a try.)
unless you really flashed crazy and messed up recovery theoretically bootstrap should be there unless completely wiped it.
Click to expand...
Click to collapse
dude i tried that with both usb and wall charger, no luck either way, i flashed stock d2g deodexed blah blah rom over fission rc1 and this happend. totally blows my mind. got my replacement today, super glad to be back away from the eris lol

botnryan said:
dude i tried that with both usb and wall charger, no luck either way, i flashed stock d2g deodexed blah blah rom over fission rc1 and this happend. totally blows my mind. got my replacement today, super glad to be back away from the eris lol
Click to expand...
Click to collapse
Just checking I didn't see you tried that specifically glad you got your replacement now you know to be very careful as the sbf isn't out yet.

sorry if that last post came off harsh lol, didnt mean it to, read it again and was like geez dude chill (at myself). So im really hoping they dont charge my ass for this, but i dont see how theyre going to know. if you flash an sbf, does it unroot it? Because, if thats what they do to phones like mine, then they wont know i had it rooted/rom'd right?

botnryan said:
sorry if that last post came off harsh lol, didnt mean it to, read it again and was like geez dude chill (at myself). So im really hoping they dont charge my ass for this, but i dont see how theyre going to know. if you flash an sbf, does it unroot it? Because, if thats what they do to phones like mine, then they wont know i had it rooted/rom'd right?
Click to expand...
Click to collapse
Yeah SBF put's it back to stock from factory software. Unless they have another way of getting in and see what was in there they won't know much unless after they SBF they can pull the residual data in data or cache but I don't think they will go to that extent only if D2 G's start dropping like flies.
If they would just release the SBF for us we could have fixed your phone in 15 minutes and it wouldn't have cost them anything at all.

newk8600 said:
Yeah SBF put's it back to stock from factory software. Unless they have another way of getting in and see what was in there they won't know much unless after they SBF they can pull the residual data in data or cache but I don't think they will go to that extent only if D2 G's start dropping like flies.
If they would just release the SBF for us we could have fixed your phone in 15 minutes and it wouldn't have cost them anything at all.
Click to expand...
Click to collapse
alrights, thanks man. i feel they probably wont be able to find anything out but im still going to use up my 10 day period i have to send the phone in just in case the sbf is magically released in that time period.

[Q] Is there a fix I can't find?

I have just switched over to verizon from AT&T a couple of days ago. It was an impulse decision as I was only in the Verizon store with my girlfriend to get a her a new phone. I was showing the sales guy my pimped out Samsung Captivate and explaining to him him how easily these things can be manipulated and how much I loved my Cappy. Thats the last thing I remember. I woke up to find I had switched my service (3 lines) over to Verizon and I was now the owner of a Droid X.
I loved my Captivate and had no thoughts of ever switching but they had a promotion going on that blew my AT&T plan out of the water so financially it was a good decision. But I am beginning to wonder if I haven't made a mistake.
Out of the box, the DX is rebooting pretty often. I had planned on getting on here when I got home to find the latest and greatest ROM anyway so I didn't worry about it too much.
I am currently running Liberty 1.0 as my first flash. That is of course after flashing .340 which I read may or may not fix the rebooting issue. I am liking the ROM but the random reboots still persist. Its beginning to get too much to bare as I have yet to have one phone conversation that isn't interrupted by the phone powering down by itself.
I have searched for any word of a fix for this but I haven't found any definitive answers other than to do a factory reset. I have done that several times, as well as reflashing .340 and Liberty to no avail.
Before I take 3 phones back to Verizon and crawl back to AT&T and beg for forgiveness does anyone have a definitive solution for this?
Its worth mentioning that I bought my daughter a DX as well to replace her Cappy (she is NOT happy BTW), and it does the same thing. It is still stock out of the box.
Thanks in advance for any replies.

I have a Dx and haven't had this reboot issue, however, my sister traded in her iPhone for an x on my advice and now she's having the same issue you are. I was going to have her flash to liberty and do a system restore but obviously that hasn't worked for you. Hopefully someone will have an answer to this problem
Sent from my DROIDX using XDA App

Send the phones back to Verizon, that is not normal.

In my opinion, not to say you don't know what you are doing which I am sure you are, I know you are well aware of the risks of flashing roms.
I hear more people having issues with Droid Xs that have been re-ROMed, flashed, themed, etc, then I do people with stock DXs that are rooted and cleaned up of bloat.
While my DX might not be clean out the box, it's still in prestine shape, rooted and even flashed to Cricket. I have never had a single issue with it unless I am bricking it or messing with it myself.
A lot of times, people mistake the phone as the issue. These were $600 phones when released, still are (give and take a few bucks lol). I doubt the issue is hardware. Send it back to VZW or try the Full SBF 320 using RSD Lite. It's been the talk of the town.
Could be that there's a bad batch of DXs going around that have just been released? None the less, VZW can get you replacement DXs over night practially.

Sbf to stock and reflash liberty. Or take it back a get a new phone.
Sent from my DROIDX using XDA App

Ben's said:
In my opinion, not to say you don't know what you are doing which I am sure you are, I know you are well aware of the risks of flashing roms.
I hear more people having issues with Droid Xs that have been re-ROMed, flashed, themed, etc, then I do people with stock DXs that are rooted and cleaned up of bloat.
While my DX might not be clean out the box, it's still in prestine shape, rooted and even flashed to Cricket. I have never had a single issue with it unless I am bricking it or messing with it myself.
A lot of times, people mistake the phone as the issue. These were $600 phones when released, still are (give and take a few bucks lol). I doubt the issue is hardware. Send it back to VZW or try the Full SBF 320 using RSD Lite. It's been the talk of the town.
Could be that there's a bad batch of DXs going around that have just been released? None the less, VZW can get you replacement DXs over night practially.
Click to expand...
Click to collapse
Ben you are right about people messing up phones by flashing. But generally taking them back to stock will fix any issues that have risen from tinkering.
My issue is that mine did it out of the box. My daughters did as well.
Funny thing is just this morning I updated my daughters with the .340 update and it seems to have stopped. Its been quiet now for about the last 30 minutes. I reflashed .340 on mine at the same time and it has rebooted about 4 times while I type this message. Maybe my daughters is fixed, but mine is definitely not right.
Thanks for the comments.

My sisters phone is also doing this bone stock. It doesn't always reboot sometimes it locks up and she has to pull the battery. She's taken it into the Verizon store and they reset it to stock (not sure exactly what they did). That didn't fix it so she took it back to exchange it and they told her " that's normal, sometimes you have to pull the battery." So they wouldn't exchange it.
Sent from my DROIDX using XDA App

Sadly this is has been a small issue with the DX, it's been posted many times. Mine did it when I first got it back in August and at first I was blaming Handcent on the reboots. Then for some reason it just stopped and I have never seen it reboot on it's own. Was it the update to 2.2 or removing Handcent? I've reinstall Handcent since so I honestly I don't know. Side note I still blame Handcent on the phones lag because when I uninstall it the screen redraws and the lag goes away.
Anyway there is a great big long thread on this at the Moto DX forums and Matt's (forum admin) advice was to return the phone for a new one. I would arm myself with a printed copy of the thread in case Verizon wants to throw a fit.
For the record I just dig this phone. I'm stock, rooted with just bloat frozen. It's been a great phone after the teething problems were solved.
fasthair

Gingerbread droid x leak update.zip

Here is the official leak for droid x gingerbread. Make sure to wipe/data before install. Warning!! There is no official root yet. Make sure to make a backup. I take no respnsibility to what happens to your phone. I get stock quadrant scores of 1800. You have 72hrs to download it. Enjoy!!
http://androidforums.com/droid-x-al...ingerbread-2-3-3-update-zip-released-tbh.html
Sent from my Droidx-Gingerblur 2.3.3

;;banana;;
Sent from my DROIDX using XDA App

I just got done upgrading to Gingerbread on the DX! Used the Team Black Hat app on the market (happily paid the $2), Koush's Droid X bootloader, and Clockwork Recovery. The TBH app downloads the gingerbread rom right onto your SD card into a zip file. Opened up the bootloader, pushed the button to boot into recovery, and it did. Then, using the volume buttons, scrolled down to make a backup. Done. Then scroll to "install from zip", not the "update" option. Use the camera button to select your options, by the way. From the install from zip option, it pulls up the folders on your SD card. Selected the teamblackhat folder. The zip was right there, highlighted and selected, and away it went! When the prompt said it was finished, I navigated to the "reboot" option, and it rebooted. Right away I could tell it was different because the Motorola logo was colored red. It took probably 5 minutes to fully load, but when it did, I had Gingerbread! All of my apps and settings were there. Didn't have to call and re-activate my phone, didn't have to login to google, nothing! Not sure if it pulled in the settings from the CWR backup or not, probably not. Now that I think about it, this is a Motorola release, intended to be an upgrade, not a full ROM swipe. The instructions and files are at mydroidworld... Have fun!

I want to do this but I don't want to lose root and then have to wait til root is available. How's it running sop far?
Sent from my DROIDX using Tapatalk

Awesome. New color scheme. No lag. Home launcher is sweet. Custom icons on dock. Blur widgets still ugly but their interfaces are cool card like tiles. Still playing but really like so far.
Sent from my DROIDX using Tapatalk

Not all apps are in market...including Slingplayer which I need...dealbreaker
Sent from my DROIDX using XDA App

can someone kindly de-odex the IME and post an apk for it?

the 1 thing i wish they would've fixed in gb is the mother effin unlock/lock screen lag
(but they didn't)

webmastir said:
the 1 thing i wish they would've fixed in gb is the mother effin unlock/lock screen lag
(but they didn't)
Click to expand...
Click to collapse
It's pretty easy to eliminate that. (Atleast I don't experience it anymore and all I've done is root/overclock. (Yeah even as I write this I remember there isnt a root yet for 2.3.))
Sent from my DROIDX using XDA App

gc14 said:
Not all apps are in market...including Slingplayer which I need...dealbreaker
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You can always download them to your phone via https://market.android.com/

chbennett said:
It's pretty easy to eliminate that. (Atleast I don't experience it anymore and all I've done is root/overclock. (Yeah even as I write this I remember there isnt a root yet for 2.3.))
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
The only way I know to eliminate the lag is to run a lock pattern. I have OC'd to 1.2 and its still there. While it is less, its still not gone compared to a vanilla lock screen.
But I'm with you webmastir, if their was one thing, the lockscreen would be it. The second item I would have wanted was the sleep effect the nexus S has.

Someone needs to root this!!

Wait it doesn't do the CRT shutdown animation?
There goes half my excitement. It's the little things.

SomeDooD123 said:
Someone needs to root this!!
Click to expand...
Click to collapse
Got root already ...just waiting on instructions
Sent from my DROID2 using XDA Premium App

(-)2 known issues so far (+)YOU LOSE NO DATA ON UPDATE.
The two issues with the update:
1) A small sync "icon" remains on top of the notification tap. I do not actually believe that it is in a constant "syncing state", its just an icon that remains at the top.
2) And this is a big one. All four of the Droid X hardware keys at the bottom, have there lights that will not go off as long as the phone is "awake" ie, your using it. After it is back in its idle unused standby state, lights go back off. Not an issue with performance at all, but a huge cosmetic issue and annoyance more then anything as the lights on the hardware keys shine very brightly.
As far as updating, or those on the fence about it. The update total time, that I documented takes around 10 to 15 minutes depending on how much data you have to back up before adding the update. I have a lot more data then the average user, so mine took around 15 minutes from start to finish. 8 minutes to back up. 2 minutes to apply update, and 5 minutes after the first reboot to apply changes. The backup time is the only one that will very depending upon your data. The other times are going very dependent on your system data (SD card not included, as this is not needed to be backed up, because it already is, because its on a physical external card obviously) but be approximative to the time.
On the plus side, there are way more pro's. There are some that I have noticed that no one has mentioned on any forum yet. The biggest of these is the change to voice synthesis speed. Before the voice only talked in one speed. The new update gives the option to change the built in Android voice synth to almost 6 different speeds of reading back to you, very very amazing. And of course, SPEED. The new update is the first update in a year and a half that I have been modding and using the Android operating system that I have had to really sit back and say "wow". I came from the Eris until the X came out, made the change immediately. The new interface and color changes are pretty much what CM has been doing since his releases began. And the biggest pull for me to apply the update: YOU LOSE NOTHING. NO SIGNING IN TO GOOGLE, NOTHING. NOT A SINGLE CHANGE TO YOUR HOME SCREEN, NOTHING IS LOST, BECAUSE ITS AN OFFICIAL UPDATE THAT WAS REJECTED. Trust me, with all the roots and ROM's that we were using on are Eris, this is a no brainer upgrade. Your not losing anything because once the the OTA update rolls out, after the root (and it will come, only a matter of time) you can go back if you like. For me, I am sure Moto leeked this, they had to have, there is no other explanation. I have seen this time and time again since Androids release. I wrote just a little over 24 hours before hearing anything about the leek, I wrote to my facebook friends "dont worry, i am sure a leek of the rejected update will make its way around" Less then 24 hours after saying that on Sunday, it happened. The only reason I would say not to apply the update, is because you have NEVER DONE A MOD TO YOUR ANDROID DEVISE. If you can afford to maybe have something go wrong, then do it. On a noob level, this is probably a 2 or 3 on a scale of 10 being the hardest. The two known issues, I am sure will be worked out. I am almost even willing to bet, since Moto did not give and official statement of the leek when the whole damn world was buzzing about yesterday. They will even put out a patch or update to those who updated early with the leek. If they didn't want us having it, they would go public warning us, like they have before. It could happen later today they say, DO NOT UPDATE, BECAUSE _____ <-- insert reason there. That is my personal educated opinion only. Do not expect it to happen, just dealing with these types of things for the last 10 years now, and given there hush hush while this is being passed around, at the same time Verizon said no, it leads me to believe the devs, or at least one of them said "lets give the people what they want, screw the system". Because as we all know, nothing gets pushed without the carriers approval. We waited months for Android 2.1 after HTC went on record and put out statements saying to the affect "Hey guys, we did are part, its in Verizon's hands now, were sorry you haven't gotten it yet, but we cant force then to put it out." You who wait, could be waiting for months guys, you could be waiting till later this afternoon to get the OTA. Its anyones guess. After hearing I would lose no data because it was an official "rejected" update, it was a no brainer to me. Not lose any data, and get the update I wanted? Downloaded and applied with in the hour last night. two bugs, I can deal with, when the OTA comes out, I have my whole system of 2.2 completely as it was with no changes and all backed up to apply it if I chose too. Hope that helps gives an idea on whats going on so far. If your going to do this, and never have before. -PLEASE, -READ AS MUCH AS YOU CAN BEFORE YOU BRICK SOMETHING OKAY? THERE ARE VIDEOS, MANUALS, MESSAGE BOARDS LIKE THIS TO HELP YOU. IF YOU DONT FEEL CONFIDENT YOURSELF, DONT< WAIT. 2.2 is more then perfect to wait it out for 2.3. Sorry for any typos there might be. -Me.

journalistically said:
.... -Me.
Click to expand...
Click to collapse
Glad you remembered to put "-Me" cause I wouldn't have known

journalistically said:
And the biggest pull for me to apply the update: YOU LOSE NOTHING. NO SIGNING IN TO GOOGLE, NOTHING. NOT A SINGLE CHANGE TO YOUR HOME SCREEN, NOTHING IS LOST, BECAUSE ITS AN OFFICIAL UPDATE THAT WAS REJECTED. Trust me, with all the roots and ROM's that we were using on are Eris, this is a
Click to expand...
Click to collapse
I wouldn't say that. I got stuck in a bootloop after doing the update, and I've read on some other forums people have has similar issues when they didn't do a wipe before updating. Once I SBF'd myself back to stock then did the update, everything was fine, and loving this leak.
I wouldn't use not losing your data as a plus to do this. There is always the risk of losing your stuff, always make a backup before you try anything like this.

Hate to say this,
But the new Moto Blur is awesome.
I like the ability to make custom app drawers,
The color scheme is easy on the eyes,
Theme is nice
so many new options,
The dock is different, and I like it
I dont have the sync icon showing all the time like others.
My hard keys dont stay lit all the time like others
battery life is the same
performance is........well for me, a solid 60% improvement.
This was worth it big time. Hell at this point, I dont care about root, I am happy. I only rooted to put roms on, to get rid of 2.2 moto blur.
Wife is jealous, wants this on her Droid Pro. ha ha ha honey, shoulda kept your DX.

Does anyone have some screen shots of GB on the Droid X ?

It's not the 2.3 release that leaves the perpetual sync at the top.
I have that in 2.2. Sometimes it goes away but most often the sync icon is there on the top.

Getting replacement phone, want to root this phone, please help

I have a Motorola Droid X from Verizon and allowed the OTA update to install. I now have v 2.3.3 and it looks really nice. Gingerbread. However, I noticed that my superuser was gone and no app would bring it back. I read all sorts of things about flashing back the ROM to Froyo, rooting, then installing a special 2.3.3 update. That is going to wipe my phone and maybe my card so I did not want to do it. But, I noticed today that I have a few black horizontal streaks in the LCD screen, easy to see on a white background. This is bad, the LCD screen has bad pixels and is on the way out so I put in a claim for a replacement Droid X and it will be here tomorrow.
Since this phone will already be "wiped" until I install all my stuff again, I would rather get this rooting done now and not have to worry about it later. I have no idea if the phone I am getting will be 2.3.2 or 2.3.3 but will find out tomorrow when FedEx gets here.
Somebody please give me some URLs to "known to work" rooting on a Motorola Droid X that I can use and tips and advice. I had no problem rooting until I hit the brick wall of 2.3.3. If ever there was a time to get this over with, that would be now. Also, will I be not using OTA updates anymore and where will I get future updates? I can use and own a Linux machine, have flashed BIOS and older phones, but really cannot afford to mess this one up. Please give good links and advice. Thank you.
Sincerely,
~Ohmster

Ohmster said:
I have a Motorola Droid X from Verizon and allowed the OTA update to install. I now have v 2.3.3 and it looks really nice. Gingerbread. However, I noticed that my superuser was gone and no app would bring it back. I read all sorts of things about flashing back the ROM to Froyo, rooting, then installing a special 2.3.3 update. That is going to wipe my phone and maybe my card so I did not want to do it. But, I noticed today that I have a few black horizontal streaks in the LCD screen, easy to see on a white background. This is bad, the LCD screen has bad pixels and is on the way out so I put in a claim for a replacement Droid X and it will be here tomorrow.
Since this phone will already be "wiped" until I install all my stuff again, I would rather get this rooting done now and not have to worry about it later. I have no idea if the phone I am getting will be 2.3.2 or 2.3.3 but will find out tomorrow when FedEx gets here.
Somebody please give me some URLs to "known to work" rooting on a Motorola Droid X that I can use and tips and advice. I had no problem rooting until I hit the brick wall of 2.3.3. If ever there was a time to get this over with, that would be now. Also, will I be not using OTA updates anymore and where will I get future updates? I can use and own a Linux machine, have flashed BIOS and older phones, but really cannot afford to mess this one up. Please give good links and advice. Thank you.
Sincerely,
~Ohmster
Click to expand...
Click to collapse
Let me start by saying, there isn't any possible way to brick this phone. This security comes from the SBF files we can use to return the phone to pure stock.
Secondly, you can use a one click method to root the phone straight from 2.3.3, even with the .602 update.
Follow the instructions here:
http://rootzwiki.com/showthread.php...ded-for-Windows-Linux-OSX)&p=76046&viewfull=1
And even though it says Droid 3, it supports most Motorola phones. (Including the Droid X)
I hope I could help =D
Sent from my DROIDX using XDA App