Develop Bugs

Dead Evo after radio update

I flashed the s3vo version of froyo on my phone and after a reboot I went back to update my radio. Once the update completed I reboot my device and saw the error screen with the software box and the droid outside of it.
I assumed something was wrong so I pulled my battery thinking I could get back into recovery and restore a back up, but now I cannot get the phone to power back on at all.
Any ideas?

Try to plug the phone into your computer and boot into recovery via ADB.

Haven't done that before so I'll have to look around for instructions.. in the meantime if my phone has no power will I be able to do this?
I cannot get the phone to power on. I have tried swapping with my wife's battery but no luck.

1. Make sure you have a charged battery.
2. Have you phone plugged in to the charger while trying to power on.
3. Are you holding down the power button and volume down at the same time to try to get into recovery?
:shrugs:

Bad news. if you cannot go into recovery or adb your phone is bricked
Sent from my Nexus One using XDA App

The charging satus led light does not come on and it still does not respond

That's the only moment from all when the battery cannot be removed. if you have a charged battery and cannot power the phone sorry to tell you this but you just got yourself a 500 dollar black brick
Sent from my Nexus One using XDA App

good thing i have phone insurance :knocks over glass of water:

I was doing the same think, and my phone bricked, had to geta new one yesterday...I rooted with unrevoked before, going simpleroot this time to make sure I don't have problems this time. good Luck

good thing this happened before phones with new software hit the stores!!!!!

Same thing happened to me. I battery pulled during a radio update. Arrrggghhh, brick.

Seriously guys, you need to research thuroughly before doing things like this. After flashing, the phone needs to reboot then it goes through another stage of unpacking and finalizing the flash. There are very comprehensive instructions here and else where about flashing a new radio. Read, read, and read some more and most importantly DON'T PULL THE F'ING BATTERY!

i didn't get that android screen when i flashed the radio on our other evo, so i assumed something was wrong on mine.... oh well.. new phone should be here in a few days

READ INSTRUCTIONS.
When in doubt, read again and have some patience.
You guys are basically bricking perfectly good phones and not allowing other people to get their nice shiny EVO's because you had to get yours ONLY because you failed to take an extra 10-20 of your life to READ CAREFULLY.
I do understand that the lack of knowledge may have caused you to "mucK" it up but your actions are your responsibility so I suggest that you READ before you try to root or flash.
On the other side of spectrum, I completely understand your naive actions. I also have had issues when I flashed and I as sweating it for a bit but I NEVER would pull the battery during a radio flash. IT IS SAID 1,000,000 times that it can BRICK your phone! -LOL!!!
...well, at least you've learned a $50-$100 lesson from this

Every time you flash a new Radio or WiMax, you'll get the android and the box on your screen. It sucks that happened, but for future reference, you should always have that happen when you update either of those two.

My phone is broken but I'm getting a replacement on the manufacturing warranty.

Have some patience before pulling battery, I personally always wait at least 15 to 20 min if it is stuck on a screen. And if you are having troubles with following written directions their is always youtube.

3 button download/recovery mode saved my butt.

Within the 14 days return policy I took my Galaxy back after it bricked for no reason. I was almost stock other than unlocking it and running ADW. Too many things wrong with them so I gave it one more chance with a replacement. The new one has a working recovery/download mode so that's the biggie for me. The lag seems better and the GPS actually works. Great, I feel better. But I decided that I won't root it yet since 2.2 is coming soon. I'll let it flash as designed before digging deep.
Yeah, right. After noticing that the WiFI is still flaky at random times I turned it off again today when it wasn't passing any data. 3G still working so fine. But then the Market started to FC which I've not seen at all. I shut it down and rebooted again which is the fix for my WiFI. Well, it once again decided to brick just like the last one. I get past the logos and then just a black screen. She's bricked and I didn't even root it this time. Only thing not stock was ADW launcher instead of the Samsung thing that I don't like.
So I put her into recovery mode and did a factory reset. That fixed it and I setup all over again. Luckily with 2.1 you get a list of all your previously installed apps in Market the first time you enter so if you don't leve the app you can quickly install everything again. 20 minutes later I'm back in business except this time I'll stick with the launcher it came with, can't think of anything else that would cause this sudden bricking other than the wonder phone might be a piece of crap. I just don't know yet.

