yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] buttie:
Seriously guys, if using Google is to hard, please at least read the OP. ;)
[Nexus 7 Android Development] YoungCorruptionV2.0:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

Tap the build number in "about phone" about 10 times
[Nexus 7 Android Development] Kingstonfx:
Dont i feel like a fool! :D thanks allot! I got it and now everything is peachy! lol thanks timez a thousand!
[Nexus 7 Android Development] YoungCorruptionV2.0:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

No problem man. Its what I'm here for
[Nexus 7 Android Development] Gezetah:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

Why only SuperSU with 4.2 ? CM uses Superuser and it's 4.2

Thanks for your work
[Nexus 7 Android Development] SinAkira:
I saw that superuser update it to v3.3 with multiuser option.... toolkit should be update it too with this last version i guess in root option :)
[Nexus 7 Android Development] puncha1580:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

Super user is not very good for Android 4.0 and up... if you go to any CM threads, you'll find a life of users to reporting force closes on superuser. supersu it's more compatible....

superuser is open source and supersu is not... that's why CM has superuser and not supersu....

Personally i use both....

superuser is installed on my nexus7 and on the GNex i have supersu... Superuser used to force close when on the GNex with jelly bean. but on my nexus7, i still haven't faced any issues with superuser....
[Nexus 7 Android Development] Droid8Apple:
Thanks!

Wanted to say thanks for all the hard work, I donated to receive the full version of the toolkit. Everyone should do that, it isn't a specific amount. you donate and get a full code. $5.00 USD gets him a cold beer or some drive through I'm sure ;) ...

Anyhow, I am also stuck on the "saving internal storage" while doing the backup. I didn't verify fastboot was working- but now I have been waiting an easy 25mins and all it says on the Grouper is "Shared Storage" under the blinking cursor which allows you to encrypt backup. I'll go read FAQ's again, but is there a way to get out of this without damaging anything? Thanks.
[Nexus 7 Android Development] Gezetah:
Thanks alot for your answer, as you said I've never faced any problems and that's why my first question, but I flashed CM10.1 and I have Superuser now.
[Nexus 7 Android Development] rayzstyle123:
Hi fellow N7 users!

This is my first day using my new Nexus 7~ I just wanted to ask and wanna be sure this will work on Android 4.2 build number JOp40c with kernel version 3.1.10-g22b4cd

Im pretty scared but i rooted other android phones before lol..
[Nexus 7 Android Development] puncha1580:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

Yes, it will... if you've rooted before, you don't need to be scared at all.... just make sure you follow the TK instructions....

You'll be good to go....

make sure you backup, if you have any data on the nexus...
[Nexus 7 Android Development] ricardowec:
Cant Backup the SD

Mark,

Just updated to the latest base, and also to the latest toolkit.

I am not given the chance to state if secure or insecure kernel,. The Kit checks for it, and detects insecure, nevertheless it comes with 0 pulled and 0 skipped.

Sorry if there is something wrong with my procedure. Long time I havent been with the Kit,

Thanks for your advice.
[Nexus 7 Android Development] NickDVS:
"waiting for device"

Hello -

I wanted to run a new rom, but I accidentally wiped my Nexus 7. I believe I formatted the system and I am no longer to boot into my ROM. I used this toolkit to unlock, root, etc. I tried to redo a recovery so I can at least mount the Nexus to my laptop so I can drag the ROM over to flash, but the toolkit keeps saying "waiting for Device". I try restarting the bootloader, which it does, but nothing seems to connect to it.I tried with CMD prompt, but it never sees the tablet either.

Any advice on how to get my tab to connect would be greatly appreciated.
[Nexus 7 Android Development] Milamber33:
Make sure the Fastboot drivers are installed correctly.
[Nexus 7 Android Development] NickDVS:
Thanks for the fast reply. I have the fastboot drivers that I used to unlock/root my htc phone, but these wouldn't be the same drivers correct? If not, where would i get these fastboot drivers?
[Nexus 7 Android Development] kendallc123:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

The toolkit can download and install them for you
[Nexus 7 Android Development] NickDVS:
Yeah, I tried to install using option 1. For some reason ADB mode and fastboot just isn't picking up the tab.

---------- Post added at 07:14 AM ---------- Previous post was at 07:08 AM ----------

