Howdy - I've had this problem with both my 001 and 004 Evo's.
After flashing a radio on the first one and a ROM on the other - charging no longer works. It works fine when the phone is off - but it won't connect at all to a computer or to the charger if on. I've tried 6 different chargers and multiple cords.
I found a solution earlier by flashing PC136 off the SD card and going back to stock. From there I rooted the phone using unrEVOked then reflashed into Savaged-Zen which went into a boot loop - as well as any other AOSP ROM I tried. The only ROMs that would flash and not boot loop are Sprint Lovers, VaelPak and other sense based ROMs.
Currently I'm on VaelPak and just installed the newest netarchy SBC kernel. Now the USB no longer works again. I reflashed PC136 and redid all of that and went back into VaelPak and the charging worked. As soon as I restored my apps through Titanium and reflashed any kernel, it no longer works.
TL;DR - In custom ROMs the USB port no longer functions when the phone is on. It works when it is off. How can I prevent/fix this?
try using a non-sbc kernel and see if charging works? that's the only thing I could think of
You know about the wide spread issues with the EVO's charging port in general correct? I've had to replace 3 phones at our company with that problem.
I don't think hes experiencing the charge problem as it charges fine without that kernel. Have you tried a different cable? I have had the charge problem but its always been the cable. I've been through 3 cables, maybe I'm just bandaiding the problem but it seems to charged like new with a fresh cable.
I've tried several different cables but just to be safe I bought a new one yesterday - no dice.
I'm going to redo everything step by step so I can figure out where this occurs. Am I really the only one that's had this problem? I know at least two other people that have had it but can't find anyone online.
Well - reinstalled VaelPak and now charging works so I do think it has something to do with the kernel.
My only problem now is the phone refuses to install -ANY- AOSP ROM. I've tried MIUI, one of the Virus, Evervolv, and SavagedMod. Any ideas?
Related
I got my Evo 3 days ago. So on the second day I rooted it/installed sprint lovers rom. Well AFTER i rooted the stock rom did the nandroid backup. Also when I bought the phone I was on firmware 3.26 so I had to update a lot of stuff to 3.29 and other things before rooting. So the problem is the phone will fully charge on the wall to usb charger but when I plug it into my computer it seems not to charge all the way, just halfway. So what I did was went back to stock rom when I rooted it. BUT I'm not sure if it's really back on stock rom fully because when I installed the Sprint Lovers rom it UPDATED my kernel/wimax/radio firmwares
So I want to get back my stock settings so I can see if it's something to do with this rom I installed.
Note: I wiped 3 things. The cache, BATTERY STATUS, and something else I forgot what it was called.
Update: well I'm using a app called "cellumap" it shows the battery percent. at 62% I took my phone off the wall to usb charger and plug my phone into USB mode. now it's at %64 in 5 mins. It just seems to be charging slow to me. I've had this phone for like 3 days so I really don't know the charging time it take for this phone.
What I'm going to do now is install nonsense custom rom and see if installing a new rom will also change my kernel/wimax/radio firmware because I think something fishy is going on with kernel firmware and my battery
Flashing a ROM won't update your radio or wimax.
Also, 2% in 5 minutes seems pretty normal to me.
Hey everyone,
So I have been having problems connecting my evo to my bluetooth fm transmitter for my car (I can't post links yet, but it is on amazon, the gogroove flexsmart x2) ever since I switched from cm6.1.2 to miui 12.31. The transmitter was working perfectly, and my phone would pair and connect to it flawlessly, however, when I switched to miui, it didn't work at all. It would just not connect, no matter what I did. So I tried switching kernels around, and none of them worked (I tried about 3 kernels on cyanogen before I switched to miui, and switching didn't cause any issues). So I decided to go back to cyanogen, yet my bluetooth didn't work when I restored to a nandroid backup. Bluetooth still wasn't working. So then I went into clockwork and wiped my data/cache and installed the latest cm6 and bluetooth worked. Excited, I installed all of my applications, got my settings right, and installed a different kernel. When I switched kernels to try out a savage one, my bluetooth wouldn't connect. Nothing would work to bring that back, so I deleted my data/cache again and got it to work. Everything worked fine, but I wanted a different kernel, so I tried putting on snap 7.6, and it won't work anymore. I am not entirely sure what to do. I can re-install cm6 by clearing my data/cache, but I want to know why I can't use any other kernels that worked previously. Any suggestions?
Recently, I posted on cyanogen forums, and someone said to use Calkulin's format all zip as well as clear davlik cache. That didn't wok. I also tried going onto a sense rom and installing a sense kernel which didn't work either. I'm not entirely sure what to do. The thing that bothers me the most, not that I can't be on a different kernel than the stock cm6 one, it is that I don't have the option to change, but I did before.
Thanks so much for any help!
Almost sounds like it may be a hardware problem. Most of the software fixes I would suggest you've already tried with no luck. Keep in mind hardware can fail.
spiicytuna said:
Almost sounds like it may be a hardware problem. Most of the software fixes I would suggest you've already tried with no luck. Keep in mind hardware can fail.
Click to expand...
Click to collapse
I would think that it is a hardware problem, but I am lead to believe it is something dealing with the kernel because when I am on a stock cm6 kernel, it works, but when I change the kernel, it fails.
EDIT: Also, would you recommend maybe unrooting my phone and completely resetting it?
i just received the newer evo with hardware 4 and gingerbread installed on it, i rooted the phone using the new root method and installed mikfroyo 4.62, the wifi is not connecting right or wont connect, ive tried at home, school, and a friends house, is there something i can change like wimax, NV, Pri, radios...just throwing stuff out there, but you know what i mean, anything like that, that i can change so wifi will work again??
Have you tried reflashing the rom? Did you install on a clean install?
Did you flash a custom kernel? Sometimes an incompatible kernel will mess with your wifi.
Sent from my PC36100 using Tapatalk
I have a similar issue that just occurred, I've had it working all until last week now any ROM I flash/restore will connect to wifi then immediately disconnect.
Any other thoughts?
same here then I wiped everything two times and flashed synergy RLS1 + godmode 3.0 rom and now its back. So maybe try that and let me know if it works for you or if it just worked for me.
sorry i thought i hit submit message like a weeks back lol, yeah i got it to work, i flashed a different rom and kernal then went back to the rom i like and it worked, weird, something must have not flashed write
Device: Desire GSM
I installed insertcoin 1.1.3 on monday and it seemed to have sorted the problems I had with crashing sense.
However I did have a problem with usb detection on win7 64 at one point. I had a demand for a scan pop up- this is something that occured frequently when my camera was still crashing. I cancelled the scan and Win7 sprung me a device error. That had not happened before.
I just unplugged/replugged and the issue was solved.
The next day I saw the 1.1.3 and 1.1.4 updates solved usb tethering issues. I figured why not try and updated, then flashed the kernel (without booting).
Result: windows won't recognize the device anymore, doesn't accept android usb drivers for it (the device returned an error). It is shown as unknown device in device manager. Furthermore, after trying to connect the card can no longer be mounted by the phone.
A restart sorts it, but it's still not very satisfactory. Does anyone have the same problem?
Did I flash the wrong kernel? It said bravo...
Meanwhile I'm going to go back to 1.1.2 and stay there...
Sounds like usb brick. A guide how to fix can be found here on xda.
TouchPaled from Oxygen with Transparent XDA App
Not a phone issue
Well I went back to 1.1.2, flashed a different kernel, flashed leedroid, then back to 1.1.2.. all of which gave no joy. Same issue exactly.
However finished my sick leave and it connects fine on my work pc.
So it's probably the cable and I'll check that tonight (was a bit too ill to crawl around the back of my home desk) and report.
(for those who found this by searching I guess RMD recovery is the USB Brick fix.)
No that's not the usb brick fix, it's a recovery. By using the search one can find a guide extra for usb brick.
TouchPaled from Oxygen with Transparent XDA App
So it turns out to be a faulty cable, and that is that.
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
Click to expand...
Click to collapse
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
gtdtm said:
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
Click to expand...
Click to collapse
I think SuperDuperWipe got it fixed. I had one lockup and one random reboot since using SDW, and it's been about a week. I consider that stable enough. I had forgotten I used the Viper ROM and needed to "clean the nooks and crannies".
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
Click to expand...
Click to collapse
Try to change the core aeroevan.. I used kernel aeroevan v15 to CM10(Chillybean) with a good result.