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 !
Hey guys, im having a bit of a problem. My phone is shuting off on itself.
Everytime i turn it on, it boots up no problem, but when i hit the power button to turn the screen off, when i want to turn the screen on again by pressing the power button, the screen just goes deep blue, and turns off.
I haven't change anything on it for quite a few months now, so i'm not sure why this is happening. Im on Viper 3.5 i think or 3.7, using faux123 kernel, dont remember which version, but an old one with which i never had any troubles... rooted, s-on
Any ideas?
Thanks!
Coldsun15
PD: Logcat in the .rar file...was too big for .txt
Really?? No one??
Well, just for further info... my phone appeared to fix itself, since it stopped doing that weird thing for a couple of days, but now is back... nothing ever changed, no new apps, or settings or anything...
Any ideas welcome
Edit: Attaching new logcats...
coldsun15 said:
Well, just for further info... my phone appeared to fix itself, since it stopped doing that weird thing for a couple of days, but now is back... nothing ever changed, no new apps, or settings or anything...
Click to expand...
Click to collapse
I think your power button is broken (or you may have a related hardware issue). Nothing but a root app can reboot the phone, and I've never seen that happen by accident.
fenstre said:
I think your power button is broken (or you may have a related hardware issue). Nothing but a root app can reboot the phone, and I've never seen that happen by accident.
Click to expand...
Click to collapse
Yeah, i thought about it being hardware but something is off... i mean, if it where the power button, then i shouldnt be able to turn it on easily, or it wouldnt turn off the screen properly, nor would it just start working alright for a couple of days... plus, it didnt recieve any hits or anything during, before or after the problem.
I also thought it could be the screen, but when its on, it works perfectly, as on the first day...
But yeah, I'm not taking hardware problem out of the table...just seems unlikely to me...
Thanks for your answer!
Coldsun15
Edit: also, I just found out it doesnt actually restart...screen just turns dark blue, then it powers the screen off and it wont turn on when pressing power... but i know its on, because i can still hear notification sounds of incoming messages...
Edit2: Just tried same but instead of using power button, i used logo2sleep and home2wake kernel options, and did the on/off with them, and same result...dark blue screen then off and not turning on... so it cant be power button
Hi all!
First of all, I'm not sure if I'm doing everything right here, so excuse me if I'm doing something wrong
I'm new.
I've had my HTC One M7 from aliexpress.com for 2 weeks and 2 days now.
Have had great fun of it, nothing seemed wrong, was working perfectly. There were some rumours about an unofficial android-version that was put on this phone, which might be the problem..
Everytime I turn the phone screen on it thinks I hold/doubletap/tap/repeatedly tap the home button, and sometimes when I power it off it thinks I hold the volume down-button and takes a screenshot.. When I finally get to type my 4-digit pin code, it unlocks, goes to home screen, does the same again. Seems like my phone thinks I'm using the buttons..
I've changed settings (in a legit official way via Settings) of my home button to Hold for menu, Hold and swipe up for Google Search, and double-tap for recent apps..
Have tried factory reset twice, have tried rebooting it over and over, have tried almost anything.. I'm at the point of buying a new phone now, because I fear that HTC will not help me because it's an unofficial version of Android.. Any suggestions?
Everytime I open an app it just closes it and goes to home, sometimes before it does that it opens recent apps.. After that it just freezes and I can't touch it. Sometimes after waiting a couple of seconds, I can tap the screen and maybe it's fast enough to open for example WhatsApp, and then it just shuts off and does what I just stated.
Really weird!
I'm quite desperate. Could a custom ROM (Cyanogen or Android lollipop) fix this perhaps?
Please, help
Gr Patrick
ExcesusNL said:
Hi all!
First of all, I'm not sure if I'm doing everything right here, so excuse me if I'm doing something wrong
I'm new.
I've had my HTC One M7 from aliexpress.com for 2 weeks and 2 days now.
Have had great fun of it, nothing seemed wrong, was working perfectly. There were some rumours about an unofficial android-version that was put on this phone, which might be the problem..
Everytime I turn the phone screen on it thinks I hold/doubletap/tap/repeatedly tap the home button, and sometimes when I power it off it thinks I hold the volume down-button and takes a screenshot.. When I finally get to type my 4-digit pin code, it unlocks, goes to home screen, does the same again. Seems like my phone thinks I'm using the buttons..
I've changed settings (in a legit official way via Settings) of my home button to Hold for menu, Hold and swipe up for Google Search, and double-tap for recent apps..
Have tried factory reset twice, have tried rebooting it over and over, have tried almost anything.. I'm at the point of buying a new phone now, because I fear that HTC will not help me because it's an unofficial version of Android.. Any suggestions?
Everytime I open an app it just closes it and goes to home, sometimes before it does that it opens recent apps.. After that it just freezes and I can't touch it. Sometimes after waiting a couple of seconds, I can tap the screen and maybe it's fast enough to open for example WhatsApp, and then it just shuts off and does what I just stated.
Really weird!
I'm quite desperate. Could a custom ROM (Cyanogen or Android lollipop) fix this perhaps?
Please, help
Gr Patrick
Click to expand...
Click to collapse
This is purely a hardware issue. Your home button is somehow always in "on" position. Given it's a capacitive button, it could be the digitizer or a scratch on the home button area
donkeykong1 said:
This is purely a hardware issue. Your home button is somehow always in "on" position. Given it's a capacitive button, it could be the digitizer or a scratch on the home button area
Click to expand...
Click to collapse
Any idea on how to fix this?
This is somewhere about what I mean, read my reply also.
This might even be closer to what I mean.
Should I just send it back to HTC or can I fix this myself, with your heroic help?
ExcesusNL said:
Any idea on how to fix this?
This is somewhere about what I mean, read my reply also.
This might even be closer to what I mean.
Should I just send it back to HTC or can I fix this myself, with your heroic help?
Click to expand...
Click to collapse
Seems like just the thing I wrote. Considering it's a hardware issue you could replace the screen-digitizer assembly by yourself if you are familiar with that kind of work. I tried once on my old Desire and fried the motherboard, so I don't have cojones to do it [emoji6]
donkeykong1 said:
Seems like just the thing I wrote. Considering it's a hardware issue you could replace the screen-digitizer assembly by yourself if you are familiar with that kind of work. I tried once on my old Desire and fried the motherboard, so I don't have cojones to do it [emoji6]
Click to expand...
Click to collapse
Thanks for assisting me. I will bring it to a Chinese or turkish guy around here who will do it for cheap
Hi everyone I've got a big problem with my wife's Mi 5. After some minutes/hours of usage the touchscreen stops working and the only solution the make it work again is to reboot the phone (by keeping the power off button pressed).
I've tried some rom (MIUI stable, MIUI dev, Paranoid Android 7.3.0) but all of them have the same problem, someone has got the same issue?
I think it's not only an hardware problem because the touchscreen works most of the time... Any ideas?
I'm having the exact same problem with my wife's Mi5 too. I thought she was talking rubbish until I started using the phone full time over the past few weeks.
Symptoms:
Screen switches on and accepts one touch event.
Screen is then unresponsive to touch events.
All other buttons (home, power, volume) all work OK.
All functions work OK (calling, SMS, etc) via remote control (MyPhoneExplorer)
Screen then becomes responsive again after reboot
Tried so far:
Clearing dalvik/cache
Clean flash - using MiFlash and China dev ROM
Opened phone, cleaned all ZIF connections and reconnected.
It almost feels like something in the touch firmware or driver crashes and does not reconnect - as the phone is clearly usable save for the touch panel.
I'm going to ask Bruno/bgcngm and see if there's anything I can do to try and diagnose the issue.
kylemd said:
I'm having the exact same problem with my wife's Mi5 too. I thought she was talking rubbish until I started using the phone full time over the past few weeks.
Symptoms:
Screen switches on and accepts one touch event.
Screen is then unresponsive to touch events.
All other buttons (home, power, volume) all work OK.
All functions work OK (calling, SMS, etc) via remote control (MyPhoneExplorer)
Screen then becomes responsive again after reboot
Click to expand...
Click to collapse
In my case unresponsive screen to touch events, all phisical button works and the only option to make it works again is to reboot. I didn't try to use it with some "remote" control.
kylemd said:
Tried so far:
Clearing dalvik/cache
Clean flash - using MiFlash and China dev ROM
Opened phone, cleaned all ZIF connections and reconnected.
Click to expand...
Click to collapse
I didn't try to open the phone, but I installed all roms with TWRP and format data/wipe cache/dalvik before.
kylemd said:
It almost feels like something in the touch firmware or driver crashes and does not reconnect - as the phone is clearly usable save for the touch panel.
Click to expand...
Click to collapse
I also think that it's related with a software issue...
kylemd said:
I'm going to ask Bruno/bgcngm and see if there's anything I can do to try and diagnose the issue.
Click to expand...
Click to collapse
I don't know who is Bruno/bgcngm but I hope he/she'll find a solution.
If you need some other information or help I'll give you as much as I can.
Well on my old mi4c i had similar problem. I mean sometimes when i pressed power button and tried to unlock it screen didn't work. For me solution was simply to press power button again to turn off screen and then turn IT on. Maybe this will help u. Have u try that ?
Wysłane z mojego MI 5 przy użyciu Tapatalka
kylemd said:
It almost feels like something in the touch firmware or driver crashes and does not reconnect - as the phone is clearly usable save for the touch panel.
Click to expand...
Click to collapse
Do you think it's something related with Doze or standby? I think so because today (and yesterday and so on...) I wasn't able to turn off the wake up alarm (the phone was in standby with the screen off all night) with "the screen" but I have to force restart the phone with the button... and it's very annoying.
Maybe we can try with some Marshmallow ROM instead Nougat one.
Alberto
uremytoy said:
I mean sometimes when i pressed power button and tried to unlock it screen didn't work. For me solution was simply to press power button again to turn off screen and then turn IT on. Maybe this will help u. Have u try that ?
Click to expand...
Click to collapse
Yes I tried it, it's the first test that I did... but It doesn't work. I tried also to double tap home button and power button but nothing happend.
Alberto
I'm facing same issue.I've changed my display panels but it doesn't solve my problem.it is quite painfull.i don't know what should i do.
any update sir?
My MI 5 has a different issue. There is no response if I place the phone on the table, but it is fine if I held it. It seems the touch panel is only responsive when the sort of sensors that a human is holding the phone. I have no idea why it starts to happen in these weeks. This symptom happens even in TWRP, so I don't think it is related some particular ROM. Tried firmware 7.7.6 ~ 7.9.22 with no luck.
skip lock screen
Hi
I know I am late to the party, but just faced the same issue yesterday. To bypass the issue, follow the following steps
1. Restart your phone .
2. Enable developer options from about section in settings. (google enable developer options for specifics)
3. In developer options, there is an option to skip screen lock. Enable that.
4. Voila!!
Hope it will help other mi5 users..
Hi,
I had the same problem. I found this video and I tried to fix it. It worked pretty well. Bye
In a situation that I can't do any service for my Mi5 as of now - is this really loose cable thing ?
Can more folks confirm that this cable solution from above video works ?
exactly same symtoms :
Random screen freeze - only option is to reboot phone or phone goes rebooting randomly itself.