Develop Bugs

HELP my GNex stuck up on Google LOGO ADB doesnt work or computer wont recognize gnex

Yesterday at work while my phone is charging it just suddenly went to google screen and i waited for about 5-10 mins and still there, i thought its a minor problem...take out the battery and still stuck up, i went to recovery and accident wipe everything. My main problem is i have a Samsung Laptop and it wont recognize my phone, ( it will recognize for a second when i turn on my phone going to google logo and it will say device is malfunction etc etc. it will also recognize for a second going to recovery mode when pass the google logo and again it will say malfuction ) I tried ADB, but wont recognize my device because of the computer? I tried ODIN but still my device wont recognize by my computer. I tried Gnex tool kit, Rootkit and heres my device manager looks like
I hope someone can help me.

That looks like a problem with the drivers you have installed on your computer. It should show up under Android Phone and then have Android ADB Interface (or Samsung Android ADB Interface). Try installing the drivers from here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mwalt2 said:
That looks like a problem with the drivers you have installed on your computer. It should show up under Android Phone and then have Android ADB Interface (or Samsung Android ADB Interface). Try installing the drivers from here.
Click to expand...
Click to collapse
I download it and how can i use this one?

benjiebench said:
I download it and how can i use this one?
Click to expand...
Click to collapse
Install samsung kies.you just need driver from kies. Dont open samsung kies when you want to use adb.
Sent from my GT-I9300 using xda premium

Samsung kies on a Galaxy Nexus ??? Put the phone in adb mode and manually install the ADB interface drivers from the google SDK. You will need to uninstall and erase all previous drivers from the device manager and then install the .inf from the sdk
Sent from my Nexus 4 using xda app-developers app

ADB not seeing N7...

Yea. That.
Drivers seem good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can get into it from the computer.
I've tried different cables.
I've tried every USB port on my computer.
I can unplug the cable from the N7 and go directly into my N4, adb devices it, good to go.
I've noticed that, on my N4, I plug it in and I can get into it through Windows Explorer AND it shows up on ADB. On the N7, if USB Debugging is checked, I can't get into it through Explorer or ADB. If I uncheck it USB Debugging, Windoze does its little unplug noise, then the plug in noise and I can get into it. Is this a 4.3 thing?
Has anyone else had this happen? Is this a bug or am I the bug?
Any help greatly appreciated. Thanks!!

I don't have an N7 2013 (thinking about getting one though ) but passing on something a friend told me about her older N7 model: it didn't allow ADB while MTP was enabled. So you might try disabling that and seeing if it helps.

Maybe you have some permission problem and need to run the shell as administrator. It looks like the tablet was recognized from a driver standpoint.

Are you sure that's the right driver? It says Android Phone/Google Nexus ADB Interface.
Seems like you have the drivers installed for your N4 but not your N7.

Geodude074 said:
Are you sure that's the right driver? It says Android Phone/Google Nexus ADB Interface.
Seems like you have the drivers installed for your N4 but not your N7.
Click to expand...
Click to collapse
Yours says something different? Mine says Android Phone and I don't think I've seen it say anything else, whether phone or tablet were connected.

I'm having the EXACT same problem and it's driving me nuts, my Device Manager says Google Nexus ADB Interface
EDIT: Solved it, go to settings > Storage > click the menu on the top right and select USB connections > Select PTP instead of MTP.

w0ng3r said:
I'm having the EXACT same problem and it's driving me nuts, my Device Manager says Google Nexus ADB Interface
EDIT: Solved it, go to settings > Storage > click the menu on the top right and select USB connections > Select PTP instead of MTP.
Click to expand...
Click to collapse
If you want to get it working with MTP and USB debugging enabled see this post:
http://forum.xda-developers.com/showthread.php?t=2391236

aletthi fess
I'd just like to throw in that I was having the same issues with ADB and the only time I got it to work was after I disabled MTP/PTP on the phone. Im sure there are better fixes in this thread but thats my two cents.

After updating to the latest driver version 8.0 it should say "Android Composite ADB Interface".

I'm having the same problem and it's driving me crazy!!! This is funny longest I've EVER went without rooting, assuming root was available for that particular device. I'm gonna try disabling both MTP and PTP, like mentioned earlier.
Sent from my '13 Nexus 7 using XDA Premium HD app

ADB does not work when using MTP with USB debugging

When I use the MTP mode with USB debugging, the list of devices attached in adb (Command:adb devices) has nothing on it.
However, the PTP mode with USB debugging works with ADB. The system will show the dialog with the RSA-key of my computer and ask me to "Enable USB Debugging" when I change the connection type from MTP to PTP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any solution that using ADB with MTP mode? Thanks a lot.:laugh:

I'd blame the drivers on the system. Remove all and reinstall them, using least amount of drivers first. I had the same issue.

This posting may be of interest to you in fixing the problem. http://forum.xda-developers.com/showthread.php?t=2391236

That thread is actually the reversed problem. MTP only works with USB debugging turned on.
I think OP is saying USB debugging is only working with MTP turned on.
My guess is old driver issue. Use Device Manager to remove device *and* remove drivers, then reboot, then install latest Google USB drivers.

