Database Info

I threw my phone in a fit of rage.

I was upset, could not handle life anymore. I was at work and just threw my phone with tremendous force into the wall. Made hole in drywall but phone remained in tact. Nothing seemed broken.
I live in a 3G area but not it never displays the 3G icon, infact most of the time it displays the roaming icon. My calls are always getting dropped. The internet on the phone no longer works.
I tried to reset the phone, and did a rom update with a rom I found here. Did update successful but no luck. Then re did a rom update with the latest one from the HTC website.
Same problem persists. How can I know what component is damaged and where can I get the part to fix it?
When I had a HTC tilt, I sat on my phone and broke the screen, was able to get replacement unit and change it myself with ease.
I would like to thank you all in advanced and hope you all have a wonderful day.

Study here how to dismantle the device and what the components are

Dude, some therapy may help....got insurance, do that and get a replacement phone

having taken mine apart, if it looks like it's still in one piece, the thing that jumps immediately to mind is just that your antenna got loose. it's the only thing pretty much with an exposed connector that could pop off. (the display may be able to also, but you'd notice that =)
search for the raphael service manual, only tricky part in getting to the antenna is after you pop the back housing loose on the top 3 sides, you have to pull back the top far/hard enough that you think you're gonna break the usb port to get the housing free of it. Pull it back a bit, unplug that speaker wire, then pull it back some more, needs a gap at the top of about 2 inches to clear the bottom usb port. it'll just click and snap free. i took 30 minutes doing it cuz i thought i was gonna break it.

[Q] Brick?

Hey folks, looking for a bit of help. So my wife washed my phone.(it didn't actually make it through the entire cycle because i realized what she did a minute or two too late. Regardless, the phone still got wet. I immediately pulled the battery along with SIM and SD.(I didn't try to power it on) I put the phone into a bag of rice and left it there for over 3 days. The phone seemed to be completely dried but i put it in the food dehydrator for good measure. The phone stayed in the dehydrator for 18+ hours. I reinserted the battery and plugged into AC and to my surprise I actually had a display. However, the phone gets to the AT&T screen and then reboots very near the end of the animation.(If left alone, the phone will boot loop indefinitely) I am able to boot into CWM recovery successfully. I tried flashing a ROM but the phone still boot loops. Flashing seems to work like it should, ie no errors, boot animation for ICS when flashing that. And yes, I've cleared cache/factory wipe/etc multiple times) I am unable to get into download via vol keys and usb cable to PC. I have a working jig that doesn't seem to invoke download mode either.(Plugging in the jig actually boots the phone into CWM recovery) The next step is to try forcing the phone into download via ADB.(downloading SDK onto new laptop now)
So after the above novel, my question is this: besides key combo, jig, and ADB is there an alternate way to force phone into download mode? A google search doesn't yield much...mostly articles ripped off of this site.
Is it possible to flash a .zip or script to force into download mode?
p.s. Odin does recognize the phone as a target when using the jig even though the phone is in recovery instead of DL mode.
Its worth mentioning that my lovely wife did spring for a brand new skyrocket the day my phone was washed meaning this phone is yet another to tinker with.

Wow what a great wife
Sent from my SAMSUNG-SGH-I727 using xda premium

You may have stuck volume buttons due to water or partial shorts on usb connectors. Try and get some isopro achohol and clean contacts and get compressed air spray to clear any debri
. Also take out sim card and clean it and the contacts
Good luck
Sent from my SAMSUNG-SGH-I727 using Tapatalk

brookfield said:
You may have stuck volume buttons due to water or partial shorts on usb connectors. Try and get some isopro achohol and clean contacts and get compressed air spray to clear any debri
. Also take out sim card and clean it and the contacts
Good luck
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion. I too considered that one of the buttons was stuck. However i am able to navigate within CWM recovery using the vol+ and the vol- buttons.
I actually did your other suggestion too.(not exactly but pretty close) I left that part out of my original post for the sake of brevity. Here's what I did:
I detached the the PCB from digitizer. I've got an electronics background so I happen to have quite a variety of small tools. One of which is a tiny medium/lite stiffness wire bristled brush.(It's like a tiny paint brush) I lightly brushed and cleaned all connections. This includes the connectable/disconnectable ribbon cables as well as any solder joint that I was able to access. Some ICs are "sealed" with epoxy so those connections couldn't be accessed.(Also seems like they stayed water proof) Basically I cleaned every place on the PCB that I saw irregularities. There were tiny spots of corrosive build up that looked as if they may be possibly shorting IC pins. Almost like "tin whiskers" except i used a magnifying lens and not a microscope.
I next used an air hose to remove debris I had just brushed off.(By the way, I like to stay away from canned air when using directly on components, it seems to leave a film. sometimes the un-evaporated contents also cause dust to cake)
I used a cap of isopropyl and some cotton swabs to clean the contacts further then let air dry. I wish I would have taken before and after pics because there was a huge difference. Anyways, this was actually done in between the bag of rice and dehydrator steps I mentioned earlier.

