Develop Bugs

Constant bootloop

My Incredible is in a bootloop. I have gone back to stock. The phone will work for a few minutes then just reboot non-stop. I did a factory reset and that did not help.
I can't keep the phone on long enough to do anything. The irony in all of this is that it started to do this 2 weeks after I became eligable for an upgrade...
Smells fishy...now I either wait for Incredible 4G or get the Rezound.
[email protected] Verizon...

Do you have a recovery on the phone still or did you get rid of it when returning to stock? I'm not sure I've heard of this before but if you post the status of your hboot that might be able to help someone help you.
and personally between the two I would go with the Incredible 4G but that's just me being loyal to HTC i guess.

Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.

binaryhat said:
Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.
Click to expand...
Click to collapse
Post hboot version, s-on or off, and current android version.

cmlusco said:
Post hboot version, s-on or off, and current android version.
Click to expand...
Click to collapse
Will do tomorrow...left the phone at work.

S-off
HBOOT-0.92
Radio-2.15.00.07.28
Stock Android

I know it sounds very round-about but you may need to flash CWM back on to the phone so you can flash unrevoked's s-on tool, I don't know for sure that this is what is causing the problem but you want s-on when you are in stock, especially if you plan on giving the phone to Verizon- if it has been messed with they won't want to handle it because they will say it is not their problem. (I have heard that Verizon has admitted to not checking very carefully, but it can't hurt to be careful yourself)

How can I flash CWM if I can't keep the phone on for more than a minute?

sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.

that is a very valid point. It still can't hurt to try, I remember when I rooted my phone, it didn't take all that long to flash CWM.
You also might want to consider booting into safe mode to see if that keeps in on longer, I am copying and pasting these instructions from technipages.com because xda won't let me post links until they trust me more or something:
Sometimes services and apps you install on your HTC Droid Incredible can interfere with its functionality. If you’ve reached a point where the phone freezes at startup or malfunctions in a way that you can’t remove the problem, Safe Mode is the answer. Booting in Safe Mode will load only software and drivers from factory defaults. This should allow you access to remove whatever ails your smartphone.
1. Turn the device off. If the power button doesn’t do the trick, remove and replace the battery.
2. Power the device on.
3. When the logo appears, press and hold the Menu button.
4. Continue holding the Menu button until you see the home screen.
The words Safe Mode should appear in the lower left corner if you performed the steps correctly.
Click to expand...
Click to collapse
I apologize if you don't have any luck, but I am only trying to help

I'll try safe mode (should have) and see if that works.

binaryhat said:
I'll try safe mode (should have) and see if that works.
Click to expand...
Click to collapse
Does the phone shut off when your in hboot too? You need to do as sugested and flash cwm thru hboot, and then see if you can access recovery long enough to wipe everything in mounts and storrage except sd and emmc, then flash superuser, and a rom.

scoobntaz1996 said:
sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.
Click to expand...
Click to collapse
Whats your hboot and android version? Have you tried an ruu?
EDIT: Nevermind i forgot i was allready talking to you in the other thread.

[Q] Potential hardware issues/ brick / batter issue? Please help