By reading the title I thought you meant that Samsungs new update to activate the 3 button combo had saved you. Having a phone with download mode enabled is quite hard to brick, you can always just put it into download mode and reflash with Odin.

That's the point, my replacement phone came with the update that Samsung is pointing people to. Labeled the same as the previous update but indeed has the button thing fixed. Until the next update comes along I'm not touching Odin or anything else, these phones have enough troubles as it is. I'm still concerned that mine bricked again simply by turning it on.

3rdcoast said:
That's the point, my replacement phone came with the update that Samsung is pointing people to. Labeled the same as the previous update but indeed has the button thing fixed. Until the next update comes along I'm not touching Odin or anything else, these phones have enough troubles as it is. I'm still concerned that mine bricked again simply by turning it on.
Click to expand...
Click to collapse
This is just my opinion but I don't think the phone would have come with the update, it would have just been an untainted unit that didn't exhibit this problem. Only a subset of new units were lacking the download and recovery modes and the fix released a couple of days ago was designed to correct that problem.
These modes are a standard feature of pretty much any Android device.
At any rate, good to hear that you have a fully functioning unit out of the box. I had to go to some length explaining and demonstrating the issue to the store from which I got my unit lacking these modes as well as my carrier until the fix came out and I fixed it myself.

I don't know either. I based my guess on the fact that Sam's fix happened to be an update that version matches what mine now shows. And my situation is a prime example why all phones need this mode. Not everyone would fix it the way I did but it only cost me 30 minutes and a few curse words because my pictures are all gone before I could get them off but I'm back up and running and that had to save somebody a few hundred dollars.
I'm still very nervous though, it did brick this morning without me doing anything. This time I don't even have NoLED or ADW but I can't leave it that way forever. My trusty Magic is way more tolerant of OS abuse.

[Q] Evo randomly reboots to white screen and vibrates 5 times?

Can anybody help me out with this? I've already searched but haven't found a clear cut answer on what to do.
For a while, I've had random events that cause my HTC Evo (running the latest stable release of CM7) cause my phone to suddenly show the "HTC Evo 4G" white screen, then go black and vibrate 5 times while having the green LED on, which never lets me do anything until I pull the battery out and start it up again. It used to only happen when I did specific things, like whenever I tried using Google Goggles at the store (and had to go through all the trouble of disassembling my 3 layer protective case just to pull the battery again). It even happened again yesterday when I was trying to use Goggles on a specific item, but it has happened before in other events since then, like when I was browsing my phone's running applications menu, or even one time when I was simply browsing the internet on it.
I've been taking steps to try and fix it, but I think it's been getting worse. I tried downloading CM7 and Google Apps again to flash on the phone to see if it fixed anything. I tried doing this again, but clearing the data and cache this time. I tried flashing the latest CM Recovery (since I stayed with 2.5.x.x for as long as I could remember), and I'm pretty sure it's gotten worse. There's points where I get to the CM7 boot animation and the phone then does the white screen and five vibrates again, and just a moment ago when I was sure I finally solved it after clearing data and cache, while filling out my Google account info, it happened again and I was greeted once again by that horrendous white screen and the five vibrates.
Now I don't know what to do. I still have S-OFF, but I have no plans to unroot. Can anybody think of suggestions? I've already tried Googling and haven't gotten anything useful enough to help me so far.
EDIT: I guessed it would help if I was a bit more specific. This started happening about two or three weeks ago after I tried using Goggles for the first time in ages. Since then, I've had this issue coming back over and over. It also puzzles me how Goggles usually works completely fine when I'm at home but causes the phone to go black and vibrates 5 times whenever I'm at a store.
Also, right now, I re-downloaded CM7 and Gapps from the CM mirrors instead of simply reusing the ones that ClockworkMod had saved for me already. I hope this somehow makes a difference.
Also, last edit, if I manage to solve this somehow, I'm going to definitely post the answer to what I did in case anybody else out there is having the same issue.
EDIT 2: Welp, re-downloading CM7 and flashing again didn't do anything to fix the problem. I'm going to try another ROM to see if the problem persists. I really want to stay with CM7, though.

Did you wipe everything? Cache and so on ect....?

