[Q] i9000 will not power on after shut down - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi All,
I am experiencing an issue which I cannot seem to find a solution to..
I purchased my i9000 in August and it has been working fine since them (no sd issues, gps sucks though). I had no lag fixes and device was not rooted.
I upgraded using the official Bell release to froyo last week. couple days ago I shut my phone off via the power button. When I tried to turn it back on, it would not turn on. It displayed the empty battery icon even though the battery was fully charged.
I tried connecting to Kies and my computer would not detect it
Finally as a last attempt, I plugged the phone into the wall charger and hit the power button and my phone turned on.
So long story short, since the froyo update for some reason my phone is not detecting the charge of the battery when it is turned off and therefore cannot be turned on without being plugged into a power source i.e wall charger, computer etc.
I tried multiple batteries and had the same outcome.
Has this happened to anyone else?

Have you tried reflashing? You could use Kies Registry Patcher to make Kies think that you have an earlier software version, and make it flash the newest software again.

I have not tried the kies patch - but I did do multiple hard resets (i.e. volume up + home + power button).
The phone starts up - but only if it is plugged into a powersource - not on its own. Once its plugged into a powersource and boots up - its fine.
this is really weird.

Something could've gone wrong with the software when you updated to froyo. Try to reflash it.

Thank you. How do i reflash it? I am a newbie when it comes to flashing android devices.
Sent from my GT-I9000M using XDA App

Hi
did you manage to resolve this issue?
i am having the same problems with my phone.
thanks

Thank You for the tip. For me worked fine after update with Kies.

Related

[Q] SGS Switch on issue

Hi,
Yesterday my sgs developed a fault. It can come out with messages saying USB connected or USB debugging connected, slows down, sometimes becomes unresponsive for few seconds. It can switch itself off and when i try to switch it back on comes up with "busy" sign (that spinning wheel) and sometimes is showing empty battery symbol. Only way for it to be switched on is to plug the charger. Battery is fully charged,I know it, cause its plugged in for few hours, i disconnect it, and all of sudden drops dead. Tried today with another battery from my friends sgs but it comes up with same stuff.
Can you help me?
Firmware is stock JPY flashed via odin, not rooted, only with few apps installed on it
Many thanks
Mario
reflash it and wipe factory settings

[Q] Incredible S Won't turn on at all anymore.

