Related
Hi guys, well I'm a new HTC One X owner and I just jumped ship from the iPhone. I had jailbroken my iPhone several times with only minor problems in the past so I thought I'd give it a try on the One X. Unfortunately, I think I've really screwed something up and now when i boot it up, it vibrates and then hangs at the HTC Quietly Brilliant screen. So here's what I did:
I downloaded Hasoon2000's HTC One X All-In-One v.1.1 kit. I followed the instructions and as far as I could tell, everything worked fine. The bootloader was unlocked and I was able to root the phone. However, after installing a couple of apps which all crashed when I tried to run them (it made the phone restart), I decided to do a factory reset and do it again. So i held onto the power button + volume down and went into the Bootloader and tried to reset it which then took me to the CWM 5.8.4.0 screen. I then did the factory reset there which led me to where I am now.
Could someone please tell me where to proceed from here to bring it back up and running normally again? As you can probably tell, I know next to nothing about Android so I would really appreciate some patience and step by steps. I've already scoured Google looking for a solution but I could never understand what people were talking about. If you need any more information to give you a better diagnosis, please let me know and maybe tell me how to find the information
Thanks a lot people, any help would be much appreciated!
MarcusJKX said:
Hi guys, well I'm a new HTC One X owner and I just jumped ship from the iPhone. I had jailbroken my iPhone several times with only minor problems in the past so I thought I'd give it a try on the One X. Unfortunately, I think I've really screwed something up and now when i boot it up, it vibrates and then hangs at the HTC Quietly Brilliant screen. So here's what I did:
I downloaded Hasoon2000's HTC One X All-In-One v.1.1 kit. I followed the instructions and as far as I could tell, everything worked fine. The bootloader was unlocked and I was able to root the phone. However, after installing a couple of apps which all crashed when I tried to run them (it made the phone restart), I decided to do a factory reset and do it again. So i held onto the power button + volume down and went into the Bootloader and tried to reset it which then took me to the CWM 5.8.4.0 screen. I then did the factory reset there which led me to where I am now.
Could someone please tell me where to proceed from here to bring it back up and running normally again? As you can probably tell, I know next to nothing about Android so I would really appreciate some patience and step by steps. I've already scoured Google looking for a solution but I could never understand what people were talking about. If you need any more information to give you a better diagnosis, please let me know and maybe tell me how to find the information
Thanks a lot people, any help would be much appreciated!
Click to expand...
Click to collapse
Did you flash a custom ROM?
as long as u can see the HTC logo ur phone is not bricked. Its a soft-brick.
just find an official firmware and flash it from recovery...ur One X will b up and running!
dr9722 said:
Did you flash a custom ROM?
Click to expand...
Click to collapse
Sorry, I'm embarrassed to say that I'm not sure exactly what you mean. By that, do you mean did I install a non-stock OS? If so, then the answer would be no. I did flash the recovery with CWM 5.8.4.0 but I have a feeling that, that's not what you meant.
realzahed said:
as long as u can see the HTC logo ur phone is not bricked. Its a soft-brick.
just find an official firmware and flash it from recovery...ur One X will b up and running!
Click to expand...
Click to collapse
Thanks a lot man! Could you...please tell me how to do that? I saw a few threads discussing soft-bricks and they suggested downloading some stuff and then plugging the phone into the PC and typing some commands into cmd. But when I connect my phone into my PC i get no response, even when I'm in the Bootloader screen.
And also, does it matter which version of the official firmware i get? I saw people mentioned RUU files but it had to match my phone's version. Does this have anything to do with that?
I believe you should just plug the phone and run your factory ruu and that would do it and bring the phone back to stock.
Heres where u can get the ruu, am not sure whats the codename for the international hox but i think this is it. Please make sure you are using the correct ruu for your phone.
http://forum.xda-developers.com/showthread.php?t=1543604
Sent from my HTC One XL using xda premium
You should probably read up before trying this again. If you can hold the power button and volume down. It should bring you into a menu. You should press the volume down button until fast boot is highlighted and then press the power button to select it. Download htc sync and install the drivers. Go to the one x development section and download the ruu for your device. Then run the ruu.
Sent from my iPhone using Tapatalk
Thanks a lot for the responses guys. That link you gave me says that they are ROMs for Endeavor, is that the same as a ruu? And also, how do i figure out which ruu is right for me? I'm in Switzerland and my carrier is Orange but I see several ruus there under orange but none of them are for Switzerland and there are even different version numbers. In my current state, is there a way for me to find out which version I need?
By the way, when I try to connect my phone to my PC in fastboot mode and open cmd prompt and type in "fastboot getvar cid", i get "'fastboot' is not recognized as an internal or external command, operable program or batch file." If i click Fastboot on my phone and then HBOOT whilst plugged into the PC, i get a few lines on my phone saying that it "Failed to open USB master mode" and then "please plug off USB".
MarcusJKX said:
Thanks a lot for the responses guys. That link you gave me says that they are ROMs for Endeavor, is that the same as a ruu? And also, how do i figure out which ruu is right for me? I'm in Switzerland and my carrier is Orange but I see several ruus there under orange but none of them are for Switzerland and there are even different version numbers. In my current state, is there a way for me to find out which version I need?
By the way, when I try to connect my phone to my PC in fastboot mode and open cmd prompt and type in "fastboot getvar cid", i get "'fastboot' is not recognized as an internal or external command, operable program or batch file." If i click Fastboot on my phone and then HBOOT whilst plugged into the PC, i get a few lines on my phone saying that it "Failed to open USB master mode" and then "please plug off USB".
Click to expand...
Click to collapse
That probably means fastboot is not properly installed in your pc.
Sent from my HTC One XL using xda premium
joker96 said:
That probably means fastboot is not properly installed in your pc.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
okay, I didn't realise I had to install fastboot on my PC. So i just configured it following the directions here: http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
and now when my phone is hooked up to my PC and i type "fastboot getvar cid" into cmd prompt, i get this:
cid: None
finished. total time: 0.004s
So what does this mean?
Download an app from the marketplace and see what that comes up with. Also go into settings about phone software information then software number. What is the software number?
ste1164 said:
Download an app from the marketplace and see what that comes up with. Also go into settings about phone software information then software number. What is the software number?
Click to expand...
Click to collapse
My phone can't get past the opening splash screen, you know where it says HTC Quietly Brilliant? It just stays there, so I can't go into marketplace or check my settings,
You are going to need to find out wich ruu version u need. I dont know how carriers identify themselves on europe. After you identify it get into the bootloader menu get on fastboot and the open the ruu you downloaded the software should do everything by itself. Btw if you do this your going back to stock that means no root no cwm or wtever you had your going to have to do everything again but at least you got the phone working. Once you identify the ruu you need i would not download the latest version just in case the carrier fixed the root method or something. Again i dont know much about how europe works and how bossy carriers are about rooting/unlocking bootloader. You can try asking on that same thread for the one you need. Someone elsr might have an answer. Good luck.
Ps. Am not sure if you are going to need to relock the bootloader in order for the ruu to run. Can someone shed some light on this?
Sent from my HTC One XL using xda premium
Btw before you do that have you tried getting on the recovery??? Can you get on cwm?? If u can do that i believe there no need to flash the ruu instead just flash a different rom maybe??? Did you get to make a backup before this happened??
Sent from my HTC One XL using xda premium
Thanks a lot joker96. I can get into CWM, so how would i flash a different rom? Unfortunately, the only backups I made are of my personal files and apps, I didn't think to backup anything else.
What were you trying to do that made all this happen?
Sent from my HTC One XL using xda premium
Oh derp sorry I completely forgot. You would download a different rom and follow the guides on the thread to install it. Wipe davlik cache, cache and data. Try ARHD.
Sorry, i didnt read the first post completly. So you did a factory restore wipe on cwm, am i correct? You didnt clear cache and dalvik?
Sent from my HTC One XL using xda premium
ste1164 said:
Oh derp sorry I completely forgot. You would download a different rom and follow the guides on the thread to install it. Wipe davlik cache, cache and data. Try ARHD.
Click to expand...
Click to collapse
What do you mean "different rom"? As in a different rom to the one I had? And what's ARHD?
joker96 said:
Sorry, i didnt read the first post completly. So you did a factory restore wipe on cwm, am i correct? You didnt clear cache and dalvik?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Well the thing is, I'm not 100% sure what I did. First I did a factory reset on CWM and everything worked fine, but when my phone rebooted, I realised CWM was still there. What i wanted was to go back to square one, as in no recovery and no root. So i went back into recovery and wiped some other stuff, and that's when this happened. I know, I'm a total idiot, I don't know what i was thinking
Yea a different rom to what you had maybe that one had problems. ARHD is Android Revolution HD any other rom would work though. Just pick one from the development section.
ste1164 said:
Yea a different rom to what you had maybe that one had problems. ARHD is Android Revolution HD any other rom would work though. Just pick one from the development section.
Click to expand...
Click to collapse
Well i just took a look at the ARHD thread and I'm stuck on the second line of instructions: "Download "Super Wipe" script & place it on your SD card (optionally if coming from earlier version of my ROM, obligatory if coming from stock or other custom ROM)"
I have no access to my SD card, when i plug it into my PC, nothing happens because all i can do is go into recovery and bootloader.
Just a question, if I try to use the wrong ruu, what would happen?
Hey so I am very new to this, and decided to try and flash a new ROM to my One X. I really do not know what i am doing, but what with the toolkit put together by Hasoon2000 it seemed rather idiot proof. I thought i followed all the steps properly, but when i went to flash a recovery to my phone, it seems its not flashing.
All i am getting now when my phone reboots is the htc logo with a developers use only warning at the bottom, and in my bootloader i have a ***tampered***
***unlocked***
and my options are fastboot, recovery, factory reset, clear storage, simlock, image crc, power down
I require my phone for work so if someone can give me a hand as soon as possible would be very much appreciated,
Thanx
Seulewolf said:
Hey so I am very new to this, and decided to try and flash a new ROM to my One X. I really do not know what i am doing, but what with the toolkit put together by Hasoon2000 it seemed rather idiot proof. I thought i followed all the steps properly, but when i went to flash a recovery to my phone, it seems its not flashing.
All i am getting now when my phone reboots is the htc logo with a developers use only warning at the bottom, and in my bootloader i have a ***tampered***
***unlocked***
and my options are fastboot, recovery, factory reset, clear storage, simlock, image crc, power down
I require my phone for work so if someone can give me a hand as soon as possible would be very much appreciated,
Thanx
Click to expand...
Click to collapse
Well with the toolkit, once it brings you to the bootlaoder close the command prompt window and another one will open and flash the recovery.
Seulewolf said:
Hey so I am very new to this, and decided to try and flash a new ROM to my One X. I really do not know what i am doing, but what with the toolkit put together by Hasoon2000 it seemed rather idiot proof. I thought i followed all the steps properly, but when i went to flash a recovery to my phone, it seems its not flashing.
All i am getting now when my phone reboots is the htc logo with a developers use only warning at the bottom, and in my bootloader i have a ***tampered***
***unlocked***
and my options are fastboot, recovery, factory reset, clear storage, simlock, image crc, power down
I require my phone for work so if someone can give me a hand as soon as possible would be very much appreciated,
Thanx
Click to expand...
Click to collapse
Assuming recovery has been flashed:
You can navigate the options by pressing volume up and down and press the powerbutton to enter an option.
Now you have to goto recovery and flash the custom ROM and flash the proper boot.img via fastboot.
In hasoon2000's thread you can read all about flashing ROM's so please be patient and read and try to understand before doing anything.
that's precisely the problem, i clicked on the TWRP recovery and clicked 'flash recovery' it went through its process and when i went back to the bootloader in my phone and selected recovery it gives me the htc logo screen with the developer warning and than a black screen
Seulewolf said:
that's precisely the problem, i clicked on the TWRP recovery and clicked 'flash recovery' it went through its process and when i went back to the bootloader in my phone and selected recovery it gives me the htc logo screen with the developer warning and than a black screen
Click to expand...
Click to collapse
Are you sure your phone is an endeavoru and not an evita? (One XL)
so i tried flashing twrp recovery on my phone again followed by the rom kernel but all that happened with my phone was it rebooted twice and now i'm back to a black screen.
All i know is that it is an 'HTC One X from Telus Canada' what the actual developers name for it is... I only wish i knew and now i realize there is a lot more to this whole changing roms than i ever thought.
Stefan0vic said:
Are you sure your phone is an endeavoru and not an evita? (One XL)
Click to expand...
Click to collapse
Thank you so much you pushed me to revisit whether or not i was using the right recovery. and it was an evita not the endeavoru
Seulewolf said:
Thank you so much you pushed me to revisit whether or not i was using the right recovery. and it was an evita not the endeavoru
Click to expand...
Click to collapse
You're welcome
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.
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
Hi im new here and hope this is in the right place. I have a htc m8 on o2 network in the uk. Its basically not booting past the htc logo then it restarts again. I have booted into the boot loader via power button and volume down. When i go into recovery there is nothing to recover. Factory reset doesnt fix it niether does wipe the cache etc.... Tried them all. I have read a few guides and had a look at twrp but always get errors flashing them to phone. I also tried to do it via sd card but samr errors. Is anyone able to help me or advise me on what go do? My email is [email protected] if you wanted to email instead. Thank you for your time.
Skarekrow0121 said:
Hi im new here and hope this is in the right place. I have a htc m8 on o2 network in the uk. Its basically not booting past the htc logo then it restarts again. I have booted into the boot loader via power button and volume down. When i go into recovery there is nothing to recover. Factory reset doesnt fix it niether does wipe the cache etc.... Tried them all. I have read a few guides and had a look at twrp but always get errors flashing them to phone. I also tried to do it via sd card but samr errors. Is anyone able to help me or advise me on what go do? My email is [email protected] if you wanted to email instead. Thank you for your time.
Click to expand...
Click to collapse
I had a similar issue once and it was the micro switch under the volume button itself being stuck. Have you had any issues with the volume sticking either up or down before?
No nothing like that m8. Ill double check that though.... i think its software issue..
Skarekrow0121 said:
No nothing like that m8. Ill double check that though.... i think its software issue..
Click to expand...
Click to collapse
Sorry it couldn't have been something as simple as that. May I suggest that you re-post your issue in the M8 help area of the forum located at, https://forum.xda-developers.com/htc-one-m8/help ?
That area seems to receive more traffic by experienced users than this one, so hopefully someone can point you in the right direction as there aren't many dinosaurs like us left using "antique" novelty items like the M8 anymore.
HemiMoparMan said:
Sorry it couldn't have been something as simple as that. May I suggest that you re-post your issue in the M8 help area of the forum located at, https://forum.xda-developers.com/htc-one-m8/help ?
Click to expand...
Click to collapse
Better to report the thread and the mods will move it. Otherwise, it doesn't really fix the problem (thread in the wrong place) but actually makes it worse (multiple threads in different sections, both asking the same question).
I'll ask the mods to move the thread.
Skarekrow0121 said:
I have read a few guides and had a look at twrp but always get errors flashing them to phone.
Click to expand...
Click to collapse
Would be helpful to know what the errors say.
If it says "remote not allowed" it is because your bootloader is locked. It needs to be bootloader unlocked (via HTCDev.com), in order to flash custom recovery TWRP.