What if it has something to do with USB debugging? Is there a way to enable it without a ROM on the tab?
[Nexus 7 Android Development] kendallc123:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

No, USB debugging doesn't do anything when the tablet is in fastboot. But the drivers installed correctly? Maybe try a different USB port on your computer?
[Nexus 7 Android Development] NickDVS:
Oh my gosh! I am so embarrassed that the issue was the wrong USB port lol! Wow. So, should I download and flash the stock rom to be able to mount the drive and drag the custom rom over?
[Nexus 7 Android Development] Milamber33:
Check the FAQ on the first page for instructions on manually installing the drivers if the auto-install fails.
[Nexus 7 Android Development] kendallc123:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

Ha glad it's working now! Yep, that should do it.
[Nexus 7 Android Development] Milamber33:
In theory there's no 'right' or 'wrong' USB ports to use. In practice, I've seen plenty of stories of people having issues which are solved by switching to a different port.

Not sure what makes some ports work fine and others not, but something in the whole ADB/Fastboot system does seem to be far more sensitive to minor changes than usual...
[Nexus 7 Android Development] cwilliams:
Just used your Nexus 4 toolkit, app backup, one click root, app restore worked great. Bought the donate version as a big thank you for your awesome tool.

Now, trying it on my Nexus 7 (Build JOP40D). Did a back up (Option 2, then 1, then all the includes, no encryption), worked great. Did a one click root, worked great, got my Nexus 7 up with root. Now, when I restore the backup I made (By going Option 2 then 10, and choosing the backup file), I have a big problem. The toolkit loads the backup, the tablet prompts me for the restore, I click except. I see the first app (the game Machinarium, a very large filesize) start transferring. After about 1 minute, the Nexus 7 flat out reboots. When it turns on, only that single app is restored. Out of my nearly 8 gig backup.

I've tried this probably 10 times. Hard reboot everytime.

Now, its not the end of the world, but my god I had a ton of apps and their data backed up. And the whole point of this rooting expedition was too install Carbon to be able to move my data freely between these devices (and mostly from the tablet->phone).

So just posting this in case mskip or anyone else has any advice on how to get around this hard reset and maybe restore my data! Excessive googling has revealed nothing...
[Nexus 7 Android Development] sm@rt:
Dear mskip, i appreciate your toolkit, and thx for last update of yesterday! I'm a donator obviusly.

I have a question about option 13 restore files from PC to SDCARD

Previously I have backup completely SDCARD on "pulled_files_are_put_here"... wait, wait, wait... and after a while I have all files and directory of /SDCARD/ are backed on "pulled_files...", that's ok.

Now after a week, I need to restore it on SDCARD of my N7-3g/32Gb..

I try to copy directory content of sdcard on my PC from :

pulled_files_are_put_here ----> to ----> put_files_to_push_here

but also with '*' or '.*' i transfer only one file at time and toolkit ask me for permission after every files!
[Nexus 7 Android Development] NickDVS:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

So true. When I first rooted the n7 and used this toolkit, the USB port that worked last night would not work. Now, the one that worked first did not work. Fun times. Thanks again for the help :thumbup:
[Nexus 7 Android Development] mskip:
The google "adb backup" process is not as reliable as it should be. There is no way to check the backup file is ok and if part of the data that is backed up is corrupted or not correct in any way such as incorrect file format then the restore process will fail. I guess the safest way to make sure after a large backup is to restore it to your system before wiping or flashing a new rom. Nobody should really have to do that every time but its the only real way of knowing your backup is ok.

Did you flash a different rom after making the backup? If so have you tried flashing back the original rom build that you had when you made the backup just to see if it restores on that?

Mark.
[Nexus 7 Android Development] mskip:
That function is only really used if you want to push a single file to your device and set its permissions. I didnt write it with the intention of someone backing up their complete Internal Storage. Why didnt you just use the "Backup Internal Storage" and "Restore Internal Storage" options in the backup/restore section?

Mark.
[Nexus 7 Android Development] mskip:
GOOGLE NEXUS 7 TOOLKIT AUTO UPDATE V4.3.2 [06TH FEB 2013] AVAILABLE!!

Changelog:

+Updated TWRP Touch Recovery to latest version [2.4.1.0]

+Updated SuperSU root to latest version [1.04]

+Insecure kernel detection script now completely automated

I know I said V4.3.0 would be the last version before I started working on the next public builds but I didnt count on Chainfire updating SuperSU soo soon. I wanted to get that pushed out aswell as the new TWRP and the updated kernel detection script.

For people who do not want or cannot get the Auto Update versions you can download twrp touch 2.4.1.0 from http://goo.im/devs/mskip/recovery/google_nexus7 and flash it via the Toolkit. SuperSU can be updated to the latest version from the app.

[Auto Updates are only accessible if you have donated to the Toolkit project, received an activation code and unlocked the donator features. Auto Updates are a much faster and easier way of pushing small updates that would otherwise not be worth doing. I can push a single textual change or add support for a new build without having to go through the whole process of building a full version and uploading a large file. IF you are not able to or do not want to donate to unlock the Auto Update feature (and other donator features) then all the smaller updates are collated and a full build made when I have time or if there are enough updates to warrant it. This is the easiest way to make sure all the Toolkits are as up to date as possible. IF you have any views about this please pm me about them and do not post in the open thread]

Enjoy :)

Mark.
[Nexus 7 Android Development] cwilliams:
Nope, I had kept the stock rom, just rooted with your tool. I doubt unrooting and trying the restore would work? I should have thought myself to test before I wiped...it had gone so smoothly on my Nexus 4 I guess I had a false sense of confidence.

I had feared it was a bad backup or some sort of device bug, but I was curious what you might know with your knowledge and experience. I appreciate you taking the time to respond. Thanks!

There isn't any sort of PC tool to open/mount the backup or something and start picking it apart is there?

Thanks again for your great tools.
[Nexus 7 Android Development] vikashhero:
You sir, are a legend.

I totally screwed up my N7 using another toolkit - it blocked access to recovery mode. It didn't even root/install SU, even though it said it was a success. Not only did I restore my N7 to its original state, but I successfully unlocked, rooted and installed SSU all using your awesome software.

Bloody legend.
[Nexus 7 Android Development] mskip:
No there isnt thats why its a risky way to backup apps (but the only way available via adb) as you can't extract any files from it and you can't view what has been backed up.

Mark.
[Nexus 7 Android Development] _Epic:
Have no idea why but I had a few issues with this. Running latest Android on WIFI version, and it wouldn't let me unlock bootloader through the option 8 (install ALL) so had to go through and do that first by itself, then ran through the root and recovery and nothing changed on my device. It rebooted and everything but no root or recovery. So had to run through it again and it WORKED! :) No idea why I had this issue. But if anyone has a similar issue, just run through it again.
[Nexus 7 Android Development] slebit:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

Thanks for this awesome tool. I rooted my n7 today, and it couldn't have been easier.
[Nexus 7 Android Development] Milamber33:
Quick bug report/request mskip:

In the backup/restore your device option, the internal storage backup tries to pull /data/media, but that doesn't work on some ROMs. I'm running the latest RasBeanJelly ROM, and it just reports 0 files pulled and 0 files skipped, but I know for sure there are hundreds of folders and thousands of files in there, over 9 gigs of data. I can see it if I open Explorer, but based on past experiences I don't trust Explorer to show all the files.
[Nexus 7 Android Development] Udonitron:
So no clue how or why but I have all of a sudden lost root on my N7...currently on SmoothROM 4.3 and went to do a backup before installing 4.4 and it says I do not have root?

Still shows unlocked when I reboot but trying to re-root with this and I am in fastboot after choosing Flash Choice 2 but now it is just stuck at booting into recovery waiting for device and my N7 is sitting at the fastboot screen?
[Nexus 7 Android Development] killall:
Check SuperSU settings, untick 'Respect Cyanogenmod root....'
[Nexus 7 Android Development] Udonitron:
Hot damn! +1 thanks to you man, appreciate it.
[Nexus 7 Android Development] mskip:
Was that with an Insecure Kernel booted?

Mark.
[Nexus 7 Android Development] CliveCleaves:
Just wanted to say thanks for this guide.

It definitely got me there eventually. I ended up unlocking it (just using the unlock bootloader option, after backing it up etc.) before running the 1 Click option (which did indeed work).