Got the phone just over a year ago so it's just out of warranty.
The phone recently started turning off, forcing me to remove the battery in order to restart it. This occurred when I turned the screen off (power button) and left it off for more than about 20 seconds. This was obviously a massive pain in the ass, so I decided to s-off, root, then put custom firmware on it.
So I plugged it into the computer and was just downloading all the required bits, and I got a phone call. I picked up, talked for a bit, then when I hung up I instinctively turned the phone screen off. I then left it for about half an hour until the downloads were done (HTC Sync downloading at 40 kbps >.<) and then went to turn it back on. Of course it had offed itself.
So I went to pull the battery out and do the usual -- to no avail. I tried outing the battery, plugging it in, then putting the battery back in (as read from a random Google result) and nothing.
TL;DR:
Here's the status:
Phone began doing the seemingly standard random turn-offs that require a battery loop.
After a week or so of this, the phone stopped coming back on.
And it will not give any sign of life (No vibrates, no lights when plugged in, no PC response)
Phone has never been dropped / watered
Tried different leads / USB - power adapters
Battery was at about 80-90% at the time of offing forever.
Tried with SIM Card in and out
Tried with MicroSD card in and out
Is this **** bricked? I wanted to wait for the Edge to come out before I upgraded; I don't want to end up with a Sensation or something.
Any fixes?
andrew207 said:
Got the phone just over a year ago so it's just out of warranty.
The phone recently started turning off, forcing me to remove the battery in order to restart it. This occurred when I turned the screen off (power button) and left it off for more than about 20 seconds. This was obviously a massive pain in the ass, so I decided to s-off, root, then put custom firmware on it.
So I plugged it into the computer and was just downloading all the required bits, and I got a phone call. I picked up, talked for a bit, then when I hung up I instinctively turned the phone screen off. I then left it for about half an hour until the downloads were done (HTC Sync downloading at 40 kbps >.<) and then went to turn it back on. Of course it had offed itself.
So I went to pull the battery out and do the usual -- to no avail. I tried outing the battery, plugging it in, then putting the battery back in (as read from a random Google result) and nothing.
TL;DR:
Here's the status:
Phone began doing the seemingly standard random turn-offs that require a battery loop.
After a week or so of this, the phone stopped coming back on.
And it will not give any sign of life (No vibrates, no lights when plugged in, no PC response)
Phone has never been dropped / watered
Tried different leads / USB - power adapters
Battery was at about 80-90% at the time of offing forever.
Tried with SIM Card in and out
Tried with MicroSD card in and out
Is this **** bricked? I wanted to wait for the Edge to come out before I upgraded; I don't want to end up with a Sensation or something.
Any fixes?
Click to expand...
Click to collapse
Sounds like your phone just died.
Another explanation is you have something loose, you should open it and check .
Sent from my HTC Incredible S using xda premium
I'll take it in the an Optus shop today and start yelling abuse, maybe that will get it fixed. Worked on my old Legend. If that doesn't work, I'll open it up and have a look.
Yelling didn't work, they just tried out the phone on all their chargers and it failed.
So I'll open it now.
OK here's a picture of the USB charger bit. I can't post external links, so I'll attach it.
It looks okay... is this what I should try replacing? The USB thingy?
BTW, I unplugged everything then plugged it all back in, so nothing's loose.
Hey Andrew, I sent you a PM.
Struggling with the same problem...
Just made a call from my phone. After the call the phone seemed to be stuck on the call screen. I didn't think anything of it and left the phone alone. When i tried to use the phone again, there was no screen and the phone was not responding. I tried to re-start the phone by pulling out the battery but it won't switch on. You people seem to have the same problem. Any help would be really appreciated. Thanks.
Just a suggestion, but have you tried removing the battery and powering on with the charger connected?
I guess this would help resolve whether it's a battery/charger issue.
Sent from my Incredible S using xda premium
incredible s wont turn on
DeGozaru said:
Just a suggestion, but have you tried removing the battery and powering on with the charger connected?
I guess this would help resolve whether it's a battery/charger issue.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
I have a similair issue i was flashing a rom and my phone decided to turn off or was restarted by the rom update utility and never came back on now i tried it connected to a regular power charger and usb to my laptop and it wont recognize anything. battery was fully charged when i was flashing the rom can the incredible s power on with no battery? and if mine can't and wont be recognized by pc is it toast?

[Q] Gnote failed on Kies

Hello XDA,
I could not find a similar problem so I created a new thread.
Last night I was finally able to update my Galaxy Note GT-N7000 VIA Kies from 2.3.6 to 4.0.0 on my Macbook Pro. Exciting!
Then it happened, Kies suggested that I update the firmware on my device. I did, the download froze, Kies froze, the joy was gone.
I tried countless times to reconnect my device and start over but the Note would not connect VIA Kies. It just said connecting over and over. After spending much time I gave up and went to bed having put my phone on charge.
3 hours after I woke up my phone was fully charged. (STILL) Then it was not, now my phone is constantly going from charge (when its not even plugged in) to not charged. Dead, then fully powered. It continues to spam me the whole time with my batteries current state.
Its an international model in the US so theres no support.
How can I fix it? Hard Reset? Throw to the wall? Paperweight? Or XDA Magic?
I take it you are still on GB. In that case, try a factory reset.
Thanks for the reply!
I tried it 3 times so far since this has happened. As soon as I start using my phone it bugs out. Keeps opening Voice Search and then exiting, completely annoying me in the middle of doing things. Then it will turn itself on when I have switched it off. Then beeps at me while its sittin on charge.
I dont know what the hell its doing. I have seen that other people have suffered similarly but they are experiencing problems with buttons not working and they flash. I dont want to flash my device because when I go back to Iraq I wont have internet all the time to just play with manual updates etcetera...

[HELP] Strange Soft Brick issue

