yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] mskip:
It should do. The current version on googles download site is D so I dont know what the difference is but the insecure boot image used in the rooting process is only booted and NOT flashed so its not permanent. If it doesnt boot then then long press the power button to reboot the device with the original boot image.

Please let me know how you get on and if it goes off without a hitch then I will add that build to the compatibility list for future reference.

Mark.
[Nexus 7 Android Development] Sjaak79:
Got my N7 last night, rooted this morning!!!

The toolkit works like a charm, thanks alot!!!

P.S. Donated ;)
[Nexus 7 Android Development] chasmodo:
Hi everyone.

Thanks a million for this useful tool. It managed to unlock, root, and flash custom recovery and busybox in no time at all. Still, I'm having problems with manually booting to CWMR. I can do it with no problems from various apps (like Widgetsoid), but cannot boot into recovery from fastboot mode for love nor money. It's a known issue and no biggie:

However, I cannot flash a custom Rom successfully - the flash goes through OK, but the tablet gets stuck on "Google". Had to re-flash the stock Rom 5 times now.:) Does it have something to do with the CWMR issue?

Root status is fine, I can paste stuff into /System using Root Explorer and superuser asks me whether to grant SU access to various root apps.

Any help will be very much appreciated.:)

EDITED: Solved my failed custom Rom flashes.

1. wipe everything

2. flash Rom

3. flash Gapps

4. flash Clemsyn's Elite Kernel (ClemsynEliteNexus7GPU520.zip)

5. wipe caches

6. reboot to homescreen
[Nexus 7 Android Development] JeanEatsWorld:
I've the same problem and I tought it was a driver problem the caused an error in the unlocking process..But it doesn't convince me.... By the way.. I can easily get into the custom recovery (TWRP/CWM) by using program like goomanager.. the problem is, each time I try to get into the recovery by pressing power vol up vol down, I got the fastboot mode, but if I select "recovery mode" by pressing the power button, I remain stuck in the black screen with "Google" written in the middle...

Please help me...I tryed different recovery and different versions but with always the same result...:crying:
[Nexus 7 Android Development] Rody2k6:
So I would choose "backup and restore your tablet" and then choose Backup ALL installed apps, or Backup to Virtual SD, or NANDROID ( I guess the latter only if I was going to install a ROM right)

thanks
[Nexus 7 Android Development] ernexto:
It works! Oneclick option and everything went well! Thank you!

Sent from my Nexus 7
[Nexus 7 Android Development] mskip:
Backup installed apps will (if you follow the recommended selections) backup any apps that you installed since you first turned on your device. This includes Play Store apps and associated userdata such as high scores or settings.

Backup Virtual SD Card will pull all data and folders from your Internal Storage which is where you may keep your Music, Videos, Pictures (and anything taken with the Camera).

NAND Backup will make a complete backup of your system, data, boot image, cache and recovery. This is useful after (or before) you install all your apps and set your phone up so you can get back to that exact point at any time in the future if needed.

Mark.
[Nexus 7 Android Development] mskip:
Nice to know it all went smoothly I will add it to the list.

Mark.
[Nexus 7 Android Development] lazl0:
Reading on Slashdot. Is this app written Google go?

root nexus 7
[Nexus 7 Android Development] tucstwo:
Was this full version ever released? I'm sorry, I only ask cause the OP still says version 2.0 and if the update is buried in the thread somewhere I want to make sure I'm not missing it?
[Nexus 7 Android Development] sean.trinidade:
You need to be on the donated version and then update via the toolkit.
[Nexus 7 Android Development] tucstwo:
yeah no, I know that. The post I quoted was when it said that the non donate or "Full version" was released or was to be released last thursday or friday.
[Nexus 7 Android Development] jayhammy:
waiting for USB debugging to be enabled

I keep getting "waiting for USB debugging to be enabled" when I try to root. Unlocking worked fine. But it hangs at this point. And, yes, it's definitely checked and enabled. Please help! Thanks.
[Nexus 7 Android Development] sean.trinidade:
Sorry. No, it wasn't.

