Okay so I've been a silly billy, when I was going to bed last night, I took my phone with me (turned out to be a bad idea), so after some time browsing the web I fell asleep, I've done this plenty of times without anything happening to the phone, but this time, it didn't go very well. So what I've think caused it was the heat from my body, and the point that I was half laying on it some of the night. But anyhow, the problem is the following. So when I woke up, I took my phone and turned on the screen, all seemed normal, except when I was pressing on the screen nothing happend, so I was checking if it was frozen by pressing the power button and got up the power menu as normal, so the screen must have been "defect", I now understood how silly I was bringing it with me to bed. But, I thought it would just need some hours, to get back to normal, so I pulled the battery, and took it out, and letted the phone lay for itself some hours. When I went back to it, it wouldn't even bring back light to the screen, I could sense it turned on as it vibrated, and it showed there was a nortification by blinking, but it simply wouldn't turn the screen on. Or atleast that's what I think it is. Now I've concluded it can't be a software issue as it doesn't even show bootanimation (whatsoever), but the nortification led works. It can't be anything related to battery neither as it boots up and so on, tried to switch the battery with my replacement one though just incase, samething happend. But the weird thing is, there's no marks on the screen itself, it doesn't seem to have recieved any pressure on it, which has caused the screen not working, also it worked earlier today, just without touch ofc. So any of you guys got an idea? Should I try to go deep into the device and check if the screen is alright ( open the device itself), I don't have an guarentee on the phone, as it expired for half a year ago. Also, I can't afford the cost of the easy way out by getting the screen replaced, atleast not at this point.
Any help would be appreciated
Are you able to acces adb? If so run "adb shell su -c dmesg > dmesg.log" post that log here.
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Are you able to acces adb? If so run "adb shell su -c dmesg > dmesg.log" post that log here.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Its completely dead now, doesn't turn on or anything even after a long charge
Sent from my LG-D620 using XDA Premium 4 mobile app
Hmm that's a bummer. I guess there isn't much else to do. Well, atleast i see you got a replacement. Good luck!
Thymo said:
Hmm that's a bummer. I guess there isn't much else to do. Well, atleast i see you got a replacement. Good luck!
Click to expand...
Click to collapse
Thanks, I did try to open up the phone case to see if anything was loose or so, didn't seem to be the problem..
Sent from my LG-D620 using XDA Premium 4 mobile app
Related
For some reason my screen has stopped working. I press the power button to wake it up and the only thing that comes on are the shortcut buttons. It happened all the sudden this afternoon, and I have charged it sincethento see if that may be the issue. I've taken out the battery 3 times and turned it back on too no avail. When it boots up it make the intro sound but nothing happens on the screen.
It's only 3 months old so it's still covered under the warranty, BUT it's rooted. I need to know is there ANYWAY to revert it back to the stock rom with out the screen so that I can take it back to Sprint. Any help would be great.
Well, they can't see the screen so let them take a look at it. If they fix the screen and see its rooted, no big deal, the phone works.
That is true, I never really thought of that. Let's say they can't fix it. Do you think they would check to see if it's rooted before they replace it, or would they even be able to?
Best bet is to run ruu before you take it in. If they fix it and see its rooted they can be butts and dbr it because of root. One of my Co techs has done it
Sent from my PC36100 using XDA App
kixcastillo77 said:
Best bet is to run ruu before you take it in. If they fix it and see its rooted they can be butts and dbr it because of root. One of my Co techs has done it
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What exactly is that and how exactly would I go about that without the use of the screen?
http://shipped-roms.com/shipped/Sup...0.07.28_NV_1.71_003_release_147044_signed.exe
Just download connect phone to pc and you're set just keep in mind it will wipe out your phone
Sent from my PC36100 using XDA App
Ok... The screen does work but it's like the backlight is broken. In the right light and at an angle I can see the screen, and the touch screen works. I have it turned all the way up but nothing. Has anyone ever heard of this happening? The good thing is will be able to revert back now to take it in.
as title says. last night I was simply watching a movie when i noticed the handset was very very hot, which is weird as it wasn't doing anything too stressing, i figured id let it cooldown abit, not two seconds after the video stopped, the audio went all messed up. I turned it off manually, and it restarted all normally. it happened again, although it wasn't particularly hot, however this time I did not manually restart it, I figured id wait to see if it sorts itself out. Instead it turned off. And it refuses to power on, charge or even go into boot. No idea, what's wrong.
Running on Leedroid OneXtreme 6.4.
shamsul007 said:
as title says. last night I was simply watching a movie when i noticed the handset was very very hot, which is weird as it wasn't doing anything too stressing, i figured id let it cooldown abit, not two seconds after the video stopped, the audio went all messed up. I turned it off manually, and it restarted all normally. it happened again, although it wasn't particularly hot, however this time I did not manually restart it, I figured id wait to see if it sorts itself out. Instead it turned off. And it refuses to power on, charge or even go into boot. No idea, what's wrong.
Running on Leedroid OneXtreme 6.4.
Click to expand...
Click to collapse
can you go through adb,fastboot...?responds to PC when is on USB???LED lights when is in the charger?
If not, you can not through the PC...no response then.....
Unfortunately your motherboard is dead...
absolutely nothing, no flashing led, nothing when connect to pc/laptop. no response to anything.
shamsul007 said:
absolutely nothing, no flashing led, nothing when connect to pc/laptop. no response to anything.
Click to expand...
Click to collapse
...
then I'm sure you lost the motherboard...brick your phone...warranty period .... good luck
i have same problem
mehrshad said:
i have same problem
Click to expand...
Click to collapse
Got that twice with ma HOX...trust me...just plug on wall charger and leave it for a while (30mins or so) and when LED starts to flash, try to boot your device again.
i will try
This is weird but yeah I left in charge for about 12± hours, started flashing about a few mins ago and it's working perfectly. Pretty sure my phone is possessed. So yeah leave it in charge until it flashes.
Btw I'm not doing much, and it's already getting a bit warm, anything I can do to make my phone handle more? Is there a way to under clock this?
Sent from my HTC One X using xda app-developers app
ok i will put in charge from now till next 12 or 13 hours
i hope to fix it
thanks
do a full wipe fastboot erase cache and re flash a rom something is doing something naughty
Sent from my HTC One X using xda premium
mehrshad said:
ok i will put in charge from now till next 12 or 13 hours
i hope to fix it
thanks
Click to expand...
Click to collapse
Good luck! Let me know if it starts working, we could have some sort of alternative medicine on our hands here.
Sent from my HTC One X using xda app-developers app
it's in charge about 13 hours
nothing change and it doesn't flashing led
HELP
No idea then, motherboard may be dead if that's how unresponsive it is. If you have warranty send it off for repairs. Can you get into recovery? How about plugging it into a laptop/computer?
Sent from my HTC One X using xda app-developers app
that sounds very bad
Has anyone tried this?
I had the same problem, no warranty because I unlocked it. Got it back, and found this topic.
Note: It can happen you need to try different pc/notebooks before it charges. I had to switch to 3 different pc s.
http://forum.xda-developers.com/showthread.php?t=1658084
Hope this helps.
Sent from my HTC One X using XDA Premium HD app
its done it again, heated up, now its completely frozen, just gonna have to go through the whole process again. the overheating issues with this phone is ****ed up.
Amicushia said:
Has anyone tried this?
I had the same problem, no warranty because I unlocked it. Got it back, and found this topic.
Note: It can happen you need to try different pc/notebooks before it charges. I had to switch to 3 different pc s.
http://forum.xda-developers.com/showthread.php?t=1658084
Hope this helps.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Do not talk nonsense, do not lose the warranty if the unlocked bootloader, but this board is dead aniway , nothing can see. Send to the service and solve the problem.
JohnnyBlack10 said:
Do not talk nonsense, do not lose the warranty if the unlocked bootloader, but this board is dead aniway , nothing can see. Send to the service and solve the problem.
Click to expand...
Click to collapse
Oh yes it does. I Fixed it with that script after i got it back from HTC.
Sent from my HTC One X using XDA Premium HD app
First time I need help, and it's a big one and hope it a positive result.
I come from viper 2.1.0
I wiped 3 times everythnig. Installed CM10 v8. then google addons, than entered fastboot and instal boot.img than erased....
Booted into android made preliminary input. started to download files and restored my old apps from google play. Whet to settings than from settings I pulled down status bar.
HOX frozze and than I presed the power button and thas' it.
NOW it does not wake up, even if I put the power cord in no lights go ON, nothing. It's like a BRICK.
Anyone any ideas.
you guys think if I send this to reapir and play stupit that thay will now that i had unlocked bootloader
On Friday night, My phone was in the breast pocket of a blazer that got very damp in an unexpected downpour. The phone continued to work on Friday night as far as I recall (I wasn't using it much, but I'm pretty sure I did use it some). When I woke up on Saturday morning, it appeared to be off and wouldn't turn on. I pulled and replaced the battery and still got nothing. I put it on the charger, but I had to run out, and I ended up being gone all day.
When I came home, the power button still wouldn't turn on the device. I pulled the battery and replaced it, and the Google screen came on, then the CM10 boot animation. When it got to the pin screen, however, the screen wouldn't respond to me entering my pin. Then, after a minute, the screen turned off, and the power button wouldn't turn it back on. I did a battery pull. Again, replacing the battery brought up the google screen, the CM10 boot animation, and the pin screen. But, again, the screen was unresponsive, and the power button did nothing when the screen went off.
I took it apart and left it alone all day Sunday. On Monday morning, I tried again and got the same results. I went and picked up a bag of white rice yesterday and left it in there last night and all of today. Still, I've got the same outcome. Buttons and screen are unresponsive.
So I'm left with a couple of questions:
First, is there anything else that can be done? This seems to me to be water damage. Does anyone have any suggestions for possible solutions?
And second, I keep getting text messages. Is there any way to pull those messages using the Toolkit or adb or anything (I'm pretty inexperienced with adb)?
Any help would be great. I'm stuck in China without a phone right now, which is a pain in the butt. I'd like to revive this, and I don't want to go track down a new phone until I know this one is sunk. Thanks for your help.
install android-sdk
run adb server on the host
connect your device to pc (feed it naked drivers manually found on dev section, if you're on windows and device manager shows unknown device)
type: adb devices
q: do you see your device listed? (should be lots of numbers and letters)
if it doesnt even recognizes that it has been plugged in, then your usb connection went down the drain, nothing else you can do
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
ejchis said:
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
bk201doesntexist said:
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
Click to expand...
Click to collapse
And you would expect this to resolve the screen and buttons being unresponsive? This is interesting. Is it possible to pull my messages beforehand?
Sent from my Nexus 7 using Tapatalk 2
I didn't have luck finding an answer to this on the forums so I figured I'd make a new post. I have been running a version (not sure which) of Liquid Smooth for a few months. Yesterday, I noticed my phone was on a boot loop. It would vibrate, show the Samsung Galaxy S3 screen and then turn off. I pulled the battery and memory card and tried again. It still wouldn't come on. I pulled the battery and then rebooted to recovery mode. I went there to wipe and reboot. When I tried to do that it said something like, "what you are looking for can't be found". I pulled the battery again but this time when I tried to turn it back on it did nothing. I have no vibrations, I have nothing on my screen. I'm not sure what could have happened because I haven't made a change to my phone for quite some time. Any ideas?
bralaheh said:
I didn't have luck finding an answer to this on the forums so I figured I'd make a new post. I have been running a version (not sure which) of Liquid Smooth for a few months. Yesterday, I noticed my phone was on a boot loop. It would vibrate, show the Samsung Galaxy S3 screen and then turn off. I pulled the battery and memory card and tried again. It still wouldn't come on. I pulled the battery and then rebooted to recovery mode. I went there to wipe and reboot. When I tried to do that it said something like, "what you are looking for can't be found". I pulled the battery again but this time when I tried to turn it back on it did nothing. I have no vibrations, I have nothing on my screen. I'm not sure what could have happened because I haven't made a change to my phone for quite some time. Any ideas?
Click to expand...
Click to collapse
Battery is going bad or the hardware is going bad.
What recovery and version?
Have you tried booting into recovery or download mode?
Take battery out and put back in:
Recovery: volume up, home button, power
Download mode: volume down, home button and power
Sent from my SGH-T999 using XDA Premium 4 mobile app
Aerowinder said:
Battery is going bad or the hardware is going bad.
What recovery and version?
Click to expand...
Click to collapse
I'm not able to get the phone to come on so I don't know the versions of anything I've used. All I know is my phone is the T-999. Sorry, I know that's probably no help at all.
You don't have a spare battery do you? If not, you should see if you can find someone you know that has one. It could be that you battery just went bad.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Da Kine said:
Have you tried booting into recovery or download mode?
Take battery out and put back in:
Recovery: volume up, home button, power
Download mode: volume down, home button and power
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried all of this but did not have any luck. The phone doesn't do anything. It doesn't make any sense how it can just stop working out of nowhere like this. Wouldn't it mess up immediately after I rooted/added a custom ROM if I did something wrong rather than a few months later? I'm afraid that the phone may be done for. : (
bralaheh said:
I tried all of this but did not have any luck. The phone doesn't do anything. It doesn't make any sense how it can just stop working out of nowhere like this. Wouldn't it mess up immediately after I rooted/added a custom ROM if I did something wrong rather than a few months later? I'm afraid that the phone may be done for. : (
Click to expand...
Click to collapse
I hate to say it, but usually when something like this happens it's most likely to be hardware related. If you don't have access to a spare, go to a T-Mobile store and ask to borrow a battery to see if it'll power up with a known good one. Batteries usually don't just die like that, but it can happen.
So you don't get a short vibe or anything out of it? What about when you hold the power button for about 10seconds? If you remove the battery and plug it in, do you get an led lit up? How about with the battery in?
If the battery turns out to be good, you could attempt the debrick method by KAsp3rd stickies in development. I don't see why it would be a brick, but at this point I'd try anything available just to be positive.
If you have insurance on it, it may be time to consider using it.
Sorry to hear this is happening to you man. These S3's are starting to get a little old though, and no matter how careful we are, they do suffer more abuse than any other electronics we may use. I'm seeing more and more posts like yours recently, I'm sorry to say.
Keep us updated on it, and good luck with it!
Sent from my SCH-I535 using Tapatalk 4
My wife's s3 shut itself down a few days ago and now it's stuck in a boot loop. It was on rooted stock 4.1.
It will not fully boot into the system, trying to get into recovery will barely let you see the recovery screen before it cuts off, and getting into download mode will turn off after about 20 sec.
I'd love to be able to savage some things from the device, but I'm lost as to what I could try now.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Sounds like a faulty/stuck power button. A common thing these days. Open the device and play with the switch a little. Ive seen several people say this fixed it temporarily. Doesn't work for everyone though. If it is the button, the only permanent fix is to replace the part. Only a few bucks online and I dont believe its too difficult to do.
Thanks for trying to help. Unfortunately it didn't help me. Took it apart, physical button actuates fine, switch underneath seems to click and return ok. Blew compressed air to be sure nothing's making it stick, button and switch. When I got it back together, except for actually having recovery load up for a few sec (once), it is behaving the same way.
Seeing as I have no soldering experience or equipment and we have already got my wife another device, I may just call it dead.
Thanks again for the help.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Sorry I cant be of better help for that. If you want to do a quick test though, just so you know for sure....
Take out the battery, then put it back in and wait a few moments. If it turns on by itself, its almost definitely a power switch gone bad.