Develop Bugs

[GUIDE] Rooting Sprint Intercept froyo 2.2 [06-02-11]

I've successfully permanently rooted my Sprint Intercept with the latest 2.2 froyo on it without installing custom kernels and wanted to share steps I took since there is some confusion and differences.
Original guide link.
Things you'll need:
Root files.
Samsung drivers.
Windows 7/vista/xp 32 bit.
Steps:
Install Samsung drivers
Reboot your PC
Reboot your phone, connect it to your PC with a usb cable
Put your phone in debugging mode (menu->settings->applications->development)
Extract root files to your c:\intercept-root folder (or any folder you wish)
Start windows command line (start->run->CMD)
Change to your "intercept-root" folder
Execute START_ROOT command
Follow instructions
Once done, don't forget to install Superuser apk.

after you rooted it you were able to put a different rom on it right. trying to clear out the garbage that comes on it.

shonok said:
after you rooted it you were able to put a different rom on it right. trying to clear out the garbage that comes on it.
Click to expand...
Click to collapse
No, this is just simply to root and remove stuff you don't want. I suggest Titanium backup. There is no proper recovery for the intercept that I know of. The one existing can be flashed and it does work but has some issues with what it backs up and what it restores. It's not complete and may create problems.
If you are rooting the latest 2.2 froyo, after removing all sprint apps you are left with true bare stock so there is really no need for anything else. Make sure you don't remove the sprint vm even if you are using google voice. It needs to be on because of system integration.

you mae one error. the drivers can't be installed on windows 7. I have gotten the drivers from the moment to work once but now its nothing. my computer no longer recognizes the phone when i plug it into the computer. which means that i cant root it or anything. sucks and i need serious help.

hmmm, same problem
Find a friend with a XP laptop and use that?
Glad to know - i have failed at rooting my intercept a few times and have been using my windows 7 box. Trying these instructions from a laptop - will report back!

Success
Using nothing but a old crappy dell laptop runing windows XP I was able to gain perma root using the instructions provided here. On my first run of the script the process failed, I simply did what the program told me to (run the script again) and it worked like a charm.
OP - thank you so very much for taking the time to post.
Question for anyone: now that I have root, I *really* want to be able to use my Intercept as a wi-fi hotspot. Can I do this? Where do I start?

No errors. I got drivers under Windows 7 working but I clearly said it has to be 32 bit as 64 does not work. Check your version.

entropy.of.avarice said:
Using nothing but a old crappy dell laptop runing windows XP I was able to gain perma root using the instructions provided here. On my first run of the script the process failed, I simply did what the program told me to (run the script again) and it worked like a charm.
OP - thank you so very much for taking the time to post.
Question for anyone: now that I have root, I *really* want to be able to use my Intercept as a wi-fi hotspot. Can I do this? Where do I start?
Click to expand...
Click to collapse
Download wireless tether app. I've had troubles with it in the past so if that one doesn't work try Barnacle.

how to flash cmo1 custom recovery after phone is rooted?

Just throw intercept root on sdcard and run
All I had to do it throw the root on the sdcard. Run it from the file manager, and then download barnacle. Sweet! Done!

Ignorance1 said:
how to flash cmo1 custom recovery after phone is rooted?
Click to expand...
Click to collapse
I don't believe there is a supported recovery for the intercept. There is one hacked up but there are some issues with it so I don't recommend it.
Sent from my Nexus S 4G using XDA App

obsanity said:
I don't believe there is a supported recovery for the intercept. There is one hacked up but there are some issues with it so I don't recommend it.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
There is no problems with the custom recovery. I recommend it if you want to try custom roms/themes. Check sdx for all things intercept
Sent from my PG06100 using Tapatalk

Can you fix/update the links, please? I need to files for root, drivers, etc. Everything I need to root my backup phone, please.

ThunderOKC said:
Can you fix/update the links, please? I need to files for root, drivers, etc. Everything I need to root my backup phone, please.
Click to expand...
Click to collapse
Yeah, me too.
Looking to root my Intercept, but the 4shared link is broken
UPDATE: OK, I think this is what he was linking to. But my Antivirus doesnt like it. It says it's a virus. A severe virus.

Trying to Root - Driver install issue

I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer

Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.

I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app

Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .

What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.

Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little

Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.

So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there

Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now

Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...

i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250

Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier

The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!

I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus

The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT

[Q] Kindle Fire wifi won't turn on at all