I wiped everything and I'm still having the issue.
I also caved and I'm going to unroot because the retards over at the Sprint repair center refuse to look at it otherwise. I got my hopes up after hearing on places like XDA or the CM forums about how Sprint didn't care about rooted phones, but I guess the Sprint guys in my area do. I'm currently downloading unrevoked forever son and PC36IMG right now.
I'm just hoping I can get a new Evo after this, because there's a chance I could lose root forever after doing this. But I'm so certain it's a hardware problem.

SirSigma said:
I wiped everything and I'm still having the issue.
I also caved and I'm going to unroot because the retards over at the Sprint repair center refuse to look at it otherwise. I got my hopes up after hearing on places like XDA or the CM forums about how Sprint didn't care about rooted phones, but I guess the Sprint guys in my area do. I'm currently downloading unrevoked forever son and PC36IMG right now.
I'm just hoping I can get a new Evo after this, because there's a chance I could lose root forever after doing this. But I'm so certain it's a hardware problem.
Click to expand...
Click to collapse
Why would you lose root "for ever"?
Just curious ....
Sent From The Tree House Out Back!

I had the same exact issue with my Evo over the past 2 weeks. But I never use Goggles and run MIUI pretty much exclusively. I was never able to fix it and it just got worse. I unrooted and still have the same problems.
I notice it happens on 3g data, I can't remember when it happened on wifi.
I am selling mine back to Sprint tmrw and using my upgrade to get the Nexus S for$50. Then hoping the Evo 3D comes out within 30 days.
Sent from my PC36100 using XDA Premium App

I took it back to Sprint today, and after being treated like a second class citizen for rooting over and over, they managed to somehow fix the random reboots, but have initiated the OTA update for me. Now I'm sitting here with it and it's asking if I should install it now or later.
I'm hesitant because I tried to unroot earlier, and since then, the technician at Sprint said that it wasn't really unrooted or something (I remembered using unrevoked forever last year when I rooted). I'm scared that maybe I'll lose my chance at being able to root again if I accept the update or not. I'm also scared if I won't be able to get full root from here.
EDIT: SON OF A *****. I can't believe this. I applied the OTA update like a good boy and everything, and then the phone starts boot looping randomly again. This is the last straw. I'm going to go back to Sprint tomorrow and be more in-your-face about this problem. I'm through letting them treat me like **** just because I rooted my phone once.

I have a similar problem.....
My problem is random. My phone will go into constant reboot mode until I pull the battery out for 10 minutes. Just pulling the battery and putting it back does not help.
I also noticed that I am losing GPS signal occasionally. It is random too. The GPS will come on and work for about 5 minutes then just lock up. I have to reboot to get it working again and there is no rhyme or reason as to when it will stick (or wont) or how long it will last. It may work for 3 days and then not work a lick for 3 days.
The local Sprint store replaced the back red portion of my phone (the part with the camera lens and kickstand) stating it was an GPS antenna problem. I got 30 secs outside the store and tried the GPS....same problem. I went back into the store and showed them and they tried to convince me I needed AGPS on as well. AGPS always worked but is not as accurate as the satellite GPS. The repair shop refused to do more or order a replacement. I just got scammed out of $35.00 cause nothing is fixed.
I got so pissed, I called Sprint. They were terrific. They refunded the $35.00 the repair center charged me of the repair (the rip-off repair) and agreed to send a replacement phone. Awaiting arrival of the replacement but they are back ordered...so, maybe, I'll get a new phone instead of a refurb.
Long story short...I don't know what is causing your reboots. Mine could not be solved by software changes. My phone was rock solid until around a month ago. Then the GPS dropouts and reboots became more frequent until they became unlivable. I think you have a bad device and would seek replacement.

I had the same problem with mine about a month ago. It happened once about a month before that and then a month ago started happening a lot. I finally narrowed it down to how "hot" it was (body temperature in this case). So basically any time that I was in the car it happened. I was able to unroot (you have to make sure you to s-off on) and put a stock rom on it, and take it in with it happening. They took it for an hour and said they had not seen any issues. I finally convinced them and the replaced it with a refurb. I'm okay as long as it works, but it makes me wonder what happened. When I first got it I used fresh for about a week and then went to CM and was on it the rest of the time. I used an SBC kernel starting around the same time and am thinking maybe that had something to do with it... Just as a precaution I'm staying away from SBC kernels.
If I were you I would just go to the store and get a replacement if you can otherwise if it's like mine you won't be able to count on it working...
Good luck

