Related
My phone keeps locking up and freezing and then rebooting. Or sometimes it wont reboot and then I have to pull the battery out. Basically what happens is I'll be surfing facebook or even using google maps and what will happen is the phone will freeze/lock up and you'll see a line of distorted pixels and the phone becomes unresponsive after that. You can't push any buttons it wont respond to anything. It either then stays on that screen and then reboots itself after a moment or it just will stay lit up on the screen you were on or it will just go black and become unresponsive. You can plug it in it wont charge it wont turn on or anything. The only way to get it back on is pull the battery and start it up again.
Weird mentions: If I try to start it up right after it's had the lock/freeze it will do it again almost immediately. It will load and right as it gets to the home screen it locks up again. I usually have to wait a little bit and then I can start it and then I can use my phone. But if I try to do to much on it, like running google maps while using navigation (Like keeping the screen on all the time) the phone is gunna lock up and freeze. But if I push the power button while it's running that app it wont lock up and freeze.
Thoughts: I dunno if it has to do with the processor and if it works too much it locks up and freezes and causes the phone to crash or if it's a heat issue.
I have an HTC Amaze 4g Phone rooted, S-OFF running EnergyROM ICS 4.0.3
I have formatted it several times, re-installed the ROM and still getting the same freezes/lock ups. Any suggestions would be awesome! Also if I can help clarify anything or provide more information for you lemme know! Thanks so much for taking the time to read all this mess and help me out!
Sounds like you did almost everything to eliminate the possibility of a software problem. If you're still under warranty, I'd say get a new one =)
Have you tried to format the SD card? I've had the same issue and that's how I solved it.
Another option is to get a new battery
Enviado desde mi HTC Amaze 4G
Gurpe said:
Have you tried to format the SD card? I've had the same issue and that's how I solved it.
Another option is to get a new battery
Enviado desde mi HTC Amaze 4G
Click to expand...
Click to collapse
That's what I was thinking because when it does lock up and freeze like that the battery will lose 20% to 30% of power from that one freeze. I could be at 100% battery power and then that the phone glitches like that then I lose that much battery power? Yeah I'm gunna try and get a new one.
have you tried any other roms? have you upgraded your kernel?
Try to go in steps and stop where it fixes the problem. It happened to my sensation when I really tried to mess up with system files. For me it got fixed on step 2
0.5) Make backup of storages on computer and take out external memory card
1-) Flash the stock ruu (use search in development thread) reboot
2-) format internal storage
3-) it might be hardware issue, depending on your warranty, you might get it fixed by HTC/t-mobile.
Try the methods 0-2 at-least
Sent from my HTC_Amaze_4G using xda premium
ahmedreaz17 said:
Try to go in steps and stop where it fixes the problem. It happened to my sensation when I really tried to mess up with system files. For me it got fixed on step 2
0.5) Make backup of storages on computer and take out external memory card
1-) Flash the stock ruu (use search in development thread) reboot
2-) format internal storage
3-) it might be hardware issue, depending on your warranty, you might get it fixed by HTC/t-mobile.
Try the methods 0-2 at-least
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I think it's the hardware. Because when I'm in recovery it freezes even in there. I even put in the new battery I bought and I'm still getting those random lock ups. I even took out the SD card for safe measure to make sure it wasn't that.
I would back everything up, do a complete wipe, flash a stock RUU and then see if it happens. Or take the easy way out and call your carrier for a replacement. If you have T-Mobile, they're pretty awesome and quick about replacements.
Call T-Mobile for a replacement..
Its a memory parity error on either the GPU or CPU... yes it is heat related, hence an almost instant lock up on warm reboot.
Sent from my Jelly Bean infused SGH-I997 Infuse!
I just had to do a warranty return on a completely stock unit to T-Mobile for this very issue. Identical symptoms to OP. Phone seemed to behave normally if little was done to it, but streaming any sort of data could get it to hard lock pretty quick. I was assuming it was a bad memory chip somewhere.
I had a similar issue. Different battery. No problems now.
First, my phone is rooted running 4ext recovery and the latest energy rom. It is also sim unlocked from a pin given by tmo.
For the past couple weeks, the phone would randomly shut off and power would drop 30%. After a week of that, my phone won't charge anymore. So obviously I think that I have a dead battery. I replace the battery with a new one and although it is much better, sometimes it still will not charge.
Another issue I have is, I constantly get the message "unlocking PUK" but I am already sim unlocked. This would turn my phone screen on and off every 5 mins or so changing back and forth from locked PUK to unlocked PUK. If I'm doing something on my phone, it would go into the "unlocking PUK" and I have to go back into the app evey few seconds.
I am not sure how to resolve this issue. Any insight would greatly be appreciated.
maRrRrRffin said:
First, my phone is rooted running 4ext recovery and the latest energy rom. It is also sim unlocked from a pin given by tmo.
For the past couple weeks, the phone would randomly shut off and power would drop 30%. After a week of that, my phone won't charge anymore. So obviously I think that I have a dead battery. I replace the battery with a new one and although it is much better, sometimes it still will not charge.
Another issue I have is, I constantly get the message "unlocking PUK" but I am already sim unlocked. This would turn my phone screen on and off every 5 mins or so changing back and forth from locked PUK to unlocked PUK. If I'm doing something on my phone, it would go into the "unlocking PUK" and I have to go back into the app evey few seconds.
I am not sure how to resolve this issue. Any insight would greatly be appreciated.
Click to expand...
Click to collapse
Tried reloading a stock ruu?
maRrRrRffin said:
First, my phone is rooted running 4ext recovery and the latest energy rom. It is also sim unlocked from a pin given by tmo.
For the past couple weeks, the phone would randomly shut off and power would drop 30%. After a week of that, my phone won't charge anymore. So obviously I think that I have a dead battery. I replace the battery with a new one and although it is much better, sometimes it still will not charge.
Another issue I have is, I constantly get the message "unlocking PUK" but I am already sim unlocked. This would turn my phone screen on and off every 5 mins or so changing back and forth from locked PUK to unlocked PUK. If I'm doing something on my phone, it would go into the "unlocking PUK" and I have to go back into the app evey few seconds.
I am not sure how to resolve this issue. Any insight would greatly be appreciated.
Click to expand...
Click to collapse
Sounds like a ROM issue to me. I would try flashing a more stable ROM, or even back to stock for a while. Just long enough to figure out the problem.
I'm also having the same problem. HTC unlocked bootloader, latest Energy Rom. It randomely shuts off, and the battery % bounces around all over the place. I reflashed the Rom in 4ext, with a full wipe, battery stats wipe, and fully drained and charged it for 10 hours. Still persists. Stock kernel, still SIM locked so I don't think that matters.
Sent from my HTC_Amaze_4G using xda app-developers app
Shouldn't they be posting in the Energy ROM thread and maybe the dev or others in that tread could help if they have seen these issues, not that I am one to talk but I've heard nothing bad about that ROM?
I want to post in the Ron thread but, even though I've been a member for a long time I do.t have the post count to post in dev posts...
Sent from my HTC_Amaze_4G using xda app-developers app
Hi, I recieved a refurbished replacement rezound from asurion when i dropped mine in water a couple of weeks ago. When i got the phone it immediately had the problem of rebooting all the time. I didnt think anything of it assuming that it was just a problem with ics so i rooted the phone and installed a different rom, i still had the rebooting problem so i flashed another rom and i Still had the problem. The phone seemingly reboots at random dozens of times a day. It has even locked up and rebooted in the recovery and even the bootloader. I cant return it because i dropped it and there is damage so i would have to pay 100$ again. any help?
If you tried complete wipe (system, data, cache, Dalvic) and clean flash without restoring anything and it's still rebooting, I would say the next step should be an RUU. (HERE is the latest).
Max725 said:
If you tried complete wipe (system, data, cache, Dalvic) and clean flash without restoring anything and it's still rebooting, I would say the next step should be an RUU. (HERE is the latest).
Click to expand...
Click to collapse
Yup, i always wipe it clean. Ill try an ruu, but that has nothing to do with it rebooting even in the revovery and bootloader does it?
I know very little of how this low-level hardware control stuff works, but it could technically be possible to make a faulty hboot that will reboot sometimes but normally work. An RUU will replace your hboot with stock, so if it's anything hboot related, the RUU should fix it. If it's not hboot related, I'm afraid it could only be faulty hardware. You could try replacing the battery, but I don't see how a battery could cause reboots. Also, if it is faulty hardware that shuts the phone down completely, flashing an RUU could be risky - if it shuts down while the hboot or radios are being flashed, you could be left with a hard brick, which would be even worse than constant rebooting.
As I said, though, I don't know much about phone hardware or low-level software, so it could be some other problem that I'm entirely unaware of.
I have the battery from my old phone that i could try. and could it have anything to do with the sim card? im using the sim card that came with my old phone that i dropped in water and i didnt use the new one they sent me because i didnt really want to go through the trouble of activating it.
I know nothing of how SIM cards work, but you could try taking out the card, and seeing if the phone will still reboot.
If it doesn't reboot right away, just activate the new one and see how it will work then - it's just a 5 minute (or even shorter) phone call.
Max725 said:
I know nothing of how SIM cards work, but you could try taking out the card, and seeing if the phone will still reboot.
If it doesn't reboot right away, just activate the new one and see how it will work then - it's just a 5 minute (or even shorter) phone call.
Click to expand...
Click to collapse
yeah but i have to call asurion and they arent open, plus im not the account holder or whatever its called.
gabezermeno said:
Hi, I recieved a refurbished replacement rezound from asurion when i dropped mine in water a couple of weeks ago. When i got the phone it immediately had the problem of rebooting all the time. I didnt think anything of it assuming that it was just a problem with ics so i rooted the phone and installed a different rom, i still had the rebooting problem so i flashed another rom and i Still had the problem. The phone seemingly reboots at random dozens of times a day. It has even locked up and rebooted in the recovery and even the bootloader. I cant return it because i dropped it and there is damage so i would have to pay 100$ again. any help?
Click to expand...
Click to collapse
And you might want to get a velcro glove and case set.
What is your hboot version, what recovery are you running, and what rom did you install?
Have you tried connecting your phone to the computer in fastboot mode and removing the battery while it's powered by USB and see if you get the random rebooting in hboot when the battery is out?
Try removing the sim and booting as was mentioned earlier as well.
So update, I installed set cpu and set it at performance and the max at 1300mhz and it hasnt rebooted since, which is saying something since it would reboot about every minute before. I fixed it! but its still not as nice as my girlfriends DNA haha oh well. thank you all for your help
gabezermeno said:
So update, I installed set cpu and set it at performance and the max at 1300mhz and it hasnt rebooted since, which is saying something since it would reboot about every minute before. I fixed it! but its still not as nice as my girlfriends DNA haha oh well. thank you all for your help
Click to expand...
Click to collapse
Did you do this on a stock kernel?
Get another replacement. Mine had an issue where wifi would not turn on. Even after I s off and tried installing roms and kernels it wouldn't boot. My replacement works perfect.
I couldn't have gotten a free one because I dropped it and there are scratches on it now.
Sent from my Rezound using xda app-developers app
I installed multiple ROMs and always had the same issue, im using cm9 rage right now
Sent from my Rezound using xda app-developers app
By switching it to performance mode you locked the CPU at its Max value which will annihilate your battery if you leave it like that. What that means is that the voltage of your CPU was too low at the bottom end and it was making the phone reboot. If your min before was 192, bump it to 384. If it was 384, bump it to 432.
Sent from my ADR6425LVW using xda app-developers app
I had asurion replace my incredible when I broke it once. Shortly after the CPU would over heat all the time and reboot. They covered it under warranty even though it was used. They might cover it under warranty if it hasn't been too long.
Sent from my ADR6425LVW using xda app-developers app
Phone shut off and will not turn on, will not charge, will not boot, nothing.... here's the backstory.
I root my girls EVO LTE for her just for the sake of backing up data and pictures and texts. She also enjoys Fresh ROM, but I never got around to putting it on this phone, bc at the time there was no need. Also, I never did get around to turning S-OFF, just rooted, stock rom, nothing else.
About 3 months ago, she had a random boot loop, which, after some googling, seemed to be a random problem that some people were experiencing, unrelated to root or anything. So we fixed her phone, updated it, at the time, and have since done nothing to it. A few weeks ago, she started have major problems. Texts would take 5 minutes to open, contacts would also, and sometimes she couldn't dial out. Problems that I hadn't gotten around to looking into.
Today, her phone just completely turned off and hasn't done anything since. Won't turn on, charging does not give it a light. I tried to boot into recovery etc. Is the phone completely BRICKED?
It's within the year warranty, but I know if sprint gets it back on and see it's rooted, they'll be assholes about it, even though it doesn't seem to be related.
jirafabo said:
Phone shut off and will not turn on, will not charge, will not boot, nothing.... here's the backstory.
I root my girls EVO LTE for her just for the sake of backing up data and pictures and texts. She also enjoys Fresh ROM, but I never got around to putting it on this phone, bc at the time there was no need. Also, I never did get around to turning S-OFF, just rooted, stock rom, nothing else.
About 3 months ago, she had a random boot loop, which, after some googling, seemed to be a random problem that some people were experiencing, unrelated to root or anything. So we fixed her phone, updated it, at the time, and have since done nothing to it. A few weeks ago, she started have major problems. Texts would take 5 minutes to open, contacts would also, and sometimes she couldn't dial out. Problems that I hadn't gotten around to looking into.
Today, her phone just completely turned off and hasn't done anything since. Won't turn on, charging does not give it a light. I tried to boot into recovery etc. Is the phone completely BRICKED?
It's within the year warranty, but I know if sprint gets it back on and see it's rooted, they'll be assholes about it, even though it doesn't seem to be related.
Click to expand...
Click to collapse
Does it show in device manager when you connect to a pc?
njfoses said:
Does it show in device manager when you connect to a pc?
Click to expand...
Click to collapse
Well I dont have the drivers installed bc I recently added an ssd and started from scratch, and like I said, I don't mess with her phone too often.
But it doesn't do anything when I plug it in via usb, doesn't make a sound, nothing pops up, and it doesn't try and connect. It's lifeless.
Some have had good results plugging into a wall charger for 6-8 hours and then it comes back to life.
It may work.
Sent from my PC36100 using xda app-developers app
Your timing is good, bricks tend to happen during major updates
Have your gf take her phone back to the Sprint store and say it won't turn on, charge etc. if the phone is truly bricked, they can't tell it was rooted or whatever. They should replace it because it's within the warranty period. If she has an SD card, take it out (especially if it had ROMs on it).
The key is have your girl friend do this, better would be to have someone's mother take it in.
bigmoogle said:
Your timing is good, bricks tend to happen during major updates
Have your gf take her phone back to the Sprint store and say it won't turn on, charge etc. if the phone is truly bricked, they can't tell it was rooted or whatever. They should replace it because it's within the warranty period. If she has an SD card, take it out (especially if it had ROMs on it).
The key is have your girl friend do this, better would be to have someone's mother take it in.
Click to expand...
Click to collapse
This is exactly what I done when I bricked downgrading firmware. An OTA had just been released and I told them I took the update and the phone died. They replaced it immediately no questions asked.
Sent from my EVO using xda premium
Hey guys!
The other day, I picked up an Atrix, mainly to use as an mp3 player so my S3's battery wouldn't drain as much during the day.
So, I took the steps any good android-user would go through. I unlocked the bootloader, rooted, and had Clockworkmod all set up.
This is within 30 minutes of having the phone. During the first while of tinkering with it, I noticed some strange things. There's really too many to list, but I'll try.
The phone at times is completely unresponsive. At seemingly random intervals, the Atrix would freeze, and randomly start selecting things.
For example, whilst using the keyboard, it would stream out random lines of text, like yyyyzzyyzyyzyyzyyyxyyxyyzy. Thinking that it was just a fluke with the rom , I carried on.
Often, the only time I can accurately and reliably select something is immediately after turning the screen off and back on again. And sometimes, that doesn't work either.
Also, there seems to be a 4-5 second latency from pressing the screen, to the device registering it.
Again, at random intervals, the image displayed on the screen begins to shake, and becomes unresponsive. I really wish I could record it happening.
There's also a host of other problems. The wifi hasn't ever worked, and the phone flat out refuses to flash some gapps packages.
So, my Atrix is basically a non-functioning, shivering, nightmare of a phone to work with. None of these issues have been caused by flashing different roms, and I have never touched any of the sbf files.
No matter what I try, it is just unusable. Every thing I have tried has failed, and this phone is out of warranty, so replacement is out of the question. So, is there anything I can do to fix this issue? I really, really need help.
Thanks in advance guys!!
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Newbleeto said:
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hey! Well, I started on the stock ota 2.3.6
Yes, the bootloader is unlocked, cwm is the recovery, and I can get into it. Before flashing, I did wipe dalvik, cache, and factory reset.
The roms I've installed are in this order:
Stock ota 2.3.6, Cyanogenmod 7 2013/1/1 nightly, TopSmart's final release 1.3 rom, and AOKP 4.1.2 from October 17.
The roms flash just fine,and I always use the correct gapps. The problems have persisted through everything I have tried.
Bluetooth does not work, and neither does anything that requires a radio. (Data, calls, wifi, etc)
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
affiatic said:
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
Click to expand...
Click to collapse
I got it used, but it was still in the box, and even had the plastic screen that says "Don't text and drive" on it. The phone had literally never been booted up.
I think I figured out the problem, and will try to post a video of it.
The touchscreen just freaks out when being used. I found this out through the pointer location in the dev tools in Cyanogenmod 7
I'm on cm10 and random touches happen to me. I just lock and unlock the screen to fix. Only happens to me on cyanogen roms.
Sent using tapatalk
Could it be a foreign phone? that would explain the radio not working. The screen breaking and ghost touches sound like the leaked rom/kernel, was it happening with all the roms you installed?