Hello all. Let me first thank you for your time in reading my post. I appreciate it. I'm not a fan of only posting for help but I suppose that the site suggesting to always search first is to thank for that because I am usually able to find answers. So please forgive me if this is posted elsewhere but I really have searched and asked around but haven't seen anything similar to my issue. If there is something like it I do not know what to call it. I at first thought it was a sudden death, but realized I think my device model & the symptoms have disproved this theory.
My story...
I bought my AT&T Galaxy S3 feb 2013. I have had it, spent a month or two stock everything. The past month & a half I have flashed CM 10.1 & most recently PK-2.32 for about 3 weeks. Have ran it and loved it with no issues. Used the kernel that comes with both ROMs.
4 days ago
I was charging my phone at work, picked it up after a while, and it wouldn't turn on. It was stuck in a loop of 2 of the screens in my attachments(the battery screen & the SGS3 logo). The battery screen is not in motion, it is stationary like that so that the circle doesn't move.
I have tested quite a few things in regard to what I thought might be the issue...other batteries, chargers, cables pull sim & SD and still no luck...etc.
While the phone is unplugged I get no indication of life. Only when I plug it in will it show me the battery symbol & the logo.
After some playing with it while it is plugged in I have been able to get it into download mode quite frequently with no issue as seen in the third attachment.
So yes I can get into download mode but I'm still "fairly new" and not sure where to proceed from here. I'm not sure what my options are as this is new to me and I can't find anything related, nor can my much more experience friend who is not so new at it that got me into wanting to load custom ROMs.
And yes, as you can see it has tripped my flash counter up once, from what I've read there's only one way to fix that if I need to send it in.
So...If you are able and willing to help I would greatly appreciate it and any options you might give me. I'm willing to try almost anything as my phone is of no use to me at this moment.

if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?

xBeerdroiDx said:
if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?
Click to expand...
Click to collapse
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.

Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?

moose0003 said:
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.
Click to expand...
Click to collapse
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.

xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?
Click to expand...
Click to collapse
Thanks again for your reply. I will try this and check back.
You are correct, it just did this, no kernel or anything. I will try wiping the device the data doesn't bother me. I won't lose much.
Have you or anyone else heard of this happening or know a cause? I could not find anything.
aybarrap1 said:
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.
Click to expand...
Click to collapse
Thanks for your reply. I have a few backups. I will try stock first and see where that takes me and go from there.

Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...

moose0003 said:
Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...
Click to expand...
Click to collapse
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?

metalsnakebite said:
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?
Click to expand...
Click to collapse
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.

xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up.......
Click to expand...
Click to collapse
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.

moose0003 said:
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.
Click to expand...
Click to collapse
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.

moose0003 said:
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.
Click to expand...
Click to collapse
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.

metalsnakebite said:
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
haha. i've done that before. cheers, buddy.

xBeerdroiDx said:
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.
Click to expand...
Click to collapse
metalsnakebite said:
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
Thanks for the input guys. I'm having a difficult time to get it to stay into recovery now again. It acts like it wants to go in but it will just reboot. I will keep trying and if I need anymore help I will come back. Thanks so much again.

Back again. So I kept playing and was finally able to get into recovery as you guys suggested. Once I got in it finished the odin process and actually booted up! First time in a week. So ran through setup and then was able to determine that wifi is not working with stock ROM. Not sure if it's the phone or the ROM.
After it booted up and turned on was able actually do most functions, didn't test a lot wanted to see if it would work without being plugged in...this answer was no.
So after much testing I think what determines what will power it on and off is determined by what it is plugged into. I still think it is having hardware issues though because of the lack of powering on, but I am fairly certain that I can start it every time with a certain cable/charging dock.
I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.
Haven't done this yet but will start tonight & have it finished by tomorrow is the plan. If anyone has any better suggestions I would gladly take them.

So this should be my last post unless a question arises for me.
moose0003 said:
.....I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.....
Click to expand...
Click to collapse
This is what I said I was going to try to do. Took it to work and found time to do the above. TriangleAway worked a lot better than I ever thought it would. Flash counter reset, loaded unrooted stock and have a replacement on the way. Went very smoothly.
So doubt I will root & rom again until out of warranty. I appreciate everyone's help with my issue.
XDA is a great place.

Unable to access Bootmenu and stuck at HTC Menu

