I was using my aria as a router using the 2.2 rom. I was IMing people and my sister was watching youtube videos on another computer. After awhile my phone became very hot but it still worked fine so I thought it was okay. Then all the sudden I got disconnected so I saw that my phone had rebooted into clockwork recovery. When I clicked reboot it went to a grey screen for a few seconds then back to clockwork recovery. I decided the phone must have tried to shut it off because it had become too hot but couldn't because it was plugged in and when its plugged in it goes to clockwork recovery. So then I decided I really wanted to talk to my friends so too cool my phone down I put it in the freezer. Yeah, that was stupid. Because now it will not get past clockwork recovery.
When I try to reboot it just flashes the led orange and goes to a dark grey screen for a few seconds then back to clockwork recovery.
Clockwork recovery only shows up when its plugged in and when I try to press the power button when its not plugged in nothing happens.
I tried clearing cache, davik cache and clearing battery stats in addition I reflashed the ROM and it still does the same thing.
UPDATE:
Wow I was a little too quick to head onto trusty XDA and make a post. It works fine now after I unpluged it and waited a few min.
"I really wanted to talk to my friends so too cool my phone down I put it in the freezer."
That is damn funny.
Never mind, glad to hear your up and running.
Sent from my HTC Liberty using XDA App
Back in the old days, when DVD players first came out, I had one that would not play an entire movie because it would overheat. I used to put an ice pack on the top of it to play movies. Worked like a champ.
Nothin' wrong with putting the phone in the fridge to cool it down... I wouldn't put it in the freezer... glass can crack when it undergoes a rapid temperature change. Either way, cooling it too much will likely kill the battery (requiring it to come back to room temp and be recharged).
Related
Rooted adb shell, was on Modaco 1.3 for three months with no problems.
Ok, so today I wiped all & SD card, flashed to Fresh 2.0d, again no problems. Flashed the Vanilla lock screen fix #3 (deleting the HTC clock). Ok stupid me, I like the HTC scene/weather battery eater clock.
Realized I wanted the clock back, so I went into Flipz Kitchen and attempted to push back the stock clock. My phone froze, blank black screen, charging light on. Left it that way for a while, then felt the phone & it was hot-hot-hot, so I disconnected it and the charging light stayed on until I pulled the battery.
Tried a reboot; no go. Gets past the "Fresssshh" sound, quietly brillant screen; hangs at the HTC screen. I went to try my nandroid and found that everything has been wiped. Everything!!!
Ok, so I made sure everything was totally wiped... again. Got Fresh back on the SD Card. Attempted to reflash the zip and it said all was fine. But still hung at the black HTC boot up screen.
WTF? Never before used the Kitchen before tonight, but everything seemed ok before this happened. I admit, I'm not the brightest blub in the bunch but I can take direction real well. Please help; I gotta a conference call bright and early and need ANY kind of workable ROM. Really don't care which at this point.
jedijackie said:
Rooted adb shell, was on Modaco 1.3 for three months with no problems.
Ok, so today I wiped all & SD card, flashed to Fresh 2.0d, again no problems. Flashed the Vanilla lock screen fix #3 (deleting the HTC clock). Ok stupid me, I like the HTC scene/weather battery eater clock.
Realized I wanted the clock back, so I went into Flipz Kitchen and attempted to push back the stock clock. My phone froze, blank black screen, charging light on. Left it that way for a while, then felt the phone & it was hot-hot-hot, so I disconnected it and the charging light stayed on until I pulled the battery.
Tried a reboot; no go. Gets past the "Fresssshh" sound, quietly brillant screen; hangs at the HTC screen. I went to try my nandroid and found that everything has been wiped. Everything!!!
Ok, so I made sure everything was totally wiped... again. Got Fresh back on the SD Card. Attempted to reflash the zip and it said all was fine. But still hung at the black HTC boot up screen.
WTF? Never before used the Kitchen before tonight, but everything seemed ok before this happened. I admit, I'm not the brightest blub in the bunch but I can take direction real well. Please help; I gotta a conference call bright and early and need ANY kind of workable ROM. Really don't care which at this point.
Click to expand...
Click to collapse
The kitchen doesn't support Android 2.1 yet and is only for 1.5. Just reflash Fresh 2.0d on top of itself in RA and you'll be good to go. You may need to wipe again.
Ah crud I'm sorry Flipz, I did read that but I was stupid thinking that I could use it to push back Sprint Navigator and customize themes and stuff. My bad.
Took me several wipes, but Fresh finally worked. My total bad.
Hey Flipz, man thank you a bunch for the super-quick response back. Damn you're good!
OK, I've got a buck thirty-seven in loose change and a John Denvers Greatest Hits cassette for whoever can help me out with this one. I was going to return my Icona to stock last night so I could let it update to 3.1; using Thors CWM, I formatted /system then /data with plans to do a factory reset (out of habit from flashing my phone every week or so, I probably didn't need to). Before the data finished formatting, I got called away from my desk to the OR and ended up leaving the tablet alone for the rest of the night.
This morning, I found the tablet powered down; when I booted it, I got the Acer screen, then the android screen, then it powered down. When I tried to use a USB keyboard to get into recovery, I got nothing. When I tried to boot and hold the "-" down to flash update.zip, it would power off before it would get there. Tried to use the hard reset, nothing.
Put my son on the project today while I was working. He tried everything he could find, specifically the 9-step procedure. No luck there, it will power off before he can get anything done. Strange thing is I just picked it up after it has been sitting a while and tried to boot into recovery, and it went into CWM.... for about 5 secs, then powered down. Now it won't boot into recovery, powers down quickly. He said it did that earlier today, so it seems that if you let it sit awhile and boot, it at least will get into recovery initially (I'm gonna explore that theory, letting it rest now).
Anyone got any advice or ideas? I've searched the threads and can't find anyone who has had this problem yet. If the damn thing had screws on the back, I'd take it apart and drain the battery down. Someone throw some genius my way.
No clues other then if it onlybruns a few minutes is it getting hot
You can open the back with a credit card. Remove your similar then go along the edge starting acoss the tap taking care and be gentle. The plastic on the back is part of what removes as part of the metal to back cover.
Hope this helps
erica_renee said:
No clues other then if it onlybruns a few minutes is it getting hot
You can open the back with a credit card. Remove your similar then go along the edge starting acoss the tap taking care and be gentle. The plastic on the back is part of what removes as part of the metal to back cover.
Hope this helps
Click to expand...
Click to collapse
I might try that soon, gonna keep at it. It's not a heat issue; it only runs a few secs before it shuts down. I know it's got something to do with me formating the data and not finishing the reset.
Have to ask, but is the bat flat or does it do it plug in.
Changing my post...I got a question instead:
When you hold down the "-" key, do you see anything on your screen saying the recovery key was pressed?
SmittyRN said:
OK, I've got a buck thirty-seven in loose change and a John Denvers Greatest Hits cassette for whoever can help me out with this one. I was going to return my Icona to stock last night so I could let it update to 3.1; using Thors CWM, I formatted /system then /data with plans to do a factory reset (out of habit from flashing my phone every week or so, I probably didn't need to). Before the data finished formatting, I got called away from my desk to the OR and ended up leaving the tablet alone for the rest of the night.
This morning, I found the tablet powered down; when I booted it, I got the Acer screen, then the android screen, then it powered down. When I tried to use a USB keyboard to get into recovery, I got nothing. When I tried to boot and hold the "-" down to flash update.zip, it would power off before it would get there. Tried to use the hard reset, nothing.
Put my son on the project today while I was working. He tried everything he could find, specifically the 9-step procedure. No luck there, it will power off before he can get anything done. Strange thing is I just picked it up after it has been sitting a while and tried to boot into recovery, and it went into CWM.... for about 5 secs, then powered down. Now it won't boot into recovery, powers down quickly. He said it did that earlier today, so it seems that if you let it sit awhile and boot, it at least will get into recovery initially (I'm gonna explore that theory, letting it rest now).
Anyone got any advice or ideas? I've searched the threads and can't find anyone who has had this problem yet. If the damn thing had screws on the back, I'd take it apart and drain the battery down. Someone throw some genius my way.
Click to expand...
Click to collapse
Well, I let it sit for a while, and instead of holding down the "-" key, I plugged in the keyboard and pressed the home key. Nothing seemed to happen, but when I turned it back on after that it booted up and let me go through the setup screen. Strange, but at least it's working.
shaun298 said:
Have to ask, but is the bat flat or does it do it plug in.
Click to expand...
Click to collapse
Yeah, sorry, I have no idea what you are asking.
tkirton said:
Changing my post...I got a question instead:
When you hold down the "-" key, do you see anything on your screen saying the recovery key was pressed?
Click to expand...
Click to collapse
Yeah, it would say that the recovery key was pressed or whatever, just for about 1 sec, the shut off.
I've had this Motorola Droid RAZR for like two years now and a friend of mine took it and worked on it, adding something called "Cyanogen Mod" and he 'rooted' it I believe? Ever since, phone has worked great. However, today I tapped the home button and the whole screen had a weird visual glitch where the wallpaper was entirely intact but the icons and such were only half appearing, like someone scratched them out with fingernails or something. It would go away and come back so I got frustrated and rebooted my phone. It starts up normally and goes to this screen where you can do different stuff with Cyanogen mod (like changing the rom? or changing boot options) and usually I just continue past that because for 1) I know nothing about it and 2) It always was fine. But when it did the typical boot up, it just skipped back to the first screen you get when you turn the phone on and repeats. It never goes to the second part of the Cyanogen Mod where the words appear and the little thing spins, it simply skips back to the screen you get when you power up and repeats. It keeps doing this and I looked online how to fix it, tried about twelve different things (like restoring different aspects and using different roms or making new roms) and it just didn't work. Eventually it got bugged out where the screen was just black, couldn't get it to do anything but reboot and go back to black. I let it sit until the battery ran dry I believe and now I'm at a brick wall.
Is there a way I can totally just revamp and start fresh? Like remove all of it and reinstall Cyanogen mod/the OS and all that jazz? I don't mind losing everything if I can just keep the phone, I don't pay for a cellphone and I don't want one I just use the droid for texting apps/games/reddit/etc. If anyone could help me save this thing I'd appreciate it.
Hi there,
Please stand by until mods will move this thread to the related forum for Droid RAZR.
For reply or ask other questions you must register an account.
Stand by
Hello? Can Somebody help me out, I've waited a couple days now and no one has said a thing?
You have safestrap installed, correct? If so, what version?
Dr. Mario said:
You have safestrap installed, correct? If so, what version?
Click to expand...
Click to collapse
How would I know if I had it installed? I remember when I booted up the phone something came on with a picture of a little robot that said "Safestrap Enabled" and then when I had this problem it was saying "Safestrap Disabled". I can't get the phone to turn on right now though, is there a way I can check what version I have another way?
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Dr. Mario said:
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Click to expand...
Click to collapse
Just tried booting it up, nothing is working I think the phone is dead. I plug it into the charger and only the notification light on the top left goes on a blueish white and stays on as long as it is plugged into the charger. Nothing will turn on at all and the phone doesn't seem to respond to anything. Is my phone just dead..?
Soft bricked. Try pushing both volume down and up button while plugged into either computer or charger, and hold down power button until it boots. I hope you won't need to buy Motorola factory cable at this point.
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
ATTACK said:
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
Click to expand...
Click to collapse
In English please?
Edit: Just plugged it in like you said and instantly the boot screen came on rather than simply that silly light so I think my phone is improving but I still would like to entirely revamp it or redo it or whatever you wanna call it so that everything is fresh and new and my phone is okay.
Good. I think it could be because the battery died somehow. Good thing the protection mechanism on the bootloader didn't have the wild idea of disabling the phone.
I was listening to an audiobook when my phone suddenly died. It would not start back up, so I removed the battery. When I replaced the battery, the samsung logo would pop up but after about a second it would go black again. It will not start again until I remove/replace the battery, at which point it does the one second shutdown again.
At one point I got the phone to boot (no idea what I did differently) and I noticed that it got very hot around the camera area before going black again. A second time I was able to get into recovery, where I did a factory reset. Booted back up and it seemed to be okay, but then heated up very quickly and shut down.
Now, even if the phone is totally cool, I cant get past that 1 second of samsung logo. I'm really at a loss here, and totally screwed without my phone because I am traveling non-stop for the next 2 weeks. Does anyone know how I might try to troubleshoot this? Thanks
Possibly flash a new ROM and start over. That's what I would do
This EXACT situation happened to me yesterday! I was streaming from Google music, it was on the charger and things were fine. A call came in and the phone started vibrating like crazy and wouldn't stop. The screen went black and it kept vibrating. Finally it went off. On boot it will get to my lock screen and then crash after about 30 seconds. If I take the battery out and try again it lasts another few seconds after boot. If I leave it for a LONG time with the battery out and restart it I can get like 2 mins on the next boot without it crashing. The top part by the camera is getting hot on my phone as well. Recovery mode and download mode start fine and the phone doesn't crash. I have some data on the internal that I want to save so I tried to use Odin to flash the most recent build L720VPUFNG2 as that would just install the OS and not touch the data. On the next reboot things seemed to be working fine and I got maybe 5 mins out of the phone before it crashed again. I still don't have enough time to get the data off so I think I'm just going to say screw it and wipe it completely. You guys know of a way I can backup this app data using Odin or recovery mode? My phone is currently unrooted. I'm new to all this tinkering stuff. Phone is out of warranty now anyway.
Threw on a custom recovery, backed up all my data, did a full wipe, now I am good as new.
It worked for awhile but now it is back to rebooting itself. Any idea what could be the issue? I'm assuming at this point it is hardware related. Why can recovery and download mode run consistently without crashing but when an os is fired up it has issues? If it was a hardware issue shouldn't it not work across the board?
So I had Sprint replace my phone on the 8th. I have been using my same batteries (1 stock 1 Anker) and chargers (some stock some not) without issue the past 5 days. I rooted and installed xposed and some modules (original broken phone was never rooted and was completely stock). Things were going great until tonight when it started reboot looping exactly like the old phone. I switched battery and same proble. After I took the battery out and left it out awhile it fired back up but I'm afraid the problem will return. Is it possible that the battery or charger randomly are causing damage to the phone? I only have 14 day warranty on this replacement and need to figure this out.
I have no idea maybe try just using your stock battery for a couple days. See how that goes then use your other battery for a couple days and see what happens.
i7vSa7vi7y said:
I have no idea maybe try just using your stock battery for a couple days. See how that goes then use your other battery for a couple days and see what happens.
Click to expand...
Click to collapse
I think it was one of the xposed modules causing the issue. I realized the rebooting seemed to happen whenever I pressed the power button. I had installed a power menu module so perhaps it was the cause. I restored from a nandroid and uninstalled that module and things seem to be working now. Hopefully that was the cause and this thing won't start acting up again after the return period.
killerz298 said:
I think it was one of the xposed modules causing the issue. I realized the rebooting seemed to happen whenever I pressed the power button. I had installed a power menu module so perhaps it was the cause. I restored from a nandroid and uninstalled that module and things seem to be working now. Hopefully that was the cause and this thing won't start acting up again after the return period.
Click to expand...
Click to collapse
That makes a lot of sense. Have to be careful with those Xposed modules. Don't get too carried away installing so many at one time and playing with them and then rebooting. You'll have a hard time figuring out which one is causing it. I'm pretty sure you found your problem.
i7vSa7vi7y said:
That makes a lot of sense. Have to be careful with those Xposed modules. Don't get too carried away installing so many at one time and playing with them and then rebooting. You'll have a hard time figuring out which one is causing it. I'm pretty sure you found your problem.
Click to expand...
Click to collapse
That is exactly what I did I installed like 6 at once and things were working well for a few hours then disaster stuck. I think I won't play with this phone anymore as I am upgrading anyway and want to sell it in working order.
So things were going well for awhile and then the reboot loops started up again. I did some digging and read that apparently Samsung phones are notorious for sticking power buttons and the symptoms were exactly what I was experiencing. I watched some videos online how to open the phone and clean out the power button but it didn't make a difference. I then read that squeezing the connector for the power button with a pair of pliers sometimes does the trick. Not for me. So finally since I'm not under warranty, have no insurance, and the phone wasn't working anyway, I just ripped the white plastic part of the power button right off. Well, that seemed to do the trick. Phone immediately fired back up without issue and has been going strong. I glued a small thin piece of plastic where the old one used to be and I am back in action. If my little plastic piece solution eventually fails or breaks off I will consider soldering on a new button but so far so good.
If you have tried everything else, and are looking for last resort, try cleaning the power button with some alcohol, and if that fails, rip off that power button! Here is the video that gave me the idea: https://www.youtube.com/watch?v=3Glllc7bEJs and here are some other power button videos: https://www.youtube.com/results?search_query=s4%20power%20button&search_type=&aq=f&oq=
Hey,
This is my first time posting here and really using the site. I have the Sprint Galaxy S4 and just updated to the SlimKat official build 7 and had no initial problems. A day later it starts to reboot constantly and would stay on for a couple minutes. Now it is stuck in a bootloop and will shut off even when going into download or recovery mode. When plugged into a computer the computer won't even recognize the phone and the phone will not turn on. The only time the phone will even start to boot is when it is not plugged into wall/computer and on battery. I have no idea what to do now.
That's a tough one. Usually with a soft brick, if you can make it to recovery, your phone can be saved but since you can't... I hope you get it working!
Sent from my SPH-L720 using XDA Free mobile app
puresublimie said:
Hey,
This is my first time posting here and really using the site. I have the Sprint Galaxy S4 and just updated to the SlimKat official build 7 and had no initial problems. A day later it starts to reboot constantly and would stay on for a couple minutes. Now it is stuck in a bootloop and will shut off even when going into download or recovery mode. When plugged into a computer the computer won't even recognize the phone and the phone will not turn on. The only time the phone will even start to boot is when it is not plugged into wall/computer and on battery. I have no idea what to do now.
Click to expand...
Click to collapse
Go to sprint galaxy s4 thread. All answers there. You need Odin 3.09 then stock ng2 tar. To flash through computer.
Sent from my SPH-L720 using XDA Free mobile app
I already have odin and the tar files for stock. When plugged into my computer it will not even register that it is connected and so I can't use odin to flash it.
The same thing is happening to me. I get to the Galaxy S4 splash screen, then it shuts off. Even if I try to boot into recovery
I'm going to pile on in here as I seem to be having a similar issue. I had my S4 (not rooted, stock rom) on my dock streaming google music. A phone call came in and the phone started vibrating like crazy and wouldn't stop. The screen shut off and the phone was still vibrating. Finally it stopped and was shut off. When I try to start it a few things happens. It will sometimes boot to my lock screen and the screen goes black and I think it is powered off. Sometimes it will get past the lock screen and then die shortly after. After like 2 or 3 times of that it won't even boot. It loads the Samsung screen but never gets to the Sprint screen or boots. If I leave it for some time shut off with battery out it will go back to booting to the lock screen then dying etc... When I press the buttons to get into recovery it says recovery is loading and then the screen goes black. I swapped batteries and that didn't do anything. I tried pressing the menu button or the home button to try and boot safe mode and it just loads normally not that I think that would help anyway.
Any ideas on things I can try next? What is this odin thing? Would that work for me?
---------- Post added at 07:09 PM ---------- Previous post was at 06:16 PM ----------
Ok... I can get into recovery now and will try a factory reset. Are you sure you are going into recovery correctly. Apparently I was not. Hold volume up power and menu button and when the phone vibrates let go of power only.
Before I do a hard wipe is there any way to get data off the internal memory from recovery mode?
So I got a custom recovery installed, reinstalled stock rom, things worked ok for awhile. Then it started random reboots every 10 mins or so. Now it is back to instant crashing and rebooting. Any idea what could be the issue? I'm assuming at this point it is hardware related. Why can recovery and download mode run consistently without crashing but when an os is fired up it has issues? If it was a hardware issue shouldn't it not work across the board?
So I had Sprint replace my phone on the 8th. I have been using my same batteries (1 stock 1 Anker) and chargers (some stock some not) without issue the past 5 days. I rooted and installed xposed and some modules (original broken phone was never rooted and was completely stock). Things were going great until tonight when it started reboot looping exactly like the old phone. I switched battery and same proble. After I took the battery out and left it out awhile it fired back up but I'm afraid the problem will return. Is it possible that the battery or charger randomly are causing damage to the phone? I only have 14 day warranty on this replacement and need to figure this out.
So things were going well for awhile and then the reboot loops started up again. I did some digging and read that apparently Samsung phones are notorious for sticking power buttons and the symptoms were exactly what I was experiencing. I watched some videos online how to open the phone and clean out the power button but it didn't make a difference. I then read that squeezing the connector for the power button with a pair of pliers sometimes does the trick. Not for me. So finally since I'm not under warranty, have no insurance, and the phone wasn't working anyway, I just ripped the white plastic part of the power button right off. Well, that seemed to do the trick. Phone immediately fired back up without issue and has been going strong. I glued a small thin piece of plastic where the old one used to be and I am back in action. If my little plastic piece solution eventually fails or breaks off I will consider soldering on a new button but so far so good.
If you have tried everything else, and are looking for last resort, try cleaning the power button with some alcohol, and if that fails, rip off that power button! Here is the video that gave me the idea: https://www.youtube.com/watch?v=3Glllc7bEJs and here are some other power button videos: https://www.youtube.com/results?search_query=s4%20power%20button&search_type=&aq=f&oq=