Try disconnecting the device from your computer, reinstalling the drivers and then reconnect. Happened to me once and that's how I eventually fixed it.
[Nexus 7 Android Development] jayhammy:
I wish it were that easy. I tried reinstalling the drivers. Keep getting "failed" messages. This is getting very frustrating.

EDIT: seems like the issue is with ADB. It works with fastboot and I can see my serial #, etc. But, with ADB, there's no serial # in the app and the computer doesn't seem to recognize that the phone is in USB debugging.

HELP !!!!!
[Nexus 7 Android Development] rnclock:
Mine was doing the exact same thing. I had to make sure that USB debugging was checked in Settings >> { } Development Options.

Hope this helps.
[Nexus 7 Android Development] mskip:
I havent updated the OP to V3.0 yet as I am re-writing several of the scripts to make them more compatible with future updates which is taking longer than I thought. Once the re-write is finished and tested thoroughly I will build a full download and update the thread.

For future reference the current full release will always be posted in the OP.

Mark.
[Nexus 7 Android Development] mskip:
What huh?? :confused:

Mark.
[Nexus 7 Android Development] demandarin:
I'm having EXACT SAME PROBLEM..lol. recognizes fastboot but not adb in app. Mydevice manager shows android adb ddevice connected. I've been trying to return this replacement unit back to stock so I can mail it back to Google. Luckily I still have my original unit which works fine. I tried the toolkit and it gets stuck after sending system or sending boot. Now my device fails to boot up. I get stuck on Google screen. But I can manually get it into bootloader/fastboot mode. I think what happened was the toolkit wiped the tablet, then it wrote bootloader back bit failed to write the system. So now I cant boot into OS. So I'm not even sure if the.USB debugging is enabled or not.

Toolkit wipes device fine. It reboots my device back into bootloader. It flashes the bootloader image fine(sending and writing says OK). Now when it comes time to flash factory image, it sends boot then Okay. Then it writes boot & Okay. Then it either gets stuck on sending recovery or sometimes it'll get past that and get stuck on System. I tried that deleting USB mass storage driver(recommended on Google+) and THST didn't work. I tried again now and its stuck on sending recovery it seems.

I've uninstalled and reinstalled drivers. Fastboot showing up and working, I believe. My device manager shows android adb device attached. I've even downloaded and installed the android SDK with the extra packages installed like platform tools. Which has adb and fastboot related stuff in there. I set correct paths and everything like video showed me on YouTube. Now "Manually" sending commands is the only thing I haven't tried yet. Which is why I downloaded the Android SDK. I have no choice but to learn it..lol. but I did open up CMD and typed adb. Then saw a bunch of crap. Them typed in "adb devices". It just says "list of devices" and my device isn't listed. Nothing is.

So like the previous poster, I can't boot up and computer not recognizing tablet as adb(in app only recognizes as fastboot & typing adb devices in cmd prompt shows nothing under list of devices). I'm not even sure if manually trying to do it will work since adb commands in cmd prompt isn't listing my device in adb devices. I will still try it though as it seems to be my last shot.

One thing for sure, I'm learning alot more than I knew before with all this. As far as manually doing adb/fastboot and android sdk.

If anyone has any tips or insight, please let us know. Ill update later on how the "Manual" method of flashing stock and relocking went.
[Nexus 7 Android Development] Barleyman:
Try changing usb connection from mtp to "camera" and see if windows won't install additional drivers..
[Nexus 7 Android Development] Milamber33:
He said he couldn't get in to Android to check that. But he won't need to.

ADB is only for when your device is actually booted into Android, or at least the recovery. Fastboot is the tool to use for flashing, just type 'fastboot flash system yoursystemimage.img' and press enter. Same process for the other partitions. And just so you know, it takes quite a while to flash the system image via fastboot, wait for it to actually finish, don't get impatient and think it's failed when it hasn't. ;)
[Nexus 7 Android Development] JDuBmkii:
help a noob out