nthknd said:
Wow what a great wife
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yes sir. The original phone was bought out of contract at full price since I didn't want to wait for my upgrade to roll around. I was eligible for the contract discount this time.

Questions go in q&a

Here's the update:
I was able to force DL mode through ADB. Now that I can use Odin, I've realized that I'm not sure what i should flash. I'm thinking I'm going to try to completely return to stock. Simply flashing a ROM seems to work except for the boot loop. The boot loop happens regardless of the ROM i flash. The boot animation changes with different roms as expected. This leads me to believe the internal storage is indeed functional.
Should I try a kernel?
Bootloader?(is one even available?)
Stock Recovery?

silver03wrx said:
Questions go in q&a
Click to expand...
Click to collapse
Can I move this thread?

I hope it does move, this is an interesting story lol
Sent from my SGH-I727R using XDA App

Touch cover issues?

After having a duff sd slot on my original surface my replacement arrived today, all good, left it doing updates and installing my apps for a while, all was well, or so I thought..
The keyboard is now not responding after a while, connected, works, close the cover, open it again, screen doesn't come on, press power button screen comes on, keyboard not responding, close cover, screen stays active, disconnect keyboard and reconnect it and it works again..
Had a quick look through the settings and there's nothing I can see that relates to keyboard sleep or power management..
Tried it on my old surface and its fine :\
Wondering if anyone has seen or heard anything similar, otherwise another tech chat with support tomorrow...

You might want to try rebooting the new Surface, and make sure the connection port where the cover links up is clean, but otherwise I don't know what would cause that problem. I've had cases where the cover wasn't recognized, but disconnecting and reconnecting it fixed that.

Only issue I ever have with the cover is if I remove it while the tablet is sleeping and when it wakes it thinks it is still attached.

It's been rebooted many times so dont think its that, had a poke thru device managet last night and looked for power saving stuff but nothing relavant..
Connectors are all clean and it works in the old Surface.. :/
Maybe the keyboards just missing the tablet it came with lol

Still nothing, hard reset, power offs nothing, have now noticed that the edges of the touch cover are peeling apart at the corners so might get this replaced as well, so far the support guys have been spot on, the device however while really promising just lacks finish :\

Trig0r said:
Still nothing, hard reset, power offs nothing, have now noticed that the edges of the touch cover are peeling apart at the corners so might get this replaced as well, so far the support guys have been spot on, the device however while really promising just lacks finish :\
Click to expand...
Click to collapse
Two options....
1. Return the cover..
2. Bring your surface bad cover to Microsoft store and let them figure out what is wrong...
I am very happy with my surface and the touch cover...

I have a 5 second delay sometimes when opening and closing. Otherwise, ref let msft know

truffle1234 said:
Two options....
1. Return the cover..
2. Bring your surface bad cover to Microsoft store and let them figure out what is wrong...
I am very happy with my surface and the touch cover...
Click to expand...
Click to collapse
I've had 2 bad units now, don't think its the cover as it worked on the first surface before I returned it.
I'll get onto surface support when they are back, I don't seem to be able to raise a ticket on the new unit, touch cover might end up going back as well at this rate...
Sent from my HTC Desire HD using Tapatalk 2

