Tonight my G1 displayed some very odd behavior. It was running normally and I pressed the power button to make it sleep and I set it aside. About half an hour later I picked it up and tried to turn it on by pressing menu. The phone gave no response other than lighting up the five buttons on the bottom. I tried sliding the keyboard out and the keyboard lit up as well, but the display remained black. Plugging it in via USB to my computer did absolutely nothing (no sounds, no notification light, etc.), and I got the same result when I plugged it into the charger. I finally decided to take the battery out in order to turn the phone off, and then put it back in and pressed the power button. The phone booted up normally, and now everything seems to be working in proper order. I am slightly concerned, however, as I have never had this behavior in the year that I have owned my G1. I am running Cyanogen 4.1.999 with the Hard SPL boot loader. I am unsure whether this behavior has anything to do with the mod and I am wondering if anyone else has experienced anything similar. I do realize that if my phone is bricked it is my fault, and I want to determine if this was simply a freak accident or if I need to do something differently with the phone.
first of all if your phone was bricked you wouldn't be able to use it. as for your problem it doesnt sound too serious so if i were you i wouldn't worry about it. but if it does happen again reflash your phone and if it happens after that, pitch it to cyanogen to see if there is a problem with the rom.
I do realize that it isn't bricked now, but I am worried that this behavior could mean that I am pushing the phone too hard. I am mostly curious as to whether or not anyone else has experienced similar behavior from their G1.
Turn off compatibility mode in spare parts.
don't worry this is a common problen It happens to me all the time any hero I flash plays nice for about a day. and then boom no problems with cyan!
I had the same problem, but unfortunately my G1 is still not working properly.
In the morning, turning off the alarm I left the phone for 5 minutes. An attempt to turn it on did not work: there was no reaction on display, although the buttons were lighting up. I restarted phone taking the battery out and now I have following:
- keyboard fully closed: no reaction/black display, buttons are lighted up
- keyboard open: I can do everything: change ROM/make call/write messages/Internet/GPS/... - everything what is possible to do with rooted G1
- keyboard partially open (visible only lowest row with such buttons as ALT, SHIFT, SPACE): similar to 'open' but with changed orientation
Can anyone help/advise? Did almost everything: ROM changed, full wipe, recovery
Hi Folks,
I have been using an unlocked Captivate for 3 months. I recently flashed MIUI ROM - 1.7.8 (from Cognition) and it was working fine for a day. Suddenly, when I had put the phone on charge (power not USB), the screen turned black and the phone is not working after that.
I flashed to stock (ODIN: as mentioned here: http://forum.xda-developers.com/showthread.php?t=776255) but after that the AT&T logo comes up (with the screen display very dull) and I hear the Samsung startup sound (no screen). That is all. It goes to black screen with the buttons highlighted.
If I connect it to my PC, I can browse the SD card but the screen doesn't turn on at all. I tried re-flashing to stock multiple times with no luck. Please help!
indophile said:
Hi Folks,
I have been using an unlocked Captivate for 3 months. I recently flashed MIUI ROM - 1.7.8 (from Cognition) and it was working fine for a day. Suddenly, when I had put the phone on charge (power not USB), the screen turned black and the phone is not working after that.
I flashed to stock (ODIN: as mentioned here: http://forum.xda-developers.com/showthread.php?t=776255) but after that the AT&T logo comes up (with the screen display very dull) and I hear the Samsung startup sound (no screen). That is all. It goes to black screen with the buttons highlighted.
If I connect it to my PC, I can browse the SD card but the screen doesn't turn on at all. I tried re-flashing to stock multiple times with no luck. Please help!
Click to expand...
Click to collapse
So your saying your phone actually fully boots, you just can't see it? (I would test this by calling myself) This is a problem I've never heard of.... Can you boot into recovery with a working screen? Could be a hardware problem, considering how it happened.
Hi,
I was able to call my number earlier (before flashing back to stock) but not anymore (get a busy line after the first ring). However, I get the AT&T screen (only time I see something on my screen) and the Samsung startup tone and the buttons are all highlighted. The screen is black.
Even when I did Odin, I was doing it from a black screen (the Download icon on the screen didn't show up). I never get to see anything on the screen other than the at&t logo (so not able to boot into recovery actually!).
I just hope it is not a h/w pbm. I would rather try fixing it myself (if it s/w pbm) than taking it to the store
indophile said:
Hi,
I was able to call my number earlier (before flashing back to stock) but not anymore (get a busy line after the first ring). However, I get the AT&T screen (only time I see something on my screen) and the Samsung startup tone and the buttons are all highlighted. The screen is black.
Even when I did Odin, I was doing it from a black screen (the Download icon on the screen didn't show up). I never get to see anything on the screen other than the at&t logo (so not able to boot into recovery actually!).
I just hope it is not a h/w pbm. I would rather try fixing it myself (if it s/w pbm) than taking it to the store
Click to expand...
Click to collapse
What kind of charger were you using? Honestly, it sounds like you fried some of those beautiful innards I'm no expert, though.
Twicebak3d said:
What kind of charger were you using? Honestly, it sounds like you fried some of those beautiful innards I'm no expert, though.
Click to expand...
Click to collapse
It could possibly be because of the power issue (my charger model is ETA0U60JBE which supports 100-240v and I have 240v at my place so it should not ideally be a pbm). I'm just trying to see if there is some s/w fix for this situation before giving it for a h/w check.
Would this be a problem with my LED screen (though I see the at&t logo come up)? If it is, would it be some connection issue to the LED screen or a completely dead LED?
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Marc_B_ said:
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Click to expand...
Click to collapse
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
timberman4444 said:
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
Click to expand...
Click to collapse
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Marc_B_ said:
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Click to expand...
Click to collapse
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Hi again, try to play a song and turn the screen off to see what happens.
Sent from my GT-I9000 using xda app-developers app
timberman4444 said:
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Click to expand...
Click to collapse
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Marc_B_ said:
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Click to expand...
Click to collapse
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
timberman4444 said:
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
Click to expand...
Click to collapse
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Marc_B_ said:
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Click to expand...
Click to collapse
you tried to install the rom on the recovery instead of odin?
timberman4444 said:
you tried to install the rom on the recovery instead of odin?
Click to expand...
Click to collapse
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Marc_B_ said:
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Click to expand...
Click to collapse
so, you can`t install any rom at the moment?
timberman4444 said:
so, you can`t install any rom at the moment?
Click to expand...
Click to collapse
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Marc_B_ said:
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Click to expand...
Click to collapse
Pretty bad signals there.. i think you should go to a repair shop or buy another device
timberman4444 said:
Pretty bad signals there.. i think you should go to a repair shop or buy another device
Click to expand...
Click to collapse
Sadly, yes... thanks for helping however !
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
thefunkygibbon said:
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
Click to expand...
Click to collapse
IIRC the Xperia Z1 has a hard reset button under the sim flap, it's a small red button, give it a shot.
remove sim card and sd card and try again, if it's still not responding do an update repair using SUS or PCC
BTW there is a known fault with the XZU and it could also be on the Z1 as they use similar Firmware, what people have found is that the phone will start up eventually and then they go into the display setting and untick the auto backlight option and that fixes it
I also reboot my Z1in this way when it blackout.
Sent from my C6902 using xda app-developers app
Had the same issue called Sony, push hard reset button all is fine in the world. Known issue Sony is working on it
Sent from my C6903 using Tapatalk 4
Managed to hard reset using power and up volume .
Put it on charge overnight but it doesn't see,m to have taken any charge at all....just trying again using diff PSU and cables but it doesn't want to charge. It recognises that I've out a cable in as I played with the smart connect setting. When it is off completely I get a red light (presumably meaning its charging ) but not in android
Any ideas?
Got it charging again by pushing the red button near sim slot for a couple seconds.
Just had another issue with SD card not being recognised after I removed another (/safely) had to reboot again using power plus vol up as it stuck on the shutdown logo when I tried to power down'...
Wow I can't believe the amount of issues I've ran into within 24hours of having this thing. I really don't know what to do...return it because it sounds like a faulty device (but all the issues are seemingly unrelated) or return and get another phone (is anyone else getting problems like I am?)
Sometimes phones have issues. I got one once that had no speakers or Mic inside... it happens lol
Try to go exchange it, and see if the next device gives you issues.. if not then you're good, if it does pick a different phone..
Do it soon though, most carriers only have a 14 day exchange period, and then after that will charge you all sorts of fees and try to fix your phone rather than just giving you a new one....
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
thefunkygibbon said:
Got it charging again by pushing the red button near sim slot for a couple seconds.
Just had another issue with SD card not being recognised after I removed another (/safely) had to reboot again using power plus vol up as it stuck on the shutdown logo when I tried to power down'...
Wow I can't believe the amount of issues I've ran into within 24hours of having this thing. I really don't know what to do...return it because it sounds like a faulty device (but all the issues are seemingly unrelated) or return and get another phone (is anyone else getting problems like I am?)
Click to expand...
Click to collapse
sounds like a similar problem I had with my 64gb SD card - as I mentioned above remove all cards then start from there - a reflash of the firmware might help also
thefunkygibbon said:
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
Click to expand...
Click to collapse
Something happened to mine with Youtube too. I'd started a video and paused it on a frame for comparison with another screen. While I was setting the other phone up, the screen on Z1 timed out. I pressed power, the screen come on and flickered, then went black!
Power and both volume keys function the same as the red button under the flap. I wasn't able to reproduce the bug.
LadFromWales85 said:
Something happened to mine with Youtube too. I'd started a video and paused it on a frame for comparison with another screen. While I was setting the other phone up, the screen on Z1 timed out. I pressed power, the screen come on and flickered, then went black!
Power and both volume keys function the same as the red button under the flap. I wasn't able to reproduce the bug.
Click to expand...
Click to collapse
yeah i've been trying to reproduce it and failing to. very odd. maybe its something to do with the first time you use youtube and do something specific?
gunna phone o2 up tomorrow and see what they say about all my issues. seems to have been fine this last 24 hours though and in their eyes that is prob reason enough not to issue a replacement.
I've had mine since Monday and this happened to me yesterday. I was troubleshooting sending MMS with T-Mobile tech support (not a phone issue as it was happening on previous phones too) and had to restart the phone several times. I noticed upon restarting that the backlight seemed to be on but the phone was not booting up. Had to perform several hard resets (both with the red reset button as well as the power/volume up buttons) before it FINALLY rebooted and stayed on. While trying to figure this out I ran a Google search to see if others were having this problem. One solution was to make sure the backlight option is checked. I had been messing with settings the night before and must have unchecked it. Since I rechecked it I haven't had the same issue.