hey everyone,
I normally don't post on here because I find the info without needing to, but I can't find this even with google fu, any help appreciated
Problem: Wifi won't turn on
ROMs tried: Orignal Kindle ROM, CM 9 (hashcode make), CM 9 (Energy mod ICS)
Other notes: My methods worked on my other KFs, but not this one.... however its an older version. I was sure to make everything factory default, wipes the two caches, and out of frustration from TeamWin deleted everything on the flash and system (except TeamWin Obviously). I have the Android SDK setup to interface with the device, so if you need me to hit it from there let me know. Everything else works, but a wifi only tablet without wifi is useless in my book.
Thanks once again for any help I will go back to google fu'n and head to wall bashing

Well can you mount your sdcard in twrp? If so transfer this to your sdcard http://forum.xda-developers.com/showthread.php?t=1439916 wipe everything except your external storage and flash it. Maybe this will help isolate whether this is a hardware issue.

hmm
Thepooch said:
Well can you mount your sdcard in twrp? If so transfer this to your sdcard http://forum.xda-developers.com/showthread.php?t=1439916 wipe everything except your external storage and flash it. Maybe this will help isolate whether this is a hardware issue.
Click to expand...
Click to collapse
Thanks for the quick reply, will give this one a shot and hopefully it works
Edit/update:
I can mount the device in TWRP, however it will not mount when I boot the ROM. Also adb is apparently not running on the device? Did these commands:
adb kill-server
adb device
and device not listed.

update
initialhit said:
Thanks for the quick reply, will give this one a shot and hopefully it works
Edit/update:
I can mount the device in TWRP, however it will not mount when I boot the ROM. Also adb is apparently not running on the device? Did these commands:
adb kill-server
adb device
and device not listed.
Click to expand...
Click to collapse
update: got a terminal emulator on the device while I waited for the download (I already had the apk). One thing peculiar is it cant find wlan0... which I can on my other one. Also usb is still a no go unless from TeamWin. Still waiting on the ROM.

final update
initialhit said:
update: got a terminal emulator on the device while I waited for the download (I already had the apk). One thing peculiar is it cant find wlan0... which I can on my other one. Also usb is still a no go unless from TeamWin. Still waiting on the ROM.
Click to expand...
Click to collapse
ROM flashed to device, kept having Google android process fail and restart causing major pains... so I couldnt even check the wifi. Using the Kindle Fire Utility I reflashed Gapps and rebooted, it locked up, so I wiped the caches and whatnots and put the ROM in Factory reset mode from TWRP. It looks like for sure the wifi NIC is fried... going to have to just send it back and have them send me another one... one final thing is I am downloading the latest factory ROM for this device and flashing it with it to see if that works, and if not then the people I am sending back to wont know the wiser lol. Thanks for giving ideas nonetheless yall!

initialhit said:
ROM flashed to device, kept having Google android process fail and restart causing major pains... so I couldnt even check the wifi. Using the Kindle Fire Utility I reflashed Gapps and rebooted, it locked up, so I wiped the caches and whatnots and put the ROM in Factory reset mode from TWRP. It looks like for sure the wifi NIC is fried... going to have to just send it back and have them send me another one... one final thing is I am downloading the latest factory ROM for this device and flashing it with it to see if that works, and if not then the people I am sending back to wont know the wiser lol. Thanks for giving ideas nonetheless yall!
Click to expand...
Click to collapse
Did the factory ROM flash correct the issue or still a no-go for WiFi?

Hey guyz.. i solve the issue!..
if your system version is lower the the the latest version:
just download the update img in amazon kindle. using PC. then copy to kinlde directory..and after updating the wifi works..
if latest version:
downgrade the kindle using KFHD_SRT_v1.2.3.zip and a fastboot cable.
then apply the above process.

kibusaki said:
Hey guyz.. i solve the issue!..
if your system version is lower the the the latest version:
just download the update img in amazon kindle. using PC. then copy to kinlde directory..and after updating the wifi works..
if latest version:
downgrade the kindle using KFHD_SRT_v1.2.3.zip and a fastboot cable.
then apply the above process.
Click to expand...
Click to collapse
Wrong device. Wrong forum.

Unable to Access Device Storage

