hello community,
i'm using my primou almost a year now
Just a week ago, after trying out usb host functions (which failed from mice and keyboard but flash drives mouted ) i can't connect my one v to a PC anymore (neither ADB nor sdcard mount), and usb host functions stopped working. the phone is just charging.
I'm currently using the shpongle build 20130518 with hellboy kernel 20130514 (my thanks to the devs!!). I do not think it is a rom issue, because fastboot does not work either.
After a little research i found out that the htc desire had this kind of problems and the called it an USB-Brick. I don't know if that is comparable, because my phone works perfectly.
Has someone had this trouble earlier or is there a solution?
I'm pretty sad, that i cannot flash the now shpongle update as it requires an new kernel :crying:
thanks in advance , Sid.
Related
Hello, I have recently upgraded from ARHD 2.13 to the latest 3.2, and I've noticed that once I connect the phone to the PS3 via USB, the phone completely freezes. This has never happened with 2.13. I have found a similar thread regarding this issue, with no solutions however. The USB freeze ONLY happens on PS3, PC works fine.
http://forum.xda-developers.com/showthread.php?p=12169141#post12169141
As you can see, it happens with Inspire 4G, and I am using DHD.
I would report this problem myself in the main thread, but I can't due to postcount limit. Could someone please confirm this and report in in the main thread?
My thoughts on this is that it might have to do with the Inspire compatibility, as ARHD 2.13 was only for DHD, if I remember correctly, and it did not have this issue at all.
Lastly, I have flashed 3.2, no-sense, advanced power menu and the 3.1 performance patch, if needed to know. Thanks alot!
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.
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
Hello XDA Devs. I would like to ask from your professional help regarding my HTC DHD. After flashing Sabsa Prime v16.0 (before i was on Sabsa Prime v12.0) my phone was not recognized by my computer. Originally, when i was on Sabsa v12.0, it was all working fine. But when i flashed a custom rom (sabsa prime v16.0), it was NOT RECOGNIZED by my computers. I tried both on my computers (Win 7 32bit and Win Xp 32 bit) and still thats my problem. I was using the cable that I was used before.
Now what I've done is to revert back to Sabsa Prime v12.0 and the issue is still there. I tried also PACMAN v22 and still its my problem. I want to try to perform an ADB commands but as i was saying the phone keeps on not recognizing my phone.
I was not using HTC Sync. Because I only connect it as a Mass Storage. And it was perfectly working before until i flashed one. Please help me. I need your expert advices and help! THANKS in advance. ) Hope you can help me.
Furthermore , when I connect it to my PC. It is only charging but still not recognized.
Hi all
I was using an old version of JellyTime ROM on my DHD, then I installed the newest version (after a full wipe). The wifi couldnt find any network after the update(I thought its a problem with the ROM). I tried wifix and it worked perfectly.
After few days I decided to try another ROM. I tried PACman, CodefieX, Xperia Honami and Oxygen JB (all jellybean 4.2.2) and the wifi problem was not fixed.
Then I tried an old version of CodefireX (still 4.2.2) and wifi worked perfectly.
Flashing a new version results the same problem .
Any help guys please :crying:
Try going back to 2.3.7 CM7 and flash another ROM. Sounds like a hardware problem though
"Two types of people: Those who buy iPhones; and those who are intelligent. I'm intelligent."
- Guy
I experienced this issue when I flashed a new ROM.
I solved the issue by flashing boot.img from the ROM manually.
You can find the boot.img file from the zip file of the ROM. Boot the phone into fastboot mode and connect the phone to PC. Use the command:
fastboot flash boot boot.img
If you don't know how to use fastboot command on PC, find it from some other threads.
Hope it is helpful for you.