Related
Something seems a little off with my Evo, I recently noticed within the last day or so that it doesn't seem to want to charge correctly. What I mean by this is I have to wiggle and play with the cord to get it to seat correctly and actually charge the phone. I have this problem with the original cable and both after market cables I purchased (all of which are the proper cable and were specified to work with this phone).
Has anyone else had this problem? Does anyone know of a quick work around/hack/fix? I would prefer to not take my phone into Sprint if I don't have to as unrooting and then rooting the refurb or whatever I end up with would be a pain in the arse.
bump
Followed the unroot guide and I will be taking my phone into the shop today... We'll see what happens.
good luck, known problem with the evo.
This is common with the Evo. According to my Sprint store it is a known problem.
Not bad Sprint
I unrooted my phone completely, I was happy to see that unrevoked forever has an S ON tool. Then took out my SD card before rebooting into the stock ROM and put in another sdcard. Then went to the store and told them my issue. They came back and said they don't have any Evo's in stock but would call me once they do. It was probably one of my better experiences in dealing with Sprint.
Can anybody help me out with this? I've already searched but haven't found a clear cut answer on what to do.
For a while, I've had random events that cause my HTC Evo (running the latest stable release of CM7) cause my phone to suddenly show the "HTC Evo 4G" white screen, then go black and vibrate 5 times while having the green LED on, which never lets me do anything until I pull the battery out and start it up again. It used to only happen when I did specific things, like whenever I tried using Google Goggles at the store (and had to go through all the trouble of disassembling my 3 layer protective case just to pull the battery again). It even happened again yesterday when I was trying to use Goggles on a specific item, but it has happened before in other events since then, like when I was browsing my phone's running applications menu, or even one time when I was simply browsing the internet on it.
I've been taking steps to try and fix it, but I think it's been getting worse. I tried downloading CM7 and Google Apps again to flash on the phone to see if it fixed anything. I tried doing this again, but clearing the data and cache this time. I tried flashing the latest CM Recovery (since I stayed with 2.5.x.x for as long as I could remember), and I'm pretty sure it's gotten worse. There's points where I get to the CM7 boot animation and the phone then does the white screen and five vibrates again, and just a moment ago when I was sure I finally solved it after clearing data and cache, while filling out my Google account info, it happened again and I was greeted once again by that horrendous white screen and the five vibrates.
Now I don't know what to do. I still have S-OFF, but I have no plans to unroot. Can anybody think of suggestions? I've already tried Googling and haven't gotten anything useful enough to help me so far.
EDIT: I guessed it would help if I was a bit more specific. This started happening about two or three weeks ago after I tried using Goggles for the first time in ages. Since then, I've had this issue coming back over and over. It also puzzles me how Goggles usually works completely fine when I'm at home but causes the phone to go black and vibrates 5 times whenever I'm at a store.
Also, right now, I re-downloaded CM7 and Gapps from the CM mirrors instead of simply reusing the ones that ClockworkMod had saved for me already. I hope this somehow makes a difference.
Also, last edit, if I manage to solve this somehow, I'm going to definitely post the answer to what I did in case anybody else out there is having the same issue.
EDIT 2: Welp, re-downloading CM7 and flashing again didn't do anything to fix the problem. I'm going to try another ROM to see if the problem persists. I really want to stay with CM7, though.
Did you wipe everything? Cache and so on ect....?
I wiped everything and I'm still having the issue.
I also caved and I'm going to unroot because the retards over at the Sprint repair center refuse to look at it otherwise. I got my hopes up after hearing on places like XDA or the CM forums about how Sprint didn't care about rooted phones, but I guess the Sprint guys in my area do. I'm currently downloading unrevoked forever son and PC36IMG right now.
I'm just hoping I can get a new Evo after this, because there's a chance I could lose root forever after doing this. But I'm so certain it's a hardware problem.
SirSigma said:
I wiped everything and I'm still having the issue.
I also caved and I'm going to unroot because the retards over at the Sprint repair center refuse to look at it otherwise. I got my hopes up after hearing on places like XDA or the CM forums about how Sprint didn't care about rooted phones, but I guess the Sprint guys in my area do. I'm currently downloading unrevoked forever son and PC36IMG right now.
I'm just hoping I can get a new Evo after this, because there's a chance I could lose root forever after doing this. But I'm so certain it's a hardware problem.
Click to expand...
Click to collapse
Why would you lose root "for ever"?
Just curious ....
Sent From The Tree House Out Back!
I had the same exact issue with my Evo over the past 2 weeks. But I never use Goggles and run MIUI pretty much exclusively. I was never able to fix it and it just got worse. I unrooted and still have the same problems.
I notice it happens on 3g data, I can't remember when it happened on wifi.
I am selling mine back to Sprint tmrw and using my upgrade to get the Nexus S for$50. Then hoping the Evo 3D comes out within 30 days.
Sent from my PC36100 using XDA Premium App
I took it back to Sprint today, and after being treated like a second class citizen for rooting over and over, they managed to somehow fix the random reboots, but have initiated the OTA update for me. Now I'm sitting here with it and it's asking if I should install it now or later.
I'm hesitant because I tried to unroot earlier, and since then, the technician at Sprint said that it wasn't really unrooted or something (I remembered using unrevoked forever last year when I rooted). I'm scared that maybe I'll lose my chance at being able to root again if I accept the update or not. I'm also scared if I won't be able to get full root from here.
EDIT: SON OF A *****. I can't believe this. I applied the OTA update like a good boy and everything, and then the phone starts boot looping randomly again. This is the last straw. I'm going to go back to Sprint tomorrow and be more in-your-face about this problem. I'm through letting them treat me like **** just because I rooted my phone once.
I have a similar problem.....
My problem is random. My phone will go into constant reboot mode until I pull the battery out for 10 minutes. Just pulling the battery and putting it back does not help.
I also noticed that I am losing GPS signal occasionally. It is random too. The GPS will come on and work for about 5 minutes then just lock up. I have to reboot to get it working again and there is no rhyme or reason as to when it will stick (or wont) or how long it will last. It may work for 3 days and then not work a lick for 3 days.
The local Sprint store replaced the back red portion of my phone (the part with the camera lens and kickstand) stating it was an GPS antenna problem. I got 30 secs outside the store and tried the GPS....same problem. I went back into the store and showed them and they tried to convince me I needed AGPS on as well. AGPS always worked but is not as accurate as the satellite GPS. The repair shop refused to do more or order a replacement. I just got scammed out of $35.00 cause nothing is fixed.
I got so pissed, I called Sprint. They were terrific. They refunded the $35.00 the repair center charged me of the repair (the rip-off repair) and agreed to send a replacement phone. Awaiting arrival of the replacement but they are back ordered...so, maybe, I'll get a new phone instead of a refurb.
Long story short...I don't know what is causing your reboots. Mine could not be solved by software changes. My phone was rock solid until around a month ago. Then the GPS dropouts and reboots became more frequent until they became unlivable. I think you have a bad device and would seek replacement.
I had the same problem with mine about a month ago. It happened once about a month before that and then a month ago started happening a lot. I finally narrowed it down to how "hot" it was (body temperature in this case). So basically any time that I was in the car it happened. I was able to unroot (you have to make sure you to s-off on) and put a stock rom on it, and take it in with it happening. They took it for an hour and said they had not seen any issues. I finally convinced them and the replaced it with a refurb. I'm okay as long as it works, but it makes me wonder what happened. When I first got it I used fresh for about a week and then went to CM and was on it the rest of the time. I used an SBC kernel starting around the same time and am thinking maybe that had something to do with it... Just as a precaution I'm staying away from SBC kernels.
If I were you I would just go to the store and get a replacement if you can otherwise if it's like mine you won't be able to count on it working...
Good luck
I would by no means consider myself a NOOB, as no one ever wants to be a newb. Although i have bricked and burned up a few devices. I have been a member of XDA for some quite some time. I started with an HTC HD2, i was dual booting windows phone 7 and gingerbread. UltimateDroid, to this day is and was still my favorite ROM of all time. Still wonder what happened to that guy. I ended up burning up that phone so much so that it would lock up and i would have to put it in the freezer for 10 minutes before putting the battery back in and turning it on. From there i graduated to an HTC sensation. Phone was awesome, i was running an early version of the InsertCoin rom, until i was on skype and dropped the phone. For some reason upon dropping the phone, it never turned on again. I then had a samsung galaxy captivate and was dissatisfied to find out i could only get 2g on tmobile based on the antenna in the phone not being able to recieve tmo's 3g signal. From there i went on to an LG G2x, what a great phone. I was using the Tsugi Rom with the oyusame overclocked, stock voltage kernel. I got kind of sick of the phone because i had flashed every new rom that came out and it just started to get redundant for me, that was when i got my Galaxy S2 Hercules. I love this phone but alas, in my continued need to root and flash the crap out of my phone with all XDA's latest and greatest goodies, i flashed a rom that didnt boot. (This was most certainly my fault for NOT THOUROUGHLY READING THE INSTRUCTIONS) so in discovering this with only a few minutes to spare before work, i opened up odin before work and grabbed what i thought was clockwork recovery and flashed it. This was not clockwork recovery and upon and flashing i recieved what every modder on here is terrifed of. QHSUSB_DLOAD followed by that god awful windows device driver error noise. Pissed off driving to work with no phone, i immediately ordered a USB jig off amazon for $3.50 cents plus an addition $35.00 to overnight ship it to my house. So impulsive to fix my phone, i even stopped at radio shack and bought myself a pack of 100k ohm resistors to try and make the part myself. Several broken usb cables, and my kitchen table looking like a tweekers wet dream later i had no resolution. I woke up the next morning tracking my usb jig every half hour and was very excited to recieve it, goign as far as to tell my wife that i would no longer be going to get her coffee or visiting her parents as I would be pre-occupied with my phone for a while. Murphy's law however saw otherwise as this did not fix my issue either. I of course knew that if i called T-Mo the insurance would not cover this. So i started calling local cellphone repair shops. After about the fifth place i called, i realized that most of those people are lightyears behind whats happening on here and found that when i tried to talk tech they would sit there and scratch their heads. Out of options, I called the 800 number for samsung on the label underneath the battery. I very openly and honestly explained to the lady that i had rooted my phone, installed a custom recovery and was flashing custom roms. I then explained something went terribly wrong and the phone does not respond at all. I also explained the QHSUSB_DLOAD problem. I believe this explanation went a little beyond they types of calls she was used to recieving. She did however explain that Samsung provides complimentry re-flashes of bricked phones as long as there is no hardware damage done to the device. She then e-mailed me a ups label with shipping paid , and my phone is in the process of being repaired. I did buy yet another HTC sensation to get me by for the 2 business day shipping to samsung, the 7 business day evaluation and repair process, and another 2 days for me to get it back. I hope this can help anyone who has made the same mistake, and moreso i hope this can show others how rushing, being careless, and not reading the instructions can come with HEAVY consequences. Although all should work for me just fine, i still had to spend $150 on a used sensation with a cracked screen, and the nearly 2 weeks of downtime i am without my GS2.
___________________________________________________________________________________________________________________
Devices: HTC HD2(DEAD), HTC - Sensation(DEAD) Samsung Captivate(SOLD) LG G2X(SOLD) Galaxy S2 T989 (OUT FOR REPAIR) HTC Sensation (Were keeping that stock at least until i get the glass replaced and my GS2 back) LG G2X (Waiting to warranty my fiance's sensation to get it back)
Sent from my SGH-T989 using Tapatalk 2
LuniZ916 said:
I would by no means consider myself a NOOB, as no one ever wants to be a newb. Although i have bricked and burned up a few devices. I have been a member of XDA for some quite some time. I started with an HTC HD2, i was dual booting windows phone 7 and gingerbread. UltimateDroid, to this day is and was still my favorite ROM of all time. Still wonder what happened to that guy. I ended up burning up that phone so much so that it would lock up and i would have to put it in the freezer for 10 minutes before putting the battery back in and turning it on. From there i graduated to an HTC sensation. Phone was awesome, i was running an early version of the InsertCoin rom, until i was on skype and dropped the phone. For some reason upon dropping the phone, it never turned on again. I then had a samsung galaxy captivate and was dissatisfied to find out i could only get 2g on tmobile based on the antenna in the phone not being able to recieve tmo's 3g signal. From there i went on to an LG G2x, what a great phone. I was using the Tsugi Rom with the oyusame overclocked, stock voltage kernel. I got kind of sick of the phone because i had flashed every new rom that came out and it just started to get redundant for me, that was when i got my Galaxy S2 Hercules. I love this phone but alas, in my continued need to root and flash the crap out of my phone with all XDA's latest and greatest goodies, i flashed a rom that didnt boot. (This was most certainly my fault for NOT THOUROUGHLY READING THE INSTRUCTIONS) so in discovering this with only a few minutes to spare before work, i opened up odin before work and grabbed what i thought was clockwork recovery and flashed it. This was not clockwork recovery and upon and flashing i recieved what every modder on here is terrifed of. QHSUSB_DLOAD followed by that god awful windows device driver error noise. Pissed off driving to work with no phone, i immediately ordered a USB jig off amazon for $3.50 cents plus an addition $35.00 to overnight ship it to my house. So impulsive to fix my phone, i even stopped at radio shack and bought myself a pack of 100k ohm resistors to try and make the part myself. Several broken usb cables, and my kitchen table looking like a tweekers wet dream later i had no resolution. I woke up the next morning tracking my usb jig every half hour and was very excited to recieve it, goign as far as to tell my wife that i would no longer be going to get her coffee or visiting her parents as I would be pre-occupied with my phone for a while. Murphy's law however saw otherwise as this did not fix my issue either. I of course knew that if i called T-Mo the insurance would not cover this. So i started calling local cellphone repair shops. After about the fifth place i called, i realized that most of those people are lightyears behind whats happening on here and found that when i tried to talk tech they would sit there and scratch their heads. Out of options, I called the 800 number for samsung on the label underneath the battery. I very openly and honestly explained to the lady that i had rooted my phone, installed a custom recovery and was flashing custom roms. I then explained something went terribly wrong and the phone does not respond at all. I also explained the QHSUSB_DLOAD problem. I believe this explanation went a little beyond they types of calls she was used to recieving. She did however explain that Samsung provides complimentry re-flashes of bricked phones as long as there is no hardware damage done to the device. She then e-mailed me a ups label with shipping paid , and my phone is in the process of being repaired. I did buy yet another HTC sensation to get me by for the 2 business day shipping to samsung, the 7 business day evaluation and repair process, and another 2 days for me to get it back. I hope this can help anyone who has made the same mistake, and moreso i hope this can show others how rushing, being careless, and not reading the instructions can come with HEAVY consequences. Although all should work for me just fine, i still had to spend $150 on a used sensation with a cracked screen, and the nearly 2 weeks of downtime i am without my GS2.
___________________________________________________________________________________________________________________
Devices: HTC HD2(DEAD), HTC - Sensation(DEAD) Samsung Captivate(SOLD) LG G2X(SOLD) Galaxy S2 T989 (OUT FOR REPAIR) HTC Sensation (Were keeping that stock at least until i get the glass replaced and my GS2 back) LG G2X (Waiting to warranty my fiance's sensation to get it back)
Click to expand...
Click to collapse
Same thing happen to me the dreaded QHSUSB error when I bricked my exhibit2. I know how you feel.
Sent from my SGH-T989 using XDA Premium App
Lol. I bricked mt very first phone (the T989) the very first day i got it. I got it replaced for free with that 14 day gap thing that Tmo has. Got lucky. Ive never had a bad flash since.
Sent from my SGH-T989 using xda app-developers app
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
supraman89 said:
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
Click to expand...
Click to collapse
Stupid kies mini hard bricked my trusty vibrant... Luckily, t-mobile replaced it for free, but it was the horrible exhibit 1.
supraman89 said:
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
Click to expand...
Click to collapse
Yeah most people went through regular warranty exchanges, but from what the OP was explaining he's a very honest person and would have said that he rooted the phone therefore he would not be able to exchange it.
That's good that he's honest, but it would have been a lot easier to just do that and get the phone next day because TMobile is just going to send that phone back to Samsung and they'll do the exact same thing they're doing to his phone now
Sent from my SGH-T989 using xda app-developers app
This sounds exactly like something I would! Especially buying parts thinking I could fix it!!
I feel so at home on xda!!
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
U could a saved a ton of time and money by just saying ur phone stopped working. Cuz technically it did
Sent from my SGH-T989 using xda app-developers app
LOOOOOOL this made my day^^
I have my phone till two years now and i bricked it once by disconnecting by mistake while unlocking bootloader (yes i fell with my phone in the hand and lukily it only disconnected and didnt pull my laptop with it.
I had it fixed in a half hour^^
Greets
Sent from my Xperia X10 using xda app-developers app
Good to know thanks
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
My very first device was the Mytouch 3G on T-Mobile. Back then, it was maybe the 2nd Android phone to have even existed at that point.
Me, never being satisfied with anything stock and coming from a heavily modified blackberry, wanted to tweak the hell out of it.
Back then, it took a LOT more to root and flash, ESPECIALLY HTC Devices. There were no custom tools yet to root, and the only easy part was using CWM. You HAD to use adb commands to exploit to get root and even get CWM on the device at that point, but only AFTER downgrading it back to Android 1.5, but after that it was easy.
(I couldn't believe how fast and easy it was to root and flash on the T989 after having HTC devices up until last year)
Anyways, I somehow managed to get it CWM to boot (you had to boot into normal recovery after replacing update.zip with a CWM zip, and then flash the new update.zip file back then) and went to flash a ROM, and instead I flashed a zip, but the wrong ROM was uploaded by the OP, and what I had flashed as for the G1. It was literally only uploaded for all of maybe 2 minutes before he pulled the post down and uploaded the correct version.
I was the ONLY one who downloaded and flashed it within that 2 minute window.
Needless to say, I hated my life.
Now the funny part:
I was so paranoid back then about not letting T-Mobile know that I was rooted, that I literally bought a BRAND NEW Mytouch 3G (because you couldn't even find broken ones on ebay yet) and sold the broken one, which I bought the day before mind you, for $20. I wish I would have known that, back then, there were no counters on the MT3G. T-Mobile would have never known as it wouldn't boot.
:crying:
Flash forward to today, and IDGAF.
So I bought my Nexus on Craigslist about a month ago. Everything went smooth, but i noticed the phone would frequently think it was charging when not plugged in or not charging when plugged in. This was because the previous owner did not use the charger that came with it and presumably bent the Micro USB connection. Nothing my trusty razor couldn't fix, just bent that dude back int place. Worked like a charm. I knew i should replace the USB port... eventually.
A few nights ago, I noticed that while I was plugged in charging, my battery was draining even though the little battery lightning bolt was showing. I figured it just needed to be bent again. Didn't fix it. I must've stayed up all night trying to fix it, flashing new ROMs, factory resets, new kernals, plugging it into a computer, new cables, new chargers, new A/C ports... EVERYTHING. I caved and ordered a replacement USB port on eBay which arrived crazy fast. Upon replacing it.... the problem persisted. I've tried more cables, more ports, more ROMs, more kernals, and more resets.
Needless to say, I'm frustrated. Any input...?
EDIT: I'm on CM10 M2 with the stock kernal
Seriously, is this some kind of joke? Every day, a thread like this pops up... if it is legit, search for one of the many other threads with your issue, I passed two scrolling down the page to yours.
Sent from my Galaxy Nexus using xda app-developers app
Did you even read my post? I've spent two days scanning these boards for solutions. I've tried everything.
No, I didn't.
But I'm not making this up, again, I passed the big one on the way down to this one, it's a very common issue, and like I said to the other guy who just posted one of these threads, some say you can straighten out the port in your phone with a fine screwdriver-like instrument, or you need to order a new USb port + board and take your GalNex apart... Otherwise, with no warranty, I'd bail and get an entirely new and different phone, because this issue is unacceptable.
Oh... you could try a class-action suit. I also mentioned this to the others, I mean really, there are so many of you with this problem, I'll probably be one of them soon enough, may as well start the legal process now...
Sent from my Galaxy Nexus using xda app-developers app
Yeah I did all that, straightened the port, replaced the USB flex, and all that. I'm still under warranty, so my fingers are crossed that they can't tell that I was inside it. Otherwise, it's off to getting the charger that charges the batteries with a dock.
I had similar issue with my rooted GNex while I was running one the ROMs. I also search everywhere on this forum and Google but i couldn't find a solution. So I tried following steps and it worked for me.
1. Using twrp I reset battery stats
2. I wiped calvik cache and system
3. Instead of a flashing a newer zip I restored one of the Nandroid backups of the system.
After reboot I tested if my phone was behaving normal and certainly it was and I haven't had same problem since.
I don't know if there is a way but may be you can go through my post and I had mentioned same issue on this forum and didn't get a response from no one.
Sent from my Galaxy Nexus using xda app-developers app
I did restore to an earlier ROM, maybe I'll try some of my other backups. If that fails, I think I'll give unrooting, relocking and going to he stock ROM and give that a shot. It's a really frustrating endeavor, I've got to say. I will post an update after trying even more methods.
Just don't settle for battery docking, fight for that warranty. Although don't tell them you took it apart.
Sent from my Galaxy Nexus using xda app-developers app
Alright, so going back to stock, unrooting, relocking, and all that didn't fix the problem. I managed to squeeze a service ticket for my Samsung warranty. I'll be shipping it off later today, hoping they fix the issue free of charge. I hope they don't notice I swapped the USB flex, I don't want to end up paying money for repairs.
I'll post back here if I ever get any relevant info about the issue from Samsung. Thanks for the input, folks!
So I had purchased my HTC One M9 through their website (it guides you where to pay and see the price). I opted out of the warranty because I have never had an issue with any of their phones and I still try to convince people to buy them. Nonetheless, while I was in the middle of a phone call my phone had suddenly just up and died, which i thought to be weird since I waited to leave the house until it hit 80%. I have tried everything I could think of since I have done quite of my own tinkering on previous models. No computer it is plugged into recognizes its' existence. I have been able to hold down the buttons and get it into recovery but everything there fails. I contacted HTC and they told me to try and manually install the update rom but without finding a computer that sees it, there was no such luck. Their only other option they gave me was to send it in and pay $250 to have it looked at. When I bought it brand new it was damn near $800! I'm just wondering if anyone has had this problem or if it is in fact a hardware rather than software issue. I have never tried to unlock it or anything since it came unlocked from the factory. Story of my life...haha
Can you get into your boot loader? That might help your computer recognize the phone.