Hi, I really need help. three months ago, some weeks after my Mi 9T overheated on sun (don't know if that has some relation to the issue), it suddenly stopped charging while on, unless I rebooted or turned off. Also, it had difficulties to transfer files to PC and connect to a flash drive by OTG.
Then, I took it to a guy and he said I needed to replace the charging port, and so I did. But only now, after a serious issue. I was changing my rom from MiRoom (MIUI 12) to Evolution X, since the MiRoom's developer ended the rom's support. But It didn't work, It boots into Fastboot mode. I tried to connect to PC and OTG, on recovery mode, but neither worked. The PC doesn't recognize my phone, and the OTG flash drive isn't recognized by the phone.
I bought the charging connector online and paid that guy to replace it. The port feels better, the connector feels way steadier when pluged in, but I still can't know if it charges while on and file transfer to PC or OTG is still not working. So, I'm stuck on recovery mode, in a rom that doesn't boot and a USB port that doesn't work properly. If anyone has a clue of what part I might take to replace or a repair, or maybe a software solution, if that's the case, I would be really thankful.
Related
Ok so long story short, i have a nexus 7 2012 which a rooted and installed cyanogen mod.
I was using it as a car install and works perfect, i'm using an otg cable to mount usb sticks, triggering soft shutdown and powering the nexus etc. So usb seems to be working fine.
Basically i removed the tablet it to modify the bootloader to turn on automatically with ac power applied, if the battery runs out i have to manually power on with button, but now i'm running into a problem.
Ever since taking the tablet out and trying to connect over usb, none of my computers detect the tablet.
I've tried different operating systems, drivers, cables etc etc.
Also changed from mtp to ptp in storage and also turned on usb debugging mode. If i connect an otg cable the nexus see's the otg and i can mount usb's etc.
So i thought i might try recover the nexus back to factory, maybe there was an issue with the rom corrupted etc, I've downloaded the original 4.2.2 firmware which is currently installed.
Booted into recovery and tried re-installing the 4.2.2 zip, it keeps aborting. A guy in work tried to use sideloader and connect via adb. no luck.
I'm not very familiar with the android platform so i've no other ideas what to do and other idea's how to recover now.
The guy i work with mentioned using a usb jig, would that be the way to go or can anyone else suggest some else that might help.
Thanks
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Does adb see the device
jadesse said:
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Click to expand...
Click to collapse
I last connected the nexus to the laptop a few monts back to load some music onto it, didn't have a problem. It's only been connected to a computer maybe 3 times. once to root/rom it then another few times to load music etc.
I can't see why the usb board maybe faulty as i can read data from a usb key when the otg cable is connected.
It's a strange one. You could be right, i might try pick up a broken nexus and swap some parts. Usb board etc.
crusrod said:
Does adb see the device
Click to expand...
Click to collapse
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
foster182 said:
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
Click to expand...
Click to collapse
I am having this same problem on my (unrooted) HTC One after attempting to "convert" it from an AT&T to a Google Play Edition device with the procedure described here.
As part of the procedure, I attempted to flash the stock Google Play Edition ROM using fastboot commands, but I got an error message. The instructions say to just try the flash again, but the phone no longer connects properly via USB (error 10) while in bootloader mode. While in bootloader mode, the phone indicates there is some sort of problem (a line showing the OS version is highlighted in red), and attempting to enter recovery mode does nothing but display a phone with a big red X in it. The phone seems to operate fine and responds to ADB commands when the phone is fully booted, albeit with the old OS (not Google Play Edition) still in place.
Any Android device could theoretically get in this state. We're sort of "paralyzed", because everything we want to do to regain control of the bootloader and fix the situation seems to require issuing fastboot commands from a computer connected to the phone while it's in bootloader mode. Yet entering recovery mode or getting a computer to connect to it via USB no longer seems possible.
I wonder if there's another way to issue fastboot commands without relying on the USB connection to a computer?
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
Okay so I f****ed up my phone bad.
Everything was working fine. I had a custom rom installed. One day the charging jack stopped working. The phone wasn't charging or connecting to PC. So I replaced the jack from a cheap shop and the mobile was charging once again but wasnt connecting to PC. I didn't mind it. Now after a few weeks the screen cracked and I replaced it again from a cheap shop. I booted the mobile and everything worked fine for 5 minutes and then the phone automatically restarted. This kept happening and then I opened twrp. the screen was working fine now and it wasn't restarting. So I knew the screen was fine the software was faulty. So after a few F**k ups I managed to remove TWRP as well as the Rom. Now the phone is only opening to fastboot mode and I cant put it back to Stock Firmware because it is not discoverable on my PC. I know I can replace the charging jack from official moto store but please help if it is possible without that.
TLDR
no rom or recovery in phone
only boots into fastboot mode
cant connect to PC.
harshill_only stock said:
Okay so I f****ed up my phone bad.
Everything was working fine. I had a custom rom installed. One day the charging jack stopped working. The phone wasn't charging or connecting to PC. So I replaced the jack from a cheap shop and the mobile was charging once again but wasnt connecting to PC. I didn't mind it. Now after a few weeks the screen cracked and I replaced it again from a cheap shop. I booted the mobile and everything worked fine for 5 minutes and then the phone automatically restarted. This kept happening and then I opened twrp. the screen was working fine now and it wasn't restarting. So I knew the screen was fine the software was faulty. So after a few F**k ups I managed to remove TWRP as well as the Rom. Now the phone is only opening to fastboot mode and I cant put it back to Stock Firmware because it is not discoverable on my PC. I know I can replace the charging jack from official moto store but please help if it is possible without that.
TLDR
no rom or recovery in phone
only boots into fastboot mode
cant connect to PC.
Click to expand...
Click to collapse
If the USB socked isn't working, there's no other connection to transfer any file to the device.
It's impossible without repairing the USB socket.
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.