Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
lesdense
Old
#11  
Member - OP
Thanks Meter 37
Posts: 99
Join Date: Mar 2011
I'm having a lot of problems with Nexus 7 Toolkit. On my new 32GB Nexus 7 I've got USB debugging checked. I'm connected to my Windows 7 PC as "Media Device MTP" (my only other choices is Camera PTP). I can get to Fastboot no problem. When I start Nexus 7 Toolkit my device is recognized and a serial number is generated. I've unlocked my bootloader (during boot up the Google logo now shows an unlocked padlock). But when I try to get it to root it goes through several steps and several restarts until it generates the following error messages: "adbd cannot run as root in production builds", "error: protocol fault (no status)", then the daemon starts successfully and I get "failed to copy root\su to system/bin/su : read-only file system" and "failed to copy root\superuser.apk to system/app/superuser.apk : read-only file system", then finally two "unable to chmod" error messages about those two actions.

I assume that all of this stems from one problem but I can't figure out what it is. Help?
 
Croak
Old
#12  
Croak's Avatar
Senior Member
Thanks Meter 224
Posts: 1,556
Join Date: Oct 2007
Location: Msida, Malta
Quote:
Originally Posted by lesdense View Post
I'm having a lot of problems with Nexus 7 Toolkit. On my new 32GB Nexus 7 I've got USB debugging checked. I'm connected to my Windows 7 PC as "Media Device MTP" (my only other choices is Camera PTP). I can get to Fastboot no problem. When I start Nexus 7 Toolkit my device is recognized and a serial number is generated. I've unlocked my bootloader (during boot up the Google logo now shows an unlocked padlock). But when I try to get it to root it goes through several steps and several restarts until it generates the following error messages: "adbd cannot run as root in production builds", "error: protocol fault (no status)", then the daemon starts successfully and I get "failed to copy root\su to system/bin/su : read-only file system" and "failed to copy root\superuser.apk to system/app/superuser.apk : read-only file system", then finally two "unable to chmod" error messages about those two actions.

I assume that all of this stems from one problem but I can't figure out what it is. Help?
Which root option are you choosing in N7 Toolkit? Option 3 is your best bet, as it doesn't rely on ADB for the heavy lifting, as it slides the root access in via Recovery.
 
Post Reply+
Tags
clone back-up
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Go to top of page...

XDA PORTAL POSTS

Auto Test Your Android Apps with Robotium

You’ve just finished coding your very first app, but before you release it to the wild, you … more

Open Source CPU Info App for Windows

So you’re playing with your shiny new Windows 8 tablet PC, when one of your like-minded geeky … more

Guide to Using Adobe Air on Android

When writing an app with performance in mind, you most likely want to write it native code using the … more