Related
Hi All,
I would like to describe something which I'm not sure if it is just me or a bug. There have been a few occasions where I have pressed the power button to put the phone to sleep and after a second, the screen turns back on again. I've tried to replicate it by maybe the way I have pressed it and it could have a residual effect on the button, thinking I want to turn it on again but I've not been successful. It just happens on and off.
Other than that, I love my HTC One X. Just like to find out if others do encounter this. Thanks! =)
erniechua said:
Hi All,
I would like to describe something which I'm not sure if it is just me or a bug. There have been a few occasions where I have pressed the power button to put the phone to sleep and after a second, the screen turns back on again. I've tried to replicate it by maybe the way I have pressed it and it could have a residual effect on the button, thinking I want to turn it on again but I've not been successful. It just happens on and off.
Other than that, I love my HTC One X. Just like to find out if others do encounter this. Thanks! =)
Click to expand...
Click to collapse
Thought it was just me, looks like it's a bug.
Same here, doesn't always happen
Same here, but happened only 3 or 4. Also i was unable to reproduce it on purpose.
Great, at least I'm not alone and it is not due to my way of pressing the power button. Hope HTC fixes this bug in the next update. Thanks all! =)
Me too!!!
same here
Mine does this too, also mines rooted with custom rom. I can replicate it if a press the screen lock button a few times it just shuts off, no shut down or any warning about what's its done. Do we know if this is a hardware or software fault as I guess my warranty is void after rooting.
Same here. I hope somebody can provide a solution.
I've had this before on my sensation but not on my HOX.. running cm10
Sent from Mars
Hmmm
Yup same ting happen to me I really thought it was me alone dat had dat problem and again I have a custom rom install, was even thinking or going back to original art ruu hoping it would solve the problem , the thing is its my back up fone incase of emergency I'm using my galaxy note 3 and now and them I keep hear a beep when I look the fone is on lol I just feel the one x has too many bugs
yeah.. same thing happened to me after i change my recovery to philz and rom to aosb.
Whenever i turn off my phone and charging, it will boot into recovery. after a while it will boot up itself as usual.
Never happened to me in stock recovery/rom... Not sure what is the cause
exquisite000 said:
yeah.. same thing happened to me after i change my recovery to philz and rom to aosb.
Whenever i turn off my phone and charging, it will boot into recovery. after a while it will boot up itself as usual.
Never happened to me in stock recovery/rom... Not sure what is the cause
Click to expand...
Click to collapse
man this is recovery future and it is kernel releated you can't turn off your phone when battery go to full will powered automatic and boot the rom.
Thant said:
man this is recovery future and it is kernel releated you can't turn off your phone when battery go to full will powered automatic and boot the rom.
Click to expand...
Click to collapse
Hi Thant,
Thanks for the info. But my battery doesn't even full or almost full. Even when my battery is only 8% left it will boot up automatically.
i wish they have option to turn the feature off..
Hi,
I'm sorry if this has already been answered I just can't find it.
My Wildfire's screen froze a couple of times, then the last time I removed the battery and reinserted it.
When I tried to power back up I got the vibrate but nothing on the screen, so I repeated a couple of times with no luck.
I then tried the Hboot method (Hold vol - and power) and I got the Hboot on, but when I tried to navigate using the volume buttons nothing happened, so removed battery and tried to repeat, I couldn't get back to Hboot. I have only been able to get the Hboot screen that one time.
When I power up, I get 1 vibrate and nothing on screen.
When I hold volume + and power button, I get three vibrates and the green light comes on.
When I hold volume - and power I don't get any vibrates, unless I remove the volume - then the power button but still only one vibrate.
I've tried installing the CyanogenMod but no luck.
Is there anything that can be done to save my Wildfire?
Thanks in advance for any help!
Seems like you're in Qualcomm Diagnostic mode. Though I don't remember the solution, some Googling might help
Sent from my HTC One S using Tapatalk 2
Any help please
I've tried the method stated on this forum but with no luck.
Does anyone have a suggestion?
Thanks!
--- EDIT ---
So you wrote your question again in the "Wildfire S" (Marvel) Forums - in this case the much more important question would be: what phone are you talking about? A Wildfire (Buzz) or a "Wildfire S" (Marvel). Despite the name those have almost nothing in common - they are totally different devices
--- EDIT ---
I'll answer in this thread although you opened another one in Q&A.
You haven't been too specific with your problem but sometimes it helps to have all the details
So here we go:
a) did the phone work correct (besides the freezes) before you took out the battery?
b) is your WF rooted & s-off?
c) which ROM?
d)
When I hold volume + and power button, I get three vibrates and the green light comes on
Click to expand...
Click to collapse
does this happen when connected to PC or charger or not
e)
When I hold volume - and power I don't get any vibrates, unless I remove the volume
Click to expand...
Click to collapse
did you hold both at least 5-10 secs or so?
f)
I've tried installing the CyanogenMod but no luck
Click to expand...
Click to collapse
you mean after your problem occured? How did you do that?
Believe me: the more details you provide the more likely someone might have a solution or at least an idea what's going on
OK, sorry for the lack of info!
My phone is a Wildfire, not a WildfireS.
A: Yes, was working.
B: No, never needed to.
C: Not sure, never kept a record of it. It's one of the first models though if that helps.
D: This happens without USB cord attached. When the USB cord is attached I pull the battery and the green light stays on.
E: Yes, I've tried this for over 10secs before.
F: Yes, after blank screen. I installed on SD card and followed the directions. Bare in mind, I cant set Debug or the charge only setting.
Thanks!
stefan2519 said:
OK, sorry for the lack of info!
My phone is a Wildfire, not a WildfireS
Click to expand...
Click to collapse
ok, you should mention it in the Marvel forums, too, to avoid misunderstandings At least you're in the right forum here.
B: No, never needed to.
Click to expand...
Click to collapse
That's what I thought. In this case you won't be able to flash any other ROM - you could just do the usual upgrades by HTC
This doesn't sound to me to be a minor problem (but probably someone else might correct me here) - nevertheless - just to make sure: have you tried to do a hard factory reset following the HTC user guide?
- With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button (instead of holding it)
if this boots your phone up:
- Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
- Press VOLUME DOWN to select CLEAR STORAGE, and then press POWER.
- Press VOLUME UP to start the factory reset
(errm and yes: this will delete all your user data, of course...)
Click to expand...
Click to collapse
But I assume you have done that anyway - did you try to connect your phone to the PC (HTC drivers installed, of course)?
How about charging - does the phone seem to behave normal - i.e. if you keep it from charging for a few hrs does it show the red LED for charging mode and the green one for being fully charged?
That's pretty much all I could suggest from scratch. - Hopefully someone else with a good idea will step in here :fingers-crossed:
OK, still have the Wildfire with the annoying blank screen.
Does anyone have any suggestions on a fix?
Thanks!
stefan2519 said:
OK, still have the Wildfire with the annoying blank screen.
Does anyone have any suggestions on a fix?
Thanks!
Click to expand...
Click to collapse
besides the suggestion of the Qualcomm diagnostic mode (no I don't know anything about that): did you try to power up without the sdcard, yet?
Furthermore I slightly remember that you could do a factory reset using a key combination - but I'm not sure about it.
Same goes for a RUU. Are you able to connect to the phone with the PC?
Really just random guessing - hard if no error messages appear...
Yes, tried with the SD card.
Because I can't see the screen I tried it loads of times, all with different combinations.
I can't get any vibrate from volume down + long hold power.
I will only get a vibrate from volume down + short hold power.
What would be ideal if there's a way to use ODIN PC to flash a new ROM, well that's what I think it is, faulty ROM?
Thanks!
stefan2519 said:
Yes, tried with the SD card.
Because I can't see the screen I tried it loads of times, all with different combinations.
I can't get any vibrate from volume down + long hold power.
I will only get a vibrate from volume down + short hold power.
What would be ideal if there's a way to use ODIN PC to flash a new ROM, well that's what I think it is, faulty ROM?
Thanks!
Click to expand...
Click to collapse
really hard to say as there's not a little information what's going on. What if just the screen is dead? have you tried to wait after boot and insert your pin after a while (I mean try to guess where the numbers might be) and call your number?
Why anyone want's to use ODIN on non-samsung?!
ODIN is purely just for SAMSUNG products
If you have warranty.. put it to service centre.. they will fix it
Need hard reset power off your phone press volume DOWN and power. YOU WILL FIX IT EASYLI.
Sent from my HTC Wildfire using xda premium
Hey there!
I'm bumping this because I have the same problem and creating a new thread seemed more bad to me.
Anyway, I'll start from the beginning.
I found out my battery was swollen 5 days ago. It's probably because of my charging habits. My battery life have shortened everyday this 5 days. Yesterday morning I wiped my battery stats to get a better battery life. When I was back home my phone's battery has depleted while I was listening to music.
I came to home, plugged my phone to charge and waited 15 mins to get it charged a bit to open. When I tried to open it, it vibrated but the "green htc text on white background" screen didn't come up. The screen wasn't working. I tried what is said before in this tried. Once I got managed to see the bootloader but the volume keys weren't working (as above) After some moments of rage, my brother offered to test the touch, I opened the phone, (as I dont have a PIN) we waited for some minutes and then he called me. I mimiced the answering gestured and boom, I could talk with my brother.
I bought a new screen as I think screen is broken. But it could be because mainboards screen part is damaged (probably because of my faulty battery, voltage wavings etc.) or something completely different.
Please guys help me. I can't buy a new phone atm so I have to fix this
zephyri-xr said:
Hey there!
I'm bumping this because I have the same problem and creating a new thread seemed more bad to me.
Anyway, I'll start from the beginning.
I found out my battery was swollen 5 days ago. It's probably because of my charging habits. My battery life have shortened everyday this 5 days. Yesterday morning I wiped my battery stats to get a better battery life. When I was back home my phone's battery has depleted while I was listening to music.
I came to home, plugged my phone to charge and waited 15 mins to get it charged a bit to open. When I tried to open it, it vibrated but the "green htc text on white background" screen didn't come up. The screen wasn't working. I tried what is said before in this tried. Once I got managed to see the bootloader but the volume keys weren't working (as above) After some moments of rage, my brother offered to test the touch, I opened the phone, (as I dont have a PIN) we waited for some minutes and then he called me. I mimiced the answering gestured and boom, I could talk with my brother.
I bought a new screen as I think screen is broken. But it could be because mainboards screen part is damaged (probably because of my faulty battery, voltage wavings etc.) or something completely different.
Please guys help me. I can't buy a new phone atm so I have to fix this
Click to expand...
Click to collapse
Ouch sounds like a rough one :/ OK so you have no visual, but do have touch and audio? Are you s-off or s-on? You could try to "blind feed" the rom.zip of a ruu to the bootloader to try restore it. But it may well be that your battery has killed the screen. Have you ordered a new battery?
tapped out from my sexy sensation XE
heavy_metal_man said:
Ouch sounds like a rough one :/ OK so you have no visual, but do have touch and audio? Are you s-off or s-on? You could try to "blind feed" the rom.zip of a ruu to the bootloader to try restore it. But it may well be that your battery has killed the screen. Have you ordered a new battery?
tapped out from my sexy sensation XE
Click to expand...
Click to collapse
I'm S-OFF. I had it written in my old sig.
I too think that it was the battery that killed the screen. Ordered both a screen and a battery but they won't be coming before 20 days at least. Damn you China, why you have to be that far.
Anyhoo, I can't get to the bootloader anymore. Or I think I can't get it. I once managed to get it but volume buttons weren't working. After that in every try I couln't see the bootloader screen. But you're right. When I can't see the bootloader, it doesn't mean I don't get the screen. I could do it with a fellow's help. But only after a few days. I'm getting a surgery in 10 hours. Can't really care about my phone right now
zephyri-xr said:
I'm S-OFF. I had it written in my old sig.
I too think that it was the battery that killed the screen. Ordered both a screen and a battery but they won't be coming before 20 days at least. Damn you China, why you have to be that far.
Anyhoo, I can't get to the bootloader anymore. Or I think I can't get it. I once managed to get it but volume buttons weren't working. After that in every try I couln't see the bootloader screen. But you're right. When I can't see the bootloader, it doesn't mean I don't get the screen. I could do it with a fellow's help. But only after a few days. I'm getting a surgery in 10 hours. Can't really care about my phone right now
Click to expand...
Click to collapse
As always man look after your self, then your family and friends, then your tec
Damn china indeed well I believe I know the blind flash procedure so hit this thread when you are better and will will rock on
tapped out from my sexy sensation XE
heavy_metal_man said:
As always man look after your self, then your family and friends, then your tec
Damn china indeed well I believe I know the blind flash procedure so hit this thread when you are better and will will rock on
tapped out from my sexy sensation XE
Click to expand...
Click to collapse
Hey I'm back
First I have to ask, do you get a vibration feedback when you are getting into bootloader by VolDown + Power buttons?
zephyri-xr said:
Hey I'm back
First I have to ask, do you get a vibration feedback when you are getting into bootloader by VolDown + Power buttons?
Click to expand...
Click to collapse
I don't think so :-\ it just depends. If its going to do it standardly then it will go once, if it goes 3 or 5 times your in trouble...
Tapped out from my sexy nexus 7
heavy_metal_man said:
I don't think so :-\ it just depends. If its going to do it standardly then it will go once, if it goes 3 or 5 times your in trouble...
Tapped out from my sexy nexus 7
Click to expand...
Click to collapse
I'm just not sure I can get into bootloader. When I Vol- + Power no vibration, no light on softkeys nothing.
There is no vibration when going to bootloader.
I have been following the CM10 preview for quite sometime and, when it was needed, would do a clean install from the recovery.
The most recent build 8/12 I flashed without a clean install and was having some random restarts.
When I tried to call someone it stayed at the call screen and did not make any sounds.
After a couple seconds the screen went black(I thought another random restart) and will not power back on.
When I hold the power button for 2 seconds it will vibrate and the screen will stay black.
I've tried entering recovery mode and download mode but nothing seems to work.
I planned on when I got home doing a clean install and starting fresh but it seems I might be too late.
Is this a brick? Can it be fixed? and what other information is needed? Open to all constructive suggestions.
CWM Recovery
CM10 Preview Build 8/12
Perfect Finale said:
I have been following the CM10 preview for quite sometime and, when it was needed, would do a clean install from the recovery.
The most recent build 8/12 I flashed without a clean install and was having some random restarts.
When I tried to call someone it stayed at the call screen and did not make any sounds.
After a couple seconds the screen went black(I thought another random restart) and will not power back on.
When I hold the power button for 2 seconds it will vibrate and the screen will stay black.
I've tried entering recovery mode and download mode but nothing seems to work.
I planned on when I got home doing a clean install and starting fresh but it seems I might be too late.
Is this a brick? Can it be fixed? and what other information is needed? Open to all constructive suggestions.
CWM Recovery
CM10 Preview Build 8/12
Click to expand...
Click to collapse
Maybe your screen died?
Does it power on without the display or does it try to power on but doesn't?
Sometimes it IS recognizable by ODIN but there is no display, try that.
it all that fails, then you MIGHT have a brick on your hands, which would be very unfortunate.
but give it a try
Wolfbeef123 said:
Maybe your screen died?
Does it power on without the display or does it try to power on but doesn't?
Sometimes it IS recognizable by ODIN but there is no display, try that.
it all that fails, then you MIGHT have a brick on your hands, which would be very unfortunate.
but give it a try
Click to expand...
Click to collapse
No the screen doesnt power on at all. I hold the power button and it vibrates like it would start up.
I havent tried it ODIN yet ill edit when I do. Ill also try to leave the battery out for a couple hours and try it.
Perfect Finale said:
No the screen doesnt power on at all. I hold the power button and it vibrates like it would start up.
I havent tried it ODIN yet ill edit when I do. Ill also try to leave the battery out for a couple hours and try it.
Click to expand...
Click to collapse
yeah go ahead and report back what happened.
Once on my gnex it wouldnt power on but it was still recognizable by ODIN
sounds like a dead battery
Noticed that build of cm10 actin weird as well. That bein said this issue sounds like the battery is dead, not the screen. I would try. To plug it in for a bit. Bet it sits and just vibrates over and over. That how u no the battery is dead. I hate it. That bein said its not bricked
This happened to me as well they plugging it into ur charger and holding the power button if that doesn't work remove the battery for a few and then pop it back it and to to boot into recovery I that my phone was dead as well.
Sent from my SPH-L710 using xda app-developers app
Hi All
Noticed that the top inch or so of my screen becomes unresponsive from time to time. So I cannot pull down the notifications or menu. Also if I try to do anything else (call, text, access apps etc) it does not respond.
A restart seems to sort it out but none the less it is annoying and I would like to know if there is something I can do to sort it out?
Thanks for reading
Is there any type of screen protector installed? Please ensure the firmware is updated to the latest version. Please try booting in safe mode to see if possibly there is a 3rd party app causing the issue. Please see the following for safe boot http://www.asus.com/us/support/FAQ/1005163/ If problem still exists then we recommend performing a hardware reset including cache wipe partition. Please see the following: http://www.asus.com/us/support/FAQ/1011956/
Sincerely
ASUS_USA
[email protected]
I do have a screen protector but I do not think it is that as it happens randomly and rebooting it fixes it.
When I tried to boot into recovery so that I can clear the cache I also get an error, basically the open droid on his back with the word error so I cannot even boot into recovery.
PJBXDA said:
I do have a screen protector but I do not think it is that as it happens randomly and rebooting it fixes it.
When I tried to boot into recovery so that I can clear the cache I also get an error, basically the open droid on his back with the word error so I cannot even boot into recovery.
Click to expand...
Click to collapse
When you see the open droid, Do the following.
Press Power (Hold), Press Volume Up and leave Volume Up.
You will enter recovery.
I think it is a hardware issue.
But still, try wiping cache and if possible do a factory reset (After Backup). Do not install any apps for a couple of days and see if the problem reoccurs
Edit:
ASUS Zenfone 2 64GB 3.2GHz
Android 5.0
O2 Network
Click to expand...
Click to collapse
Hey, Your Signature says you have a 3.2 Ghz Zenfone. Damn It, I too should have bought that one.:laugh: (Correct It)
[email protected] said:
When you see the open droid, Do the following.
Press Power (Hold), Press Volume Up and leave Volume Up.
You will enter recovery.
I think it is a hardware issue.
But still, try wiping cache and if possible do a factory reset (After Backup). Do not install any apps for a couple of days and see if the problem reoccurs
Click to expand...
Click to collapse
Thanks but that does not work. When I boot using power and volume up, I get the open droid and the boot options. I choose recovery and it boots but then I get an open droid with a red triangle with an '!' inside coming from his belly and the message 'Error!' underneath. From there the only thing that seems to work is holding the power button for about 10 seconds and that then turns the device off.
PJBXDA said:
Thanks but that does not work. When I boot using power and volume up, I get the open droid and the boot options. I choose recovery and it boots but then I get an open droid with a red triangle with an '!' inside coming from his belly and the message 'Error!' underneath. From there the only thing that seems to work is holding the power button for about 10 seconds and that then turns the device off.
Click to expand...
Click to collapse
THERE YOU HAVE TO DO THE FOLLOWING:
Press Power + Volume up
And release only volume up while holding the power button. And once you see recovery, release power button too.
I find this occurs onmine sometimes too, the dead screen, not the unable to get to recovery. It has to be software as when you rotate the phone the problem still occurs on the top of the phone.
It is very occasional, generally after a reboot, and another reboot will fix it but just an annoyance.
Funny thing is, I have 2 Zenfone 2's one a 2.3ghz 64gb and a 1.8ghz(I'd love it if the transcribe error was right, 8.1ghz would kill anything and heat up the room like a fire) 32gb phone and the problem is present on both...
[email protected] said:
THERE YOU HAVE TO DO THE FOLLOWING:
Press Power + Volume up
And release only volume up while holding the power button. And once you see recovery, release power button too.
Click to expand...
Click to collapse
No need for the CAPS! All you had to say is to press them when I get the droid with the error message, I thought you meant when I first entered to select the recovery mode. Thank you, managed to get in.
ultramag69 said:
I find this occurs onmine sometimes too, the dead screen, not the unable to get to recovery. It has to be software as when you rotate the phone the problem still occurs on the top of the phone.
It is very occasional, generally after a reboot, and another reboot will fix it but just an annoyance.
Funny thing is, I have 2 Zenfone 2's one a 2.3ghz 64gb and a 1.8ghz(I'd love it if the transcribe error was right, 8.1ghz would kill anything and heat up the room like a fire) 32gb phone and the problem is present on both...
Click to expand...
Click to collapse
Strange.
Perhaps Asus_USA could get back to us about this?
ultramag69 said:
I find this occurs onmine sometimes too, the dead screen, not the unable to get to recovery. It has to be software as when you rotate the phone the problem still occurs on the top of the phone.
It is very occasional, generally after a reboot, and another reboot will fix it but just an annoyance.
Funny thing is, I have 2 Zenfone 2's one a 2.3ghz 64gb and a 1.8ghz(I'd love it if the transcribe error was right, 8.1ghz would kill anything and heat up the room like a fire) 32gb phone and the problem is present on both...
Click to expand...
Click to collapse
Hahahaha!!! Seriously Mate. 8.1Ghz Just imagine Antutu Benchmark Scores, Single core performance!!!. Asus could then have advertised zenfone 2 As a mobile + Room Heater.
PJBXDA said:
No need for the CAPS! All you had to say is to press them when I get the droid with the error message, I thought you meant when I first entered to select the recovery mode. Thank you, managed to get in.
Click to expand...
Click to collapse
Well, By CAPS i never meant to be rude. I was just emphasizing that "There" (Where you see the droid bot)"You have to do the following". Caps grabs attention.
This is Post #4 by me
When you see the open droid, Do the following.
Press Power (Hold), Press Volume Up and leave Volume Up.
You will enter recovery.
I think it is a hardware issue.
But still, try wiping cache and if possible do a factory reset (After Backup). Do not install any apps for a couple of days and see if the problem reoccurs
Click to expand...
Click to collapse
Well, If you recheck, In post #4, I explained clearly.
Any ways, glad that you figured it out.:good:
Hi Guys,
I dropped my zenfone2 in water yesterday.. Just for 2 seconds though.. I found the screen behaving weird,so switched off,removed all parts and kept to dry. There was some lag in the screen. At night again kept it in rice jar and also dried for sometime in sun.
1 problem i am facing is, since yesterday,the exact middle part(about 1 inch) of the screen has become unresponsive. Rest everything is working fine except this. Due to this facing issues with handling the phone.
Please if someone can help that would be great. Or do i need to visit the service centre?
Regards,
Satish
satishmohapatra said:
Hi Guys,
I dropped my zenfone2 in water yesterday.. Just for 2 seconds though.. I found the screen behaving weird,so switched off,removed all parts and kept to dry. There was some lag in the screen. At night again kept it in rice jar and also dried for sometime in sun.
1 problem i am facing is, since yesterday,the exact middle part(about 1 inch) of the screen has become unresponsive. Rest everything is working fine except this. Due to this facing issues with handling the phone.
Please if someone can help that would be great. Or do i need to visit the service centre?
Regards,
Satish
Click to expand...
Click to collapse
Probably but will cost you, unless you have insurance...
Today I was surfing the web and the phone locked up and restarted itself. Kept getting to the android screen with the red yellow and blue symbols then restarting. Left the phone alone to get back to work then the phone restarted finally went to use the phone and after about 3 mins froze up again. Now the phone won't get past the Google boot screen and if I want to try and power the phone on the power button has to be pressed in about 30secs to a minute of two.
Also i can't get into recovery mode reliably since if I select recovery the phone again freezes at the Google screen on reboot and never gets to recovery 9 out of 10 times other times I can get to recovery and then phone will then crash while in recovery or will allow me to use recovery long enough to wipe the cache and factory reset which neither has worked.
While Plugged into a charger and just sits there nothing on screen just a black screen.
Phone is on latest android unrooted and locked.
i had this happen to my SO's stock/locked/unrooted Nexus 6P.
Plug it into a PC, wait a couple minutes, then press and hold the power button for like 1-2 minutes.
2x4 said:
i had this happen to my SO's stock/locked/unrooted Nexus 6P.
Plug it into a PC, wait a couple minutes, then press and hold the power button for like 1-2 minutes.
Click to expand...
Click to collapse
What is this supposed to do? Where did you hear about this solution? Just curious.
jgr208 said:
Today I was surfing the web and the phone locked up and restarted itself. Kept getting to the android screen with the red yellow and blue symbols then restarting. Left the phone alone to get back to work then the phone restarted finally went to use the phone and after about 3 mins froze up again. Now the phone won't get past the Google boot screen and if I want to try and power the phone on the power button has to be pressed in about 30secs to a minute of two.
Also i can't get into recovery mode reliably since if I select recovery the phone again freezes at the Google screen on reboot and never gets to recovery 9 out of 10 times other times I can get to recovery and then phone will then crash while in recovery or will allow me to use recovery long enough to wipe the cache and factory reset which neither has worked.
While Plugged into a charger and just sits there nothing on screen just a black screen.
Phone is on latest android unrooted and locked.
Click to expand...
Click to collapse
do RMA
PiousInquisitor said:
What is this supposed to do? Where did you hear about this solution? Just curious.
Click to expand...
Click to collapse
read it on the nexus help forums i think. I was about to RMA the phone, so I'm glad i didn't have to. give it a try
2x4 said:
read it on the nexus help forums i think. I was about to RMA the phone, so I'm glad i didn't have to. give it a try
Click to expand...
Click to collapse
I don't have any issues. I was just curious. I've just never heard of a fix for any phone that requires a button press for more that like 30 seconds.
So what is the expected outcome? Does the phone just reboot and simply function correctly? Do you have a link to the forum post you read this in?
PiousInquisitor said:
I don't have any issues. I was just curious. I've just never heard of a fix for any phone that requires a button press for more that like 30 seconds.
So what is the expected outcome? Does the phone just reboot and simply function correctly? Do you have a link to the forum post you read this in?
Click to expand...
Click to collapse
Sure.
Here is where I read about plugging it into a PC and then pressing the power button:
https://support.google.com/nexus/troubleshooter/3337561?hl=en#ts=3337942,3339328
That didn't work (15 seconds hold). Then I found this random post on XDA where someone said they held it for more than a minute, so i tried that.
deanb1234 said:
Same exact problem. Phone was over 80% charged. Picked it up off of my desk at work to check the time and nothing. Just a brick.
Update*** I hooked the thing to power and nothing. So I just sat here at my desk for several minutes holding down the power button and the damn thing finally came back on. But I had to hold it for a very very long time, not the normal 10-30 seconds like it should take to do a hard power off. I'm talking minutes.
Click to expand...
Click to collapse
not sure why this worked, but it did. probably held it for 45s to 1m and it booted normally after that. honestly not sure what happened or why this worked.
2x4 said:
Sure.
Here is where I read about plugging it into a PC and then pressing the power button:
https://support.google.com/nexus/troubleshooter/3337561?hl=en#ts=3337942,3339328
That didn't work (15 seconds hold). Then I found this random post on XDA where someone said they held it for more than a minute, so i tried that.
not sure why this worked, but it did. probably held it for 45s to 1m and it booted normally after that. honestly not sure what happened or why this worked.
Click to expand...
Click to collapse
I'm glad my old post helped! Just an update though, it did that a few more times and then eventually I had to have it RMA'ed as no amount of time would make it boot.
deanb1234 said:
I'm glad my old post helped! Just an update though, it did that a few more times and then eventually I had to have it RMA'ed as no amount of time would make it boot.
Click to expand...
Click to collapse
haha dang, i hope the Nexus 6P it helped me boot doesn't have this issue any more...
Apayah said:
do RMA
Click to expand...
Click to collapse
Already did. Trying any last ditch efforts to revive the phone oh well it was a good phone.
deanb1234 said:
I'm glad my old post helped! Just an update though, it did that a few more times and then eventually I had to have it RMA'ed as no amount of time would make it boot.
Click to expand...
Click to collapse
Yup same here. It can get to the boot menu but recovery only works 1/10 times and can't ever get through 54% of the boot log until it freezes and crashes.
jgr208 said:
Yup same here. It can get to the boot menu but recovery only works 1/10 times and can't ever get through 54% of the boot log until it freezes and crashes.
Click to expand...
Click to collapse
Sounds like its time to RMA that bugger. Bummer.
PiousInquisitor said:
Sounds like its time to RMA that bugger. Bummer.
Click to expand...
Click to collapse
Yup new one is getting here today. Anyways, before old one is sent off I am curious to see if the battery is even charging when I connect to the charger. Anyone know if I can use a multi-meter to check this?