sfhub said:
That thread is actually the reversed problem. MTP only works with USB debugging turned on.
I think OP is saying USB debugging is only working with MTP turned on.
My guess is old driver issue. Use Device Manager to remove device *and* remove drivers, then reboot, then install latest Google USB drivers.
Click to expand...
Click to collapse
I believe he has the same issue I have MTP + USB debugging does not allow adb to work. However, keeping USB debugging on and switching to PTP (the camera mode) does allow adb to see the nexus 7 and pop-up the authorization prompt. I've uninstalled the drivers many times trying to get adb working when using MTP and USB debugging, but it never, ever takes. Must be something in the system config, not the driver.

Is this the stock ROM?

sfhub said:
Is this the stock ROM?
Click to expand...
Click to collapse
Yes, I have updated to JSS15R.

This is just a drivers conflicts..its really annoying just keep configuring

true. when mtp or ptp, your nexus is not treated as an android machine any more
Sent from my Nexus 7 using XDA Premium 4 mobile app

Pls help a noob! My PC don't recognize my Redmi Note 8 in Fastboot-Modus

Hello my dear Friends
I am struggling with unlocking my phone.
Phone-Model: M1908C3JGG
First, what I have done:
Allow the bootloader to be unlocked (in dev. options)
Set the USB debuggin to ON (in dev. options)
Downloaded the Adb-Tool & drivers and install it and set the variables.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I start the Phone in Fastboot-Modus, my PC don't recognize the device.
What I have be done wrong?
Sorry for my newbienes XD

You need to manually update the driver in device manager, try the below one. If it says installation failed due to unsigned drivers, then disable signature verification in your PC and try install again

hmd_msrf_k said:
You need to manually update the driver in device manager, try the below one. If it says installation failed due to unsigned drivers, then disable signature verification in your PC and try install again
Click to expand...
Click to collapse
It still don't work.

Right click on Android Bootloader Interface
Then connect your phone to the computer
Click on update driver
Select Browse my computer for drivers.
Then select Let me pick from a list of available drivers on my computer
Click Next and let it complete

If you still face any issue download updated adb and fastboot drivers
ADB and FASTBOOT DRIVERS

I get this error message:
It means This device cannot start. (Code 10)
Updated also not help.
Is this always so difficult on Windows?

hans12312!! said:
I get this error message:
View attachment 5465485
It means This device cannot start. (Code 10)
Updated also not help.
Is this always so difficult on Windows?
Click to expand...
Click to collapse
No it is not. Uninstall the Android Bootloader drivers and restart your computer. Restart using restart button
Then connect your phone and see if it solves your problem.

mvikrant97 said:
No it is not
Click to expand...
Click to collapse
Your words make my a little more optimistic

hans12312!! said:
Your words make my a little more optimistic
Click to expand...
Click to collapse
Try this one, i'm used this in in my Windows 8 and it worked perfectly, it should work in Windows 10 too.

thanks to mvikrant97 I can now unlock my phone.
My Rzyen 5 3600 CUP had some issues with the driver. We used the "AMD Ryzen USB controller fix.zip".
A known Error https://forum.xda-developers.com/t/fix-fastboot-issues-on-ryzen-based-pcs.4186321/

Question USB tethering

Any way to disable Samsung's 'cable detection' feature? USB tethering doesn't work because device doesn't recognize cable. I'm using original one and tried new and older cables also. I've had similar problems with another Samsung devices before and it's pretty annoying. WIFI is too slow and bluetooth even slower compared to USB so I don't like using them. Device just keeps telling use original cable and starts charging slowly.
Also the usb c port is cleaned, tried restarting device several times, tried all usb ports of my pc. I'm using Windows 10 pro. All drivers are updated and I have newest Samsung drivers.

Turn on Developer options and try setting it up there. No blocked or disabled Samsung system apps, right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

blackhawk said:
Turn on Developer options and try setting it up there. No blocked or disabled Samsung system apps, right?
View attachment 5713053
Click to expand...
Click to collapse
Tried that but it doesn't work. Also Windows is saying it can't recognize usb-device. I have disabled YouTube only because I use another app for that.

Slixy said:
Tried that but it doesn't work. Also Windows is saying it can't recognize usb-device. I have disabled YouTube only because I use another app for that.
Click to expand...
Click to collapse
Hit take no action in the Windows connect popup*. Then go to Disk Management and punch scan for new devices. Access the drive in that window and do the transfers there. Command line can also be used to access Disk Management etc.
Try rolling back or updating the driver. Installing the latest version of SmartSwitch on Windows should load the correct driver.
*you must authorize the connection first on the Android via a popup window that should appear after being connected.

Not working. Reinstalled all usb drivers including Samsung ones. Smartswitch is not working because Windows can't recognize this device at all. Maybe I just reinstall Windows some day and try if it works then. Thanks for the help.

Slixy said:
Not working. Reinstalled all usb drivers including Samsung ones. Smartswitch is not working because Windows can't recognize this device at all. Maybe I just reinstall Windows some day and try if it works then. Thanks for the help.
Click to expand...
Click to collapse
You're welcome.
Try another port and cable.
Reboot, always reboot Windows.
Check Event Viewer for error messages.
For Windows to recognize the device you sometimes need to use the scan for new devices command in Disk Management. The solution is likely simple and right in front of you.
Play with it... fun times.