Related
Hi,
So I upgraded from cm7.2 to 10 on my defy green lens. After a long and difficult upgrade, almost everything works - except any functionality of the usb port...
I'll jump right into the real deal: without usb connectivity, I cannot try to flash other SBFs to fix it! I can enter the bootloader screen just fine (says 09.10 on top, I believe that the last SBF I flashed was 3.4.2_179-002 , as recommended, before I rooted it, 2ndinit, and sucessfuly installed cm10) and the phone recognizes when I plug in a usb cable to it. but the computer always shows up a "usb device not recognized" error, and I tried on two machines, winxp/win7, and several different usb cables. I read some threads about crashing drivers between rsdlite and different tools motorola made; I never installed any of that junk but just to be on the safe side I removed all drivers and started fresh. still no go.
______________(That's the problem, now I'm just going to give more information about it)______________
The phone does not charge off a computer nor from a wall charger, with an assortment of different usb ports, cables and chargers. when connected to a computer (whether the phone is on or off) a "usb device not recognized" message comes up, on both windows xp/7 (different machines.) Seldom, when connected to wall charger, I can get the battery icon to show charging for about a second, (after a restart and plugging in to the pc briefly beforehand.) If I'm so lucky to make that happen, either it goes off in about one second, or it will change statues from charging to not charging several times very rapidly and then stay on not charging.
If the phone is off and I connect it, the white led sometimes come on, and then the phone comes on- presumably to go into battery charging screen, but instead it boots up normally. (this may be the correct behavior with this rom. idk.)
If you care for more information, let me elaborate about what I mean by "After a long and difficult upgrade":
I previously upgraded to cm10 (30/7/2012) CM10-20120730-NIGHTLY-mb525.zip,
but downgraded shortly after, back to 7.2. (I decided to wait for something a bit more functional)
Back then both the upgrade/downgrade went fine. This time I got into a bootloop (or stuck on bootscreen) after updating to 26/03/2013 God's version (oops I meant Quarx's version.)
Trying to use my nandroid backup for 7.2 I got a md5 mismatch and even after generating a new md5 file I couldn't restore /data.
Moving on. using CWM I tried installing some kernels (kernel-froyo-222-179.zip, and same thing but signed,),
then a fixed sbf (not full) 3.4.2_177-Fixed.NORDIC_DEBLUR.sbf,
and a very crappy sbf JRDNEM_U3_2.26.0_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB1B5TEL02A.0R_USAJORDANTELSTRA_P033_A017_M008_HWp3_Service1FF.sbf
** this one almost gave me a heart attack, after successful flash defy black screened with no LED indications. I was able to work my way into the bootloader and flash another SBF with rsdlite, without any indications from the device. lucky me.
Then I flashed the sbf I mentioned above and that's how I eventually got into cm10.
I can't even downgrade to stable cm7.2. Tried flashing a fresh install through CWM (wiping everything before and after, of course) and ended up stuck on boot screen. I don't know if it has anything to do with CG numbers or what, but I really can't figure out why CM7.2 wouldn't boot on the same SBF CM10 is booting fine right now.
I can't also share the SD card through CWM. (-> device not recognized)
I'm losing my marbles over here. Been working on it for two whole days and can't think of anything else I can try out... If I flashed the wrong rom using CWM I might get locked out because bootloader won't be any help!
:crying: cry for help... thanks :fingers-crossed:
Have you tried installing adb and the motorola drivers so you can try to communicate with the device?
Thanks for your word zero gravity!
Well, I thought that since "usb device not recognized", and since it shows up as unknown device under device manager (currently it disappears and reappears every 3 seconds, but I think this is a new behavior) I automatically assumed that I couldn't get proper communication with it! I guess I got to do some reading about adb commands any help with it would greatly be appreciated (No worries though I know how to google )
http://forum.xda-developers.com/showthread.php?t=1241935
Here's a simple guide for adb. Hopefully you can get some sort of communication to flash your stock sbf and start over again.
So, even though I have the drivers installed (Motorola_End_User_Driver_Installation_4.9.0_32bit.msi_.zip, and also installed MotorolaDeviceManager_2.3.9.exe,) Android SDK Tools installed, then I tried adb devices - nothing comes on.
by enabling ADB over network I can adb connect to the phone through wifi and go into shell. but I can't see how I can debug the buggy usb interface with network access.
Also tried starting the adb service through recovery - no go, won't show up.
(I plugged in a different Android phone (an Xperia), installed the drivers and had it running on adb usb in no time. So I'm doing it right.)
Any thoughts? are there commands to specifically listen and figure out what's coming from the usb port?
any other leads anyone may have? I'm listening!
Cheers, Shawn
The port must have suffered hardware damage. Examine the port for obvious conductivity hindrance. If not I'm afraid you'll have to get it repaired
As for cm7.2 after flashing just format to ext3 from boot menu(before this wipe dalvik cache), and after a reboot wipe data from stock recovery for good measure
Sent from my MB526 using xda premium
Well, thekguy seems to be on the right track.. I can fiddle around with the usb plug and get it to charge, So the problem seems to be mostly physical - if not completely.
I still can't get it to connect properly to the computer, but go figure which usb signal is dropping off. might be power, might be data.
After spraying it several times with contact cleaner the port is good enough for steady charge. No change about how it doesn't connect to a computer.
I feel like a dumbass, cus I already gutted the phone up a couple of days ago to try tracing conductivity paths through the port. the usb port is cast in plastic that is not removable from the pcb. There's no access to the USB pins, excepting four conducting points through the plastic right next to the port, but they are all connected to ground - they probably belong to a bracket that's holding the plastic to the pcb.
anyhow I did all that (I got closeup pictures if anyone's interested) but I wasn't able to check conductivity, and I didn't try fiddling with it after that. bah!
___________________________
Still wondering about one thing! The bootloader is locked, so that means it was never-ever changed since the phone was manufactured, correct? So no effect of writing different SBFs on the bootloader, correct? (minding the Efuse and CG numbers)
if so, than can I conclude only by that information (and that I cannot connect the phone to the computer anymore with bootloader) that there must be hardware/physical damage? I've just completely eliminated the software factor out of the equation. haven't I?
Did I miss anything? let me know.
P/S, I'm going to stick with this phone as it is. I can work around never having usb data connection.
Cheers
Can you try installing Linux and see if the you can mount /system or even /sdcard on Linux from bootmenu? Bootmenu mount only works in Linux. I've tried it in Ubuntu 10.10
Its worth a try, if Linux doesn't see it then it must be a hardware issue and would need a Motherboard replacement.
Use ubuntu live disk to make things easy and not mess your Windoze
Sent from my MB526 using xda premium
You're right, sbf flashing cannot break usb functionality. I'm not very well versed in mobile hardware but I think the port can be replaced, though I don't know how. It may be possible that a local mobile store could fix it.
Trying Linux is a good idea, though it may not work out from the looks of it(the phone)
Sent from my MB526 using xda premium
If anyone is reading this, I had some bad batteries and a usb port that is having physical problems. I'm flashing it with contact cleaner spray every now and again and it helps. I can get a usb connection to the computer and charge it with a bit of luck and while I keep it stationary.
Hello,, I have a galaxy s4 running on Omega rom,, and my usb porn doesnt work,
I did a factory reset to find that ALL the apps crash on startup
If the usb porn was working I would have just flashed the stock firmware,, but any operation that needs USB is impossible
Can you please help me? Isnt there a solution?
** It's USB port , not USB porn **
What exactly do you mean by that?
1) Do you have USB cable connected to PC and your PC does not detect it?It could be a cable problem.Have you try a different one?
2) It could also be a driver problem.Do you have installed the correct drivers so your PC can detect your phone right?
Also if you had a custom rom flashed to your phone you can make it work again just by flashing it back using a custom recovery.Format system , data , boot and cache partitions and make a clean install of your rom.If you have not a custom recovery I am afraid you have to flash your phone through USB.
First of all, I would like to thank you for your help
Apologies for that mistake I'm still getting used to my new keyboard..
The USB port doesn't work meaning it neither charges nor connects to pc, because when it was charging, I smelled some plastic burning, could be a short circuit
And I don't have the Zip of the rom anymore on the phone, could it be possible to put an SD card and flash another one that is guarenteed to work?
And yes I have custom recovery
SohaibTheGame said:
First of all, I would like to thank you for your help
Apologies for that mistake I'm still getting used to my new keyboard..
The USB port doesn't work meaning it neither charges nor connects to pc, because when it was charging, I smelled some plastic burning, could be a short circuit
And I don't have the Zip of the rom anymore on the phone, could it be possible to put an SD card and flash another one that is guarenteed to work?
And yes I have custom recovery
Click to expand...
Click to collapse
Yes just put a rom on your sd card and flash it.
SohaibTheGame said:
First of all, I would like to thank you for your help
Apologies for that mistake I'm still getting used to my new keyboard..
The USB port doesn't work meaning it neither charges nor connects to pc, because when it was charging, I smelled some plastic burning, could be a short circuit
And I don't have the Zip of the rom anymore on the phone, could it be possible to put an SD card and flash another one that is guarenteed to work?
And yes I have custom recovery
Click to expand...
Click to collapse
Yes.If you have access to recovery you can just connect you sdcard to PC with an adapter and put the zip of your rom inside.Then put it but to your phone and flash it back.
You could also try to mount your sdcard to PC from your custom recovery and you put the zip of your choice inside.
Hello XDA, my virtual phone heros, i appreciate your good work, i am reading here for a few years as a ghost and today i signed up because i am lost with a serious problem on my Note4 N910C (English is not my native language)
THE CONDITIONS AND ENVIRONMENT:
My Phone was first running on stock Lollipop 5.1.1 when i rooted it over ODIN 3.10.6 with space X kernel and CF Autoroot, SuperSU then i flashed the latest TWRP...
After that i flashed a Custom Rom: Sweet_ROM_V17.1_COJ2_N910C...
Everything was running flawlessly for about 2 weeks...I installed Titanium Backup, Xposed, Xprivacy Pro, Busybox and a lot more and made a complete TWRP Backup then, it was running like a charme...The backup is fine because when i messed up my phone through trying harder xprivacy parameters and other tweaking i needed to set it back by TWRP into the old state...
Nothing happened after that, it was running 100% for over a week of heavy usage...
THE PROBLEM:
The one morning i took it from the charger with 100% Battery and went to work...
Before the error occured I did some searching on the internet, used chats. movies, nothing special this day, USB Debugging was On, i remembered something messed up my chrome browser like this ad hijackers, i set it back by erasing data,cache of chrome in the app menu, then there was nothing else strange i remembered, my AF Firewall was closed, only Whatsapp and Browser were allowed to going through...
The same day in the afternoon i tried to use my car charger to recharge my Note 4 as usual, but this time it wasnt recognizing the charger and my first thought was that the charger is faulty or the cable, so i turned off the phone by the androids power menu...I retried loading my battery In the phones off state but when i plug in the charger, the battery symbol came up for short and then it remained dead, it s the same scenario until today, so i used my powerbank to try charging, because the powerbank has an indicator to show the loading state and everytime i plugged it in, it came up for short, battery symbol shows up for a few seconds, but no percentage or animation is showing as usual and no red LED, then its switching off, the powerbank LED indicator stops the loading state after a few seconds, so the loading current stops...
At home i tried the stock charger and it remained the same, since that, i have to charge the battery outside the phone...
The strange thing is:
The Rom is still booting fine, TWRP is booting, but its not going into download mode from Androids Power Menu like before, its always just rebooting back into android if i choose download mode and i have to take the battery out and back in and hit the download mode pattern Vol- Home Power, to enter Download Mode and even the booting into Download mode from TWRP gives the same strange results:
On my Laptop i started the device manager to see the USB hardware string parameters after a windows popup was telling me something like "Device not recognized"
The USB Driver ID dont fit the old right driver ID, it seems to be empty and the port is not communicating anymore
since the charging bug occured,( Everything worked fine the day before.)
I tried my Laptop to narrow down the bug with the same driver i used for flashing phones (S6,910F,910C) over ODIN and my Lappy has USB 2.0 and USB 3.0 ports.
I always used the same USB 2.0 port for ODIN and other MTP stuff, but since the bug showed up the 910C is not recognized at the USB 2.0 Port anymore, seems to be dead in the devices manager table, only the USB 3.0 Port shows it as unknown device with a strange empty ID --> I tried the other devices like the N910F and G920F that are still recognized by ODIN on the same USB2.0 and 3.0 Ports both with the same USB hardware strings, its just the N910C that isnt recognized anymore, in no mode, no ADB, MTP, no download mode, everywhere the same, USB is bricked! Windows finds no driver and says its no info avaiable on this device so I tried to force the right driver to run with the wrong buggy driver ID but its not communicating, ODIN indicator and log remains unchanged...So it seems to be the same situation like other people getting from killing the bootloader by bad flashing, the only difference is that my phone is still booting fine into recovery and even Android but with no charging. My USB Port is totally useless now, its like if Samsung or Google OTA update has overwritten my bootloader or something hidden in the rom that woke up to kill my mods i dont know and now.
PS: Things i tried so far with no results on fixing my issue....
1. Complete fresh reinstall of Sweetrom, 2. Flashing another kernel...
3. Roll back to my TWRP Backup of perfect running ROM but with no USB support anymore:
The Phone remains in unknown state, not affecting ODIN to switch into flash mode
I am sure its the bootloader, since its battery bug is still occuring while the phone is in off state...
Unable to tell the charger the right ID without USB communication...
i was wondering if there is a solution to make a bootloader hotflash from out of Android or something like getting me back on stock first with download mode, forcing the USB ID or communication with a tool out of android, SD card boot image like on note 3 whatever, please tell me! I cant find something related to my USB and Charging ISSUE
PLEASE HELP ME, I am lost
Still the same. It's booting fine, USB2.0 no reaction on the laptop in Fastboot/Adb/Mtp ... On USB 3.0 Device remains unknown with strange Device ID String in windows 10 hardware Manager... Forced the old formerly working driver, but Odin can't find it anymore... Adb, Mtp, fastboot don't work, no communication... USB Cid is hard bricked, Charging never works in no state, just showing up for a few seconds in off state while plugging it in for short.... Bootloader must be damaged, fastboot and twrp can be started with dead USB... So is there a way to run a boot image to fix my bootloader from SD card, Aroma, or like OTA Updates are flashing? If Samsung and Google apply bootloader updates over OTA and simply restart, why we can't do that??? I need a new bootloader, is there any way without USB?
Greetings,
Thank you for using XDA Assist.
I have moved your question to your device's Q&A forum. You'll receive expert advice here. Good luck!
Fixed!
The problem is the USB Connector Port itself, figured it out after bending the inner contacts up with a flat screwdriver and cleaned them. Before that i always tried the same gently with no change, but please do it at your own risk only. After searching for many hours about possible reasons for the problem, I came to the conclusion to even compromise the Port and heavy bending it up, now it's charging! I will exchange the port soon and change the frame too to have it back like as new... OK, if anyone in the future have problems with the bootloader or USB hardbrick n910c, feel free to ask me, I upgraded my knowledge on many causes now
Thank you very much
My 2cents stick to one charger. Do not share that charger with others.
The worst culprit are the cheap china car chargers.
I went thru two USB ports on my first phone to figure this out.
Ever since I have adopted the policy of using only one cable. Never had this issue.
Hi, looking for some 2nd thoughts on this before I throw this phone away. I got this Nexus 6P a year ago and put purenexus into it along with TWRP, everything was going great. Had an issue with a car charger, the charger port heated up badly and I couldn't charge it. After messing around with it I finally got it to charge but not rapidly (no big deal). Now I tried to upgrade the purenexus version and had some booting issues. So I tried to mess around with the versions and in the process I accidentally wiped the data on the phone. Now the charger port charges but I cannot connect to the PC (as in nothing detected in device manager, no sound of plugnplay or anything). I cannot boot to transfer files with the wifi because there is nothing to boot to. 6P has not ext SD port so I cant put files in. TWRP has also a sideload on the install version but ADB doesnt see the device in any state (obviously if the pc doesnt see it). Finally, I figure I just had to change the charger port so I ordered a new port, put it in and same thing. Phone charges but not detected by any PC. I don't think there's another way to put a rom image on the internal SD but if there is I am all ears.
rbigras said:
Hi, looking for some 2nd thoughts on this before I throw this phone away. I got this Nexus 6P a year ago and put purenexus into it along with TWRP, everything was going great. Had an issue with a car charger, the charger port heated up badly and I couldn't charge it. After messing around with it I finally got it to charge but not rapidly (no big deal). Now I tried to upgrade the purenexus version and had some booting issues. So I tried to mess around with the versions and in the process I accidentally wiped the data on the phone. Now the charger port charges but I cannot connect to the PC (as in nothing detected in device manager, no sound of plugnplay or anything). I cannot boot to transfer files with the wifi because there is nothing to boot to. 6P has not ext SD port so I cant put files in. TWRP has also a sideload on the install version but ADB doesnt see the device in any state (obviously if the pc doesnt see it). Finally, I figure I just had to change the charger port so I ordered a new port, put it in and same thing. Phone charges but not detected by any PC. I don't think there's another way to put a rom image on the internal SD but if there is I am all ears.
Click to expand...
Click to collapse
Hi... Seems like you already tried all the available options. How about bootloader? Is the phone detected? Try to reboot in bootloader and issue: fastboot devices
If your phone is recognized, you can try installing a factory image.
Just in case, download last adb/fastboot version from Google directly:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
DEVICE: OnePlus 6T T-Mobile flashed to International 10.3.8 OOS bluspark kernel, Magisk, TWRP, unlocked boot loader.
CURRENT SITUATION: Currently, lost magisk, twrp, and am factory reset/wiped to stock OOS 10.3.8 have no USB function through OTG, EDL, Fastboot, or ADB. I HAD all of that properly setup and working just days ago. USB only works for charging now. Phone “works” otherwise. Just can’t use USB for DATA, or push recovery, root it now. Which my main reason I bought this phone used was for having root.
HOW: I had everything running and setup how I wanted. But in TWRP recently (not from beginning of owning the device) when I flashed stuff or switch slot A/B in TWRP I would get a warning saying “unable to mount storage” even though the flash file would complete successfully and slot would change. Then when plugging in my USB C OTG drive the phone no longer picked it up. THEN I noticed I couldn’t ADB into the phone. I plugged it into the same cable and USB 2.0 port that had been used fine for a couple weeks. So even though I had everything working fine otherwise I decided to “fix” this problem and try some things which stupidly got me to now a “kinda working” never again to be rooted device. Useless to me. I thought I would reach out here for last ditch effort for any options I missed before trying to sell on eBay for whatever I can for the state it’s in. Can’t post on OnePlus forums for two weeks and OnePlus support sent me template support reply that was no help. Repair would cost more than what I paid for the phone anyway.
I HAVE TRIED: Different cables, different PCs and ports. Full reset from stock recovery option, installing 10.3.8 zip in Local Upgrade to see if it would help anything. I have USB debugging on. No matter what when I plug it into PC I get nothing in Device Manager pop up, no indication from my computer anything has been plugged in. Only thing that happens is the phone starts charging. Doesn’t matter if in OOS, or boot loader. Trying to boot to EDL does nothing. My previously installed Qualcomm driver didn’t indicate anything was plugged in neither does MSM tool. Uninstalled reinstalled drivers. Nada. Think it’s a hardware problem because the phone should pick up in edl or fast boot at least, or the OTG stick. But nothing. Sucks. Hindsight if I had known this was going to be the result I would have never messed with it and left as it was rooted and recovery. Now it’s just a no fun device I’m going to have to part with. Also of note if I have the cable plugged in and try to reboot the phone doesn’t power back on. I have to unplug it then hold volume + PWR to get it to turn back on.
Thanks for reading maybe someone has options but I’m thinking I’m SOL without USB function I can’t get recovery or root back ever.