Database Users

[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.

Loaded rubiX, freaked out, now am i FUBAR?

Alright so I flashed rubiX, but it started going haywire. Volume started flipping balls, then it kept going in and out of honeycomb (when you press home and it zooms out). Also my home and menu button lights were really dim and flickering. So I SBF'd it back to stock, so I was then running a completely stock, new, fresh droid x. I began to root via z4 and since my battery door was off it accidentally came off. Now I m stuck on the motoroala M bootscreen. I can get into bootloader, i can SBF, but even after SBF flashing, nothing. Holding Home+Power button does nothing. Help me out fellows! I shouldn't be rooted at this point since the battery came out during rooting. Ideas? I need my phone for tomorrow, I will be up all night.

Should I take it back to Verizon? I need to know before I get off work. It never rooted, but the z4 root app is on there. Will the void because of that?
LET ME KNOW!

If it doesn't boot they wont be able to tell. I would recommend taking it to Verizon

Thank you sir. I mean it is literally completely stock, bootstrapper and z4 apps are on it, but i sdf'd it 5 or 6 times. Just going to cross my fingers and bring it to verizon

Yes I have gotten my phone to a point like that in the past. I took it to Verizon, and they didn't even ask what happened they just gave me a new one

You sir are a scholarly gentleman. Leaving work now.

Thank you very much. I do try

Isnt it "a gentleman and a scholar"? Lol
Sent from my DROIDX using XDA App

haha I guess. So I will be taking it back to Verizon tomorrow. If they ask if i rooted ill be like wtf is that?
THe sbf should have cleared everything, right?

Yes the sbf should clear everything. And if the employee knows enough to ask about rooting, they are usually sympathetic as they probably do it themselves. So you are all set

Sounds good. Leaving for verizon store right now, ill tell you whats up when i get home

Got it coach! They're overnighting it, will be here monday!

[Q] Sprint Service and Repair

So my epic was rooted. I was on the stock rom, just removed all the bloatware. I kept getting the google services framework force close and random reboots. I ODIN'd back to stock froyo ec05 (before the Gingerbread update came out) and it was still happening. I have TEP, so I figure I'll just bring it in to Sprint and maybe they can reflash it or something. I drop it off, they tell me to come back in 3 hours. I return and the girl brings out this piece of paper with some stats on it. She asks me if I have ever rooted my phone. I want to say no and play dumb, but it looks like I'm busted anyway. She shows me the sheet of paper, it says "version in:" and below that "version out:" She tells me this is how they can tell the phone has been rooted, it's blank next to one of them. She also tells me that because it's been rooted they can't do anything with it; no reflashing, no repairs, nothing. She tells me I can pay the $100 deductible and get a replacement but that's it. She also tells me her phone is rooted, and most of the employees there root their phones too. So I leave and reflash with ODIN once again. My problem seems to be resolved, but then I ran across this post.
http://forum.xda-developers.com/showthread.php?t=1211794
According to Squishy, it sounds like they could have at least reflashed it. Is it at their discretion? Did they just not want to deal with it? Or maybe the policy has changed?
Has anyone else tried to bring a previously rooted phone in to Sprint and had this happen?

Crazy people. Good to know that they know.
Sent from my SPH-D700 using XDA App

Yea, it's at the individual stores discretion, based on how big of an ass the manager is, and that store's exchange attainment scores. Too many unnecessary exchanges, comes back to hurt a store's goals, so some manager's will institute policies as such, to give themselves leeway. Take it to another store, preferably not a corporate store.
Sent from my SPH-D700 using Tapatalk

after a fresh odin all root remnants are removed. The sprint rep was just stupid.
Sent from my SPH-D700 using XDA App

brimart said:
So my epic was rooted. I was on the stock rom, just removed all the bloatware. I kept getting the google services framework force close and random reboots. I ODIN'd back to stock froyo ec05 (before the Gingerbread update came out) and it was still happening. I have TEP, so I figure I'll just bring it in to Sprint and maybe they can reflash it or something. I drop it off, they tell me to come back in 3 hours. I return and the girl brings out this piece of paper with some stats on it. She asks me if I have ever rooted my phone. I want to say no and play dumb, but it looks like I'm busted anyway. She shows me the sheet of paper, it says "version in:" and below that "version out:" She tells me this is how they can tell the phone has been rooted, it's blank next to one of them. She also tells me that because it's been rooted they can't do anything with it; no reflashing, no repairs, nothing. She tells me I can pay the $100 deductible and get a replacement but that's it. She also tells me her phone is rooted, and most of the employees there root their phones too. So I leave and reflash with ODIN once again. My problem seems to be resolved, but then I ran across this post.
http://forum.xda-developers.com/showthread.php?t=1211794
According to Squishy, it sounds like they could have at least reflashed it. Is it at their discretion? Did they just not want to deal with it? Or maybe the policy has changed?
Has anyone else tried to bring a previously rooted phone in to Sprint and had this happen?
Click to expand...
Click to collapse
Before i got into flashing roms, themes, mods. The only thing i knew how to do was root. Before i even knew odin and this forum existed, i bricked my phone 2 times within a week.... Both times didn't know any better other then to take it the closest sprint repair store. Both times they replaced my phone which was rooted and bricked when I walked in....
Moral of my story- it's the stores discretion.
Sent from my SPH-D700 using XDA App

Mmm, yeah... Previously activated Droid...

As you can tell, I bought a used Motorola Droid on EBay...
Works fine and all, but it was still activated on the previous user's account. And I bought the phone from a resale company, so I have no way of contacting the previous owner...
How do I deactivate this Droid and use out on my own account?
Sent from my Droid using XDA

Odds are that it's already had the data wiped and been reset. If not, since it's on CM7 as noted in your sig you can simply boot into recovery and do a data wipe or do it from within the settings menu once the phone boots and you're on the homescreen.
Like I said though, odds are if someone knew enough to flash a Rom, they were kind enough and smart enough in terms of their own interests to wipe the phone before selling it.
Also, I'll say it nicely cause you never know what kind of mood you'll catch a mod in =p Make sure you post in the right sections, as this should really be in Q&A.

Well, I didn't buy it with CM7 preinstalled, I rooted and flashed CM7 myself. Clearing data does nothing, I already did that when I installed CM7.
It's a CMDA phone, so like I said, clearing data does nothing.
Swyped from my OG Droid running CM7

I'd take the receipt and Etsy posting to Verizon and see if they can override it.

Ah, misunderstood what you were needing to do. Yeah, guess you'll have to go to VZ. An SBF will let you activate it again and sync a google account, but it will still try to activate on the old number AFAIK.