[Q] Dead phone? - Atrix 4G General

Dropped phone in toilet, got it out in seconds and removed battery and sim card. Then i dried it off and took it apart. Cleaned everything. Cut open a bunch of those pouches that absorb water in my vitamins and stuck it in a baggie with all the parts for about a day. Then i put the battery back in and started it up and it seemed to be fine until i got to the home screen. Where the connection bars are it has a red circle with a line through it. Then after being on for 15 seconds or so it just restarts and did this over and over. Eventually i figured out that if i put it in airplane mode it stays on and functions fine, even connecting to wifi and getting on the net works fine. Only when i took it out of airplane mode and it tried to connect to at&t did it do this. So i got to thinking it might be this app i have called phone locator pro thinking i stole the phone or something. Eventually i got this uninstalled and now my phone takes probably half the time it usually does to start up but now when i get to the home screen a couple force close messages appear "The process com.motorola.service.main has stopped unexpectedly, please try again" and then it restarts. Ive searched for a solution to this but everyone just says to do a reset.
I would have done a factory reset right when everything started if i could but when i try to go into android recovery it gives me "Failed to boot 2" and i have to pull out the battery to get it to turn off.
Would appreciate any help i could get as i am stumped.

1lb rice and a tuperware dish
place phone battery out sim out sdcard out,inthe middle of the rice for 48 hours
then pull phone out sturr rice place back in for 24 more hours then check phone make sure its dry if so reinstall batt sim and sdcard or to be safe go a nother 24 hours in rice ive seen this method work!
b........ut you already turned on the phone so...
the condencation inside may have borked somthing but its worth.a shot:banghead:

Use rice.
Sent from my MB860 using XDA App

Looks like the damage has been done. If you get no signal it seems that you at the very least fried something involving the radio chip. Imo you are screwed. But i would try to reflash recovery just to see.
Sent from my MB860 using XDA App

i was able to flash the recovery and do a factory reset. The force close messages dont pop up anymore. But it still doesnt connect to the at&t network and when it tries it shuts off. im unable to make it through the motoblur setup screen before it shuts off. Is there a way to start it up in airplane mode because i cant make it through the setup to turn it on. This way i could at least use my phone to play music, games, get on wifi, etc.
Thanks for everyones help.

atravisty said:
i was able to flash the recovery and do a factory reset. The force close messages dont pop up anymore. But it still doesnt connect to the at&t network and when it tries it shuts off. im unable to make it through the motoblur setup screen before it shuts off. Is there a way to start it up in airplane mode because i cant make it through the setup to turn it on. This way i could at least use my phone to play music, games, get on wifi, etc.
Thanks for everyones help.
Click to expand...
Click to collapse
If you're able to use wifi without it shutting down, then just connect to wifi before trying to setup blur. Menu key, then setup or connect to wifi.
Sent from my MB860 using XDA App

Related

G1 Doesnt Always Wake Up