Hello Everybody,
I habe a really big Problem with my GNex.
Today I Copied some Files over to my PC. For this I used for the first time "USB Mass Storage". Because I haven't seen some Files wich i can see under my Phone.
It worked really good. I unplugged my phone and to my things. Some minutes later i Heared the "Pling" from superuser. Then my phone was really slowly and need a bunch of time only to open the Launcher. So i deactivated Superuser. Deinstalled USB Mass Storage and MyMobiler.
After this i rebooted my Phone 2 times and the lag on my screen was gone. But now i'm unable to Access the Device under Android booted as MTP.
Even after reinstalling USB Mass Storage i'm unable to Access the Device via MTP or Mass Storage. My Windows PC and Android don't says anything. My Device is only Loading.
So i Unlocked my Bootloader with "BootUnlocker" and updated my System with offical Google Update 4.2 "fastboot update image-yakju-jop40d.zip" .
But i cann't access my Device now. Only fastboot is working.
So i'm unable to backup all my data and do an Factory Reset.
Have anyone out there an Suggestion how i can fix this Problem.
My Device:
Galaxy Nexus
Stock: 4.2
BL: Unlocked
Root: No Root (But with BL unlocked should this be the smallest problem.
Best regards and Thanks
Chris
P.s Sorrry for the really bad English
P.s.s Fastboot is working ... so it don't seems like an HW error

The nexus doesn't have use mass storage
Sent from my Galaxy Nexus using Tapatalk 2

This point i know, thats why i used the App.
But how can i aceess my Phone with MTP?
It's not even reconigzed under Windows ... and Android also don't set an Logo which tells that USB is Connected.

Chris302 said:
This point i know, thats why i used the App.
But how can i aceess my Phone with MTP?
It's not even reconigzed under Windows ... and Android also don't set an Logo which tells that USB is Connected.
Click to expand...
Click to collapse
have you tried a different usb chord?

simms22 said:
have you tried a different usb chord?
Click to expand...
Click to collapse
Yes i tried another USB-Cord.
Same thing -> Phone is Charging but not resposing over ADB.
And also i can't see it in the Explorer.
Same thing at my GF PC (Win Vista)

are you trying to use adb in the bootloader? if so, that will never work. ever.

Zepius said:
are you trying to use adb in the bootloader? if so, that will never work. ever.
Click to expand...
Click to collapse
No i'm using Fastboot when i was in BL to confirm that i have no HW error.
I try to ADB when i booted my Phone.
Or to access the My Device via Explorer

Have you tried removing and re-installing the drivers from your PC?
Have you checked the Android SDK to see if there is a 4.2 specific version of adb?

danger-rat said:
Have you tried removing and re-installing the drivers from your PC?
Have you checked the Android SDK to see if there is a 4.2 specific version of adb?
Click to expand...
Click to collapse
I Don't think hat There is my Problem, because under Windows i can Not even See my device it is not even recognized.
I can test driver uninstalling but i can not see my device under the device manager
:/ it seems like my android is f****ed up because root is also not working :/

When you update to a stock image you over write your/system partition (which is where you enabled root access) - that is most likely how you lost root access.
Also, since you updated your device, it is possible that your PC no longer sees it as the same device, which is why I suggested removing and reinstalling the driver...

danger-rat said:
When you update to a stock image you over write your/system partition (which is where you enabled root access) - that is most likely how you lost root access.
Also, since you updated your device, it is possible that your PC no longer sees it as the same device, which is why I suggested removing and reinstalling the driver...
Click to expand...
Click to collapse
I want to clear some things.
Don't think i want to shame you, i really thankfull for your help . Also it is the Best forum for Android Development and everything around it wo i have ever seen.
I was always on Stock. I updated the Offical 4.2 to 4.2 with an Stock image, it is now working again, i think the Update cleaned the Things up. Only Thing (shame me) i have forgotten to check after update is under-> settings -> storage -> Menu -> USB-Connection -> and check there "MTP".
So now my Device says connecting as "MTP" and my PC also recognize it again.
Before that my Device don't even say connecting as MTP.
I know that i will loose root when i update my Device -> but with my unlocked BL I just Booted to CWM and flashed Superuser.
Maybe (i hope) you are willing to help me again.
I am unable to update my SU binary and also i dont see a Message from Superuser, where i can allow Root access.
Even if i set under Settings -> Security -> Automated Answer -> "Allow"
I don't see the Message where i can say "allow" to Root access. I cannot even install SuperSU.
Have you any idea why it seems like i cannot access Root. For me it's seems like my app's don't recognize root.
When i Start SuperSu he says "Su-binary" must be updated" and next step is "Installation failed".
Have you any Idea where this came from?
But the good thing is at this point i'm abel again to access my Device via Explorer Thank you really really much for your Help You can't belive how glad i'm not to do a Factory reset and loose all my data.
Thank oyu for your great help
Chris
P.s. Root is working from Shell

Please read forum rules before posting
Questions and issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Okay i will read the Rules again.
Thank you for moving the Thread.
I hope in the right section someone can tell my why my Root isn't working ?
P.s. or should i make a new thread for that problem ?

Chris302 said:
Okay i will read the Rules again.
Thank you for moving the Thread.
I hope in the right section someone can tell my why my Root isn't working ?
P.s. or should i make a new thread for that problem ?
Click to expand...
Click to collapse
Use SuperSu instead of Superuser.
Sent from my i9250

bk201doesntexist said:
Use SuperSu instead of Superuser.
Sent from my i9250
Click to expand...
Click to collapse
Sorry for the long delay.
I had no time to check this thread. And also my Email Notification hasen't worked.
So I hope you still look at this and can also suggest something.
I tried SuperSU but supersu says.
He need to install the Binaries.
After roundabout 15 seconds i get an Error message which says: "Installation failed".
My Super user tells me that the Binary is outdated.
And i get this Error Message in SuperSU even when i say "Answer every Permission Request with Allow".
I Even tried to remount the System as RW and the say update. But Both of them Seems to fail to install the Binary.
I flashed Superuser Through Temp Booted CWM.
Is their another Zip that i can try ?! or have i done something wrong while Flashing ?
Or can i theoretically flash SuperSU through CWM and then get Root Access?
Thank you for your help
Chris

Chris302 said:
Or can i theoretically flash SuperSU through CWM and then get Root Access?
Thank you for your help
Chris
Click to expand...
Click to collapse
Correct; you will be rooted again. Just boot a custom recovery and flash.
Sent from my i9250

bk201doesntexist said:
Correct; you will be rooted again. Just boot a custom recovery and flash.
Sent from my i9250
Click to expand...
Click to collapse
Hello
And again a dumb question.
Could you please provide me a download link for a zip. Which is working under 4.2 ?
I have seen zip's around for Superuser but not for SuperSU.
An i only Mention that maybe Superuser have a Problem with 4.2 but i cannot Prove it.
Thanks again
Chris :]
Sent from my ASUS Transformer Pad TF300T using xda app-developers

