Hey guys
i recently flashed codename android 1.3.3 and i could no longer mtp host so i switched roms and still not dice i flashed every kernel and nothing is working does anyone know how to fix this or and i screwed. to be clear my phone still charges it just wont mount to transfer files. adb does not recognize that a phone is plugged in either
thanks in advance for all the help
Matt
Mine is doing this now as well following AOKP Build 23. I haven't bothered flashing anything else yet as I was doing preliminary research before work to try to find out exactly what happened and how I could fix it. (No answer yet).
Edit: I found a solution. It won't automatically turn on anymore, but I can turn it on manually under Settings > Storage. Problem fixed (for me anyway).
no idia??how can improve this
i tried that still not working is there any way to uninstall the drivers from the phone?
Had this problem after installing AOKP 23 too. Have to turn on manually.
Working now.
Could be that you have a faulty USB port. Many have reported about this here http://forum.xda-developers.com/search.php?searchid=15930021
Related
So I have been having some trouble lately. I'm running the latest versions of everything and have been having a few USB problems. First, my phone was mounting as a usb device even when set to charge only. Then, USB Debugging stopped working. I redid the entire thing, using the PC36IMG.zip that contains the image for the latest OTA and Radios and patching with Superuser. It worked for a while, then a couple days ago the charge only stopped working again. Now my Evo rebooted on its own while plugged in, something I've heard of but never experienced with any Android phone. After the reboot, USB Debugging stopped working again. Please, if anyone knows what I can do to fix this, please help. I'd be willing to give more information if needed. I'm fairly good at ADB, but can't seem to fix this problem. Thanks.
Bluetooth problem - need help
Here is my situation. I have a EVO 4G Rooted with rooted 3.29.651.5.
My phone's bluetooth paired perfectly with my car for several months.
Then I installed Vlingo and my bluetooth stopped working with my car. I uninstalled Vlingo and the bluetooth worked only sporadically. Since then I have tried almost everything I can and have searched for weeks to get this to work.
I have tried:
* complete wipe and reinstall of ota rooted rom
* reinstalled Vlingo tested, then unistalled again
* deleted and then restored backups of BrcmBlueToothServices 1.0 and Bluetooth Share 2.2
* deleted BrcmBlueToothServices 1.0 and Bluetooth Share 2.2 then flashed rooted ota rom to get clean copies back again (I hope)
* Unpaired my Evo from my car then paired them again.
* Upgraded to rooted 3.30.651.2n.
* Flashed a new King's Kernel #11 (2.6.32.24-king-hav-OcUv)
I know it is not my car as my wife as the same phone I have. I rooted it and except for the recent kernel change on my phone the only real difference is that I never put Vlingo on her phone. I can pair her phone perfectly with my car and it works great just like mine did before Vlingo.
I'm not an expert, my learning curve was huge to get to root and I have done a lot of reading to try to figure this out.
ANY help would be appreciated! I need my phone to work with my car as I'm on the phone a lot.
The kernels will break bluetooth on the CM builds.
The CM framework has been redone and there are few compatable kernels. Yes kings kernel will work, but not everything. Currently, there is no custom kernel (beside the stock CM kernel in each build) that will work and keep bluetooth working on CM roms
kthejoker20 said:
The kernels will break bluetooth on the CM builds.
The CM framework has been redone and there are few comparable kernels. Yes kings kernel will work, but not everything. Currently, there is no custom kernel (beside the stock CM kernel in each build) that will work and keep bluetooth working on CM roms
Click to expand...
Click to collapse
Thanks You very much for your response. Since my technical level is a little limited let me see if I understand. You are saying that my rooted stock ROM is a Cyanogen Mod Build. That ROMS made using this with stock kernels should work with Bluetooth, but if you use a custom kernel there could be a problem.
If this a correct understanding, the only problem is that I was using the stock kernel that came with the ROM and it was working fine for weeks. Then I installed Vlingo and the problem arose. I then unistalled Vlingo and the problem still persisted. Days later I then switched kernels in an attempt to fix the problem. I have the same problem regardless of which kernel I use.
Do you have a suggestion for a solution? Again, thank you.
bluetooth
nykbob said:
Thanks You very much for your response. Since my technical level is a little limited let me see if I understand. You are saying that my rooted stock ROM is a Cyanogen Mod Build. That ROMS made using this with stock kernels should work with Bluetooth, but if you use a custom kernel there could be a problem.
If this a correct understanding, the only problem is that I was using the stock kernel that came with the ROM and it was working fine for weeks. Then I installed Vlingo and the problem arose. I then unistalled Vlingo and the problem still persisted. Days later I then switched kernels in an attempt to fix the problem. I have the same problem regardless of which kernel I use.
Do you have a suggestion for a solution? Again, thank you.
Click to expand...
Click to collapse
i have the same problem did everything mentioned above, rooted my wife evo and mine my Bluetooth doesn't work on mine hers does, maybe the devs could make a backup flashable zip for Bluetooth and htc syn that would be great
Using rooted file manager, I can get to the bluetooth.apk and BrcmBluetoothServices.apk files. When I click on either one of them I get a message that asks:
"Replace Application
This is a system application. Do you still want to replace it?
All previous user data will be saved."
Question, If I say "OK" what does it replace with? Maybe replacing these two files will change things for me so I can get my BLuetooth function back again.
Any comments?
Nothing I have done has gotten my bluetooth function back again. I'm desperate. Anyone have any ideas. What is frustrating is that my wife's Evo will work just fine in my car, but mine has not ever since I tried Vlingo.
There must be a way to reinstall bluetooth without having to do a factory reset and start all over again. (And I'm not sure that would do it anyway.)
Anyone with suggestions?
Update: I just flashed the updated stock ROM (New_RUU_Supersonic_3.30.651.3_Deodexed_signed - http://www.4shared.com/file/yLaxLUnJ...RUU_Super.html) from http://forum.xda-developers.com/showthread.php?t=836728.
"So Far - So Good" as my bluetooth suddenly worked again. I have flashed the previous stock 3.30.651.2 ROM and nothing changed. This also comes with a updates stock kernel. So who knows, may be this update fixed the problem. I'm keeping my fingers crossed.
BTW, I forgot to wipe anything when I did this update. All good so far.
Later: It works better but not consistent. I still have problems where after a phone call I have to turn the bluetooth off, then on again to make or receive additional phone calls.
I think i fixed my bluetooth !!!!!!
I THINK I FIXED IT !!!!!!
Wow after over 2 months of searching, learning, and trying everything I could think of (other than unrooting and going stock) I stumbled upon what seems to be a solution.
Here is what I did:
Using ASTRO file manager I opened up the "system" folder then opened the "app" folder. From there I scrolled down to the "BrcmBluetoothServices" file and long clicked it until the "File Options" appeared. Then I selected "Edit" and on the next pop-up I selected "Delete". (I was desperate and was going to delete it and reinstall from scratch).
When I selected Delete, a confirmation box appeared that said something that caught my eye like, "Are you sure you want to delete the update as this will return the file to stock?" (or something like that). WOW, when I heard delete the update I figured that Vlingo may have updated this file causing the problems. So I said yes. The update was deleted.
The BrcmBluetoothServices file remained but evidently it reverted to its original stock format. I noticed that my Evo no longer showed a pairing with my car. So I went to my car and deleted that pairing as well and then re-paired my car and phone.
Success! I have been using it for a day and so far so good. My Evo instantly connects with my car when I turn the car on, and I can make and receive phone calls normally. It has only been one day, but it looks good so far!!!
This did fix the problem. Working now for 2 weeks.
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.
My GSM unlocked GN, running original ROM IMM76D with Franco kernel Milestone 3, stopped responding to being plugged into a USB port using the original cable (I don't have another cable atm). I just wanted to change some music I had on it and I realized it just doesn't detect the phone.
Since I tried an OTA update to IMM76I that didn't work, I thought it might have fiddled with something, so I decided to upgrade to IMM76I using the trusted toolkit which I've already used several times.
[on win7 sp1 64bit]
I managed to browse the phone when it was in recovery mode (ADB), and take off it my various backups - not via the toolkit. Flashed, unlocked, rooted, the works. Restored apps. Plugged back into the computer... Nothing. The computer reads it when in fastboot or recovery though. If the device is plugged in before fully booting into Android, it works fine. If I unplug it and try again - when android is fully up and running - no cigar. It doesn't even read on the toolkit. Receives power though.
I've tried connecting the phone to other computers (other win7 no sp1, xp), still nothing. That's why I assume it's a phone software problem, but I can't figure out what. Did anyone encounter this phenomenon?
Do you have fast-charge enabled?
Also make sure MTP is checked in Settings>storage>options.
MTP is on and always was.
I have supercharging on via the franco app. I'll try turning it off and plugging it in when I get home.
Sent from my Galaxy Nexus using XDA
That is why. If you disable USB fast charge it'll work great again.
Only use fast/supercharge, if you're in a hurry to charge your phone, like in a train, or something...
When you're at home, just leave everything as it is, and you'll never have problems, like that...
If that then doesn't work, reinstall the drivers
thanks people! I'll send franco an email about mentioning that supercharging disables data right next to the enabling tickbox.
Not home yet...
Sent from my Galaxy Nexus using XDA
Hi Everyone,
I'm new here and I search the forums but didn't find anything that would fix the issues I'm having.
I bought a kickstarter edition through the internet on the cheap that wasn't working but showing up in adb.
So I checked it out, ran recovery and flashed the latest ouya firmware on it.
Now the Ouya booted, and averything is working except for the sound.
I tried unplugging and replugging, I tried cables and different tv, checked out the volume settings, not muted.
So far nothing is working.
I read some topics on other android devices where they had to modify a file on the sytem to get audio working again.
Now I hope someone has had the same issue and can help me to fix this.
Greetz,
Rik
Ok people,
I'm very stupid.
While recovering the ouya i put my tv selection mode to PC instead of HD.
When switching this back it worked right away.
Mods please close this thread.
Rikdegraaf said:
Hi Everyone,
I'm new here and I search the forums but didn't find anything that would fix the issues I'm having.
I bought a kickstarter edition through the internet on the cheap that wasn't working but showing up in adb.
So I checked it out, ran recovery and flashed the latest ouya firmware on it.
Now the Ouya booted, and averything is working except for the sound.
I tried unplugging and replugging, I tried cables and different tv, checked out the volume settings, not muted.
So far nothing is working.
I read some topics on other android devices where they had to modify a file on the sytem to get audio working again.
Now I hope someone has had the same issue and can help me to fix this.
Greetz,
Rik
Click to expand...
Click to collapse