I want to flash a theme can anybody walk me through it I'm so lost...rooting with this program was so simple even I could do it and with my current dilemma I think that says a lot!!!
[Nexus 7 Android Development] demandarin:
I ended up manually trying to fastboot flash. Everything went well initially. But it got hung on sending "system". It sat like that for over half an hour. It takes longer than that? Then I tried again and it got hung on sending boot.

I made an update post in the manual Google stock img fastboot thread. I got close but kept getting hung up. Fastboot method did the same thing toolkits did. Get stuck at either sending boot, recovery, or system. The furthest I've gotten was sending system. Ill try again tomorrow. At least I know how to manually fastboot now. I feel that I'm close to getting it to finish.

Any Insight as to why it gets stuck on what I mentioned?

P.s. when I try tomorrow, ill leave it for like an hour or so to see if my old computer takes that long to flash system img via fastboot. Maybe I did cut it short but it was like THST for over half an hour. Plus it doesn't explain why other times I tried it gets stuck on other parts, like sending or writing boot or recovery.
[Nexus 7 Android Development] Milamber33:
The fact that it's getting stuck on different things each time is a concern. And half an hour does seem to be quite a long time.

Have you tried using a different USB cable or port? Maybe you're having connectivity issues.
[Nexus 7 Android Development] demandarin:
Funny you said that. I was just reading on the other website on the same thing. People had similar issues and switched ports and it worked. That's something I haven't tried yet. I hope it is that simple. I will try using a different port tomorrow. Someone also said they had similar issue. Then they switched computers and it worked just fine. I don't have another pc to try. So I do hope its just the port acting funny. I have at least 2 other ports to test out.

Thanks for the insight. Appreciate it. I have a feeling it might be connectivity issue also. Ill try different ports and ill try the actual cable THST came with replacement unit. I was using my original unit USB cable for all of the previous efforts.
[Nexus 7 Android Development] chasmodo:
It could be a number of things. My Toolkit also had ADB problems at first, and I'd get a lot of the following:

adb server is out of date. killing...
*daemon started successfully*
***daemon still not runningerror: cannot connect to daemon
killing...starting...error: (blank)...killing...starting...started successfully
(command)
OK
(command)
OK
Everything done.

And nothing was done, actually.

What did the trick for me was to

1. uninstall all my Samsung Galaxy Note drivers using Device Manager

2. launch USBDeview and uninstall everything with Samsung in its name

3. uninstall other programs which had platform-tools (i.e. adb.exe) because I noticed at one point that there were 2 adb.exe processes running in the system - perhaps this was unnecessary

It was plain sailing after that, no more adb errors and everything got done.
[Nexus 7 Android Development] gallahad2000:
Thanks for the tool box, makes things much faster.

The "reflash stock" option really helped after I flashed a rom that wouldn't boot.
[Nexus 7 Android Development] Spacemonkie4207:
Has anyone tried this with the latest build ?
[Nexus 7 Android Development] chicoelnino:
unlocked but can't root?

I've spent about 5 hours like a muppet today trying to root this thing.

I used wugfresh toolkit v1.5.3 method and followed everything by the letter.

Unlocked fine...no problems there. Drivers are correctly installed as "Android ADB interface" in device manager.

When it comes to root its where the problem is.

It says its push root files and "rooting" on the pc and the screen just stays in the bootloader screen as you can see in the photo:

[/URL][/IMG]

I just stays on that screen and I end up pressing the power button to click start again.

So basically I can't get root access as there's no superuser or any busybox files installed.

So I'm just left with an unlocked nexus 7. And I've checked to make sure its locked as there is the lock symbol showing up during boot up.

Can anyone help me get this sorted? Would love to have root access on this thing.
[Nexus 7 Android Development] reef2009:
Hi Mark,

I really like your toolkit.

It's worth my donation !!

For all people with connecting (ADB) problems.

MTP (standard setting) doesn't work with ADB (uninstall and delete the driver to use it like normal storage in windows.

Change it to PTP-mode and you can install the right drivers.

Two more things Mark:

please stop annoying us with the (endles) slow menu messages ???

Don't automatically go back to the main menu, let us choose so we can read the whole message
[Nexus 7 Android Development] sean.trinidade:
That's not true - I use mine in MTP mode, and ADB recognises it fine!
[Nexus 7 Android Development] littlewierdo:
Ugg