Hello all,
I searched around, but didn't find anything quite like my issue so figured I'd create a new thread.
I work for a company that uses Galaxy Tabs for various purposes. One of our men brought back their VZW Galaxy Tab (SCH-i800) and it was in an infinite boot loop.
I went to recovery and attempted to do a full wipe. This did not work (partitions were all jacked up) so I couldn't get it fixed. I'm not sure if the guy tried to root the thing and broke it or what.
Anyway, I was attempting to root then fix the partitions (then was going to flash a stock unrooted rom) and ended up soft bricking it (Phone Icon -- /!\ -- Computer Icon). The issue I'm having is the only time that screen comes up is when the device is plugged into the wall. It turns on, then off, then on, then off. If I unplug the device, it shuts down with no way of bringing it back up. I've tried holding power for 5 minutes, the same amount of time with power + vol up and power + vol down. Plugging it into the computer's USB ports does not help either.
It's like the battery is drained but it won't charge when it's on the soft brick screen. I've had it plugged in to the wall for almost 6 hours now with no hope in sight. When it's plugged in, I feel heat on the back of the device like it would normally be charging. The AC adapter is also the standard warmth after a lengthy charge.
I was wondering if anybody has had similar issues with this device and if there is any way to correct it.
--- EDIT 8/10/2012 ---
Another thing of note is when the device is charging, I can power it down by holding power for a few seconds, but the Soft Brick screen pops back up almost immediately upon release of the button.
I cannot boot into recovery or the standard download mode even when it's plugged in.
As long as you can get the Phone ! PC screen, your'e good, because this screen IS as a download screen. Go to this screen and flash a known good ROM.
ableeker said:
As long as you can get the Phone ! PC screen, your'e good, because this screen IS as a download screen. Go to this screen and flash a known good ROM.
Click to expand...
Click to collapse
You must not have read the whole thing. Not a problem.
The only time I get the Phone ! PC screen is when it's plugged in to the wall. As soon as I unplug it, it goes away and the device won't start up no matter what I try.
When you connect the tab to the pc, is it recognized by Odin.
Sent from my GT-P1000
salahmed said:
When you connect the tab to the pc, is it recognized by Odin.
Sent from my GT-P1000
Click to expand...
Click to collapse
No... When the device is unplugged from the wall it is shut down and won't boot back to the download screen, recovery, nothing. It doesn't turn on. There are occasions where the download screen stays up but it appears to just be frozen. The computer doesn't recognize it and neither does Odin.
I left it plugged in when I left work on Friday... Going to see if charging for the weekend does anything.
MaskedDriver said:
No... When the device is unplugged from the wall it is shut down and won't boot back to the download screen, recovery, nothing. It doesn't turn on. There are occasions where the download screen stays up but it appears to just be frozen. The computer doesn't recognize it and neither does Odin.
I left it plugged in when I left work on Friday... Going to see if charging for the weekend does anything.
Click to expand...
Click to collapse
No dice.. still jacked.
I determined the following scenarios may have happened:
1) The battery died (bad battery) during a software update and messed up the partitions
2) The battery died (bad battery) while he attempted to (unauthorized) root or flash the device, messing up the partitions.
The only thing I'm sure of is the battery is fried so any kind of hacking I can do to the device are for naught. I was able to get it to connect to Odin this morning for about 3 minutes (after having it plugged in to the wall all weekend). During the flash it shut down again bricking it even worse. Now the device won't turn on when plugged in to the wall.
Thanks for the suggestions and help. I'm calling this a lost cause at this point. We're just swapping out the device for a new one. Once that's complete, I may tear the device down and try to do a reset on the main board to see if that does anything, though I doubt that's the case.
Right I had exactly the same problem as you (exactly the same symptoms) but I have now fixed my tablet.
Like you I got to the point where the Tablet had enough charge to actually unplug it and connect it to my PC where I then tried to flash a stock ROM using Odin. About three quarters of the way through flashing the stock ROM the tablet died, disconnected from Odin and I got a message in the task list in Odin advising me that the process had failed. Even weirder my PC did an emergency shut down and restarted in safe mode.
Anyway I tried it again but when I started my machine, once I'd logged onto my desktop I started up Odin as quickly as possibly, selected the .tar file and pressed start as quickly as possible....it worked and my tablet was flashed with a stock ROM. However my battery was still pretty much dead and the first time of charging once it had been flashed with the ROM took about 24hrs plugged in at a mains charger for the battery to reach 100%.
My point is persevere with it and you will fix it. I was at the point where I was about to send it off to be un-bricked but obviously I'm glad I didn't now.
It is a ***** of a brick though, this 'coma brick'.
I've been having these same issue with my friends i800 galaxy tab. Can you chime in and offer some advice?
Sent from my Galaxy Nexus using Tapatalk 2
same problem-solved
I was having the exact same issue. the device screen was completely black when plugged into the computer. I was just about to give up when, all of a sudden the device went to the boot error screen while plugged into my computer. Apparently, it must remain plugged into the computer for about 20-30 minutes. Once this screen appeared, I ran the Heimdall one-click unbrick utility, and like magic, my galaxy tab was working again. Give it a try, and good luck.
MaskedDriver said:
Hello all,
I searched around, but didn't find anything quite like my issue so figured I'd create a new thread.
I work for a company that uses Galaxy Tabs for various purposes. One of our men brought back their VZW Galaxy Tab (SCH-i800) and it was in an infinite boot loop.
I went to recovery and attempted to do a full wipe. This did not work (partitions were all jacked up) so I couldn't get it fixed. I'm not sure if the guy tried to root the thing and broke it or what.
Anyway, I was attempting to root then fix the partitions (then was going to flash a stock unrooted rom) and ended up soft bricking it (Phone Icon -- /!\ -- Computer Icon). The issue I'm having is the only time that screen comes up is when the device is plugged into the wall. It turns on, then off, then on, then off. If I unplug the device, it shuts down with no way of bringing it back up. I've tried holding power for 5 minutes, the same amount of time with power + vol up and power + vol down. Plugging it into the computer's USB ports does not help either.
It's like the battery is drained but it won't charge when it's on the soft brick screen. I've had it plugged in to the wall for almost 6 hours now with no hope in sight. When it's plugged in, I feel heat on the back of the device like it would normally be charging. The AC adapter is also the standard warmth after a lengthy charge.
I was wondering if anybody has had similar issues with this device and if there is any way to correct it.
--- EDIT 8/10/2012 ---
Another thing of note is when the device is charging, I can power it down by holding power for a few seconds, but the Soft Brick screen pops back up almost immediately upon release of the button.
I cannot boot into recovery or the standard download mode even when it's plugged in.
Click to expand...
Click to collapse
I am having this issue with my sch-i800.... phone /!\ pc screen only when plugged into the wall, and no recognition of it on the pc. Any way of fixing it?

