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
Related
Hi guys,
I've had me evo3d from the first day it came out here, august 6th. Never had any problems at all. Until now. Srry about the novel... I've highlighted the most important parts for your convenience.
About 2 weeks ago, i dropped my phone from about 60cm, but with no apparent damage. Later that night, my battery went completely empty (not unexpected, it was a long day). Plugged it into the charger when i got home, led flashed to indicate a completely empty battery then stayed on to indicate charging, no problem. Then it stopped charging after a little while and didn't resume.
I took the phone apart so see if maybe some wire had come loose from falling. None had, but after putting it together again, it did charge again for a moment (also showed flashing leds again), and then it stopped again.
A friend of mine suggested it might be that battery's contacts, so he scratched them with a screwdriver. This actually seemed to help and everything was fine for about a week and a half.
Now trouble has started again. Taking the battery out and blowing on the contacts (NES cartridge style) worked at first, giving me about 10 minutes until it died again. But it seems to be getting worse, and by now it will only turn on or even just charge sporadically. Always flashing the led, indicating the battery is completely empty.
additional info:
It's not the rom that's faulty, as i hoped at first (re-installed an old rom after trying some ICS-goodness the day before all this started), because it also crashed in Recovery at least once. And i've already installed a diffrent rom without any success.
When it crashes, it doesn't just die instantly. Instead, it freezes for about 1/3 of a second. When it crashed in Recovery, during this freeze the text got a weird yellowish background-color and a different font color as well.. but the parts of the screen without text retained their original looks.
What else could i try to fix this? I don't know anyone with a shooter, but i've heard pyramids battery works as well, is this true? Can i try one of those to see if it's just the battery that's tripping?
Let me know if you need any more info.
Thanks a lot for your help in advance!
I didnt had the same problem, but I had something similiar.
Try this:
1. Unplug from charger
2. Get battery out
3. Wait a bit, and put battery in
4. Press Volume Down + Power button
or
4. (better solution) Press Power + Volume Up + Volume Down + Camera button
5. Phone will start
6. Just plug it in
It's known as "Chargning bug" when you flash some roms
It's the charging bug due to flashing clockwork recovery-- search the forum there are many similar threads and solutions
Hi,
Thanks for your responses. But that's not what's happening. In fact, i have an old clockworkmod that's never been a problem at all and i never updated it.
I tried your solution, though, but it only allowed my phone about 15 minutes of charging before it died again.
If it charges, it charges just fine while the phone is off.
Hello everyone.
After several hours of googling and going through tons of pages here on xda I decided to make this post.
First, let me explain when the problem started:
The issue
Yestarday I was playing candy crush when suddenly the game started to get "laggy". I didn't think of it, exit the game and left my phone on the table. A few hours later I wanted to use it again only to find the small hard drive icon on the top saying something about Memory almost full. I clicked it and it took me to "All installed programs". I saw that it had used 1.9 gb of the total 2gb and only 20-40 mb were free. I started immediately to uninstall apps that I no longer use to see if this could help. It did for a few seconds but the memory got filled fast again.
This is when I started to search the net for solutions. The first post I read was to delete some log files so i did that. But it didn't change a thing. I thought to myself that I should make a backup of my stuff so it wouldn't go lost if I had to wipe the phone. But before I got to it my phone shut down. Now, when I turned it back on it would just start Media Scan and shortly after shut down. This is where I am now.
I am running stock ROM (have never rooted before).
What I have tried
I found the stock ROM (4.1.2 I think) and I flashed it with Odin thinking this would stop my phone from restarting. It did not.
I have tried to clear cache from Recovery Mode several times with no effect.
I have tried to wipe the phone from Recovery Mode but when I am half way through the setup process of setting up the phone for first use, it shuts down.
My battery also drops in power after the shutdown happens, so in this very moment I am waiting for the battery to charge fully so I can try to calibrate.
Please let me know if you need some additional information and I will happily provide what I can.
Thanks in advance!
You have flash stock and it still shuts down? Hardware problem. Battery old? Try with charger plugged in. Flashing stock makes it like new so there should be no faults. Id say battery is about had it. What firmware did you flash and were from?
My phone (and battery) is almost 1 year old so im still under warrenty if something fails. I just don't want to hand it in and wait weeks to get it back if I can handle it myself
Yes I flashed with stock ROM from samsung-updates.com/device/?id=GT-I9100 so it should be good.
It makes no difference if the charger is plugged or not (which I find odd cause shouldn't it be able to keep awake while on alternating current?).
At the time typing this my phone is online and I am currently backing up photos (yay!!!). What I did was to not type in PIN code so maybe the sim card is the trouble (also 1 year old). I will report back when everything is backed up.
Update:
4 seconds after entering the PIN code the phone shuts down. Also it plays about 10 silent "clicks". Can't hear if its from the phone or from the speaker.
Update2:
Alright so I tried inserting another sim card that I have which has no pin code. The phone boots (but only when plugged) but shuts down after statup, exactly the same place/ after the same time as when I use the other SIM and enter the code.
I have had it online for 5 minutes now without typing the pin so my guess is that it's some setting it loads with the sim that makes it crash (but its a wild guess).
It's also worth noting that it doesen't drop in battery capacity when it shuts down ATM.
Id still say battery problem but could be wrong.
I see some sort of flicker on the screen just before it shuts down. I don't know if this could help someone to address the problem.
For the full memory issue i solved wiping log files in the "/data/log" dir, i had almost 1000 log files, 1 MB each.
Hope this is your problem too.
There is hardly anything left in the /data folder. I have tried to delete the logs (65 mb) from Phone/log but that didn't change a thing. Im going to send the phone to the company i bought it from next week.
Ive recieved a battery that I ordered from china and the phone works now. So the problem was the battery just to let everyone know.
Glad you sorted it.
My Samsung Galaxy SIII smart phone has only recently been having issues. My phone will turn on, will be charged and function as normal - ie, no performance issues at all when the phone is actually on. But sometimes, my phone will randomly shut off with no prompt or message. Sometimes it will attempt to turn back on itself, other times I need to press or even hold the power button to turn it on.
The real problem is when it boots, it SOMETIMES (3/5 times average) will begin to boot, then the screen goes black again - ie, the Samsung logo will show up upon vibrating, then shut off or reboot and try again (this can sometimes happen singularly or in tandem). Other times, it will boot as normal, sometimes working normally, other times just randomly doing the abrupt shut down, and the cycle starts over.
I've tried taking the battery out, rebooting it, booting to safe mode, removing battery + keeping it out for ~10 minutes to discharge, etc. My phone isn't up to date, as my phone is rooted. However, I haven't modified my phone or done anything to it in a long time, and this has only has begun happening recently. My current firmware is rooted stock Android 4.2. Are there any other solutions besides formatting my phone? I cannot send it in/get it replaced by my provider as my warranty has expired. Thank you. :angel:
Go to the Play Store and download emmc brickbug check.
Get that diagnosed.
If it's good i suggest you do a full wipe and update it to the latest samsung 4.3 update.
Ultimate GS3 sudden death thread.
Well you better get up to date, best to start with a factory reset and the latest stock rom first.
I guess you're running an unstable leaked 4.2.2 firmware,so I would suggest you to install stable 4.3 firmware.
Maybe your power button got stuck..
To find out, push your power button and keep hold it even the "samsung galaxy s III GT-I9300" appear.
Do you experience the same thing or not.
TheoDores said:
Maybe your power button got stuck..
To find out, push your power button and keep hold it even the "samsung galaxy s III GT-I9300" appear.
Do you experience the same thing or not.
Click to expand...
Click to collapse
I found a fix for my S3 which was doing EXACTLY what many of you are describing. I will get to the fix and it will sound ridiculous, but it worked for me and for the other people responding to the posted fix. ***** Hint: my problem was the power button and the fix was free and easy though may require you to be pissed at your phone as I was at the time.
Before getting to what fixed my phone. It seems like every one with a Samsung phone Sh*tting out in this manner should go through the well-conceived sequence I post below in the link. That guy though through the problem and made a great help list even though I found myself with a phone that was a mess even after all of those steps. My phone just vibrated when I tried to start it or maybe it began to show a graphic screen of the boot process before it went to black again and just vibrated. I am stuck with 4 more months of verizon contract so I was desperate and unahppy to say the least. I tried at least 50 time to boot my phone yesterday and went to a verizon store they were no help as expected especially when they saw a boot screen image that they did not recognize... I was one of those rooting creeps that they are not obligated to help...
first link:
http://thedroidguy.com/2014/03/fix-galaxy-s3-wont-turn-troubleshooting-guide/
A stuck or malfunctioning power button can cause... getting random reboots, lack of starting, lack of posting, getting stuck at various screens in the boot process and then going to a black screen which may just accompany a vibrating phone or a seemingly dead phone. Our problem is the power button being "stuck" underneath/inside of the janky, crappy little clip on power button that you are actually pushing in on your phone.
see this youtube video. In other words the thing you push is only pushing something else inside. I took my power button out (it clips in) cleaned out the cavity by blowing and with a toothpick and I was fixed!
http://www.youtube.com/watch?v=pQ-U-Q_NdOo
I was pissed at my phone so where the guy in the above youtube video says something like tapping his nail (finger nail) into the power button or whatever I was pretty aggressive and crammed my thumbnail down the sides of the power button until the janky little piece of crap actually popped out revealing itself as a clip kind of a thing. I then blew the hell out of the hole with all of the breath I could muster and took a toothpick and depressed the actual power button several times and "cleaned out" and cleared out any hair or gunk (really did not see any) that might have been in the socket. I put my power button back in (just clips in by itself if you put it in the socket the right way and push down) and I have had NO PROBLEMS since. Start with the first link I posted but be wary of the clearing Cache part unless you no what you are doing ahead of time. I had just done a factory reset and total wipe with TWRP before installing a new ROM so I did not have anything to lose. You might... I don't know enough about what resides in "cache" to advise you. Then if you are still in trouble listen to the second post which is a video. I actually crammed my thumbnail down into the power button cavity on both the top and bottom (the long axis) of the button aggressively enough that the visible button popped out. Then I did my blowing and cleaning, etc... crammed the visible button back int - which clips into place and I have been stoked since. Hope it works for you if not, sorry!
*As a side note, I sort of assumed that the problem with my phone (and I bet yours) has something to do with power: either getting to the right place in the phone from the battery or the power chord OR the f*ing power button on our cheap, janky plastic yet expensive Samsung phones might be a problem because before the weird random reboots and not booting began the power off dialog (like when you hold the power button down long enough and you get the "reboot" "power down" "airplane mode" menu kept coming up while I was surfing watching youtube or even talking. I figured it was time to install another ROM, did so twice and still had the same issues. I reflashed recoveries back and forth from TWRP to the other one several times too. Nothing worked until I cleaned out the power button. Go figure.
I was pissed at my phone so where the guy in the above youtube video says something like tapping his nail (finger nail) into the power button or whatever I was pretty aggressive and crammed my thumbnail down the sides of the power button until the janky little piece of crap actually popped out revealing itself as a clip kind of a thing. I then blew the hell out of the hole with all of the breath I could muster and took a toothpick and depressed the actual power button several times and "cleaned out" and cleared out any hair or gunk (really did not see any) that might have been in the socket. I put my power button back in (just clips in by itself if you put it in the socket the right way and push down) and I have had NO PROBLEMS since
Click to expand...
Click to collapse
I tried a similar approach and it looks like it actually worked. I just took the plastic cover of and removed he 10 little screws and played around with the plastic thingy that depresses the power button. I don't know what exactly fixed it but is seems to work.
So you might not have to remove your power button but instead just play around with it first and see if you can't get it to function properly again.
Thank you so much brjoon1021!
Galaxy SIII I9300 shuts of randomly but only when not used
I have a problem with my S3 since about a week now. First it was a standard S3 with stock ROM and not rooted. The phone would turn itself of 3 - 5 times during daytime and also at night when charging.
What I tried:
- Clearing battery connections
- Cleaning power button
But finally I think it's not a hardware problem. Loose contacts, battery connections or a power button problem would probably cause more shut downs when I was using it. But in my case it's the opposite: it always shuts down when I am *not* using it.
So I rooted the phone and flashed a custom ROM on it: [ROM] [4.4.4] [CyanogenMod] [GCC 4.8] [Excellent] [31/12/14] ArchiDroid V3.0.2
That was succesfull, but after that I still had the same problem.
When do I have this problem: as stated: always when I am *not* using the phone. It's lying on my desk or next to my bed, charging and no program is running.
When I don't have the problem: when some program is running on the foreground, at night during charging if I keep the clock on the foreground (daydreaming), when I have waze running (in my car) etc.
I have the impression the device only shuts itself down when in deep sleep mode.
I also tested if it was a case of Deep Sleep of Death, but when the phone is shut down, I can not text to it, the LED does not light up.
I can boot the phone by pressing the power button once for about 8 seconds, so that seems a normal boot and not a reboot.
Any suggestions on what I could test? Or how I can find out what the problem is?
Thanks!
Dion64 said:
I have a problem with my S3 since about a week now. First it was a standard S3 with stock ROM and not rooted. The phone would turn itself of 3 - 5 times during daytime and also at night when charging.
What I tried:
- Clearing battery connections
- Cleaning power button
But finally I think it's not a hardware problem. Loose contacts, battery connections or a power button problem would probably cause more shut downs when I was using it. But in my case it's the opposite: it always shuts down when I am *not* using it.
So I rooted the phone and flashed a custom ROM on it: [ROM] [4.4.4] [CyanogenMod] [GCC 4.8] [Excellent] [31/12/14] ArchiDroid V3.0.2
That was succesfull, but after that I still had the same problem.
When do I have this problem: as stated: always when I am *not* using the phone. It's lying on my desk or next to my bed, charging and no program is running.
When I don't have the problem: when some program is running on the foreground, at night during charging if I keep the clock on the foreground (daydreaming), when I have waze running (in my car) etc.
I have the impression the device only shuts itself down when in deep sleep mode.
I also tested if it was a case of Deep Sleep of Death, but when the phone is shut down, I can not text to it, the LED does not light up.
I can boot the phone by pressing the power button once for about 8 seconds, so that seems a normal boot and not a reboot.
Any suggestions on what I could test? Or how I can find out what the problem is?
Thanks!
Click to expand...
Click to collapse
Hi
I have the exact same problem!
I tried factory reset, wipe cache, I have bought new battery ... nothing helped so far...
S3
pagep said:
Hi
I have the exact same problem!
I tried factory reset, wipe cache, I have bought new battery ... nothing helped so far...
Click to expand...
Click to collapse
Turn off sync. See if that helps it fixed mine.
zern said:
Turn off sync. See if that helps it fixed mine.
Click to expand...
Click to collapse
Well it started to get worse every day, so we tried factory reset once more and after that, the phone just died. (only colored rubbish is shown on the screen) ...
Never ever buying Samsung again. Piece of crap ...
Anyway we had chance to buy LG G2 on the sale. I know it's quite old, but the price was perfect and it's many times better than S3. :good:
Dion64 said:
I have a problem with my S3 since about a week now. First it was a standard S3 with stock ROM and not rooted. The phone would turn itself of 3 - 5 times during daytime and also at night when charging.
What I tried:
- Clearing battery connections
- Cleaning power button
But finally I think it's not a hardware problem. Loose contacts, battery connections or a power button problem would probably cause more shut downs when I was using it. But in my case it's the opposite: it always shuts down when I am *not* using it.
So I rooted the phone and flashed a custom ROM on it: [ROM] [4.4.4] [CyanogenMod] [GCC 4.8] [Excellent] [31/12/14] ArchiDroid V3.0.2
That was succesfull, but after that I still had the same problem.
When do I have this problem: as stated: always when I am *not* using the phone. It's lying on my desk or next to my bed, charging and no program is running.
When I don't have the problem: when some program is running on the foreground, at night during charging if I keep the clock on the foreground (daydreaming), when I have waze running (in my car) etc.
I have the impression the device only shuts itself down when in deep sleep mode.
I also tested if it was a case of Deep Sleep of Death, but when the phone is shut down, I can not text to it, the LED does not light up.
I can boot the phone by pressing the power button once for about 8 seconds, so that seems a normal boot and not a reboot.
Any suggestions on what I could test? Or how I can find out what the problem is?
Thanks!
Click to expand...
Click to collapse
my is also the same problem..if u have found solution for it please tell me .
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!
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.