Hello, I recently flashed sphongle on my HTC ONE V, and it was working fine. I later installed gapps, which was also working fine (downloaded a few app and recovered my contact etc... using Titanium) for a while until I rebooted the phone. After this I could not get past the loading screen for sphongle. I do not know if Gapps was the issue, but I used version 20130301.
I then went to the my CWM recovery menu and did a factory reset, cleared the cache and tried restoring to the backup I made before I flashed the ROM. After doing this I could not get past the HTC menu. After doing all of this I now cannot access the bootmenu, it instead goes straight to the recovery menu when I hold down the power and volume down button as one would do to access the bootmenu. Because I can't access the bootmenu, I can't use an RUU.
If anyone has any suggestions or ideas I would be very happy.:fingers-crossed:
I'll try to answer any questions people have.

CWM is more trouble than its worth. it doesnt have a boot to bootloader option like twrp? you are in a fix without the ability to access hboot

No it doesn't have the option sadly.
Curtis1973 said:
you are in a fix without the ability to access hboot
Click to expand...
Click to collapse
Yep that's pretty much jist of it.

whick kernel are you using ?

I'm using HELLBOY-2013-06-29-4.2

Managed to figure it out myself.:victory:

nostalgickitty said:
Managed to figure it out myself.:victory:
Click to expand...
Click to collapse
im curious what you did to get back in to hboot. it may be something users may need to learn how to do if they ever encounter this issue.

24339642 120
Curtis1973 said:
im curious what you did to get back in to hboot. it may be something users may need to learn how to do if they ever encounter this issue.
Click to expand...
Click to collapse
Honestly It's pretty embarrassing, and shows my inexperience at this, but the whole time I tried booting to hboot, my phone was plugged into my computer. Once I unplugged it I could boot into hboot no problem. I guess this would be helpful for new users to know.

Solved: Power Down reboots into Recovery

Installed CWM Recovery (recovery-clockwork-6.0.4.8-m8.img) using Fastboot,
and then installed UPDATE-SuperSU-v1.94.zip
then took a nandroid backup.
Booted into Android - no problems.
But now :
- when I power down it reboots straight into CWM Recovery.
- when I select the advanced options of CWM Recovery / Power Down,
it reboots into CWM Recovery.
- when I select Fastboot/Power Down it also reboots into CWM Recovery.
From CWM Recovery I can
Boot System Now
and it boots into the system,
But when I power down, it reboots again into CWM Recovery.
ie, I can't power down.
The above only happens if a power or usb cable is connected.
If no power cable is connected, it shuts down normally.
But, if after it is fully shut down, I connect a power cable,
it again boots, by itself, into CWM Recovery !!
Notes:
- A restart from Android does an actual restart into the phone OS, not into CWM Recovery.
- if I turn back on Power/Fastboot, then I can shutdown properly even with power connected,
so the problem happens when Fastboot is off.
Anybody have any idea what is causing this
and what I can do about it?
some things I can think of trying
but I don't want to make things worse.
Have done this before on a Galaxy Nexus with no problems,
and have put CyM on an S3 with no problems.
[previously posted in the wrong forum (M7) moved here.]

undecidable said:
Installed CWM Recovery (recovery-clockwork-6.0.4.8-m8.img) using Fastboot,
and then installed UPDATE-SuperSU-v1.94.zip
then took a nandroid backup.
Booted into Android - no problems.
But now :
- when I power down it reboots straight into CWM Recovery.
- when I select the advanced options of CWM Recovery / Power Down,
it reboots into CWM Recovery.
- when I select Fastboot/Power Down it also reboots into CWM Recovery.
From CWM Recovery I can
Boot System Now
and it boots into the system,
But when I power down, it reboots again into CWM Recovery.
ie, I can't power down.
The above only happens if a power or usb cable is connected.
If no power cable is connected, it shuts down normally.
But, if after it is fully shut down, I connect a power cable,
it again boots, by itself, into CWM Recovery !!
Notes:
- A restart from Android does an actual restart into the phone OS, not into CWM Recovery.
- if I turn back on Power/Fastboot, then I can shutdown properly even with power connected,
so the problem happens when Fastboot is off.
Anybody have any idea what is causing this
and what I can do about it?
some things I can think of trying
but I don't want to make things worse.
Have done this before on a Galaxy Nexus with no problems,
and have put CyM on an S3 with no problems.
[previously posted in the wrong forum (M7) moved here.]
Click to expand...
Click to collapse
Well I haven't had this happen to me ever so, not sure how much help I'll be but...
Have you tried reflashing CWM? Perhaps clear the cache? Try to flash TWRP and see if it does the same, can always flash CWM again afterwards.

