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
Hey i hope all is good.
I really need your help. I have a TILT 2 cell phone and by mistake a friend activated the bootloader. Previously the ROM has been updated. the phone got stuck in that screen and the only way to turn it off is removing the battery. so, i try to reboot the phone and it only loads the bootloader with a flash message saying "no image file". ok, i though, the ROM was damaged and after reading a lot in the forums, i followed the instruction to put a new ROM. I connected the phone the the computer and the message in the phone changed to USB and my PC installed the HTC USB Sync driver (but Active Sync does not detect the phone); anyways, i ran the task 29 and a new rom. I was able to see the progress bar in both (PC and Phone) but then the phone reboots and loads again the bootloader. I tried to use the HARD SPL 1.00 as well but it does the same thing after finishing the flash it loads again the bootloader.
can some help me pls?? i'm new in this and the phone is a work tool for me i really need your help.
rgds
You should do the HSPL before flashing a ROM (unless it was already done).
I would try to flash the newest HSPL, then a ROM.
Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls
jsolanon said:
Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls
Click to expand...
Click to collapse
Hrm, have you tried doing a task29? Re-flash the ROM after task29.
yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do
jsolanon said:
yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do
Click to expand...
Click to collapse
So you've flashed the stock ROM? Have you tried relocking? Probably won't do much, but worth a shot I guess.
When you flash back to stock you flash the stock ROM, then relock, then reflash stock.
Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help
jsolanon said:
Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help
Click to expand...
Click to collapse
My phone is never turned off. I'm not sure what else to suggest, you've tried seemingly every step that could remedy this problem. Radio firmware probably won't help, but it shouldn't hurt either - you could try a new radio...
hi , this happened to me, solved it by reloading the rom again via sd, once it finish maybe you will see the bootloader screen again, so with stylus pres the reset buttom a few times until the rom boot , this can take several times to make it boot. after revive your cell , do a task29 then reload the rom again then do a hard reset, this happened to my 2 times, and its still alive ,good luck.
Same Problem
Hi,
I'm having the same problem. Installed the latest official ROM from HTC/ATT (gorgeous), and same problem after install. Whenever you try to reboot, it gets stuck in the bootloader screen. The last 50 tries it will not reboot at all, even after removing the battery and hitting the power button. This used to work occasionally.
Any other process anyone knows for getting the device to read the ROM?
Is the phone just worn out?
I suggest you reflash the shipped rom to your device and after the flash finishes and your device begins to boot immediately remove the battery to turn it off before it boots. Then replace the battery and press and hold the Send and End keys and while holding them down press the Power button and follow the instructions to factory reset(hard reset).
I have a One X S720e, CID_J15
I recently upgraded the hboot to 1.39, and since the update the phone has been going crazy. First installed a IceColdJelly 2.5.1 ROM. And after installing Gapps everything was okay at first but 5min into usage everything started FCing. starting from com.google.process to the launcher to every single application. And this just keeps happening. I ran a super wipe script installed other ROMS including the CM 10.1 and same issue kept happening.
After a day of this, the phone randomly started turning off and got stuck in APX mode. I managed to get out by holding power button and vol up + vol down for 40+ sec. The phone runs for a bit, boots into ROM, works for some time as long as no app is run. If i open ANY app at all, again the FC starts and eventually the phone reboots into the APX mode again.
Frustrated, i ran another Super Wipe Script, again tried to install the HBOOT 1.39 update, and then installed the STOCK ROM for a nandroid backup i had. But the same thing keeps happening. All apps force closing. So basically i cant use the phone.
PLEASE HELP ME. Anyone have any ideas whats wrong ? or could it be a hardware issue ? should i relock the bootloader and send it to a HTC service center ??
You did flash the boot.img for every specific ROM right?
I think if you send it to HTC they will charge you for the full repair service, which WILL cost you a lot of money.
Got no further solution for you buddy, good luck. Hope you can fix it before sending it to HTC
yup. Done evreything by the book. flashed all the boot.img files. The ROMs boot perfectly, just that after a while while im installing apps and or doing ANYTHING everything starts crashing.
My phone is still in warranty though. I read that if the phone goes into APX mode its usually a hardware problem. My question is why did the problem arise only after i updated the HBOOT. everything was just fine till then. I hope this issue is covered in warranty :'(
i have exactly the same problem!!
What you say, sometimes it will work for 5 minutes. But when you open an application it will force close and all the applications will start FCing.
Did you already solve the problem?
APX is a hardware defect ..... not much to do about that.
I have exactly the same problem! It all started with ICJ: gapps and almost all other apps started FCing after some time. After dozens of hard reboots I got stuck in APX mode. At least that's what I think. My PC recognized the device as "unknown devices", the screen was black, adb and fastboot didn't work. I managed to get out by pressing the power button + volume up/down for many seconds... I flashed numerous Roms in the past days and I always get the same FCs (especcially Gapps) - doesn't matter if it is a sense or an AOSP based ROM. So is this a hardware probelm? Is there any way I can solve it? If I send my HOX to HTC I'll most probably need to pay right?
Mr Hofs said:
APX is a hardware defect ..... not much to do about that.
Click to expand...
Click to collapse
Said it already ....
Mr Hofs said:
Said it already ....
Click to expand...
Click to collapse
sh*t Already thought so
so basically we're f*cked...
Yep
Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.
Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.
I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app
There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.
The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!
Do u guys have the most up to date version of whatever particular recovery that you're on?
Yep. I've flashed the stock recovery multiple times to no avail. :/
nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?
wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/
nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?
wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!
Hi all, hopefully someone can help, I was using my phone fine earlier when all of a sudden it just switched off, wouldn't turn back on at all. After trying for a while I've gotten into fastboot. I've tried booting into recovery but no luck.
I've since tried wiping cache - no effect. Flashing recovery - 'FAILED (remote: image update error)'. Boot recovery image - reports success, does nothing.
I'm S-ON, was on a custom ROM. Anyone offer any advice?
Thanks.
Also, the phone doesn't seem to stay turned off now, keeps booting itself into fastboot.
What the model of the phone
Sent from my GT-I9195 using XDA Free mobile app
It's a UK One M8.
After a couple of hours of messing around with no luck it's now just turned on. No idea what that was about. Afraid to turn it off now!
If anyone sees this and does have advice I'd still appreciate it, feel like I'm probably on borrowed time...
top_bunk said:
After a couple of hours of messing around with no luck it's now just turned on. No idea what that was about. Afraid to turn it off now!
If anyone sees this and does have advice I'd still appreciate it, feel like I'm probably on borrowed time...
Click to expand...
Click to collapse
have you had custom rom, recovery or root installed before?
I've only had this phone a month or so, rooted it pretty much straight away and installed Viper ROM. Left it alone since then waiting for Lollipop.
If you just mean experience wise, I've rooted all my phones for years, never had one randomly turn off for no reason and refuse to enter recovery though (thankfully), usually when I have issues its cos I did something daft!
Half way through Christmas day the phone froze up, completely unresponsive. Once the battery had died and I could turn it on again I was back to where I was, can't boot up, can't get to recovery, fastboot won't flash a new recovery, get the same failed message as last time.
Anyone got any ideas?
top_bunk said:
Half way through Christmas day the phone froze up, completely unresponsive. Once the battery had died and I could turn it on again I was back to where I was, can't boot up, can't get to recovery, fastboot won't flash a new recovery, get the same failed message as last time.
Anyone got any ideas?
Click to expand...
Click to collapse
you could try this
http://android-revolution-hd.blogspot.com/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html
Thanks clsA. I'll take a look at the link...
The phone started working again late last night though, again no reason, just did. I took the opportunity to update the recovery, do a full wipe and install a new ROM. Hopefully I won't see the same issue again, if I do I'll try out that fix.
Thanks!