whenever my phone is turned off and i charge it the phone will immediately power on in recovery mode. its been doing this since s-off/htcdev unlock on multiple roms and recoveries. is anyone else experiencing this?
Linch89 said:
whenever my phone is turned off and i charge it the phone will immediately power on in recovery mode. its been doing this since s-off/htcdev unlock on multiple roms and recoveries. is anyone else experiencing this?
Click to expand...
Click to collapse
It is a known issue. HTC's charge mode is actually a low power mode of recovery. Since I use a stock kernel in my recoveries, the phone tries to boot into this low power state, then realizes the requisite charge-mode init and resources aren't available. This has actually been resolved in the CM device tree, but with CM's kernel there is no option to mount external sdcard over USB. (I haven't released any of these builds) So, it's a pick your poison kind of thing.
Related
I used the unrevoked method to root my phone which installed Clockworkmod Recovery 2.5.0.1. I noticed that when I poweroff, if I have a USB cable plugged into the phone, even a charging only cable, it reboots into Clockworkmod Recovery. I don't remembering it do this before. Any suggestions? Also, it now appears I have no service when I reboot. It was working fine before. {service came back after a couple of reboots}
Known issue discussed in several other threads. Also of note, booting into Clockwork this way is not advised. Basically, you don't need to turn your phone off to charge the phone. And if you need to do anything in Clockwork, make sure it is unplugged and boot into it by holding the Volume Down button and then Power.
You can't turn your phone off when it's plugged into the USB (regardless of whether it is connected to the computer or a power source) with clockwork recovery installed. The phone will boot into an unstable form of clockwork recovery which you should not use.
Not sure about the signal issue. The phone starts off with no signal for a few seconds but usually finds it in a bit. Just in case I thought I'd mention that the back cover needs to be on the phone for it to find a signal (since the antennae is in the cover).
phone rebooting when charger is plugged in! with phone switched off
oahceasgnikgneas said:
You can't turn your phone off when it's plugged into the USB (regardless of whether it is connected to the computer or a power source) with clockwork recovery installed. The phone will boot into an unstable form of clockwork recovery which you should not use.
Not sure about the signal issue. The phone starts off with no signal for a few seconds but usually finds it in a bit. Just in case I thought I'd mention that the back cover needs to be on the phone for it to find a signal (since the antennae is in the cover).
Click to expand...
Click to collapse
This problem is caused when clockwork touch recovery is installed :- [
My Amaze has been off for about a week or two and now it wont even power on.
If I press and hold the power button I get no indication that it is doing anything. However, if I press the buttons on the bottom of the screen I get a slight vibration indication that it is indeed getting power to it. Tried booting into recovery with no luck.
Any thoughts?
What recovery are you using? I know most recoveries don't support charging while off. I suggest 4EXT but you will need to charge the battery externally first in order to flash it. Good luck.
do you have an external battery charger to charge the battery out of the phone?
did you try to charge the battery ?
Here's an interesting update.
Was able to plug it in USB and using ADB restart into recovery. From recovery I hit restart and the phone booted up like normal.
BUT, about 5-10 seconds in Android it reboots again back to the black screen with the vibrating buttons. Had to run back to work so I wasn't able to play around with it anymore than that.
BiznessMan said:
Here's an interesting update.
Was able to plug it in USB and using ADB restart into recovery. From recovery I hit restart and the phone booted up like normal.
BUT, about 5-10 seconds in Android it reboots again back to the black screen with the vibrating buttons. Had to run back to work so I wasn't able to play around with it anymore than that.
Click to expand...
Click to collapse
if your running a custom rom maybe it got corrupted somehow, happens to my phone often due to the fact im trying to find a way around to cloning one rom to another phone, try to reset your phone back to stock by flashing a ruu stock rom or a different rom, flash 4EXT and wipe everything from the phone (including sd card) don't forget to check and realign the partitions and then toggle usb mode and put the rom on the sdcard and flash it , hope that helps
Ninjistix said:
if your running a custom rom maybe it got corrupted somehow, happens to my phone often due to the fact im trying to find a way around to cloning one rom to another phone, try to reset your phone back to stock by flashing a ruu stock rom or a different rom, flash 4EXT and wipe everything from the phone (including sd card) don't forget to check and realign the partitions and then toggle usb mode and put the rom on the sdcard and flash it , hope that helps
Click to expand...
Click to collapse
Thanks for the reply but I can't even get it to recognize via USB anymore
Buttons still vibrate, screen is still black. I can't get anything to work on it
BiznessMan said:
Thanks for the reply but I can't even get it to recognize via USB anymore
Buttons still vibrate, screen is still black. I can't get anything to work on it
Click to expand...
Click to collapse
Battery pull, hold volume down(or is it up? I work on too many android phones..) and power button and it should boot into bootloader. From there reboot into recovery. Flash a custom rom of your choice after doing a full wipe. Problem should be solved unless there is a hardware issue, at which point it must have been dropped, battery issue, etc..
What it really seems like is your battery doesn't have enough juice to sustain power, (I get bootloops when my battery goes really low and I try turning it on). Just let it charge a bit and if the battery isn't holding its charge, then time for a new battery
Sent from my Amaze using xda app-developers app
Hello,
I'm rooting/installing a custom rom on a friends phone. I'm on 2.3.5, .418. I successfully rooted using the self-extracting method. I've been trying to flash CWM/bootstrap to no avail. I was wondering if anyone had any ideas on what to do?
I've tried droid2bootstrap v1.0.5 and This .apk method. Neither seem to work. When I tell the phone to boot into recovery via the application is just reboots normally, if I select booting into recovery via vol- + pwr once I select android recovery it goes into a screen similar to that of cwm recovery, but there are no options and I have to perform a battery pull to reboot the phone.
Any help/ideas would be fantastic.
Thanks!
I'm special
bdpope88 said:
Hello,
I'm rooting/installing a custom rom on a friends phone. I'm on 2.3.5, .418. I successfully rooted using the self-extracting method. I've been trying to flash CWM/bootstrap to no avail. I was wondering if anyone had any ideas on what to do?
I've tried droid2bootstrap v1.0.5 and This .apk method. Neither seem to work. When I tell the phone to boot into recovery via the application is just reboots normally, if I select booting into recovery via vol- + pwr once I select android recovery it goes into a screen similar to that of cwm recovery, but there are no options and I have to perform a battery pull to reboot the phone.
Any help/ideas would be fantastic.
Thanks!
Click to expand...
Click to collapse
Well, found out what the issue was. The .apk method linked above asked that you plug in your phone to an AC outlet. I thought this was to ensure that your battery is high enough. With the battery at 100%, I ignored the warning. Going over the issue one last time, I tried plugging in the phone and it worked like a charm.
I'll leave this up just in case someone in the future is as special as I am.
bdpope88 said:
Well, found out what the issue was. The .apk method linked above asked that you plug in your phone to an AC outlet. I thought this was a, to ensure that your battery is high enough. With the battery at 100%, I ignored the warning. Going over the issue one last time, I tried plugging in the phone and it worked like a charm.
I'll leave this up just in case someone in the future is as special as I am.
Click to expand...
Click to collapse
LOL. Well done sir.
For reasons unknown, I'm able to boot into flash mode and therefore restore my ROM.
Thanks for helping me though, random stranger!
So can anyone close this thread? It isn't needed anymore.
I recently flashed a new stock pure Lolipop ROM on my Xperia Z Ultra from a stock pure Kitkat ROM that I've been using for months now.
However, it is noteworthy that my device has been rooted and custom roms has been installed on this device for about a year now. So my device has its bootloader unlocked.
I followed all of the instructions I can
- Wipe the data and cache ( incl. dalvik )
- Flashing the ROM in question
- Flashing the su and GApps
- Wiping the cache ( again, just to make sure )
And here's where the problem started
When I started to boot my smartphone, it flashes red for a couple of times. At first instinct, I thought it was a battery depletion problem, and sure enough, it was! So I plugged in and noticed yet another problem; my phone started randomly turning on for a brief moment before shutting back down, presumably due to extremely low battery power. And it didn't even bother to wait for my Z Ultra to be charged to a reasonable level of power before attempting to power on. However, I tried using the power+up button fix, and it didn't work and then there's yet another kicker; Fastboot ( Blue LED ) Mode is no longer accessible on my phone. When I plug in while pressing down on my ZU, it does nothing and simply just charges ( presumably ).
I'm currently on my last legs of hope and doing the last resort: to wait for my smartphone to charge substantially enough for a long time.
Which is about 8-9 hours after this post is made.
TL;DR
- Device is currently rooted for a year now and has been installed with custom roms left and right.
- I followed the instructions to the T
- Phone not able to turn on
- When charging, phone attempts to turn itself on, regardless of power level
- Plausibly due to low battery level 15%-24% during flashing
- Fastboot Mode not possible presumably due to low power
- Now waiting it out for 9-8 hours to see if issue resolved
- Will update whether if method works or not
Please help! This is one of my most used smartphones.
Yeah, it might be the battery that's gone bellow the "zone". What I mean is when you deplete the battery completely to 0%, there's still more battery left, but the system shuts it down so not to damage the battery. It's a Li-ion thing. But once in awhile it does happen that it get completely empty, and you'll experience what you've done here. A dead device. It's not only Sony phones that experiences this, but from all OEMs.
Notes:
- So, keep it charging for 15-20 hours and see if it helps.
- You mentioned fastboot not working. Be sure to have fastboot installed on the computer. If it's not, it won't work.
- Blinking red LED also (usually) means there's been a kernel panic
RE
Klaos3000 said:
Yeah, it might be the battery that's gone bellow the "zone". What I mean is when you deplete the battery completely to 0%, there's still more battery left, but the system shuts it down so not to damage the battery. It's a Li-ion thing. But once in awhile it does happen that it get completely empty, and you'll experience what you've done here. A dead device. It's not only Sony phones that experiences this, but from all OEMs.
Notes:
- So, keep it charging for 15-20 hours and see if it helps.
- You mentioned fastboot not working. Be sure to have fastboot installed on the computer. If it's not, it won't work.
- Blinking red LED also (usually) means there's been a kernel panic
Click to expand...
Click to collapse
I'll try to follow your advice on the extended charging thing.
Fastboot is definitely on my computer so ye
Kernel panic? What can I do to remedy that?
LWarrior said:
Kernel panic? What can I do to remedy that?
Click to expand...
Click to collapse
Just flash a different kernel. If that doesn't solve anything, then we'll know that it isn't a kernel panic.
Klaos3000 said:
Just flash a different kernel. If that doesn't solve anything, then we'll know that it isn't a kernel panic.
Click to expand...
Click to collapse
How though? Flashboot isn't working for me.
LWarrior said:
How though? Flashboot isn't working for me.
Click to expand...
Click to collapse
We've got Fastboot and Flashmode. Fastboot is what you use when you want to flash some ROMs and kernels through a terminal (command line), while Flashmode is for flashing ROMs in Flashtool and Sony's PC Companion.
You can enter Fastboot by holding VOL UP while you connect your device to the computer. Remember to hold VOL UP until the LED above the screen turns blue. Once you've achieved that, the either flash/hotboot a kernel with recovery, like NUT's Dual Recovery, and then restore or flash a different ROM. If the device doesn't reboot by itself or do anything weird, then case closed. If it does do something weird, then I'm not sure what's going on.
Remember to have fastboot installed on your computer. Or else it won't work. You can easily install it by using this installer. If you don't know how to use fastboot through a command line, then use Flashtool or QuickIMG.
EDIT: JUST SCROLLED UP AND READ THAT YOU'VE SOLVED IT! JUST PRESS EDIT ON THE FIRST POST, AND ADD "SOLVED" IN FRONT OF THE TITLE, LIKE THIS: "[SOLVED] [Q] Booting Problems!"
Facts:
- Pocophone F1 is in an endless boot loop. Every 8 seconds it reboots itself.
- Recovery mode and Fastboot are reachable, but this doesn't stop the boot loop.
- I have never used a custom rom
- The bootloader is unlocked (ADB confirms this), USB debugging is enabled, but OEM unlocking is NOT enabled.
History:
The problems started after a regular update (I had never put a custom rom on the phone). The phone became unstable, constantly restarting itself. Sometimes restarting quickly, sometimes after a few minutes (reaching Android). I tried to unlock the bootloader, by tapping 7 times on MIUI Version, enabling USB Debugging [I did not enable OEM unlocking unfortunately...] and run the flashtool. The flashtool reported that the phone was unlocked. And after restarting, the phone reports to be unlocked. ADB confirms this too. But after unlocking the phone, it never ever again reached to Android, restarting itself always after exactly 8-9 seconds. I can get into recovery mode and fastboot, but it will still restart. In Fastboot, my pc recognizes the phone as an Android Phone. Is there a magical way to get out of this loop?
Similar thing happened to twice. My power button was kinda stuck (not noticeable to eyes thoughts). Flicking onto the power button real hard solved the issue.
lockhrt999 said:
Similar thing happened to twice. My power button was kinda stuck (not noticeable to eyes thoughts). Flicking onto the power button real hard solved the issue.
Click to expand...
Click to collapse
The problem persist when I completely remove the connector of the power/ volume button... When I push the power button I feel that the button moves and I hear a click-sound. Something else must be the cause of the problem. But still thanks for your help.
i have the same issue, did you find any solution to the problem?
Have the same problem is there any solution?
I don't have the phone so I cannot say this will solve the issue, however this sounds like a problem with the battery, something similar happened to my Redmi Go. The voltage should be low enough that the system boots, but just as it starts up the voltage drops to the point it reboots.
Solved it!!
I have Played with the power button and press it several times and it help.
I think the button was stuck or something close to that.
Thanks for you help guys!
ozer86 said:
Facts:
- Pocophone F1 is in an endless boot loop. Every 8 seconds it reboots itself.
- Recovery mode and Fastboot are reachable, but this doesn't stop the boot loop.
- I have never used a custom rom
- The bootloader is unlocked (ADB confirms this), USB debugging is enabled, but OEM unlocking is NOT enabled.
History:
The problems started after a regular update (I had never put a custom rom on the phone). The phone became unstable, constantly restarting itself. Sometimes restarting quickly, sometimes after a few minutes (reaching Android). I tried to unlock the bootloader, by tapping 7 times on MIUI Version, enabling USB Debugging [I did not enable OEM unlocking unfortunately...] and run the flashtool. The flashtool reported that the phone was unlocked. And after restarting, the phone reports to be unlocked. ADB confirms this too. But after unlocking the phone, it never ever again reached to Android, restarting itself always after exactly 8-9 seconds. I can get into recovery mode and fastboot, but it will still restart. In Fastboot, my pc recognizes the phone as an Android Phone. Is there a magical way to get out of this loop?
Click to expand...
Click to collapse
Chance 1: Power button bug
Chance 2: EMMC failed and your phone is long gone.
lockhrt999 said:
Similar thing happened to twice. My power button was kinda stuck (not noticeable to eyes thoughts). Flicking onto the power button real hard solved the issue.
Click to expand...
Click to collapse
Thank you! This was the issue. There is no way to tell that the power button is stuck. But it is and was causing my Poco F1 to bootloop even in fastboot or recovery mode. A symptom to look out for: your phone randomly locking once in a while due to this.
mateuxi said:
I don't have the phone so I cannot say this will solve the issue, however this sounds like a problem with the battery, something similar happened to my Redmi Go. The voltage should be low enough that the system boots, but just as it starts up the voltage drops to the point it reboots.
Click to expand...
Click to collapse
i booted in TWRP for 8-9 minutes with full brightness & no timeout but then mine didn't go into bootloop... recovery's getting powered but OS isnt?
Same thing happened to my F1, I press and flicked my power button hard and it worked. My problem happened maybe because the hard cover pushing the button too tight because it sometimes lock it self. Thank you for the tips! Just made account to reply to this thread.