[Q] Hp Touchpad - black screen "Please release key(s)... HELP - TouchPad Q&A, Help & Troubleshooting

I have a 32gb Touchpad. It has been running CM7 fine (dual boots that and WebOS) since June 2012. The battery had completely died so I plugged it into the power adapter. After it had charged for a few minutes it started to go threw the process of loading. The hp logo came up as normal and then a black screen appeared with the message "Please release keys..." I tried keeping the power button pressed down for eternity does nothing (I've rebooted if the Touchpad has gotten frozen before or if the touchpad didn't recognize touch on the screen).
Please help, I have no clue what to do. I googled the problem and it seems people have this happen when they install CM, but mine's been running fine for months and this is spontaneous.

Sounds like your home key is stuck!
Sent from my SAMSUNG-SGH-T989 using xda premium

-SGA- said:
Sounds like your home key is stuck!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Any suggestions on how to fix this? Although it doesn't seem to be stuck. I am able to press it when trying to reset the device.

Touchpad Boot Loop due to Stuck Home button
-SGA- said:
Sounds like your home key is stuck!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I think this is what I have been experienced :
Have done some significant research before posting but have not found a clear match to my problem. I bought two Touchpads for my daughters when on fire sale (lucked out with OnSale), and they have been running with CM9 with no problem for several months. One of them last week would not boot and after some charging it appears to be stuck in a boot loop. I have charged it for several days to try to eliminate battery issues with no luck, and I suspect something other than charging...
Here is what it will do :
If I hold home and power to reset, it will momentarily show the HP logo, then the Moboot menu, but it instantly flashes to a Cyanogenmod boot with no waiting (first clue that the home button is stuck ????). The unit then tries to boot but the display will not stay lit. Occasionally when the unit is resting on the Touchstone I can see the clock like it has been booted into CM9, but I cannot interact with the touch screen at all, and the clock will not stay on the display.
If I try to boot and bring it into recovery mode, I can hold the Volume Up after releasing the home and power and I get a blue screen and the message to "Please Release Keys" (another clue that the home key is stuck ?).
From this position it runs the boot loop again, with no opportunity to interact. Can't get it to recovery so it is a paperweight at this point..
I see my options as follows :
1. Keep trying to charge to see if it is just a battery charge issue, but if I see evidence that it is booting into CM9, that steers me away from this solution
2. Let it discharge cpmpletely and then recharge (don't really like the risk of introducing a battery issue where there isn't one...)
3. Crack the unit open and try a replacement of the home button
Would appreciate any input.
Thanks
Todd

You might try using adb.
In the terminal navigate to the folder with adb and:
adb start-server (to start adb)
adb devices (to confirm the Touchpad is recognized)
adb reboot recovery (to boot into recovery)
adb reboot recovery should be entered while it has the boot loop in process
Sent from my SAMSUNG-SGH-T989 using xda premium

thanks for the reply. Installed the SDK and ran ADB,but it does not recognize the Touchpad - have tried reset, all manner of button combinations and it won't list it as a connected device.
Any other ideas ?
Thanks in advance
Todd
-SGA- said:
You might try using adb.
In the terminal navigate to the folder with adb and:
adb start-server (to start adb)
adb devices (to confirm the Touchpad is recognized)
adb reboot recovery (to boot into recovery)
adb reboot recovery should be entered while it has the boot loop in process
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse

cthenrys said:
thanks for the reply. Installed the SDK and ran ADB,but it does not recognize the Touchpad - have tried reset, all manner of button combinations and it won't list it as a connected device.
Any other ideas ?
Thanks in advance
Todd
Click to expand...
Click to collapse
I don't think that your home button is stuck. If it were stuck, the screen would read "please release keys" as you have seen when holding the volume buttons while booting. Based on that, I wouldn't suggest attempting to replace the home key.
It's likely that debugging was not enabled on the Touchpad before the issue started, hence why adb cannot connect, which is unfortunate.
I would suggest that you might try pressing one of the volume keys in rapid succession while booting into moboot. That may get you the opportunity to catch the boot menu before the timeout (sounds like it has been set to "0" somehow).

