Database Info

[Q] Help! Frozen Phone! Captivate

Hello, everyone.
Ok I'll explain the situation, then explain how it might of happened.
My phone will not turn on. It is stuck at the white at&t screen.
How It Happened:
I went out camping with family. We decided to go boating, No I didn't dunk the phone in lake water. I was listening to music on the boat, I noticed that an error message kept coming up. It said something along the lines of "com.android.phone has stopped unexpectedly, please try again." I would get this message every other second. So I booted the phone into clockwork recovery, hoping to recover an old back up of my system. It didn't work, I got some other error message saying it couldn't recover. Being desperate, I was like, "I'll just flash a different ROM!" I tried flashing cognition. It said it installed correctly. I was stoked! I rebooted my phone. I noticed it still showed the cyanogenmod 7 boot animation, so of course it didn't flash the other ROM. I decided to reboot my phone again. This time instead of turning all the way on, it stopped at the cyanogenmod animation, then restarted. It looks as if, right before it would restart it looked like a "loading screen" in clockwork recovery. It rebooted continually for the next 10 minutes until I took the battery out. I then tried to recover the phone again. Then I rebooted my phone, but then it froze at the at&t white screen. I left it like that for around 20 minutes. As we were coming back to the dock, I decided that I had enough messing with it and turned it off.
Any ideas. Did I do what they call "Bricking" and if so, what can I do to fix it?
And if not what do you think I did?
Thanks for help. I am getting a new phone in 2 days.
Btw, I am running through AT&T, and I own a sumsung captivate.

Well, the phone does sound like it has a pretty solid issue, I would have assumed that the flashing would have fixed it. There are probably other things you can try to get it running, but honestly after everything you've done, I would just Odin the phone. There are plenty of posts in the dev forums about running Odin. You download it on PC, plug the phone into download mode, click the button in Odin and after a bit, bam you are back to stock 2.1 like it's right outta the box. Then the obvious, root/rom. Unless you are desperate to get data off the phone I would just use Odin.
Someone may have a better answer, but weird stuff like that, I don't bother with trial and error. Just make sure if you do go with the Odin route, follow instructions, or you definitely WILL brick the phone. If you need the link because you actually can't find it on the forums (sigh) then I can send it tomorrow, it's bookmarked on another PC. Hope this helps

DanBroChill said:
Well, the phone does sound like it has a pretty solid issue, I would have assumed that the flashing would have fixed it. There are probably other things you can try to get it running, but honestly after everything you've done, I would just Odin the phone. There are plenty of posts in the dev forums about running Odin. You download it on PC, plug the phone into download mode, click the button in Odin and after a bit, bam you are back to stock 2.1 like it's right outta the box. Then the obvious, root/rom. Unless you are desperate to get data off the phone I would just use Odin.
Someone may have a better answer, but weird stuff like that, I don't bother with trial and error. Just make sure if you do go with the Odin route, follow instructions, or you definitely WILL brick the phone. If you need the link because you actually can't find it on the forums (sigh) then I can send it tomorrow, it's bookmarked on another PC. Hope this helps
Click to expand...
Click to collapse
No, I got Odin3. Thanks, I got it back to stock. I got my new Cappy today. I'm sending my old one to AT&T and all that. Thanks anyways.

[Q] NvFlasher problem

Hi everyone,
I am having a weird problem.
I have a friend's G2X that received the OTA and is up and running with official Gingerbread. Problem is the phone at some random point blacks out and you cannot wake it up or power it up without removing the battery and reinserting it.
So I thought why not use NvFlasher and flash CWM and then load a custom rom, see if that fixes these issues...
Using Windows 7 64-bit, I removed battery, held Volume UP/DOWN pressed while plugging in the USB, but nothing happened, no notification from windows...
Tried it on 2 other computers, no luck....
My G2X is fine and it comes up as APX device when performing the steps above, but when using my friend's G2X, nothing happens...
Does anybody know what to do at this point?
I tried performing Factory Reset on the phone, couple of times, it seems it does not help since the problem is still happening...
My computer is fine, USB ports are fine, my phone is recognized, but his is not...

My 1st G2x used to shutoff by itself, but I didn't have any problems with nVflash....
Sent from my LG-P999 using XDA Premium App

No one shoot me but try just volume down or up.... On mine its just volume down but the first g2x I had it was volume up and down...
Sent from my LG-P999 using XDA Premium App

I dont know if it makes a difference or not but try checking his usb debugging. that may be your problem. Settings-applications-development-usb debugging. Also be sure unknown sources is checked. I have had a few different roms, Faux AOSP, Trigger, and X-Boarders along with a couple others and I still have that deal every now and then when It wont wake up unless I pull the battery. Hope you dont but wanted you to know its not just your phone. I believe it is something in the hardware causing it.

bls2633 said:
I dont know if it makes a difference or not but try checking his usb debugging. that may be your problem. Settings-applications-development-usb debugging. Also be sure unknown sources is checked. I have had a few different roms, Faux AOSP, Trigger, and X-Boarders along with a couple others and I still have that deal every now and then when It wont wake up unless I pull the battery. Hope you dont but wanted you to know its not just your phone. I believe it is something in the hardware causing it.
Click to expand...
Click to collapse
That wouldn't make a difference, because the phone isn't loaded into a ROM when S/W update is running.

jonapunk said:
No one shoot me but try just volume down or up.... On mine its just volume down but the first g2x I had it was volume up and down...
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Tried all combinations, no go...
I am assuming the update messed something up. My next option is to get to a Windows XP machine and try the .kdz file and restore using that see if that helps...

Ok tried using the KDZ flasher and KDZ file on an XP machine and it went through with the update, or at least it seems like it did.
But the random blackout where I have to pull the battery and reinsert for the phone to come back on still happens and intermittent wifi problems as well...
Not sure if there is anything else I can do...
I will continue trying to get the phone into APX mode in order to use NvFlasher...

I have two G2x that do the Sleep Of Death - we now manually restart once a day, and that significantly reduced if not eliminated the problem. Or shall I say masked the problem...

My main problem on this G2x is that I cannot get it into the APX mode in order to use NvFlasher to flash CWM...
No matter what I do, what button combination or how long I wait the device never enters that mode...
Is there any other way to get the phone in APX mode?

After many, many tries, it finally worked!
I must have tried 50 times to plug it in to get it into APX mode.
Finally I removed the micro SD card and tried one more time and voila it worked.
I pressed volume UP first then Volume DOWN and kept holding them, plugged in and windows recognized it finally... whew!

[Q] Weird screen. Might be broken?

Okay so I was in the process of installing gingerbread on my phone with Odin when my phone just turned off unexpectedly. Not thinking anything of it, I turned it back on to this weird screen and the phone is stuck here. Any help would be appreciated. I have attached a picture of the screen for reference. Thanks.

Don't know if it'll help since I haven't had this problem before but, try removing the battery (just to get rid of that screen for now), then without even turning it on, go straight to Download mode and return it back to stock using GTG's procedure.
Sent from my SAMSUNG-SGH-I997 using XDA

How do I go about doing that? How do I put it into download without turning it on?

Pull Batt, Hold the volume up and down rocker....put batt back in and plug in your USB cable that is plugged into your Computer.
you should be in DL mode after that.

Okay that's what I thought you meant, but I wanted to clarify because I tried that before and I tried it again just now and still the same thing. The screen is slightly different, but basically the same.

does it boot at all, into a logo or anything?
without a method to get to Recovery or DL mode......i would think you needed a Jig to accomplish getting your phone back to a working state.

No it doesn't boot to anything. Just comes on to that screen.

http://forum.xda-developers.com/showthread.php?t=1147636
this is the Jig i was speaking of........otherwise you may just have to return it.

No you don't have to return it. It will go into dl mode. Hold volume up and down and insert USB cable. Open odin and reflash.
That is a static rainbow screen. I ran into that among others while trying to flash it. I just gave up and flashed to stock and reflashed miui. There are some who did have success in getting it to boot but not me.
Sent from my SGH-I997 using XDA App

TOA Duck said:
No you don't have to return it. It will go into dl mode. Hold volume up and down and insert USB cable. Open odin and reflash.
That is a static rainbow screen. I ran into that among others while trying to flash it. I just gave up and flashed to stock and reflashed miui. There are some who did have success in getting it to boot but not me.
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
if you had the same screen/problem how did you get into DL mode to reflash stock.
this may help him out.

Okay so the jig is something that I have to buy? And TOA Duck how did you reflash to stock from this? Thanks.

infamousosiris said:
Okay so the jig is something that I have to buy? And TOA Duck how did you reflash to stock from this? Thanks.
Click to expand...
Click to collapse
you could make it, just resisters and a gutted USB cable. but for 8 bucks to have a DL mode fix is kind of worth it.
i have only bricked my Cappy like that though, and i made one at work.

