Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,730,629 Members 41,250 Now Online
XDA Developers Android and Mobile Development Forum

[Q] phone not being recognized at ALL as usb? (cm11)

Tip us?
 
emaayan
Old
#1  
Senior Member - OP
Thanks Meter 3
Posts: 113
Join Date: Nov 2008
Default [Q] phone not being recognized at ALL as usb? (cm11)

hi..

after installing cm11 it would appear my phone is not being recognized as usb device at all? neither as usb mass storage device or as mtp , i does charge the phone, but that's it.

i've enabled MTP in usb comptuer connection, and tried to connect it to 2 different computers.
 
Magamo
Old
#2  
Senior Member
Thanks Meter 217
Posts: 241
Join Date: Oct 2012
Hmmm. I haven't seen an answer to this question posted yet. Emaayan, did you ever get a resolution to this? I actually have run into this twice in the past, and the answer is to shut the phone down, and do a battery pull to reset the hardware completely. Had me scratching my head for months, and even had me develop a way to do a full unroot and return to stock without ever touching USB or terminal, until I took the battery out of my fiancee's phone since we were planning on returning it, and using it on what would've been her backup phone. When I returned the battery to it, the USB worked again. It's not a CM issue, or a software issue at all. It's definitely a Samsung not-initializing things properly issue. I've seen it happen on stock, I've seen it happen in the old 4.3.1 FatToads, and the 4.4.X FatToads.
TeamApexQ -- irc.freenode.net/#apexqtmo
The Following User Says Thank You to Magamo For This Useful Post: [ Click to Expand ]
 
yohan4ws
Old
#3  
Senior Member
Thanks Meter 160
Posts: 467
Join Date: Oct 2012
Location: Calgary
Let me know if the above works (battery pull).

I had this issue too, didn't realize it until I tried updating different roms...

I put on Carbon after OmniRom ... OmniRom was overheating my phone and battery and it was at that time I actually pulled it apart and wrapped it in a gel ice pack to cool it down.

I don't recall if Carbon had worked, but I'm back on CM11 now and am getting USB working.

I also updated to the latest CWM per OmniRom thread in development forum.

I trust Magamo, though, in providing the right diagnosis and solution.
Samsung Galaxy Relay 4G - Unlocked on Virgin Mobile Canada
- G.Skill 32GB Micro SDCard. CWM, Titanium Backup Pro. Apex Launcher, JuiceDefender Ultimate.
- Current rom: [4.4.4] [Official] LiquidSmooth v3.1
 
REV3NT3CH
Old
(Last edited by REV3NT3CH; 8th March 2014 at 04:58 AM.)
#4  
REV3NT3CH's Avatar
Recognized Contributor
Thanks Meter 1371
Posts: 1,957
Join Date: Dec 2012
Location: Oroville

 
DONATE TO ME
mod please delete
☢ Samsung Galaxy SIII ☢
Rom: [4.4.3] [Official] LiquidSmooth v3.1 Kernel: Deathly 1.6 Recovery: TWRP 2.7.0.0
☢ Samsung Relay 4g ☢
Rom: [4.4.3] [Official] LiquidSmooth v3.1 Kernel: B14CKB1RD Recovery:TWRP 2.7.0.0
☢ HTC REZOUND ☢
HBOOT: 2.28, Unlocked, S-Off, 2.23.10.0123r/2.23.10.0124r radios Recovery: TWRP 2.7.0.0 (Masque Of The Red Death)

Donations are never expected but are greatly appreciated
 
Magamo
Old
(Last edited by Magamo; 8th March 2014 at 04:41 AM.)
#5  
Senior Member
Thanks Meter 217
Posts: 241
Join Date: Oct 2012
Quote:
Originally Posted by REV3NT3CH View Post
i believe OmniRom caused my phone to brick...flashed it to see the issue people were having to help with a fix....apparently lbcoder is breaking stuff again lol...when i get either a new relay somehow or fix mine..i may look in their code to see what it is...im almost assuring its how MTP is not being handled correctly.... i respect @Magamo and most the other devs.. but all i can do is suggest a fix and get disrespected by lbcoder

Edit: like this for example https://github.com/TeamApexQ/android...95e16dfcb3dee8
OmniRom was not the cause of your bricking, I hate to break it to you. The commit you just linked actually has very little to do with the kernel. It was an update to fstab to match a change in paths. There was no driver functionality change in anything that was dependant upon. If you respect me, I would appreciate it if you were to stop spreading FUD about us, and my work. I'm starting to become personally insulted here. Bricks more often happen due to faulty hardware. No properly booting kernel would have been the cause of what happened to you. I assure you, our kernel is working properly.

This is also completely off topic to the question asked. As stated, I've personally seen this happen on several images, Stock included. This particular issue is a Samsung hardware initialisation issue, and is resolved by a battery pull.

Since it is off topic for this question, I will not ask here what you feel is wrong with our MTP code. We can start another thread, and stop hijacking this one. Better yet, as always, the best place to discuss this with us would be on IRC.
TeamApexQ -- irc.freenode.net/#apexqtmo
The Following User Says Thank You to Magamo For This Useful Post: [ Click to Expand ]
 
Autolooper
Old
#6  
Junior Member
Thanks Meter 0
Posts: 1
Join Date: Mar 2014
Default Surprisingly, pulling the battery fixed the problem!

After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.

I can vouch that pulling the battery does fix the problem with devices not being recognized.

Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.
Tags
cm11, mtp, usb
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes