my damaged nexus one screen has progressed to the point of a black screen all the time... i didnt think of it before the screen died, but i am a bit stumped as to how i now reset to clear all my data? i cant see anything on the screen, but the phone still has my google account linked to it.
doh! :-(
reason i want it cleared: may send in for repair and i dont want others to get my info, or i may have to send to insurance company for payout (they said to hang on to phone for now) and i dont want them to see my info, or may sell damaged unit if insurance doesnt pay and i dont want those folks to get my info either.... see the problem?
You can try this. Did a google search.
http://www.droidforums.net/forum/droid-general-discussions/28793-how-do-full-adb-wipe-help.html
thanks for the link...would work if id had debugging enabled before the screen died... adb wipes require debugging mode.
any other suggestions?
There's this:
http://code.google.com/p/androidscreencast/
But if you don't have Debugging enabled and can't get it to register when you hit "adb devices" you're probably effed. I don't know much about touch screen engineering, though. Does it still respond to touch as far as you can tell, or is the screen completely dead when the OLED display stops working?
This serves as a good warning for others, though. ALWAYS MAKE SURE USB DEBUGGING IN SETTINGS > APPLICATIONS > DEVELOPMENT IS CHECKED. There's really no good reason I can think of that would ever make you want to leave this unchecked, and this is an example of when it would come in very handy.
cant you use the clear storage function by booting while holding volume down, waiting 5 seconds, then pressing volume down 3 times followed by a press of the power button?
flybyme said:
cant you use the clear storage function by booting while holding volume down, waiting 5 seconds, then pressing volume down 3 times followed by a press of the power button?
Click to expand...
Click to collapse
is this a commonly known sequence ? if so, please link to a list of all the known boot-up key combos. thanks
Kiserai said:
There's this:
http://code.google.com/p/androidscreencast/
But if you don't have Debugging enabled and can't get it to register when you hit "adb devices" you're probably effed. I don't know much about touch screen engineering, though. Does it still respond to touch as far as you can tell, or is the screen completely dead when the OLED display stops working?
This serves as a good warning for others, though. ALWAYS MAKE SURE USB DEBUGGING IN SETTINGS > APPLICATIONS > DEVELOPMENT IS CHECKED. There's really no good reason I can think of that would ever make you want to leave this unchecked, and this is an example of when it would come in very handy.
Click to expand...
Click to collapse
the digitizer still accepted touch input as screen beneath began to fail. colors bled from the cracks and the images began to imprint in the screen... within a few hours, it was completely illegible, and then the next morning, it appeared as a dysfunctional unit with a non working screen.
i will try and methods suggested, but i have no way to verify success... thanks for the sequence.
well when you boot by holding power, your given options FASTBOOT, RECOVERY, CLEAR STORAGE, SIMLOCK
Heres the exact key combination
Boot phone using Volume Dn + Power
Wait 5-10 seconds to be safe
Press Volumn Dn twice
Press Power Btn
Press Volume Up
Phone should reboot after 5 seconds
i will try that... confirmation of success will be the charging LED turning off and then back on again?
nexusonemeover said:
i will try that... confirmation of success will be the charging LED turning off and then back on again?
Click to expand...
Click to collapse
of the reboot? ya. i cant imagine doing this without the screen lol. Sorry i couldnt be more help
You could also probably flash a PASSIMG.zip from the bootloader. That will overwrite all partitions so it should make it 100% stock.
It might be harder to do without the screen than the clear storage function though.
flybyme said:
of the reboot? ya. i cant imagine doing this without the screen lol. Sorry i couldnt be more help
Click to expand...
Click to collapse
tried the method... and i think it worked... i cant verify, but thanks for the help guys.
You can easily verify that by sending yourself an email and see if your phone can get the notification of that new email (by trachball or sound).
Related
Hi guys,
I honestly thing that this is a unique situation. I have done a lot of searching, not just here but on Googlez as well, and no one seems to present a solution for me.
I have a Galaxy S that I received yesterday. I thought this was going to be a new hand set but it has been used. I know this because the previous user has set a pattern lock that I don't know on it.
So I have been trying to wipe this phone so that I can use it. I have tried a lot of avenues and yet nothing has worked. Here is what I have tried:
Reboot Into Recovery Mode : I believe I have tried every button combination to get into the recovery/maintenance mode so I can select wipe. However, when I try a combination (for example holding vol down and power) the phone gets to the initial boot logo, goes black, shows the same logo again, goes back, and repeats this in a loop until I let go of one of the buttons. When I do that it boots normally.
So this seems to indicate that the recovery mode on this phone is broken. Anyone else have any ideas with this bit?
ADB : Ok, so I turn the phone on to the lock screen. Then I plug in the USB cable to the computer. First, the device drive unsuccessfully installs on Win 7 every time. Then I fire up CMD, navigate to my ADB folder, and run 'adb devices' this just returns an empty list of devices attached.
I assume that based on the results of ADB that 'debugging via usb' is not turned no. I cannot turn this on because I'm locked out. Anyone know a way round this?
Special Code : Apparently there's a special code that can be entered on these Galaxy S devices when in the phone normally to wipe it. You have to enter this code via the Dialer (my mate tells me the code is '*2767*3855#'). I can't get to the normal dialer because I'm locked out so I try and use the Emergency Dialer. However, this proves unsuccessful as the phone just tells me that the code is not an emergency number.
At the moment I cannot see a way to fix this phone. It is impossible to find who used this phone before me.
Any ideas are welcome.
Before anyone Calls BS on this "Stolen Phone" its not and it is legit i can verify that the phone is legit and defiantly not stolen.
If I bought a "new" phone which is actually a "used" phone, I would return it!
And if it is legal, that should not be the Problem.
Anyway:
For the normal way to unlock the phone if you forgott your pattern you need the gmail account.
Without adb or 3-button-mode your phone is kind of useless.
He is just doing the combo wrong if you ask me. Hold the buttons until you see the initial bootscreen and then let go. If it doesn't work, 3 key combo might indeed be disabled
Sent from my GT-I9000 using XDA App
It was not purchased it was given as a competition and there was nothing stipulating that the handset would be new.
Obviously the competition handset had been used as a demo before being given out as a prize and they had forgot to factory reset the handset before giving it out.
Problem is Gmail, lock pattern, adb (doesn't seem to work as usb debug must have been left of) , and recovery wont work by the looks of things. Also tried to call the handset and press back button but must have updated FW
The people who held the comp have been notified but obviously where there is an android problem you guys know your onions so we ended up posting here.
I was just about to say the same thing as Kenneth. This is indeed a device won through a competition with Samsung them selves.
What combinations of buttons are talking about? I've tried and read about a lot, but would like to what you guys think the combination should be.
Any combination does seem to do the same thing though:
Hold down till the logo appears the release = Normal Boot
Hold down till the initial logo changes to a black screen = Normal Boot
VolUp+Home+Power is the one i am talking about
Wait until u get the white text logo and release as soon as you see it. If it doesn't work, combo is broken and the phone will indeed be useless until you can get the right pattern
You should try it like this and stick to the order!
Hold Volume up + Home (sqaure bottun in the midle) + Power on
When Galaxy S (white on black) appears you can release all buttons. It should go to recovery, if not this mode is disabled on your phone.
Even so I would try to swap it! If it is from Samsung itself that should not be a Problem at all.
OH... MY... DAYS!
Ok! The three button combination, and then releasing it as soon as the logo appeared, worked. I have successfully wiped the phone and am in.
Great advice guys. Thanks.
Thanks from me as well quick response and always awesome knowledge.
Oddly enough the combinations from vodafone uk and others were different so you guys are amazing.
Cheers Kenny
Thread moved to Q&A.
I am in the same situation and the 3-combo combination doesn't work .
It doesn't communicate either ...
I opened this app (battery booster, can't post link because I am new) after downloading it excited to hoping it was better then a previous one I was trying that seemed to do next to nothing.
I saw the brightness button and hit it. It showed 11%. I was like oh I thought I had this all the way down...so I use the scroller to take it all the way down assuming 0% meant that it was the lowest it could possible dim the screen...well it sure is a battery saver considering I can't even see my screen as its completely BLACK...............................
1. Why would you even allow something like this in a app.
2. Please help me fix it...
I have tried for about an hour to assume where the scroll down, and mounting the phone to my computer so that I could possibly uninstall it via computer with no luck...
anyone????!
I don't want to piss you off or anything, but I had read a comment on another thread saying they could never get it to come back, even when they went back to stock.
You may need to head down to the Verizon store :/
chronster said:
I don't want to piss you off or anything, but I had read a comment on another thread saying they could never get it to come back, even when they went back to stock.
You may need to head down to the Verizon store :/
Click to expand...
Click to collapse
son of a...this is so stupid! What a bad feature to have in a app for idiots like myself apparently
if you have adb debugging you might be able to fix it...
http://forum.xda-developers.com/showthread.php?t=785603&highlight=horror
If you have usb debugging on, you can use adb to delete the app you downloaded I think. Did you have it enabled?
Florynce said:
If you have usb debugging on, you can use adb to delete the app you downloaded I think. Did you have it enabled?
Click to expand...
Click to collapse
I didn't have debugging on i checked via adb and long story short...i was still within 30 days of purchase ;-)
All may not be lost!!
If you're still in your 30 days take it back and exchange it.
If not, try booting into recovery mode and reset the phone. I don't think you need root to do that much and it should put the phone back to the way it was when you took it out of the box.
Hold down the volume button so that you are pressing both up & down volume at the same time (easiest to do with the battery cover off).
While holding the volume keys down press and hold the power button too. When the Samsung screen comes up release both buttons. A couple seconds later you will see the "Android system recovery" screen.
Press the volume down button until you have highlighted "wipe data/factory reset".
Press the "Home" button to select it.
You will then be told to press the volume up button to wipe the phone or press the volume down button to exit/cancel. Press volume up and follow any additional instructions. That's as far as I go to guide you (I want to keep my stuff as is ).
If that doesn't take care of the issue then you should take it to verizon and tell them what happened. Good luck and let me know if this worked for you!
~Johnny
So I inherited a G1 that looks like its in good shape. But when I turn it on it briefly flashes a boot screen that quickly fades to black.
If I hold down the power and camera button it starts to boot, I let go of the power button and keep the camera button held down the screen will stay lit and I can see the fastboot mode. As soon as I let go of the camera button some other words flash on the screen and it dies again.
I looked through the forum assuming I could quickly fix this and have a new backup phone but this forum is now so advanced nobody seems to be having basic problems like this. And anyone who is still here seems to have lots more experience than me with this particular model of phone. Usually the stickies have an unbrick thread but I cant seem to find it.
I am sure this is something simple but if someone could point me in the right direction, or say the screen is burned out, I its bricked, or whatever you think it might be, I would appreciate it.
After more reading and discussing with previous owner, I think that the Camera and power button puts it into fastboot. (not sure exactly what that is yet)
From there it tries to install something from the SD card but fails.
The SD card contains DREAIMG.nbh and two empty folders. It seems to be trying to install something else besides DREAIMG but it fails so fast I cant catch it.
Is there something else I should place on the external SD card or perhaps a different version of the same file?
The previous owner also told me the G1 had been running CM6 if that makes any difference. ( I know it does on CM7 ).
I can get it to the screen with the three skateboarding androids (engineering spl indication? )but any time I let go of any of the buttons the screen fades right to black, making any further button pushing useless.
Any helpful hints? Anyone? Even a thread you think I should read completely?
I copied the DREAIMG.ngh to the desktop of my computer and reformated the SD card. After I bunch of button pushing and holding I managed to get it to hold on the HBOOT screen without going black. I pushed the trackball down and it reloaded the image apparently. Now it turns on and such but none of the keyboard buttons work and it says safemode in the bottom left corner. I will continue to read and search.
I cant find anything in this forum about safe mode. I am stumped.
The phone will boot and tries to get me to sign up for the gmail account but the keyboard only has the d, e, f, and x keys working.
The emergency dialer seems to work. I dialed my other phone with it and it said its not an emergency number and wont let it dial.
I am pretty sure this is not a lost cause here. There is just something I am missing. Could it be a bad flash from the DREAIMG.nbh?
Would it be possible to download a different image.nbh from someplace and try that?
Anyone have any ideas?
ok what are you trying to do exactly? i think your having trouble because the files on your sd... take them all off and see what happens??
can you boot into recovery? holding home+power??
ldrifta said:
ok what are you trying to do exactly? i think your having trouble because the files on your sd... take them all off and see what happens??
Click to expand...
Click to collapse
Trying to get a functioning phone is all. I am comfortable fiddling with it , just dont know the process to go through.
I pulled the SD card and rebooted and its the same result. Little grey box in the bottom left that says 'safe mode' and it proceeds to the google account screen.
The touch screen works, and the trackball seems to. but Home and Menu dont so I cant even back out of the sign in screen.
Booting up with home+power gives me the triangle with the ! inside it instead of any kind of recovery mode like I expected.
Like I mentioned earlier, I believe it might be running CM6 but I am not even positive about that. I was told it was.
Any suggestions on my nextstep to get it into some kind of functoning state? I am willing to try anything suggested. New ROM or whatever.
I really thing its something simple, I just dont have any expreience with this model at all.
After more searching I guess the ! with triangle is the first screen of the recovery mode? But pushing Alt+L or Alt+I doesnt do anything.
I am used to the Galaxy S recover mode being all right there on the screen.
So next step would be......?
no wait you get the triangle and the !?? thats good lol that is the stock recovery mode.. so now i know what to work with when you get to that screen you can press alt+L and a list should pop up!!
FireRaider said:
After more searching I guess the ! with triangle is the first screen of the recovery mode? But pushing Alt+L or Alt+I doesnt do anything.
I am used to the Galaxy S recover mode being all right there on the screen.
So next step would be......?
Click to expand...
Click to collapse
oooo it doesnt do anything?? hmmm
you sure nothing happens? try pushing down alt hard and keep holding it.. than press down on L hard see if a list pops up.. it only like 3 choices..
ldrifta said:
you sure nothing happens? try pushing down alt hard and keep holding it.. than press down on L hard see if a list pops up.. it only like 3 choices..
Click to expand...
Click to collapse
Nothing, hold down Alt and then press and hold L. No changes.
The other odd thing is now when I do the camera+power combo it takes me to the welcome screen instead of the HBOOT screen. I was going to try reflashing the image on the external SD card and now it wont do that either.
The return+power combo also takes me to the welcome screen now.
The welcome screen is where I want to be except the 'safe mode' seems to be keeping the keyboard from functioning?
what welcome screen? lol
are the keys sticking maybe? lol
ldrifta said:
what welcome screen? lol
Click to expand...
Click to collapse
First I get the T-Mobile G1 screen.
then the Android guy
then the Welcome to T-MobileG1, touch the android to begin.
That all seems normal to me, except for teh grey box that says 'safe mode' in the corner.
So i touch the android and it moves to the Setting upp your T-mobile G1 screen and wants me to enter my account info, which I cannot do because the keyboard is not funtioning properly. Its almost like the image flash borked the keyboard drivers or something.
ldrifta said:
are the keys sticking maybe? lol
Click to expand...
Click to collapse
the d, e ,f , x keys are all working so I think its not a stuck key. no other keys seem to work though. nor the menu buttons.
would safe mode mean some of the drivers are disabled? kind of like on a desktop computer?
And if so, how to get out of safe mode?
uhhh i never even been on safe mode.. is the led blue while its on? my advice would be to unroot but you cant get recovery functioning properly so im not sure what to do.. do you know what radio and hboot you have?
does it go to safe mode when you just boot up normally?
ldrifta said:
does it go to safe mode when you just boot up normally?
Click to expand...
Click to collapse
Yes, safe mode shows in the bottom left corner of the screen when I power up normally.
I should have writen down what radio and such as I saw it displayed when I was in HBOOT and installing the DREAIMG.nbh file but I didnt think to.
Now I am either getting the Welcome to T-mobile screen or the first step of the recovery screen depending on the button combo I use.
But I am unable to proceed to do anything useful.
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
KomuroXV said:
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
Click to expand...
Click to collapse
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
LibertyMarine said:
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
Click to expand...
Click to collapse
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
stovie_steve said:
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
Click to expand...
Click to collapse
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
KomuroXV said:
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
Click to expand...
Click to collapse
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
clsA said:
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
Click to expand...
Click to collapse
I've tried both.
Here's another one anyways.
https://www.youtube.com/watch?v=1zyA6XGFEpo&list=UUzlEfhRw_dyaJ7aAFpWC7-A
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
LibertyMarine said:
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
Click to expand...
Click to collapse
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
KomuroXV said:
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
Click to expand...
Click to collapse
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
nkk71 said:
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
Click to expand...
Click to collapse
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
@KomuroXV but what nkk suggested is a good idea, but just be very very gentle. I f#cked up my powerbutton pressing it too much. Luckily HTC believed my (altered) story and I got a replacement.
What you can try is to just go with a paper edge between the power button and the Magnesium surrounding then try to much it upwards and downwards, this may help "unstucking" your powerbutton if that's even the case.
I'm gonna test the with my phone how long it takes to reboot if I hold down the power button (will post again in a few min). If it's about the same as shown in your vid, it might really be a stuck power button.
LibertyMarine said:
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
Click to expand...
Click to collapse
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
nkk71 said:
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
Click to expand...
Click to collapse
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
LibertyMarine said:
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
Click to expand...
Click to collapse
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
KomuroXV said:
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
Click to expand...
Click to collapse
I'm gonna sleep now, will answer tomorrow evening. I have an important meeting tomorrow.
KomuroXV said:
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
Click to expand...
Click to collapse
i dont see how flashing / interrupting flashing a recovery could cause that, the recovery is in a different partition than bootloader, so even if you were unable to enter recovery (due to bad flash), you should be able to get to bootloader
but when you say it got stock at 40%, i'm seriously surprised, as flashing a recovery literally takes 2 seconds:
Code:
C:\ADB3>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
maybe try covering the light sensors completely, and hold voldown, when it reboots again.... maybe (though i doubt it), it will forego the simulated battery pull
KomuroXV said:
[...]
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
[...]
Click to expand...
Click to collapse
How did you turn it off? Did you press the power button very hard/strong?
Did you flash the recovery with fastboot
or did you flash your recovery within rebootRUU and with an firmware.zip ?
Because the method via fastboot (fastboot flash recovery recovery.img) doesn't indicate a percentage. And btw. I had issues with this method too and interrupted the installation several times, didn't cause any problems. To the theory that your phone wants to continue flashing recovery is not true. This isn't possible since your phone should boot correctly and if it wanted to boot into recovery you could prevent that with pressing the vol. down button. That didn't work in your case so I think that this theory doesn't work out.
If you flashed it with a firmware zip, was there another hboot.img that you installed too without knowing/wanting? Because interrupting a hboot flash will brick your device. but if that happend you wouldn't be able to boot your phone. So I think this isn't true either.
i have exactly the same problem, is very strange beacause i was updating my ROM
Hey guys,
So I have had my One more than a year, never root, never install any mod in it, just simple, daily use. It worked well till last night when some weird thing happened:
- At first, the Back, Home and HTC buttons keep flashing along with the screen. When I unlock my screen pass lock and go to the home screen, it showed a notification like "To restart the phone, keep pushing the power button for (x) second" with x is the count down number. After that, the phone is automatically rebooting, then the problem happen again.
- After a few times, I manage to shut it down properly then turn the phone up. As I notice, as long as I doing something with the phone such as calling somebody or checking facebook or simply sliding the home screen, thing is normal. But as I stopped using it, that weird notification pop up again
- The phone keep restarting after that, again and again. Sometime it boot successful, but when Im go to the home screen, the notification shows up and my phone restarts again. As I couldnt turn off my phone, it is drained and out of battery.
- This morning, I put the cable in and try to charge it, and My One now stuck at the first HTC logo screen then restarting and then stuck again. That looping process is drive me crazy. As I try to pull out the cable, the phone is not working (Obviously) since it is out of battery.
- As I hold down Power and Volume down, I can enter bootloader screen. I saw a "locked" banner and cannot navigate through the menu and can not press Fastboot or anything. After 2-3 seconds, the phone is shut down and keep looping.
Long story shot, can anybody tell me how to fix this. As I have a lot of pictures that havent been backed up, I really appreciate if I can keep everything without doing a factory reset. Oddly enough, I cant even do a factory reset since the bootloader is not working.
Please help.
Have you tried a factory reset?
On boot, bottom down n power will take u to fastboot.
You can do a factory reset from there.
HTC sync can save your stuff.
Sent from my HTC One_M8
mashk said:
Have you tried a factory reset?
On boot, bottom down n power will take u to fastboot.
You can do a factory reset from there.
HTC sync can save your stuff.
Sent from my HTC One_M8
Click to expand...
Click to collapse
As I mentioned above, I can hardly do anything from that fastboot screen. Up, down and power button is not working as I cannot navigate to recovery or factory reset. Even pushing power button wont do.
When I connect the phone to PC, nothing happen. It is because the phone is out of battery i suppose?
The problem is when I start to charge the phone, it will keep looping. But if I dont, the phone is death and I cant do anything.
I honestly dont know. I suspect you have
Fast boot selected under Settings>power.
You've got to try till you can get into fastboot otherwise send it for repairs.
Sent from my HTC One_M8
evelucife said:
Hey guys,
So I have had my One more than a year, never root, never install any mod in it, just simple, daily use. It worked well till last night when some weird thing happened:
- At first, the Back, Home and HTC buttons keep flashing along with the screen. When I unlock my screen pass lock and go to the home screen, it showed a notification like "To restart the phone, keep pushing the power button for (x) second" with x is the count down number. After that, the phone is automatically rebooting, then the problem happen again.
- After a few times, I manage to shut it down properly then turn the phone up. As I notice, as long as I doing something with the phone such as calling somebody or checking facebook or simply sliding the home screen, thing is normal. But as I stopped using it, that weird notification pop up again
- The phone keep restarting after that, again and again. Sometime it boot successful, but when Im go to the home screen, the notification shows up and my phone restarts again. As I couldnt turn off my phone, it is drained and out of battery.
- This morning, I put the cable in and try to charge it, and My One now stuck at the first HTC logo screen then restarting and then stuck again. That looping process is drive me crazy. As I try to pull out the cable, the phone is not working (Obviously) since it is out of battery.
- As I hold down Power and Volume down, I can enter bootloader screen. I saw a "locked" banner and cannot navigate through the menu and can not press Fastboot or anything. After 2-3 seconds, the phone is shut down and keep looping.
Long story shot, can anybody tell me how to fix this. As I have a lot of pictures that havent been backed up, I really appreciate if I can keep everything without doing a factory reset. Oddly enough, I cant even do a factory reset since the bootloader is not working.
Please help.
Click to expand...
Click to collapse
looks like an hardware defect, maybe your power button is stuck?
alray said:
looks like an hardware defect, maybe your power button is stuck?
Click to expand...
Click to collapse
I dont think so man. It seems working normal for me. But thanks anyway
evelucife said:
I dont think so man. It seems working normal for me. But thanks anyway
Click to expand...
Click to collapse
"To restart the phone, keep pushing the power button for (x) second" with x is the count down number.
Click to expand...
Click to collapse
Because this is exactly the message we usually get when holding the power button for more then 5 sec...
and that would explain the reboot issue
looks like the "power" key is always active
definitively sounds like an hardware issue imo
and your issue is even present in bootloader what confirm that this is an hardware defect.
alray said:
Because this is exactly the message we usually get when holding the power button for more then 5 sec...
and that would explain the reboot issue
looks like the "power" key is always active
definitively sounds like an hardware issue imo
and your issue is even present in bootloader what confirm that this is an hardware defect.
Click to expand...
Click to collapse
Yeah u has a point. Any idea how to fix that? Or I have to bring it to someone else to fix it.
evelucife said:
Yeah u has a point. Any idea how to fix that? Or I have to bring it to someone else to fix it.
Click to expand...
Click to collapse
You'll probably have to send it for repair. Better to contact HTC and see how much it will cost...
alray said:
You'll probably have to send it for repair. Better to contact HTC and see how much it will cost...
Click to expand...
Click to collapse
Thanks man. I will see if i can do.