Related
Dear Geeks,
I need your urgent help/advice. i'm three weeks far to my wedding and have a lot of troubles to handle, of course i need this phone.
let me describe the matter i have.
My nexus s is not booting, not starting, nothing.
what i did?
Last night, power button stopped working. I have experienced this 4-5 months ago. I don't know why, the problem has been solved by itself after few days later. i did nothing at those days. the power button came back. (as to my opinion, this is happening due to software problem) Anyway, i have used the market and installed ''fix power button'' application to use volume buttons for opening the screen.
I slept and when i woke up, i saw that phone needs to be charged but i waited. there was %11 something. i tried to handle the power button, pressed many times on it, thought that it may come back again same as 4-5 months ago it happened.
I removed battery and replaced again. i tried this many times. removed, replaced, used the usb cable via AC charger and phone started but there was no result. power button still was not working.
i thought that if the battery runs out, and then, when i charge the phone, maybe this matter may be solved. (ok this was stupid idea)
phone started to charge. when i plug the usb cable, phone was booting and displaying the google and animation and later it was ok to use.
meanwhile i keep on removing battery and replacing battery while the usb cable connected. but when phone starts to boot, i removed battery and replaced again. phone was ok, it was booting. few times it was booting.
but baaaam.
it is now not starting not booting, nothing.
now, when i replace the battery, phone is getting hot, especially sim-card area. i m removing the battery and connecting the usb. same again phone is getting hot, same sim-card area again.
i have waited enough not to connect the battery or usb charging cable. but no result.
what can i do now? what are your opinions?
my opinions/guess:
-i am using 3500 mah lithium polymere battery. maybe the battery died. i m using that battery more than 1 year, around 15 months. i dont turn off wi-fi so i m charging phone everyday.
- phone crashed during booting. and now the phone is totally brick.(i dont wanna believe this, this phone can be usable, believe me i feel it i think whatever happens, this phone can be usable via software installing or rooting... of course if you dont throw it towards a wall etc.)
by the way, my phone was not rooted. no time to root these days. and of course the phone was not starting.
what is your idea? what happened phone? what should i do?
if you reply, i will be appreciated.
A big advice for people reading this, dont remove the battery when your phone is booting.
I hope someone has a solution, since I have the same probelm...
I searched everything and tried every tool in this forum, but no success...
use search button, there is tens of similar threads...
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button
same thing has happened to me since updating from JB. Just past one year warranty too lol!
greg2826 said:
use search button, there is tens of similar threads...
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button
Click to expand...
Click to collapse
Actually, it was power button failure issue but now, i believe it is not.
But thanks i will try it.
captainirmak said:
Actually, it was power button failure issue but now, i believe it is not.
But thanks i will try it.
Click to expand...
Click to collapse
what is ur theory then?
u might find something here as well http://forum.xda-developers.com/showthread.php?t=1504501&highlight=power+button+conspiracy
greg2826 said:
use search button, there is tens of similar threads...
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button
Click to expand...
Click to collapse
dude, unfortunately those solutions not working on my device.
when i connect charger and i replace the battery, within seconds phone boots itself without power button. it should be this way. removing and replacing the battery helped me to start to boot.
i sense this case a bit different from that solutions.
i need to try with a different battery. my wife has nexus s also. she is very lucky she has no problems i have experienced so far. i will try with her battery.
i think there is a matter with mainboard.
by the way i forgot to say that i dropped my phone last evening. just after then phone was acting that i'm pressing long onto power button. and power button finally stopped working when i remove the battery.
i think this is happened because of dropping the phone from my belly high.
but the last thing i have done which removing the battery while the phone is booting, i wish, i should not have done. i could use it without the power button.
captainirmak said:
dude, unfortunately those solutions not working on my device.
when i connect charger and i replace the battery, within seconds phone boots itself without power button. it should be this way. removing and replacing the battery helped me to start to boot.
i sense this case a bit different from that solutions.
i need to try with a different battery. my wife has nexus s also. she is very lucky she has no problems i have experienced so far. i will try with her battery.
i think there is a matter with mainboard.
by the way i forgot to say that i dropped my phone last evening. just after then phone was acting that i'm pressing long onto power button. and power button finally stopped working when i remove the battery.
i think this is happened because of dropping the phone from my belly high.
but the last thing i have done which removing the battery while the phone is booting, i wish, i should not have done. i could use it without the power button.
Click to expand...
Click to collapse
If you have not rooted your device, you should have you warranty, right? Take the phone back to the carrier, and tell them about your problem. o.o Sorry, I'm of no help, but you're in a horrible situation. Wanted to at least give a little help.
Same exact problem here.
2nd of August - mom's phone turned of and just would not boot or prompt at all. The modem heats up when power is turned on or connected.
Tried
The unbrickable methods (but the computer would not detect the device in any form)
A JTAG - I was able to write the recovery and bootloader - assembled the phone and it just won't boot or prompt
Need to try
Another battery to see if it solves the issue.
Removing the xOM5 resistor and converting to a development S5PC110
Tried another battery - no luck
Did the resistor removal and converted to a dev board - Unbrickable now detects the board!
trying to get the device into fastboot - will update
ru1dev said:
Same exact problem here.
2nd of August - mom's phone turned of and just would not boot or prompt at all. The modem heats up when power is turned on or connected.
Tried
The unbrickable methods (but the computer would not detect the device in any form)
A JTAG - I was able to write the recovery and bootloader - assembled the phone and it just won't boot or prompt
Need to try
Another battery to see if it solves the issue.
Removing the xOM5 resistor and converting to a development S5PC110
Click to expand...
Click to collapse
I had the same problem few months ago. Power button had died. While I was able to boot with remove battery and connect to charger option and I was rooted. But after a week I decided to take the phone to Samsung service center to get the power button replaced. My phone did not have warranty. Samsung took few hours to get the power button replaced and it costed me about $7. I think that's the easiest method. They did not have a stock of I9020 power button, so they fixed a I9023 power button.
Any update? I'm curious to see if you get it working. Had the same happen to my NS a few days ago and would like to see if I can get it going again so I can give it to my stepson.
Sent from my Galaxy Nexus using xda premium
I've given nexus s to samsung service. Actually, power button may be handled by replacing with new one, but with no hope, it will not come back when i read messages about mainboard failure. I will update news whenever it's possible.
we'll see.
I would like to hope it is kind of software matter.
Pls god give my nexus s back, i got extended 3500mah battery.
grrr....
anshumandash said:
I had the same problem few months ago. Power button had died. While I was able to boot with remove battery and connect to charger option and I was rooted. But after a week I decided to take the phone to Samsung service center to get the power button replaced. My phone did not have warranty. Samsung took few hours to get the power button replaced and it costed me about $7. I think that's the easiest method. They did not have a stock of I9020 power button, so they fixed a I9023 power button.
Click to expand...
Click to collapse
So with the hardware mod - instead of selecting Nexus S -> I tied the Galaxy S in unbrickable - first time I've seen the screen alive! - puts the phone into download mode and I can disconnect from the usb and it stays in download mode! .. when i tried to flash odin I get a "There is no PIT partition" error -> this ofcourse is with re-partition and bootloader update UNCHECKED
When I tried Heimdall it wouldnt let me flash without a pit file. So trying Heimdall 1.1.1 - I get Failed to Access device Error: -3
Any chance some one with an i9020T can do me a huge favor? Use Heimdall 1.3.2 - download your PIT file and upload it here?
reaching for string ends out here :/
@ru1dev
i`m in the exact situation right now...
did you solved your problem?
jokkergsm said:
@ru1dev
i`m in the exact situation right now...
did you solved your problem?
Click to expand...
Click to collapse
The power button had to be replaced. I shorted the connection when ever I had to press the power button during the boot sequence. That's how I fixed mine.
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
devmage said:
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
Click to expand...
Click to collapse
Well the good news is that you aren't bricked, if the phone gives any signs of life then you are not bricked. Have you always installed SuperSu updates through recovery? I always select I believe it says "normal" and let it do it's thing and until now (knock on wood) haven't had any issues updating binaries that way. I would go back to stock and see if your problems continue or flash the previous SuperSu and see if it still happens.
devmage said:
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
Click to expand...
Click to collapse
Make sure you aren't trying to power it on while still plugged in. The charging animation bug really rears its ugly head sometimes when trying to do that.
The Stig 04 said:
Well the good news is that you aren't bricked, if the phone gives any signs of life then you are not bricked. Have you always installed SuperSu updates through recovery? I always select I believe it says "normal" and let it do it's thing and until now (knock on wood) haven't had any issues updating binaries that way. I would go back to stock and see if your problems continue or flash the previous SuperSu and see if it still happens.
Click to expand...
Click to collapse
I would love to go back to stock if I could get the device to turn on.
This was the first SuperSU update that I can remember having installed, so yes, I've always installed through recovery. The update even prompted me that, for HTC devices, better luck is had via updates through recovery.
dottat said:
Make sure you aren't trying to power it on while still plugged in. The charging animation bug really rears its ugly head sometimes when trying to do that.
Click to expand...
Click to collapse
I'm unaware of this bug. When disconnected, the device still refuses to reboot via any of the usual reboot patterns (Power, Power + Vol Up, Power + Vol Down, Power + both Vols).
devmage said:
I'm unaware of this bug. When disconnected, the device still refuses to reboot via any of the usual reboot patterns (Power, Power + Vol Up, Power + Vol Down, Power + both Vols).
Click to expand...
Click to collapse
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
dottat said:
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
Click to expand...
Click to collapse
Power light does not blink at all on connection. This is true both when connecting to a USB power adapter and to the computer.
My computer does not recognize a device. ADB does not report that a device is connected. Also, I use a Mac, so System Information does not report any USB device being connected. For comparison, I tried with my wife's Samsung S5, and it reported correctly in both places, so I know the cable and computer are working correctly here too.
devmage said:
Power light does not blink at all on connection. This is true both when connecting to a USB power adapter and to the computer.
My computer does not recognize a device. ADB does not report that a device is connected. Also, I use a Mac, so System Information does not report any USB device being connected. For comparison, I tried with my wife's Samsung S5, and it reported correctly in both places, so I know the cable and computer are working correctly here too.
Click to expand...
Click to collapse
Can you check dmesg on your Mac and see if you have any qualcomm devices show up near the end of the file? . Plug the phone in right before running the command.
dottat said:
Can you check dmesg on your Mac and see if you have any qualcomm devices show up near the end of the file? . Plug the phone in right before running the command.
Click to expand...
Click to collapse
Nothing from Qualcomm, nor anything related, upon plugging in the phone.
Using
Code:
sudo watch 'dmesg | tail -n 15'
(OS X requires dmesg be accessed with sudo), I saw the following come up upon plugging in the S5 mentioned before:
Code:
USBMSC Identifier (non-unique): 0x00000000 0x4e8 0x685b 0x232, 2
With the same watch in place, I saw no output at all for the M8.
devmage said:
Nothing from Qualcomm, nor anything related, upon plugging in the phone.
Using
Code:
sudo watch 'dmesg | tail -n 15'
(OS X requires dmesg be accessed with sudo), I saw the following come up upon plugging in the S5 mentioned before:
Code:
USBMSC Identifier (non-unique): 0x00000000 0x4e8 0x685b 0x232, 2
With the same watch in place, I saw no output at all for the M8.
Click to expand...
Click to collapse
I would suggest warranty route through HTC. You have got a brick.
dottat said:
I would suggest warranty route through HTC. You have got a brick.
Click to expand...
Click to collapse
That is my fear. Thank you for your help.
dottat said:
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
Click to expand...
Click to collapse
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
TIA for any help!
Matt
sigmaxaa said:
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
Thanks TIA for any help!
Matt
Click to expand...
Click to collapse
I'm afraid that I won't be of much help going forward. I sent in the device on a warranty claim.
I will add that, in the day or so following my posts here, I plugged the phone in again and to my surprise it began taking a charge again. I let it charge for about an hour, and tried turning it on - remarkably, it came up normally. It was stable for about an hour more, and then froze and powered off as before, refusing to once again turn on.
I left it alone for another couple of days, during which time my replacement arrived, and tried again. It began taking charge, and I left it as such for a couple hours more. This time knowing that my stable time was limited, and with a replacement phone in hand, I immediately restored the phone to RUU stock and locked it.
Your problem seems different from mine, in that my device was outright refusing to even take power or turn on. Best of luck to you, though!
Thanks for the info...I appreciate the response. I'm hoping that there's something that can be done but after 2 hours, trying every trick I could find via
Google with nothing to show for it, I'm keeping fingers crossed that it's something simple I'm missing. If I could just get into the dang bootloader!
Thanks again!
Sent from my SM-P600 using XDA Free mobile app
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
sigmaxaa said:
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
TIA for any help!
Matt
Click to expand...
Click to collapse
To add to this, I've let the phone sit for about an hour, untouched, and now the green light is blinking like it does when there's a SMS/email. Pushing the power button doesn't do anything.
devmage said:
I'm afraid that I won't be of much help going forward. I sent in the device on a warranty claim.
I will add that, in the day or so following my posts here, I plugged the phone in again and to my surprise it began taking a charge again. I let it charge for about an hour, and tried turning it on - remarkably, it came up normally. It was stable for about an hour more, and then froze and powered off as before, refusing to once again turn on.
I left it alone for another couple of days, during which time my replacement arrived, and tried again. It began taking charge, and I left it as such for a couple hours more. This time knowing that my stable time was limited, and with a replacement phone in hand, I immediately restored the phone to RUU stock and locked it.
Your problem seems different from mine, in that my device was outright refusing to even take power or turn on. Best of luck to you, though!
Click to expand...
Click to collapse
For what it's worth for anyone that finds this info useful...can't take credit for this as I found it over in the One M8 forum. Thanks to @mpogr
I quote his post: "The problem was that my phone's screen was going blank after the normal boot screen, so I couldn't see when it gets turned off. I was simply pressing the Vol Up + Power for too long, so it would go into full reboot. I just measured the amount of time it was taking to do this (was ~12 seconds). So I pressed Vol Up + Power for ~10 secs, then released those and pressed Vol Down. That finally brought me into Fastboot.
I could have probably gotten the same result by pressing Vol Down + Power, however, the phone screen was blank all the time, so it was difficult to understand when I should have released the Power button to let it go into Fastboot."
I held Power/Vol Up for 10 seconds (as he described) and then let go and immediately held Vol Down only...after about 3 seconds, bootloader screen came up and I was able to get into recovery and restore a backup.
Hello,
Ive tried to look for a similar situation in other thread but each case is different so i open a new one.
This morning, when i took my idol 3 the screen did not switch off when pressing power button. I thought it was battery but when i plugged charger,nothing happened except the led is on continuously. I kept power button pressed for 10 seconds. The phone vibrates shortly but still a black screen, no sound and no reaction from the touch panel. Power+vol+ did not led me to my twrp recovery. What can i do now to get it work again? The phone is rooted with Rom Eu 4.2 from murigny64 and it is the first time i encounter this issu. Thanks in advance for helping me
Tonight i disconnected the battery for about 30min then connect it again. Then i tried to start in recovery: Just a vibration but no display and no sound. I unplugged/plugged the battery again and try to start. Same problem. What the hell could happen? Maybe a deffective hardware
Insist on boot ( normal or in to recovery with vol + and power).
That is a hardware brick.
Happened to me to some times, insist, it will unbrick
persona78 said:
Insist on boot ( normal or in to recovery with vol + and power).
That is a hardware brick.
Happened to me to some times, insist, it will unbrick
Click to expand...
Click to collapse
Hopelessly i tried to restart several times before you post your message. But im gonna try again.
I charged the phone all the night but nothing better and the phone is not detected on pc so no adb action possible.
Maybe the battery is dead...
nigloud said:
Hopelessly i tried to restart several times before you post your message. But im gonna try again.
I charged the phone all the night but nothing better and the phone is not detected on pc so no adb action possible.
Maybe the battery is dead...
Click to expand...
Click to collapse
Can be, can be to... To bad if is battery.
But still trying to boot, is very difficult to.
.
thank you for advise but it's still not working. I spend about 30 minutes trying different combination of button: power pressed until it vibrate, power+vol up, power+vol down, power+vol up & down, discontinuous press of power with charger and no charger....and so on. Its a complete failure.
If it is the battery, there was no sign of weakness before (short life, random shutoff, ....) . It happen suddenly: I lock my screen before sleeping and the next morning no way to switch it on again.
I thought I would avoid problems for long with a twrp recovery, a backup and adb tools on my pc.....but for hardware issues its useless.
How can I be sure it is battery before purchasing another one ?
nigloud said:
How can I be sure it is battery before purchasing another one ?
Click to expand...
Click to collapse
There is also possibility that your screen has been broken
Sent from my 6045I using Tapatalk
belkoo said:
There is also possibility that your screen has been broken
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
If it was the screen the touch panel would work and i could sense vibration when typing the pin code no?
The led bright continuously when i plug instead of flashing slowly as it used to do when charging. That why i think its battery.
...and when i start in recovery the phone is not detected on my pc
That's hardware brick. Don't give up, try to boot, normally or in recovery, keep trying it will boot.
Have you tried to open the phone and disconnect battery? Custom ROMs made me similar issue a few times.
jani0417 said:
Have you tried to open the phone and disconnect battery? Custom ROMs made me similar issue a few times.
Click to expand...
Click to collapse
Wtf idol 3 has non removable battery haha
Sent from my 6045I using Tapatalk
belkoo said:
Wtf idol 3 has non removable battery haha
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
Therefore the back can be dismantle and we can access battery and that s what i did.
Yes i disconnected it for several hours and pluged it again but it gave me the same result. And now it doesnt vibrate anymore when i keep the power button pressed a while.
I purchased a battery on internet and im waiting for delivery to test if im right or not. Il feedback about the test.
Anyway its nice from you to look for any solution. Thanks
nigloud said:
Therefore the back can be dismantle and we can access battery and that s what i did.
Yes i disconnected it for several hours and pluged it again but it gave me the same result. And now it doesnt vibrate anymore when i keep the power button pressed a while.
I purchased a battery on internet and im waiting for delivery to test if im right or not. Il feedback about the test.
Anyway its nice from you to look for any solution. Thanks
Click to expand...
Click to collapse
I guess you did everything properly, so just one thing: at first time when I did this, I choosed the wrong cable (which didn't 'reset' the phone), so I hope you pulled both out.
jani0417 said:
I guess you did everything properly, so just one thing: at first time when I did this, I choosed the wrong cable (which didn't 'reset' the phone), so I hope you pulled both out.
Click to expand...
Click to collapse
I think i choose the good connection: This is the one over the battery with 6 wires: 2 red, 2 white and 1 black (see picture attached). I just left it with a small screwdriver to disconnect.
nigloud said:
I think i choose the good connection: This is the one over the battery with 6 wires: 2 red, 2 white and 1 black (see picture attached). I just left it with a small screwdriver to disconnect.
Click to expand...
Click to collapse
Yep, that's it
Hello,
I received the new battery today.
So i unpacked it, i unplugged the old one and plugged the new one ...and guess what happened......the same bevahiour as with the old battery: when i press the button power, it vibrate but it doesnt start neither in recovery nor in normal mode.
I just precise that the new battery is charged at 50%........:crying:
So the problem is not the battery but it was the only thing i could test by myself before sending the phone to alcatel for repair.
Im still wondering what could happen to my idol 3: It had been woking perfectly for months and one morning with no warning, it refuse to switch on. Ok sorry for annoying us and hope it wont happen with yours.
I hope alacatel will apply the guarantee although the phone is rooted and bootloader unlocked....because its a hardware issue i think.
Hello,
Just to conclude. The phone got back from repair after 10 days. They have changed motherboard, battery and also the back that was damaged. Its a brand new phone .
Hi there, my google nexus 5 has completely dead. Yesterday i was using my phone and it shutdown itself. Now i'm not able to charge or turn on the phone. No bootloop, no logo, no sound, nothing... If i connect the phone to pc windows is not able to recognize the hardware, no windows sound, no bootloop on the phone, no life signal. There is any way to fix the problem? Thanks
Try opening the phone, disconnect the battery for a few minutes, reconnect battery, connect to a charger and look for a flashing red led. Don't try to turn on the phone during this process.
I opened the phone, when i connect a charger i can hear something like an imperceptible click noise... and the logic board become hot:crying:
I had this issue recently. The phone was not turning on like you mentioned.
I was able to enter recovery mode (hold power + volume down for few seconds)
Once in recovery I wiped cache. Now the phone turns on.
I still get sudden restarts with heavy use. But at least the phone turns on now.
I took the phone to a phone repair kiosk. He told me he had 3 customers complaining of similar issues with their Nexus 5 and that he was unable to fix it.
I'm with Rogers, latest firmware, stock, locked bootloader.
erryday said:
I had this issue recently. The phone was not turning on like you mentioned.
I was able to enter recovery mode (hold power + volume down for few seconds)
Once in recovery I wiped cache. Now the phone turns on.
I still get sudden restarts with heavy use. But at least the phone turns on now.
I took the phone to a phone repair kiosk. He told me he had 3 customers complaining of similar issues with their Nexus 5 and that he was unable to fix it.
I'm with Rogers, latest firmware, stock, locked bootloader.
Click to expand...
Click to collapse
one day we will discover google has been killing older phones with updates once pixel was released, lel. jkjk
I just talked to LG Customer service. He told me the whole logic board needs to be replaced. Which would set me back $150+tax and downgrade my storage to 16Gb. No thanks.
I was hoping for a workaround, like installing a custom kernel with specific settings.
I have already tried factory reset, switching to LineageOS, removing sim card. Nothing helped.
Underclocking with Elemental X Kernel seems to be the best workaround so far.
Story
- Upgraded my Pixel to Oreo 2 weeks ago.
- 1st instance: Was doing a file transfer from iPhone to Pixel of photos via USB-C to lightning cable. Suddenly phone freezes. I restart and can't boot OS at all. Recovery mode was not working (display/text of recovery mode messed up). Files unrecoverable.
- Phone RMA'd. Replaced with refurbished Pixel.
- 2nd instance: Was just driving. Listening to music on car's bluetooth. Music stops because phone froze. I restart the phone and the display shows nothing at all. Multiple tries to reboot and enter recovery mode and nothing shows up on display. I just get haptic feedback when I press and hold power button.
- Currently outside the US and won't be back until December. Google can't honor warranty and send a phone to me outside the US. (Phone bought from Google Store in US and RMA'd while I was in US).
Ideas? Anyone else experienced this with Oreo?
sounds weird but plug it into the charger and let it sit over night. The next day unplug it for an hour then try to turn it on
eqbirvin said:
sounds weird but plug it into the charger and let it sit over night. The next day unplug it for an hour then try to turn it on
Click to expand...
Click to collapse
Thanks for the suggestion. No luck though. It's non-responsive. The only feedback I get are vibrations when I try to enter recovery mode but nothing shows up on the display. It isn't even detected on USB by a computer...
I faced a similar issue a few months ago when I woke up in the morning and my phone was unresponsive. It wasn't plugged in but I went to bed with more than enough battery to make it through the night. I would get one short vibration after ~20 sec of power + voldown and nothing else.
An online chat with Google support got me an RMA with few questions asked.
If you can feel the haptic feedback that means the OS is powered or if not then at least kernel is responding to the taps. Try and install the adb and fastboot drives manually in PC or you can give Skipsoft Toolkit a try. Once done, you can manually flash the factory image on it.
IMHO, such frozen screen and bootloops are related to hardware issues - generally loose connectors. Rather waiting for December you can try your luck with above.
Good Luck!
cntryby429 said:
I faced a similar issue a few months ago when I woke up in the morning and my phone was unresponsive. It wasn't plugged in but I went to bed with more than enough battery to make it through the night. I would get one short vibration after ~20 sec of power + voldown and nothing else.
An online chat with Google support got me an RMA with few questions asked.
Click to expand...
Click to collapse
Thanks. My problem is I'm currently out of the US and won't be back until December. I was able to RMA the first one without any problems because I was still in the US when it happened.
mannunikhil said:
If you can feel the haptic feedback that means the OS is powered or if not then at least kernel is responding to the taps. Try and install the adb and fastboot drives manually in PC or you can give Skipsoft Toolkit a try. Once done, you can manually flash the factory image on it.
IMHO, such frozen screen and bootloops are related to hardware issues - generally loose connectors. Rather waiting for December you can try your luck with above.
Good Luck!
Click to expand...
Click to collapse
Thanks! I'm trying this right now. This needs USB debugging enabled though, right? I wasn't able to activate it on the 1-week-old Pixel yet
ricardo.ortuoste said:
Thanks! I'm trying this right now. This needs USB debugging enabled though, right? I wasn't able to activate it on the 1-week-old Pixel yet
Click to expand...
Click to collapse
you can refer to this link for to Enable USB debugging and this link to help Flash Factory image.
Hope this helps you.
Know anyone still in the states? Ship it to them.