Ok so I have a rooted droid x2 with bloatware frozen, well my battery puked, went to Verizon and got a new one, but I made the mistake of letting one of the guys put it in well he decided to do a factory reset and it is now stuck at the setup screen and its blank. What do I do? It got reset with bloatware froze and rooted. Any help would be great cause even after I let loose on them and had to be escorted out by security officers my phone will not be replaced.
And I know I am an idiot for letting him touch it!
Rule 0: Don't do anything requiring security to escort you out.
Rule 1: Don't let people touch your phone.
Have you tried using the SBF to flash it back to factory state? For me, that'd be step one.
Actually, step one would be pulling the battery, but I'm assuming you've tried that.
Yes tried both, and unfortunately didn't work.
Is there anyway to apply through sd card? Or an easy rsd way?
The SBF isn't an update.zip file, so no SDCard method.
nene95 said:
Is there anyway to apply through sd card? Or an easy rsd way?
Click to expand...
Click to collapse
Have you tried going into recovery and wiping your data and cache? This would of course be a factory reset.
Sent from my Droid X² using XDA App
Yes it still went back to blank setup screen, would the frozen bloatware cause this?
I'm not sure. Have you tried posting this problem over at the Droid X Forum?
Sent from my Droid X² using XDA App
If you aren't sure if you flashed it correctly with RSD, try following this post.
When you say the startup screen is blank, what is it doing? Like, if you were describing it, you hold the button to power it on, then...?
It powers up goes through the droid eye, then gets to the blue screen where your supposed to call to activate your phone but the top part is normal and the lower part is dark blue.
Does it respond when you touch it, or is the screen frozen? Is the entire screen fine when the droid eye is on it, or is the lower part messed up then as well?
My thoughts on the subject are this; A) You froze something that's needed to go through start-up, or B) The phone got physically damaged somehow. If the screen is responsive while the bottom part is messed up, I'd lean more towards something physically went bad.
Assuming you still have service with Verizon, have you thought of taking it to a different store? Or even sending it in for repair?
Sounds like something else went wrong, as far as I know any frozen apps simply get defrosted with a factory reset.
If it is a software problem then a successful sbf will clear it up. If you are getting a PASS after sbf and it's still not working then your battery "puking" was just a symptom of a larger hardware problem.
Sent from my DROID X2
I can use the pull down notifications so its not froze up.
Sent from my DROID X2 using XDA Premium App
Sounds like a bad screen.
Sent from my DROID X2 using XDA App
Related
So I had originally put the leaked non-rooted GB update on my X2 with no issues. I had been running that for a few days when I decided to replace it with the p3 pre-rooted version. I did an SBF back to Froyo without issue, did the Gingerbreak, etc. The pre-rooted version went on fine with no errors, but then when it came up, the digitizer was unresponsive.
I did several factory resets, SBF back to Froyo again (several times), but the digitizer is still unresponsive....I now can't get past the setup screen. I also noticed that the emergency dial button has a blue highlight around it, and when I press the power button, the "Power Off" item in the menu has a blue highlight around it....almost like if I had a trackball or arrow keys, I could move the highlight....I wonder if it knows the digitizer is not functioning?
Has anyone else seen this? I see one thread on the Motorola site where two people have the same issue after updating the GB (presumable the OTA version since they are posting on that site), but no helpful responses.
My phone is only 3 weks old, so I am tempted to just SBF and try to get a replacement out of Verizon, but thought I would check here first in case I can fix it....or figure out what went wrong so it doesn't happen again.
i'm 1 of the people thats having the SAME EXACT problem as your having............ive sbf'ed like 100 times (no joke) and factory reset about as much............i'm just goin to take it back and hope i can get a replacement..............
I called Verizon and I was on my exact "30 day" since I bought it, so they are shipping me out a new one overnight. I have insurance, so I could have gone through them I suppose if it was after 30 days, but at least I'm getting a brand new one. Now I just have to decide if I'm willing to try it again.
So if more than one person has this issue, I'm guessing it is NOT a hardware problem. However, it is odd to me that doing the SBF doesn't fix it. I wonder what could be happening, maybe someone with more knowledge about this will be able to shed some light.
Unless we figure out what happened and how to potentially fix it, this seems pretty close to a bricked phone. I wonder it is something in the GB update in general, or something going wrong in the manual update!?!?!
Don't these phones have some type of manufactures warranty?
Edit: The phones carry a one year warranty wether or not you purchase insurance. If the hardware fails, as it has in your cases, they will replace it for free.
Sent from my DROID X2 using XDA App
I did get it replaced, I am more interested in why a handful of us had this happen upon GB updating. Seems odd.
Sent from my DROID X2 using Tapatalk
blickley said:
I did get it replaced, I am more interested in why a handful of us had this happen upon GB updating. Seems odd.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
Not All Android Phones Are Built The Same.
I noticed you didn't say you factory reset after you sbf to 2.2.2 in your original post. I don't claim to know for sure but some people are not following this direction, and it MAY be one of the problems. It is recommended that all directions are followed exactly for a successful update. The only way to tell if there is a problem with the method is if everyone follows it to the letter.
Sent from my DROID X2 using XDA App
Thanks, yes I did factory reset after the SBF. Oh well, this doesn't seem to be widespread and I got a brand new X2 out of it.
Hi.
I was flashing my phone back to stock gingerbread and after doing some verification and stuff my phone just went crazy.
The touchscreen clicks on everything by itself, sometimes it's so hard to unlock the pattern.
The screen is clean, nothing on it, nothing went inside the phone.
flashing back to any other ROMs wont work so im assuming that it's the hardware problem.
I was going to go to the verizon retail center and ask for the exchange but I already made an exchange from tbolt to x2, and now I'm wondering if I can get my phone exchanged for the malfunctioning.
Or any way that I can get this thing back to normal.
Thank you.
I'm sure that as long as you can reproduce the issue they won't have a problem replacing it with another X2. Just make sure you SBF before you make the exchange.
Well that's the thing.
It wont show up on rsd lite 5.3.1 with PC mode and USB debugging on.
------------------------------------------------------------------------------------
i factory reseted by using the recovery mode. This is really annoying and driving me nuts.
As long as it's on stock firmware and SU isn't there or anything that requires root you should be okay.
Alright. Thanks for the comment!
stevebizkit said:
Well that's the thing.
It wont show up on rsd lite 5.3.1 with PC mode and USB debugging on.
------------------------------------------------------------------------------------
i factory reseted by using the recovery mode. This is really annoying and driving me nuts.
Click to expand...
Click to collapse
if youre trying to sbf you have to put it on rsd mode...power off the phone hold power and volume up till it flashes and it should say ready for rsd protocol or whatever, from there plug it in to the computer and it should recognize it.
Mine was doing the same thing,only it was a random ocurrence throughout the day for like two weeks and it only happened in the middle left of the screen,flashed back to stock still happened then it just stopped doing it,weird
Sent from my DROID X2 using XDA App
mine does this on the atrix rom but once I sbf back to GB it works fine.
Had this happen to me one time. I accidentally flash back a nandroid of a froyo backup. I was running P3's Pre-GB at the time, phone went crazy. SBF fixed everything, I was S***ing bricks when it happened though... lol
It also happened to me too. Bit it went away after I started to mess with flashing stuff to the phone like themes. It sucked, I thought I messed something up bad haha.
Sent from my DROID X2 using XDA App
Mr_GreenJeans said:
Had this happen to me one time. I accidentally flash back a nandroid of a froyo backup. I was running P3's Pre-GB at the time, phone went crazy. SBF fixed everything, I was S***ing bricks when it happened though... lol
Click to expand...
Click to collapse
BEST description for what was happening lol. Bricks are hard coming out lol
btw..
any new news on ya nandroid problem greenjeans? I mean MR greenjeans ..r u from the same area as me? Near claymont boothwyn Philadelphia etc....sorry for off subject...looking for the small world lol
I have had this happen several times when flashing. Just SBF back, wipe all data and cache and start over. It will go away! It seems it happened more when I took short cuts or flat out forgot a step, but it always went away after a clean instal. Hope that helps...
same here.... i do the sbf and a wipe (3X) and it always comes back for me
Sounds like you need an exorcism!
My wife's DInc had was also possessed. With her's it was a faulty digitizer and is a problem with many DInc.
More directly related, my DX2 does this about every day at some point. I'm running Eclipse v.6 FWIW. It seems to be a software problem as I can just turn off the screen and it goes away.
This happens to me on my DX2 with some ROMs but only when the phone is plugged in to the charger or the USB cable... Unplug it and it goes away... Really random... I have thought about taking it in but cant remember if it does it on stock unrooted or not... Might give it a try this weekend and if it does I may just get it replaced.....
It works fine after SBFing to stock GB.
lol i thought i f***ed up something bad haha
I might just keep using this GB until the eclipse .6 gets fixed up or something
Well I'm currently on .7 rc1 eclipse and its the best rom I've tried yet... And I've tried a lot lol
Sent from my DROID X2 using xda premium
DAG425 said:
This happens to me on my DX2 with some ROMs but only when the phone is plugged in to the charger or the USB cable... Unplug it and it goes away... Really random... I have thought about taking it in but cant remember if it does it on stock unrooted or not... Might give it a try this weekend and if it does I may just get it replaced.....
Click to expand...
Click to collapse
mine was still acting weird after restoring with the backup i made with stock froyo.
It's fine after deleting all the data/cache in the device and flashing stock GB.
you should just give it a try. This problem just seems so random
DAG425 said:
This happens to me on my DX2 with some ROMs but only when the phone is plugged in to the charger or the USB cable... Unplug it and it goes away... Really random... I have thought about taking it in but cant remember if it does it on stock unrooted or not... Might give it a try this weekend and if it does I may just get it replaced.....
Click to expand...
Click to collapse
I have heard that if the wrong voltage is coming through the charger it can make it go nuts like that which can be pretty bad for ur phone.
Are u using the stock x2 charger or a replacement of some kind?
Mine says output 5.1Volts (850mA)
ashclepdia said:
I have heard that if the wrong voltage is coming through the charger it can make it go nuts like that which can be pretty bad for ur phone.
Are u using the stock x2 charger or a replacement of some kind?
Mine says output 5.1Volts (850mA)
Click to expand...
Click to collapse
Im using the rocketfish wall charger for the DroidX so I would assume it should be fine... But the voltage is interesting because it happens when the phone is plugged into my pc or my lappy also..... and that is using the stock USB cable... If it were more frequent and on all ROMs including stock I would have had it replaced already... I'll check the voltage on that rocketfish wall charger with the stock moto one and see when I get off work later....
I accidentally installed the new Motorola update.
Now, its essentially soft-bricked.
I know the hard way around this, but if their's anyway I could stop a restart from happening without reinstalling my ROM, all 100+ apps, and configure my phone yet again, it'd be greatly appreciated.
rsjc741 said:
I accidentally installed the new Motorola update.
Now, its essentially soft-bricked.
I know the hard way around this, but if their's anyway I could stop a restart from happening without reinstalling my ROM, all 100+ apps, and configure my phone yet again, it'd be greatly appreciated.
Click to expand...
Click to collapse
What does the update do, my phone keeps having errors checking for an update.
Sent from my MB855 using xda premium
deedscreen said:
What does the update do, my phone keeps having errors checking for an update.
Click to expand...
Click to collapse
No idea.. the thing would shutdown my phone, send it to a pre-boot installer, similar to installing a ROM, then give me a error sign half way through.
Turn the phone back on, and repeat.
Utter BS. You'd think Motorola would take errors into consideration.
I imagine theirs some poor soul out their with a similarly virtually-bricked phone.
I imagine it's either a WebTop update or a Motorola phone connect update.
If its a webtop update, that would explain why it keeps failing. My webtop folder is on my SD card and im using Ubuntop.
I'd really love to have a functioning phone again.. any help?
rsjc741 said:
No idea.. the thing would shutdown my phone, send it to a pre-boot installer, similar to installing a ROM, then give me a error sign half way through.
Turn the phone back on, and repeat.
Utter BS. You'd think Motorola would take errors into consideration.
I imagine theirs some poor soul out their with a similarly virtually-bricked phone.
I imagine it's either a WebTop update or a Motorola phone connect update.
If its a webtop update, that would explain why it keeps failing. My webtop folder is on my SD card and im using Ubuntop.
I'd really love to have a functioning phone again.. any help?
Click to expand...
Click to collapse
Try reverting back to stock, by SBFing. Look for more information in the development threads.
This happened to me, I just wiped the cache and dalvik cache and it hasn't happened since! I am rooted and unlocked and tried to accept the stupid update. After that my phone kept trying to turn off and flash it. Isn't it not flashing cause the stock recovery isn't there?
Sent from my MB855 using XDA App
That could be, but I wish you good luck!
I have the motorola photon 4g and I've yet to find a thread that says exactly what my phone is doing.
My phone has been stopping at the motorola screen and saying RSD protocol startup, none of my buttons are stuck and I've tried to put it in flashboot and it just wont do it. I've tried holding the volume up and power button and holding the power button and volume down. I jsut don't know what else to do.
The phone is completely stock, no roots or anything. I just want a working phone because I'd rather not switch back to an lg rumor touch.
What did you try to get it into Fastboot mode?
Edit: Never mind, I see you are running a separate thread on this one...
.cruiser said:
What did you try to get it into Fastboot mode?
Edit: Never mind, I see you are running a separate thread on this one...
Click to expand...
Click to collapse
I only tried because on all the many forums I've seen on various with people with similar issues with photons and oither droids, people were telling them to do a factory reset or bring it to flashboot, I just want my phone fixed.
You left out the part about dropping it in the toilet in this thread. It worked fine before that. So my guess its water damaged. You really dont need 2 threads for the same issue.
Sent from my MB855 using xda app-developers app
Water damage or not, I'm still going to try and fix it. It obviously will turn on, I just need a way to either restart the phone or get it past that screen.
caitybmccall said:
I have the motorola photon 4g and I've yet to find a thread that says exactly what my phone is doing.
My phone has been stopping at the motorola screen and saying RSD protocol startup, none of my buttons are stuck and I've tried to put it in flashboot and it just wont do it. I've tried holding the volume up and power button and holding the power button and volume down. I jsut don't know what else to do.
The phone is completely stock, no roots or anything. I just want a working phone because I'd rather not switch back to an lg rumor touch.
Click to expand...
Click to collapse
are you unable to boot into recovery?
If you are familiar flashing motorola with rsd lite then flash it with "(198_6)-1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US" sbf file via rsd lite, it will return back to stock.
there is a thread on xda.just explore....
caitybmccall said:
Water damage or not, I'm still going to try and fix it. It obviously will turn on, I just need a way to either restart the phone or get it past that screen.
Click to expand...
Click to collapse
Water damaged or not you probably broke it by dropping it in the toilet...so..water damaged...get a replacement..
Sent from my MB853 using XDA
deepak251146 said:
are you unable to boot into recovery?
If you are familiar flashing motorola with rsd lite then flash it with "(198_6)-1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US" sbf file via rsd lite, it will return back to stock.
there is a thread on xda.just explore....
Click to expand...
Click to collapse
I've looked for it a bunch and all the things I've seen on here don't give me the correct download and send me somewhere else.
caitybmccall said:
I've looked for it a bunch and all the things I've seen on here don't give me the correct download and send me somewhere else.
Click to expand...
Click to collapse
http://lmgtfy.com/?q=(198_6)-1FF-su...-1_SUN-198_6-CM-release-keys-signed-Sprint-US
Sent from my MB853 using XDA
na7q said:
http://lmgtfy.com/?q=(198_6)-1FF-su...-1_SUN-198_6-CM-release-keys-signed-Sprint-US
Sent from my MB853 using XDA
Click to expand...
Click to collapse
I've tried that before I even found this site, none of the downloads that I've found are correct and they download something completely opposite of what I want so that was no help honestly.
My phone has insurance, I'll just get a new one.
Thanks anyways.
caitybmccall said:
I've tried that before I even found this site, none of the downloads that I've found are correct and they download something completely opposite of what I want so that was no help honestly.
My phone has insurance, I'll just get a new one.
Thanks anyways.
Click to expand...
Click to collapse
Stuck in a goddamn bootlook after SBF'ing at least 10 times. Any ideas how to fix this POS phone?
Bootloop is not reason for flashing sbf.
Wipe data!
MikeyLee said:
Stuck in a goddamn bootlook after SBF'ing at least 10 times. Any ideas how to fix this POS phone?
Click to expand...
Click to collapse
Not a "pos phone". You need to read stickies, read threads and become familiar with your phone before modifying it. If done so you would know that SBFing would not cause a bootloop , you obviously chose to RSD in the first place for a reason.
Now, for the spoonfeed:
Try to boot into recovery, if you can, wipe data and do a factory reset. If you can't access recovery, make sure you have the latest drivers and try with multiple computers.
Sent from my Motorola Electrify using Tapatalk 2
Hi there. I tripped over my Usb cable to my Droid X2 while trying to SBF it back to 2.3.4. It won't even show the Moto logo. The only thing it does is show a green light when the cable is plugged in. ANY help is greatly appreciated because I can't afford to replace this thing even though it's not very pricy. PLEASE HELP!!!!!!!!!!!!!!!!!!!!
Did you figure this out? I've been in the same boat a few times. Between trying to boot into recovery and the auto updater and multiple battery pulls I eventually got into recovery and was able to sbf back to stock. Never figured out what the trigger was, just lots of booting this way and that way until things started happening.
Sent from my DROID X2 using Tapatalk 2