ClockworkMod Recovery autoboots when I plugged in my cable for charging while my phone is off. Any idea how to turn it off such that the only way I will boot into clockwork mod is either by Rom manager or power+vol down?
the way DHD is designed is it will display charging animation if the phone is switched off. and that charging animation is part of stock recovery. since CWM replaces stock recovery, charging with phone off will load CWM. i don't think you can do anything about that unless some new CWM came out with that fix
Related
Hi,
ive recentley s-offed, got clockwork recovery mod, root, and flashed cyanogenmod 7.1.0.1. Alls been running great but ive got one question. I have done a search an the answers have been a bit flakey. When i power my phone off i then plug in to charge. The red led comes on like it should. I unplugg the charger the led stays on. The phone doesnt power on until battery is removed and charger cable. Im not sure but according to the other posts i searched its something to do with the recovery so heres my clockwork mod version : Revolutionary CWM V4.0.1.4
Thanks
Roshurwill
Yes it is CWM which contains this bug. Update to 5.0.2.0. The LED colour will still remain bugged (It will remain amber. Won't turn green when the phone is fully charged) but the phone will turn on normally.
so i just flash it like a normal zip file, install zip from sd card, choose zip and done?
thanks
roshurwill
No. Read this post, under the heading Custom Recoveries:
http://forum.xda-developers.com/showpost.php?p=12782368&postcount=2
thanks all sorted now
I was running AOKP for a few days and I decided it wasn't going to work for me. So, I reboot into recovery, wipe everything and restore my CM7.1 backup. The CM 7.1 backup restores just fine. I boot the phone once to make sure it works and it does. I then immediately reboot into recovery so I can install gapps. Booting into recovery hangs for a minute so I pull the battery and try to boot into recovery. This is where the problem arrises. The phone doesn't boot into recovery unless it is plugged into the USB. After selecting the recovery option in the bootloader, the screen goes black, vibrates 4-5 times and the green LED flashes. Also, the phone will no longer boot into the CM7.1 backup. If I restart the phone, the white HTC EVO screen displays and then the same vibrate/screen/LED issue happens again.
Can someone point me to the right direction for fixing this?
Hello,
I've got a Problem with the charging Screen when the phone is turned off:
The first time I installed KitKat Version of Android on my phone, there was an error and I had a corrupted System and recovery. So I installed the new bootloader and TWRP Recovery again and restored my backed up Rom.
Everything worked again, except the charging Screen that appears when you plug your phone in, while it is turned off (battery with black Background). It only Shows the loading circle and freezes then. If I hold the power button it doesn't turn on, but restarts the charging mode and freezes again.
Is there any way to restore a functional charging mode Screen?
P-Froggy said:
Hello,
I've got a Problem with the charging Screen when the phone is turned off:
The first time I installed KitKat Version of Android on my phone, there was an error and I had a corrupted System and recovery. So I installed the new bootloader and TWRP Recovery again and restored my backed up Rom.
Everything worked again, except the charging Screen that appears when you plug your phone in, while it is turned off (battery with black Background). It only Shows the loading circle and freezes then. If I hold the power button it doesn't turn on, but restarts the charging mode and freezes again.
Is there any way to restore a functional charging mode Screen?
Click to expand...
Click to collapse
I had this problem when I installed an AOSP Rom. Does your backup include the system partition?
If not, reinstall stock Rom or any TouchWizz Rom.
Hope it helps. ^.^
I had installed 'blackhawks next kernel' for dual-booting.
I had CM11 on partition 1 and Stock Samsung on Partition 2.
I decided I want to simply revert to a single partition with the stock Samsung.
I booted into partition 1.
I used Phils to install 'GT3_MH2_STOCK_Kernel_SM-t310_Tab3.zip'
When the machine rebooted, it jumped into the Cyanogen Mod boot sequence, and just loops.
If I try to turn the machine off to boot into recovery, the Tab doesn't shut down - it just reboots.
Trying to 'time' getting into recovery hasn't netted me much luck with about 20 tries of nailing the 10-second 'hold power button then nail volume up.'
Any suggestions?
Well, I got further.
I found that if I plugged the USB cable into the device into my computer, then pressed and held the power, when it would 'auto-reboot' to the battery icon screen.
Once at the battery icon screen, I unplugged the USB cable and the tablet completely turned off.
From there, I was able to get back to Philz.
So, I guess my new question is: How do I correctly install any kernel other than blackhawks, which would allow me to flash back to a stock ROM?
curiousmike said:
I had installed 'blackhawks next kernel' for dual-booting.
I had CM11 on partition 1 and Stock Samsung on Partition 2.
I decided I want to simply revert to a single partition with the stock Samsung.
I booted into partition 1.
I used Phils to install 'GT3_MH2_STOCK_Kernel_SM-t310_Tab3.zip'
When the machine rebooted, it jumped into the Cyanogen Mod boot sequence, and just loops.
If I try to turn the machine off to boot into recovery, the Tab doesn't shut down - it just reboots.
Trying to 'time' getting into recovery hasn't netted me much luck with about 20 tries of nailing the 10-second 'hold power button then nail volume up.'
Any suggestions?
Click to expand...
Click to collapse
Do a clean install of stock ROM by going into download mode. Power + Volume down + Home button.
curiousmike said:
Well, I got further.
I found that if I plugged the USB cable into the device into my computer, then pressed and held the power, when it would 'auto-reboot' to the battery icon screen.
Once at the battery icon screen, I unplugged the USB cable and the tablet completely turned off.
From there, I was able to get back to Philz.
So, I guess my new question is: How do I correctly install any kernel other than blackhawks, which would allow me to flash back to a stock ROM?
Click to expand...
Click to collapse
The kernel you installed will only work with stock roms. You still had CM installed as primary rom and attempted to use a stock kernel with it. That's why it wouldn't boot.
You have a couple options now for reverting to stock.
1. Odin - Download and flash a full stock firmware; then boot into recovery and do a factory reset. There are many guides for doing this with Odin. Firmware is available at sammobile.com.
2. Recovery - Download a stock-based rom and flash it in recovery. Make sure you do a full wipe in recovery before flashing. The rom will have a kernel also, so there is no need to flash another one.
I've had a CM11 Official Nightly installed on my phone for a couple weeks, and just today my phone started turning off, and when I try to turn it back on it just shows the Samsung logo for a few seconds, then flashes the CM11 logo, then the screen goes black. It does fully boot up when I pull the battery for a few minutes then turn it on again, but it only lasts for a couple minutes before shutting off again. It does the same thing when I try to boot into recovery (TWRP), it shows the Samsung logo with the boot recovery text, then shows the TWRP screen for a second, then shuts off again. Rarely it will boot into recovery. Any idea what the problem is or how to fix it?
I would try installing the latest version of Philz Touch for the d2lte to see if you can get into recovery and stay in recovery. I used to have twrp on my phone but it gave me problems when flashing ROMs.
Thanks, installed Philz Touch recovery via Odin, and got it to boot into recovery and installed CM11 and it seems to be working so far.
Good news. For future reference, I would load the Samsung Phone Info app from the playstore to confirm the bootloader and modem on your phone as some ROMs may require the latest bootloader and modem to function properly.