I had a few problems with getting the dialog option to show up (I was in fastboot, device was recognized (showing serial number)) it would just say waiting for device and even leaving it for a very long time would not resolve to anything.

Anyways, splitting up the steps did work, I am rooted and unlocked so that is great. A number of applications did not end up coming over, but I had used other services to back up the actual APK files.

Thanks!
[Nexus 7 Android Development] tropicanapure:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

Hello, I have rooted my device with your excellent toolkit. I have also installed a custom kernel over it. Now that 4.2.2 is starting to become available, I was wondering whether it would work with my rooted device?

I did remember to do a full backup with your toolkit though. I am guessing the way to do it would be to restore the stock kernel. Is this possible using this toolkit? All I see is a restore option. Will it proper me which but I want to restore?

Sent from my Nexus 7
[Nexus 7 Android Development] sean.trinidade:
You;ll need to not only restore your backup, but also the stock recovery. Only then will you be able to install the OTA.
[Nexus 7 Android Development] Archon810:
Hmm, with 4.2.2, when rooting, I had to reboot manually to fastboot mode. Otherwise it was just "waiting for device". Could it be due to the new whitelist adb functions? I even tried replacing adb files in the toolkit with the ones from 4.2.2, but that didn't change anything.

All rooted though, after performing that step manually.
[Nexus 7 Android Development] tropicanapure:
hey thanks, while i am doing those restores I have noticed something odd. During restore CWM touch sees a single backup (which should be my stock, I am praying) but /sdcard/clockworkmod/backup/ is empty:confused:

Any idea where else this backup is being kept?

---------- Post added at 01:45 AM ---------- Previous post was at 01:30 AM ----------