BerndM14 said:
Well I haven't had this happen to me ever so, not sure how much help I'll be but...
Have you tried reflashing CWM? Perhaps clear the cache? Try to flash TWRP and see if it does the same, can always flash CWM again afterwards.
Click to expand...
Click to collapse
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!

undecidable said:
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
Click to expand...
Click to collapse
Don't think a system reset is necessary just yet. First try to clear the cache and re-flashing CWM to see what it does. If nothing then you can try TWRP to see if it does the same thing.
Have you tried searching for a similar problem in the CWM thread if it's recovery related?
---------- Post added at 06:21 AM ---------- Previous post was at 06:10 AM ----------
undecidable said:
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
Click to expand...
Click to collapse
I also just noticed the version number for the CWM you're using, are you sure that's the right version? What device variant are you using, International, Verizon etc?
I see only these versions for international
philz_touch_6.25.5-m8.img
philz_touch_6.26.6-m8.img
philz_touch_6.41.6-m8.img
philz_touch_6.43.6-m8.img
Maybe you have wrong version if you use international version.
Download newest one here and reflash. That is IF you use international.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8

BerndM14 said:
Don't think a system reset is necessary just yet. First try to clear the cache and re-flashing CWM to see what it does. If nothing then you can try TWRP to see if it does the same thing.
Have you tried searching for a similar problem in the CWM thread if it's recovery related?
Click to expand...
Click to collapse
A system reset is no problem. I already did one before starting, and it is new. So no data/apps to lose.
Yes, spent about 6 hours searching last night. Haven't come across anything like it.
Plus, there doesn't seem to be a CWM thread for the HTC One M8 - there are threads for TWRP and Philz (CWM Advanced).

got info below nevermind =oD

I also just noticed the version number for the CWM you're using, are you sure that's the right version? What device variant are you using, International, Verizon etc?
I see only these versions for international
philz_touch_6.25.5-m8.img
Click to expand...
Click to collapse
I'm not using philz, I'm using standard CWM:
http://clockworkmod.com/rommanager
which is the recommendation in the Cyanogenmod instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_m8
So I think my version of CWM is correct.

BerndM14 said:
Yeah just linked the same to you now as well. Where did you get that version from then?
Nevermind, I got where you downloaded it from http://forum.xda-developers.com/showthread.php?t=2708520
So you're on Verizon?
Click to expand...
Click to collapse
No, I have the international version, and the recovery is from
http://clockworkmod.com/rommanager
the last line on the page, labelled M8.
I think it is the official version.

Well it seems we're back to square one then, erase cache.
Hook up device to PC, go into fastboot, adb reboot bootloader
fastboot erase cache
If it doesn't work then try another recovery, Philz or TWRP. Did you want to flash CM hence why you followed their tutorial?

BerndM14 said:
Well it seems we're back to square one then, erase cache.
Hook up device to PC, go into fastboot, adb reboot bootloader
fastboot erase cache
If it doesn't work then try another recovery, Philz or TWRP. Did you want to flash CM hence why you followed their tutorial?
Click to expand...
Click to collapse
I always read about 20 tutorials first: some are vague, some unreliable, some incomplete, some assume you have more experience, to make sure I fully understand what I have to do.
I chose CWM because I've used it before on a Galaxy Nexus and an S3 and it has been reliable.
I will install Cyanogenmod as soon as it goes to Stable for the M8. I have it on the S3 and am over-the-moon happy with it. However that could be a year.
Might wait a day before I try flashing TWRP. See if I can discover more, or if anyone has an insight to offer. I mean, why would it boot when you plug in the power cable?! Too strange to not be cautious.