I've had the same issue with the type cover. Sometimes it works fine throughout. Other times it seems to fall asleep until an adjustment is made.
I've caught the connection off by a few millimeters at times (although that doesn't explain why the initial connection would work), but you can look and check for that as well.
From now on I'll simply restart from the Power button without removing the connection to see if it's really a 100% mechanical issue.

Ha I've had all of these problems you've named

On Live Chat with support now, the MS forums seem to suggest a reset, I've tried it a few times tho, will see if they will fire out another cover..

Right, cover is being swapped out on AR as well now, hope they hurry up and take the hold off the card though, the hold is for more than it would cost to actually buy the bloody thing new again..

Weird fault with Note 10.1. Help!

Hi guys, newbie here, and im in desperate need of your help!
So I decided to buy an Note 10.1 and yesterday I received it. Straight away (after turning on) I noticed this rather irritating noise (like a notification sound but not one that is the ringtones options on the tablet) that the tablet made when I held it with one hand well, at first I thought it was a motion gesture since whenever I hold it with one hand (the right hand) it switches to the previous app if your in an app, or previous Web page when surfing the net. So I searched the options 100 times, and nothing to toggle off.
Anyway it bugged me more and more and I couldn't figure it out, then by chance i just pushed slightly on the back of the tablet and the notification noise goes off. Push again, it happens again. I decided that it could be a loose connection being made and remade every time I decompress the right side back panel (I can play it like a piano). So I took the back panel off (a pain in the ****) and noticed a ribbon cable that runs directly where I push the back panel (the S pen sensor cable). It was plugged in correctly, but wasn't taped to the battery like the 2 fatter ribbon cables.
So, I taped it down thinking that me pushing the back panel was moving it and creating a loose connection. I thought I had solved it. Booted it back up, no sound!!!!! Reinstalled the back panel, booted again and BOOM, the sound returns.......
Gutted.
Not sure what to do next, it definitely sounds as if something is disconnecting and reconnecting like a USB on a PC, im getting the sound but no notification or error. I have no idea why this would make an app switch to the previous app or webpage when on net.
Any help would be much appreciated.

Well, it seems I have solved the issue. Since this is a new account, I can't post youtube videos. So I'll leave those out for the time being.
Firstly, heres a video showing the fault. As you can see, I've narrowed it down to the docking station/charger connector.
The ribbon cable was seemingly depressed causing it to disconnect briefly before reconnecting when released. Probably the down side of having a flimsy plastic case.
Solve the issue I removed the ribbon cable and taped a small amount of foam right at the mouth of the connector, making the whole connection sturdier and harder to depress with the cover on, which can be seen here.
Hopefully this helps anyone who finds themselves with a similar issue.

joey8 said:
Well, it seems I have solved the issue. Since this is a new account, I can't post youtube videos. So I'll leave those out for the time being.
Firstly, heres a video showing the fault. As you can see, I've narrowed it down to the docking station/charger connector.
The ribbon cable was seemingly depressed causing it to disconnect briefly before reconnecting when released. Probably the down side of having a flimsy plastic case.
Solve the issue I removed the ribbon cable and taped a small amount of foam right at the mouth of the connector, making the whole connection sturdier and harder to depress with the cover on, which can be seen here.
Hopefully this helps anyone who finds themselves with a similar issue.
Click to expand...
Click to collapse
that woulda went straight back to the store

Yep, if the problem isn't fixed there's no way it'll get fixed under warranty now...
If the device is less than a week old, in Oz, the shop is supposed to replace the device immediately. This doesn't mean they won't try the old "It'll take 2 weeks to fix" and "It has to be sent back for repairs" schtick....

shaun298 said:
that woulda went straight back to the store
Click to expand...
Click to collapse
I got it from Ebay, although it was listed as new/unused.

[Q] Water Damaged Nexus 5 Boot Loop Suggestions

