Related
So before everyone yells because of my inability to search the forum, please understand that not only have i searched this forum, but just about every other one. And if someone finds a thread with an answer to my question than i will admit defeat and have myself stoned and crucified.
I will greatly appreciate anyone's and everyone's help.
History in cliffnotes
Rooted with Unrevoked about a month ago, since then been running CM 6.
Have been happy with just using stock CM 6 and nothing else, haven't flashed any other kernels, radios, or for that matter roms.
Have always had problems with random reboots but didn't care.
Last night my phone appeared to have the desire to random reboot, and on start up got into a boot loop, just HTC splash boot loop. I can get into bootloader but if i try to go to recovery it is just more boot loops.
I'm running mac OS X however i eventually just tried running RUU on my roommates computer but to no avail, mostly, i think, because my phone can't boot into a state where its recognized by the program or sync, etc...
The real problem
As of now i've gone as far as basically completely unrooting, using a pc36img that i found through you guys here
So if you guys have any ideas, at this point, i'm completely willing to try them because, this was completely random that it happened, and i really am at a complete loss as to what to do besides buy a new phone.
i love you all in a masculine plutonic way. thanks.
well you could always re-root with unrevoked. all it needs is bootloader mode to root it and then once its done, flash a rooted rom on it, then proceed to unroot.
EDIT:
btw, i am a mac user too and unrevoked works great. if it fails, run it again. and no need to use an ruu, look up a thread in our development section titled shpped roms and they have pc36img versions of the ruu. you will be able to root with your mac and unroot all on the device. unrevoked has an s-on zip on their web page. to unroot it, flash the s-on zip then run the pc36img zip from the base of your sd card. thats all!
EDIT#2:
YOU CAN ALWAYS FLASH A RECOVERY VIA BOOTLOADER ALSO AND FLASH A ROM. LET ME KNOW WHICH RECOVERY YOU PREFFER, I GOT BOTH CLOCKWORKMOD AND RA.
EDIT#3: LOL, Sorry i didnt see that you mentioned a pc36img to unroot.
why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom
t3project said:
why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom
Click to expand...
Click to collapse
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!
Well since you can't get into recovery, we suggested to flash a recovery in pc36img.zip format in bootloader mode.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
paulieb81 said:
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!
Click to expand...
Click to collapse
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader
t3project said:
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader
Click to expand...
Click to collapse
If you read my message you will see that I DID flash a recovery, that same one you just linked, and it flashed ok, but when i restart and choose to enter the recovery the phone just reboots again!
Did you solve this?
Yes I did, I went back to the store and had them replace the phone. I could not get it to boot into recovery for some reason.
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
Did they give you any problems about s-off being visible in the bootloader when you got your phone replaced? I'm to that point of taking it back with the EXACT same problem but I didn't know if it was an issue. (or is there any trick to get s-on back without being able to load into recovery i.e. a fastboot command?)
i was worried about the s-off as well because i also was unable to change that. all i could find for that was the s-on tool but since u cant actually flash anything, had to leave it s-off. i even tried a battery pull during the radio update on a pc36img so that they wouldnt be able to get to bootloader but i couldnt even brick it. i live more than 50 miles from a sprint store so they didnt make me drive to a sprint store. they sent me a replacement and i mailed my evo back. on the paperwork for the new phone they said i could still be charged 75 dollars for a recoverable phone and 125 for an unrecoverable phone. it was probably 2 weeks ago or so when i sent my old broken evo back and i havent been billed yet so i dont know what if anything they will charge. when i talked to the sprint tech on the phone i told him it was rooted because i knew they would see the s-off and i didnt want to get screwed when i sent them my broken phone and they said "u rooted, ur problem" but he said he would still replace it and he did.
k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm in the same boat buckley. I don't get it?! I did run cm for a couple days but I was always looking at my phone wondering if something was going to happen. Almost gave myself a panic attack so I just went back to sense, lol.
ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
And I just wanted to say, that although you've seen 5, and I've seen around 10, and that does suck, that the fact is, that this is an EXTREMELY low percentage of CM users that are experiencing this problem. With that noted, it's still enough for me to use a different rom, at least until someone can at least figure out what caused that to happen. I am just extremely curious, as to what the actual malfunction with the device is, when this sort of things happens. And why it seems to only be happening on CM. (at least from the reports I've seen around here)
Add me to the list of people with this problem. I think I'm going to try my chances at the Sprint store. They've been good to me so far.
k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It has nothing to do with CM. It is clearly a hardware problem. It has happened on other roms, but more likely to happen to someone using CM as it is the most used Rom.
Sent from my PC36100 using XDA Premium App
Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..
jkxklutz said:
Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..
Click to expand...
Click to collapse
If its anything like the evo you might want to try and wipe cache and dalvik cache when you get into recovery let it boot back up if that doesn't work try to fix permission if that doesn't work wipe battery stats when your phone is at 100% using battery calibration app and if none of that works do a full wipe and flash a new ROM or unroot and run the ruu of the stock ROM .
Sorry I know nothing about that phone so IDK if any of that will work for you just trying to help and those are pretty much the steps I would take.
Sent from my PC36100 using XDA App
Happened to me
Hey guys this happened to me and i was running cm and sense roms i have had alot of experience with this and its an actual glitch that causes the os to stack on each other and confuse the boot the only way to fix is to wipe the entire phone back to stock if that dosent work call sprint and they gladly replace ur phone due to manufacture defect its been happening to unrooted phones also from the updatesnot being installed properly phone needs to be wiped every time u do a new rom
Hello there,
I just rooted and flashed a custom recovery to my S3 today. Afterwards, I installed CyanogenMod through the CWM recovery and rebooted, however,after the reboot the device powered off completely. Now when I try to turn on the device I get a grey battery icon with a static circle on it, and it does not proceed any further. I cannot access recovery mode or even get to the Samsung loading screen. Plugging the device into the wall charger doesn't seem to be doing anything as it has been 'charging' for over 30 minutes and still does not power on. I've been scouring the net for hours looking for answers, but the few people who seem to have the same problem have not found any sort of resolution. There are all sorts of tricks people are suggesting such as putting your battery in and plugging the cable in, vice versa..etc but nothing seems to work. The phone was working just fine and the battery still had a good 30-40% charge when this happened. Does anyone know what the issue could be? I cannot even get it serviced because I had JUST rooted/custom recovery'd it when this happened, so just my luck with that. If anyone could help me it would mean a lot. Thank you for reading.
Regards,
Mike
Cryceratops said:
Hello there,
I just rooted and flashed a custom recovery to my S3 today. Afterwards, I installed CyanogenMod through the CWM recovery and rebooted, however,after the reboot the device powered off completely. Now when I try to turn on the device I get a grey battery icon with a static circle on it, and it does not proceed any further. I cannot access recovery mode or even get to the Samsung loading screen. Plugging the device into the wall charger doesn't seem to be doing anything as it has been 'charging' for over 30 minutes and still does not power on. I've been scouring the net for hours looking for answers, but the few people who seem to have the same problem have not found any sort of resolution. There are all sorts of tricks people are suggesting such as putting your battery in and plugging the cable in, vice versa..etc but nothing seems to work. The phone was working just fine and the battery still had a good 30-40% charge when this happened. Does anyone know what the issue could be? I cannot even get it serviced because I had JUST rooted/custom recovery'd it when this happened, so just my luck with that. If anyone could help me it would mean a lot. Thank you for reading.
Regards,
Mike
Click to expand...
Click to collapse
Copy and paste the name of the zip that you downloaded and flashed for me so I can better determine what you did bud, I don't want to say hard brick because this could be battery cells going bad coincidentally
Danvdh said:
Copy and paste the name of the zip that you downloaded and flashed for me so I can better determine what you did bud, I don't want to say hard brick because this could be battery cells going bad coincidentally
Click to expand...
Click to collapse
Hello there,
Thanks for the reply. I followed the instructions as per this thread:
http://forum.xda-developers.com/showthread.php?t=2179330
The CWM mod version I got from following Step 2 of that guide, which led me to this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
Afterwards, everything seemed to be working fine, so I grabbed a copy of the official CM latest nightly for my device, wiped/factory reset, and installed the ROM + gapps. After I reboot, the phone shut off, and this has been going on since. I am able to get into download mode, as I have just discovered, but I cannot get into recovery mode or turn the phone on past this mysterious grey battery icon.
Thanks for your time,
-Mike
Cryceratops said:
Hello there,
Thanks for the reply. I followed the instructions as per this thread:
http://forum.xda-developers.com/showthread.php?t=2179330
The CWM mod version I got from following Step 2 of that guide, which led me to this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
Afterwards, everything seemed to be working fine, so I grabbed a copy of the official CM latest nightly for my device, wiped/factory reset, and installed the ROM + gapps. After I reboot, the phone shut off, and this has been going on since. I am able to get into download mode, as I have just discovered, but I cannot get into recovery mode or turn the phone on past this mysterious grey battery icon.
Thanks for your time,
-Mike
Click to expand...
Click to collapse
kk download you're stock firmware and flash it in odin, something went wrong my friend so you're going to have to start over
stock roms are here http://forum.xda-developers.com/showthread.php?t=1968625
the good news is download mode = soft brick so you are in luck! My guess is the ROM was corrupt or just a very horrible flash =/
Danvdh said:
kk download you're stock firmware and flash it in odin, something went wrong my friend so you're going to have to start over
stock roms are here http://forum.xda-developers.com/showthread.php?t=1968625
the good news is download mode = soft brick so you are in luck! My guess is the ROM was corrupt or just a very horrible flash =/
Click to expand...
Click to collapse
Thanks very much! I was able to use the stock firmware in conjunction with Odin to get myself back up and running!
Now the issue remains, is there any way to install CM 10~ on this device? I cannot find a proper version of CWM aside from the 'universal' one which I mentioned above, however, if I try and flash any version of CM using that recovery, it gives me a Status 7 error, which people say is due to an old recovery version. Any idea as to where I can find a working (new) version of CWM for this device?
Kind Regards,
Mike
All up to dates CWM are there:
http://www.clockworkmod.com/rommanager
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
---------- Post added at 10:38 PM ---------- Previous post was at 10:34 PM ----------
And here show to install it:
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
I've solved the issue. Thanks for all the help.
The problem was that apparently I had an outdated bootloader which wasn't compatible with newer versions of CM and CWM. I installed the new bootloader from a thread here in the S3 forums and then flashed a new version of CWM and managed to get CM running.
I'm having new, unrelated issues now, but I'm sure I will be able to solve those.
Thanks again
I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.
JimmyDeemo said:
I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.
Click to expand...
Click to collapse
If you want good rom for gaming and everything else, then try gaming hybrid 2.1.2
Amazing rom with 190 mb free RAM on startup
And there is no bugs.
JimmyDeemo said:
I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.
Click to expand...
Click to collapse
What kernel are you using?
When the screen goes black can you see the phone in if you run adb devices?
Jure220 said:
What kernel are you using?
When the screen goes black can you see the phone in if you run adb devices?
Click to expand...
Click to collapse
Hi Jure220, thanks for the reply. I'm using the 480p version of the one you recommended in the ROM thread here; http://forum.xda-developers.com/showthread.php?t=1804003.
I'm not able to try adb devices right now, but will do later. It's like the phone is still running but just the screen won't turn on. Sometimes I can get it to come alive with by opening the slider. When booting with the problem, I get one vibrate to show that the power has been pressed, then another for the kernal logo (used to indicate going into the recovery menu). It's very strange, I will get back to you on the adb devices but is there any other details I could get you?
Cheers for the help.
JimmyDeemo said:
Hi Jure220, thanks for the reply. I'm using the 480p version of the one you recommended in the ROM thread here; http://forum.xda-developers.com/showthread.php?t=1804003.
I'm not able to try adb devices right now, but will do later. It's like the phone is still running but just the screen won't turn on. Sometimes I can get it to come alive with by opening the slider. When booting with the problem, I get one vibrate to show that the power has been pressed, then another for the kernal logo (used to indicate going into the recovery menu). It's very strange, I will get back to you on the adb devices but is there any other details I could get you?
Cheers for the help.
Click to expand...
Click to collapse
If its posible run adb logcat when the screen still works and keep it connected until the black screen apears and post the log in a txt file. But it isnt necessary. But if you reflash the rom it shuld work fine. And if it dosent try the new update I just released
Jure220 said:
If its posible run adb logcat when the screen still works and keep it connected until the black screen apears and post the log in a txt file. But it isnt necessary. But if you reflash the rom it shuld work fine. And if it dosent try the new update I just released
Click to expand...
Click to collapse
Yes I did notice that you had posted v1.3, will give that a try. I was a bit confused as to why the ROM would affect the screen on boot, but this is me assuming that it is something to do with the ROM at all.
Out of interest, did I need to use any specific settings when formatting /system ready for the ROM? I did a full wipe and fresh Kernal install at the time so had to format it.
JimmyDeemo said:
Yes I did notice that you had posted v1.3, will give that a try. I was a bit confused as to why the ROM would affect the screen on boot, but this is me assuming that it is something to do with the ROM at all.
Out of interest, did I need to use any specific settings when formatting /system ready for the ROM? I did a full wipe and fresh Kernal install at the time so had to format it.
Click to expand...
Click to collapse
When you flash the rom /system will be formated automaticly, and I also doubt it is a rom issue I think something went wrong while flashing...
Jure220 said:
When you flash the rom /system will be formated automaticly, and I also doubt it is a rom issue I think something went wrong while flashing...
Click to expand...
Click to collapse
Hi Jure2020, so I just flashed the ROM again with v1.3, booted fine after flashing. Powered off and then black screen again. I think that it must be a Kernel issue, do you have any other recommendations for Kernels compatible with your ROM?
I tried adb devices btw, all I got was the follwing;
C:\Development\Android SDK\platform-tools>adb devices
List of devices attached
CB5A1E0AJ2 device
C:\Development\Android SDK\platform-tools>
JimmyDeemo said:
Hi Jure2020, so I just flashed the ROM again with v1.3, booted fine after flashing. Powered off and then black screen again. I think that it must be a Kernel issue, do you have any other recommendations for Kernels compatible with your ROM?
I tried adb devices btw, all I got was the follwing;
C:\Development\Android SDK\platform-tools>adb devices
List of devices attached
CB5A1E0AJ2 device
C:\Development\Android SDK\platform-tools>
Click to expand...
Click to collapse
Try to reflash the kernel or use lupus ics/gb one and if it still dosent work reflash the firmware, btw when it first happend did you drop the phone or something?
Jure220 said:
Try to reflash the kernel or use lupus ics/gb one and if it still dosent work reflash the firmware, btw when it first happend did you drop the phone or something?
Click to expand...
Click to collapse
Yeah I will try re-flashing a new kernel this evening. Will try this one; http://forum.xda-developers.com/showthread.php?t=2167766.
No honestly, just one time I noticed it didn't wake the screen. Then it got a bit more regular, now it's pretty much every time the phone is left idle for a while, the screen just won't come on. The phone is active, I can 'unlock' it by swiping; I get the haptic feedback and hear the unlock noise. The phone is running, just the screen is off. I even thought it could be a CPU clocking issue, so used SetCPU to force the minimum speed up for resumption and no luck their either.
I have been thinking that it could be a hardware issue, my phone is kinda old now, but the thing is once the phone is on, it's on. I've gamed on it for a good hour or two with no problems, then pressed power to sleep and immediately haven't been able to turn it back on again. It's just very strange, thanks for the help though.
Hi JimmyDeemo,
I think your problem is flex cable related. I've also experience this before. After I replaced the damaged flex cable, my phone just work fine....:victory:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
biga72112 said:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
Click to expand...
Click to collapse
Edit: --> I was able to install TWRP using Mobile Odin. Now I'm going to change the bootloader and see if that fixes the problem.
biga72112 said:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
Click to expand...
Click to collapse
If the phone powers on itself immediately the battery is replaced, i.e. without you having to press the power button, chances are 99% you have a stuck power button problem. It's not uncommon with this device and can be routinely fixed at any repair shop or by DIY if you have the right tools and technical resources.
If the phone is working OK (other than the booting issue), I'd stay off flashing bootloaders to avoid bricking
Larry2999 said:
If the phone is working OK (other than the booting issue), I'd stay off flashing bootloaders to avoid bricking
Click to expand...
Click to collapse
Thank you very much for the reply!
No its not a power button issue. I DO have to hold the power button to power on. Here's what happens when the restart fails...
I have to:
1) pull the battery
2) sometimes, I have to hold the power button WITHOUT the battery in for a few seconds (I've had laptops that have this issue before. I think it's a static buildup of some sort.)
3) reinsert the battery
4) hold the power button, and
5) if I'm lucky, the phone will boot up.
This is only about 50% successful. Sometimes I have to do this 3-4 times.
Now, I don't know if this is a hardware issue, or a firmware/software issue. If it IS a hardware problem, then I may just replace the phone. If it's a firmware/software problem, then hopefully it can be fixed. If it's a problem with the bootloader, and a fix isn't possible, then I'll just keep on truckin' till I get a new phone.
biga72112 said:
Thank you very much for the reply!
No its not a power button issue. I DO have to hold the power button to power on. Here's what happens when the restart fails...
I have to:
1) pull the battery
2) sometimes, I have to hold the power button WITHOUT the battery in for a few seconds (I've had laptops that have this issue before. I think it's a static buildup of some sort.)
3) reinsert the battery
4) hold the power button, and
5) if I'm lucky, the phone will boot up.
This is only about 50% successful. Sometimes I have to do this 3-4 times.
Now, I don't know if this is a hardware issue, or a firmware/software issue. If it IS a hardware problem, then I may just replace the phone. If it's a firmware/software problem, then hopefully it can be fixed. If it's a problem with the bootloader, and a fix isn't possible, then I'll just keep on truckin' till I get a new phone.
Click to expand...
Click to collapse
It's almost certainly an hardware issue. Very unlikely a firmware problem would cause this and even more likely the bootloader would. With a bootloader issue, your phone likely wouldn't even boot at all. Power button problems present in several ways and a loose power button could cause the kind of issues you've described. I'd take it to a local tech shop for a quick look before giving up on it.
Larry2999 said:
It's almost certainly an hardware issue. Very unlikely a firmware problem would cause this and even more likely the bootloader would. With a bootloader issue, your phone likely wouldn't even boot at all. Power button problems present in several ways and a loose power button could cause the kind of issues you've described. I'd take it to a local tech shop for a quick look before giving up on it.
Click to expand...
Click to collapse
I may just wait and get me a new phone in a few months. I'm expecting a bonus from work, and I'll likely just get the new S5. Thanks for the information
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