Develop Bugs

Well and truly bricked - desperate

Hi all,
I desperate need help. After an unsuccessful radio flash, my Desire won't even turn on. No response from any buttons or lights. Here's how it happened:
I'm relatively new to Android. I recently bought a Desire, to replace my Touch HD, which has seen about 25 different WM ROMs, over it's life.
I successfully rooted my Desire and had tried a few ROMs. I was sitting on the MoDaCo Custom ROM r17, which was all customised and running perfectly. I'd even used ADB to successfully update my wifi config to connect to my company LEAP-authenticated network.
I decided to flash the latest radio (32.37.00.32U_4.06.00.16_2), from this thread:
http://forum.xda-developers.com/showthread.php?t=687464
I entered Recovery using 'Fake-Flash';
I started flashing the radio image;
All the good messages were scrolling down the screen;
I kept one eye on the phone while I worked on my laptop;
I saw a message saying something to the effect of "Finished installing radio..." (sorry, I don't remember the exact wording);
The blue recovery menu had returned, with 'reboot device' as the default selection;
As I clicked the trackball, I saw another message appear under the 'finished' messages, which said "Writing rad " I guess it didn't have time to print the whole message, when I selected reboot.
The screen went blank then a graphic appeared in the middle (where the recovery exclamation mark and triangle usually appear), of a software box with a curved yellow arrow over it and the android icon peeking out from behind it. I left it for a while (already had that sinking feeling) then pressed the power button. It switched off and stayed there.
Since then, nothing that I've tried has received any response. Various combination's of button pushes, USB connection, removed SIM, SD and battery...nothing, not even an LED.
I've searched and haven't been able to find any solutions to this particular situation. Can anyone help, or am I totally bricked?
Regards, PF.

The radio update does 2 reboots to install it. The software box with yellow arrow is the default graphic used by the fake flash recovery as far as I know so that wasn't any real problem.
I know this might sound silly, but is the battery charged?

socktug said:
The radio update does 2 reboots to install it. The software box with yellow arrow is the default graphic used by the fake flash recovery as far as I know so that wasn't any real problem.
I know this might sound silly, but is the battery charged?
Click to expand...
Click to collapse
No question is silly under this circumstance!
Yes. I'd just taken it off overnight charge. 100%. If I plug the USB cable in now, there is no response from the LED.

Leave the charger plugged into it for about 5 minutes and see if there is any response to it. With the usb bricks it would take nearly 5 mins to register and the led to light up.
I know this isn't a usb brick, but I've not seen anyone with a failed radio flash that has caused the phone to totally die to the extent that it won't even switch on.
I take it you have tried the usual power and volume button combos etc?
I suppose if there is no quick fix for this, the fact that it's totally dead may go in your favour if you try to get it repaired/replaced under warranty

socktug said:
Leave the charger plugged into it for about 5 minutes and see if there is any response to it. With the usb bricks it would take nearly 5 mins to register and the led to light up.
I know this isn't a usb brick, but I've not seen anyone with a failed radio flash that has caused the phone to totally die to the extent that it won't even switch on.
I take it you have tried the usual power and volume button combos etc?
I suppose if there is no quick fix for this, the fact that it's totally dead may go in your favour if you try to get it repaired/replaced under warranty
Click to expand...
Click to collapse
ok. The charger has been plugged in for 35 minutes and still no response.

Also don't want to sound patronizing, but have you taken the battery out and turned on with the back button helld?
Ignore me, just reread your original post.

the procedure u said sounds rite, thats whats ment to happen, when you flash a radio, only other thing that comes to mind is, sure the radio u flashed was for the gsm desire?

so what youre saying is that your phone simply doesnt turn on, not for a second?
if you press the power button NOTHING happens?
are you sure your charger isnt broken?
have you tried charging it through your pc?
have you seen if its recognised through adb devices on your computer?
have you tried a new battery?
if your phone is simply dead, it must be a hardware problem, in which case you can probably send it off for repair and not have your warranty void as the whole phone will need to be replaced. they cant identify if you have voided your warranty if your device doesnt turn on.

cgrec92 said:
so what youre saying is that your phone simply doesnt turn on, not for a second?
if you press the power button NOTHING happens?
are you sure your charger isnt broken?
have you tried charging it through your pc?
have you seen if its recognised through adb devices on your computer?
have you tried a new battery?
if your phone is simply dead, it must be a hardware problem, in which case you can probably send it off for repair and not have your warranty void as the whole phone will need to be replaced. they cant identify if you have voided your warranty if your device doesnt turn on.
Click to expand...
Click to collapse
Right first time. It won't turn on at all. It doesn't react in any way to any of the button combinations I'm aware of from rooting and flashing it. Nothing happens at all.
I live in an HTC household, so I've tried a number of chargers and cables, including the PC's USB port. I haven't tried another battery...but the incumbent battery was holdng a good charge and was 100% at the time. What's more, I remember that the phone can run on the charger without the battery.
Not surprisingly, adb devices shows no connected devices.
I think everyone is right, it's back to HTC. I *hope* you're right that they cover it under warranty. I'm going on the weekend, so I'll let you all know the result.
Thanks to all for your help.

I think you can try to remove battery, leave the phone with no battery for 30 minutes and then try to insert battery and connect to usb without power it on to check if LED (and than the phone) is revived.
I had an Acer Liquid that gave me same problem, pratically when a flash on the radio go wrong, the device go in "protection mode". You must also check on the net if there is a protection mode on Desire too, and if there is a button combination to unlock it. I repeat: i just giving an idea becouse the same problem happened for me on an Acer Liquid, so i'm not sure if it's the same for the Desire.
Good Luck

Maybe a usb brick? No usb is no charging. So when you didn't had a full battery, it may be went wrong on that.
Try another battery, if you can get to one.

peewster said:
Maybe a usb brick? No usb is no charging. So when you didn't had a full battery, it may be went wrong on that.
Try another battery, if you can get to one.
Click to expand...
Click to collapse
In the usb brick situation you can still charge. This isn't it!

socktug said:
In the usb brick situation you can still charge. This isn't it!
Click to expand...
Click to collapse
Ok i didn't know that.

If the phone doesn't turn on at all, you can maybe try sending it back to the shop for replacement. Chances are, they won't be able to know what happened, so you can pretend it just stopped working.
If it gets back to HTC, they probably won't bother to figure out what's wrong with the phone and just give you a replacement. Otherwise, they'll just send you the phone back and you won't have lost much (maybe postage costs?).

ash1684 said:
I think you can try to remove battery, leave the phone with no battery for 30 minutes and then try to insert battery and connect to usb without power it on to check if LED (and than the phone) is revived.
I had an Acer Liquid that gave me same problem, pratically when a flash on the radio go wrong, the device go in "protection mode". You must also check on the net if there is a protection mode on Desire too, and if there is a button combination to unlock it. I repeat: i just giving an idea becouse the same problem happened for me on an Acer Liquid, so i'm not sure if it's the same for the Desire.
Good Luck
Click to expand...
Click to collapse
Thanks for the suggestion. I left the battery out overnight. Then tried to activate it (all the usual button combos) with:
Battery out, USB cable plugged in;
Battery in, USB unplugged;
Battery in, USB in.
I scoured the 'net for anything on protection mode for the Desire...no luck. If there is one, it hasn't been posted yet.

I would just act stupid and try to return it under warranty!

I think it should be ok to RMA this, if its completely bricked there is no way of them knowing that you tried a different radio.

Umbrella Corp. said:
I think it should be ok to RMA this, if its completely bricked there is no way of them knowing that you tried a different radio.
Click to expand...
Click to collapse
Yes, if it's totally bricked then just send it back to HTC and they will change it with no problems just same as acer done with my Liquid

All's well that ends well
Good news...
The HTC service centre were kind enough to replace my 'faulty' handset.
Re-flashed with r19 and radio updated (patiently) successfully.
Thanks all for your support.

Nice one. Glad it worked out for you

[Q] Flashed Caulkin's_format_all.zip, will not turn on

I had flashed Caulkin's_format_all.zip and I managed to accidentally reboot my phone before flashing a rom or anything. The phone will not power on, and if I plug it in, the charge indicator will not turn on. I've already tried pulling the batt for 5 minutes with no luck. any suggestions?

I did this once by being too quick at pushing the power button , I was able to reboot into recovery by pushing volume down and power button and then install a backup or you could flash rom. Hope this helps.

problem is, I can't even get it to boot, be it normal boot or bootloader.

If you hook it up to the computer, is it recognized?

Your going to have to borrow someones battery. I've seen people with this problem and for some reason, your phone won't recognize your battery and since it won't it won't charge it. Trust me, stick in a different battery and you will boot right up.

I've tried using my sprint extended life batt and the stock htc batt. neither worked.

and pc won't even recognize it.

spalding1028 said:
I've tried using my sprint extended life batt and the stock htc batt. neither worked.
Click to expand...
Click to collapse
So 100% sure that both batteries you've tried have a charge on them? And still no led when plugged in, to computer or wall? That sucks, because it sounds like it got bricked, somehow. I have also accidentally booted after flashing calk's format all from hitting the power button too quick, and as the other guy said, I was able to get to the bootloader by voldown+power, and restore a nandroid. I don't know what went differently in your case, but if you're positive that the batteries you've tried are good and charged, and you get no power led plugged into the wall, then it does sound like you somehow got a brick? Did you try leaving it plugged in for some time? A couple hours maybe, just to see if the led comes on?

Also make sure you are using a wall charger, I know if my battery charge is too low or dead the usb on my computer won't work, I then have to use the wall charger. The led will flash at first before starting to charge. When led is flashing phone won't turn on.
Edit:I just saw wall charging mentioned in previous post. I guess it shows the importance of it

I haven't tried leaving it plugged in. doing that now.

so I took it into the sprint store today and even the techs couldnt figure it out. I've got a replacement on the way. thanks for your suggestions guys!

spalding1028 said:
so I took it into the sprint store today and even the techs couldnt figure it out. I've got a replacement on the way. thanks for your suggestions guys!
Click to expand...
Click to collapse
Well i guess that may be a way of doing it. Completely break the phone if something goes wrong during root

hmmm.... weird.... your phone decided it had enough flashing apparently
First ive seen of a phone completely bricked that wasn't during a radio update.

I'm F****d!!! please help!

so my droid inc died on me at work the other day, im running cm7 build 36 or 37 i think and i cant get it to turn back on. no charging light when i plug it in either. like i get nothing from it! have pulled the battery numerous times.. tried with a known good battery with life in it and still nothing. i really need your guys' help!

Have you tried to get into recovery yet?
Sent from my ADR6300 using XDA Premium App

Have you tried a different charger yet? Different outlet? If that doesn't work your charging port may have come loose.

yea ive tried but it wont let me do anything....

Same Boat
I am in the same boat. I was rooted but wanted to go back to stock. So I put the stock image on my sd card, installed it, and on the reboot its not doing anything.

Reminds me of when I attempted to flash a radio and got an "!" inside of a triangle. I pulled the battery and my poor Droid Eris was Bricked beyond (my) repair.

ok, so when you push the power button nothing happens... have you done a full battery pull? Happened to me during the nightlys once or twice i pulled batt and it rebooted

stevefxp said:
I am in the same boat. I was rooted but wanted to go back to stock. So I put the stock image on my sd card, installed it, and on the reboot its not doing anything.
Click to expand...
Click to collapse
Steve, do you have a slcd? I'm betting you went back to the original stock which doesn't have a slcd driver. Search http://www.incredibleforum.com/ for an easy fix. There's an easy fix on there somewhere. I tried a 100 different things and nothing worked but finally got it. You should be able to boot into recovery if this is the case but I never could... I did get it fixed but don't remember exactly how.

bradatz is right. you could try to do a stock 2.2 ruu or a 2.2 PB31IMG.zip. the display driver for amoled is not compatible for slcd models.
see if this helps:
http://androidforums.com/1476696-post1.html

Bingo
Thanks guys for the heads up on the display situation. I do have SLCD, and my bet this is the issue. I will work on this tonight and report back.
See this is exactly why we have these communities. The power of many is greater than the power of one!
Steve
PS - Looks like this posting does the trick: http://dougpiston.com/?p=133

My first thought would be if the phone is off/dead, and it wont charge when you plug it in, it isn't software so much as either charger or socket issue. Since you said you tried various chargers and it didn't work... have you tried finding a different battery, with a charge, and see if it'll turn on? If that's the case, your MicroUSB port or internal circuitry is shot. Or the leads are soiled (make sure there's nothing in there... I had problems and found a lint ball from my pocket wedged itself in there. Make sure if you're digging in there you take the battery out just in case.
I guess if you need to replace it do so soon, Asurion is raising their deductible to $90 from $80.
Tapatalk Pro Sig. Yep, boring.

I made that mistake It's scary. Especially if you do it the 1st day you get your new phone
I rooted my droid and then thought I didn't do it right where some programs said it couldn't get root access, so I went to flash back stock. Dead screen
Following doupistons site helped me get back up and running.

If your phone vibrates when you turn it on after doing a battery pull, then it's probably an SLCD issue. If not, it's likely a battery issue.
You say you were running CM7 with no problems on the phone, the battery drained, the phone turned off, and now it wont charge or turn on?
You can take it to Verizon and have them check the battery for you as well.

ozzman54 said:
If your phone vibrates when you turn it on after doing a battery pull, then it's probably an SLCD issue. If not, it's likely a battery issue.
You say you were running CM7 with no problems on the phone, the battery drained, the phone turned off, and now it wont charge or turn on?
You can take it to Verizon and have them check the battery for you as well.
Click to expand...
Click to collapse
Steve's is an easy SLCD issue. Downgrade, lost screen.
The OP's... well I have no idea but since it doesn't boot up and gets no charging led then I'd say it sounds like the phone is dead. Best of luck to him and I hope he's got insurance.

i tried a new battery an still nothing, i believe i am amoled, and its like when you hold the power button and the volume up button and it vibrates, then wont turn on til you pull the battery, except its like locked in safe mode so bad that it wont even let the phone charge. so its dead, and wont come out of safe mode, and wont charge. wtf. i just got a new phone so i dont have insurance on it anymore but wanted to sell it to make some of the money i spent back...

[Q] What the hell just happened??

So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)

zander21510 said:
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
Click to expand...
Click to collapse
My first guess is your battery is shot. i was gonna recommend the power button failure but if its staying off it might not be that. but id let it charge fully then try to boot up.

Thanks, oddly after a bit of messing around finally got it to boot up. Immediately backed up in CWM....seems to be acting OK now. Idk what happened...

i'll guess, the USB connector got short-circuited when you plugged in, and it caused a cascade failure that fried the SD card or something else inside the phone
there was a factory defect back then with the old SGS 1 (i9000m) model, they fixed that after the 3rd batch, everyone with an old phone from 1st and 2nd release batches, were able to exchange i for a new one.
however in your case, that's not a factory defect, but you plugged it wrong (my guess)
because it has happened to me before when i plugged it in, but the battery was still not charging even after several minutes, yet the phone was getting really really hot
then i unplug, and plug it back in and got the sound feedback "tuu tuud" and then it was actually charging after a few minutes
the first time around even though the charging icon changed, there was no feed back sound, and that was the key, it was not plugged in properly.
so after that time, i always made sure to verify to make sure the phone was plugged in properly and not just relay on he visual icon.
check back after a few minutes, to make sure the phone doesn't get very hot, and it actually increased 1%

It happened again today! After a full charge overnight and no problems for the day up to a little while ago, I opened my email app, it froze, then proceeded to start boot looping. I'm in class so I don't have my computer to try to bring it out of it...so yeah that sucks...
I do remember when I got it to charge yesterday it showed it was charging for 20-30 minutes, but after I "revived" it, I found it hadn't charged at all.
I have been using a Nokia USB cable to charge my phone since I got it, because it was longer than the cheapie Samsung cable that came with it...but it hasn't ever caused problems before. And it charged just fine last night.
How long is the warranty on these things thru tmobile? I may just swap it out while I still can.

Also on an unrelated note, I upgraded to the LG3 radio because I was meaning to anyways...

I pulled it out of it again! This time I held the power button while putting the battery in, when it vibrated I let go, it vibrated again, showed the Samsung logo, and then booted like normal

May I ask what rom are you currently on?

datrapstar said:
May I ask what rom are you currently on?
Click to expand...
Click to collapse
CM9.1 nightly 9/3 with included kernel

It did it a third time during class while it was in my pocket, the power button trick didn't work this time, I had to pull the battery after the samsung logo, plugging it back in to get it to boot...but...
near the end of the CM9 boot animation, when it vibrates and the auto brightness kicks in, it started it again! I have yet to revive it...
This is a bit upsetting because I had just got CM9 the way I liked it and I don't exactly have the time right now to mess with warranty and a new phone...I would like to fix it.
There are about 20 different threads on here on how to revert to stock...let me as a last ditch try to revert to stock and see if it keeps doing it...unless somebody has any ideas...

I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.

zander21510 said:
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
Click to expand...
Click to collapse
Here you go!!
http://forum.xda-developers.com/showthread.php?p=30832325
Sent from JMT Goodness

Well, finished playing stupid for T-Mobile, in two weeks I will have my replacement T989. Now all that's left is returning this thing to stock before it starts acting up again.
And my temporary replacement phone?
HTC Dream, aka the G1, the first Android phone! Lol what a difference...GB feels like a dinosaur...

http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app

datrapstar said:
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks! got it all done, back to ugly, ugly stock lol...and just when I thought maybe I would have to brick it myself it did the reboot thing again...so pulled the battery and there it sits factory reset.

Phone a goner?

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!