Related
So I seem to have a problem with my Epic Touch. (Caution: Semi-lengthy explanation ahead).
First of all, I am running the stock ROM with the ZedomaxEpicTouchKernel v6.02.
Last night I happened to let my phone die all the way, and i plugged it into the wall charger this morning. Everything seemed to go normal at first, the red indicator light and battery charging icon came on. However, after letting it charge awhile (10 - 15 minutes) I came back to see how much it had charged, only to find that when i pressed the power button nothing happened (it didn't wake the screen as it normally would).
So, I tried to long press the power button to see if the device would turn on, and it didn't. I disconnected the phone from the charger, did a battery pull, and reconnected the phone to the charger, and the device did the same thing it did, when I initially connected it to the charger.
I tried using my old charger for my Samsung Captivate, and the Epic Touch is still doing the same thing. At this point, I'm not sure what else to do. I am able to access CW Recovery mode, but not Download Mode (Error message saying battery too low to enter Download mode). Right now, I have the phone in Recovery Mode, to see if the battery will charge that way. Would wiping the battery stats help?
Somebody PLEEEEAAAASE tell me that there's a fix for this, and hopefully it doesn't involve going to the sprint store.
if you can get to cwm then try flashing another kernel from a zip and see if that helps.
just be sure to leave it plugged in while flashing so it doesn't die
I had that happen with zedomax 6.2 as well. Kind of. It wouldn't take a charge at all this morning. I have the no moar power app and it stays at 0%. It was at around 40% last night when I plugged it in. had to flash lost .8 to get the power going. It must be something with the undervolt? I've used other zedomax kernels with no problem.
Sent from my SPH-D710 using XDA App
Atticuspoint6 said:
I had that happen with zedomax 6.2 as well. Kind of. It wouldn't take a charge at all this morning. I have the no moar power app and it stays at 0%. It was at around 40% last night when I plugged it in. had to flash lost .8 to get the power going. It must be something with the undervolt? I've used other zedomax kernels with no problem.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Thanks for the help guys. I'll try a different kernel and see if that helps. I found by entering CWM Recovery and letting it charge for awhile, then selecting 'reboot' did the trick in getting it to boot. Im coming from using the Samsung captivate, so things work similar but the ET4G is still kinda new to me.
What kernel/ROM would you guys suggest? I am a big fan of CM7 and I really hope we get a build soon.
So, when i try to turn on my phone all it does is vibrate once and not turn on (the screen wont come on and the indicator lights dont come on either - when plugged in and charging) ...
I had it plugged in last night and i tried to turn it on this morning and it doesnt work...
i think there was like a surge of power that broke it or something -- anyways Sprint ordered me a new evo and i was just curious -- i have a nandroid backup of this previous phone, so if i get the new phone and put RA recovery on it, can i just import the backup and it will go back to normal? or can i not do that because it is a new phone (a.k.a - i will have to start from scratch?)
Any help would be appreciated -- especially if i can get this previous phone fixed -- i would sell the old one lol
But Thanks,
Collin
The nandroid should work just fine.
Sent from my ADR6425LVW using Tapatalk 2
The nandroid should work as long as you have the same recovery version. As for the phone it could be the battery that got fried you should stick in the new battery from your new phone to see if it works
Asonicperson said:
The nandroid should work as long as you have the same recovery version. As for the phone it could be the battery that got fried you should stick in the new battery from your new phone to see if it works
Click to expand...
Click to collapse
alright cool --- no it wasnt the battery, i took it to the sprint store and they told me the motherboard was fried... I have been experiencing power outages that last like 5 seconds because of the heat, I believe, and i think one of those surges fried my phone
anyways thanks for the help --- im glad my nandroid will be fine lol.. yea ill just reflash RA recovery then.
Thanks again, Collin
sorry for double posting but my nandroid didnt work lol ---
it said oops something went wrong .. please check recovery file
so i guess from scratch lol -- DAMNIT hahaha
Thanks anyways
I would recommend getting a surge protected power strip because it is likely another power outage can occur and ruin the next phone. Good luck
hey, im having the same problem.
The detailed problem i had is as follows:
-Phone randomly turned off at work and was completely unresponsive.
-After pulling the battery and removing the sd card it finally booted.
-Random freezing on startup, during phone usage, and random shut downs while using phone.
- - Also couldn't unlock phone sometimes although the led for a text would still be blinking,
-Tried recovery, which kept freezing but finally lasted long enough to wipe and flash a different rom.
-Worked for about 15 minutes then shut down only to never boot again.
TO THE PUNCH:
Phone won't turn on, vibrates once while holding powering button and thats it. Everytime i hold the power button it vibrates once, even holding it down consecutively. Tried with 3 different charged batteries. Plugging it into a charger lights up orange.
Idk what's wrong with it. Recovery doesn't work either. Could it be the LCD screen? Possibly a loose connector?
I bumped this thread bc it seemed similar enough even tho i had no power surge.
plus: i would bring it to a sprint repair store but the share plan i have has security restrictions due to a fraud attempt and i'm not the account holder.
Hello! let's just cut to the chase. I need help..
Couple of days ago I got tired of waiting for the new ota for my phone so I decided to root.. unlocking bootloader went well, installed newest cwm, made a backup of my rom and chose renovate 3.0 as my first rom to try... everything works normal and I update the faux kernel on the rom to version 5b01.. all works normally at this point.. I play games, listen to music, surf the web.. yesterday I then updated the kernel to 5b03.. I went playing dark knigt rises (btw a very good game) and the phone heats up pretty much (which I think is normal as the game is quite heavy and I use wilkyys game booster app). I play about 15minutes and I get the message that the battery is running low, I plug the charger in and continue.. five minutes go and the phone freezes and the screen goes black.. the phone is connected to the charger and the charging light blinks red.. the phone won't start, even when pressing the power key for 10seconds. I can get to the bootloader and recovery _when_ the phone is connected to the charger thou.. if I unplug the charger the phone won't do anything. I search the problem on xda and find some threads about similar problems.. eventually after changing from the wallcharger to the usb charger on my pc (did this many times..) the red light goes solid and I press power and the phone boots normally.. weehee I made it!! or so I thought..
Next day: I woke up and the phone was in charger all night. Battery reads 100%. I load "system tuner" and experiment with undervolting my phone (only -50mv) and run some benchmarks and everything seems working.. I start to download an app from the play store.. the phone freezes and again the same flashing red light is to be seen, I thought it could be because of the undervolt but I'm not sure anymore.. and now I haven't got the phone in working condition.. I have now got the phone in recovery for about three hours and there should be enough juice for it to start but it wont..
I also restored my backup but that didin't help.. with the getvar battery-voltage command it reads about 2500mv which should be enough to atleast power it on?
Hi
elmonen said:
Hello! let's just cut to the chase. I need help..
Couple of days ago I got tired of waiting for the new ota for my phone so I decided to root.. unlocking bootloader went well, installed newest cwm, made a backup of my rom and chose renovate 3.0 as my first rom to try... everything works normal and I update the faux kernel on the rom to version 5b01.. all works normally at this point.. I play games, listen to music, surf the web.. yesterday I then updated the kernel to 5b03.. I went playing dark knigt rises (btw a very good game) and the phone heats up pretty much (which I think is normal as the game is quite heavy and I use wilkyys game booster app). I play about 15minutes and I get the message that the battery is running low, I plug the charger in and continue.. five minutes go and the phone freezes and the screen goes black.. the phone is connected to the charger and the charging light blinks red.. the phone won't start, even when pressing the power key for 10seconds. I can get to the bootloader and recovery _when_ the phone is connected to the charger thou.. if I unplug the charger the phone won't do anything. I search the problem on xda and find some threads about similar problems.. eventually after changing from the wallcharger to the usb charger on my pc (did this many times..) the red light goes solid and I press power and the phone boots normally.. weehee I made it!! or so I thought..
Next day: I woke up and the phone was in charger all night. Battery reads 100%. I load "system tuner" and experiment with undervolting my phone (only -50mv) and run some benchmarks and everything seems working.. I start to download an app from the play store.. the phone freezes and again the same flashing red light is to be seen, I thought it could be because of the undervolt but I'm not sure anymore.. and now I haven't got the phone in working condition.. I have now got the phone in recovery for about three hours and there should be enough juice for it to start but it wont..
I also restored my backup but that didin't help.. with the getvar battery-voltage command it reads about 2500mv which should be enough to atleast power it on?
Click to expand...
Click to collapse
2500mv is far too low for lithium ion batteries. There are protection mechanisms in most lithium ion batteries that will trigger at 2.7volts or lower putting the battery and its protection circuitry into deep sleep.
From the battery university: http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries/
Li-ion should never be discharged too low, and there are several safeguards to prevent this from happening. The equipment cuts off when the battery discharges to about 3.0V/cell, stopping the current flow. If the discharge continues to about 2.70V/cell or lower, the battery’s protection circuit puts the battery into a sleep mode. This renders the pack unserviceable and a recharge with most chargers is not possible. To prevent a battery from falling asleep, apply a partial charge before a long storage period.
If this is the case you may not be able to recover easily. We can only assume something went wrong with the phones firmware that caused it to deeply discharge and now protection measures have kicked in.
Regards
Phil
hmm.. thanks for the answer.. last night I got the charging light to stay solid when I plugged the phone in and I was so happy.. but I was so stupid and tried immediatly to turn it on.. it even started and got to the quietly brilliant screen, but died pretty soon and the red light started blinking again.. then I realised I should have kept it charging for a while before trying to turn it on... god damn it..
Hi
elmonen said:
hmm.. thanks for the answer.. last night I got the charging light to stay solid when I plugged the phone in and I was so happy.. but I was so stupid and tried immediatly to turn it on.. it even started and got to the quietly brilliant screen, but died pretty soon and the red light started blinking again.. then I realised I should have kept it charging for a while before trying to turn it on... god damn it..
Click to expand...
Click to collapse
When lithium batteries are deep discharge (below 2.7volt) changes take place which can cause short circuits in the battery, recharging then becomes dangerous, hence the battery goes into a form of safety mode, it's like a fuse blowing. It may never take a charge again, or if it does, the battery life will be less than before.
Hope it recovers okay however if it really did hit 2.5volt it could be permanently damaged now.
Regards
Phil
mine was doing that for a while. Keep it plugged in, if the wall charger doesnt work hook it up to a computer. it will turn on again...
simple keep the phone on charge for few hours and dont touch it.
Ok back to the problem.. the phone was in charger yesterday for about 12hours.. and still won't show any signs of recovery.. blinking red light continues... I might just have to accept that I have to send it in to repair... sigh.. and I think I have to pay for it..
As I said in my first post I have restored a nandroid backup of which I made as soon as I installed cwm.. so I should be at stock firmware? allthou I can't confirm it as I can't get the phone to boot but cwm said restore was succesful.. next step is to install original recovery and relock the phone, am I correct? so next question is.. is there anyway to do this as everytime I try to flash something with flasboot I end up with "failed: low battery"...?
elmonen said:
Ok back to the problem.. the phone was in charger yesterday for about 12hours.. and still won't show any signs of recovery.. blinking red light continues... I might just have to accept that I have to send it in to repair... sigh.. and I think I have to pay for it..
As I said in my first post I have restored a nandroid backup of which I made as soon as I installed cwm.. so I should be at stock firmware? allthou I can't confirm it as I can't get the phone to boot but cwm said restore was succesful.. next step is to install original recovery and relock the phone, am I correct? so next question is.. is there anyway to do this as everytime I try to flash something with flasboot I end up with "failed: low battery"...?
Click to expand...
Click to collapse
I've experienced this kind of problem when I drain the battery flat; naturally, I crapped myself like everyone else since there's no easy way to remove the battery like you would for any other phone.
All I did (and still do) when this happens is hold the power button until the main buttons flash white a few times, let go and it should reboot the phone..
two minutes pressing power button, nothing happens
elmonen said:
two minutes pressing power button, nothing happens
Click to expand...
Click to collapse
did the buttons even flash??
Try holding vol down + power until you get a response, then try holding the power button again ..
for me the key was to get the buttons to flash white, thats when i knew things were gonna be ok! :highfive:
kennylovesyou said:
did the buttons even flash??
Try holding vol down + power until you get a response, then try holding the power button again ..
for me the key was to get the buttons to flash white, thats when i knew things were gonna be ok! :highfive:
Click to expand...
Click to collapse
no response! only response is that when it's in charger I can get to to blootlader and recovery with the vol- power combination..
If it won't charge read this thread. http://forum.xda-developers.com/showthread.php?t=1658084
Helped me out with similar problem.
Hope this helps.
Sent from my HTC One X using XDA Premium HD app
Amicushia said:
If it won't charge read this thread. http://forum.xda-developers.com/showthread.php?t=1658084
Helped me out with similar problem.
Hope this helps.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Tried that :/ won't work.. as my phone doesnt restart with the script.. only way to get a response from it is to press power and vol down when in charger...
Thanks for the suggestion thou.
all right.. quick update.. I have sent the phone in for repair.. so just waiting for the repair bill
Ok... update (don't know if anyones interested..) Today I got at txt message from my carrier that the phone is now ready.. and what do you know.. it was covered by warranty. They changed the motherboard and the screen module (I had one dead pixel) needless to say Im pretty happy now.
elmonen said:
Ok... update (don't know if anyones interested..) Today I got at txt message from my carrier that the phone is now ready.. and what do you know.. it was covered by warranty. They changed the motherboard and the screen module (I had one dead pixel) needless to say Im pretty happy now.
Click to expand...
Click to collapse
Don't you just love it when that happens.
I had a rooted phone and my warranty was probably void. A week ago I dropped the phone screen first onto a concrete floor and I expected the worst. Picked it up and turned it on and to my surprise, the screen hadn't cracked. Used it for 5 minutes and it worked as it normally would. When I got back home and wanted to make a call, the screen wouldn't turn on. The lights for the buttons would light up but the screen would remain blank. Calls and texts would come through so the phone worked, just without the screen. After about 10 minutes of tinkering, the screen turned on and I heaved a sigh of relief thinking all was normal again. But when I locked it and tried unlocking it, the screen refused to turn on again. At this point I assumed there would be a loose connection between the MB and screen.
I took the phone to a few repair shops around here to find out how much they would charge and I got quotes around $200. So I decided to try taking it to the vodafone store to see how much it would cost to get HTC to repair the phone. The guy over the counter inspects the phone and finds no physical damage to the screen and says that they'd be glad to replace the phone right then and there at the price of me losing all my data as that would be unrecoverable. I told him I'd be glad to have a replacement on the spot. So in the end, I guess I got a good deal.
Lucky you !
Sent from my HTC One X using XDA Premium HD app
I had the same problem last night:
phone charging with the HTC wallcharger, alarm set.
the device did not ring: it died during the night.
At first, impossible to boot (rom or hboot) or to charge it. I plugged it on my PC and the red light started to flash. One hour later, it was still flashing, so I tried to turn it ON
It turned ON but repported 2% battery only. (ok, that's why it was refusing to boot)
4 hours later, ON and plugged to the HTC wallcharger (that I verified of course), it was still 2%
After three reboots, plug/unplug several times, suddenly battery displayed 44% instead of 2%
Battery monitor repports that indeed, the device charged for the 1st part of the night, then suddenly and very quickly discharged to 0 while plugged, with no particular app to drain the battery.
During the 4 hours it was plugged and ON, it remained 2%, then a sudden 44% after a reboot.....
What the hell is that???? I've now cleaned cache and battery stats in recovery and I'm letting it charging to see if it goes above these 44%
Weird, I really thought my battery had just died....
EDIT: 2 minutes later, it now repports 46%, so seems to charge correctly. But I need to know what happened, I usually relay on my phone alarm to wake up, and if it happens again, it could be a real problem. Maybe I should flash an other recovery, even if I never had a single problem with it?
kennylovesyou said:
did the buttons even flash??
Try holding vol down + power until you get a response, then try holding the power button again ..
for me the key was to get the buttons to flash white, thats when i knew things were gonna be ok! :highfive:
Click to expand...
Click to collapse
I have drained battery, been charging all night with a flashing red LED. No response. Now when I plug it in it still flashes red. When I hold the power button (also power+volume down) the main buttons start flashing white, but no response from the phone whatsoever.
When I let go the power button during the flashing, the lights either go out or stay on..
Any ideas? Thank you!
We had a power surge in this house while my HOX was charging... I'm guessing that's what caused the problem.
Unfortunately I bought it outright, 2nd hand, about 7 months ago. So can't get it replaced or repaired for free. It's been trouble-free until about a week ago.
Phone is rooted, has been upgraded/running Jellybean ROMs successfully; originally an Optus branded HTC One X (Australia).
The Problem:- so by default, if I charge it (with solid red LED on) while it's off, at random intervals with no user intervention, it'll boot to the boot screen, and then turn itself off to a black screen a few moments later. This will continue at random intervals of say... 30 minutes or so. Strange huh. Oh yeah, and when I try to boot the phone manually, it does the same thing. Annoying.
I can still get into HBOOT/Fastboot using power+voldown... and from there recovery. So I thought - okay... I can fix this. But upon booting, no matter how long I charge it while it's off, it complains that the battery is too low to flash. So I've been charging it in recovery for hours before flashing successfully.
So I've flashed a couple of different JB ROMs (such as Ordroid/Black Pearl) with their associated boot.img files properly (the way I always had before, i.e. before flashing the ROMs, and w/ fastboot erase cache etc), and each time it'll boot up into the newly flashed ROM fine, then I'll charge it up to full (green LED). But upon rebooting the phone, it goes back to it's initial behavior of going to the boot screen, then a few moments later going to the black screen and staying there (with red LED on). And then when I boot it with power+voldown... it complains the battery is too low to flash, even though fully booted and working it was saying it was 100% charged just a few moments before (having previously left it for hours to charge up to full). I've tried 2 genuine HOX chargers and cables, with no change in behaviour, and have searched threads about this kind of thing in this forum, to no avail.
I suspect the power surge has killed the battery somewhat , though I really don't know for sure.
Or is this a PEBCAK problem... could easily be... I'm sure I could've stuffed up somehow without realising.
Fixing this phone isn't critical, as I'd already moved on to a Nexus 4, however I had been intending to give this phone to my brother before it started misbehaving... so if anyone knows how I should proceed, I'd most appreciate any guidance.
Thanks.
It's a bit difficult to say whether it's the battery or the actual mainboard which got damaged.
There's only one way to find out, purchase a new battery and see. You can sell the battery if it doesn't work.
Sent from my One X using xda premium
Hi guys, TMO Galaxy S III. I was running Cyanogenmod 10.2.
I was driving home from a road trip to the race track, used GPS on my phone as it was plugged in charging. Turned it off as soon as I got to a familiar place. Put the phone in my pocket after I got home. Pulled it out 30 minutes later and it's turned off.
Efforts to turn it on failed. I plugged it in (even though it had batter left before it died) and nothing happens. No LED, no battery charge graphic, no vibration.
I switched batteries. I switched plugs. Tired to reboot into recovery. Nothing. I can't get Kies to recognize it.
I didn't drop it. No water damage. Any ideas?
If after putting battery back in, and unplugged, you get zero response from pressing power, then yes it sounds like it's dead
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If after putting battery back in, and unplugged, you get zero response from pressing power, then yes it sounds like it's dead
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yup. Zero response. The only way I can get it to do anything, is to pull the battery, then plug in the phone w/ no battery. That gives me a red LED. Nothing else. That's the only sign of any life. No vibration or anything. Just the red LED.
Try a different battery, ?
Sent from my SGH-T999 using xda app-developers app
illegal machine said:
Yup. Zero response. The only way I can get it to do anything, is to pull the battery, then plug in the phone w/ no battery. That gives me a red LED. Nothing else. That's the only sign of any life. No vibration or anything. Just the red LED.
Click to expand...
Click to collapse
That battery may have died from heat. Navigation while plugged in tends to heat up the phone.
It's unlikely enough that I would not recommend buying a new one just to test though. Maybe go to a T-Mobile store and swap with someone just to test.
Sent from my SGH-T999 using Tapatalk
I mentioned in my first post I switched batteries. First tried my wife's battery and it didn't do anything. She tried my battery and her phone booted with 89% life.
Took it to a store and tired a new battery and it didn't work.
My wife just emailed me. Her phone was acting strange, turned itself off once. She booted it back up and it turned itself off again and won't turn back on. SHE AT LEAST gets the "Galaxy SIII" screen. She couldn't get it into recovery mode, but she could get it into download mode. I'll try and flash it tonight.
Samsung is garbage.
Sorry bout the battery thing. A few of us answer so many of these things it sometimes gets mixed up a bit and we will just add to someone else's information, not always rereading each thread...
There is a debrick thread stickied in development you may want to try. Can't guarantee anything of course, but you never know, it could end up fixing one or both of the devices.
On your wife's, take out the battery and then put back in. Wait a few to see if it attempts to turn itself on w/o pressing power.
If it does, then it's probably got a broken power button. This has become a common occurrence recently, but from what I hear is a relatively easy fix.
It may not be this though if she can get download mode to stay booted every time. But it's an easy test.
Also, when plugging into the computer, if it says something like QHSUSB in device manager, it's probably hard bricked. The debrick thread can probably help in this case.
Sorry you're having such issues with both devices. It's not the norm though. If it is a hardware failure, and you got both at the same time, it could be that one of the components may not have been completely up to par for the batch yours came from. That's just speculation though...
Sent from my SGH-T999N using Tapatalk
DocHoliday77 said:
Sorry bout the battery thing. A few of us answer so many of these things it sometimes gets mixed up a bit and we will just add to someone else's information, not always rereading each thread...
There is a debrick thread stickied in development you may want to try. Can't guarantee anything of course, but you never know, it could end up fixing one or both of the devices.
On your wife's, take out the battery and then put back in. Wait a few to see if it attempts to turn itself on w/o pressing power.
If it does, then it's probably got a broken power button. This has become a common occurrence recently, but from what I hear is a relatively easy fix.
It may not be this though if she can get download mode to stay booted every time. But it's an easy test.
Also, when plugging into the computer, if it says something like QHSUSB in device manager, it's probably hard bricked. The debrick thread can probably help in this case.
Sorry you're having such issues with both devices. It's not the norm though. If it is a hardware failure, and you got both at the same time, it could be that one of the components may not have been completely up to par for the batch yours came from. That's just speculation though...
Sent from my SGH-T999N using Tapatalk
Click to expand...
Click to collapse
For sure, I know how many times the question comes up. No worries on the battery thing.
Ok, so I was able to get my wife's phone into recovery and wiped dalvik/factory restore. It turned itself off twice over the next 30 min. But at least it boots every time.
Would you guys suggest I use Kies to factory restore? Or if it keeps restarting after factory restore via recovery, is it not going to do any good?
My wife said it's turned itself off 7 times today (over 5 hours). Ohhhh Sammy....
illegal machine said:
For sure, I know how many times the question comes up. No worries on the battery thing.
Ok, so I was able to get my wife's phone into recovery and wiped dalvik/factory restore. It turned itself off twice over the next 30 min. But at least it boots every time.
Would you guys suggest I use Kies to factory restore? Or if it keeps restarting after factory restore via recovery, is it not going to do any good?
My wife said it's turned itself off 7 times today (over 5 hours). Ohhhh Sammy....
Click to expand...
Click to collapse
I'd try the Kies to Factory Restore. You've got not much to loose that way. Keep an eye on it afterwards to see if the reboots go away.
But before you do that, can you let me know if wife's phone has its own battery or your phone's battery ? If its was your Battery that was in there when she experienced the reboots then put her own battery and check.
Perseus71 said:
I'd try the Kies to Factory Restore. You've got not much to loose that way. Keep an eye on it afterwards to see if the reboots go away.
But before you do that, can you let me know if wife's phone has its own battery or your phone's battery ? If its was your Battery that was in there when she experienced the reboots then put her own battery and check.
Click to expand...
Click to collapse
Soooo on Sunday her phone completely shut off again. It would only boot to the swirling galaxy S circle, the turn itself off (in mid animation). I can boot it into recovery and download mode, but it only stays booted for 3 seconds or so, before turning off. Not long enough for Kies/Odin/factory restore via recovery.
SO we fixed the problem permanently. I got an HTC One and she got a Nexus 5.
Samsung can die in a fire. Never again are they getting my money.
illegal machine said:
Soooo on Sunday her phone completely shut off again. It would only boot to the swirling galaxy S circle, the turn itself off (in mid animation). I can boot it into recovery and download mode, but it only stays booted for 3 seconds or so, before turning off. Not long enough for Kies/Odin/factory restore via recovery.
SO we fixed the problem permanently. I got an HTC One and she got a Nexus 5.
Samsung can die in a fire. Never again are they getting my money.
Click to expand...
Click to collapse
You may consider donating the devices to some developer on here. The community will benefit from better code.
illegal machine said:
For sure, I know how many times the question comes up. No worries on the battery thing.
Ok, so I was able to get my wife's phone into recovery and wiped dalvik/factory restore. It turned itself off twice over the next 30 min. But at least it boots every time.
Would you guys suggest I use Kies to factory restore? Or if it keeps restarting after factory restore via recovery, is it not going to do any good?
My wife said it's turned itself off 7 times today (over 5 hours). Ohhhh Sammy....
Click to expand...
Click to collapse
Well, I'm glad you solved the issue to your satisfaction. Sorry we weren't able to help in getting it fixed w/o needing to spend your money.
Good luck to the future and your new toys!