A couple weeks ago, I finally figured out that Cyanogenmod wasn't auto-updating past CM 10.2 on my Evo 4G LTE because I needed to update TWRP to 2.7.1.2 and also get S-OFF and update HBOOT to version 2.10.0000. Although I had a couple stressful moments in updating all of that where I thought I might have accidentally bricked my phone (I'm still pretty new at flashing custom ROMs), I managed to get it all figured out and I updated Cyanogenmod to CM11. I can't remember whether I updated directly to Snapshot M11 or if I updated first to M10 and then M11, but at any rate everything worked out fine and I had no problems with my phone. Then I updated to snapshot M12 through the auto-updater when it came out a week or so after doing all the above, and again everything was working fine with no problems (though I did start having some lag sometimes when I was using the Kii keyboard app I had installed, or sometimes the keyboard would drop my swipe halfway through a word and type two words instead of the one that I wanted, which was happening at an increasing frequency in the days before my phone crashed). At any rate, a few days ago I was reading the news on a news app, then the screen froze, the operating system crashed (the screen just went black and the phone turned off), and ever since then I haven't been able to use the phone at all. It doesn't turn on now.
I have tried booting into recovery a number of times using the power + down volume combo, but I haven't been able to get it to work -- though I'm not sure if there's some trick that I don't know about how long to press down. The phone does not boot up into Cyanogenmod, either. The screen just stays black no matter what I do. Sometimes when I mess around with pressing the power button or holding it for different periods of time and/or pressing and holding the down volume, the phone has made some responses. Sometimes the capacitative buttons will light up for a couple seconds before going black again, and sometimes the phone will vibrate for a half second. (Also, when I have it plugged in, sometimes I can get the battery charging light to turn off or on.) But after that, the screen always just stays black. It seems like I bricked my phone, but I wanted to ask before throwing in the towel. The thing is, sometimes when I was flashing new ROMs, my phone would get into a similar state (I was never quite sure what was going on) and I'd be able to get it into recovery or get it to boot regularly (though I was never quite sure what exactly I did to make it work again -- I always kept trying different combinations and pressing-lengths of the power and volume down buttons like I've been doing recently), so it seems like maybe there's still a possibility I could do something similar now.
Any idea what I should try? Any idea what might have happened to lead to a crash like this, so that I can avoid making the same mistakes or having the same problems in the future? I would appreciate your help so much; I'm overseas right now and was depending on having my phone to stay in touch with people. Thank you!
Related
Long time lurker, first time poster. First, let me thank all the devs and countless others for all of the support. OK, so i've had the U.S. TMO HD2 since around launch time, and its performed like a champ until about 2 days ago. The touchscreen stopped responding all together. At the time I was running:
ChuckyDroidRom w/ shubCRAFT 1.5 (8/30 build I believe)
2.12.50.02_2 Radio
HSPL 2
Had been running android for the last 2 weeks. Screen Stopped responding in both WinMo and Android. I scrapped android, and tried a few different WinMo roms. Switched back to stock rom+radio and now with constant soft and hard resets, I can get it to work for like 5 minutes every few hours.
The only relevant threads I found dealt with individuals who encountered problems after opening the housing. Also I read that flashing the stock rom via SD brought the phone back to a repairable status if I were to send it in. I tried, extracting and renaming the signed .nbh from a stock rom, then holding vol down while powering up. I get to the boot menu and a white screen flashes briefly, and then it just reverts back to the red/green/blue/white screen. Also reformatted card countless times.
Long read, but thanks in advance. Can the screen be fixed? If not, how can I get my HD2 repair ready?
almost same prob
similair situation to yours except im running MDJs cm7 gingerbread 2.6 NAND android rom right now. my screen started doing that back when i had 2.0 of the rom yet it persists after updating. my screen will let me keep going for any length of time unless i hit standby button. that puts me in a 50/50 of the screen tanking on the lockscreen. sometimes it works after i try again. however, every single time i hold the standby button to say reboot that seems to just turn my touchscreen function off flat out. battery comes out to fix that so basically i have to pull my battery to shut it off. it hasnt stopped working in the middle of anything only whem the standby/power button gets touched. this hd2 has never fallen down either so not an oops i dropped it but it didnt crack moment lol
Really hope someone can help me here.
I rooted, and put CM10.2 on my phone a month or two ago (don't play that much with ROMs, etc), but fancied a change from stock.
Anyways, it's been fine (although battery life not quite as great as before, but hey ho), this evening just got a WhatsApp message, dropped the notification bar down, clicked on it to open Whats App, and the phone rebooted... And then continued to just reboot over and over after 2-3 seconds (showing the i9300 Samsung logo with the red ! in the top left).
Removing battery stops this obviously, but weirdly when I put the battery back in boots straight away, and continues to just loop like that. Holding power, home, vol up/down makes no difference (been playing with this for about an hour now, and searching other peoples solutions, someone said 5 times wait, and release). Just can't get anything other than this loop, just weird that I can't actually turn it off either.
Suggestions please?
Thanks Gunja
Booting as soon as battery is inserted indicates power button sorted out, try wiggling it or seek a repair.
Yes I believe thats the case, as I have actually got it into the "Accept different OS" mode, stays there for 2 seconds and reboots. Nothing seems physically weird about the power button.
It did the sudden die thing a few months back, and I returned it to Sammy UK and they fixed it (due to 2 year warranty) in 2 days. It's still under 2 years old, so will give them a call. Was rooted before, but didn't show the red ! in the left left. Hope that they don't mind that, as this does seem to genuinely be a physical hardware problem not software.
If you just hold the power button on the S3 when it's booted, just it just turn off eventually? How annoying, 2nd problem with it in the last 4-5 months, wonder if will get another sammy when upgrades due in a couple of months. Lets see how their support is again this time round!
Hello XDA,
Way to start off my Friday Hope EVERYONE has a GOOD AND SAFE weekend!
PROBLEM:
Out of the blue it started to reboot itself more often, always had issues with candykatt even after few re-install and wipes. Last night, it would reboot with in 1-5 minutes after full boot and load, then the time decreased to 30 seconds. Till finally 1 second, that is if i am lucky to full boot and load. (auto attempt to reboot with multiple vibrations).Tried to load into odin and twrp, and same symptoms first will fully load into those two for 30 seconds and then auto reboot.
ATTEMPTS
Tried various batteries of various charge types percentages, stock samsung battery fully charged another 2500MAH even 5400MAH. Tried taking sim and memory card out and same thing! (debating on opening up and clean, hope just power button even though feels fine)
CANDYKATT:
I love the rom, work well for couple months with minor popular known issues, like camera not working and random but not frequent freezes. And power hungry, was waiting for updates in forum but never happened. Not as tech savy as i used to be (not my first rom, ran every blackstar and everything from GB, JB,KK and just not on this device) still a not a pro or almost out of noob stafe
XDA FAMILY HELP ME PLEASE!
would love to fix issue with out wipe or reflash at the moment to save files (did not have memory card long)
Phone:
AT&T i717
CandyKatt (Non Uber)
TWRP
64gb SD
No Other tweaks or fancy anything
All Buttons seem fine
No Rattles haha
NO WARRANTY
(Charge port messed up, no major accident besides tripped on power cord while plugged in)
Power Button
XDA World,
Attempt Power Button cleaning and pop out with screw driver (not forced). My button worked fine, looked fine and felt fine. After attempting ODIN and TWRP many times, idk what I did but re flashed and loaded into candykatt os set up. My files still there, and so far has been on for a few minutes as I transfer my photos to SD (full battery).
Uh oh random auto reboot!!! dang it
working better
I still do not know what I did, entered odin and twrp so many times (as mentioned old post). After it reflashed due my button mashing between those two, it works better random reboots even vibrating thing. But does the bad vibrations here n there until I hold power button then reboots.
And was able to sync to get photos off.
I am going to try a new rom, sorry candykatt ...promise soon as bugs are fixed I will re-install
Many times the stuck power button issue seems okay it may not be. I always tell folks to flick the phone in the back a few times, even if the button feels the click. Flick it. Some are courageous enough to take a swab and alcohol to the contacts for cleaning. Not me.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Hi everyone. I'll try to make a long story short while being thorough. Any help is much appreciated in advance.
TLDR Version: after messing around trying to get a working ROM and finally getting Tachyon 4.3.1 to load (without the SIM Card in), I powered down and the Rezound no longer powers on in any mode nor is it registered by adb. LED lights up while plugged in, that's it.
Complete version:
I spent a few days reading up on rooting & ROMing - but apparently not long enough - then spent an arduous night attempting to get a working ROM on my Rezound. I initially used AmonRa to get RezROM EX 3.4 to load up, but was stymied by constant "com.android.phone has stopped working" messages. After attempting several fixes, I formatted all back to Ext 3, and wiped the phone to factory settings (I know, I know...) in an attempt to start fresh. After that sloppy attempt, the phone wouldn't get past the initial white HTC screen, so I did the following using less than stellar judgment: I removed the Verizon SIM Card, rebooted, and installed Tachyon 4.3.1 (linked at bottom) in AmonRa recovery. Miraculously, I thought, the phone loaded up Tachyon and after one "com.android.phone has stopped working" message, I was able to use the phone, albeit with no network connection. I thought all I had to do was power down, put in the SIM Card, and maybe things would be alright.
Instead, what happened was this: I powered down, took out the battery (which had some charge) and put the SIM Card in. When I pressed the power button back on, the phone did not turn on. Unplugged, not even the LED would light up. I plugged it into my PC, at which point the LED does turn on, but pressing power only causes the buttons on the bottom portion of the phone to light up for a few seconds. That's it. The screen does not do anything. Holding Volume Down + Power does the same thing; it does not vibrate or boot to Recovery. Lastly, adb no longer registers the phone's presence (error: device not found). I plug it in the USB, hear the chime, but commands like adb list, adb reboot, etc. do nothing. The phone appears as an external drive in Explorer, but it cannot be opened. I've now tried two batteries and let the phone charge for a few hours. Still no results.
If I've bricked the phone, I understand. I fortunately have another Rezound I can fall back on. I understand the risk of taking the unresponsive phone to the Verizon store, so I'm asking for help/suggestions here. Thanks!
DentalAppointment said:
Hi everyone. I'll try to make a long story short while being thorough. Any help is much appreciated in advance.
TLDR Version: after messing around trying to get a working ROM and finally getting Tachyon 4.3.1 to load (without the SIM Card in), I powered down and the Rezound no longer powers on in any mode nor is it registered by adb. LED lights up while plugged in, that's it.
Complete version:
I spent a few days reading up on rooting & ROMing - but apparently not long enough - then spent an arduous night attempting to get a working ROM on my Rezound. I initially used AmonRa to get RezROM EX 3.4 to load up, but was stymied by constant "com.android.phone has stopped working" messages. After attempting several fixes, I formatted all back to Ext 3, and wiped the phone to factory settings (I know, I know...) in an attempt to start fresh. After that sloppy attempt, the phone wouldn't get past the initial white HTC screen, so I did the following using less than stellar judgment: I removed the Verizon SIM Card, rebooted, and installed Tachyon 4.3.1 (linked at bottom) in AmonRa recovery. Miraculously, I thought, the phone loaded up Tachyon and after one "com.android.phone has stopped working" message, I was able to use the phone, albeit with no network connection. I thought all I had to do was power down, put in the SIM Card, and maybe things would be alright.
Instead, what happened was this: I powered down, took out the battery (which had some charge) and put the SIM Card in. When I pressed the power button back on, the phone did not turn on. Unplugged, not even the LED would light up. I plugged it into my PC, at which point the LED does turn on, but pressing power only causes the buttons on the bottom portion of the phone to light up for a few seconds. That's it. The screen does not do anything. Holding Volume Down + Power does the same thing; it does not vibrate or boot to Recovery. Lastly, adb no longer registers the phone's presence (error: device not found). I plug it in the USB, hear the chime, but commands like adb list, adb reboot, etc. do nothing. The phone appears as an external drive in Explorer, but it cannot be opened. I've now tried two batteries and let the phone charge for a few hours. Still no results.
If I've bricked the phone, I understand. I fortunately have another Rezound I can fall back on. I understand the risk of taking the unresponsive phone to the Verizon store, so I'm asking for help/suggestions here. Thanks!
Click to expand...
Click to collapse
So, if you disconnect the USB cable, remove and reinsert the battery (also, try another battery), then press and hold POWER+VOL DN for a few seconds are you able to get into HBoot? If not, it is likely borked, but not because of flashing a ROM, it was probably just it's time to go...
got it working
Thanks for the reply.
Just to update this post, I did eventually get the Rezound working again. Clearly it wasn't totally borked, but I guess I had in fact drained the first battery without knowing it - when I inserted the second battery, which I believe did have some power left, for some reason that power wouldn't register with the phone. I left it plugged into USB for a couple more hours and after several on-off and USB plug-unplug attempts, I eventually got it back into HBOOT (not to give myself credit for this), to my relief.
I then switched to Clockwork revival and managed to get Cyanogenmod 10.2 (10.2-20131217-Flyhalf2015-vigor) working on the phone. Without understanding what happened with perfect clarity, I surmise the reason the install wasn't working in the first place was that I was attempting to install a different kernel simultaneously - ie. from recovery mode without a reboot in between. Either I got the order of installation wrong (ROM before kernel or ROM after kernel I don't know) or that kernel was not compatible. Anyway I wiped the phone again and just installed Cyanogen without attempting to install a kernel and it worked - I'm guessing with cyanogen's own kernel.
So now I have Cyanogen working and ROM Manager set up with a backup. While the new features and customizability are cool, the system overall is somewhat glitchy. Don't know if that's due to the version of cyanogen, the kernel, my installation technique, or the phone hardware. It's certainly not unusable and I'm going to leave it as-is for a bit after this ordeal, but the following glitches happen occasionally:
-not all lock screen features appear, or lock screen background won't appear
-phone screen will suddenly fill up with random 'glitchy' patterns of colored pixels
-screen will remain black after tapping power switch to go from idle state to using. backlit keys will light up but will have to remove battery and restart device to work again
-battery life is still poor if not a bit worse (probably not a glitch, just rezound's stock battery)
But it's now an old piece of hardware and I'm still happy I carried the process through to the end. Given that I couldn't stand certain aesthetic features of the stock OS, I am content with the results for now.
Fin
DentalAppointment said:
Thanks for the reply.
Just to update this post, I did eventually get the Rezound working again. Clearly it wasn't totally borked, but I guess I had in fact drained the first battery without knowing it - when I inserted the second battery, which I believe did have some power left, for some reason that power wouldn't register with the phone. I left it plugged into USB for a couple more hours and after several on-off and USB plug-unplug attempts, I eventually got it back into HBOOT (not to give myself credit for this), to my relief.
I then switched to Clockwork revival and managed to get Cyanogenmod 10.2 (10.2-20131217-Flyhalf2015-vigor) working on the phone. Without understanding what happened with perfect clarity, I surmise the reason the install wasn't working in the first place was that I was attempting to install a different kernel simultaneously - ie. from recovery mode without a reboot in between. Either I got the order of installation wrong (ROM before kernel or ROM after kernel I don't know) or that kernel was not compatible. Anyway I wiped the phone again and just installed Cyanogen without attempting to install a kernel and it worked - I'm guessing with cyanogen's own kernel.
So now I have Cyanogen working and ROM Manager set up with a backup. While the new features and customizability are cool, the system overall is somewhat glitchy. Don't know if that's due to the version of cyanogen, the kernel, my installation technique, or the phone hardware. It's certainly not unusable and I'm going to leave it as-is for a bit after this ordeal, but the following glitches happen occasionally:
-not all lock screen features appear, or lock screen background won't appear
-phone screen will suddenly fill up with random 'glitchy' patterns of colored pixels
-screen will remain black after tapping power switch to go from idle state to using. backlit keys will light up but will have to remove battery and restart device to work again
-battery life is still poor if not a bit worse (probably not a glitch, just rezound's stock battery)
But it's now an old piece of hardware and I'm still happy I carried the process through to the end. Given that I couldn't stand certain aesthetic features of the stock OS, I am content with the results for now.
Fin
Click to expand...
Click to collapse
I had some unfortunate nastiness happen to my Rezound a while back which prompted me to go out and get an M8, but I did eventually get the Rezound 99% functional again.
First off, cell phones in general rely on something called NAND memory for all mass storage. It's decently quick stuff, but not the most reliable storage medium in the known universe. Basically, it slowly dies with use. NAND only has so many read/erase/write cycles before it begins to degrade. This can lead to very quirky corruptions in the partitions, and that's kind of what it sounds like has happened to your Rezound. The fix that got mine back to working order was a complete stock RUU restoration followed by a "factory reset" through Hboot. That will wipe and rewrite all of your partitions. Then flash your custom recovery, ROM, and kernel.
As for flashing ROM's and kernels in the right order, you want to flash the ROM and then the kernel. A lot of devs recommend flashing the ROM, then booting it up, then flashing a custom kernel, however, if you know you've got a working combination of ROM and kernel, there is no reason you can't just flash the ROM and kernel (in that order) at the same time in recovery.
Hi,
I've had my Z3TC for around 5 years now and still love it but has been having a few issues recently, notably the battery life is getting worse, but it's still usable. However, yesterday, something strange happened to it. The power on/off button stopped working when I pressed it once (double press for camera still worked), so I couldn't turn it off or turn the screen off (other than my closing the case cover) and one of the volume buttons didn't work either.
Then, the battery dropped from around 40% to 0% and it shut down. I charged it overnight and this morning when I turned it on, all the buttons were working again but it was in safe mode. I tuned it off/on multiple times, restarted it, rebooted in safe mode then rebooted again hoping it would go to normal mode, but none of this work.
I've now done a full factory reset and it is still stuck in safe mode (and I've restarted it, turned on/off multiple times). Are there any suggestions for how I can get it back to normal?
Thanks,
Frank
Nearly the same thing happened to me. It happened about 3 years ago. The power button stopped working (just like you), so I chucked my Z3TC. To this day, it was - and is still one of the best - phones I ever had. I ALWAYS got asked questions about it. I own an iPhone now, but I still love the Z3TC. The camera was terrible, but everything else about the screen was solid. Just wished they updated the OS on it, but due to Google and the chip restrictions, never got far. Either way, I'll never forget this phone. Pity our time came to an end due to that power button breaking.
Also stuck
Same thing also happened to me.
I had the tablet for quite some time and the battery would start going straight to 0% from quite a high number. And also my volume down button doesn't work and I am stuck in safe mode. Rebooting, poweroff, etc doesn't make it get out of safe mode.