Hello All,
I have a Motorola Atrix 4G running Dark Side rom. It has been working great for me and loving my phone. This morning it gave me a Wi-Fi error and after a few minutes rebooted. So first I did a complete reflash of the rom but nothing changed. Then I downloaded the Nottach rom and followed all instructions. Once phone booted up everything looked fine until i clicked on Wi Fi... it gave me a error I clicked it again and phone rebooted.
Does anyone have any ideas. Please keep in mind i am kind of a newbie to this so if you can keep it simple when explaining I would greatly appreciate it.
And most of all I want to THANK anyone who takes the time to help me.
THANK YOU
Does bt make it reboot as well? If so, hate to say it, but sounds like your wifi/bt chip died. All around the forums are people with this problem and lots of them say our atrix is known for this to happen. Hopefully that's not the case for you and someone will come along with more help.
If BT is blue tooth, i just clicked on it and it never turns on, but does not make the phone reboot. So the phone is trash i take it?
Okie_Bama said:
If BT is blue tooth, i just clicked on it and it never turns on, but does not make the phone reboot. So the phone is trash i take it?
Click to expand...
Click to collapse
If it doesn't turn on, that's bad news. Time to see about a warranty replacement and hope its not one that motorola has blocked the unlocking of the bootloader. Bad luck man.
Related
I have a very unusual problem that i just googled and have not come across. I woke up this morning and found that my display wasn't turning on, as if the phone was off. I had encountered this problem before and a battery pull worked fine. Im on MR2 btw... but this issue is different, my diplay is completely dead, D-E-D, dead... after the battery pull i held the power button to start up again but all i got was the vibration on start up, no lcd screen response.
i know the issue is the lcd screen and i can replace it myself, if it had just been that. i have the total protection plan set up and can replace it, but my only issue is that the TB is rooted. upon fixing it they will realize it once the CM7 animation comes up. i need advice on how to handle this situation.
i cant bootload neither, display is completely off... i can hear sound going on so i know its on. Help please!
i had CM7 rc1.2, mr2 radio, clocked up to 1.6.. i was on bamf for a while but switched to cm7 2 days ago.
You cant boot into recovery mode? Try booting into hboot see if the screen works. If it doesnt just take it to VZW and when they fix it be like "What the heck! You guys rooted my phone?!"
alluzzion2o9 said:
I have a very unusual problem that i just googled and have not come across. I woke up this morning and found that my display wasn't turning on, as if the phone was off. I had encountered this problem before and a battery pull worked fine. Im on MR2 btw... but this issue is different, my diplay is completely dead, D-E-D, dead... after the battery pull i held the power button to start up again but all i got was the vibration on start up, no lcd screen response.
i know the issue is the lcd screen and i can replace it myself, if it had just been that. i have the total protection plan set up and can replace it, but my only issue is that the TB is rooted. upon fixing it they will realize it once the CM7 animation comes up. i need advice on how to handle this situation.
i cant bootload neither, display is completely off... i can hear sound going on so i know its on. Help please!
i had CM7 rc1.2, mr2 radio, clocked up to 1.6.. i was on bamf for a while but switched to cm7 2 days ago.
Click to expand...
Click to collapse
Have you tried running a RUU (ROM update utility) to return your phone to stock? Download one of the .exe RUU's (not the zip) to your computer from this page http://dougpiston.com/ThunderBolt/RUU/ and run it from your computer with your phone plugged in and turned on. With any luck it will return your phone to stock.
i cannot multi quote for $hit, anyways no i cannot get into bootloader because my display wouldn't boot up... but out of sheer luck i finally got it to work!!! and heres what i found! the screen has water damage! then i remembered this morning before getting my phone i tipped over a cup of tea my son left there. im lucky the phone even boots up! i guess facing the phone downwards saved my phone but not the screen... ill hit up VWM and see what they have to say.
nucher said:
Have you tried running a RUU (ROM update utility) to return your phone to stock? Download one of the .exe RUU's (not the zip) to your computer from this page http://dougpiston.com/ThunderBolt/RUU/ and run it from your computer with your phone plugged in and turned on. With any luck it will return your phone to stock.
Click to expand...
Click to collapse
does it matter which one i pick? of the RUU i mean?
[edit]
nevermind i got it, the process seems similar to updating touchpro2, half way through updating.. thanks man! although i got my phone working im going to be bothered with the watered down screen. i can simply open it up and clean it but that'll waste my total protection plan i have with VWM =P
alluzzion2o9 said:
i cannot multi quote for $hit, anyways no i cannot get into bootloader because my display wouldn't boot up... but out of sheer luck i finally got it to work!!! and heres what i found! the screen has water damage! then i remembered this morning before getting my phone i tipped over a cup of tea my son left there. im lucky the phone even boots up! i guess facing the phone downwards saved my phone but not the screen... ill hit up VWM and see what they have to say.
does it matter which one i pick? of the RUU i mean?
[edit]
nevermind i got it, the process seems similar to updating touchpro2, half way through updating.. thanks man! although i got my phone working im going to be bothered with the watered down screen. i can simply open it up and clean it but that'll waste my total protection plan i have with VWM =P
Click to expand...
Click to collapse
Glad you were able to get the RUU to work. I didn't specify one RUU because I figured you would use any one of them just to get your phone to stock, then you can take it to Verizon or mail it to asurion for replacement.
nucher said:
Glad you were able to get the RUU to work. I didn't specify one RUU because I figured you would use any one of them just to get your phone to stock, then you can take it to Verizon or mail it to asurion for replacement.
Click to expand...
Click to collapse
ye i already set up the order... cost $99 in deductables or some $hit... hopefuly it will be here tues/wednes.. thanks a whole lot for the help
alluzzion2o9 said:
ye i already set up the order... cost $99 in deductables or some $hit... hopefuly it will be here tues/wednes.. thanks a whole lot for the help
Click to expand...
Click to collapse
You're welcome. When you get the new phone don't hesitate to put CM 7 back on after you're rooted. I feel its they most flexible and up to date ROM you can put on an Android phone.
nucher said:
You're welcome. When you get the new phone don't hesitate to put CM 7 back on after you're rooted. I feel its they most flexible and up to date ROM you can put on an Android phone.
Click to expand...
Click to collapse
will come in tomorrow, i have 15 days to mail my damaged one or its 300 ;P. CM has always been my fav. its super fast. my favorite part is how fast booting up can be, unlike bamf sense 3.0. only problem i had with cm7 was that when it rings it rings once.. and when i get a voicemail notification it goes ape $hit.
other than that its still my fav.
alluzzion2o9 said:
will come in tomorrow, i have 15 days to mail my damaged one or its 300 ;P. CM has always been my fav. its super fast. my favorite part is how fast booting up can be, unlike bamf sense 3.0. only problem i had with cm7 was that when it rings it rings once.. and when i get a voicemail notification it goes ape $hit.
other than that its still my fav.
Click to expand...
Click to collapse
I had the same problem with the phone only ringing once, I changed the ringtone from Digital Phone to Bell Phone and that solved my problem. I read that certain ringtones don't work properly with CM7 and there is fix in the next update.
I have searched and searched, but can not find what seems to be an applicable fix, so here goes.
Ok here is my best description. Equipment: Rooted vibrant. The plot: Rooted. Ran fine for months. Yesterday purchased Rom Manager premium. Installed one of the premium roms. Can't remember the name of the rom. After install everything worked fine except I kept getting the error, "com.google.process.gapps has stopped unexpectedly" so I tried everything I could find related to that problem to fix it, but nothing worked. As a symptom the market, gmail, etc wouldn't work. Anyway I figured I'd just recover the last rom that I backed up and start over. So I did, but now the phone boots, goes to the "draw pattern to unlock screen" and won't recognize the fact that I'm actually drawing the pattern to unlock the screen. The "buttons" on the bottom of the screen recognize my touch (menu, home, search, back) as they darken when touching them.
So there the phone sits on the unlock screen. After a minute or two the screen goes blank, the phone vibrates once, and the unlock screen comes back and won't accept any input.
Is this fix applicable, or would it work in bringing my phone back to me?
http://forum.xda-developers.com/showthread.php?t=848737
I want to make sure as I don't want to further exacerbate the uselessness of my phone. I feel like I've lost a limb with it gone.
Thanks for any help.
Sorry to hear you found the worst gremlin of all. I'll get that from time to time when my phone feels like being stupid. Lucky for me, I can just reboot the phone, and she's back to normal.
As far your situation is concerned, I would probably try to use Odin and flash your phone back to stock so you can build it back up to whatever ROM you're on. This usually happens when you bounce back and forth between a froyo and GB ROM; or a ROM from a different dev that's used a different framework to make all his stuff work.
Jump into the link in my sig, and see if you can find the files you need. Otherwise, shoot me a message so I can link you to the files I use to go back to stock pre-rooted.
Lol, did you try this?
http://forum.xda-developers.com/showthread.php?t=749605
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
younix258 said:
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
OK. The sticky worked. I admit I panicked, but IT WORKS NOW!! I'm just ecstatic! You guys rule.
I guess I was just gun shy. I bricked the snot out of my my-touch a year ago (still doesn't work).
Anyway, on to hacking.
Thanks again!
Awesome! Glad you got it werkin
Next time just try a simple Google search of the error itself.
*EDIT*
If you still have the mytouch I'd be interested in it. PM me if so
Yeah I tried to google the problem, but I was still stuck. None of the fixes seemed to work. Until google led me here.
I do still have the my touch. Mint condition, minus the fact it doesn't work! I'd like to get it working again if possible. Is there a way to odin the my touch? I tried and tried last year when I bricked it, but I never got it to work again. Is there a my touch forum here somewhere named something other than "my touch"?
Sent from my SGH-T959 using XDA App
Hey guys, so I just updated my att galaxy s2 via kies to android ICS however after that I've ran into some problems.
After updating however I encountered a period where the screen went black and the phone kinda just died on me. After restarting I began to encounter some problems. For some reason, whenever the phone goes to sleep and and then wakes up, my screen gets flipped upside down and the screen gets really bright. Despite that, I still have to press the screen like usual. Which means that if the call button is at the top after flipping, I still have to press the bottom of my screen. Also the screen isn't perfectly flipped and there is space above the top bar.
However, the phone does work fine on bootup, and only fails after it sleeps. Also, very recently my phone just went through a screen repair after the screen cracked under the glass, but otherwise that I have no clue what's going on.
Is this just a poor repair and a hardware problem or is their another problem here?
Also I've tried a factory reset and that didn't help.
Thanks for any help you can give.
(Hopefully I got the right board)
Kovath said:
(Hopefully I got the right board)
Click to expand...
Click to collapse
considering this board is all about CUSTOMIZING devices... I dunno about that. Maybe try the AT&T site?
Maybe one of our divas will be kind enough to help anyway.
Yes, I mean divas, also referred to around here as devs. I <3 u all!
Clay
Sent from my SGH-I777 using XDA
Yeah I kinda got that gist =P
but, after searching through the web, there weren't really a lot of sites that I came across detailing about my problem, but this was one of the sites that came up a lot so I was just hoping if anybody, just anybody could help me out with this.
Kovath said:
Hey guys, so I just updated my att galaxy s2 via kies to android ICS however after that I've ran into some problems.
After updating however I encountered a period where the screen went black and the phone kinda just died on me. After restarting I began to encounter some problems. For some reason, whenever the phone goes to sleep and and then wakes up, my screen gets flipped upside down and the screen gets really bright. Despite that, I still have to press the screen like usual. Which means that if the call button is at the top after flipping, I still have to press the bottom of my screen. Also the screen isn't perfectly flipped and there is space above the top bar.
However, the phone does work fine on bootup, and only fails after it sleeps. Also, very recently my phone just went through a screen repair after the screen cracked under the glass, but otherwise that I have no clue what's going on.
Is this just a poor repair and a hardware problem or is their another problem here?
Also I've tried a factory reset and that didn't help.
Thanks for any help you can give.
(Hopefully I got the right board)
Click to expand...
Click to collapse
There are alot of things that could go wrong when flashing ROMs.
All of the custom ROMs here have built in safeguards which allow users to recover from issues involved with flashing. The same cannot be said about stock builds.
Unfortunately, your options are limited if you're going to stay stock. You can either try a factory reset and re-installing the update via KIES or you can call AT&T. That's pretty much it.
Personally, i'd Mobile Odin a rooted package with CWM and start flashing some of the wonderful work the developers have graciously allowed us to partake.
BROKKANIC said:
Personally, i'd Mobile Odin a rooted package with CWM and start flashing some of the wonderful work the developers have graciously allowed us to partake.
Click to expand...
Click to collapse
OP, I agree with the sentiment here, but you can't use mobile odin until your are already rooted. One option you could follow the guide linked in my signature to root the phone and go from there.
My personal suggest is that if you're running stock ROM, updating an official stock ROM and having problem, I call the provider for help.
My download and install went fine but I incounterd some unusual problems afterwards. My phone doesn't always keep a data signal while browsing the internet and a phone reboot makes it return. Setting browsers home to Google instead of default AT&T doesn't stick. I also had few dropped calls and very low signal bars in status bar at my house which gingerbread gave me full ones.
same here
Kovath said:
Hey guys, so I just updated my att galaxy s2 via kies to android ICS however after that I've ran into some problems.
After updating however I encountered a period where the screen went black and the phone kinda just died on me. After restarting I began to encounter some problems. For some reason, whenever the phone goes to sleep and and then wakes up, my screen gets flipped upside down and the screen gets really bright. Despite that, I still have to press the screen like usual. Which means that if the call button is at the top after flipping, I still have to press the bottom of my screen. Also the screen isn't perfectly flipped and there is space above the top bar.
However, the phone does work fine on bootup, and only fails after it sleeps. Also, very recently my phone just went through a screen repair after the screen cracked under the glass, but otherwise that I have no clue what's going on.
Is this just a poor repair and a hardware problem or is their another problem here?
Also I've tried a factory reset and that didn't help.
Thanks for any help you can give.
(Hopefully I got the right board)
Click to expand...
Click to collapse
I just got my screen replaced and have the exact same problem, factory reset did not help either.
Did you managed to fix it?
Any help would be greatly appreciated
So I recently got my old bricked evolte replaced by Sprint. The one I was given worked fine the entire time the device was powered on. However, once turned off and back on, its screen would not work. It stayed like this for hours, until I finally started playing with it and realized it would come back on after playing with it for a little bit. I also found out that with this error the home screen pops up for a second when powering on your device, and that's exactly what I had. I read up on the error and found out it was a software error, and to reset to factory settings. So, this fixed it, I thought.
So now, after it is apparently fixed, it still does this to some extent. It will do this if the phone has been powered on for a while, and the screen won't stay off for more than like 2 or 3 minutes. Also the home screen doesn't pop up any more like it used to with the other error.
So what should I do? I was thinking of going to Sprint, but my problem is hardly reproducible. It only happens when it's been powered on for a long time, and won't do it twice in a quick succession. I feel that even if I could show them the problem, they might think they've fixed it when they haven't because it won't do it twice. I would like to root my device, but I'm afraid they're going to say that I'm the cause of the problem if I do that. If it's just a software problem though, maybe flashing a custom rom would fix the problem.
What do you guys think? What do you think is the best course of action? Any advice would be greatly appreciated. Thank you.
Never mind, I didn't know Sprint would order you a new phone if it was a minor problem like that. I thought they would only repair yours. So feel free to close this thread.
Hi everyone. Thank you for reading.
I am posting for help with a friend's phone. I, personally, have an S3 on Sprint and haven't had much experience with T-Mobile phones. He has rooted his S5 (T-Mobile, obviously) using galaxys5root.com (I'm now not fond of that site due to his bad experiences that consistently happen) and has not put a new ROM on yet. It has been successfully rooted for several weeks, but today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on. He's getting a replacement anyway, but we want to unroot it before sending in the defective device. I'm wondering (and to my knowledge it seems like) if it's a boot loop. Nothing shows up on the screen at all, not even the back light is coming on. I have yet to connect it to Odin to see if anything comes up. I'm just seeing if this has happened to anyone else and if they have figured out a way to resolve it. My suspicion is that there's a problem with either the boot sector or the recovery sector, as it does not go into recovery.
Any insight would be much appreciated. Thanks again!
caderyn19 said:
today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on.
Click to expand...
Click to collapse
It sounds like the LCD display has gone bad if the vibration and blue light function normally but you cannot see anything ever.
When they get the new device you might want to suggest that they follow the rooting instruction in this forum on XDA instead of going to a website to do it. Just my opinion.
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
caderyn19 said:
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
Click to expand...
Click to collapse
Normally, even in a boot loop you see the initial Galaxy splash screen when it first starts booting. Then you see it over and over again. If you see nothing, it normally means the LCD is bad and unfortunately it's the most expensive part of the phone.
Good Luck with it.
If I've been helpful, please hit the thanks button.
That's what I figured... Thanks for your help! (I hit the button )
caderyn19 said:
That's what I figured... Thanks for your help! (I hit the button )
Click to expand...
Click to collapse
Wouldn't surprise me if the device is rebooting itself trying to fix a hardware fault. Might be detecting the LCD has stopped forcing itself to reboot.
But yeah, stick to XDA from now on We are good people here Welcome to the family!
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
caderyn19 said:
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
Click to expand...
Click to collapse
Well get your friend over here too!
Sent from my SM-G900T using Tapatalk