Hi all,
First off I would like to thank anyone and everyone that reads this thread, it helps me out if you have any information that could help me out here.
About a week or so ago my girlfriend dropped her Nexus 5 in water, and removed it almost immediately then brought it to me. Sadly the damage was already done and the screen was black. I got the back off and got as much water out as I could shake gently, and the screen still had haptic feedback when I touched it, so I messaged it and it displayed the notification light. This led me to believe the battery was ok, so we left the back off and let it dry for a while, and over time the screen and sound came back. We placed the phone overnight in dry rice, and for the meantime we put her SIM in an old S2. The next morning there was obvious water damage on the screen but less than before, and everything seemed to be working fine, games ran, music played, messages came and went on Hangouts, and when we plugged it in to charge it worked like a charm, so we believed we had gotten lucky, put it back in the rice overnight again and the next day tried putting the SIM card back in the phone.
The Nexus at this point asked to restart and we obliged, but this is when the problem started. It would get to the Google boot screen, hang, then restart, over and over. I tried going into recovery and I could, but no further than that. I am not an expert so don't know what would cause this, but I am led to believe that the battery and everything else is all in working order otherwise it wouldn't have been working and charging while it was on. I wonder if maybe there is a separate part of the phone used for BIOS bootup and it got damaged? Any suggestions or ideas on how to fix the issue would be met with extreme gratitude. Thanks for reading all this.
TL;DR Phone was dropped in water, aired out and worked fine, restarted for SIM card and get stuck in endless boot loop.

QyuBurt said:
Hi all,
First off I would like to thank anyone and everyone that reads this thread, it helps me out if you have any information that could help me out here.
About a week or so ago my girlfriend dropped her Nexus 5 in water, and removed it almost immediately then brought it to me. Sadly the damage was already done and the screen was black. I got the back off and got as much water out as I could shake gently, and the screen still had haptic feedback when I touched it, so I messaged it and it displayed the notification light. This led me to believe the battery was ok, so we left the back off and let it dry for a while, and over time the screen and sound came back. We placed the phone overnight in dry rice, and for the meantime we put her SIM in an old S2. The next morning there was obvious water damage on the screen but less than before, and everything seemed to be working fine, games ran, music played, messages came and went on Hangouts, and when we plugged it in to charge it worked like a charm, so we believed we had gotten lucky, put it back in the rice overnight again and the next day tried putting the SIM card back in the phone.
The Nexus at this point asked to restart and we obliged, but this is when the problem started. It would get to the Google boot screen, hang, then restart, over and over. I tried going into recovery and I could, but no further than that. I am not an expert so don't know what would cause this, but I am led to believe that the battery and everything else is all in working order otherwise it wouldn't have been working and charging while it was on. I wonder if maybe there is a separate part of the phone used for BIOS bootup and it got damaged? Any suggestions or ideas on how to fix the issue would be met with extreme gratitude. Thanks for reading all this.
TL;DR Phone was dropped in water, aired out and worked fine, restarted for SIM card and get stuck in endless boot loop.
Click to expand...
Click to collapse
Take the device apart, remove the motherboard. Get some rubbing alcohol and a tooth brush.
Remove any shields that can be taken off to expose more components. Then start scrubbing!!! Continue until you get all of the green/white corrosion. If there are any black scorch marks on the connections, take a eraser and it will remove the burn mark, then continue to clean with alcohol. Also the flex cable connections would need to be cleaned also.
The next step is up to you, if you feel comfortable with it. Make sure all plastic and rubber pieces are off the motherboard. Then stick it in the oven on 400F for 30 min to reflow some of the solder that may have gotten damaged.
Put back together, you may have to factory reset if the software got corrupted.
It is still highly possible to recover the device.
Good luck!