Goto gtg's ultimate unbrick thread in development and read through the directions for unbricking.
All I did to get into dl mode was pull battery, reinsert battery, hold vol up and down together and plug in USB.
Don't make the mistake I made the first few times trying to get into dl mode and hold power button along with. ONLY hold the 2 volume keys.
I understand where you are coming from. I thought my phone was f--ked too when I got that static screen.
Hope it helps
Edit,.... my dl mode screen looked different than the usual one this time. It looked like a computer and a phone side by side with an ! Between them. No worries its still dl mode.
Sent from my SGH-I997 using XDA App

Okay well I don't know what happened, but I was able to reflash to stock somehow. I did the process for getting to the download screen, but the rainbow screen showed up so I just decided to act like it was there and hit the volume up and it showed up in odin finally and I was able to flash it. Thanks for the help everyone!

Hand claps, im glad it was an easy fix.

Kudos to you for not freaking out or giving up.
*applause*

Okay I got it working again and reflashed the stock ROM using GTG. But now that its running its running like crap and the second I turn on the phone it gives me like 5 notifications that some apps have stopped unexpectedly and I have to force close them. Not only that, but now every time that I open an app it almost immediately closes saying that it has stopped unexpectedly and needs to be force closed. Any ideas on what might be causing this? I'm thinking that it has something to do with the reflash, but I'm not sure. Oh also on a smaller note, my market app is completely different as far as how it looks. Not a big deal but just thought it was interesting. Thanks.

i always a fan of reflashing.....lol
since you got it past that rainbow of death, i would go back to stock one more time wipe EVERYTHING and go from there....the Force Closes is not a Huge deal. usually happens from a bad install or using TiBu to restore sys data.
so Flash away,

weird screen
that kind of screen happens when you use the lagfix with a rom in 2.2 base and change it from rfs. you have to put it back to rfs and try the rom you installed again or you have to reflash back to stock. This has primarily happened to me when going from a 2.2 base rom to a 2.3 rom

[Q] HELP!!: My Phone Bricked Itself!!

Hi all,
As the title says :'( I flashed the new Android Revolution HD 3.6.2 ROM (updated from 3.6.0) and the recommended radio yesterday. Everything went fine and the phone was smooth as ever.
However, while I was playing robo defence today (played for about 5 mins) the phone suddenly shut down, rebooted itself to the startup screen (HTC Logo on a white screen) then when to a black screen and then repeated the process. This happened about 5 times after which I pulled the battery and then tried to restart the phone.
Now the phone won't power on at all!
- Nothing happens when I press the power button.
- Tried vol + power: nothing.
- Took the battery out, waited 20min, tried the above again: nothing
- Plugged it into my pc: nothing i.e. no LED light either
- Plugged it into a wall charger: nothing i.e. no LED light either
What I don't understand is how come my phone has died when I was not in the middle of flashing anything? Has my phone actually bricked itself?
any help would really be appreciated!
Thanks
Is there anything I can do via adb? (I don't know how to use it that well)

Keep trying to boot into vol+down and power
Leave phone on charger and try the button combo that happened with my mytouch when I had one and that worked.
Sent from my HTC Sensation XE with Beats Audio

Remove SD card, boot in recovery, clear cache / dalvik.
If you can boot of cource.

charlieb620 said:
Keep trying to boot into vol+down and power
Leave phone on charger and try the button combo that happened with my mytouch when I had one and that worked.
Sent from my HTC Sensation XE with Beats Audio
Click to expand...
Click to collapse
I've tried that. Still no luck No LED charging light either
septix said:
Remove SD card, boot in recovery, clear cache / dalvik.
If you can boot of cource.
Click to expand...
Click to collapse
No I can't boot at all. Tried booting without the SD card and no luck.
Is it even possible from for a phone to brick itself? Because after I flashed the ROM everything worked fine. It was only when I was playing a game that it died.
Could it be a battery problem? It would explain why no charging light is showing up

charge it via the original charger, hold on for a little while and try booting it up
i've seen it happen to mine once, i panicked just like you.

Before I s-off'ed or rooted I had this happen to my phone. It took a battery pull and then a long hold of the power button to get it to boot. I freaked thinking it was a dud (I had just gotten the phone).
If nothing works, it may be a hardware failure that had nothing to do with rooting. I would go for a warranty exchange. If YOU cannot get it to boot, neither will they without re-flashing the phone the hardcore way. (I believe its called a JTAG?). They will never know you rooted. They will just try a quick boot, see it doesnt, and then open it up to re-flash the thing via factory methods.
Matt

Would have to say its prob an fault with the handset as i am running the same setup as you and also playing robo defence and i play it for about 45 mins at a time with no issues at all .

awesam said:
charge it via the original charger, hold on for a little while and try booting it up
i've seen it happen to mine once, i panicked just like you.
Click to expand...
Click to collapse
Going to try that tonight. Its my last resort because i've exhausted every other option.
Diydude said:
Would have to say its prob an fault with the handset as i am running the same setup as you and also playing robo defence and i play it for about 45 mins at a time with no issues at all .
Click to expand...
Click to collapse
LOL...robo defence love! Thinking about it...it could be a handset issue. When I use the play robo defence on ARHD 3.6.0 ROM the phone would always die or go into a boot loop. But now its just dead.

Any news?
Sent from my Sensation using xda premium

would it be ground problem? check all the contact points
---------- Post added at 08:53 PM ---------- Previous post was at 08:45 PM ----------
would it be ground problem? check all the contact points hope it'll help

Just to update you guys:
I tried everything that has been suggested on this thread and had no luck.
I've sent off my phone to HTC today to hopefully get it fixed. we'll see how it turns out. They said it should be done and on the way back in 7 days. Will post if I get new info or updates

Installing the same Rom I had the same issue. New phone is on the way so I thought what harm could it do now. I tried everything u did. What worked was pulling battery out plug the wall charger in and then hold the power and vol down button then slip in battery and it went into recovery . I tried a reg reboot and nothing. So I pulled sd card out and put into another phone then downloaded another Rom. Put sd card back in shot phone and got back into recovery and flashed a diff Rom and it worked. The phone over heating is bad tho so will leave it be till New phone comes in.

I've had the no boot problem after messing with my partition tables, took it to my carrier, and they fixed it. Hopefully, your phone is so messed up that they can't read that it's been rooted (or hope that they don't care)