I downloaded your little tool and installed it, I stopped after your tool was installed to just mention some thoughts before I do anything more.

Both in your OP AND during the installation of the app I was being told to donate, more times than I can count, starting with the OP, then with the last page of the installation of the program. I was then told there was a later version (3.0) and was told that I would have to donate to receive this update, all with text that took about 60 seconds to go through each feature and when it was done listing each new feature of the new version, one final time for good measure to donate YET AGAIN, before being unpleasantly dropped into the main menu BEFORE I could even read all of the features. Yea, I didnt read them while they were appearing, I waited, assuming that I would be able to read everything when it was done.

I get it, you want people to donate. But nagging is not the way to do this. It isnt appropriate to ask people to donate before they have even had a chance to use the software!! Im suggesting you let people use the program before you start beg...err...asking for money.

I might be overly sensitive here on this issue but I still believe that people will donate if the software is helpful or useful. Nagging me every step of the way and then having the software tell me there is an update that I cant get unless I donate is insulting to say the least. In fact, if I cant get the latest version, what exactly is the reason for checking for updates? Dare I say this is intentional...

It is not in the spirit of donating when people feel COMPELLED to do so in order to not be nagged about doing so in the future and so that they can receive the latest updates to the software. There are other software companies out there that provide old versions of their software for free and charge for the latest version and that is what you are doing here.

Please consider providing the software without the 'donate to me money' every step of the way, remove the dreadfully slow text, and do NOT proceed to the next screen until the user gives input (pushes a key for example).

The last part is why I am not going any further with your tool, if something goes wrong (or right), I have no idea whether your software will stop long enough to tell me one way or the other. I want to know every step of the way what is going on and if it thinks everything went well, I want to SEE the program tell me that. If something went wrong, I FOR SURE want to see any messages provided.

Let people actually use the software before you ask for money. There are creative ways you can do this, possibly after the user exits the program or maybe every other time the user starts the program (but NOT the first time they start the program).

Im sorry if all this came across as rude, I just think there is a better way. People will donate more when they consider it a donation which should be something done willingly, ie. because they wanted to (for whatever reason).
[Nexus 7 Android Development] demandarin:
I'm still stuck with same situation. No matter whether using toolkit or manually using fastboot, I get stuck at sending "system", when attempting to flash stock image.

Update: I gave up..lol I even uninstalled all toolkits and Android drivers from my computer. Then attempted to manually fadtboot flash stock image. Stillgot stuck on same part. So I just entered in fastboot command "fastboot oem lock". I relocked the tablet as is. I will ship it back to Google with bottloader locked. No trace of root anyways as I believe my OS got wiped from previous attempts of flashing stock image through various methods. My tablet info got wiped/erased several times now. Just glad this isn't my main n7. It was a replacement whi h I was sending back to them anyways.

Quick question: would I just type "fastboot oem unlock" to unlock n7 through fastboot? Just curious so I'd k la for future reference.

At least I learned android sdk and fastboot through all of this. Entering fastboot commands and android sdk not as complicated as I originally thought. Maybe now I can test out kernels not made into flashable zips. Like Franco kernel. Since I know how to flashboot fla**** now ;)
[Nexus 7 Android Development] sean.trinidade:
If you actually used the tool, you would see that it does actually do this - i.e. walk you through each step!

Also, unless you select "yes" on the initial update question, it doesn't ask you to donate again until you quit the tool.
[Nexus 7 Android Development] DeerSteak:
it says there's an update from 2.0.0 to 3.0.0 when it offers to auto-check, but it never actually downloads. This is with the donate version, btw. Looks like it came out on the 11th, but I just now needed to use it tonight. :o

Temporarily disabled windows firewall and AV, made no difference. It's just an HTTP port so it shouldn't be a big deal.

Update Checker now starting..

Current ToolKit [V2.0.0], Latest Available [V3.0.0]

Current Mods Section [V1.0.0], Latest Available [V2.0.0]

AN AUTO UPDATE IS AVAILABLE TO DOWNLOAD

