Related
Can someone help me wipe my phone from recovery b/c i cant see anything on the screen but i do know the phone works and responds to touch?
I just need someone who can tell me exactly where to scroll in recovery to get to the wipe data/cache option.
Any help is very much appreciated
Unfortunately it may not be possible to help you navigate blindly because Clockword Recovery has a feature that places the confirm option among 10 choices to prevent accidental clicks. But from repeated tries it seems to come up in the same spot for me, so hopefully it might work for you.
So I can suggest that once you boot into recovery (volume down + power) and do the following.
- Press volume down 3 times and press trackpad, very very gently. Sometimes it registers a single click as two if you hold it for too long.
- Press volume down 7 times and press trackpad to confirm.
If it you select one of the "No" options on the confirmation page it will spit you back out to the main menu. So you press volume down 3 times, trackpad, volume down 7 times, trackpad.
Are you sure wiping your cache will resolve the issue you are having? It sounds like a screen defect or perhaps a resolution issue? Have you messed with your build.prop? If it doesn't work you may need to do some additional work from adb shell.
Thanks for the reply. I will try this as soon as I get back from class. I think it's a screen defect because the phone was working perfectly fine and when I came back to my phone after 10 minutes all I saw was a blank screen with the backlight on. I haven't messe with the build.prop. I have messed with the LCD density a couple times but I don't think that's what cause this issue. I just wanna try to clear all data I have on the phone so I can try to exchange it at a tmobile store lol. I know it won't fix the screen issue.
Thanks for helping. I'll see if it works. I do remeber that confirming wipe data and cache would also be the 7th option repeatedly.
Can you get into Fastboot?
Carloswithac said:
Can you get into Fastboot?
Click to expand...
Click to collapse
im not sure. i cant see anything on the screen
so, my rom did not back up and my phone on regular power on just stay on white sceen displaying htc, when i try recovery it says no images. i have a back up G2 and i am looking for a way to save the proper to the sd card so i can boot back up. any feedback would be awesome. thanks
O and I'm s on, so I guess I'm not rooted
Sent from my T-Mobile G2 using the XDA mobile application powered by Tapatalk
So I went into the T-Mobile store and got my g2 replaced
Jmsbishop, I'm new to this but ima try searching around and see what I can figure out to help you out.
Sent from my T-Mobile G2 using XDA App
Hey guys! I recently updated my phone to 4.1.2 and noticed almost every time I go to use my phone and hit either the power button or the home button the recent app screen pops up instantly as if you were to hold the home button down. So far I tried a soft reset a factory reset with no luck. The phone worked perfectly before the update so I know it isn't either of the buttons sticking. If anyone has any ideas I would greatly appreciate your help, I'm at the point where I'm pulling my hair out haha
Thanks!!
Did you do the OTA (over the air) update Sprint pushed out, are you on a custom rom, or are you using a non stock launcher? Give us some details and someone, if not me, will help you out.
Also try rebooting. Some users in the past have reported that trying to activate recent apps properly (by holding the home) stopped working and a simply powering the device off then turning it back on fixed the issue. This may solve your issue too.
I see this is your first post, are you familiar with rooting and custom roms? Just curious so we know how to get you through this.
Thanks for helping. I did the ota update that sprint pushed out. The phone is completely stock nothing on it is modified at all. I already tried rebooting multiple times and tried a battery pull also. I am new to rooting and custom roms. Everything else on the phone is working fine but the recent app screen will come up as soon as I turn the screen on. It wont come up if I turn the screen on hit home to go to home screen turn screen off using power button and turn the screen back on quickly, it has to sit for 30sec to 1min for it to start doing it again.
Thanks!!
thatjerk said:
Did you do the OTA (over the air) update Sprint pushed out, are you on a custom rom, or are you using a non stock launcher? Give us some details and someone, if not me, will help you out.
Also try rebooting. Some users in the past have reported that trying to activate recent apps properly (by holding the home) stopped working and a simply powering the device off then turning it back on fixed the issue. This may solve your issue too.
I see this is your first post, are you familiar with rooting and custom roms? Just curious so we know how to get you through this.
Click to expand...
Click to collapse
Anybody got any ideas?
Sorry for the late reply, I work a night shift.
Are you waking the screen up with the home button or the power button. The reason I am asking is because the only way I can make this same situation occur is with no lock screen set, I wake up the phone with the home screen button.
Try setting up a lock screen and see if it fixes the problem.
If it does not fix the problem then I recomend taking the phone back to Sprint to see if they will swap the device since you are not rooted.
If you have a custom recovery installed try rebooting into recovery and wiping cache and dalvik cache then go to advanced and fix permissions, if you only have stock recovery try wiping cache from it. To boot to recovery, power off phone, hold volume up and home then power, let go of the 3 keys when the note 2 splash screen pops up. If that doesn't alleviate the issue it may be a setting with the home key presses, for instance you can change what it does with longpress and double tap, may have gotten the svoice and recent apps mixed up. Try double tapping home and see if svoice comes up or recent apps, also longpress to see which comes up.
I like to break stuff!
-EViL-KoNCEPTz- said:
If you have a custom recovery installed try rebooting into recovery and wiping cache and dalvik cache then go to advanced and fix permissions, if you only have stock recovery try wiping cache from it. To boot to recovery, power off phone, hold volume up and home then power, let go of the 3 keys when the note 2 splash screen pops up. If that doesn't alleviate the issue it may be a setting with the home key presses, for instance you can change what it does with longpress and double tap, may have gotten the svoice and recent apps mixed up. Try double tapping home and see if svoice comes up or recent apps, also longpress to see which comes up.
I like to break stuff!
Click to expand...
Click to collapse
This is deff recent update caused i believe. I also have a non rooted sprint device that I just updated, and its doing the exact same thing. Annoying as hell. My device is less then a month old. To explain more on what happens, I have my screen timeout set for 2 mins, lock at 5 mins. Use phone, put it down, wait for screen to time out, pick it up and hit him key once and it brings up the task manager. Not a long press, just a fast press.
I tried to clear the cache with no luck..
I guess that makes two of us for this problem.
I have noticed sometimes when I go to use the phone there will be a blue box around one of the apps. Not sure if its the last app I used but it has been doing this since before the update.
I cant replicate the issue to save my life. When you guys updated something must have gotten confused in the process. May need to download a stock restore of ma7 and start fresh. That would be what I would do if nothing else fixes it. It will erase all you apps and settings and internal storage so back em up. Back up internal to PC
I like to break stuff!
Ok ill be more than happy to try that.. what exactly is ma7 and where can I dl it. Is there anything special I need to know or do to complete the process? I already cleared my my contacts.. google said they were uploaded but apparently not.
Thanks again for the help!!
-EViL-KoNCEPTz- said:
I cant replicate the issue to save my life. When you guys updated something must have gotten confused in the process. May need to download a stock restore of ma7 and start fresh. That would be what I would do if nothing else fixes it. It will erase all you apps and settings and internal storage so back em up. Back up internal to PC
I like to break stuff!
Click to expand...
Click to collapse
MA7 is the latest OTA 4.1.2 which would be the update you took prior to this recent apps incident. Look in development for a thread by garwynn it'll have the links to the Odin one-click packages and since you already took OTA you won't need the modem. Just follow the directions in his thread. Before doing it if you have anything stored to your internal storage you want to save back it up to your PC via USB. You'll want to grab the full restore one click so it wipes everything and starts fresh.
I like to break stuff!
Same issue, called Sprint
I spoke with sprint about this today, very frustrating. I learned:
Not all note users are having this problem
they did a reactivation, prl update, firmware check, profile (?) update.
That didn't do anything, so the recommended a hard reset, that's when I flipped out.
They said I may be able to sent me a new phone if the hard reset doesn't help, but would need to pay a $49 exchange fee... then i flipped out more.
possible reasons: I really don't know, here is what i have:
Go Launcher
SD card, inserted a couple weeks after activation
I use Home2 to modify my home button double tap action
Not rooted or anything.
david.dannicker said:
I spoke with sprint about this today, very frustrating. I learned:
Not all note users are having this problem
they did a reactivation, prl update, firmware check, profile (?) update.
That didn't do anything, so the recommended a hard reset, that's when I flipped out.
They said I may be able to sent me a new phone if the hard reset doesn't help, but would need to pay a $49 exchange fee... then i flipped out more.
possible reasons: I really don't know, here is what i have:
Go Launcher
SD card, inserted a couple weeks after activation
I use Home2 to modify my home button double tap action
Not rooted or anything.
Click to expand...
Click to collapse
I'm still having the same issue with recent apps popping up upon awake, non rooted sprint, happened after recent OTA update, and have no apps in common with above poster. I have not done a reset yet as it hasn't bothered to that extent yet, and once I get ready to root and really tear into things, ill work it out then I suppose.
I'm having the same issue after updating to MA7. Im rooted, cleared both caches and still going on. When I wake the phone with the home button it wakes up and shows the recent apps, when I close that it take me to my lock screen (wigetlocker)
Edit: Fixing permissions just fixed it for me and also clearing the caches again.
Double Edit: Started doing it again. -___-
nyboy07 said:
I'm having the same issue after updating to MA7. Im rooted, cleared both caches and still going on. When I wake the phone with the home button it wakes up and shows the recent apps, when I close that it take me to my lock screen (wigetlocker)
Edit: Fixing permissions just fixed it for me and also clearing the caches again.
Double Edit: Started doing it again. -___-
Click to expand...
Click to collapse
I am having this problem to it happens when the screen goes off but does not lock in my experience. I would never pay for a new phone if it is a update that messed my phone up I would have snapped
Sent from my Nexus 7 using xda app-developers app
Solved
I have the Note 2 on Sprint. The update that I got a couple days ago has solved this problem.
Hey guys,
So I've got an S3 running AOKP at the moment and I was wondering if there was any way to disable the power button. It's been malfunctioning, and causing my phone to reboot constantly. Sometimes even when off it continues to think I'm holding down the power button and cancels the boot process...
Any ideas of a workaround? I'm out of warranty and can't want to pay for repairs at the moment.
S3 power button boot loop (sudden death?)
poacherD said:
Hey guys,
So I've got an S3 running AOKP at the moment and I was wondering if there was any way to disable the power button. It's been malfunctioning, and causing my phone to reboot constantly. Sometimes even when off it continues to think I'm holding down the power button and cancels the boot process...
Any ideas of a workaround? I'm out of warranty and can't want to pay for repairs at the moment.
Click to expand...
Click to collapse
Hi,
I am having the exact same issue. Very strange as it decided to do this while checking my email (finger no where near the power button) and I have never had any issues prior to this.
I'm running CWM, CM10.2 and I CANNOT BOOT into recovery (CWM) or ODIN, best I got was the CM loader screen then it reboots.
Even if I disconnect the battery, wait 30 minutes (fully charged) and replace the battery, it attempts to boot itself again. and again and again...
The best videos I've seen involve smacking the phone on the power button side (not going to do that, at least hard) I think it may be a random power button failure. I will be disassembling the phone tonight and trying to open or close the power button contacts and wipe my phone before it goes back....
Yoiks!
mc045 said:
Hi,
I am having the exact same issue. Very strange as it decided to do this while checking my email (finger no where near the power button) and I have never had any issues prior to this.
I'm running CWM, CM10.2 and I CANNOT BOOT into recovery (CWM) or ODIN, best I got was the CM loader screen then it reboots.
Even if I disconnect the battery, wait 30 minutes (fully charged) and replace the battery, it attempts to boot itself again. and again and again...
The best videos I've seen involve smacking the phone on the power button side (not going to do that, at least hard) I think it may be a random power button failure. I will be disassembling the phone tonight and trying to open or close the power button contacts and wipe my phone before it goes back....
Yoiks!
Click to expand...
Click to collapse
It's very random for me too. Sometimes it'll work all day then it'll take like an hour and a half to turn back on.
Quick question, as I've heard this from a couple people. Do you use an otter box?
Regardless I'm 90% sure this is hardware related and has nothign to do with software, because all the cases I've heard of this have had different roms, one of which was stock unrooted.
Pretty frustrating. Not sure I'll buy a Samsung again to be honest.
poacherD said:
It's very random for me too. Sometimes it'll work all day then it'll take like an hour and a half to turn back on.
Quick question, as I've heard this from a couple people. Do you use an otter box?
Regardless I'm 90% sure this is hardware related and has nothign to do with software, because all the cases I've heard of this have had different roms, one of which was stock unrooted.
Pretty frustrating. Not sure I'll buy a Samsung again to be honest.
Click to expand...
Click to collapse
This started gradually happening to me too and I bought both my phone and Otterbox in July 2012 when it came out. I noticed with my family members' S3's that their Otterboxes were different in regards to the power button (it stuck out more) whereas mine hardly stuck out at all. I got a warranty replacement this past July (2013) and the exact issues you described began happening. It started out as random reboots and as of yesterday, I can't get my phone to boot because it thinks I'm holding the power button down (therefore not letting the boot process finish). I took my phone apart, expecting the power button to be an easy swap like it was in the GS2, but no, it's a part of the friggin motherboard. I also am looking for a way to disable the power button. I'd recommend that if you are able to get it to boot even once, that you make sure to backup all your stuff. Fortunately all my pics are backed up since I can't boot my phone anymore, but other files are currently inaccessible. I wonder if anyone knows if some sort of electrical tape or something could prevent the power button signal from transferring so that we would be able to boot our phones?
I had the same power button issue with my Captivate as well... and thought that issue had been looked into. After 14 months of use on my S3, I noticed this issue appeared.
Solution (well not quite): change key layout to disable power button. Re-map volume down as "power, wake". Yes, by doing this, I am losing volume down button. Also, when the phone is off, I still need to press the power button to power it up. My fix of changing the key layout file won't take charge until after the phone boots up.
I have installed CM 10.1. Occasionally the screen will not turn on when I press the power button. I have to hold down the button for 10-20 seconds to reset the device to get it to power on. Happens at least 3-4 times a day. Anyone else have this issue or ideas on how to fix it? Thanks.
Stuke00 said:
I have installed CM 10.1. Occasionally the screen will not turn on when I press the power button. I have to hold down the button for 10-20 seconds to reset the device to get it to power on. Happens at least 3-4 times a day. Anyone else have this issue or ideas on how to fix it? Thanks.
Click to expand...
Click to collapse
No one else has seen this issue?
Many ROMs have their little quirks here and there, this could be one. I use hashcode's ROMs so this is just speculation though.
I had this issue with twa_priv's rom. If I keep at the button, pushing it multiple times at different intervals, it would eventually come on. Interestingly, if I went into the developer options and put the CPU at the full 1200MHz, it didn't happen.
Not having this issue with CM (though I'm running 10.2) so not sure there.
This was a common occurrence in cm10.1 with TWA_priv's build I believe. This is called a Sleep of Death or SoD. I thought that was cleared up, but maybe not. If there is a newer version of the ROM that you are on, I recommend trying that. There is no way to recover from an SoD except to force power off like you did, and start back up.
Sent from my Nexus 7 using Tapatalk
Hey,
I have been experiencing a bit of weird bug with my Nexus 7 2013. Basically, when I go to use my Nexus after it has been idling for a little while, it will often be on when I open the tablet from its case. However, it does not display any typical Android elements but shows only a lit black screen...I have to hard reset it to get it back to normal function...
Any ideas? Very perplexed....I have tried different kernels and factory reset several times.
--Android 4.4.4 (Rooted)
--Kernal: Faux Kernel 22u/Franco R17
One thing to note: I can replicate the behavior by quickly pressing the power button several times. It goes right into the 'lit black screen' and needs to be reset.
Thank you!
dsudi19 said:
Hey,
I have been experiencing a bit of weird bug with my Nexus 7 2013. Basically, when I go to use my Nexus after it has been idling for a little while, it will often be on when I open the tablet from its case. However, it does not display any typical Android elements but shows only a lit black screen...I have to hard reset it to get it back to normal function...
Any ideas? Very perplexed....I have tried different kernels and factory reset several times.
--Android 4.4.4 (Rooted)
--Kernal: Faux Kernel 22u/Franco R17
One thing to note: I can replicate the behavior by quickly pressing the power button several times. It goes right into the 'lit black screen' and needs to be reset.
Thank you!
Click to expand...
Click to collapse
What do you mean by 'lit black screen'? It sounds like a hardware problem to me.
-----------------------------------------------------------
Don't Say Thanks.
Press The Thanks Button.
DEVICE:
Nexus 7 2013 LTE (DEB)
Stock 4.4.3 KUT84L
Stock Kernel
I have the same problem with my nexus 7 2013. It happens very often. When the screen was turned off for a while, it won't react to anything and the screen stays black, but the notification led is still active. The only thing that helps is pushing the power button very long. Then the Google logo shows up and it boots up normally. The tablet is on original Android 4.4.4 not rooted.
I will ask for an exchange in the next couple days.
gaschue said:
I have the same problem with my nexus 7 2013. It happens very often. When the screen was turned off for a while, it won't react to anything and the screen stays black, but the notification led is still active. The only thing that helps is pushing the power button very long. Then the Google logo shows up and it boots up normally. The tablet is on original Android 4.4.4 not rooted.
I will ask for an exchange in the next couple days.
Click to expand...
Click to collapse
Great haha. I know that I am not the only person with this problem now ...So you think it is hardware related and not software?
If so, UGH! I've already had to sent this POS in twice now .