Nexus 7 wont connect to computer via MTP - Nexus 7 (2013) Q&A

When I connect my Nexus 7 to my windows 7 computer it is not recognized in MTP, but is when I change it to PTP. When I connect my 1st gen Nexus 7 to the same computer it is recognized fine and I am able to transfer files. I have all the drivers installed and adb works when I am in PTP I just cant transfer any files. Has anyone else experienced this problem or is there maybe something wrong with my Nexus?

Check out this thread. I was experiencing similar issues although I didn't test out PTP .
Sent from my Galaxy Nexus using xda app-developers app

Disregard. I figured it out. It was a driver issue after all.

How did you fix it? I have the same problem. Is root needed to view transfer files via USB?

My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?

lucastmw said:
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
Click to expand...
Click to collapse
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium

jmileti said:
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I tried it with debugging on and off.

thaliagoo said:
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
Click to expand...
Click to collapse
Root is not needed to transfer files via USB. I just uninstalled the previous driver and updated to the latest and that worked for me.

No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.

thaliagoo said:
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
Click to expand...
Click to collapse
These are the drivers I used... http://developer.android.com/sdk/win-usb.html

fixed mine by just forcing it to reinstall the drivers.

fstbusa said:
fixed mine by just forcing it to reinstall the drivers.
Click to expand...
Click to collapse
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.

dirtyfingers said:
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
It is definitely a driver issue. I had to uninstall my drivers and then manually install others, because I had a Nexus 7 2012. Those drivers were showing up as *up to date* according to windows, but the device was not working. Total clean install worked to correct it.

Xirix12 said:
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
Click to expand...
Click to collapse
In device manager, go to the properties of each android device. I had one near the top of the list and one lower under portable devices. Click update driver and navigate to your updated drivers folder.
It should update them. The device listed under portable devices had mtp as part of the title so I figured that one was the problem.
Sent from my Nexus 7 using xda app-developers app

To anybody who comes to this thread looking for help.
Go to device manager, and under devices remove the Google ADB Driver. This drove me nuts. All of my nexus devices wouldn't connect because they lacked an external SD.
Sent from my Nexus 7 using XDA Premium HD app

I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.

i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it

golfinggino said:
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
Click to expand...
Click to collapse
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.

huizingajm said:
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
Click to expand...
Click to collapse
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.

sfhub said:
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
Click to expand...
Click to collapse
I switched kernels to stock to jassy to tiny. None of them work so it has to be the ROM. I am just going to use WiFi transfer of files. Nothing major right now while everything is still new to 4.3.

Related

Galaxy S3 Will Not Connect To Windows Computer

