Related
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
DTTD said:
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
Click to expand...
Click to collapse
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Fallon9111 said:
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for providing more information on this. I have done a Factory Reset via Settings and also via Recovery, but still not available.
I think I'm making progress with adb via Ubuntu over USB, but USB Debugging still gives the Epic crash and still will not charge while On, which is more just annoying than anything else.
Asus/Google Support are saying it is a physical pin issue, but that doesn't explain why USB Debugging is failing. Does anyone know where the USB files are contained? I'm wondering if I've messed up at the Kernel level. Any thoughts?
About my Nexus - More Info
I forgot that I should provide more information about what I'm running:
Phone: Nexus 7
Android Version: 4.2.2
Kernel version: 3.1.10-g05b777c
Build number: JDQ39
Prior to issue also had:
Recovery: TWRP
ROM: Stock JDQ39
MultiROM: Yes
UPDATE
So after more work on my Ubuntu we have found more information and seem to have narrowed down the issue! :fingers-crossed:
I have been able to flash via Fastboot just fine, which has thus allowed me to get TWRP installed and now I'm back rooted. I still cannot adb via USB though. We've double checked with multiple Nexus 7's of the same type, which allow command: adb devices and their devices will show, while it does not for my device. (Side note: my version of Ubuntu does not "see" the adb command in its pwd so... But tests have been done on other machines and worked...)
So after sifting down to adb issues, we found that in /data/property I'm missing persist.sys.root_access and persist.sys.usb.config ... But creation of persist.sys.usb.config didn't do anything...
Hello.
I recently installed the 4.3 ota update. I knew I would have to reroot. After the update I have tried everything I can think of to flash a new recovery or bootloader or anything. All without success. Fastboot simply says "Sending...", the phone says "downloading..." and that's the end of it. They would both sit in that state forever if I let them.
I know I'm not alone on this issue. I have searched and searched without finding a solution. Does anyone know of one?
Thanks.
pfederighi said:
Hello.
I recently installed the 4.3 ota update. I knew I would have to reroot. After the update I have tried everything I can think of to flash a new recovery or bootloader or anything. All without success. Fastboot simply says "Sending...", the phone says "downloading..." and that's the end of it. They would both sit in that state forever if I let them.
I know I'm not alone on this issue. I have searched and searched without finding a solution. Does anyone know of one?
Thanks.
Click to expand...
Click to collapse
1. Usb debugging enabled and bootloader unlocked?
2. Correct drivers installed, try these usb naked drivers for instance https://www.google.nl/url?sa=t&rct=...=RUlfH35SAJki_DdLfo8MeA&bvm=bv.51773540,d.Yms.
3. Used the original usb cable or tried another usb port?
4. If you type fastboot devices in fastboot mode do you see a serialnumber? The same for adb devices in adb mode?
gee2012 said:
1. Usb debugging enabled and bootloader unlocked?
2. Correct drivers installed, try these usb naked drivers for instance https://www.google.nl/url?sa=t&rct=...=RUlfH35SAJki_DdLfo8MeA&bvm=bv.51773540,d.Yms.
3. Used the original usb cable or tried another usb port?
4. If you type fastboot devices in fastboot mode do you see a serialnumber? The same for adb devices in adb mode?
Click to expand...
Click to collapse
USB debugging is enabled.
I've tried the original USB cable and others. I've tried different USB ports.
adb works fine. Fastboot recognizes my phone and prints a serial number. Fastboot even works for locking/unlocking the boot loader.
There are no "drivers" in the Linux world. Should I find someone who has a Windows system and ask to use their computer?
Thanks.
pfederighi said:
USB debugging is enabled.
I've tried the original USB cable and others. I've tried different USB ports.
adb works fine. Fastboot recognizes my phone and prints a serial number. Fastboot even works for locking/unlocking the boot loader.
There are no "drivers" in the Linux world. Should I find someone who has a Windows system and ask to use their computer?
Thanks.
Click to expand...
Click to collapse
Yes, you may try that. I`am talking about a windows pc and never had an issue. I don`t have xperience with linux computers.Good luck bro
Solved
gee2012 said:
Yes, you may try that. I`am talking about a windows pc and never had an issue. I don`t have xperience with linux computers.Good luck bro
Click to expand...
Click to collapse
So. I solved the problem. I now feel like an idiot.
I plugged my phone into a Windows system and a nice notice popped up saying that my device could run faster if it was plugged into a USB 2.0 port. Then it dawned on me that only a few of the ports on my computer are 2.0 and that I had tried one of them previously but with an extension cable (because it's in the back and hard to reach). I unplugged the extension cable and plugged the USB cable directly into the port and all was well.
I hope that others who have had this issue find this useful.
Thank you for your help.
I wanted to flash purenexus , i tied the steps in the guide from the general section of the forum, but when i went into bootloader and connected to my comp in did not install any drivers and doesnt show any devices connected, i tried from sdk it also said no devices connected, any help would be great
What operating system are you running on your computer?
We will need this information.
I assume you are probably using windows. Did you follow all steps of the guide? It should work.
Have you tried a different USB port for example plugging into a USB 2 port instead of a USB 3 port.
Hi, I apologize for the post here, I did search for about an hour trying to find a solution but couldn't connect the dots. Thanks for your help. The good news is I rooted my phone for the first time and flashed a custom rom. The bad news is that at some point the root got destroyed and the phone is not detected by Win7 when connected in download mode. Recovery works fine, the latest TWRP is in place, Win7 detects the phone. I've tried restoring with a few TWRP backups that I took, but they didn't work. I backed up with Titanium too, but Titanium says it can't restore because of the loss of root. I can flash ROMs from recovery like Lineage 15.1, I am presently flashed to a very current stock g900t rom and the phone is functioning fine.
But I want root back and I want a better rom in there. I worry that we're looking at a complicated bootloader/PIT issue here and I'm soft bricked. This is my message in download mode:
(red) ODIN MODE
PRODUCT NAME: SM-G900T
CURRENT BINARY: Custom
CURRENT STATUS: Custom
KNOX WARRANTY VOID: 0x1 (2)
(grey) QUALCOM SECUREBOOT: ENABLE (CSB)
(grey) AP SWREV: S1, T1, A1, A1 P1
(blue) SECURE DOWNLOAD : ENABLE
(red) UDC START
Your suggestions are sincerely appreciated. Thank you
TheHumbleS3 said:
Hi, I apologize for the post here, I did search for about an hour trying to find a solution but couldn't connect the dots. Thanks for your help...
Click to expand...
Click to collapse
It could be a number of things that may be happening.
Download Mode does require a different set of drivers as opposed to being in TWRP and even booted up.
Here's just a handful of helpful hints in which one or more (or a combination) may help resolve this issue.
Keep in mind that the communication between the device and the PC can be temperamental/picky.
1) Try a different USB Cable.
2) Try a different USB Port.
3) See if you have the latest Samsung Drivers installed on your PC. The latest version is the "SAMSUNG USB Driver for Mobile Phones v1.5.63.0".
4) While your device is connected to the PC, fo into your PC's "Control Panel" then the "Device Manager" and see if you can locate a driver conflict (which is reflected by the Triangle with the Exclamation Point in it). If it's there, Right Click them, one at a time, and select Uninstall but, if the option exists in the popup window, don't select the box to remove the Driver. Then disconnect and reconnect the USB to a "Different USB Port". This sometimes works too.
I hope this helps you out and I do wish you the best of luck!!!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
It could be a number of things that may be happening.
Download Mode does require a different set of drivers as opposed to being in TWRP and even booted up.
Here's just a handful of helpful hints in which one or more (or a combination) may help resolve this issue.
Keep in mind that the communication between the device and the PC can be temperamental/picky.
1) Try a different USB Cable.
2) Try a different USB Port.
3) See if you have the latest Samsung Drivers installed on your PC. The latest version is the "SAMSUNG USB Driver for Mobile Phones v1.5.63.0".
4) While your device is connected to the PC, fo into your PC's "Control Panel" then the "Device Manager" and see if you can locate a driver conflict (which is reflected by the Triangle with the Exclamation Point in it). If it's there, Right Click them, one at a time, and select Uninstall but, if the option exists in the popup window, don't select the box to remove the Driver. Then disconnect and reconnect the USB to a "Different USB Port". This sometimes works too.
I hope this helps you out and I do wish you the best of luck!!!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks Ibuprofen! The cable is brand new and it does work for mtp in normal and recovery boots. Swapped phone through ports in download mode, it wasn't recognized. I checked for conflicts (none) and updated drivers and tested across ports again. Win 7 still isn't recognizing my phone in download.
TheHumbleS3 said:
Thanks Ibuprofen! The cable is brand new and it does work for mtp in normal and recovery boots. Swapped phone through ports in download mode, it wasn't recognized. I checked for conflicts (none) and updated drivers and tested across ports again. Win 7 still isn't recognizing my phone in download.
Click to expand...
Click to collapse
With the USB unplugged, open the Windows Device Manager again and then plug the device back in.
If the phone is being detected, you should be able to see the Device Manager refresh a few times as the PC adds the device drivers.
By the way... The latest Samsung USB Drivers is v1.5.65.0
If not, then it's either your phone or the USB cable.
I have an S5 G900V that can use either a USB 3.0 or the standard Micro USB 2.0 but, I had to go through several USB cables till I found one that worked properly in download mode (to add... All but 2 of the USB cables were new/newer ones).
There's certain devices (especially the newer ones) that are extremely picky regarding the USB cables being used because, if the Data Transfer between them are not good enough, the device will either not be appropriately detected or error out as a panic type of reaction from the device.
I hope I explained this okay via text...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
With the USB unplugged, open the Windows Device Manager again and then plug the device back in.
If the phone is being detected, you should be able to see the Device Manager refresh a few times as the PC adds the device drivers.
By the way... The latest Samsung USB Drivers is v1.5.65.0
If not, then it's either your phone or the USB cable.
I have an S5 G900V that can use either a USB 3.0 or the standard Micro USB 2.0 but, I had to go through several USB cables till I found one that worked properly in download mode (to add... All but 2 of the USB cables were new/newer ones).
There's certain devices (especially the newer ones) that are extremely picky regarding the USB cables being used because, if the Data Transfer between them are not good enough, the device will either not be appropriately detected or error out as a panic type of reaction from the device.
I hope I explained this okay via text...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks, I will update to the latest drivers that you've pointed out here. I realize that the comm standard is different between Download, Recovery and MTP. I'm pretty sure it's not the cable as it worked in Download just 48 hours ago when I ran Odin for my original root. I will retest everywhere after updating to that driver set. I'm worried that something has changed with the bootloader and I'm unsure how to get it back unless I can find a way to successfully restore from my Titanium backup without root?
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Delete the drivers you have installed, boot into fastboot and have Windows automatically detect and install for you. Have you tried that? What source did you get your fastboot drivers from?
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Msmdownload drivers are not the same at all, they are Qualcom drivers. Uninstall your fastboot drivers and let windows install them
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Oh man, I had issues getting my 6t to connect to my PC when I first got my 6t. The answer for me was to plug my phone into a USB 2.0 port on the BACK of my PC instead of the front USB ports my PC has. Try using the back USB ports and let me know if that works for you!
Thank you all. I will try these suggestions later today and report back.
I tried the suggestions and still no success in fastboot connecting with my device. Thanks again for the suggestions.
After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10:
wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved.
Thank you all!!!
jullev said:
After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10:
wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Click to expand...
Click to collapse
Thank you! I can't believe I didn't think to check that.
it is solved for me oneplus 6t not recognized in fastboot
{ solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty).
i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%,
so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally
good luck
hichemkanon said:
{ solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty).
i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%,
so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally
good luck
Click to expand...
Click to collapse
Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP?
Thank you.
phaino00 said:
Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved.
Thank you all!!!
Click to expand...
Click to collapse
Did this and still not able to recognize it in fastboot mode
sonice43 said:
Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP?
Click to expand...
Click to collapse
Rijul30 said:
Did this and still not able to recognize it in fastboot mode
Click to expand...
Click to collapse
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Really need help. I'm going in circles and wasting a lot of time:
I'm attempting to root a OP6T A6013. Its already been unlocked.
My device is recognized when powered up as an ADB device.
But when i boot into the bootloader it isnt recognized as a fastboot device, and my laptop (Win 8.1) shows ""device malfunctioned. USB not recognized". I've also been trying to install the OP driver but I'm not sure its working correctly. But would that cause the problem with recognizing fastboot?
I've root my OP7Pro (twice, actually) and though I had some driver issues then eventually figured it out. But I never had issues with fastboot.
Any tips or direction?
Hey all , replying to share my solution to this exact problem I was having..
My OP6T (T-Mobile converted to international) was not showing in fastboot devices but showed in ADB.. after hours of searching google and XDA , I ended up just plugging my 6T into another computer and it worked! , instantly recognized my device without hassle.
So just a fyi, it could be something simple as switching USB ports or even another computer.
hopefully this helps if someone get's stuck at this point.
I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.
OhioYJ said:
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Click to expand...
Click to collapse
sudo fastboot oem unlock worked in linux in first shot while windows was unable to recognize the device.
Thanks a ton.
EDIT : Just to add .. this linux was in VM
OhioYJ said:
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Click to expand...
Click to collapse
I agree. Linux is far better when flashing android phones
anonymoustl said:
I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.
Click to expand...
Click to collapse
This worked for my OnePlus 9 Pro running Windows 10. Happy modding!