Did you install any Kernels with GPU Overclocking for example? Or was it only the normal ROM?

What recovery are you using?

CrazyCharlie said:
What recovery are you using?
Click to expand...
Click to collapse
Clockwork. Can't remember the version
xotox83 said:
Did you install any Kernels with GPU Overclocking for example? Or was it only the normal ROM?
Click to expand...
Click to collapse
No I didn't. Just stock ROM and the standard kernel that came with it. No overclocking either. I mentioned this before - i use to have boot loops every time i played robo defence - even with ARHD 3.5.x. so I reckon it was a hardware issue that eventually kicked the bucket when I moved to 3.6
Matt1408 said:
I've had the no boot problem after messing with my partition tables, took it to my carrier, and they fixed it. Hopefully, your phone is so messed up that they can't read that it's been rooted (or hope that they don't care)
Click to expand...
Click to collapse
Yea...i'm hoping exactly that! its being repaired atm. finger's crossed!

Have u try to connect ur phone to ur pc see if it detected? If you connect ur phone to ur pc and it show up something like can't find the driver that mean is ur phone got hardware issue just call HTC they will fix for you.

Johnsonyc said:
Have u try to connect ur phone to ur pc see if it detected? If you connect ur phone to ur pc and it show up something like can't find the driver that mean is ur phone got hardware issue just call HTC they will fix for you.
Click to expand...
Click to collapse
Yep tried that. My PC didn't detect it - there was no response from either device. Tried to force my PC to detect all connected usb devices and no luck.

My Phone Lives!
Hi guys,
Just to update everyone: I got my phone back yesterday and it's working again!!
Although it has been returned to stock again. According to the letter that came with my phone I think I've got a new main board. This is what it says:
Parts Replaced: PCBA-Main Board with SKU_ID, HTC Global, QSD8260 UMT
Anyone know what it means for sure?
I guess there is hope if a phone bricks itself entirely! and HTC didn't even bother asking any questions i.e. if I rooted my phone or anything. All they asked me was did I try to charge the phone via the main charger, did I take the battery out etc.

Good for you dude. I'm happy it worked out fine for you! And thanks for the update, good to know how they handle things over there.
Sent from my Sensation using xda premium

Help please! Just installed Android Revoluation HD, now won't turn on?

I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.

newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium

Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!

I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?

I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.

Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?

newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.

Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.

He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O

@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves

Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!