Hello,
I somehow managed to burn my kindle fire down by accidentally pluging it to an stereo amps output jack. It turned off instantly and never have got it past the TWRP boot logo nor with a factory cable or the motherboard short circuiting the connections mentioned on another thread. Nothing works.
So, I searched for a new motherboard, found one and ordered it on ebay. Did not receive it within 1,5 months. Seller made a refund. Now I am searching for another one but cant seem to find any place where to get a replacement mobo. I would really like to go the road that consists of just the mobo, not the whole kindle with a broken screen or smth as I do not want to receive a piece of crap that has been floating in the pool for a week and then sold as "just broken screen, returns not accepted".
In conclusion- if any one of you could point me in any direction I would be really really grateful.
Thanks in advance.
Have you tried resetting the bootmode?
[Edit:] Nothing about your statement makes a whole lot of sense. Typically, when your device hangs at the boot screen, it means it's in fastboot and is usually as simple as changing the bootmode to normal. A factory cable wouldn't work because it forces the device into fastboot mode. The shorting trick is just as useless because it boots the device into USBboot mode. Besides, if you had fried your motherboard I don't think your device would even turn on.
[Edit:] What I think is more likely, assuming your amp output is a USB micro-b connector, is the connector is probably configured in the same way as a factory cable, forcing you into fastboot.
if you mean like with the kfu to set to normal boot mode- nothing, absolutely nothing there is mentioned on this forum works as something is fried near to the audio output jack, did not see any burnt resistors or anything else, but I am sure something is really f*ed up on the board itself where setting any bootmodes won't help.
It seems that the kf turns off right after the twrp "press power button for recovery" which I cant enter and the device turns itself off about 15 secs in to boot just at the moment where bootanim should start.
If there have not been any breaktrough methods discovered in the last 1.5 months on the topic of unbricking I am pretty sure that any attemt will end in a failure, so lets get back to the main topic - where could I score a working mobo?
skrubis said:
but I am sure something is really f*ed up on the board itself where setting any bootmodes won't help
Click to expand...
Click to collapse
You may be right, but you'll be pretty pissed off if you buy a new motherboard just to find out it was a software issue all along.
Before spending any money you should check that your drivers are in order (perhaps reinstall them) and try again.
When you use the factory cable, does it still shut itself down?
Yeay that would be unnecessary if this was just a software problem. I think the audio jack got a 12v dc blasted straight in to it from my car battery.
The kf turns itself off at any attempt to do anything, except it stayed on with kf unbricker one of the adp attempts. nothing else (even the short circuiting the motherboard pin to grnd did not work)
skrubis said:
Yeay that would be unnecessary if this was just a software problem. I think the audio jack got a 12v dc blasted straight in to it from my car battery.
Click to expand...
Click to collapse
Yeah, that would probably do it.
There's another thread here somewhere where buying another motherboard was being discussed. I'll post it if I can find it.
skrubis said:
if you mean like with the kfu to set to normal boot mode- nothing, absolutely nothing there is mentioned on this forum works as something is fried near to the audio output jack, did not see any burnt resistors or anything else, but I am sure something is really f*ed up on the board itself where setting any bootmodes won't help.
It seems that the kf turns off right after the twrp "press power button for recovery" which I cant enter and the device turns itself off about 15 secs in to boot just at the moment where bootanim should start.
If there have not been any breaktrough methods discovered in the last 1.5 months on the topic of unbricking I am pretty sure that any attemt will end in a failure, so lets get back to the main topic - where could I score a working mobo?
Click to expand...
Click to collapse
I don't know where to get a mobo in such conditions but I'd like to offer my 2 cents, have you tried reflashing recovery? when I first started testing Hashcode's ICS on my Kindle I'd see exactly the same behavior (since I didn't plug it into a live stereo output I had no reason to think something was wrong with the motherboard) so I tried flashing TWRP again and got it to work just fine.
Again, this is something that might/might not work but you can as well try it while you find where to get a new mobo, who knows, maybe it works and you save yourself some bucks
So I found a dead kindle at the local classifieds for roughly 10 bucks in US currency and brought it home and switched the motherboards, sure enough the kindle boots as new.
If anyone wants my old mobo to thinker with I will gladly give it to anyone who is willing to cover those 2-3 bucks for international shipping.
Thank you for your support!
Related
Ok, I'm getting desperate now. Not sure why this has happened. Tried resetting the device and nothing. Tried flashing it witch stock rom and now I can't get past the telephone provider setup as I can't touch the 'Next' button. Has anyone had a similar issue and if you have, please tell me there's a fix for this as I think my manufacturers warranty has ran out as I bought this device when it came out.
LeShin said:
Ok, I'm getting desperate now. Not sure why this has happened. Tried resetting the device and nothing. Tried flashing it witch stock rom and now I can't get past the telephone provider setup as I can't touch the 'Next' button. Has anyone had a similar issue and if you have, please tell me there's a fix for this as I think my manufacturers warranty has ran out as I bought this device when it came out.
Click to expand...
Click to collapse
I've got no advice for you but I'd just like to say I have never heard of a charger causing this problem before EVER.
right. if it's a genuine motorola charger, I even would say they are more reliable then oem.
anyway it's not making sense, because right behind charger connector goes power management IC which wouldn't send higher voltage through but would burn instead.
First I would try to test the digitizer, it should have around 500 ohms resistance on terminals for both horizontal and vertical when not touched. you can test it while still wired.
if it's working ok, then change the digitizer controller. I didn't have rhodium opened yet but from pictures, it looks like it's on mainboard so you probably can't do it yourself.
Hello All
I have an interesting situation. I sold my working phone on ebay, but the buyer returned it after 2 months (the phone went all the way to Ukraine and came back) saying the phone does not work. I now see that the water damage indicator is red only on the phone but not on the battery (interesting) and the display is black (back light is on but nothing else). I dont know where it went wrong since I know I checked it b4 shipping. Anyways the phone powers on (i can feel the vibration) and when connected to the computer shows it shows all the LG modem, usb, etc...So here is the question
1. Is there a software that can run from the desktop that will make the phone, ring, play noise over the ear piece, headphone jack etc..
This is so I can figure if there is more damage than what meets the eye and can decide if should replace the LCD or put it for electronic waste.
2. Does Nitro have the USB to HDMI option?
If so then I might try and use as one of those HDMI android stick computers
SW status: It is on STOCK ICS original shipment Korean English. Since I did the unbrick procedure and de-rooted it b4 selling the device.
Thanks for any suggestions
dcnarad said:
Hello All
I have an interesting situation. I sold my working phone on ebay, but the buyer returned it after 2 months (the phone went all the way to Ukraine and came back) saying the phone does not work. I now see that the water damage indicator is red only on the phone but not on the battery (interesting) and the display is black (back light is on but nothing else). I dont know where it went wrong since I know I checked it b4 shipping. Anyways the phone powers on (i can feel the vibration) and when connected to the computer shows it shows all the LG modem, usb, etc...So here is the question
1. Is there a software that can run from the desktop that will make the phone, ring, play noise over the ear piece, headphone jack etc..
This is so I can figure if there is more damage than what meets the eye and can decide if should replace the LCD or put it for electronic waste.
2. Does Nitro have the USB to HDMI option?
If so then I might try and use as one of those HDMI android stick computers
SW status: It is on STOCK ICS original shipment Korean English. Since I did the unbrick procedure and de-rooted it b4 selling the device.
Thanks for any suggestions
Click to expand...
Click to collapse
Hmm it kinda sounds like it's ether bricked or water damaged in some way or another, water can do some funny things to electronics. I'm not familiar with how the Nitro acts while it's bricked so you can browse the brick forums on here or someone can point you in the right direction if it is indeed a brick. If it is indeed water damaged personally I would scrap it because I doubt the screen would be the only thing effected by the water . Now the interesting thing is how did it get damaged? maybe the person dropped it in something or bricked it and sent it back. Just my two cents there are a lot more knowledgeable people that will help. Hope it works out.
I would agree it is not worth fixing - I would ebay it "as is". I am assuming that you shipped it out with a stock ROM right ? If it had a custom rom in it you could try to put it into recovery and attempt to "adb shell" into the device to determine if it actually booted into recovery. Although this is not a definitive answer. But even a bricked phone flashes the LG logo on startup. The nitro is supposed to support mhl http://meetmhl.com/DoIHaveMhl.aspx but I have never gotten mine to work, but I am on a custom rom
Nz
Hello,
I just got my N7 back from repair where they replaced the ME571K SUB_BD./AS board since the USB Port was not working anymore.
Luckily the port works now, but on the other hand the Touchscreen is not responding at all.
I tried restarting already without success. I also cannot reset the tablet since I got TeamWinRecovery Touch (and CWM 10.2) installed.
I can connect the tablet in bootloader and with "fastboot devices" it shows up as 077a744a.
Could anyone help me on how to flash or reset the tablet?
Ps.: This replacement was out of warranty, therefore I paid for it. The service center suggested replacing the mainboard (to make money) as well. Before I sent the tablet in everything was working just fine except mentioned USB Port.
Natschlaus said:
Hello,
I just got my N7 back from repair where they replaced the ME571K SUB_BD./AS board since the USB Port was not working anymore.
Luckily the port works now, but on the other hand the Touchscreen is not responding at all.
I tried restarting already without success. I also cannot reset the tablet since I got TeamWinRecovery Touch (and CWM 10.2) installed.
I can connect the tablet in bootloader and with "fastboot devices" it shows up as 077a744a.
Could anyone help me on how to flash or reset the tablet?
Ps.: This replacement was out of warranty, therefore I paid for it. The service center suggested replacing the mainboard (to make money) as well. Before I sent the tablet in everything was working just fine except mentioned USB Port.
Click to expand...
Click to collapse
Try flashing the JSS15R factory image.
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
I just flashed (with wipe) the factory image without success.
There's no response at all. Also when I try to get into recovery mode now the opened Android with the red exclamation mark shows up.
Is there a low level touchscreen calibration or something I could run through fastboot?
Anymore help would be greatly appreciated.
I'm starting to think they just put my motherboard in another tablet with abroken display...
I'd return it, it sounds like total screen failure.
Natschlaus said:
I just flashed (with wipe) the factory image without success.
There's no response at all. Also when I try to get into recovery mode now the opened Android with the red exclamation mark shows up.
Click to expand...
Click to collapse
That fallen android is just an image overlaid over the stock recovery menu. It just means you've booted into stock recovery. You can get the recovery menu by press/hold Power, press/release VolUp, release Power.
Natschlaus said:
Is there a low level touchscreen calibration or something I could run through fastboot?
Click to expand...
Click to collapse
There are various different touchscreen software you can load via fastboot and there is a calibration file in /system/usr/idc, but it isn't clear any of these would help if your screen doesn't work at all.
You can try changing the touchscreen software, worse case, it stays the same:
http://forum.xda-developers.com/showthread.php?t=2428133
Alternatively, you can open up your tablet and check to see if the flex cable for the touchscreen has become dislodged. There are 2 cables that run across the center battery. The one that is reinforced using tape is the one for the touchscreen.
Just did a reset but it didn't work.
I already tried these different firmwares from your link but it didn't make a difference.
I guess the screen is just broken. Or is it possible that the new Subboard is not working with the motherboard and therefore the screen fails?
I opened the back but it looks fine doesn't it? Is the big cable the on for the touchscreen or the orange one?
Natschlaus said:
I opened the back but it looks fine doesn't it? Is the big cable the on for the touchscreen or the orange one?
Click to expand...
Click to collapse
Yes, that is the cable. You can carefully removing the tape reinforcing the motherboard side of the orange cable and seeing if there is anything preventing a good connection, possibly use compressed air to clear out the connection area. The other end of the orange cable also connects to the touchscreen underneath the usb module so you would need to remove some screws to check that connection.
That's about all I can suggest. It didn't sound like a software issue because your screen completely doesn't work.
Yes I will look at the side where I have to open screws since that is the part they changed. Mabybe they didn't connect the screen.
I also wrote the support already.
Thanks for your help, I will report back.
Same problem experienced
Natschlaus said:
Hello,
I just got my N7 back from repair where they replaced the ME571K SUB_BD./AS board since the USB Port was not working anymore.
Luckily the port works now, but on the other hand the Touchscreen is not responding at all.
I tried restarting already without success. I also cannot reset the tablet since I got TeamWinRecovery Touch (and CWM 10.2) installed.
I can connect the tablet in bootloader and with "fastboot devices" it shows up as 077a744a.
Could anyone help me on how to flash or reset the tablet?
Ps.: This replacement was out of warranty, therefore I paid for it. The service center suggested replacing the mainboard (to make money) as well. Before I sent the tablet in everything was working just fine except mentioned USB Port.
Click to expand...
Click to collapse
Hi there
I have also experienced a very similar problem. The charging port on my 2013 Nexus failed to work, I then ordered a replacement part and changed it. It is very straight forward and simple to do for a novice like me.
on replacing the pcb the charging resumed faultlessly but the touchscreen has become unresponsive, i then replaced the old pcb and the screen has resumed functionality, but charging is not working.
The part was replaced by the supplier and it has occurred again, charges fine but the screen is unresponsive. Again i reinstall the old part and hey presto screen is ok.
I am now going to try and replace the actual usb pin itself from the original failed board and see if i can repair myself.
I had also done all the resets and reboots mentioned online.
Not sure if this helps but thought i'd share as its relevant
Many thanks
Is this the n7 2013? If it is how the hell did you get the back off? I tried and was afraid of breaking something.
Sent from my Nexus 7 using xda app-developers app
It's really easy. No tools required. Run your fingernail around the perimeter of the tablet edge between the screen edge and angled plastic. You'll hear the clips releasing as you go. Then carefully work the back off. No glue, just clips. Takes about 1 minute.
Sent from my Nexus 7 using XDA Premium HD app
Any update on how you solved this ?
I would appreciate if anyone could share the solution for unresponsive touch screen, if it's possible at all. The screen only reacts on the edges, and only to the swipe gestures, not to tapping. But all and all is the same - broken USB, replacement part, unresponsive screen.
no_cannabis said:
I would appreciate if anyone could share the solution for unresponsive touch screen, if it's possible at all. The screen only reacts on the edges, and only to the swipe gestures, not to tapping. But all and all is the same - broken USB, replacement part, unresponsive screen.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?p=45183659 it made 2 of my tablets usable.
Sent from my DarkKat Nexus 7 using Tapatalk 2
I think this is the same issue: http://forum.xda-developers.com/nex...a/usb-io-pcb-touchscreen-calibration-t2939991
Is there nothing to "calibrate" the screen? Asus is supposed to do it for you.
I think the problem is the rev. number of the usb board.
I found this explicative video on youtube, but I can't put the link. Look for "Nexus 7 2013 2nd gen charge port replacement issue"
I have the opposite problem: I changed lcd and digitizer two times, both times touch screen was completely unresponsive. I wonder if there's a software solution for this. I know usb board have different revisions, but what about digitizers? Are all the same for every nexus 2013 model? In this case I have to think touch screen connectors on usb board are broken somehow...
parcs said:
I think the problem is the rev. number of the usb board.
I found this explicative video on youtube, but I can't put the link. Look for "Nexus 7 2013 2nd gen charge port replacement issue"
I have the opposite problem: I changed lcd and digitizer two times, both times touch screen was completely unresponsive. I wonder if there's a software solution for this. I know usb board have different revisions, but what about digitizers? Are all the same for every nexus 2013 model? In this case I have to think touch screen connectors on usb board are broken somehow...[/QUOTEI
I know this is an old thread, but the problem is replacing a rev 1.3 board with a rev 1.4 board. They are not compatible touch screen wise. I have heard that there is a reset tool that only Asus has that can fix this...
Click to expand...
Click to collapse
My kid broke the original screen and I replaced it with a cheaper one that worked great until he broke it again
Got a new screen but the touch doesn't work and I can't enter twrp except if I disconnect one of the daughther board connector ribbons (can't remember which one now).
My guess is that the screen is for a different revision board.
Any way to solve the problem?
This is the perfect thread. I have a collection of Frankenstein parts and the problem I've had with 5 or 5 devices (flo) is the sub board. Some work, some don't. I'll try the firmware links and report back.
Has any one found solution for this problem, even my Nexus 7 2013 touch screen has stopped working after I repaired the micro USB port. Actually my tablet was not charging and I figured out that there was some lose contact in the micro USB solder joints, untill then my touch working. I haven't changed any daughter USB board but just resoldered the micro USB port after which my charging has started working and I can even connect a mouse or pendrive through USB OTG cable but the touch screen has stopped working.
I thought I'd share my experience with this, as I've seen posts in the past relating to a water damaged phone boot looping and I don't think I've seen a proper solution given.
First thing's first, this advice is in relation to a very specific type of boot looping. Nothing to do with rooting, or software bugs. This is boot looping that has come about as a result of water damage. It may not have been long, maybe a couple of seconds in the toilet or some brief rain exposure. Whatever it is, you know your phone has been exposed to some water and it has begun boot looping. There will be no way to get out of it, as the phone boots for 2/3 seconds max before looping all over again. Even when you go into recovery, same thing, automatically boot loops.
Most people, including the official HTC Service Centre, will tell you the motherboard is fried and needs replacement. Whilst it is possible that may be true, it isn't guaranteed. It's an easy way out for HTC, as they can charge you an extortionate price for a new motherboard and not have to bother going through the work of taking the phone apart to find out what is wrong.
The solution may be much simpler - the Power Flex Cable. This is a very small cable that goes along the top of your phone. WHen water damaged, this cable can become damaged, causing a constant boot loop. The reason being it constantly tells the phone the power button is on, causing a constant on/off cycle. In this instance the motherboard is fine and you can get a replacement Flex Cable for less than £5!
There is an easy way to tell whether the Flex Cable is the likely cause of your looping. When the phone is looping, hold down the down volume button only. Don't touch the power button. If your phone still goes into recovery (then loops again) then it is entirely possible your Flex Cable is damaged, not your motherboard.
Next step, order a Flex Cable (they are easy to find). When it arrives, you will need to open your phone (there are guides on YouTube for this), detach the motherboard and replace the Flex Cable. An advance warning, this isn't easy and you have to be extremely careful. One bad move and your phone is history. The motherboard is delicate. If you look around the internet you will find guides which show how the HTC One X is configured. Note that the Flex Cable is behind the motherboard and quite awkward to get off. I would post a couple of links but as a new member I'm not allowed! PM me and I'm happy to share some helpful links though.
You'll know quickly if this has worked. When connecting your phone it will no longer loop. Let it charge for a little while, then power on and hope for the best. If the Flex Cable was the problem your phone will reboot, and you will be able to use it and get your data off.
Note that water damage can have long lasting effects on a mobile phone. Whilst this may solve the problem for a while, it's entirely possible your phone will fail at some point down the line. Prepare for that and make sure you back up accordingly. The above advice may give you a lifeline in getting data off your phone, though, and being able to use it for a little longer. I know that when I was looking around the net I only found this advice by chance, and I think it was on a non-phone related forum. This advice may exist on the forum somewhere but if so it isn't so easy to find. I hope somebody may come across this topic when trying to fix their water damaged phone and find it is the solution.
Good luck!
Same symptoms, but no water damage
Hey man,
Thanks a ton for your post. I have the same issue, as in it won't stop booting at all. However, mine didn't happen because of water damage, but when I tried to do a factory reset (the phone was only on 5% charge so I'm not sure if that screwed it up). Do you think it could still be solved with a flex cable? I tried holding just the volume button down, and it does go into the bootloader so it seems pretty much exactly like what you have described!
Cheers
My only experience with replacing the flex cable comes from water damage, I'm not sure whether a software fault (as this appears to be) could have any effect on the cable itself!
When you get into the bootloader screen, does it just cycle all the way through to fastboot without allowing you to select any other options before rebooting? If so it would suggest your phone thinks the power button is constantly pushed down, which is suggestive of a power flex cable fault.
These cables are very cheap to buy, so if you aren't able to do anything else with the phone it's definitely worth a shot, even if it doesn't work. Just remember that opening the phone voids your warranty, and be careful if you do attempt it, as the insides of the One X are quite delicate. It would be very easy to break something!
de4life said:
My only experience with replacing the flex cable comes from water damage, I'm not sure whether a software fault (as this appears to be) could have any effect on the cable itself!
When you get into the bootloader screen, does it just cycle all the way through to fastboot without allowing you to select any other options before rebooting? If so it would suggest your phone thinks the power button is constantly pushed down, which is suggestive of a power flex cable fault.
These cables are very cheap to buy, so if you aren't able to do anything else with the phone it's definitely worth a shot, even if it doesn't work. Just remember that opening the phone voids your warranty, and be careful if you do attempt it, as the insides of the One X are quite delicate. It would be very easy to break something!
Click to expand...
Click to collapse
I had to replace my power flex cable when I was changing my battery as I accidentally snapped it.
Kahun said:
I had to replace my power flex cable when I was changing my battery as I accidentally snapped it.
Click to expand...
Click to collapse
It's very easy to do, the flex cable is a fragile piece. There are quite a few parts inside the HOX which could easily snap, which is why I always urge a lot of caution when opening the phone up!
de4life said:
I thought I'd share my experience with this, as I've seen posts in the past relating to a water damaged phone boot looping and I don't think I've seen a proper solution given.
First thing's first, this advice is in relation to a very specific type of boot looping. Nothing to do with rooting, or software bugs. This is boot looping that has come about as a result of water damage. It may not have been long, maybe a couple of seconds in the toilet or some brief rain exposure. Whatever it is, you know your phone has been exposed to some water and it has begun boot looping. There will be no way to get out of it, as the phone boots for 2/3 seconds max before looping all over again. Even when you go into recovery, same thing, automatically boot loops.
Most people, including the official HTC Service Centre, will tell you the motherboard is fried and needs replacement. Whilst it is possible that may be true, it isn't guaranteed. It's an easy way out for HTC, as they can charge you an extortionate price for a new motherboard and not have to bother going through the work of taking the phone apart to find out what is wrong.
The solution may be much simpler - the Power Flex Cable. This is a very small cable that goes along the top of your phone. WHen water damaged, this cable can become damaged, causing a constant boot loop. The reason being it constantly tells the phone the power button is on, causing a constant on/off cycle. In this instance the motherboard is fine and you can get a replacement Flex Cable for less than £5!
There is an easy way to tell whether the Flex Cable is the likely cause of your looping. When the phone is looping, hold down the down volume button only. Don't touch the power button. If your phone still goes into recovery (then loops again) then it is entirely possible your Flex Cable is damaged, not your motherboard.
Next step, order a Flex Cable (they are easy to find). When it arrives, you will need to open your phone (there are guides on YouTube for this), detach the motherboard and replace the Flex Cable. An advance warning, this isn't easy and you have to be extremely careful. One bad move and your phone is history. The motherboard is delicate. If you look around the internet you will find guides which show how the HTC One X is configured. Note that the Flex Cable is behind the motherboard and quite awkward to get off. I would post a couple of links but as a new member I'm not allowed! PM me and I'm happy to share some helpful links though.
You'll know quickly if this has worked. When connecting your phone it will no longer loop. Let it charge for a little while, then power on and hope for the best. If the Flex Cable was the problem your phone will reboot, and you will be able to use it and get your data off.
Note that water damage can have long lasting effects on a mobile phone. Whilst this may solve the problem for a while, it's entirely possible your phone will fail at some point down the line. Prepare for that and make sure you back up accordingly. The above advice may give you a lifeline in getting data off your phone, though, and being able to use it for a little longer. I know that when I was looking around the net I only found this advice by chance, and I think it was on a non-phone related forum. This advice may exist on the forum somewhere but if so it isn't so easy to find. I hope somebody may come across this topic when trying to fix their water damaged phone and find it is the solution.
Good luck!
Click to expand...
Click to collapse
Thanks. I've already taken the back off and noticed some broken bits of plastic...from the back....but I did notice a bit of ribbon that looked a bit screwed up....I'm gonna take it to the gizmo wizard to fix once I buy a new power flex cable.
Good luck!
Another thing to try
de4life said:
Good luck!
Click to expand...
Click to collapse
Old thread I know but thought it was worth adding that with a water damaged phone the issues can result from the fact that tap water contains minerals which can leave a conductive residue when it dries - can change resistances, cause shorts etc. What I've done previously is used isopropyl alcohol (tape head cleaning fluid) with a toothbrush on the motherboard. Brought a phone back to life. This removes the mineral deposits and cleans everything. Had to remove the metal covers from the mobo first though. If a phone is basically dead or not working right after water damage then it's worth a go. As de4life says, just need to be super careful on the HOX with all the delicate ribbon cables.
Indeed, the phone should be thoroughly clensed if possible to wipe out any corrosive liquids left behind from the water (especially if it's dropped in an ocean). The effects of corrosion can be very slow and potentially last for months.
M8 please reply to this all the flex cables that I found are 40$+ can you give me a link for one as you stated that would cost 5 pounds
It worked
It worked! I replaced the power flex cable with a spare one on my HTC One X, previously damaged by being sucked by my one year old son - water damage.! It worked!
Many thanks to you man!
IamNewBee said:
Many thanks to you man!
Click to expand...
Click to collapse
Wondering if this is the right cable?
http://www.ebay.com/itm/New-Power-O...972183?hash=item27d4be6597:g:n6AAAOSw9GhYbb-y
Thanks!
Thank you!
de4life said:
I thought I'd share my experience with this, as I've seen posts in the past relating to a water damaged phone boot looping and I don't think I've seen a proper solution given.
First thing's first, this advice is in relation to a very specific type of boot looping. Nothing to do with rooting, or software bugs. This is boot looping that has come about as a result of water damage. It may not have been long, maybe a couple of seconds in the toilet or some brief rain exposure. Whatever it is, you know your phone has been exposed to some water and it has begun boot looping. There will be no way to get out of it, as the phone boots for 2/3 seconds max before looping all over again. Even when you go into recovery, same thing, automatically boot loops.
Most people, including the official HTC Service Centre, will tell you the motherboard is fried and needs replacement. Whilst it is possible that may be true, it isn't guaranteed. It's an easy way out for HTC, as they can charge you an extortionate price for a new motherboard and not have to bother going through the work of taking the phone apart to find out what is wrong.
The solution may be much simpler - the Power Flex Cable. This is a very small cable that goes along the top of your phone. WHen water damaged, this cable can become damaged, causing a constant boot loop. The reason being it constantly tells the phone the power button is on, causing a constant on/off cycle. In this instance the motherboard is fine and you can get a replacement Flex Cable for less than £5!
There is an easy way to tell whether the Flex Cable is the likely cause of your looping. When the phone is looping, hold down the down volume button only. Don't touch the power button. If your phone still goes into recovery (then loops again) then it is entirely possible your Flex Cable is damaged, not your motherboard.
Next step, order a Flex Cable (they are easy to find). When it arrives, you will need to open your phone (there are guides on YouTube for this), detach the motherboard and replace the Flex Cable. An advance warning, this isn't easy and you have to be extremely careful. One bad move and your phone is history. The motherboard is delicate. If you look around the internet you will find guides which show how the HTC One X is configured. Note that the Flex Cable is behind the motherboard and quite awkward to get off. I would post a couple of links but as a new member I'm not allowed! PM me and I'm happy to share some helpful links though.
You'll know quickly if this has worked. When connecting your phone it will no longer loop. Let it charge for a little while, then power on and hope for the best. If the Flex Cable was the problem your phone will reboot, and you will be able to use it and get your data off.
Note that water damage can have long lasting effects on a mobile phone. Whilst this may solve the problem for a while, it's entirely possible your phone will fail at some point down the line. Prepare for that and make sure you back up accordingly. The above advice may give you a lifeline in getting data off your phone, though, and being able to use it for a little longer. I know that when I was looking around the net I only found this advice by chance, and I think it was on a non-phone related forum. This advice may exist on the forum somewhere but if so it isn't so easy to find. I hope somebody may come across this topic when trying to fix their water damaged phone and find it is the solution.
Good luck!
Click to expand...
Click to collapse
Thank you very much for typing this out! My Google Pixel OG (2016), which was made by HTC, experienced the exact same problem. I have just fixed it by replacing the power flex cable like you suggested.
lazinase said:
Thank you very much for typing this out! My Google Pixel OG (2016), which was made by HTC, experienced the exact same problem. I have just fixed it by replacing the power flex cable like you suggested.
Click to expand...
Click to collapse
I was surprised to get a notification for this old thread! I'm glad this worked for you. I had no idea HTC used the same design for the original Pixel.
ive been having a problem with this phone for a while. it has a problem with turning on and statying on. i will set it on charge while its powered off for atleast two hours, but as soon as i turn it on it will last for about 5 mins and turn off.
i first replaced the battery and it has the same problem. so i replaced the charging port and it was working fine for a few weeks and now its back to the same issue. i cant even get it to charge now
so just trying to figure out what kind of other components it could be
Disclaimer: You're at a more advanced level than I am. I've never done phone repair, and I don't know enough about phone hardware to say if there are other components that could be responsible. I'm a software guy.
That being said, I'll chime in with what I do know, on the off chance that it's actually helpful.
When computers get too hot, they do an automatic thermal shutdown to try to prevent permanent damage. I assume smartphones do this as well. You're on XDA, so there's a good chance you like to tinker. Did you overclock the phone? Overclocking generates more heat, which could potentially lead to a thermal shutdown or permanent damage. Or you might be using or storing the phone in a hot environment.
Have you tried using a different charging cable? Maybe the cable or its connector went bad. You could also test the cable with a different device. Maybe the wall outlet, etc went bad. Did you check the connectors that the battery attaches to, to make sure they're clean?
When you opened the phone to replace the charging port, maybe you didn't put it together quite right, so over time something came loose or got pinched. Desktops and laptops use various types of adhesives such as thermal paste, and computer technicians have to remember to reapply new adhesive when putting a machine back together. Maybe phones use some adhesive too, and maybe you forgot to reapply it?
Hopefully someone more knowledgeable about phone hardware will chime in, but the Incredible 2 section of these forums has been a ghost town lately. That's why I'm giving my two cents. If it were me, I'd just buy a new phone.
Slinkwyde said:
Disclaimer: You're at a more advanced level than I am. I've never done phone repair, and I don't know enough about phone hardware to say if there are other components that could be responsible. I'm a software guy.
That being said, I'll chime in with what I do know, on the off chance that it's actually helpful.
When computers get too hot, they do an automatic thermal shutdown to try to prevent permanent damage. I assume smartphones do this as well. You're on XDA, so there's a good chance you like to tinker. Did you overclock the phone? Overclocking generates more heat, which could potentially lead to a thermal shutdown or permanent damage. Or you might be using or storing the phone in a hot environment.
Have you tried using a different charging cable? Maybe the cable or its connector went bad. You could also test the cable with a different device. Maybe the wall outlet, etc went bad. Did you check the connectors that the battery attaches to, to make sure they're clean?
When you opened the phone to replace the charging port, maybe you didn't put it together quite right, so over time something came loose or got pinched. Desktops and laptops use various types of adhesives such as thermal paste, and computer technicians have to remember to reapply new adhesive when putting a machine back together. Maybe phones use some adhesive too, and maybe you forgot to reapply it?
Hopefully someone more knowledgeable about phone hardware will chime in, but the Incredible 2 section of these forums has been a ghost town lately. That's why I'm giving my two cents. If it were me, I'd just buy a new phone.
Click to expand...
Click to collapse
well i greatly appreciate your lengthly response. to be honest, it is my mothers phone, which is why i want to try and fix it. i gave her an iphone so she really doesnt need this phone but i would like to figure out what is wrong because i do like to tinker with things. i have tried different chords, wall outlets, usb ports on the pc etc. i will reopen the phone to see if everything is back together, because thats the only thing i can think of from what you mentioned.
thanks again. if anyone has had a similar problem, let me know
sounds like you're either having a battery issue or need to replace your charge port on your phone. its a really simple process all you do is order the port from like amazon or ebay and the old one on your phone just unplugs from your phone circuit board there actually is a tutorial forum in the development page for the droid incredible 2 that gives you instructions on how to do this. hope this was of some help to you and if so please click thanks.
jam0688 said:
sounds like you're either having a battery issue or need to replace your charge port on your phone. its a really simple process all you do is order the port from like amazon or ebay and the old one on your phone just unplugs from your phone circuit board there actually is a tutorial forum in the development page for the droid incredible 2 that gives you instructions on how to do this. hope this was of some help to you and if so please click thanks.
Click to expand...
Click to collapse
The OP already tried both of those things.
Oh ok yeah i just noticed where he put that. Hardware problem maybe. Im more into software myself than i am hardware.
MINE TOO! Omg
This... it's too much. Okay, a month ago the damned power button got too hard to press in, which should have been a warning that the hardware was getting faulty I suppose. But I downloaded an app that let me use the volume button to turn screen on/off. (I won't say which because I half-blame it, unfairly, for killing my phone
(Sorry, I'm still —mourning! the death of my phone I guess.)
The app was an ugly solution, I guess, but it worked. (I couldn't turn the screen off easily, so I set the screen-off to 10 seconds.) And I hadn't used screenshots in a while so that was no big deal; and my ROM could get me to Recovery easily enough, so screw the power button, right?
But then last night, my phone STOPPED CHARGING! I did a batt pull, tried new cords; turned off every useful app. I even went back to stock ROM, which (even though plugged in) left me with 20% batt. Might as well have bricked it, I guess.
Nothing worked. I was able to turn bluetooth back on so I could use my Air Droid acct to get my on-phone pictures, at least (everything else is safe on the SD), and then I charged it overnight in the wall and hoped for the best.
I was pretty thrilled to wake up to 100% charged! —For a few minutes. As soon as I unplugged it, it started discharging fast, and then not even the wall charger stopped it from discharging.
After brooding, for a few hours, I called Verizon tech. The tech (VERY nice, admittedly) said my Dinc2 was just dead. (Damn they're good: he was more sympathetic than a doctor delivering bad news!!) —But I feel so lost. He offered me a DNA or a Dinc 4G (and some motos and crap), but said my Dinc2 wouldn't be worth fixing. He said the power button alone was a PITA, but the dongle thing you plug the charger into was likely the problem, AND it might be the battery. Maybe he said other problems, but ultimately he suggested some pre-owneds he had for sale (I'm trying to keep my unlimited data plan), or try PhoneKarma.com. (He said he didn't recommend eBay, where they have Dinc 2s, but I'm not sure why.)
So ...do Dinc2s just have power issues after (?) 3 years? I guess that's a pretty good lifetime, but boy is it depressing. (I know — hooked on a damned phone. #Sucks.) I mean, it would be stupid to fix this one, or buy another one, right?
@Trebuchette, no matter what machine you use, rechargeable batteries do not last forever. Order a new battery from Amazon or eBay and you should be fine. They're pretty cheap and easy to replace. http://www.amazon.com/HTC-Incredible-6350-BTR6350B-Packaging/dp/B0064SI3QA
A case might make your power button easier to press. The OtterBox Defender is an excellent case that you can get for $15 used (very good condition), if a new battery successfully fixes your problem.
Hey: might be worth a shot! I did try another batt, but it was older too. And I didn't think of an otterbox at all, tbh. Thanks! Might be worth a try!
Hey: does it matter much if my USB cable is LG or whatever? I tried several different USBs too, but I'd been using this LG one (no idea how!) for probably about a year.
No, the brand of micro USB cable should not matter. It's a technical standard.
Don't buy a case until you've verified that a new battery actually fixes your problem. If a battery doesn't fix it, it's only a few bucks lost. In that case, I would then get a new phone.
i just came back to this thread after i basically put the project on hold for a while and wanted to see any new suggestions. so after leaving the phone alone for two months, i pluuged the phone in and i saw that orange ligh indicating it was charging. so far so good, im not using it as a primary phone which is good, but that would be my suggestion is to give the phone a rest for a while
EDIT: yeah scratch that, its doing the same **** now