HELP! My phone gets hot and restarts! Please look for more info inside!

Hello dear friends!
HTC let me down Kind of stupid phones indeed at least desire...
I have my phone for quite a time now, it is rooted with unrewoked, clockwork recovery and s-on. I flashed many different roms in the past and everything was brilliant. In a pas half-a-year or so I stayed with only one ROM - MIUI-Au. I kept updating it to the newer versions and so on and on. Never had any random reboot or something. At least maybe it was because of some strange app or something else. But now it started to reboot randomly and constantly!
Phone gets hot abit and it just reboots, and never comes to android homescreen again, until I put out the battery, hold it for few minutes, pop it back and then it boots. But as soon as start to play music, or run a game the phone gets hot abit and reboots again. and so on and on. I thought maybe it was a miui issue. So I tried to flash different roms, but guess what? None of the even boot! The main screen shows and with the same second it bootloops again and forever!... (
Even from recovery it sometimes reboots randomly. So i managed somehow to flash my miui back and it at least boots. But it is very unstable now, I barely can use my phone now
PLEASE WHO CAN HELP ME????
My warranty probably out of date, and my phone is rooted, I dont think HTC would accept it...
any thoughts? friends?

What have you set the CPU max to?
Sent from my HTC Desire using xda premium

Thank you for response! Appreciate, really!! I didn't set it, I left everything by default I think! Because as i said, i even tried flashing different roms, not only miui.
What else could be? By the way, with stock froyo rom If I remember correctly, sometimes it became extremely hot, but I didnt get any reboots from that. But now, it gets just a little bit hot and it seems that this causes the reboot...

Now what I just noticed, I get reboots even when the phone is idle. And it is not even warm!

If its not getting hot then I'm confused lol. It sounds like a actual hardware fault. Sorry I can't help with this one
Sent from my HTC Desire using xda premium

cluendo said:
My warranty probably out of date, and my phone is rooted, I dont think HTC would accept it...
any thoughts? friends?
Click to expand...
Click to collapse
try and get it taken back to stock if you dare.
The phone hasn't been out 2 years yet, which is how long the warranty is.

Thank you! But is there any possibility to fix it without HTC involvement? Maybe it is not hardware issue ? Can it be because phone is rooted and I flashed many roms to it ? I didnt try AOSP roms since reboots started, I will try to pop in Cyanogenmod or other and see if I will get reboots.
Would rerooting my phone and updating my recovery fix the problem?
and Note: yesterday I tried to S-OFF my phone, but I can't even do that with my unstable MIUI. It rebooted in the middle of the process..

I had a similar problem, apparently it's not uncommon on the early revisions. I sent mine to HTC and they replaced the mainboard.

Thank you for answer! But what if my phone is bought through a contractor?
Can just call HTC and ask the for repair? Or should I contact my contractor first ?

Just give them a call and they will try to help you out. I had a very good customer service experience with them when my desire had some issues.
They will require a proof of purchase though. If you managed to get the receipt from your "contractor" (I am unsure what you mean by a contractor), then there should be no problem.

Sorry for misleading word, I meant T-Mobile. I bought my phone under contract. I think I have a receipt. I even have whole box and stuff of the phone somewhere in my drawer.(just sayin ). So how is customer service of HTC? Poor, good ? I heard you need to tell them that you did a factory reset and that didn't help. Is that true. Also if I will unroot my phone, will they know it was rooted anyhow?
Ahhh....this overheating issue seems common. How they can release faulty phones?? No clue.
thanks for answers mates!

In Singapore, HTC service is really good. Phone was still under warranty.
It took me just one (real) call to confirm a repair order. The first call I was just checking to see what options were available to me.
The second call was an actual repair request. And the third call was me pestering them for a pickup date. heehee
In Singapore, repairs were done via courier. They picked it up and 1 working day later, they sent it back.
Naturally, you will probably need to impress upon them that you tried everything to fix your phone (which I hope you did which includes proving to yourself that it's not the ROMs fault).
You will definitely need to reset everything back to zero. In my case, I downloaded an RUU to totally reset everything back to STOCK, which included removing clockworkmod recovery. You WILL need to create a goldcard for this though so bear in mind that it's not exactly a case of a simple flashing procedure. At least not if you don't already have a goldcard.

Sorry if I overread it at some point, but you speculated at the beginning there could be some faulty app causing this, but you never meantioned performing a full wipe. Have you full wiped yet? Just to make sure it is indeed no software problem.
greets

Thank you for your answers. At the moment I have SuperNova classic ROM. ( 2.3.3 + Sense 2.1) But my phone crashes again and again, it is so annoying and causes me so much trouble.
I never tried a reset or unroot and return to original rom. Im just wondering now, would this help to remove or at least remove those reboots?
Today I was in my work and i was keeping my phone in my jeans pocket. it got hot as u would expect when keeping in pocket and suddenly it rebooten, then it went into a bootloop and started to bootloop 7 times in a row quickly. then again and again. It became very hot at that time.
For the interest, what exact hardware faults causes these reboots and why phone gets even hotter if you keep it on boot loop. If I keep phone cold, the rom usualy stays normal, without reboots. but as soon as I start using my phone, texting or calling for at least 5minutes of using it just reboots.
as I said- really annoying thing :S
I remember my happy times with miui, apps and no reboots Was fun!
cheers for helping!

I would give full wipe / factory reset a chance, and maybe RUU.
At least try it before sending phone to htc.

It is hardware problem, search forum. Fresh ROM without SD card, enabled WIFI and GPS, running G navigation, back of the phone is warm - restart after few minutes.
Maybe someone know how to read info form the phone right before reset? We could understand why the phone is reseting and hopefully add some patch.

Reboot-loop experience
Hey,
i had the same problem over the last few months: In the beginning my phone restarted only when it got hot, but it got worse over the last few weeks, in the end i was not able to use two apps at the same time (music and mytracks) or even to surf the internet longer than a few minutes. The problem did noticeably decrease when the phone was cool - tested by putting it on a fan or in the fridge. Yet, Skype was regularly killing it. As i really love my phone (and especially the AMOLED-Screen!) i did not want to resign. The battery cover contains some metal which is supposed to enhance heat dissipation - so i attached a little thermal pad to the hotter bottom of the phone to improve contact with the head spreader. Unfortunately it did not entirely fix the problem. Yes, it improved the situation a little, but it got even worse after a week or two - in the end i had to turn it in.
So i decided to take it to the Telekom-Shop. They were very kind and told me they would call the other day to confirm that the replacement would have been shipped. It took a few days longer, but i got a phone with the AMOLED-Screen! The employee said it was a used mainboard in a new case, completely refurbished. They only replaced the main unit, i kept the battery, sd-card, charger and so on. Now i have a working Desire again!
Terminator

Similar?
Hi i on the other hand have similar problem, qiute anoying one, my desire, cm7 hboot, s-off, insert coin cm7 rom, have phone freezing in diferent situations, sometimes its working sometimes just freezez and i need to get battery out and turn it one and sometimes several times in row to get it working again???? RUU and go to give phone in service? plaese advice?

@cp6ija Sandisk SD card? If yes, smash it.

nvm
cant delete post so just posting gibberish

Possibly Bricked T-Mobile T989

So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.

aaronpaws said:
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
Click to expand...
Click to collapse
Would it be possible that you tried so many combinations that the phone's battery has died? Have you tried plugging it in and seeing what happens?

charged for four hours and nothing.
Took it to a tmobile store and they're doing a warranty exchange since they couldn't get it to do anything either, even with a different battery.
Kind of curious as to what'll happen when I send it back since it has cyanogen mod 7 on it and its rooted. Then again, the phone won't boot, go into download mode, or recovery.
edit: I'm thinking the phone won't charge because of the custom kernel in cm7. Don't know how I would flash a kernel if I couldn't get it to boot though.

Dam,, too late
But for reference try!
Take the battery out and let it sit for a few min the put it back in and see if it boots.
If it still will not boot
Take the battery back out
Plug in the USB cable connected to the computer
Hold down the volume up and down then
Put the battery back in.
You should get the option: Volume UP / Volume Down for Reboot
Hit Volume UP and go get some Odin love!

I still have the phone, I'm gonna try this now. Will update with results.

aaronpaws said:
I still have the phone, I'm gonna try this now. Will update with results.
Click to expand...
Click to collapse
Cool man, keep us updated.

Well, I tried both suggestions to no avail. Anyone else have any ideas?

aaronpaws said:
Well, I tried both suggestions to no avail. Anyone else have any ideas?
Click to expand...
Click to collapse
I did not see you mention it, but did you try the "10 second" power button hold? You know it works when the phone vibrates 3 times. Simply hold the power button until it vibrates. It takes about 7-10 seconds (although when you think your phone is bricked, it feels like it is taking 5 minutes). If it vibrates, you are in the clear. You can usually get to recovery or odin from there. Try doing this on battery only first.

no cigar with the hold for ten seconds method on the power button.

aaronpaws said:
no cigar with the hold for ten seconds method on the power button.
Click to expand...
Click to collapse
It is really, REALLY difficult to brick a phone unless you are changing the radio (for example, flashing a wrong or corrupted radio). A kernel can hose your phone, but not brick it as you don't need a kernel to access recovery. A bad recovery could also brick your phone, but then you have download mode (Odin) to access that bypasses recovery. In other words, there are layers of protection or access points. We have not flashed any new radios for our phones yet, so you know that is not the problem. Having said all that, that does not mean you are not bricked.
To be clear on your position, you are getting no power response at all? Again, try this:
Unplug your phone;
take battery out (wait about a minute before replacing battery);
replace battery;
"10 second" hold until phone vibrates 3 times (or vibrates at all for that matter);
If you see no sign of life, then try the above process with phone plugged in (try plugged into computer and wall socket separately). Odin recognizes when you are plugged into computer and the boot process goes differently.
As for Odin bootup:
Load Odin;
Plug in your USB to computer;
try the volume/power boot up;
if that fails, try the "10 second" hold boot up with Odin running on your system and phone plugged in.
Outside of that, I can not think of any other way to get you to recovery or Odin.
I have flashed my android phones probably 150+ times in the last 2 and a half years and never made a brick. I thought I had, but was always able to get to recovery or bootloader (think Odin for HTC), and recover the phone. The only times I ever saw anyone truly brick the phone was when flashing the wrong or bad radio for their phone (radio is your 4G / cell receiver). So, walk through your processes to recover your phone in a methodical way and if that all fails, then return it. If you can't get it to go trying all these techniques, then T-mobile probably won't be able to as well and see that you rooted it.
Hope this helps.

Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.

What happens when you pull your battery, put it back in and attempt to turn your phone on?
Sent from my SGH-T989 using Tapatalk

@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).

Are you seeing anything on the screen?
Sent from my SGH-T989 using XDA App

aaronpaws said:
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Click to expand...
Click to collapse
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk

Typically with Samsung phones, if you can get ANYTHING at all to show on the screen it is not bricked.
Do you have a G+ account? If I can see what is going on while I walk you through it it would be easier. Could possibly hold an open hangout so others can join in and help or just for informational purposes.
I have had soft bricks on my behold 2, vibrant and SGS2, over 100 times all together. Sometimes it takes a little fiddling, my SGS2 seemed a little more difficult only because of the relative simplicity of it compared to the others.
---------- Post added at 02:18 PM ---------- Previous post was at 02:15 PM ----------
mikeyinid said:
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well i think he said it did boot initially, so I doubt that is the problem.
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
btyork said:
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
Click to expand...
Click to collapse
That depends if they can tell or not.

Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.

aaronpaws said:
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
Click to expand...
Click to collapse
Let me know, G+ is easy. Im out of class at 2est.

Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.

more like it wasn't plugged in properly to begin with
because that happened to me, even though it said "charging"... it was stuck at 43% for like 4+ hours, so i figured something must be wrong
and indeed it was, so i unplugged it, and plugged it back in, then voila! now it starts to charge as it was supposed to.
the phone is not picky by any means, i've used my old BB charges with it, the other HTC charger, the other samsung USB, the generic cheap chargers i get from Deal Extreme, etc
they all charges the phone just fine and fast
you do have to be careful when you plug it in, and make sure it's really charging
sn0warmy said:
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
Click to expand...
Click to collapse