Galaxy S5 (AT&T) Won't Power On - Tried Multiple Good Batteries - Tried 3 Button

Asking for a second opinion before pronouncing the patient dead.
Last night my wife handed me her Galaxy S5 and said that it was hot to the touch (and it clearly was). I pulled the back and the battery to let it cool for about 30 minutes. After that, I tried to power it back on, but it was in a boot loop. I pulled the battery again, reinserted it and let it charge overnight. This morning she woke me to show me that her phone was at the OS download screen. She said that she had pressed Power and Home to boot it up and that it went to the OS download screen on its own. She denies having pressed VOL-Down (or VOL-Up) when she powered it on.
This was followed by it being an endless boot-loop. Anyway, after all this, I thought that I'd reflash the kernal and start over. However, after another battery pull, I can't get it to turn on. I swapped the battery in her S5 with a fully charged battery from our daughter's S5, but wife's S5 still wouldn't power on. I tried wife's battery (strangely only 52% charged after being on charger all night) in daughter's phone and it booted right up. So... battery is not the issue. Further troubleshooting this morning, I tried the three-button-salute (holding power, VOL-Down and Home button) until I thought I'd need finger surgery, but nothing. I installed Odin and connected wife's phone to my PC. For an instant Odin seemed to recognize the device, then nothing. Subsequent restarts of Odin never recognize that there's a phone connected. I installed KIES, but it doesn't see anything connected. My PC's USB "safe eject" thingy does not see a device connected.
Her phone seems (to me) well and truly dead. I'm out of ideas for troubleshooting (much less fixing) this device. Any suggestions before we have a memorial service and bury it in the backyard?
A Few Questions
The mention of odin's temporary recognition leads me to believe it isn't completely dead.
1. What was the version of android (4.4.4, 5.0, 5.1)?
2. Are the samsung drivers installed properly on your pc?
3. Did you use the oem cable or a good build quality data cable?
Birkyjon said:
1. What was the version of android (4.4.4, 5.0, 5.1)?
Click to expand...
Click to collapse
It was at least 5.x. It was whatever AT&T had given as far as OTA updates goes. It had never been rooted. It would have taken any OTAs that AT&T ever issued. Sorry, not my phone, so I'm not sure.
Birkyjon said:
2. Are the samsung drivers installed properly on your pc?
Click to expand...
Click to collapse
There were no error messages of any kind when installing KIES 3.2.16011_2 (which would have installed/updated Samsung drivers).
Birkyjon said:
3. Did you use the oem cable or a good build quality data cable?
Click to expand...
Click to collapse
I used a high quality cable from MonoPrice. I've used the same cable countless times for flawless data transfers between my PC and various family Android devices.
Dupe, sorry.
Use the method in the thread I made up to the first flash. http://forum.xda-developers.com/att...x-samsung-s5-att-sm-g900a-lollipop-5-t3305497

Categories

Resources