hello guyz
Sorry for my bad english .
I''m here cuz my htc one max was out of charge ,
and when i plugged it to charge it won't charge ,
i tried to open it and same
#i tried to open it with recovery mode and smae
#led light not working too
#i tried different chargers with different outlits .
what to do plz ?
Constantly mess with all button combos when its plugged in. Try holding both vol buttons and power for example...
Jiggity Janx said:
Constantly mess with all button combos when its plugged in. Try holding both vol buttons and power for example...
Click to expand...
Click to collapse
i didn't work , same
Same here, vzw Htc One max no charge, no power....
One foggy hungover little extra bad on me. Was firewater s-off with temporary root, twrp 2
6.3 recovery flashed fine but never had SU commands only SH. In a hungover haze I noticed twrp had 2.7 open recovery out and without due thought I downloaded it to update the recovery. I blatantly force flashed the zip from my phone using CWMR. foolish of me straight out, no excuses. Phone rebooted twrp recovery flashed 2.7 zip and then power dropped immediately. Will not power up/charge.
I got the USB/DLOAD message. Been reading every since to self fix . Would appreciate advice on proper path to take. I've been reading on one hand since it was S-Off it possibly blew the LCD and no bueno brick city. Yet I've also seen success with flashing the RUU as a possible. Other option I found so far was run the JTAG method with Ubuntu and/or try shorting the 2/5 pins with 300k resister.
I'm not concerned about warranty, I would really appreciate anyone who has the time to respond and experience with this indescretion. I would prefer not to damage it further with incorrect fixes if possible. I believe i just jacked my boot image and need to use the RUU method unless the LCD was blown from over clocked over voting .
Direction on the correct method if any is appreciated. I'm completely open to answer questions i may not have addressed. Totally thoughtless and my fault yet I'm very clear on what I did to cause it. Many years electronics repair, still medicore Linnux skills so please go easy on me there. I just need the correct path if known. Im a big boy and fully capable of learning it on my own so no need for you to feel you have to list script and hold my hand.... but a good ass chewing is never out of line ") Thanks for any experience you wish to share.
someone help please ?
Phones dead, no led, no charging, no button combo brings it back. Everything worked great, plugged it in Friday night like always, wake up Saturday to find it was off while on the charger. The cable and charger that it came with, and girlfriends DNA charges on it no problem. Took it to Verizon and they tried a few things, nothing they did helped, like I was surprised. So they are sending me one, but I want to know what happened and how to fix it. This seems to be a common problem, but it seems most people at least get it to power back on at one point.
Exactly what was happen to me some time ago.The only solution i found is to open case and charge the battery about 10 seconds.I advise you to use usb port of your computer to charge it. Btw if you let it drain to zero you will have to do this procedure again
Related
I have read similar threads but want to make sure I did not miss anything...
My Samsung Galaxy S2 SGH-I777 device seems to be totally dead:
Pressing and holding power button does nothing
Pressing power and Volume Up and Volume down buttons do not get into download mode
Removing the battery and holding power button for a minute to do s oft reset and drain power did not help
Putting the unit in a freezer bag and into the freezer for an hour did not help
Leaving it charging overnight did not help
Using USB Jig method did not work
Here is the sequence of events, as best as I can recall, that led me to this state:
Device was rooted with CWM recovery installed and Android 3.2.4
I then installed FoxHound PsychoMantis 2 custom ROM so I could try ICS (bad idea for a noob)
I ran into the problem "Unfortunately, Samsung keypad has stopped" and device making it really slowwwwwww!!!
I then tried to go back to the stock version using Heimdall 1.3.2 and heimdall-frontend (build from source for my Ubuntu 11.04) and the XXJVU_heimdall.tar.gz heimdall firmware package. At this point the device was fully charged and I was still able to get into recovery mode but was getting "ERROR: Setting up interface failed!" from heimdall-frontend when flashing.
At some point after this I must have turned power off to get out of download mode and then could never turn the device on after.
I ordered a USB jig from Amazon and tried the USB jig method but that did not make any difference to the problem
Is there any thing else for me to try? If not, is Mobile Tech Videos JTAG service my best bet?
Thank for your help and patience with a noob.
What instructions did u follow to do this operation? I think its interesting people think they'll get more help if they put Noob on the page somewhere. "I'm a noob." I'm gonna try that with the IRS next tax year. "Sorry but I can't file this year.". " why not sir?". "Oh. I'm noob at it.". "Oh **** really?! Nmind then its all good. No need to file."
Sent from my SGH-I777 using xda premium
Make sure your phone not missing its motherboard.
One thing I see wrong is jvu, that's not a firmware for this phone
Sent from my SGH-I777 using Tapatalk 2 Beta-5
USB Jig not working is never a good sign....
Looks like you flashed some i9000 firmware. Depending on how far the flash went, you may be bricked to the point of needing a JTAG repair. I suggest MobileTechVideos, they've had good reviews.
[Solved] Samsung Galaxy S2 SGH-I777 wont turn on
I finally decided to take the device back to AT&T as it was under warranty. It turns out the problem was a dead battery! It was a shocker to find out that this device will not turn on if the batter is dead (or not installed) even if the power is plugged in. Can any one explain how this is possible and why Samsung chose such a questionable design? It seems to means that to troubleshoot a dead phone one must have a working spare batter!
farrukhnajmi said:
I finally decided to take the device back to AT&T as it was under warranty. It turns out the problem was a dead battery! It was a shocker to find out that this device will not turn on if the batter is dead (or not installed) even if the power is plugged in. Can any one explain how this is possible and why Samsung chose such a questionable design? It seems to means that to troubleshoot a dead phone one must have a working spare batter!
Click to expand...
Click to collapse
Or a charger nearby...
Sent from my SGH-I777 using Tapatalk 2 Beta-5
I've had some issues if my phone dies I just can't get it back on yet either...
I've found that if I pull the batt plug in the usb put in the batt and go into the 'forced upload mode' (as long as I'm able to still get it that far I can bring it back)
the problem I have is that sometimes it seems like it goes into this mode, and then restarts... after a while i'm able to get it to stay in this mode, and then i believe it is able to charge the battery;
I don't know what the deal is, I tohuhgt that charging while device off was now enabled (I believe before if the device was so dead it couldn't load a kernel it couldn't charge or something like that)
anyway; i thought that was in the kernels maybe it's not maybe i need to use something else, maybe our problems are unrelated -- my best advice ... try to get it into downloader (I have a kindle Fire charger that is 5v 1.8a or so, more than the phone needs but I stick it on there and then fight it off and on for sometimes 2 days...) it's *#$(# annoying I can tell you that -- but it ain't quite bricked ... Good luck broseph.
i have a htc amaze i unlocked from htcdev, and install recovery, i was trying to get s-off via wire trick and i attempt many times(like 14 )
and then when i try again the phone just die, i have a spare battery`s ( 3) i change batteryes and nothing i pull battery and nothing and even with usb coneccted to computer nothing not even the l.e.d light come on,, its totally dead,, please help me what i can do i search unbricked amaze but no solution :crying::crying::crying:
I was going to say maybe your recovery was shot but if you're swapping new charged batteries and still nothing, possibly a static discharge from the wire trick?
have you tried the RUU exe? to get you back to stock?
pandemoniumsax said:
i have a htc amaze i unlocked from htcdev, and install recovery, i was trying to get s-off via wire trick and i attempt many times(like 14 )
and then when i try again the phone just die, i have a spare battery`s ( 3) i change batteryes and nothing i pull battery and nothing and even with usb coneccted to computer nothing not even the l.e.d light come on,, its totally dead,, please help me what i can do i search unbricked amaze but no solution :crying::crying::crying:
Click to expand...
Click to collapse
With a charged battery hold down the power button and down volume button, see if it boots into bootloader.. if it does, your amaze is far from bricked. I remember the s-off tool getting some sort of a backup file made, some command you can use in the tool that will put it back into the stock boot sequence- I can't find it now, but I know it is there.. try what I suggested above, and look/read all you can on the s-off tool, I definitely remember them having something for that, but I'd like to know you're putting some work into finding the answer rather than having others do it for you..
andy55 said:
I was going to say maybe your recovery was shot but if you're swapping new charged batteries and still nothing, possibly a static discharge from the wire trick?
have you tried the RUU exe? to get you back to stock?
Click to expand...
Click to collapse
thanx for you response,, but yes i did try RUU and no luck,, the phone is completely dead,, no one single light come on :crying:
Silentbtdeadly said:
With a charged battery hold down the power button and down volume button, see if it boots into bootloader.. if it does, your amaze is far from bricked. I remember the s-off tool getting some sort of a backup file made, some command you can use in the tool that will put it back into the stock boot sequence- I can't find it now, but I know it is there.. try what I suggested above, and look/read all you can on the s-off tool, I definitely remember them having something for that, but I'd like to know you're putting some work into finding the answer rather than having others do it for you..
Click to expand...
Click to collapse
thanx so much for reply,, yes i try to boot into bootloader but... nothing i swap batteries fully charged, but it doesn`t do absolutly nothing,, no one single blink on screen or led light, i also put out the battery and conect usb to computer holding power and nothing,plug it to wall charger for around 1 hr then take out battery ,put it back with no luck
Ive never heard of a bricked amaze... but it sounds like you may have one
Sent from my SGH-T999 using xda premium
if it happened during your attempts at the wire trick, then I'll say you shorted something, or hit the wrong terminal, but something hardware related. Still have warranty? Time to play dumb and take it back to the store
SOLVED!!!!
Well thanx you so much for all your reply`s!!! after i did everything in the post and 9 hrs of NO luck,, i decide to open my amaze and with a small flat screwdriver i lift the "INSIDE BATTERY" (a small battery that looks like a clock batt) just a little bit enoguh to sperate it from the board,, leave it like that for around 2 mins and then i put it back in place and yoohhooooooo!!!!!!! it turns on again im able to get into bootloader,,, now to get sim off again,,
P.S:: yes the phone turns completely off with no signals of life when i was doing the wire trick so maybe like andy55 said i touch wrong terminal o something,,, hope this help somebody thanx so much.......:victory::victory::victory:
Thread moved to Q&A section.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Didn't we go to different schools together?...Coffee Bean!
Sent from my HTC One X, using XDA Premium.
pandemoniumsax said:
Well thanx you so much for all your reply`s!!! after i did everything in the post and 9 hrs of NO luck,, i decide to open my amaze and with a small flat screwdriver i lift the "INSIDE BATTERY" (a small battery that looks like a clock batt) just a little bit enoguh to sperate it from the board,, leave it like that for around 2 mins and then i put it back in place and yoohhooooooo!!!!!!! it turns on again im able to get into bootloader,,, now to get sim off again,,
P.S:: yes the phone turns completely off with no signals of life when i was doing the wire trick so maybe like andy55 said i touch wrong terminal o something,,, hope this help somebody thanx so much.......:victory::victory::victory:
Click to expand...
Click to collapse
The battery you lifted is likely the motherboard battery that keeps the Bootloader's information in memory so removing it is the lowest level reset you can do on a computer/phone. To reset a BIOS password for example this is the way to do it when you don't know the password.
And after that, cool, yet another way to unbrick an Amaze!
Sent from my HTC_Amaze
Hi friends
Iv been a long time reader on xda forums and have always found answers to my queries.
My brother tried flashing a rom but unfortunatley he flashed the wrong rom for his device which resulted in his phone to become hard bricked. no download mode or recovery mode. been doing some reading on the forum and it seems that i might be in for a chance to revive the phone with the UnBrickable SD necromancy mod http://forum.xda-developers.com/showthread.php?t=2023069 thanks to Adam. i have followed the steps which he has outlined, iv disassembled the phone, flashed my sd card with the image file and placed it into the phone. Now this is where im stuck. do i need some sort of a jig to power on the phone or can i use a usb cable attached to my laptop for power? also does the battery have to be connected? iv tried the above but im not getting any response it seems. i short the resistor with tweezers and let go after a couple of seconds from pressing the power button but no response.
i would have posted this in the above link but my post count is low
can someone please point me in the right direction
thanks
How would any operation be possible without a connected power source? Rig the battery to the motherboard before you start, otherwise nothing could happen. The process sounds like a desperate long shot to me, but you've got nothing to lose I suppose.
boomboomer said:
How would any operation be possible without a connected power source? Rig the battery to the motherboard before you start, otherwise nothing could happen. The process sounds like a desperate long shot to me, but you've got nothing to lose I suppose.
Click to expand...
Click to collapse
sorry i guess i didnt explain myself properly. ofcourse i will be needing a power source, i just wanted to ask if my normal usb cable hooked up to my laptop sufficient enough or would i need a rig.
okay im going to try and rig the battery to the mother board and see what happens, i dont need the usb cable attached in this case do i?
Thanks in advance for any help...
Recently my phone bricked, out of the blue. I rooted it and flashed the most recent release of TWRP (I don't remember the utility I used) and tried (and failed) to gain S-OFF with lazypanda and moonshine. After flashing the stable CM10 release and realizing the touch screen did not work, I found a ParanoidAndroid release that I wanted to try (http://forum.xda-developers.com/showthread.php?t=2373565). I flashed it from recovery and it worked great for around a week, then one morning it just bricked. Before that, I had rebooted it many times each into recovery and bootloader and did a couple full reboots. I had also fully powered down and back up a couple of times as well. However, that morning I powered down the phone and it has not powered up since. I began the power down on the AC charger, and removed the charger a few seconds after the screen went black; the buttons were still lit up. It does not respond to any button combination other than having a PC recognize it as a QHSUSB_DLOAD device. I have tried the LazyPanda unbrick method, PblClear, and (against all hope) an RUU, none successful. At this point, I am forced to concede that I must take my phone to Sprint and have it replaced under TEP...unless someone has a solution?
Again, quick details - brick occurred after a week of full and non-buggy operation. Not the result of a botched S-OFF attempt as far as I know, though I did try to gain S-OFF with 2 different utilities, failing both times. Removed power cord (AC Charger) while powering down; LED does not light up, will not respond to any button combination. Mounts as QHSUSB_DLOAD device.
Thanks again for taking your precious time to help me! :laugh:
dadrumajor said:
Thanks in advance for any help...
Recently my phone bricked, out of the blue. I rooted it and flashed the most recent release of TWRP (I don't remember the utility I used) and tried (and failed) to gain S-OFF with lazypanda and moonshine. After flashing the stable CM10 release and realizing the touch screen did not work, I found a ParanoidAndroid release that I wanted to try (http://forum.xda-developers.com/showthread.php?t=2373565). I flashed it from recovery and it worked great for around a week, then one morning it just bricked. Before that, I had rebooted it many times each into recovery and bootloader and did a couple full reboots. I had also fully powered down and back up a couple of times as well. However, that morning I powered down the phone and it has not powered up since. I began the power down on the AC charger, and removed the charger a few seconds after the screen went black; the buttons were still lit up. It does not respond to any button combination other than having a PC recognize it as a QHSUSB_DLOAD device. I have tried the LazyPanda unbrick method, PblClear, and (against all hope) an RUU, none successful. At this point, I am forced to concede that I must take my phone to Sprint and have it replaced under TEP...unless someone has a solution?
Again, quick details - brick occurred after a week of full and non-buggy operation. Not the result of a botched S-OFF attempt as far as I know, though I did try to gain S-OFF with 2 different utilities, failing both times. Removed power cord (AC Charger) while powering down; LED does not light up, will not respond to any button combination. Mounts as QHSUSB_DLOAD device.
Thanks again for taking your precious time to help me! :laugh:
Click to expand...
Click to collapse
PM XDA member Zarboz regarding JTAG, which may be just what you need to resurrect your phone.
Sent from my EVO using xda premium
FinZ28 said:
PM XDA member Zarboz regarding JTAG, which may be just what you need to resurrect your phone.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thanks! What exactly would a JTAG do? I did some research but couldn't find a good answer. Is there an advantage to that over just bringing it to Sprint to replace it, or do you think they might not take it?
EDIT: I went through my research again; I guess I just didn't understand it the first time. So, a JTAG can access and write to any memory on the phone, especially the memory that is now unavailable due to messing up the low-level boot software?
I've run into a similar situation on a completely different phone. I have a nexus 4 on AT&T that's been running ParanoidAndroid without problems for many months (most recent update flashed about 3 day earlier) that just wouldn't turn on one morning. The only indication it's alive at all is that it shows up as QHSUB_DLOAD / QDL mode when connected to the computer, and if I hold down the power button long enough to force it to restart the indicator light will briefly turn red for about a second. Your post caught my attention because almost no one else runs into this situation other than when they're flashing something wrong to the phone. Perhaps there's a bug in ParanoidAndroid that's responsible? (It's the only common element I see so far.)
Anyway, most every unbrick tool I can find expects you at least can access the storage to rewrite bootloaders, etc. The only thing I've found so far that will talk to the Qualcom chip in this mode is a perl script that still doesn't manage to get me out of this mode and to a state where the other tools can take over. JTAG may be my last resort. If you're considering a JTAG service, you should be aware that it involves taking apart the phone and in some cases soldering temporary leads to the circuit board. If you have any warranty style replacement options, you'll likely have to choose between those or the JTAG route.
iconoclastnet said:
I've run into a similar situation on a completely different phone. I have a nexus 4 on AT&T that's been running ParanoidAndroid without problems for many months (most recent update flashed about 3 day earlier) that just wouldn't turn on one morning. The only indication it's alive at all is that it shows up as QHSUB_DLOAD / QDL mode when connected to the computer, and if I hold down the power button long enough to force it to restart the indicator light will briefly turn red for about a second. Your post caught my attention because almost no one else runs into this situation other than when they're flashing something wrong to the phone. Perhaps there's a bug in ParanoidAndroid that's responsible? (It's the only common element I see so far.)
Anyway, most every unbrick tool I can find expects you at least can access the storage to rewrite bootloaders, etc. The only thing I've found so far that will talk to the Qualcom chip in this mode is a perl script that still doesn't manage to get me out of this mode and to a state where the other tools can take over. JTAG may be my last resort. If you're considering a JTAG service, you should be aware that it involves taking apart the phone and in some cases soldering temporary leads to the circuit board. If you have any warranty style replacement options, you'll likely have to choose between those or the JTAG route.
Click to expand...
Click to collapse
Just an update - I went to Sprint, and they agreed to replace the phone...waiting on it at the time of writing, but I will be starting from scratch. I plan to unlock the bootloader and root but not try for S-OFF as TWRP does have a way around it...and I WILL be staying away from ParanoidAndroid, although I love their ROM. Too bad...I just don't want another paperweight on my hands!
-EDIT- iconoclastnet: do you remember what circumstance the phone was in when it bricked? Like, on the charger, off the charger, turning on or off as it was plugged in/unplugged? Because I was unplugging mine just as it was powering down (not a reboot) and that's when it would not turn back on.
dadrumajor said:
-EDIT- iconoclastnet: do you remember what circumstance the phone was in when it bricked? Like, on the charger, off the charger, turning on or off as it was plugged in/unplugged? Because I was unplugging mine just as it was powering down (not a reboot) and that's when it would not turn back on.
Click to expand...
Click to collapse
Sorry for the delayed response, I was out of town for a couple of weeks and didn't notice your reply until now. Anyway, just for the record...
The notification led was indicating that the battery was about to run out (yes, I set a custom notification color for very low battery). It appeared to finally give up and shut off just moments before I reached the charger. So, I plugged it in and let it charge over night like usual, except the next morning it wouldn't turn on or respond to anything. At first I thought that the battery might not have charged for some reason, so I switched to a wireless charger because it has a charging/full indicator led on the charger itself, and confirmed a fully charged battery. Plugging it into the computer revealed the QHSUB_DLOAD / QDL mode status. I still haven't been able to get it out of that mode. At this point I'm really more interested in recovering the data from it than whether or not the hardware works normally anymore.
As for Paranoid Android, I've been using it successfully on a couple of other devices (both before and since the brick incident) and haven't had any problems with it, so it may be a complete coincidence. I'm at a loss for a good explanation though.
The issue was with TRIM not being removed from some early 4.3 ROM builds, which caused the bricks. It was discussed in some of the ROM threads. Had nothing to do with whether a phone was S-on or S-off.
Sent from my HTC EVO 4G LTE
This morning I got in my car and plugged my phone in, turned on Waze and drove to work which everything was fine. I started to do some testing on my phone at work which was killing the battery so I plugged it in, but the light did not appear for charging. I tried plugging it into two different computers, wall outlet, and different cords. I tried a co-workers phone on my cord and his started charging with no problems both connected to the PC and wall outlet. I cleaned the USB port on the phone thinking their maybe some dirt and build up in there, but still no love. Tried simulating a battery pull, flashing a ROM, and doing a restore...again no love. So I am guessing either the battery or the port is bad, even though the cable clips into place and is not loose.
My question I guess is: I have insurance on the phone, but do I need to RUU the phone in order to get the work done or will Sprint not care? I don't want to RUU and not be able to unlock and root again, but at the same time....I need a working phone. Also, if I missed something in my troubleshooting that someone has had success with for the same issue, please let me know.
Here is an early Thank You for those that may have suggestions or advice.
bdiddled said:
This morning I got in my car and plugged my phone in, turned on Waze and drove to work which everything was fine. I started to do some testing on my phone at work which was killing the battery so I plugged it in, but the light did not appear for charging. I tried plugging it into two different computers, wall outlet, and different cords. I tried a co-workers phone on my cord and his started charging with no problems both connected to the PC and wall outlet. I cleaned the USB port on the phone thinking their maybe some dirt and build up in there, but still no love. Tried simulating a battery pull, flashing a ROM, and doing a restore...again no love. So I am guessing either the battery or the port is bad, even though the cable clips into place and is not loose.
My question I guess is: I have insurance on the phone, but do I need to RUU the phone in order to get the work done or will Sprint not care? I don't want to RUU and not be able to unlock and root again, but at the same time....I need a working phone. Also, if I missed something in my troubleshooting that someone has had success with for the same issue, please let me know.
Here is an early Thank You for those that may have suggestions or advice.
Click to expand...
Click to collapse
Hey bud. First thing I would do is flash the latest stable TWRP for the phone. Then boot to recovery and see if it will charge.
If not, try flashing a stock kernel and see if that fixes the issue.
If it still has problems, I would be willing to bet it is hardware related be it the board, port, or battery.
If you are S=OFF, you will be able to root and unlock just fine. I don't know the carriers policies, but it's always safe to be RUU if you intend to do a Insurance claim. Make sure all your internal memory is backed up prior to flashing a RUU.
I found out the usb port on the phone is bad, but if I plug it in halfway the phone will charge. Thanks for the response and suggestion neo.
bdiddled said:
I found out the usb port on the phone is bad, but if I plug it in halfway the phone will charge. Thanks for the response and suggestion neo.
Click to expand...
Click to collapse
I've had that problem a few times too. Followed these instructions (found somewhere else) and it's corrected it every time:
1. Power phone off
2. Put on charger for at least ten minutes (does not appear to be charging, but that was the instruction)
3. Hold both the volume up and power buttons at the same time for at least two minutes (phone goes into kind of a boot loop)
4. Release both and phone reboots and charging works again
For me it fixed the "messing with the USB plug"
At least worth a try.
tlarm said:
I've had that problem a few times too. Followed these instructions (found somewhere else) and it's corrected it every time:
1. Power phone off
2. Put on charger for at least ten minutes (does not appear to be charging, but that was the instruction)
3. Hold both the volume up and power buttons at the same time for at least two minutes (phone goes into kind of a boot loop)
4. Release both and phone reboots and charging works again
For me it fixed the "messing with the USB plug"
At least worth a try.
Click to expand...
Click to collapse
I have not heard of this one before. I will give this a try, see what happens and report back. Thanks.
tlarm said:
I've had that problem a few times too. Followed these instructions (found somewhere else) and it's corrected it every time:
1. Power phone off
2. Put on charger for at least ten minutes (does not appear to be charging, but that was the instruction)
3. Hold both the volume up and power buttons at the same time for at least two minutes (phone goes into kind of a boot loop)
4. Release both and phone reboots and charging works again
For me it fixed the "messing with the USB plug"
At least worth a try.
Click to expand...
Click to collapse
Unfortunately this did not work for me, but thanks for the suggestion.
bdiddled said:
Unfortunately this did not work for me, but thanks for the suggestion.
Click to expand...
Click to collapse
Sorry that didn't work. I always hate giving up, especially when it's usually a mess I've caused. Hahaha but anyway, if things are straightening out when I have issues, I go back and flash the stock android rom, I'm on Verizon and use the deodexed one in another post on here. Seems as though using the rom designed for the phone cures a lot of ills (imagine that). Again, unless your set on sending it back (personally I hate the hassle of that) I'd give that a try too along with doing the button holding thing too if just flashing the rom doesn't correct it. Good luck whichever you decide!
tlarm said:
Sorry that didn't work. I always hate giving up, especially when it's usually a mess I've caused. Hahaha but anyway, if things are straightening out when I have issues, I go back and flash the stock android rom, I'm on Verizon and use the deodexed one in another post on here. Seems as though using the rom designed for the phone cures a lot of ills (imagine that). Again, unless your set on sending it back (personally I hate the hassle of that) I'd give that a try too along with doing the button holding thing too if just flashing the rom doesn't correct it. Good luck whichever you decide!
Click to expand...
Click to collapse
Well I ran an RUU yesterday and had no luck, until I found plugging it in halfway got it to charge. I have tried everything that I can think of along with neo and your suggestions, but the port is just bad. So I am hoping it will hold off until the end of the month when the m9 comes out and I am able to upgrade. So I will ride it out till it completely stops charging or I get a new phone. I do appreciate your suggestions and help though.
bdiddled said:
Well I ran an RUU yesterday and had no luck, until I found plugging it in halfway got it to charge. I have tried everything that I can think of along with neo and your suggestions, but the port is just bad. So I am hoping it will hold off until the end of the month when the m9 comes out and I am able to upgrade. So I will ride it out till it completely stops charging or I get a new phone. I do appreciate your suggestions and help though.
Click to expand...
Click to collapse
If you have insurance they should cover that... Also if your have Verizon the extended warranty may cover it.
TapPed fRom mY HTC OnE mAx