but then nothing.
[Nexus 7 Android Development] rnclock:
Only thing I could add is if you use PeerBlock, make sure it is disabled. Got me the first time.

---------- Post added at 05:04 AM ---------- Previous post was at 04:55 AM ----------

Yes, that command would unlock the N7 in fastboot mode. Also, "fastboot oem lock" will relock it.
[Nexus 7 Android Development] littlewierdo:
If you actually read what I typed, youd know why I was concerned and didnt want to continue.

I listed the places where I was asked to donate and I even left a few out.

Not going to argue or debate the subject, it just comes across as wrong to me withhold updates and functionality but still call something freeware if you REQUIRE someone to PAY money for these.

Of course, its up to the developer to decide whether anything I said is worth listening to, I just think more people would be willing to donate.
[Nexus 7 Android Development] Milamber33:
He releases updates for donators first, then updates the free download, but the free version has been the same as the donate version on many occasions.

And yes, there are some features which are donate only. None of these are core functionality, however. The free version does as advertised without requiring you to pay anything, so IMO it still qualifies as freeware.

On the other hand, I agree that the way the auto-update feature has been added makes the tool a bit of a hassle to start up. Possibly a better way to implement this would be to store a setting in the toolkit, something like 'auto-update on startup? (yes/no/ask)', with ask as the current setting and no as the default for non-donators. This would get rid of the nag factor at startup. And yes, I also agree that it should wait for input before proceeding.

Another thing I think this toolkit could use is a logging feature. The outputs from some commands are longer than the terminal window, so it would be nice if it was echoing everything it does to a log file somewhere to check through for errors.
[Nexus 7 Android Development] Cor-master:
This tool is great, made unlocking and rooting simple. The nexus 7's built in backup function however, not so great. it pretty much chose what apps get saved and what apps don't. Some apps that got saved just picked up where they left off, with all saved data intact. other apps however, such as my games, all lost their data. Its obvioulsy not the toolkit's fault as it was just running commands to access a function that was already there, so what did I do wrong?

Also why did it delete my internal storage such as pictures and stuff? I unlocked my flyer's bootloader and didn't have that issue, it only wiped the system partition. If I'd have to guess, its because of the Nexus 7's wacked out one partition to rule them all scheme. Other devices have a virtual sd card partiton, but the Nexus doesn't.
[Nexus 7 Android Development] cordell507:
help, i donated but can't find a 10-digit conformation number anywhere
[Nexus 7 Android Development] ayopancheezy:
this is by far the greatest flashing tool i have ever used.

everything was straight forward and i didn't even have to worry about my nexus about to brick. thank you very much for making my life extra easier!
[Nexus 7 Android Development] Milamber33:
Some apps backup their data to Google's servers. Some don't. Depending on which backup option you chose, you might not even be backing up app data locally at all. Best way to get this is something like Titanium Backup.

From what you said though, you were backing up to unlock the bootloader, so you weren't rooted. So Titanium wouldn't have worked for you. Without that, you can only grab whatever files are on the virtual SD card and hope for the best. Many apps (mostly games) won't pick up save/setting files from an old install just by chucking their data file back in, this is probably a security thing to stop people modding their save games. Only solution for this that I know of is stuff like Titanium and other root level backups. You were always going to lose this data without root.

As for why unlocking the bootloader wipes so much, that's an entirely arbitrary decision on Google's part. There's no reason why it has to wipe anything at all, and in fact some Galaxy Nexus phones purchased from the Play Store don't wipe when you unlock the bootloader. My guess is it's so that if your device gets stolen, the thief can't just unlock the bootloader, flash a custom recovery, and get access to all your data. From a data security standpoint, it's understandable, just irritating.

He emails it out to you, if you haven't got it after a couple of days PM him with the Paypal receipt number.
[Nexus 7 Android Development] Cor-master:
I think they need cloud backup for gaming data. Would be nice if I could play a game on my nexus and resume it later on my vivid. But I'm honestly surprised a nexus device even has a locked bootloader. I know Samsung devices for instance generally don't unless the carrier requests it.