Does anyone elses G1 not wake up when Menu is pressed? Sometimes I have to press it like 6 times before the phone wakes up, does anyone know why?
Mine does this as well. I just thought it was learning from it's owner (I take more than 5-6 pokes to wake me up too).
My only guess is that something is running in the background in order to slow it down and the number of presses has little to do with it.
momentarylapseofreason said:
Mine does this as well. I just thought it was learning from it's owner (I take more than 5-6 pokes to wake me up too).
My only guess is that something is running in the background in order to slow it down and the number of presses has little to do with it.
Click to expand...
Click to collapse
Yea, i was thinkin the same, i should try runnin a ton of apps and find out if [email protected] the problem
mine does the same things sometimes. gets annoying at times. usually i just open and close the keyboard
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
brooklynite said:
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
Click to expand...
Click to collapse
Shop Savvy?
I also started having the wake up problem and quicker then normal battery drain. I have an ADP1 phone which I updated to 1.1 a few days before noticing issue
I think that the theory of something sucking clock cycles is a good one. I noticed my CPU Usage (when nothing was running other then System Monitor) went from 0-40% to 20-70%.
I couldn't be bothered with the finer points of troubleshooting, so I took the thermo-nuclear approach and did a factory wipe.
Just before the mystery CPU cycle and wake up issue, I hadn't installed any new apps, BUT I did update a bunch of existing apps. After the factory wipe, I left off installing the following list:
Watts
StreamFurious
DroidFTP
Telnet
e-VoiceRecorder
VoiceRecorder
Constitution
Barcode Scanner
Astro
RingDroid
SlovoEd Classic English Dictionary
Things are fine now.
both of my g1's do this, and have done this out of the box, anyone turn off there screen with the keyboard out, and then close the screen and the screen comes back on with the lock screen up and then having to turn the screen back off? annoying
try the swapper app?
or turn phone off and back on, it might becuase you are usingahome or openhome or dxtop or sweeterhome, these app may slow down the interface a bit, try downloading droid sans tweak lite and fool around with that..
goodluck i also get this sometimes
brooklynite said:
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
Click to expand...
Click to collapse
I'm having same issue as the OP and issued #1, 3 and 4 from the above post.
Hmm, im not experiencing any of the above posted issues, it may be a particular app that u have installed. I only have the wakeup issue sometimes, most likely when the phone is running slow from the browser or another memory draining app, but no app in particular.
Hmm, when mine fails to wake up, I never waited long enough for it to come back, just reseated the battery for a reboot.
Of the other problems, I have the "screen-black-for-a-few-before-caller-picture-shows-up" issue.
JayBachatero said:
I'm having same issue as the OP and issued #1, 3 and 4 from the above post.
Click to expand...
Click to collapse
what firmware do you have?
btw, dont count on Locale to turn off your stuff all the time, its not very accurate imo, at times its great, but thanks to the crappy g1 battery, they have a choice, constantly check time/location/.ect and drain the battery in a hour flat, or periodically check it and reduce battery drain, do you have any wifi programs that keep wifi on when phone sleeps (such as wifi lock and so on)? if so use the program on the market that writes up a log of its actions and see if its acting up
as for #1 (sorry im unorganized) my phone does that too, i believe its because i have 2 programs that run when the phone rings, let alone im sure locale is checking to see who is coming since thats a condition, which would make 3, and then i have a mp3 that plays when the phone rings, and i have a class 4 sd card (i know, i know), the way that programs work is that it has to go line by line of the code, if it is slowed down, or it has to execute other items before continuing that are slow to execute, than everything has a delay, but yeah from time to time i have this issue, phoneplus was a program that made me miss a few calls (1/4th of the time)
i think 3 and 4 are directly related, could be wrong
I was having the same problem right after I installed the app "Contact Owner"
No amount of reboots fixed the problem. Uninstalled and everything was back to normal.
@wootroot - I have stock RC30. Haven't rooted yet.
JayBachatero said:
@wootroot - I have stock RC30. Haven't rooted yet.
Click to expand...
Click to collapse
consider upgrading to the rc33 ota update yet? i had better battery life (and my battery didnt get as hot) when i used rc33
also, if youve had your phone since it first came out (rc19 i believe) and your battery used to get very hot, you might of damaged some of the cells (especially of the battery has expanded), if this is the case simply call tmobile and tell them that your noticing even after wiping the phone that your battery life is lasting shorter and shorted, even with out any programs installed from the market, i even went as far as to say that i made sure wifi was off, only 2g was on, gps was off, screen was dimmed, timeout set at 30 secs, and im still only getting a hour of life (none of which is true but it got through all the "well how about trying this and calling back if you still have a problem" bs, with the ota rc33 and the new battery, i noticed a pretty good difference
I have a modified version of this "doesnt always wake up". The phone is less than 24 hours old, it was a refurb they sent me for the last one that went dead. I used it with the rc33 it came with and found the problem, then figured it was hosed so i rooted and installed 3 of the versions of cupcake (The Dude, JF, and Haykuro) to see if they all had the issue- they do. Here is a video, hope you can see the attempted keypresses. There will be lines that appear, like the screen is broke..then, they will go away. Sometimes it takes 5 minutes to get the phone to turn on, however if I leave it on (never goes to sleep) it works flawlessly.
http://www.youtube.com/watch?v=ecQo2Ly2WUM
I get this all the time also...
Uninstalling dxTop doesn't change anything for me...it still acts the same...
I also get the problem that when someone calls me the screen stays blank for about 5 seconds and I can't tell who calling...
wake up issue
I am experiencing the same problem, with a brand new warranty replaced G1, what happens is when the phone goes to sleep it completely locks up, when I try to wake it up via menu, it does not wake. Plugging the phone in and trying ddms or adb does not work, ddms shows the phone as offline, also the device seems to get really hot when this happens, sometimes Call + Menu + Power resets it, and sometimes I have to pull the battery.
I think this may have to do with wifi turned on. Because when the screen goes off your phone switches wifi off and goes to 3G as default setting.
I think we should try leaving wifi on all the time and see if that solves the issue, im about to try that now.
It seems this is a known issue over at tmo forums
A couple questions:
When this happens to you guys is wifi enabled and connected when the phone is shut off?
What Rom, SPL, and Radio is installed?
I noticed this didnt happen to me until I enabled wifi, maybe I didnt wait long enough because its completely random, please send back your results
defcon

Fried USB?

I guess **** happened...
At morning taking phone from the dock, I noticed some apps FC. And it continued sporadically along day, so at one point I simply decided to reboot. Phone turned of fine... However I was unable to turn it on immediately after. It was showing black battery. Whatever I did no dice. I even tried my wifes phone battery.
That happened on the road, so at one point I decided to plug it in. Oh miracle - phone booted with power!!! But then my troubles worsened, because I've noticed that it always shows USB connected, starts desk home in night mode, shows battary constantly charging. Stuff like this. I've tried factory reset, reflash to stock DJ05. Nothing helped. Now it getting worse, because screen started to blink when on power...
Does it sounds familiar to somebody? Need to replace?
After trying everything I can imagine, it is kind of obvious that I have HW failure. My problem is that in order to return it back to Verizon I need to have DI01. I did backup from recovery before flashing DJ05.
All this is fine, however I'm not sure if this backup will restore radio. I guess not. If not, how I can flash one? I'm having problems to get in download mode and I think ODIN is unable to detect port. Do we have radio zip i can flash with recovery?
My first fascinate had the same problem, had to return it.
Sent from my SCH-I500 using XDA App
It seems like USB is still alive, at least partially. After countless attempts I managed to connect it computer in download mode and flashed DI01. At first it looked like it fixed the problem... However now USB indicator changes on and off constantly. If you turn it off it reappears in a few seconds. Only upside is that comp sees it and I now have unrooted DI01.
Sad. My phone was in mint condition after over 3 months of usage. Who knows what kind of refarb I'll get.

Where did everything go? (Factory Reset Itself)

The oddest thing happened.
Went to bed around 12 last night and left the tablet on charge for 14 hours and when I went to use the tablet at 2pm everything was gone! Pictures Apps everything.
It's like it factory reseted itself...
I rebooted the tablet and everything was back to normal
Get this,
uptime before reboot was 42hr 40min
Tablet is the 817 sticker is on top
My 817 Verizon restarts and shuts down whenever it feels like it. Safe mode makes no difference. Longest it lasted in safe mode was 2 hours. It will do a restart and not show it in uptime stats sometimes. Sometimes it will go to the red Verizon start screen and just turn back on, not really a restart. Done numerous factory resets, removed sd card, and even used Verizons repair tool to reinstall stock system. Hate sending it back. Even though I reported the problem within days of getting it, Verizon had me doing things with it trying to fix it which took days and getting sent higher up the technical help team till they said I needed to return it but i'd only get a refurbished on because I had it too long.
You accidentally put your tablet in guest mode. Look at the top right icon in your notifications pull down.
ajonrichards said:
You accidentally put your tablet in guest mode. Look at the top right icon in your notifications pull down.
Click to expand...
Click to collapse
Good pick up!!
Sent from my D6603 using XDA-Developers mobile app
Oop- thanks that helped lol

Phone won't stop vibrating...

Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
I have had this issue on both at&t and t-mobile firmwares, but only while rooted.
Best thing to do is to re-flash the stock firmware again(or go to a different firmware if you'd like) but this is the reason I'm currently avoiding root. It soft bricks about a month in and is an easy fix but its annoying.
Was wondering about that too (flashing the stock firmware). But, will it wipe everything I had on there? Will any of my txt msg's and photo's or summat be lost to the ether?
Stupid question, I know, but had to be asked.
Thinking about flashing stock firmware and rooting agin for the sake of being able to do it again lol.
Well, if you flash stock, it does factory reset. That's why I have backups lol all I have to do is log into my Google account and everything is there.
buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
Did you have security log or security update disabled as that updates and causes weird after affects.
buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
These two threads describe exactly your issue and solution - http://forum.xda-developers.com/verizon-s7-edge/help/g930t-updates-unroots-overnight-t3426636 and http://forum.xda-developers.com/tmobile-s7-edge/help/rooted-weeks-rebooted-stuck-t-mobile-t3425814
I had the same problem, twice I had a rooted device totally lock up and had to re-do everything. But after disabling the security updates as advised, I'm currently going on two months without a problem.
Hope this helps!

Nexus 4 went nuts

Hi,
My Nexus 4 has been acting up for some time. I had the infamous "optimizing apps" issue almost one year ago. Since then I used an app ("optimizer app fix" or something) to get around it. It's rooted, but I can't remember the details/versions.
More recently, the phone started to lose the network connection. I tried to change the setting from automatic to my home network, it did seem to help a bit, but didn't really fix the issue.
Yesterday I was using the flashlight, and just before I turned it off, the phone rebooted itself. From then on it became very unstable. If I leave it alone in flight mode, it will stay on. If I start doing anything, at some point it will shut down. If I keep it plugged to the charger, it stays on, though. So it looked like the battery is gone. I'm just not 100% sure because if I boot it into recovery mode it stays there apparently with no issues, for a long time. It could be that the current draw is not so big in that mode, though.
I have just finished backing up whatever I could, and wiped the data/dalvik/cache partitions from the TWRP recovery menu. Still not good. Did a Format Data from there too. No luck.
Given the cost and hassle and wait and the number of fake batteries in the market, I don't want to buy a new battery to revive this phone (knowing that it's likely to fail again sooner than I can expect). Is there anything else you'd suggest that I try before I go shop for a new phone? :crying:
Thanks,
VMat
vmat005 said:
Hi,
My Nexus 4 has been acting up for some time. I had the infamous "optimizing apps" issue almost one year ago. Since then I used an app ("optimizer app fix" or something) to get around it. It's rooted, but I can't remember the details/versions.
More recently, the phone started to lose the network connection. I tried to change the setting from automatic to my home network, it did seem to help a bit, but didn't really fix the issue.
Yesterday I was using the flashlight, and just before I turned it off, the phone rebooted itself. From then on it became very unstable. If I leave it alone in flight mode, it will stay on. If I start doing anything, at some point it will shut down. If I keep it plugged to the charger, it stays on, though. So it looked like the battery is gone. I'm just not 100% sure because if I boot it into recovery mode it stays there apparently with no issues, for a long time. It could be that the current draw is not so big in that mode, though.
I have just finished backing up whatever I could, and wiped the data/dalvik/cache partitions from the TWRP recovery menu. Still not good. Did a Format Data from there too. No luck.
Given the cost and hassle and wait and the number of fake batteries in the market, I don't want to buy a new battery to revive this phone (knowing that it's likely to fail again sooner than I can expect). Is there anything else you'd suggest that I try before I go shop for a new phone? :crying:
Thanks,
VMat
Click to expand...
Click to collapse
No. You need to replace the battery.
Sent from my Nexus 6 using Tapatalk
trent999 said:
No. You need to replace the battery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's what I thought. What a bummer.
Thanks for the reply. Happy new year, everyone!
VMat

Categories

Resources