oasad92 said:
Yeah SuperSU should do the trick
Click to expand...
Click to collapse
Thank you for the Reply.
But how i have written 2 post ago. SuperSU also did not work.
He keeps saying "Installation Failed" thats why i asked for an Flashable Version which is working under 4.2.

I recently reverted back to stock 4.2.1 (just to try it)
My Win7 computer was unable to see my phone when connected in MTP mode. Nothing showed in the computer at all, However when I selected PTP I could acess the DCIM folder.
In the end I couldn't be F**Ked with it so I pushed a custom rom to data/media/ and every thing was normal again.
I spoke to a friend who had the same issue I had, and he just enabled debugging (which a custom rom has enabled by default) to solve the issue.

Chris302 said:
Hello
And again a dumb question.
Could you please provide me a download link for a zip. Which is working under 4.2 ?
I have seen zip's around for Superuser but not for SuperSU.
An i only Mention that maybe Superuser have a Problem with 4.2 but i cannot Prove it.
Thanks again
Chris :]
Sent from my ASUS Transformer Pad TF300T using xda app-developers
Click to expand...
Click to collapse
oasad92 said:
Yeah SuperSU should do the trick
Click to expand...
Click to collapse
I have not tried Superuser again since Chainfire released Supersu and all those issues rose with JB.
Chris302 said:
Thank you for the Reply.
But how i have written 2 post ago. SuperSU also did not work.
He keeps saying "Installation Failed" thats why i asked for an Flashable Version which is working under 4.2.
Click to expand...
Click to collapse
http://www.google.co.uk/search?q=xd...&sugexp=chrome,mod=0&sourceid=chrome&ie=UTF-8
would take you to:
http://forum.xda-developers.com/showthread.php?t=1538053
flash that
p.s: on the supersu thread says you need to be rooted... for us, of course, it's not quite true, rather we need unlocked bootloader and custom recovery.

Nexus 7 wont connect to computer via MTP

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.