oOflyeyesOo said:
Take the device apart, remove the motherboard. Get some rubbing alcohol and a tooth brush.
Remove any shields that can be taken off to expose more components. Then start scrubbing!!! Continue until you get all of the green/white corrosion. If there are any black scorch marks on the connections, take a eraser and it will remove the burn mark, then continue to clean with alcohol. Also the flex cable connections would need to be cleaned also.
The next step is up to you, if you feel comfortable with it. Make sure all plastic and rubber pieces are off the motherboard. Then stick it in the oven on 400F for 30 min to reflow some of the solder that may have gotten damaged.
Put back together, you may have to factory reset if the software got corrupted.
It is still highly possible to recover the device.
Good luck!
Click to expand...
Click to collapse
I wouldn't go so far as reflowing solder for a dry-out.
http://www.amazon.com/o/ASIN/B000BXOGNI?tag=adapas02-20
can be attained at your local auto supply, simply disassemble the boards and give them a once-over spray and wipe-down. Reassemble, and then troubleshoot the bootloop, which may require a full stock flash. Good luck!

wideasleep1 said:
I wouldn't go so far as reflowing solder for a dry-out.
http://www.amazon.com/o/ASIN/B000BXOGNI?tag=adapas02-20
can be attained at your local auto supply, simply disassemble the boards and give them a once-over spray and wipe-down. Reassemble, and then troubleshoot the bootloop, which may require a full stock flash. Good luck!
Click to expand...
Click to collapse
I am not reflowing to dry it, sometimes solder on the connections/components need to be reflowed when they got WD or the device will not function correctly.I have seen it more time that I can count.

oOflyeyesOo said:
I am not reflowing to dry it, sometimes solder on the connections/components need to be reflowed when they got WD or the device will not function correctly.I have seen it more time that I can count.
Click to expand...
Click to collapse
There wouldn't be solder damage when OP acted almost immediately to dry it out. A cleaning, further drying should be all that's needed. One should NEVER turn on electronics until fully disassembled, cleaned and dried in any event.

wideasleep1 said:
There wouldn't be solder damage when OP acted almost immediately to dry it out. A cleaning, further drying should be all that's needed. One should NEVER turn on electronics until fully disassembled, cleaned and dried in any event.
Click to expand...
Click to collapse
The second the device hits air corrosion starts to build. Rice does nothing, it pulls a little bit of the water from the charge port and headset jack, basically what drips out. There is possibility that there is still water inside the device. He needs to open it up to scrub it down with a tooth brush and alcohol at least.The connections may break in time even after cleaning, that is why I suggest a reflow.

oOflyeyesOo said:
The second the device hits air corrosion starts to build. Rice does nothing, it pulls a little bit of the water from the charge port and headset jack, basically what drips out. There is possibility that there is still water inside the device. He needs to open it up to scrub it down with a tooth brush and alcohol at least.The connections may break in time even after cleaning, that is why I suggest a reflow.
Click to expand...
Click to collapse
I don't disagree most of this up to the point of reflow, which should be an absolute, last-ditch exercise. If corrosion is a major concern, after cleaning with solvent, a Caig deoxit treatment would be my next advice, but I think reflow is best left to the experienced.

wideasleep1 said:
I don't disagree most of this up to the point of reflow, which should be an absolute, last-ditch exercise. If corrosion is a major concern, after cleaning with solvent, a Caig deoxit treatment would be my next advice, but I think reflow is best left to the experienced.
Click to expand...
Click to collapse
Thanks to both of you for your advice on this. I will go and get some of the cleaning spray you suggested and give all the components a good clean, and will look for any scorch marks that may have occured when it was damaged. I would try flashing the OS as well but I'm not entirely sure how to do that when the phone has not been set up for USB Debugging. I attempted to flash it after unlocking the bootloader, but that didn't seem to work either. I will report back when I have performed the steps and let you know if there has been any progress.
Thanks =)

QyuBurt said:
Thanks to both of you for your advice on this. I will go and get some of the cleaning spray you suggested and give all the components a good clean, and will look for any scorch marks that may have occured when it was damaged. I would try flashing the OS as well but I'm not entirely sure how to do that when the phone has not been set up for USB Debugging. I attempted to flash it after unlocking the bootloader, but that didn't seem to work either. I will report back when I have performed the steps and let you know if there has been any progress.
Thanks =)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2513701
And to the guy above, sorry if it seemed I was arguing. A few too many drinks at that point.