Well I got it to do something...
I got it to where my PC would recognize a Palm / Novacom device and was able to run WebOS Doctor, which is great. What is not so great is that I get no display, although I can tell the unit is booted into WebOS (I.e. I get a tone when increasing / decreasing volume and I can get the camera to fire by pressing power and home.
After a reset and putting it on the touchstone it appears that WebOS is running fine, but there is nothing on the display.
Best guess now is just a bad display that can be replaced,correct ?
Thanks for the help
Todd
-SGA- said:
I don't think that your home button is stuck. If it were stuck, the screen would read "please release keys" as you have seen when holding the volume buttons while booting. Based on that, I wouldn't suggest attempting to replace the home key.
It's likely that debugging was not enabled on the Touchpad before the issue started, hence why adb cannot connect, which is unfortunate.
I would suggest that you might try pressing one of the volume keys in rapid succession while booting into moboot. That may get you the opportunity to catch the boot menu before the timeout (sounds like it has been set to "0" somehow).
Click to expand...
Click to collapse

Related

[Q] Strange Reboot Loop, searched forum Not Addressed

Hello All
I did search the forum and still not answer for the stranger reboot loop.
I got a phone call, and answered it. The reception was crappy and hear no voice. I then looked at the phone to see if call had dropped and it was frozed on the incoming call screen. I then pulled the battery and pressed the power button to turn on the phone and It would not power on. After multiple battery pulls and many many power button presses, still nothing. It was like it was out of battery. It was stitting on the home charger before i left the house. Prior to this the phone worked fine. Over the past week or two I had to do a battery pull may be 3 times.
I got to my car and plugged it into the charger and the orange charge led came on, on the front of the device. I then pressed the power button and it vibrate once as normal and then went to the multi-colored nexus "X." he screen went black and then vibrated once again and and was back at the mulit-colored "X." Then the loop starts.
In between the restarts I try to get it to boot into the bootloader by using the "vol down and power" and the "trackball and power button" and the white screen for the boot loader flashed for a milisecond the goes to black. As long as I hold the "vol down" button the while bootloeader or recovery screen flashes every 4-5 sec for a milisecond. As soon as I let go of one of those button, it automatically goes to the full reboot loop.
THis all happens when it is plugged into a power source. As soon as i unplug it, it goes back to the power button not responding. Again it acts as if it has no battery power. But it is in the 90%.
So i am unable to do any other step as in reflashing, and or doing a recovery.
ANY IDEAS any one.
I was running Cyanogen RC3. the latest rom with amon RA 1 7 1, korean radio 5.0.8
It was running perfectly up till today. when it went into its loop.
ANY HELP WOULD BE AWESOME
THanks in advance
DD
Plug it in to the USB, adb reboot recovery, reflash rom. Or even wipe and reflash if needed.
Sounds like it could be hardware the way you have to hold the keys down and you said it wasn't responding to the power button press.
ok thanks, ill give it a try.
here is my only issue. I am not using my original computer Mac. I just sent it out to apple for repair. So i am using my companies computer. I need to set up the AndroidSDK to be able to talk to the nexus. Since the phone will not turn on i can not load the drivers. and ive tried every way and it has not installed and i cant check because it wont stay on. it just goes to the loop. and it wont turn on if its not plugged to a power source.
Any ideas or suggestion.
SOrry I am an noob, so could you please be specific in your instructions.
I as of right now have insalled the Android SDK and i am unable to see the serial number (working on an old dell, running XP sp3) because it wont turn on.
It cant manually install the drivers because I cant turn the phone on to specify the drivers.
and
I using USBDeview, the phone also has to be on to erase all HTC previously installed drivers. i think. but there were none in the usb log...i think becuase they didnt install...agains because it would not power on...:-(
any ideas...please
DD
Also
Sorry excuse me if its a sort of a duhhh question...
even if i am able to load the device bridge, if the phone will not boot can i still flash another rom, or do a recovery. The phone is not getting past the Multi-colored "X" ???
DD
It should still read the commands when it's trying to boot. You don't need to turn the phone on at all to be able to install the ADB drivers, they are independent of each other.
As strange as it started, is a strange as it went.
This morning open the phone to pull the sd and the sim to put it in a throw down phone. I replaced the battery and cover and just hit the power button. The phone does a full boot and it appears to be working properly. the sd card and sim are fine. I the odd thing is i did this multiple times yesterday and last night. I pulled both sim and sd, replaced the battery and tried to boot with the same issues as named above with nothing different.
I left the phone on charge last night and it was charging for close to 8 hours and it was still showing the orange charging light.
So after it booted this morning, and i checked everything. It showed the same amount of charge as yesterday, right before it froze, which was 75%. So that is another strange occurance.
I plan on reflashing the rom and seeing how things go.
I thank you for your assistance and time.
appericate you helping out a clueless noob.
DD

[Q] No really, I bricked it...

OK, I've been reading here for 6 days all manner of Captivate unbricking. Here is my story...
I picked up a Captivate on the Rogers network. I connected it to my email server (Exchange 2010) with no problems, poked around, noticed the lag, noticed the SMS time issue, then promptly rooted, installed clockwork, and then threw cognition 2.2 beta 9.1.3. Quite frankly I was shocked at how much faster it was.
Anyways, after a day of poking around, I could not get my email to my exchange server running (tried the email.pak floating about), so I actually decided I was going to go back to the backup I made of my phone using clockwork before I installed cognition. When I restored my backup, I thought I had bricked my phone.
I let it rest for a day, then came back here, and found one of the 3-4 different variations of the 4 button download mode combo that permitted me to do the 1 click restore. This restored me to the AT&T version of 2.1. It worked, but was less than desirable.
I decided that at that point I really wanted to go back to stock, so I downloaded the stock backup on the Rogers Captivate wiki page, and did the restore using clockwork. The phone has not been the same since.
When i turn it on, I get an at&t splash screen, then in about 20 seconds I get the at&t "jingle", but the splash screen stays on. I can't seem to find any key combination that will permit me to get back into download mode so I can restore using the One Click that worked for me the first time. I have tried:
1. 3 button salute with USB in first, battery out initially.
2. 3 button salute with USB plugged in *as* I was inserting the battery.
3. Power and volume down (both with and without USB, and with battery being plugged in after USB and "during" insertion of battery)
4.Power and volume up with same combo's as #3.
5. Just volume up and volume down with same combo's as #3.
In all cases Odin was running before USB connected, running as administrator. I'm running 64bit windows, but I'm sure I have the correct drivers because I did this the first time with Odin and download mode and I haven't added or changed anything. But just for arguements sake I did uninstall, and then install the drivers again.
Any combination of power and volume buttons just gives me a battery charging logo. Occasionally when holding up until the second black screen I will get a quick indication that the computer might see something, but it dissappears withing a handful of seconds showing it promptly removed.
I'm downloading the Android SDK in the hopes that when I get the normal at&t splash screen after the "jingle" that something might actually be running in the background and maybe I can adb reboot download it but I'm not holding my breath.
Anyone seen this that has managed to get out of it? I'm starting to think the "unbrickable captivate" can be bricked. Assuming it is bricked, short of taking it back, is there anyone on the internet that can jtag these and in some fashion bring back to life?
Cheers,
Tim
This doesn't belong in Development.
MikeyMike01 said:
This doesn't belong in Development.
Click to expand...
Click to collapse
ditto
and download mode is easy.
1. start odin3 and have data cable plugged into the computer
2. insert proper files if needed
3. hold volume up and volume down for 2 sec (no power button needed) then insert usb cable, continue to hold volumes till either the download mode screen pops up or odin3 sees the phone(if you bork the phone bad enough you can corrupt the download mode image, i did it with the not to successfull manhatten project kernel) but despite the screen being black it very well may be in download mode.
4. start flash
5. if it doesn't work send it to me ill find a use for it
alternatively if the phone can go passed the splash screens and boots fully you can adb reboot download. just get the development kit and drivers on your pc.
Dani897 said:
ditto
and download mode is easy.
1. start odin3 and have data cable plugged into the computer
2. insert proper files if needed
3. hold volume up and volume down for 2 sec (no power button needed) then insert usb cable, continue to hold volumes till either the download mode screen pops up or odin3 sees the phone(if you bork the phone bad enough you can corrupt the download mode image, i did it with the not to successfull manhatten project kernel) but despite the screen being black it very well may be in download mode.
4. start flash
5. if it doesn't work send it to me ill find a use for it
alternatively if the phone can go passed the splash screens and boots fully you can adb reboot download. just get the development kit and drivers on your pc.
Click to expand...
Click to collapse
Thanks, but that doesn't work. All I get is the battery charging screen. Using the process it does not go into download mode.
MikeyMike01 said:
This doesn't belong in Development.
Click to expand...
Click to collapse
Could a moderator move this to Captivate General then? Sorry about that...
timmy22 said:
Thanks, but that doesn't work. All I get is the battery charging screen. Using the process it does not go into download mode.
Click to expand...
Click to collapse
just to be clear, you are holding volume up as well as volume down starting with the phone being powered down and continue to hold them after you plug in usb untill something shows on the screen?
if your phone is not seeing the volumes buttons you are one of the very unlucky few that had a problem at the most inopportune moment.
there is also a way where you hold all three buttons till the phone reboots twice, or something. let me try it and ill give more specifics.
timmy22 said:
Thanks, but that doesn't work. All I get is the battery charging screen. Using the process it does not go into download mode.
Click to expand...
Click to collapse
Pull the battery, open odin, plug usb into computer, hold vol up and down, plug usb into phone still holding vol buttons, drop in battery still holding vol buttons, when dl screen pops up and yellow com port lights up in odin release volume buttons. Do not touch power button at any time
Swyped...and sorry I don't proofread
Have you tried rebooting into recovery mode instead of download mode? Stock recovery is adb-ready and you should be able to adb reboot download. Its a long shot if you're having problems using button combo to get to d/l mode, but it's probably still worth a shot at this point.
If you were able to use 3 button combos before all this happened, and did NOT have to install the 3 button combo fix, its strange you don't have access to it now... Could restoring a Rogers Cappy to AT&T stock be the problem?
Dani897 said:
just to be clear, you are holding volume up as well as volume down starting with the phone being powered down and continue to hold them untill something shows on the screen?
if your phone is not seeing the volumes buttons you are one of the very unlucky few that had a problem at the most inopportune moment.
there is also a way where you hold all three buttons till the phone reboots twice, or something. let me try it and ill give more specifics.
Click to expand...
Click to collapse
Yes, that's exactly correct. I do this:
1. everything pulled (battery, USB, sim, sd)
2. Open Oden (1 click)
3. Install battery
4. hold down (and keep holding) volume up and volume down
5. insert USB cable
6. depress (i.e. don't hold) power button
Goes straight to battery charging indicator.
If I swap #6 with holding the power button down, it continually reboots while just barely showing the battery charging indicator. I've tried letting go between black screens on the 1st, 2nd, 3rd, 4th, and 5th black screen. Still no android dude with the shovel.
Try all the steps you stated but not the last one where you press the power button. Don't press the power button.
newter55 said:
Pull the battery, open odin, plug usb into computer, hold vol up and down, plug usb into phone still holding vol buttons, drop in battery still holding vol buttons, when dl screen pops up and yellow com port lights up in odin release volume buttons. Do not touch power button at any time
Swyped...and sorry I don't proofread
Click to expand...
Click to collapse
Goes straight to battery charging.
johnny13oi said:
Try all the steps you stated but not the last one where you press the power button. Don't press the power button.
Click to expand...
Click to collapse
Goes straight to battery charging.
Pull out battery for 10 seconds, hold volume up + down, connect usb into other usb port.
Sent from my GT-I9000 using XDA App
Seriously, try adb. It works wonders.
Sent from my SAMSUNG-SGH-I897 using XDA App
10tonhammr said:
Have you tried rebooting into recovery mode instead of download mode? Stock recovery is adb-ready and you should be able to adb reboot download. Its a long shot if you're having problems using button combo to get to d/l mode, but it's probably still worth a shot at this point.
If you were able to use 3 button combos before all this happened, and did NOT have to install the 3 button combo fix, its strange you don't have access to it now... Could restoring a Rogers Cappy to AT&T stock be the problem?
Click to expand...
Click to collapse
Trying to get into recovery mode gets me the at&t logo and the "jingle", but no recovery mode menu to reboot, etc.
This is what I'm worried about, restoring the Rogers stock over top of the Odin 1 click restore (which is an AT&T image) has bricked it and prevents download mode from invoking.
fatttire said:
Seriously, try adb. It works wonders.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I know, I played with adb before I bricked it. ADB needs to "see" the phone, it no longer sees it (I have three computers, all three can't see it, but they can see my friends cappy with no problems first time, every time). Same process for his phone works every time to get into download mode, but not on mine.
And yes, have tried other USB ports on the same computer, both on the mainboard, and on the front ports.
Keep the ideas coming though please, I will try every one.
timmy22 said:
I know, I played with adb before I bricked it. ADB needs to "see" the phone, it no longer sees it (I have three computers, all three can't see it, but they can see my friends cappy with no problems first time, every time). Same process for his phone works every time to get into download mode, but not on mine.
And yes, have tried other USB ports on the same computer, both on the mainboard, and on the front ports.
Keep the ideas coming though please, I will try every one.
Click to expand...
Click to collapse
There's a trick to prompt download mode through a "jig" which you can hack together for about $2 in parts and a sacrificial microUSB cable...it works on the other SGSes, but I think it should work on the Captivate as well. Never tried it personally...
Merlin_reloaded said:
There's a trick to prompt download mode through a "jig" which you can hack together for about $2 in parts and a sacrificial microUSB cable...it works on the other SGSes, but I think it should work on the Captivate as well. Never tried it personally...
Click to expand...
Click to collapse
I work in a tech shop so have access to electronics, sacrificial cables, soldering irons, resistors, caps, etc.... could you point me in the right direction?
Oh, nevermind, found it in the i9000 forum. Will test first thing in the morning!
Cheers,
I bricked one today as well. Exactly what you are talking about here. The only thing is that i was still under the 30days so i swapped it out for a new one. As of right now ive been debating whether i want to do the voodoo fix (which i think is what bricked it to begin with)

[Q] Help me turn my Captivate off!

So here is the situation:
My power button is non-functional. This happened before, and I was able to press very firmly on the power button to access a shut down menu and turn off the phone. From this, I was able to enter download mode (pressing volume button while inserting USB) and go back to stock, which surprisingly, fixed my power button. I thought this nightmare was over.
Now, my power button has stopped working again (ICS hacksung 5.0). No matter how much pressing, prodding, whatever, I cannot get the power button to turn off the phone.
I cannot find any adb commands to turn off phone.
"adb reboot download" simply restarts the phone, no download mode. (adb does recognize the device)
If I take out the battery, as soon as I put it in the phone boots up.
If I am pressing any of the volume buttons when I put the battery in, I can access recovery mode (But cannot select anything because power button is still broken)
Any ideas? I doubt my phone is still under warranty (1.4 years old) and I do not have mobile insurance.
Thanks for any help in advance
Depending on what recovery u have (cwm or ?), U can use the capacitive buttons, while in that revovery, to navigate and select the power off option.
Sent by XDA Premium App
Thats a neat tip that I didn't know about, but I can't find any option to power off? Sorry for being retarded but I have given this time I promise
cwm recovery is what I have installed atm
Reboot to CWM and Power off option may be at the bottom of the 1st screen that u come to. That is dependent on what version of cwm u have though.
Quick boot from the market, you can place a poweroff button directly on the home screen
Sent from my SAMSUNG-SGH-I897 using xda premium
The ICS ROMS CWM recovery doesn't have power off choice, so he can't do that.
Sent from my SGH-I897 using xda premium
Unfortunately the quick boot "power off" option simply froze my phone, or restarted it.
I let my battery drain so that I could get a dead phone (that part worked), but when I hold my volume buttons and plug in the USB for download mode it goes to the "battery" screen or (if both are held down) recovery. No download mode.
In recovery "key test" the power button fails to register any key press, but it is not spamming either. This seems like a hardware problem, but I am not sure how it was fixed when I flashed back to stock before if that is the case
I will next try making a download mode jig, I'll let you guys know how it goes...
My cousin had the exact same problem less than a month ago.
I see you tried reboot download through adb, have you tried it using the same command, but using android emulator from market? That worked for her phone so worth a shot.
its a far shot but odin is now available for use on the phone itself and works on our phones. maybe you can find a kernel thats had the buttons reconfigured. i know darky has one somewhere.
StaticMatt said:
My cousin had the exact same problem less than a month ago.
I see you tried reboot download through adb, have you tried it using the same command, but using android emulator from market? That worked for her phone so worth a shot.
Click to expand...
Click to collapse
Thanks for this idea, when I use
#su
#reboot download
the phone simply reboots. Same thing happens in "Quick Boot" 's "Bootloader" reboot option. This phone just seems broke as hell.
Firstly, this power button problem is a lot more common than you would think. It is most often a hardware failure - I mean the button mechanism (springs etc. just dies). Google it to see how common.
Your post suggests a clue: If just putting the battery in reboots the phone, then the power button may be stuck in the "in" position.....so it is always getting "pushed". Then anything you do would mean ht epower button is already being pressed. If this is the case, you will never get a software solution ???
Also, I absolutely do not mean to be nasty. But if you search both Q&A and General sections there are previous threads with this button problem. Many other solutions have been posted and it will be difficult to list them together.
Finally, you can actually replace - yes, replace - the button yourself. Google/you tube has it.
http://www.globaldirectparts.com/Samsung-Captivate-i897-Replacement-Repair-Parts-s/6412.htm
http://forum.xda-developers.com/showthread.php?t=1206459
Hope this helps !

Nexus 7 4.2.2 bricked

My nexus 7 android 4.2.2 bricked. I am not able to start it in recovery mode. After start it shows black screen and failed to show google logo. Please help me.
Thanks in advance.
Mehrab
mehrab.nexus said:
My nexus 7 android 4.2.2 bricked. I am not able to start it in recovery mode. After start it shows black screen and failed to show google logo. Please help me.
Thanks in advance.
Mehrab
Click to expand...
Click to collapse
Hold down power button with charger plugged in for 30-40sec.
Sent from my LT26i using xda app-developers app
And bricking usually implies you did something to it; so what lead up to this?
And I agree; I suspect your battery is just dead. If you haven't yet, leave it on the charger for a few hours.
mehrab.nexus said:
My nexus 7 android 4.2.2 bricked. I am not able to start it in recovery mode. After start it shows black screen and failed to show google logo.
Click to expand...
Click to collapse
Mehrab,
Your sentence above is a little vague - I think you are saying that you can not get into bootloader/fastboot mode, and from there you can't subsequently get into recovery mode. Is that what you are saying?
It is possible that the tablet is simply in APX mode; to exit out of that, hold the power button down for 13-20 seconds. Get ready! As soon as you see the Google logo appear, you need to immediately press the Vol-Down button (within one or two seconds).
It doesn't seem to be well understood by N7 users, but when a hard reset is performed by pressing & holding the power button, the Tegra3 SoC always attempts to invoke the bootloader. It doesn't matter what mode you are starting from! (although it does seem to take a different number of seconds, depending on starting conditions)
That black and white Google logo is the bootloader - giving you a 1-2 second opportunity to hit the vol-down button to enter fastboot mode... rather than defaulting to a boot of whatever is in the boot partition.
So - if you can get the Google logo to appear through any means, be ready and press vol-down quickly!
If you can not get that logo to appear, for the moment you are out of luck as APX mode has not been exploited successfully at this time.
Good luck.

Locked up phone, holding power not rebooting

I am on CleanRom and flashed OMJ's mod pack. CleanRom for what ever reason listed that he removed the fast reboot option. When I flashed the mod pack this option was restored. Right after first boot, my wallpaper didn't load (using landscape wallpaper app) This has happened before and a quick reboot fixes it. Well, selected hot reboot instead of full reboot. Shell rebooted, boot animation ran, then stopped at the cleanrom logo. The phone will not boot, is not recognized as adb access and will not reboot from holding the power button. I eld the power button for about 5 minutes, the capacitive buttons flash but it never reboots. When connected to pc with windows 8 adb does not connect. I am using koush's universal adb driver and adb and fastboot normally function fine. When my phone is connected it shows ad "android phone" in device manager but drivers are not installed. Pointing it towards the universal driver folder does not work and searching automatically does not work either. I'm planning on letting the battery die then trying to boot again unless anyone has any better ideas?
never mind, manually installed the driver and got adb to connect and was able to reboot
Next time, Place the phone under a Bright light and hold the power button. Not kidding, it works and mentioned various places here on this forum. Question 17
I guess that trick is our replacement for the battery pull
naturecannon said:
Next time, Place the phone under a Bright light and hold the power button. Not kidding, it works and mentioned various places here on this forum. Question 17
I guess that trick is our replacement for the battery pull
Click to expand...
Click to collapse
Interesting. I'm gonna re-lock it up and try that! Just out of curiosity.
EDIT: huh, that actually made a difference. Just holding the power button and it wouldn't reboot, put it directly in front of a light bulb and held the power button and it rebooted.
DomSim said:
Interesting. I'm gonna re-lock it up and try that! Just out of curiosity.
EDIT: huh, that actually made a difference. Just holding the power button and it wouldn't reboot, put it directly in front of a light bulb and held the power button and it rebooted.
Click to expand...
Click to collapse
It's so it doesn't reset in your pocket etc for any reason.
Sent from my HTC One using xda premium

Categories

Resources