undecidable said:
I always read about 20 tutorials first: some are vague, some unreliable, some incomplete, some assume you have more experience, to make sure I fully understand what I have to do.
I chose CWM because I've used it before on a Galaxy Nexus and an S3 and it has been reliable.
I will install Cyanogenmod as soon as it goes to Stable for the M8. I have it on the S3 and am over-the-moon happy with it. However that could be a year.
Might wait a day before I try flashing TWRP. See if I can discover more, or if anyone has an insight to offer. I mean, why would it boot when you plug in the power cable?! Too strange to not be cautious.
Click to expand...
Click to collapse
It seems like it's an old issue with CWM though on various devices.
HTC Desire S same problem as you also CWM recovery.
Desire Z same problem also with CWM recovery.
Desire HD same problem ALSO CWM.
Don't know if there is a problem with CWM and HTC devices maybe...Those 3 are all for HTC devices. Though doing a google search you do get the same problem with different manufacturer phones also with CWM

BerndM14 said:
It seems like it's an old issue with CWM though on various devices.
HTC Desire S same problem as you also CWM recovery.
Desire Z same problem also with CWM recovery.
Desire HD same problem ALSO CWM.
Don't know if there is a problem with CWM and HTC devices maybe...Those 3 are all for HTC devices. Though doing a google search you do get the same problem with different manufacturer phones also with CWM
Click to expand...
Click to collapse
wow! Clearly the issue! And it seems changing recoveries fixes it. Will try in the next hour.
what was the search phrase you used? All I tried returned irrelevent results, though mostly I was using G not XDA.
As my father used to say, your blood is worth bottling (its a compliment).
thankyou!

undecidable said:
wow! Clearly the issue! And it seems changing recoveries fixes it. Will try in the next hour.
what was the search phrase you used? All I tried returned irrelevent results, though mostly I was using G not XDA.
As my father used to say, your blood is worth bottling (its a compliment).
thankyou!
Click to expand...
Click to collapse
https://www.google.co.za/search?q=w...ite:forum.xda-developers.com&biw=1920&bih=979
Tossed in plenty of keywords into google, of course doing it normally gives a lot of results from other sites too but I just decided to narrow it down to xda(Most sites refer help questions to xda anyways so...)
I think it's better to use Google for searches anyways, it records info from a lot of sites. XDA works on a "keyword" basis it seems and most people when making threads don't really add any keywords to it so finding it is difficult. Heck, I even had issues finding HTC__622 in a thread where I knew for a FACT HTC__622 was mentioned at least 4 times, the results in xda itself turned up nothing.
I didn't even bother to try and search within xda for this issues, went the Google route and narrowing it down to xda, much better :good:
Back to the issue though, it would still be interesting to know what actually causes it to boot into recovery when it gets plugged in, it's strange and I'm curious about it. I also think flashing either Philz or TWRP should help, there are quite a few people on here using Philz and I can't recall an issue like this being mentioned before so perhaps it's not a problem with Philz.

BerndM14 said:
Back to the issue though, it would still be interesting to know what actually causes it to boot into recovery when it gets plugged in, it's strange and I'm curious about it. I also think flashing either Philz or TWRP should help, there are quite a few people on here using Philz and I can't recall an issue like this being mentioned before so perhaps it's not a problem with Philz.
Click to expand...
Click to collapse
Thanks. I did try an XDA search from G, but you are just better at it
There is code that gets executed when you plug in the power cable:
it shows the battery charging.
The battery charging icon that is showing just before boot into CWM recovery is different from the normal battery charging icon (that I can see when I have settings /power / fastboot on).
I wonder if CWM changes that code? If that is the case, flashing TWRP might not fix it - will soon know.

Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
Now, when I power-off,
1. initially this funny black/white battery charging logo appears
with words in red at the bottom like:
This build is for Developement Purposes only
Do not distribute outside of HTC
without HTC Permission...
Click to expand...
Click to collapse
2. Then the normal green battery icon appears
3. but then the TWRP screen appears and disappears.
4. For about 2 secs the TWRP screen may flash back briefly
before returning to the green battery icon with the backlight.
5. Then it settles on the green battery icon,
and the backlight stays on for about 10 secs.
6. then the screen switches off
and it really appears to be powered off.​
But if I quickly 'touch' the power button
the TWRP screen briefly appears (with a lock over it) once
and then the green battery screen reappears.
If I unplug then replug in power,
the same things happens: steps 1-6 above.
Tried flashing TWRP 3 times - no change.
Will now try flashing philz.

