Hey everyone I have a problem that I sort of fixed but not really? About 2 days ago my phone kept restarting and vibrating. I researched the problem and it said that it might be a stuck button problem. After a few hours I came to the conclusion that a stuck power button was the problem. I went to a cell phone repair shop and had it repaired. IT worked fine on the way home but then I got home and set it on the counter only to come back to it restarting and vibrating all over again. How is that possible after replacing the power button I though. So I did my best and I was able to flash the stock 4.1.2 rom back onto my phone and unroot it and everything. Now my phone has been working fine ever since. Could it be that I cant flash roms anymore? Does anyone know what the real problem to my phone is? If so please respond here. Thank you very much for you're time.
Jyjieng11 said:
Hey everyone I have a problem that I sort of fixed but not really? About 2 days ago my phone kept restarting and vibrating. I researched the problem and it said that it might be a stuck button problem. After a few hours I came to the conclusion that a stuck power button was the problem. I went to a cell phone repair shop and had it repaired. IT worked fine on the way home but then I got home and set it on the counter only to come back to it restarting and vibrating all over again. How is that possible after replacing the power button I though. So I did my best and I was able to flash the stock 4.1.2 rom back onto my phone and unroot it and everything. Now my phone has been working fine ever since. Could it be that I cant flash roms anymore? Does anyone know what the real problem to my phone is? If so please respond here. Thank you very much for you're time.
Click to expand...
Click to collapse
If your phone is functioning normally.....there's no reason why you can't flash any rom made for our phone.
Sent from my cell phone telephone....
The problem is that everytime I flash a custom rom my home button goes crazy and makes the rom un-usable. I have flashed both JMT and Slimrom on my phone and bot ended in the same result.
Jyjieng11 said:
The problem is that everytime I flash a custom rom my home button goes crazy and makes the rom un-usable. I have flashed both JMT and Slimrom on my phone and bot ended in the same result.
Click to expand...
Click to collapse
It sounds more like boot loops which can happen often if you look thru the forums. Your buttons either work or they don't. What rom you are on plays no part in hardware issues like that.
Just be sure when trying a rom, you follow the instructions to the letter. Otherwise boot loops can easily happen.
Sent from my cell phone telephone....
kj2112 said:
It sounds more like boot loops which can happen often if you look thru the forums. Your buttons either work or they don't. What rom you are on plays no part in hardware issues like that.
Just be sure when trying a rom, you follow the instructions to the letter. Otherwise boot loops can easily happen.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
It couldnt have been a bootloop because it was working just fine for a while after flashing and then later on I set it on the table to come back to it flashing where it kept unlocking and locking and unlocking. I was unable to do anything with the phone at the time and after a while it kept restarting and vibrating. You dont think its hardware issues?
Related
I am running the RENOVATE 4.1.2 ROM (ICS) on my One X with CWMR 5.4.0.8. Had a weird problem today. I accidentally dropped my phone while rushing to pick up a call. When I picked it back up again, its screen was frozen at whatever it was displaying whatever was on it before I dropped it. When I tried to navigate, nothing worked and no buttons were responding.
It eventually self rebooted itself and got stuck at the HTC logo. I tried rebooting it via the bootloader three times and it never progressed beyond the HTC logo screen. Thankfully, the recovery was still accessible and I figured that maybe the boot was corrupted and not the ROM itself. I immediately reflashed the boot.img for the ROM and waited for it to reboot.
VOILA! It did. Rebooted normally and came to the home screen. NO changes. No damages. Its all working fine now.
The reason for creating this thread is to know if this is normal? I mean, dropping the phone SHOULD NOT corrupt the boot! I was on a custom ROM and I knew how to flash the boot.img again so I recovered from the issue quite easily but if its was a stock phone, then what? I dont think users will be able to figure it out.
SO, is this supposed to happen?
RipperNash said:
I am running the RENOVATE 4.1.2 ROM (ICS) on my One X with CWMR 5.4.0.8. Had a weird problem today. I accidentally dropped my phone while rushing to pick up a call. When I picked it back up again, its screen was frozen at whatever it was displaying whatever was on it before I dropped it. When I tried to navigate, nothing worked and no buttons were responding.
It eventually self rebooted itself and got stuck at the HTC logo. I tried rebooting it via the bootloader three times and it never progressed beyond the HTC logo screen. Thankfully, the recovery was still accessible and I figured that maybe the boot was corrupted and not the ROM itself. I immediately reflashed the boot.img for the ROM and waited for it to reboot.
VOILA! It did. Rebooted normally and came to the home screen. NO changes. No damages. Its all working fine now.
The reason for creating this thread is to know if this is normal? I mean, dropping the phone SHOULD NOT corrupt the boot! I was on a custom ROM and I knew how to flash the boot.img again so I recovered from the issue quite easily but if its was a stock phone, then what? I dont think users will be able to figure it out.
SO, is this supposed to happen?
Click to expand...
Click to collapse
don't think so mate. maybe the fall has shaken the electronics and did that...weird indeed.
i dropped my wallet on to my phone the other night it froze and turned off, slightly strange if you ask me.
Sent from my Transformer TF101 using xda app-developers app
No it is not supposed to happen. The only reason I can think of is the impact somehow causing an electrical spike due to some internal contacts short circuiting. Probably some files in the system partition got corrupted. But that is a very unlikely scenario.
So my S2 is stuck constantly rebooting before I can attempt to get the phone into download mode or back to CWM.
The best luck I've had so far is to rather consistently press the power button while the phone is trying to boot. This keeps the phone booting for the longest, and I've even made it into CWM and ODIN doing so. However anytime I stop tapping the power button, the phone will reboot.
At one point I did do a super wipe of the cache and OS, I just haven't been able to flash the phone back to stock. The same behavior occurs with a charged battery, a battery-less phone plugged into the wall, and a phone plugged into the wall with the battery in it.
I've opened up my phone to take a look at the power button placement. The plastic case is not pressing in the button, and when I press it in myself I hear a distinct click noise as normal. I've even pried away the case with no luck.
What next steps do I have? I do not have insurance with t-mobile or warranty of the phone. I do have the knowledge to solder if needed. Are there more options for me to try, to fix this issue?
EDIT: So this time I was able to get into ODIN, after letting the phone sit and do nothing for a week. No idea why it works now. I flashed back to stock. Will give it a day or two and then flash back to custom.
If you can get a computer to recognize the phone it can be fixed using adb or another method.
Sent from my SGH-T989 using Tapatalk
So now it's in ODIN and staying there! I don't know why, it never did before.
Should following this be all I need?
http://forum.xda-developers.com/showthread.php?t=1513359
My only confusion is, what is "This will restore to T-Mobile 2.3.6 ULKL1." ? I only know I have the T-Mobile T989 version.
ralewis said:
So now it's in ODIN and staying there! I don't know why, it never did before.
Should following this be all I need?
http://forum.xda-developers.com/showthread.php?t=1513359
My only confusion is, what is "This will restore to T-Mobile 2.3.6 ULKL1." ? I only know I have the T-Mobile T989 version.
Click to expand...
Click to collapse
what i know for sure is that it should be T-Mobile uvlh1 which im 98% sure is the standard base band when i got my phone
but other than that is your phone already rooted?
also when you go in CWM what does it say?
Does it just freeze?
So I did go through with the link and flashed back to stock. Everything seems to be working great now. I did nothing to the phone and it stopped acting up.
What used to happen is the device would act like I was holding the power button constantly. It would simply reboot, but never freeze. It felt Software independent, which worries me that it'll come back.
The problem started slowly, where my phone would reboot on its own here and there. Gradually getting worse. This happened after applying some OTA updates for CyanogenMod10. Though it didn't happen immediately after applying the updates.
Hello everyone.
I have a rooted note 2. Rooted it about 6 months ago, and it have been working without any problems.
Then last night my phone worked fine, no problems at all. Then i wake up this morning, and my phone is turned of.
Tried to turn it back on but when it starts up, I am stuck on my rooms logo. Can't get past it. Then i went to recovery mode (Power+Home+VolumeUp) And did a clear catche. Then did a reboot. And my screen just turned black. Can't turn it on. Now it's just bricked. It wont even charge. When i try to start it up, pushing the home button nothing happens, only the red led light is blinking. Otherwise it is completely bricked. Please, what can i do? I am traveling in Thailand atm. and are so dependent on my phone. This is a really big problem.
Thanks for the help.
Regards Andy
solving soft break
Here have 2 method
1. flash official stock rom through ordin
2. flash stock or other custom kernel through ordin or recovery
than you will solve the brick
i think your phone got SDS.
the only solution is to change your motherboard.
read this thread for more info about SDS.
But when i hold Power+Home+VolumeDown. It doesn't react. The phone is completely dead. Doesn't respond to anything. So how can i flash official stock rom?
sora9009 said:
i think your phone got SDS.
the only solution is to change your motherboard.
read this thread for more info about SDS.
Click to expand...
Click to collapse
OMG. Really hope that this isn't the case.
So weird, last night no problems. Then the next morning it's SDS. LOL
McAndy87 said:
Hello everyone.
I have a rooted note 2. Rooted it about 6 months ago, and it have been working without any problems.
Then last night my phone worked fine, no problems at all. Then i wake up this morning, and my phone is turned of.
Tried to turn it back on but when it starts up, I am stuck on my rooms logo. Can't get past it. Then i went to recovery mode (Power+Home+VolumeUp) And did a clear catche. Then did a reboot. And my screen just turned black. Can't turn it on. Now it's just bricked. It wont even charge. When i try to start it up, pushing the home button nothing happens, only the red led light is blinking. Otherwise it is completely bricked. Please, what can i do? I am traveling in Thailand atm. and are so dependent on my phone. This is a really big problem.
Thanks for the help.
Regards Andy
Click to expand...
Click to collapse
this might help you
http://www.youtube.com/watch?v=0U3x9f_0qLM
But my phone doesn't respond to anything. And i need to get it in recovery mode to unbrick it.
Think that i have SDS though. Really sucks. This is my first and last samsung phone i will ever buy.
Have had so many problems with my Note 2.
Gonna buy the Sony Xperia Z1 next month.
McAndy87 said:
But my phone doesn't respond to anything. And i need to get it in recovery mode to unbrick it.
Think that i have SDS though. Really sucks. This is my first and last samsung phone i will ever buy.
Have had so many problems with my Note 2.
Gonna buy the Sony Xperia Z1 next month.
Click to expand...
Click to collapse
Can you get into download mode. ? If so you may be able to flash stock via Odin.
My Galaxy S3 keeps shutting off during boot. I encountered this problem while running Cmod 11. Was using poweramp playing music off my 64gb exFat microsd card, and suddenly Poweramp encounters "Error too many files" and promptly shuts the phone down. (Poweramp has been giving me strange problems before this, like that error just mentioned, and scanning for changes when there are none, but this is the first time the error caused the phone to shut down).
After rebooting it, The S3 gets to the boot screen and upon opening an app, promptly shuts down again. Further attempts result in the phone shutting off during the boot animation, and finally now the phone simply shuts down right before the boot animation. (note: it doesn't reboot. It turns itself off).
I thought it might be a problem with Cmod, so I wiped everything and using CWM, installed slimkat. Same problem. so I went and installed stock android using Odin, and now I'm back to stock. STILL same problem.
When I have the phone plugged into a computer, it seems to get further than the boot animation before shutting down (sometimes it gets to the lockscreen before shutting down again).
Any idea what's causing this problem? I have no problems with erratic shutdowns during recovery and download mode.
How old is your battery? Might be time to replace it.
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
cheezyphil said:
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
Click to expand...
Click to collapse
They're not as heavy to load.
Was any modification done to your phone (software) about when that started happening?
The s3's been on and off custom roms for a year now
cheezyphil said:
The s3's been on and off custom roms for a year now
Click to expand...
Click to collapse
I mean before it started happening. Or were you on the same ROM/version of that ROM for a while when it happened.
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
cheezyphil said:
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
Click to expand...
Click to collapse
Well if you can get in recovery, I would suggest doing a clean flash. But chances are that it's your battery giving out.
If you want to test, borrow a battery from another S3. I know with T-Mobile you can go to a store and they usually have a device on hand that you can borrow one from to test it out before spending money on it. I imagine you can do this at AT&T stores as well.
had the same problem with my atnt galaxy s3
i have the same problem,,i am using cm12 ryt now,,i tried to put every single rom and same thing happens,,i also brought it back to its stock firmware,,and still the problem occurs... did u find any solution for it,already?
:crying:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.
DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.
DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited
Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.