I've got debugging enabled, have tried literally all the connection options, multiple computers, etc. I just want to back up and root my phone. I'm at the point that I'm willing to try a factory reset and pray that works. Is there anything else I can do before that?
Do you have device drivers installed on your computer? Does adb/installed properly? Is OEM unlocking ticked? If its a driver issue update them. If its adb download the minimal adb from XDA. Otherwise that's it.
Device drivers are installed and OEM unlocking is ticked. I'm working on updating adb/fastboot.
Alright, everything is updated as much as it can be, and still nothing. No recognition whatsoever.
What version of windows are you running?
I had to do this to get mine to work... go into the device manager on Windows, find the Nexus, right-click and choose update driver software. Browse to where the driver is located on your PC and select the folder.
Related
Hi XDA. I have a problem and could use your help.
In order to make flashing ROM’s easier for myself I thought it would be a good idea to place them in the first folder listed on the internal sd card. In order to do this I placed a “.” befor the name of the folder. After wiping everything I learned CWM 5.8.1.8 (touch) does not see folders with dots(“.”) at the beginning. So I now am in recovery with no ROM to flash
I then proceeded to dig an even deeper hole for myself. In my attempts to install drivers for my device I have done something; now my computer fails to recognize that the device is plugged into the USB at all. Prior to my messing with it I would hear the USB input chime and Device Manager would show an “unknown device”. Now when I plug in my device nothing happens. I have tried two computers and both Win7 and Ubuntu.
I read that Linux might be able to see my device so I installed Ubuntu then the Android SDK as per this thread. It did not work for me. I still cannot see my tf101 but I can see my Nexus s with the “adb devices” command.
I bought my tf101 refurbished and can’t find the “B” version written on the device. I think I initially rooted with razorclaw...not %100 sure. I am not sure adb debugging was checked when I wiped...not sure it makes a difference at this point.
I am now looking at these NvFlash instructions but I can’t get past the 2nd step (I am a noob...obviously)
- run “./blobunpack recovery-clockwork-5.8.2.1-tf101.img” (Replace “recovery-clockwork-5.8.2.1-tf101.img” with the name of your downloaded file”)
Will this NvFlash tutorial work if the computer can’t see the device?
Any ideas?
Thanks for your time!
Try those steps from this website Reverting to Stock ROM (unroot and remove CWM recovery)
this is easier for you when u try to nvFlash your tf101. remember update driver, run as administrator on program
Thanks for the info!
I am away until tomorrow evening. I will try it then.
Hi,
I am still having problems.
Can I install drivers if the device is not listed in device manager? How?
Thanks again!
it will be reinstall or request when you unplug and plugin back your connect from tablet to PC
if your driver had been load or connected just go to Devices and Printers to check your connection, after that update your driver
Hi. Thanks for trying to help.
My problem is my computer is not seeing the device at all. No USB input chime. Nothing showing up in device manager. No nothing!
Could be the chord I guess but I don't think so. I was getting "unknown device" in device manager initially after I wiped the ROM. After attempts to install drivers I stopped getting any sign of the tf101 in device manager.
Hi guys,
after unocking bootloader and so on, i cannot connect the n4 as a media device. camera (ptp) and debugging works, but not mtp.
already wiped everything
someone can help me?
I had the same problem. Had to remove the Google drivers I installed to get fastboot (do this via device manager, make sure to tick the box to delete the driver files as well else it will just reinstall them)
1.Delete the Device from device manager.
2. Grab the naked drivers in teh dev forum and install them.
3.???
4.Profit
i don't think it's a driver problem, i have the same issue on both w8 and ubuntu
someone else wanna try?
If you turn off USB debugging, media device mode works.
Nexus4, Tapatalk
tyea said:
If you turn off USB debugging, media device mode works.
Nexus4, Tapatalk
Click to expand...
Click to collapse
already tryed, but still doesn't work.
also tryed to relock bootloader, unroot, but nothing.
now i'm switching back to windows7, i'll see if it will work
solved getting rid of windows8 and going back to windows7
I cannot get my adb to work because I never get the box that pops up asking if I want my computer to trust this phone. Have switched from mtp, ptp, etc...have revoked usb debugging authorizations, and I have toggled adb on and off.
I have a oneplus two that works fine and I have had a nexus 5x that was fine and even when I first got my 6p it worked. I just downloaded android sdk for the newest platform tools and I flashed new images for the phone.
need help
thanks
Try installing HiSuite
chichu_9 said:
Try installing HiSuite
Click to expand...
Click to collapse
Doesnt do anything...that program says something about being offline...try unplugging and all that...over and over
very frustrating...ive tried everything, different cables, all of it.
Lets start over.. Make sure, you remove all drivers from your PC. Uninstall HiSuite and restart
Now install HiSuite and launch the program before you connect your phone to your PC, Click on the button that says "Hot to connect phone for Android 4+" follow the onscreen instructions.
All along ADB was working fine. Now when I enabled it, nothing is detected on the computer. The phone went entirely missing. If I turn it off, the phone comes back. Anyone encountered this?
With ADB turned off
- Phone works in PTP Mode to PC
- Phone works in MTP Mode to PC
- Phone works in MIDI to PC
With ADB turned on
- No phone device detected at all. So I am not even able to change to any of the ADB drivers
mobileman88 said:
All along ADB was working fine. Now when I enabled it, nothing is detected on the computer. The phone went entirely missing. If I turn it off, the phone comes back. Anyone encountered this?
With ADB turned off
- Phone works in PTP Mode to PC
- Phone works in MTP Mode to PC
- Phone works in MIDI to PC
With ADB turned on
- No phone device detected at all. So I am not even able to change to any of the ADB drivers
Click to expand...
Click to collapse
What do you mean by "ADB turned off" and "ADB turned on"?
Are you talking about USB Debug?
Sent from my interstellar 6P
CyberZeus1977 said:
What do you mean by "ADB turned off" and "ADB turned on"?
Are you talking about USB Debug?
Sent from my interstellar 6P
Click to expand...
Click to collapse
Yes, USB debug in development menu, even turning it on/off, revoke does not seem to make it work again. it just does not show up on my PC.
Further tests done.
Fastboot works.
Adb works in recovery mode when booted into TWRP 3.0.2-3.
Think I need a way to reset the ADB /usb debug settings within the phone as it looks more and more to be an issue from the phone rather than Windows (v7 x64 sp1)
mobileman88 said:
Further tests done.
Fastboot works.
Adb works in recovery mode when booted into TWRP 3.0.2-3.
Think I need a way to reset the ADB /usb debug settings within the phone as it looks more and more to be an issue from the phone rather than Windows (v7 x64 sp1)
Click to expand...
Click to collapse
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
v12xke said:
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
Click to expand...
Click to collapse
Shall give it a whirl. Previously it was incorrect driver issue years ago but everything has been working fine on all my Android devices till yesterday when I can't seem to ADB to my 6P. I have the latest USB drivers installed via Android SDK Manager.
v12xke said:
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
Click to expand...
Click to collapse
Still no go. There's no device at all where I need to change/delete/update driver if I turn on ADB USB mode. Phone is only seen by Windows Device Manager when I turn off USB debugging in developer menu. I still feel it might well be something in the developer menu causing this issue.
I am checking on the folder /data/misc/adb . Permissions is rwxr-s--- . What's the permissions you have for this folder?
Using USBDeview (trying to compare between 2 sets of 6P, both with the December 7.1.1 roms)
6P that works over ADB
Reported VID and PID is 18d1 / 4ee2
6P that does not work over ADB
Reported VID and PID is 18d1 and PID is 4ee1, 4ee5 and 4ee8 depending on which mode (PTP/MTP/MIDI).
Nothing gets reported to be connected at all when I used USBDeview while the 6P that does not connect over ADB USB has USB debugging turned on.
Problem fixed. No idea what was the cause. Hopefully it will help someone else who gets this down the road.
Steps performed
- Clean up SU
- Reboot
- No go
- Reboot to Recovery
- Reflash EFS backup
- Reboot
- No go
- Reboot to recovery
- Clear cache, clear dalvik
- Reboot
- No go
- Reboot to fastboot
- Reflash System, Vendor, Boot
- Reboot
- Works
- Reflash Magisk and PHH
- Still works
Puzzling.
Glad you got it fixed.
v12xke said:
Glad you got it fixed.
Click to expand...
Click to collapse
Yeah, would have done a full factory reset if all else fails since the hardware was indeed able to connect to my PC properly. Glad the various flashing worked out.
I have my phone on bootloader mode, and "Android Bootloader Interface" is listed there. Even if I install the Samsung driver of the same name, it still says "no drivers are installed for this device". Fastboot commands won't work even though adb works perfectly fine
AOSP100 said:
I have my phone on bootloader mode, and "Android Bootloader Interface" is listed there. Even if I install the Samsung driver of the same name, it still says "no drivers are installed for this device". Fastboot commands won't work even though adb works perfectly fine
Click to expand...
Click to collapse
Update: Replacing the Google drivers (ADB, bootloader, etc) with Samsung ones in device manager broke everything so I had to reinstall the Samsung USB drivers, and uninstall platform-tools and the Google drivers through Android Studio
Adb/fastboot drivers work with Samsung drivers, not against.
Install both, don't set a preferred driver.
After that connect your phone while it's active on the main OS, the Samsung drivers will then properly install for your device.
Once the set-up is finished, boot into fastboot and plug your phone in using USB.
You computer should install generic drivers or specified bootloader drivers.
ninjasinabag said:
Adb/fastboot drivers work with Samsung drivers, not against.
Install both, don't set a preferred driver.
After that connect your phone while it's active on the main OS, the Samsung drivers will then properly install for your device.
Once the set-up is finished, boot into fastboot and plug your phone in using USB.
You computer should install generic drivers or specified bootloader drivers.
Click to expand...
Click to collapse
The driver issue was fixed by turning USB debugging back on, as I forgot to after I tested the validity of that done to death method to enable the OEM unlocking option, of setting the clock a week back and all, which my prediction was right of it being complete garbage. ADB now detects my device again and I'm able to reboot into the bootloader, but fastboot still does absolutely nothing
AOSP100 said:
The driver issue was fixed by turning USB debugging back on, as I forgot to after I tested the validity of that done to death method to enable the OEM unlocking option, of setting the clock a week back and all, which my prediction was right of it being complete garbage. ADB now detects my device again and I'm able to reboot into the bootloader, but fastboot still does absolutely nothing
Click to expand...
Click to collapse
Yeah, sadly the a205u will probably never get root or custom ROMs. We have an extremely small chance since Samsung promised two major updates for the A20.
Either way, https://forum.xda-developers.com/android/software/tool-universal-fastboot-adb-tool-t3475832/amp/
Has the fastboot drivers if you haven't tried that one yet.
.