undecidable said:
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
....
Will now try flashing philz.
Click to expand...
Click to collapse
Philz does exactly the same as CWM - not surprising given that it is CWM based.
So have returned to TWRP, which is at least usable.
Any idea how to file a bug against CWM?
Philz I can do on their forum here.

undecidable said:
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
Now, when I power-off,
1. initially this funny black/white battery charging logo appears
with words in red at the bottom like:
2. Then the normal green battery icon appears
3. but then the TWRP screen appears and disappears.
4. For about 2 secs the TWRP screen may flash back briefly
before returning to the green battery icon with the backlight.
5. Then it settles on the green battery icon,
and the backlight stays on for about 10 secs.
6. then the screen switches off
and it really appears to be powered off.​
But if I quickly 'touch' the power button
the TWRP screen briefly appears (with a lock over it) once
and then the green battery screen reappears.
If I unplug then replug in power,
the same things happens: steps 1-6 above.
Tried flashing TWRP 3 times - no change.
Will now try flashing philz.
Click to expand...
Click to collapse
Well removing the red development purposes text is easy enough if you have S-OFF. Remove Red Text on Splash screen
I'm not sure if the same issue with CWM is applicable to all or most users of Philz on here, like I said before, I haven't noticed any threads popping up discussing the issue, unless they discussed it in Philz thread itself.
I myself haven't noticed the issue you have with TWRP, will look into it more as I get some time, gonna be a hectic week Personally I only use custom recovery when I need it, which isn't that often, not a big "flasher" of ROMs etc, so I'm on stock recovery.

BerndM14 said:
Well removing the red development purposes text is easy enough if you have S-OFF. Remove Red Text on Splash screen
I'm not sure if the same issue with CWM is applicable to all or most users of Philz on here, like I said before, I haven't noticed any threads popping up discussing the issue, unless they discussed it in Philz thread itself.
I myself haven't noticed the issue you have with TWRP, will look into it more as I get some time, gonna be a hectic week Personally I only use custom recovery when I need it, which isn't that often, not a big "flasher" of ROMs etc, so I'm on stock recovery.
Click to expand...
Click to collapse
Yes, found the post for Remove Red Text on Splash screen early this morning. Seems to be related to Root, and separate from the TWRP issue.
I have to wonder if the TWRP problems aren't caused by the initial flashing of CWM. Anyway will post the issue on the TWRP forum tomorrow and see what they say.
Seems Philz has had this problem before, it comes from CWM, and fixed it before.
I have to say, this is the last HTC phone I buy - Samsungs are so much friendlier to flashing. Also I greatly dislike the big Tampered sign.
Reason for flashing recovery this time is I wanted root so I could remove garbage from the phone.
I don't flash ROMs much. High learning curve and risky. I do just one flash: from stock to CyangenMod. so much nicer it is worth it. I have to say if I had to choose between my old S3 with CyanogenMod and a stock M8, it would be the S3. If I can't get the garbage off the M8, I will just put it in a drawer till CyM goes stable for it.