Actually scratch that - it seems that CWM touch (the one included with the kit) is keeping it under /data/media/clockworkmod/backup/ - wonder why :confused: Bug perhaps?
[Nexus 7 Android Development] Guto ViP:
I cant root my son`s Nexus 7 with 4.2.2... What can i do?

DONE! Nexus 7 rooted!

Link to help another users:

http://www.teamandroid.com/2013/02/12/root-nexus-7-android-422-jdq39-jelly-bean-cwm-recovery/

Don't forget to click on Thanks if i help you.
[Nexus 7 Android Development] Ruben1987:
I wanted to use your Toolkit to sideload the new 4.2.2 update as it should be possible according to your changelogs, but I cannot find the sideload option in the menu.

I have the Nexus 7 Wifi only with 4.2.1, drivers are installed and somehow trying to run the adb command manually does not work as it does not recognize the command.

I have tried using the Android SDK, but that says that the adb command is out of date and terminates the sideload.

Any help on how to get the 4.2.2 sideloaded?
[Nexus 7 Android Development] hirenvasani:
bricked Nexus 7... Only load in fastboot...

Erasing partitions for flashing

erasing 'boot'...

FAILED (command write failed (Unknown error))

finished. total time: 0.599s

erasing 'cache'...

FAILED (command write failed (Unknown error))

finished. total time: 0.595s

erasing 'recovery'...

FAILED (command write failed (Unknown error))

finished. total time: 0.622s

erasing 'system'...

FAILED (command write failed (Unknown error))

finished. total time: 0.613s

Flashing Bootloader Image

sending 'bootloader' (2096 KB)...

FAILED (command write failed (Unknown error))

finished. total time: 0.645s

rebooting into bootloader...

FAILED (command write failed (Unknown error))

finished. total time: 0.645s

Now Flashing Factory Image: Boot, Recovery, System and Userdata

erasing 'userdata'...

FAILED (command write failed (Unknown error))

finished. total time: 0.624s

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

getvar:version-bootloader FAILED (command write failed (Unknown error))

finished. total time: 0.715s

Deleted file - C:\Google Nexus 7 ToolKit\put_google_factory_image_here\bootloader-gro

uper-4.13.img

Deleted file - C:\Google Nexus 7 ToolKit\put_google_factory_image_here\flash-all.bat

Deleted file - C:\Google Nexus 7 ToolKit\put_google_factory_image_here\flash-all.sh

Deleted file - C:\Google Nexus 7 ToolKit\put_google_factory_image_here\flash-base.sh

Deleted file - C:\Google Nexus 7 ToolKit\put_google_factory_image_here\image-nakasi-j

op40d.zip

Deleted file - C:\Google Nexus 7 ToolKit\put_google_factory_image_here\nakasi-jop40d-

factory-6ac58a1a.tar

Deleted file - C:\Google Nexus 7 ToolKit\put_google_factory_image_here\nakasi-jop40d-

factory-6ac58a1a.tgz
[Nexus 7 Android Development] Milamber33:
Should be. It's with the latest RasBeanJelly ROM, Brainmaster's tweak to enable init.d support, and latest Trinity kernel. Also, I was able to get the data by pulling from /storage/emulated/legacy, so it's not an access problem, it's got to be something to do with the way the mount points and symlinks are set up.
[Nexus 7 Android Development] ThomasKru:
How to update a rooted Nexus 7 to Android 4.2.2

What are the necessary steps to update a rooted Nexus 7 from Android 4.2.1 to Android 4.2.2 :confused:
[Nexus 7 Android Development] mskip:
I switched to /data/media/ to keep the relationship with CWM recovery as it was moved out of /sdcard/ to keep it seperate from user accounts. I will have to look into the paths more closely to see if there is a better method.

Mark.
[Nexus 7 Android Development] mskip:
If you havent received it yet then download the OTA and flash via stock recovery. As soon as google images are available I will upload them to my goo.im account and add support to the Toolkits.

Mark.
[Nexus 7 Android Development] mskip:
Is your bootloader unlocked?

Mark.
[Nexus 7 Android Development] mskip:
CWM backups have been moved to /data/media/clockworkmod/ to keep it seperate from the multi user accounts that 4.2+ bought. Legacy folders were created under /sdcard/ so each registered user could keep their files seperate from other users but that meant a clockworkmod folder was also made in each legacy folder. Moving it out of /sdcard/ and into /data/media/ keeps it out of that whole system and available to all users.

The Toolkit also changed its Internal Storage backup path to /data/media to enable backups of the complete system including clockworkmod.

Mark.
[Nexus 7 Android Development] adrian08:
Sir, mskip.

I have a question that may seem newbie-ish. So when I get the 4.2.2 update, my root access will be gone right and the same rooting method in your toolkit may not be possible as of now as it only supports up to 4.2.1?

Thanks!
[Nexus 7 Android Development] edbertin:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

I having this error when tried to update to 4.2.2.

No changes were done before, just using regular stock 4.2.1

Any ideas how to install the update?

Tks in advance
[Nexus 7 Android Development] edbertin:
Re: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH

You can install ota rootkeeper from play store before update, and it will keep your root after update.
[Nexus 7 Android Development] edbertin:
@mskip i donate some english tea for you

Cheers
[Nexus 7 Android Development] mskip:
As many people have found out the older versions of my Toolkits (or adb) won't work with the 4.2.2 update. The device shows as offline as will not connect for any adb operations. The older adb server doesnt include the new authentification method needed to connect. Fortunately the fix is as easy as updating 4 files which I have zipped up and uploaded to my server to make everything easy.

NOTE: The latest Auto Updates for the Toolkits include the new google files so this shouldnt be a problem for anyone who has Auto Updated their Toolkit recently.

1. Download http://www.skipsoft.net/download/toolkit/New_adb_fastboot_files_for_4.2.2.zip

2. Make sure your Toolkit has been closed correctly with the "x" option in the Main Menu or the adb server will still be running

3. Extract the contents of the zip file above to your Toolkit folder (overwriting the original files)

4. Run the Toolkit and when you get to the Main Menu a popup will appear on your device asking for authentification

5. Click ok to add your pc to the accepted list

6. Select the 'Refresh Main Menu' option in the Toolkit and your device will now show as 'device' and not 'offline'

Mark.
[Nexus 7 Android Development] ESdesigns:
Don't see 4.2.2 after auto update

mskip,

I just auto updated to V4.3.2 of your tool kit, but I don't see the 4.2.2 build available to choose from in the toolkit. I had unlocked my bootloader and rooted 4.2.1 prior to the OTA update to 4.2.2. It appears as if my bootloader is still unlocked (unlocked padlock at bottom during boot), which choices should I select to regain root for 4.2.2? Thanks. I donated for your N7 and S3 root kits.
[Nexus 7 Android Development] Skyfall007:
4.2.2 factory image is out!