Had a good look around but don't seem able to find the answer
My daughter has an unrooted Nexus 7, for which the pass number has been forgotten
Have tried to hard reset to no avail, have used the standard methods shown on the net
The thing goes to a google logo or just freezes whether I connect to pc or not
Have downloaded nexus 7 toolkit, but cannot install drivers (option 1)
Have downloaded pdanet to install adb/fastboot, but it tell me its unable to tether
Remember that I am unable to get onto the tablet so I am unable tick usb debugging
When I connect the device, the autoplay option opens, however using "open device to view files" is empty
Finally, I can follow instructions but don't have a clue what most of it means, so be gentle
Any help appreciated
How long have you let it sit at the logo?
Sent from my Nexus 7 using Tapatalk 2
Over 5 minutes, it then goes to the log in number square
had another go, pressed power button when in recovery screen, went to google logo then an android with red warning triangle, then back to log on number pad
I'm not sure when this problem first appeared. For whatever reason, my phone doesn't show up at all when connected to either of my two PCs. It must have when I first rooted the phone (to load ChainSU) but I'm not sure if the problem is recent or occurred immediately thereafter.
USB debugging is disabled. When I plug my phone into a computer, it attempts to install the MTP Driver and fails. When I uninstall my device, it disappears and I'm unable to manually install the driver's I've downloaded from other threads. When I load into the Bootloader, my device is recognized by Fastboot.
I'm hesitant to factory reset as this will leave me unable to root if the problem persists, which is important to me as I can get rid of the yellow tint on this screen.
Any thoughts?
Edit: $10 via Paypal for anyone who successfully helps me to a solution!
Are you definitely sure usb debugging is disabled? The phone should install as a portable device on your pc. Also ensure to enter your password onto your phone when connected otherwise the phone will not show up its contents.
Make sure for windows media player to be updated to the latest, for the windows mtp driver.
duraeas said:
I'm not sure when this problem first appeared. For whatever reason, my phone doesn't show up at all when connected to either of my two PCs. It must have when I first rooted the phone (to load ChainSU) but I'm not sure if the problem is recent or occurred immediately thereafter.
USB debugging is disabled. When I plug my phone into a computer, it attempts to install the MTP Driver and fails. When I uninstall my device, it disappears and I'm unable to manually install the driver's I've downloaded from other threads. When I load into the Bootloader, my device is recognized by Fastboot.
I'm hesitant to factory reset as this will leave me unable to root if the problem persists, which is important to me as I can get rid of the yellow tint on this screen.
Any thoughts?
Edit: $10 via Paypal for anyone who successfully helps me to a solution!
Click to expand...
Click to collapse
There are a few things you can try. Have you tried uninstalling the drivers completely then reinstalling from the toolkit? In the past, I've had issues where the phone wouldn't be accessible in some way on one computer but would be fine on another, so maybe try a different computer to try to narrow down the problem as to whether it's an issue with the phone or the computer? Also, this may sound a bit ridiculous, but simply switching USB cables and / or ports has fixed detection issues for me in the past as well--something to consider.
Sent via Morse code from my Nexus 4
Remove any existing drivers (while phone is connected), do the same for other android devices if you have any, then reboot and install Universal Naked Drivers. Have always had success with this driver pack.
Rizy7 said:
Are you definitely sure usb debugging is disabled? The phone should install as a portable device on your pc. Also ensure to enter your password onto your phone when connected otherwise the phone will not show up its contents.
Click to expand...
Click to collapse
100% sure on both counts.
I have this same issue with my rooted nexus 4, I've tried 3 different computers and several cables and it never connects to the PC and only charges the phone. It doesn't even give me option to choose media files.
I've had this issue before, my Nexus/Computer was acting in complete stupidity. When connecting the phone to your computer you will see a notification saying "Connected as a media device" on your phone, just touch it, and change it to "Camera (PTP)". It might access the camera for you, but It actually accessed the storage for me.
YeledKaki said:
I've had this issue before, my Nexus/Computer was acting in complete stupidity. When connecting the phone to your computer you will see a notification saying "Connected as a media device" on your phone, just touch it, and change it to "Camera (PTP)". It might access the camera for you, but It actually accessed the storage for me.
Click to expand...
Click to collapse
Thats not the problem, it doesn't give any option. It doesn't show up on the computer at all and only charges. It's the same for every computer.
yuriorkis said:
I have this same issue with my rooted nexus 4, I've tried 3 different computers and several cables and it never connects to the PC and only charges the phone. It doesn't even give me option to choose media files.
Click to expand...
Click to collapse
I'm thinking we've screwed something up with the phone's side of the MTP protocol - mine is totally independent of the cord/computer used. All the correct drivers installed.
Have you tried Factory Resetting? I'm really hoping this is a workable option.
If you have a recovery back up the current Rom and flash stock and see if it's working
Sent from my KFTT using xda premium
if the phone is locked with a pin/password/pattern unlock it.
I had same problem on my pc yesterday. Even if the drivers installer showed up that installation was successful, somehow for a mtp mode system was using some other Microsoft driver. Correct one was only used in ptp mode. So when I connected n4 in mtp mode storage wasn't available, when I switched to ptp mode everything was fine. Turn on your usb debug, switch on mtp and connect. Go to device manager in system, find your nexus there and rmb on it and manually reinstall driver. After this my n4 is visible in system in mtp mode again.
Sent from my Nexus 7 using Tapatalk HD
my screen is cracked and phone is useless now (replacement coming tomorrow) can i connect it and wipe it back to factory before i have to send it out?
K0v4L said:
I had same problem on my pc yesterday. Even if the drivers installer showed up that installation was successful, somehow for a mtp mode system was using some other Microsoft driver. Correct one was only used in ptp mode. So when I connected n4 in mtp mode storage wasn't available, when I switched to ptp mode everything was fine. Turn on your usb debug, switch on mtp and connect. Go to device manager in system, find your nexus there and rmb on it and manually reinstall driver. After this my n4 is visible in system in mtp mode again.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
The problem is that even if I switch between MTP and PTP it still does nothing, I have tried multiple cables, computers and have reflashed the ROM and wiped the device but it still does not connect with the PC. This is frustrating.
yuriorkis said:
The problem is that even if I switch between MTP and PTP it still does nothing, I have tried multiple cables, computers and have reflashed the ROM and wiped the device but it still does not connect with the PC. This is frustrating.
Click to expand...
Click to collapse
Is yours able to connect during Bootloader/Recovery? Fastboot/ADB have no trouble recognizing my device.
It's really odd that if these things work, meaning your USB connection is fine, replacing the all of software fixed nothing... unless MTP occurs at a much lower level of the OS (maybe kernel is corrupted?)
I've got a similar problem that others have posted - PCs not detecting my N4. I got it last Friday (2/1) from Google and after the registering process and updating to 4.2.1, I connected it to my Win7 laptop and it showed on the PC as a drive. But since I couldn't copy/paste Office docs to that drive and had to do that through Dropbox, I didn't bother trying to reconnect until Monday, at which time the PC didn't detect it. Neither will one other Win7 nor two XP (both with WMP10) PCs. Have tried multiple cables, all of which work with other Android devices (pre 3.0). I've seen several suggestions on this and other threads, but one major issue I'm having is that some of the fixes require enabling USB Debugging. For the life of me I can't find that option in the N4's Settings. Unlike my other phones, there is no Applications subcategory under Settings on my N4 (4.2.1, Build JOP40D). Can anyone help me find that option? TIA.
Edit - Found answer. Click on Build in About Phone setting 7 times. That activated Developer options. Now to try the fixes which require USB Debugging mode turned on.
I recently bought a refurbished 2012 Nexus 7 on 4.2. The only things that I have done on the phone are entering my Google account details and downloading a single app (papyrus). I then clicked to install the automatically downloaded software update (it downloaded 4.3), and after restarting the tablet was stuck on the Nexus X boot animation forever. Factory reset/cache wipes do not help.
I found drivers for the phone to be recognized while showing the X, and I found drivers for the phone to be recognized after selecting the a "apply update from ADB" option from stock recovery. However Windows does not recognize the phone at all in recovery mode before selecting that option. Nothing changes in the device manager when plugged/unplugged. Windows doesn't attempt to install anything. It's as if I unplugged the cord once it enters recovery from the bootloader. I assume USB debugging is off, because it would be at the default setting. I tried using the Flash Stock + Unroot option in the Nexus Root Toolkit with the Soft-Bricked/Bootloop setting in, but that fails in both normal recovery (with the device unnoticed) and sideload mode. I'm guessing that debugging needs to be on for this?
Does anyone have any suggestions for other things to try? I have no way of knowing what the original owner may or may not have done, and this was the first time that I restarted the device, so I have no way to know if the problem was caused by the OTA or not.
EDIT: It looks like I made the situation worse. I attempted running the Flash Stock + Unroot option from the bootloader. I am not sure what happened, but now the device starts at the Google page with green start in an arrow. I have the bootloader options, and start and recovery options give me a "booting failed" message in the top left and just stay on the google page. Restarting the bootloader gives me the normal bootloader android image and the options have the same effects.
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
wioneo said:
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
Click to expand...
Click to collapse
still have a problem?
Wrong drivers, try other USB ports. Had that happen with another tablet. Only recognized in adb side load with galaxy nexus driver loading, possibly from universal adb drivers... Switched to a port on the other side and correct drivers finally worked.
Sent from my Le Pan TC1020 using Tapatalk
norwoodesteel said:
still have a problem?
Click to expand...
Click to collapse
As far as I know, no. I was never able to get the device is to be detected by my computer while in stock recovery mode, however it was detected after I flashed ClockworkMod Recovery. So I still have no idea what was causing that problem, but it is no longer relevant.
Hi!
My Nexus Player was rooted, but this was messed up by a recent OTA update (not the current 7.1.1, but the last one before that I guess), after which I factory reset it. I don't really remember if I tried connecting it to my PC then or do something else. A while later I tried rerooting with Nexus Root Toolkit, but there were some issues with the ADB drivers I think, it didn't maintain a connection with the computer during fastboot. It also kept resetting the USB default to charging (I chose MTP, but it just kept switching back by itself). So I took a break for a while and now it won't connect to my computer at all except for a brief moment while booting. All during this I've tried different cables and actually two more computers, but the issue persists. The bootloader is still unlocked and factory resets don't help. Does anyone have any idea how to solve this?
Best regards,
Mikk
re enable debugging? The flip back to Charging from MTP is by design I think...as is the inability to shut off auto update. Google trying to save us from ourselves. Have you flashed twrp? I found the only way to see the player on the desktop was when booted in twrp. Otherwise, like you , it appeared the player wasn't connected. I do believe I was still connected as a fastboot device though.
I haven't bothered to re root as my SD card is supported and kodi installed from the play store removing any need to sideload or file explorer my way to install apps. I have found the 7.1.1. update to be solid/stable with no issues.
Hi all,
I am having a slight dilemma with my UK Note 4 N910F. I broke my screen while trying to replace my rear camera (long story). Now I have a phone that still works apart from the screen is dead.
My next problem is my phone is stock, USB debugging not enabled and has a password/fingerprint lock on it. The fingerprint lock won’t work due it being the first time the phone gets turned on after a restart it doesn’t work. I have looked into “recovering the data from it” for quite a few days now, and am at a dead end.
I first downloaded Android Control & Droid Screen and finally got them to work after having a windows 10/java nightmare.*
Downloaded and installed SDK platform tools and ADB drivers and to no avail it still would recognise my phone in “adb devices” so I thought this must be because USB debugging isn’t enabled.
I then installed Samsung Odin 3 and flashed Clockworkmod recovery which I believe has worked fine.
Still “ADB devices” nothing listed.
I then downloaded Dr.Fone (trial version) and started the data recovery and pulled my phone half way through. Which leaves it in recovery mode. Closed Dr.Fone reconnect my phone and I can get adb devices to show a “serial number recovery” listed.Droid screen detects my device but says its offline, and I can power on/off reboot etc my phone through android control.
If I reboot my phone then I lose recovery and droid screen/adb/android control wont work anymore.
Is this because it is resetting USB debugging enabled option?
Is there anyway when im in recovery mode I can enable USB debugging and keeping that setting if my phone is reset?
Any advice would be great.
Regards Jim