Solved: Power Down reboots into Recovery
undecidable said:
Seems Philz has had this problem before, it comes from CWM, and fixed it before.
Click to expand...
Click to collapse
The solution! From the Philz M8 thread.
http://forum.xda-developers.com/showthread.php?p=53464839
An earlier version of Philz: 6.26.6-m8.zip.
The earlier version doesn't have the problem.
Thanks to @donmarkoni

[Q] One M8 Stuck on Logo...Period

I am in need of some serious help. My AT&T M8 won't boot past the HTC logo screen and won't allow me to go into recovery or the hboot screen. I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen. It was so bad that I just left it plugged in overnight and I don't have a clue as to how long it took to power off because I fell asleep before it did. If there's a video tutorial out there that someone has or simply a link that can show me how to install something via backdoor on this device, that would be great!

alpinesun said:
I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. !
Click to expand...
Click to collapse
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
alpinesun said:
Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen.
Click to expand...
Click to collapse
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.

Thanks already. I didn't realize I had to hold down the volume down button after it goes dark. It got me into twrp. I believe I should be good from here after I download a new rom to sideload. But to give you a run down, I was prepping the phone to sell it by wiping the data and installing the rom the guy said he wanted on it. When I was going thru the normal procedure to install the rom (wipe, flash, etc) that's when the phone started sticking on the logo screen. My assumption was that I downloaded a bad rom, so since then I've been trying to get back into twrp so I can load a new rom and finally was able to after you told me this. I'll report back if a new rom actually didn't help the situation. I only thought I wiped the OS because something similar happened with my Note when I was tinkering and that was the result.

alpinesun said:
I'll report back if a new rom actually didn't help the situation.
Click to expand...
Click to collapse
If you need any further help, please answer all the questions I previously asked.
Good luck.

redpoint73 said:
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.
Click to expand...
Click to collapse
So, it seems I'm still having the problem, even while trying to install cyanogen. Here are the answers to those questions...
1) bootloader unlocked?... YES
2) custom or stock recovery... TWRP
3) custom ROM?... It was a custom AOSP Rom
4) what hboot number?... 3.16.0.0000
5) s-on or s-off... S-OFF
6) did you make a nandroid with custom recovery?... It was erased
Any help you can give from this point would be awesome. Thanks again!

alpinesun said:
So, it seems I'm still having the problem, even while trying to install cyanogen.
Click to expand...
Click to collapse
Failure to flash ROMs can often be solved with fastboot erase cache, then install TWRP by fastboot again. Update TWRP version, if you are using an outdated one.
Also, if you try to flash any ROMs based on Sense software beyond version 1.x (huge majority of them are past 1.x at this point) you will likely experience extremely long boot times (10 minutes or more) and broken WiFi due to outdated firmware. But CM should be okay.
alpinesun said:
6) did you make a nandroid with custom recovery?... It was erased
Click to expand...
Click to collapse
It was erased, or you wiped it?

Okay. Do you suggest trying an older sense rom to see if it works? The last time touched the phone was when I picked up my Note 4, so I will look for something that predates that.
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.

alpinesun said:
Okay. Do you suggest trying an older sense rom to see if it works?
Click to expand...
Click to collapse
Sure, it couldn't hurt. With your current firmware, you will need a ROM based on 1.x software. There aren't a heck of a lot of those left. But there are a few. GoldenEye is one I can personally vouch for, since I was running it for a while back in the day:
http://forum.xda-developers.com/showthread.php?t=2705640
But I would definitely recommend just trying fastboot erase cache and re-install TWRP first. I've lost count how many times suggesting this simple fix has helped other users here on XDA, when ROMs fail to flash.
alpinesun said:
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.
Click to expand...
Click to collapse
Fair enough. Just FYI, don't do a factory reset in bootloader (in the OS settings or recovery is OK). On modded phones this may cause the internal storage to become corrupted. Nandroids have sometimes been lost this way. This may or may not be what happened to you. Just wanted to throw that out there.
Also, there has been the occasional occurrence of internal storage being corrupted, possibly by TWRP. It may not even have been something you caused.