I am trying to connect my galaxy s3 to my windows computer and it will not install the drivers. Has anyone experienced this yet. I am rooted and running cm9 nightly. I also have a custom kernel installed. This was working when i rooted a couple of weeks ago. When I plug my phone into the usb it searches for drivers and display an error message that say it was unsuccessful at installing drivers. Any help would be greatly appreciated.
Have you tried uninstalling and reinstalling kies? I got a pop up on my phone when i plugged it in last time and it said it couldnt find the software but yet i was able to connect to kies and go into phone through windows.
Sent from my SGH-T999 using Tapatalk 2
Since I got my phone it hasn't connected to my pc. I have the drivers but I get a "hardware id missing" error. I've uninstalled and reinstalled the drivers but it won't connect. Works fine in ubuntu tho. Idk
Sent from my SGH-T999 using xda app-developers app
Uninstall Kies if you have it. And install drivers again. That should do the trick.
Sent from my SGH-T999
crushbox311 said:
I am trying to connect my galaxy s3 to my windows computer and it will not install the drivers. Has anyone experienced this yet. I am rooted and running cm9 nightly. I also have a custom kernel installed. This was working when i rooted a couple of weeks ago. When I plug my phone into the usb it searches for drivers and display an error message that say it was unsuccessful at installing drivers. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I experienced a similar issue, it may have to do with the fact that I didn't wipe cache partition and wiped dalvik cache when installing zip from sd card etc... I don't know what caused it, but nothing I could do (including re-installing drivers a couple of times from KIES and tying it on a different laptop etc.) would fix it until I did a wipe data/factory reset by mistake! (instead of wiping catche partition) ;<( and that seemed to do the job!
Perhaps you may want to try doing a "wipe catche partition" and "Wipe Dalvik Cache" from CWM before tying to go ahead a do a "wipe data/factory reset"?
crushbox311 said:
I am trying to connect my galaxy s3 to my windows computer and it will not install the drivers. Has anyone experienced this yet. I am rooted and running cm9 nightly. I also have a custom kernel installed. This was working when i rooted a couple of weeks ago. When I plug my phone into the usb it searches for drivers and display an error message that say it was unsuccessful at installing drivers. Any help would be greatly appreciated.
Click to expand...
Click to collapse
This occured with me when I was using early build of CM10, the system fails to recognize the MTP and screws the drivers..
I say you revert back to nandroid, and reflash cm9
chrisram88 said:
Uninstall Kies if you have it. And install drivers again. That should do the trick.
Sent from my SGH-T999
Click to expand...
Click to collapse
I have buddy. Several times. And I've never installed Kies. Idk what it even does lol
Sent from my SGH-T999 using xda app-developers app
mikeyinid said:
Since I got my phone it hasn't connected to my pc. I have the drivers but I get a "hardware id missing" error. I've uninstalled and reinstalled the drivers but it won't connect. Works fine in ubuntu tho. Idk
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
have the same problem
I did have that 'hardware ID missing' error suddenly after i was connecting my phone to my laptop just fine. my desktop has no problem. i did a few things that seemed to have fixed it or steps for a solution. I downloaded the TMO Samsung drivers. if you already have it installed, try uninstalling it. If that doesn't work, toggle USB debugging in between connecting and disconnecting from the computer. Other times, toggling USB debugging wouldn't work, so i toggled in between MTP and PTP. i play with a few times til it work. hope that helps. i can't post the link the the drivers yet, but get it from samsung's website.
i'm on gsm r6 and trinity kernel
Since I've gotten the phone I've had to keis air everything. Hardware I'd missing error on every PC/laptop I owned.
Up until yesterday. Plugged it in and keis opened. Connection troubleshooting joppy. It redownloaded and installed drivers. Like if always has...but this time it actually worked and so does my mtp now.
I wonder if its ROM related. Before I was using stock with the problem. The aokp unofficial r6 with the problem.
But now I'm running the official aokp jellybean release and it works.
I dunnnoooooo. Unicorn is mighty!
Sent from my Unicorn powered T999
whatmonster said:
Since I've gotten the phone I've had to keis air everything. Hardware I'd missing error on every PC/laptop I owned.
Up until yesterday. Plugged it in and keis opened. Connection troubleshooting joppy. It redownloaded and installed drivers. Like if always has...but this time it actually worked and so does my mtp now.
I wonder if its ROM related. Before I was using stock with the problem. The aokp unofficial r6 with the problem.
But now I'm running the official aokp jellybean release and it works.
I dunnnoooooo. Unicorn is mighty!
Sent from my Unicorn powered T999
Click to expand...
Click to collapse
I also got mine working last night. But after a reboot I got the same error again. Idk what it means.
Sent from my Galaxy Nexus using xda app-developers app
chrisram88 said:
Uninstall Kies if you have it. And install drivers again. That should do the trick.
Sent from my SGH-T999
Click to expand...
Click to collapse
I tried uninstalling Kies and that didn't work. I have to re-flash CyogenMod to get it to work again. Wierd!
From my experiences it only ever occurs when Kies is running, even in the background, while usb debugging is enabled. If kies isnt running then its all good.
I ran into this using CM9; seems to me that Samsung is using MTP protocol's now instead of USB. I just use Driod Explorer with debugging and I can move files without any issues.
If you are wanting to just transfer files to/from computer try SwiFTP. I love this little program.
Original dev no longer supports but its been picked up by another. Download latest version here.
http://ppareit.github.com/swiftp/
Sent from my SGH-T999 using xda app-developers app
Please help my gs3 won't connect to any computer
I have tried on four different computers to plug my gs3 but phone never show any option on screen and computer never finds phone plugged in. I also used tried with different usb cables and resetting to factory but the result is same. All it does is charging the phone on all computers without any message or options on the screen. I am thinking there is something wrong cause it never found plugged into any computer nor any computer tried to install the driver.
If someone have experienced this please let me know what should I do to connect it to PC?
fix a "hardware id missing" error
1. install latest version of kies.
2. uninstall SAMSUNG USB Driver for Mobile Phones version 1.5.9.0
3. download and install SAMSUNG USB Driver for Mobile Phones 1.5.6.0
4. connect the phone let it install...thats it.
5..open kies update firmware, backup or whatever
pate201 said:
I have tried on four different computers to plug my gs3 but phone never show any option on screen and computer never finds phone plugged in. I also used tried with different usb cables and resetting to factory but the result is same. All it does is charging the phone on all computers without any message or options on the screen. I am thinking there is something wrong cause it never found plugged into any computer nor any computer tried to install the driver.
If someone have experienced this please let me know what should I do to connect it to PC?
Click to expand...
Click to collapse
it turned out that phone is defective, they are getting me replacement.
SOLVED!
crushbox311 said:
I am trying to connect my galaxy s3 to my windows computer and it will not install the drivers. Has anyone experienced this yet. I am rooted and running cm9 nightly. I also have a custom kernel installed. This was working when i rooted a couple of weeks ago. When I plug my phone into the usb it searches for drivers and display an error message that say it was unsuccessful at installing drivers. Any help would be greatly appreciated.
Click to expand...
Click to collapse
:good:SOLVED! Check this thread
Connecting Galaxy S3
mikeyinid said:
I have buddy. Several times. And I've never installed Kies. Idk what it even does lol
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
From talking to Samsung Advanced Technical Help, I learned that, although it is never mentioned on any site or any literature, if you have
Samsung Studio 3 and/or Samsung New Studio and the USB drivers, uninstall ALL. I use Revo Uninstaller. Then reinstall the USB drivers from Samsung site. Make sure WiFi and Bluetooth are turned off,on the phone, and connect the phone. Should work.

adb shows no devices

Hey guys,
I recently upgraded my ROM to AHRD 12.0, and I noticed this morning that adb stopped working...
I tried to reinstall HTC Sync and also updated the SDK, but no success..
The device's MTP is being seen by my OS (windows 7) and I am able to access the file system, and HTC Sync Manager actually works. Still - no ADB.
Any advices?
Freezeil said:
Hey guys,
I recently upgraded my ROM to AHRD 12.0, and I noticed this morning that adb stopped working...
I tried to reinstall HTC Sync and also updated the SDK, but no success..
The device's MTP is being seen by my OS (windows 7) and I am able to access the file system, and HTC Sync Manager actually works. Still - no ADB.
Any advices?
Click to expand...
Click to collapse
Try going under device manager and looking for your device and make sure it's ensbled. Also make sure you have usb debugging enabled on your phone. Finally try updating your phones usb drivers. If that doesn't work it may have something to do with the new ROM you installed.
Sent from my SCH-I535 using xda premium
shimp208 said:
Try going under device manager and looking for your device and make sure it's ensbled. Also make sure you have usb debugging enabled on your phone. Finally try updating your phones usb drivers. If that doesn't work it may have something to do with the new ROM you installed.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The device is indeed enabled (made sure it is, also reinstalled it), and USB debugging is indeed enabled, but still no adb devices.
Also, fastboot works
Freezeil said:
The device is indeed enabled (made sure it is, also reinstalled it), and USB debugging is indeed enabled, but still no adb devices.
Also, fastboot works
Click to expand...
Click to collapse
That's really bizarre that fastboot works, and adb doesn't. Make sure you have the latest version of adb installed and see if that fixes it.
Already updated to the latest adb (from either sdk-platform or htc sync drivers) - still no luck...
Freezeil said:
Already updated to the latest adb (from either sdk-platform or htc sync drivers) - still no luck...
Click to expand...
Click to collapse
Did you have this problem with adb not working before you installed AHRD 12.0?
What's the condition of the cable?
Sent from my HTC One X using xda app-developers app
The cable is in excellent condition - no tears and such - and it works for everything else (charging, MTP file transfers, fastboot)...
I remember it took me a while to get 'adb shell' when I just started ROMing, but it eventually worked all the same. I installed AHRD 12.0 when it came out a few days ago, but it certianly worked beforehand.
Freezeil said:
The cable is in excellent condition - no tears and such - and it works for everything else (charging, MTP file transfers, fastboot)...
I remember it took me a while to get 'adb shell' when I just started ROMing, but it eventually worked all the same. I installed AHRD 12.0 when it came out a few days ago, but it certianly worked beforehand.
Click to expand...
Click to collapse
Try reverting to a previous version off AHRD and see if your able to use adb or not on the earlier version of AHRD. If you are able to use adb on a previous version of the AHRD ROM, then it's likely that for whatever reason on AHRD 12.0 adb might not be working. You can also try going to the ROM thread and seeing if anybody has had similar problems.
shimp208 said:
Try reverting to a previous version off AHRD and see if your able to use adb or not on the earlier version of AHRD. If you are able to use adb on a previous version of the AHRD ROM, then it's likely that for whatever reason on AHRD 12.0 adb might not be working. You can also try going to the ROM thread and seeing if anybody has had similar problems.
Click to expand...
Click to collapse
I tried reverting to 11.1, but still no luck. Any other advices?
If you have cwm, try adb while in recovery. Cwm supports basic adb commands. If it works there, it's not pc or cable problem but rom problem.
Sent from my HTC One X using Tapatalk 2
eyosen said:
If you have cwm, try adb while in recovery. Cwm supports basic adb commands. If it works there, it's not pc or cable problem but rom problem.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Works!
Will post a link to this thread in ARHD's, so mike & co can read and check this out
Thanks.
No problem. Glad to see problem narrowed down.
Sent from my HTC One X using Tapatalk 2

[Q] Windows 8 driver not working

OS: Windows 8 x64
Phone: Verizon DINC2 rooted with CM9
I rooted and flashed my phone on Windows 7 with no issues. Windows 8 will not recognize my phone. Device manager shows: Other devices->Android Phone with a warning symbol over it.
I've tried installing HTC sync
I tried installing Win7x64 drivers via this method: http://forum.xda-developers.com/showthread.php?t=2232799 but I get an error message saying "Windows was unable to install your Android Phone"
I've tried using different USB ports (non 3.0) and different USB cables and still nothing. Could this be a ROM issue, I know CM7 is the only one officially supported for DINC2.
Has anyone else had any luck with Windows 8?
NamesTwister said:
OS: Windows 8 x64
Phone: Verizon DINC2 rooted with CM9
I rooted and flashed my phone on Windows 7 with no issues. Windows 8 will not recognize my phone. Device manager shows: Other devices->Android Phone with a warning symbol over it.
I've tried installing HTC sync
I tried installing Win7x64 drivers via this method: http://forum.xda-developers.com/showthread.php?t=2232799 but I get an error message saying "Windows was unable to install your Android Phone"
I've tried using different USB ports (non 3.0) and different USB cables and still nothing. Could this be a ROM issue, I know CM7 is the only one officially supported for DINC2.
Has anyone else had any luck with Windows 8?
Click to expand...
Click to collapse
Sorry, but i'm not surprised. Win7 drivers. Are you technical? MIght be able to work with it though.
right click on the file and look at my screenshot. I'm not sure how win8 is different, but that might work
sjpritch25 said:
right click on the file and look at my screenshot. I'm not sure how win8 is different, but that might work
Click to expand...
Click to collapse
I installed the HTC 4.0 driver in compatibility mode, then in device manager added legacy hardware. Phone shows up as My HTC under Android USB Devices now, but I get error Code 10 device cannot start in device manager.
Bummer. I'm out of ideas until that driver is updated to win 8
Sent from my ADR6350 using xda app-developers app
sjpritch25 said:
Bummer. I'm out of ideas until that driver is updated to win 8
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
Doubtful that it will ever be updated since it is such an old phone now. Thanks for trying to help anyway though.

Windows 8 - Drivers x86

Guys i need help.
Normally i connect my note 2 to my windows 7 64 bit system, however i have recently upgraded to a windows 8 desktop and now i cannot get the PC to recognize the drivers at all.
I installed the toolkit and downloaded/installed drivers accordingly NO DICE
downloaded drivers directly from samsung, only 1 available download.... installed.... NO DICE
Phone is in USB debugging mode but that apparently changes nothing. I have not changed anything at all except the computer i'm connecting the phone too. Is this phone compatible w/ win8? I have 64-bit so i am not sure if that's a problem.
BigBison420 said:
Guys i need help.
Normally i connect my note 2 to my windows 7 64 bit system, however i have recently upgraded to a windows 8 desktop and now i cannot get the PC to recognize the drivers at all.
I installed the toolkit and downloaded/installed drivers accordingly NO DICE
downloaded drivers directly from samsung, only 1 available download.... installed.... NO DICE
Phone is in USB debugging mode but that apparently changes nothing. I have not changed anything at all except the computer i'm connecting the phone too. Is this phone compatible w/ win8? I have 64-bit so i am not sure if that's a problem.
Click to expand...
Click to collapse
Try a different usb port. I have no problems with windows 8
--
Think inside the RootBox!
BigBison420 said:
Guys i need help.
Normally i connect my note 2 to my windows 7 64 bit system, however i have recently upgraded to a windows 8 desktop and now i cannot get the PC to recognize the drivers at all.
I installed the toolkit and downloaded/installed drivers accordingly NO DICE
downloaded drivers directly from samsung, only 1 available download.... installed.... NO DICE
Phone is in USB debugging mode but that apparently changes nothing. I have not changed anything at all except the computer i'm connecting the phone too. Is this phone compatible w/ win8? I have 64-bit so i am not sure if that's a problem.
Click to expand...
Click to collapse
Did u try installing the drivers through kies?
Sent from my SAMSUNG-SGH-I317 using Xparent Skyblue Tapatalk 2
Unsigned drivers on windows 8. Had this problem a few months ago
http://forum.xda-developers.com/showthread.php?t=2303046
brandonarev said:
Try a different usb port. I have no problems with windows 8
--
Think inside the RootBox!
Click to expand...
Click to collapse
I did that ... nothing happened
softballjunkee13 said:
Did u try installing the drivers through kies?
Sent from my SAMSUNG-SGH-I317 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
No i actually saw somebody else recommended this but i have not tried it yet.... i will give that a shot
mrevankyle said:
Unsigned drivers on windows 8. Had this problem a few months ago
http://forum.xda-developers.com/showthread.php?t=2303046
Click to expand...
Click to collapse
This is interesting... so the drivers on the samsung website are unsigned? that's pretty dumb. Will try this quick fix first and see if that fixes it. Thanks
BigBison420 said:
This is interesting... so the drivers on the samsung website are unsigned? that's pretty dumb. Will try this quick fix first and see if that fixes it. Thanks
Click to expand...
Click to collapse
The ones bundled with the tool kit aren't. Never hurts to try though
mrevankyle said:
The ones bundled with the tool kit aren't. Never hurts to try though
Click to expand...
Click to collapse
so o did all the above but still no luck. ininstalled everything and installed drivers via kies..... notjing
disabled signing on the advanced reboot menu too

[Q] Nexus 7 2013

hello. please help me, I do not know who to ask. at one point, my computer does not recognize the tablet. came out inscription unknown device. I tried to connect the tablet to other computers, all to no avail. then I made a factorial reset. that is completely erased tablet, in the hope that it will solve the problem. but he also failed to recognize. What shall I do?? I tried to connect via a USB flash drive OTG. but the tablet does not see any stick. I trust only your help
sergio1231 said:
hello. please help me, I do not know who to ask. at one point, my computer does not recognize the tablet. came out inscription unknown device. I tried to connect the tablet to other computers, all to no avail. then I made a factorial reset. that is completely erased tablet, in the hope that it will solve the problem. but he also failed to recognize. What shall I do?? I tried to connect via a USB flash drive OTG. but the tablet does not see any stick. I trust only your help
Click to expand...
Click to collapse
I have the same problem. I fixed it before on my nexus 10 by trying a different kernel. Let me me know if it helps.
Sent from my Nexus 7 using XDA Premium HD app
Do you have the correct drivers installed? If so, you could uninstall and reinstall them. Also, have you tried PTP connection rather than MTP?
Sent from my XT1080 using XDA Free mobile app
Jhall8 said:
Do you have the correct drivers installed? If so, you could uninstall and reinstall them. Also, have you tried PTP connection rather than MTP?
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Been there done that and have always eventually been able to get it back so the computer sees the device as mtp. Wugs toolkit has always been helpful
To me. I like the step by step directions for manually updating the drivers and configuring them correctly in adb AND fastboot.
Bit I have come to an impass..........I am currently on the latest carbon nightly, with f2fs file storage for data and cache. My computer will not recognize the device in mtp and I am unable to pass files with a USB cable. I am wondering if my computer has to be compatible with f2fs, because iam sure that it is not. Will this make a difference PR should I once again uninstall and reinstall the drivers configuring them correctly?
Sent from my Nexus 7 using XDA Premium 4 mobile app
1
I'm telling you that there is no firmware on the tablet. what do you advise.
sergio1231 said:
I'm telling you that there is no firmware on the tablet. what do you advise.
Click to expand...
Click to collapse
Plug it in to a computer.
Boot into recovery if you have one
Adb devices......hopefully it shows and work from there.
Or boot into bootloader mode (after getting the twrp IMG)
Fastboot flash recovery......
Then you can side load your favorite OS
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Been there done that and have always eventually been able to get it back so the computer sees the device as mtp. Wugs toolkit has always been helpful
To me. I like the step by step directions for manually updating the drivers and configuring them correctly in adb AND fastboot.
Bit I have come to an impass..........I am currently on the latest carbon nightly, with f2fs file storage for data and cache. My computer will not recognize the device in mtp and I am unable to pass files with a USB cable. I am wondering if my computer has to be compatible with f2fs, because iam sure that it is not. Will this make a difference PR should I once again uninstall and reinstall the drivers configuring them correctly?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this worked for me im just passing along a possible fix http://forum.xda-developers.com/showthread.php?t=2383146&page=389 post #3888 is the one I followed and been no problems since. also cpl days before in my sdk program google had updated drivers which may or may not have played a roll. before this I could not pass files with mtp only ptp would allow my device to appear. hope it helps!
edit also should note I did device manager then android devices removed drivers in there. plugged in n7 and the adb composite interface drivers installed and that was it. if that doesn't do it make sure sdk has updated google driver which should be 10.0.0 or something don't quite remember exact #
jblaze10 said:
this worked for me im just passing along a possible fix http://forum.xda-developers.com/showthread.php?t=2383146&page=389 post #3888 is the one I followed and been no problems since. also cpl days before in my sdk program google had updated drivers which may or may not have played a roll. before this I could not pass files with mtp only ptp would allow my device to appear. hope it helps!
edit also should note I did device manager then android devices removed drivers in there. plugged in n7 and the adb composite interface drivers installed and that was it. if that doesn't do it make sure sdk has updated google driver which should be 10.0.0 or something don't quite remember exact #
Click to expand...
Click to collapse
Thanks jblaze. I've been able to function pretty well usind adb. Sort of glad cuz it forced me to learn some pretty essential stuff I have been getting along with for far too long.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Thanks jblaze. I've been able to function pretty well usind adb. Sort of glad cuz it forced me to learn some pretty essential stuff I have been getting along with for far too long.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ur right, I wish I knew more about it. I'm in that phase now where I'm digging thru Xda for info such as adb backups among other things. Hey no prob, take it easy.
Sent from my Nexus 7 using Tapatalk

Categories

Resources