Anyone else experience problems/issues waking up the phone via the power button after flashing Telus roms based of Mr. X's stock rooted no ciq?
It acts as if the power button is broken and needs to be pressed several times before it reacts.
I do not get this with the stock Tmobile rom.
I am wiping data cache and dalvik before flashing, not installing any apps, not customizing, not even login to google on an SGH-T989.
Thanks,
-CC
Related
i just flashed beastmod and when i power off the phone ends up rebooting evrytime
i was wondering if anyone has a fix for this...
(yes i searched the forum for answers but they were for diff phones, and the fix didn't work for me, i think the fix may be device specific)
anyone...?
so your phone wont boot? your stuck in a bootloop?
i would recommend reflashing, did u factory reset, format cache, dalvik, fix permissions?
yea i figured out the issue was the kernel i flashed. i flashed faux kernel 6u on beastmod4.2 and this started happening. the issue is when i hold down the power button and select power off it would just reboot, i also selected "reboot into recovery" and it also perform a normal reboot. basically the only way to power off my phone and get into recovery was to pull the battery out
I wasn't sure if I need to add reply to one of the topic or have similar topics. So I am creating new thread.
Hello,I have wind S3 T999V.
Before, the phone did not reboot constantly. It is just few days ago, the phone is reboot constantly.
There is enough battery and I did not click on power button to turned off the phone.
Sometimes, if I am in browsing or open the app, it sometimes turned itself off. Also, sometimes, when I click the power button, the menu interfaces for turn off, reboot come out several times and go turned off itself instantly. Then when I need to turned on again, it reboots several times stuck in boot menu and the phone is on.
So, what I did is since this is rooted phone, I backup my rom, clear cache/data, and install 4.3 Touchwiz StockMod custom rom with 4.3 modems. At first, I thought the problem has solved. After restore apps and used for few hours, the phone now has same problem again. At this points, I am thinking it may be phone itself has problem.
What steps should I need to try out?
Please do Factory Reset. Do Not restore any apps or install any either. See if the problem repeats.
I tried leave my phone with factory reset and no apps for overnight. Also, I am in safe mode for the phone.
Actually, with no apps and factory reset, I think it does randomly shut down as well.
However, as I play with power button, sometimes, the screen does not shut down and turned on twice or sometimes, power options prompt come out.
Your Power button is likely defective or broken. I suggest have it looked at in a service center.
Hello everyone, first time posting but I have been on the forums for some time now.
I have searched, but now my issue is more specific so I wanted to post about it.
I am running Cyanogen Mod 11 from around december time 2013.
Tonight out of the blue my device has been restarting and staying turned off, no indications previous and no new apps or recent changes etc. I looked up these issues and it points to the power button being stuck.
-I replaced the battery with a different one
-Booted into clockwork mod, trying to navigate to wipe cache etc and it would reboot the device before I made it there (did this many times)
-Trying to boot it normal and it wouldn't make it far without a reboot
-Took the device apart and cleaned up etc, took out the battery and held power and tried again (many times). No avail.
-Looked online for replacement buttons and saw what I would need to do, so I tried to unsolder the power button but to no avail.
This is where things looked up!
-Turned the device on and booted into CWM and did a backup successfully!
-Wiped devilk cache and normal cache (mind my spelling please), and rebooted.
-Made it to the starting up the apps (from the devilk wipe), and to the main screen to see "shutting down" as if the power button was still being pressed.
-Tried again many times, but still the same result.
-Did a key test in CWM and it doesn't show the power button being pressed, unless I press it (all other buttons worked fine).
So that is where I am at, I tried to do a reinstall of cyanogenmod with the windows installer but it wont detect it as before. Any suggestions? Thanks!
What bootloader are you on? I would restore to stock for your current version of bootloader or newer by ODINing the stock tar. Then try the CM process again.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
My wife's old S3 was given to me to use. I had originally flashed CM 11 on it and tried to upgrade to CM 12.1. In doing so I accidentally forgot to flash GAPPS.
I reverted to the stock ROM via Odin but now I'm stuck in a boot loop. The best part? The device's power button does not work and I cannot make any selections within the stock recovery to clear the cache and reset to factory settings.
Can anyone help me?
Pull the battery to turn off the phone and put it back in. If you feel the phone power up by vibrating upon putting the battery in and not touching the power button and go into loop then you have a bad power button. Do you have this problem? If so, then your only options are repair or remove the power button (there is an alternate way to power the phone up). Let us know if it is a bad power button or not so that hardware issues can be accounted for and go from there.
NOTE: The S3 has been known for some time now to have power buttons that fail. Mine did, and I opt to remove mine as I could not justify paying for a repair when the S3 is my backup phone and test platform and I have a method to power up. I use widgets for controlling power off, restarts, and recovery once powered up.
I no longer have a power button either and recently encountered this same issue after using Odin to flash a stock image.
My solution was to flash TWRP recovery using Odin, which allows one to perform operations using touch instead of the power button.
Gargat said:
I no longer have a power button either and recently encountered this same issue after using Odin to flash a stock image.
My solution was to flash TWRP recovery using Odin, which allows one to perform operations using touch instead of the power button.
Click to expand...
Click to collapse
That works. Glad you found a way to get through it.
n_alvarez2007 said:
My wife's old S3 was given to me to use. I had originally flashed CM 11 on it and tried to upgrade to CM 12.1. In doing so I accidentally forgot to flash GAPPS.
I reverted to the stock ROM via Odin but now I'm stuck in a boot loop. The best part? The device's power button does not work and I cannot make any selections within the stock recovery to clear the cache and reset to factory settings.
Can anyone help me?
Click to expand...
Click to collapse
Bootloops have not been uncommon when reverting from LP to KK. Once you have flashed TWRP as others in the thread have suggested, you will probably need to wipe/ format the internal sdcard. The other remedy some have posted is to load a stock recovery and do a factory reset from within that stock recovery.
Not sure how to get into recovery without a power button.
Is the button loose or not functioning at all? You could try opening the phone and removing everything from the frame and see if the power button functions.
I haven't tried this with my SGS3, but on my Acer tablet I have booted into recovery using adb and fastboot. This requires connection to a computer, but not a power button. Unless you have a touch version of a custom recovery installed you still would not be able to select an item.
You may be able to flash a custom recovery using adb. I had broken my stock recovery on that tablet and used fastboot to reflash a working stock recovery.
Mostly happens through the night while charging but happened today while using it. This began after updated to June stock update. Is this happening to anyone else?
tinroofrusted said:
Mostly happens through the night while charging but happened today while using it. This began after updated to June stock update. Is this happening to anyone else?
Click to expand...
Click to collapse
Just wipe the phone and reinstall a stock image from Google. If (for some insane reason) you haven't unlocked your bootloader, do a factory reset (you will lose all your data) and it'll work like brand new again. To do a factory reset, power off your phone and hold in the volume down + power buttons until the bootloader screen appears. Using your volume up and down buttons, choose Recovery from the list of options and click the power button. On recovery screen with broken android, hold down the Volume Down key, and while holding it down, click the Power Button. You have to try this a few times to get it to work, but it will unlock a menu of options, one of them being to do a factory reset, wiping system data and userdata and the cache.
Yes my bootloader is unlocked and I'm rooted using Magisk. I was wanting to avoid wiping everything bc it's a pain to set things up again. Is there a way to run a logcat and figure out what is causing it to crash? Not sure if that is possible seeing that it happens so randomly. It all started when I flashed an ota with twrp...I usually don't update that way so I'm guessing something went wrong with that. I have since updated again using the full system image and removing the -w from flash.bat but still getting the same problem.
Thanks for responding.