yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Gitah.:
I'm on 4.4 and I just flashed supersu but it doesn't show up on the drawer. I even tried to download the latest build from chainfire's site but it still doesn't show up, what happened?
[Nexus 7 Android Development] :
just got the 4.4 update and for the life of me I cant get the toolkit to flash CWR.

it says its done then when I boot into it, its not flashed, I can boot a temp recovery but when I go to flash the cf auto root, it gives me errors,

can anyone help?
[Nexus 7 Android Development] cammel:
[MENTION=3110798]WugFresh[/MENTION] please I need you to please tell me if this is normal, I just flashed back to stock 4.3 my 2012 nexus 7 (grouper) using the latest version of the toolkit and everything seemed to work out just fine, I mean, the flashing process was successful and my nexus 7 is up and running stock again , but during the process the log window showed a few fail messages and I'm just a little bit worried, so if you please can take a look at the pictures I took (sorry about the quality of them) of the log screen and tell me if that is normal it will be really great for me.

Thanks in advance!
[Nexus 7 Android Development] bamaredwingsfan:
Can I use this program to update the bootloader in grouper nexus 7 tablet?
[Nexus 7 Android Development] keneth_c:
its normal

"Archie does not contain...." .... thats normal i believe....

i faced the same thing yesterday but definitely look like my device was back to stock....

Gr8 work WugFresh... much appreciated.
[Nexus 7 Android Development] WugFresh:
Yeah, disregard "archive does not contain sig files"

Google doesn't include sig files since you need to be unlocked in order to flash stock.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Yes, see advanced utilities.

{{ WugFresh }}
[Nexus 7 Android Development] rushter:
Will the ota for 4.4 work if rooted using twrp?
[Nexus 7 Android Development] WugFresh:
Please read the FAQs under "Updating and OTA"

{{ WugFreah }}
[Nexus 7 Android Development] fysxx:
couldn't boot to recovery

I could not boot into stock recovery after going back to stock recovery using this tool. Its Shows booting failed

I did all my bootloader unlocking rooting and putting custom recovery with this tool, and its simply easy and had no problem. As KITKAT update is on the way I tried to go back to stock recovery, And everything went smoothly with no problem.

However today when I try to boot into stock recovery manually it say booting failed. Other than that I dont find any problem and my tablet start and it doesn't have any bootloop.

Any solution please.
[Nexus 7 Android Development] WugFresh:
Help!!! My Nexus device is totally messed up. It has ______ problem. What do I do??

{{ WugFresh }}
[Nexus 7 Android Development] Ekofasc:
Dumb question: Even though this doesn't contain the new factory images for the Nexus 7, can I use this to root and install custom recovery on my 4.4 tablet with unlocked bootloader?
[Nexus 7 Android Development] WugFresh:
FAQs - If I don’t see my build listed in the selection menu, what should I do?

{{ WugFresh }}
[Nexus 7 Android Development] fullmetal509:
Long story short, I flashed this super wipe script file on my Nexus 7 (2012), http://xdaforums.com/showthread.php?t=2121649

Completely wiped EVERYTHING! ( I know I should of read the OP) Anyways I'm stuck in a bootloop, can boot into custom recovery but that's it. Tried using your tool reflashing stock images but I get error, that it doesn't recognize through ADB. Also tried using adb sideload but no luck! Any ideas?

Via HTC Uno!
[Nexus 7 Android Development] WugFresh:
FAQs - Help!!! My Nexus device is totally messed up. It has ______ problem. What do I do??

Use softbrick mode.

{{ WugFresh }}
[Nexus 7 Android Development] Deshabilitado:
can i flashan ota update with this tool? i see the option in advanced settings "flash zip", also my N7 doesnt have open boot or custom recovery ... thanks.
[Nexus 7 Android Development] WugFresh:
Yes, however the proper terminology would be "Sideloading and update". There is a tool in advanced utilities for this that will work on stock devices. Use that and follow its instructions.

{{ WugFresh }}
[Nexus 7 Android Development] limpet:
I was having trouble with SoftBricked/Bootloop mode until I swapped

out my USB cable for one which did not disconnect intermittently.

With a tight cable, it worked fine.

The microusb connector is the weak point in the N7 hardware and

they get flakey after while. I usually charge with a pogopin dock

to reduce wear on the connector....unfortunately, the dock doesn't

support usb communication.

I've had good luck with a Samsung cable. #ECC1DU2BBE.

https://www.google.com/search?q=ECC1DU2BBE
[Nexus 7 Android Development] Cor-master:
What's the friggen deal here!

I tell it to sideload the update, follow the instructions, as soon as I get into recovery where it's ready to sideload the toolkit tells me "ADB is not connected". Is this feature just broken? Serioulsy adb works fine up until that
[Nexus 7 Android Development] porkovich:
Hey Wug, can i use the latest 1.7.5 version of the tool to flash stock 4.4 image on my nexus 7 (grouper) ?
[Nexus 7 Android Development] rushter:
Yes, you can. As long as you have the update file you can sideload it. Look in Advanced Utilities.

I first took the nexus back to stock and unrooted it. Not sure if this is an absolute must but it is what I did. (@WugFresh can verify this)

I'm using the Nexus 7 (2012) model so I went here to get the OTA file to sideload it directly

http://xdaforums.com/showthread.php?t=1745781

The other OTA files can be downloaded here -

http://www.xda-developers.com/android/android-4-4-ota-updates-captured-for-nexus-10-and-7-both/

1 - Open the Toolkit and click Launch under Advanced Utilities

2 - In the Advanced Utilities on the right side you'll see where it says ADB Sideload Update - click Sideload Update and then follow the instructions. BE PATIENT - it looks like it's doing nothing for a long time but it will complete with no issues.

3 - Reboot and enjoy KitKat goodness.

If you want to root and were not rooted before this is what I did

1 - In the Toolkit main screen check the Custom Recovery checkbox and click Root

2 - Follow the steps and you'll get to the script screen that tells you to open SuperSU so you can update it but it doesn't work correctly - even though the customer recovery had me select it during the setup, SuperSU was nowhere to be found on my nexus.

3 - Go to the Play Store and download it. Run it

3 - Do the Busybox installer as instructed

4 - you should be good to go.

Sorry if I'm stepping on toes here but I just wanted to share my problems I had - other than that one little SuperSU issue everything went flawless.
[Nexus 7 Android Development] cammel:
[MENTION=3110798]WugFresh[/MENTION] I´m having an error when flashing the n4 stock 4.4 image using the tookit, please help! It starts the process, pushes the bootloader, but fails because of the baseband or radio version, the toolkit says that I´m using .84 version and that I should be running version .97 so it fails every time!!! what can I do to solve this?? Thanks in advance!

---------- Post added at 10:55 PM ---------- Previous post was at 10:52 PM ----------

[/COLOR [MENTION=3110798]WugFresh[/MENTION] I´m having an error when flashing the n4 stock 4.4 image using the tookit, please help! It starts the process, pushes the bootloader, but fails because of the baseband or radio version, the toolkit says that I´m using .84 version and that I should be running version .97 so it fails every time!!! what can I do to solve this?? Thanks in advance!
[Nexus 7 Android Development] WugFresh:
Enable force flash mode in the toolkits main options menu and try again.

{{ WugFresh }}
[Nexus 7 Android Development] cammel:
OK, what I did was to manually open the cmd prompt under the advance utilities on the toolkit, locate the image folder of the 4.4 build and run the update all .bat script and apparently it worked, is this OK?? Is the same thing or did I messed it up?

Thanks in advance!!

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 7 Android Development] IP IHI II IL:
This worked perfectly! Thanks!
[Nexus 7 Android Development] WugFresh:
Yeah, I actually helped write the code for the official google flash-all.bat file :)

The toolkits built-in script actually parses that file for flashing info. That is definitely a legit way to do it.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
If you are on a Nexus 7 2012 (Grouper/Nakasi), and you are having trouble updating to 4.4 due to bootloader. You need to first downgrade to JWR66V bootloader first (not the JWR66Y). Use advanced utilities, flash bootloader button, and flash this: http://d-h.st/c6P then you can proceed to flash stock + unroot with the official factory image package.

{{ WugFresh }}
[Nexus 7 Android Development] WoodmanMN:
Thanks for this very handy toolbox. Brought me back from CM10.2 to stock 4.3, then let me sideload 4.4 with no issues.
[Nexus 7 Android Development] bittersound:
Hashcheck failed

Hi there, I've not had much luck finding a solution so here I am...

Is anyone else getting a problem flashing the 4.4 (KRT16O) to their N7 2013 wifi with regards to the hashcheck failing? I had downloaded the image several times and have copied and paste the 'MD5 Checksum' into the Hashcheck Verification but it always fails the the "Hashcheck: Failed. This script will not continue. Try downloading it again. or use the built in downloader".

The device is unlocked and unrooted... I've previously used NRT to flash images before with no problem.

Any feedback gratefully received, and many thanks in advance!

Cheers,

David
[Nexus 7 Android Development] WugFresh:
Its not your fault. Google servers have been acting screwy. They seem to be serving files that don't match the hashes they posted.

I don't know if the files are wrong or the hashes they posted are - but NRT is doing it's job by protecting you from flashing incomplete downloads.

Try checking your download with a third party hashcheck utility and you will see. You can either wait for Google to fix it. Or enter the hashvale of the file you downloaded rather than the hash they posted.

I use this for hash checking: http://code.kliu.org/hashcheck/

{{ WugFresh }}
[Nexus 7 Android Development] l'irlandais:
thank you i checked the hash with your software and it work ...... I mean i am flashing now.... wait and see :)

edit : it woked I am now on 4.4

again thank you very much
[Nexus 7 Android Development] Anderson2:
Hi Wugfresh

Thank you for all your wonderful work with the toolkit and keeping it constantly updated. You've helped a lot of people, myself included, to root their devices.

I would like your advice on 2 issues if I may.

1. In the faq you do acknowledge that in some cases the adb install can be a problem. I am one of those cases. I used the toolkit to root my Nexus 7 2013 and my Nexus 7 2012, each twice because of ota updates that removed root. For both tablets it took forever to finally install the adb drivers that worked. I believe in both cases I finally had to find and download the drivers separately manually. It might be a thought to offer that method as a first choice. In some cases it was the Samsung drivers that did the trick and here I found something that might be significant: when selecting to install the Samsung drivers, the install always told me they were already installed - even though neither the Windows 7 64 bit device manager nor the view tool showed it to be installed! So could the presence of the installed but hidden Samsung drivers be a reason why some have trouble with the universal or other drivers? I'm no expert and am offering this for what it is worth.

2. After rooting with the toolkit, both tablets could no longer be accessed by Windows 7 via usb cable. Previously, the usb connection worked fine. Could this be because of a conflict with the installed adb drivers or possibly because some of usb drivers deleted during the adb install are needed but absent? If the latter, which drivers might they be and how to restore them?

These are just questions, not a criticism of your excellent work.
[Nexus 7 Android Development] WugFresh:
1. Samsung's driver installer actually installs itself as a registered windows program as well, so you would have had to removed it from add/remove programs to fully remove it. My fault if that isn't in the driver guide or faq.

2. The drivers you want are MTP, which windows should auto-configure. Probably a better way to go about driver config is to first plug your device in (without doing anything with usb debugging) and just let your comp configure those MTP driver automatically. Then go about the adb/fastboot stuff. That said, you could probably have them configure by just toggling usb debugging off, or enabling/disable MTP or PTP in the usb config settings on your device (which you should see in the notification bar when you plug your device in). I will try to make all that more clear in v1.7.6.

Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Yes. And yes, you could do it that way. Or you could just flash the official CWM with the advanced utilities flash to recovery button.

{{ WugFresh }}
[Nexus 7 Android Development] NZtechfreak:
Thanks for that :)
[Nexus 7 Android Development] allen099:
Thanks for the effort, Wugfresh.

Just one question..I used your latest toolkit to root the 4.1.1 with this small Wallet update (JRO03D). The root worked, but I don't know if there are any ill-effects. Is this OK to do, or should I use one of the other tools to root this version?

I notice that every now and then, the device freezes up when I'm typing. Turning the screen off and on seems to resolve.

Thanks again!!
[Nexus 7 Android Development] WugFresh:
I didn't know about those problems. I suppose you could do what I said but before flashing twrp you could use the flash stock recovery button in the advanced utilities. That way you were flashing TWRP over the stock recovery instead of CWM, but since you ran the root with CWM script, those files I spoke of would be renamed to ensure that your alternate recovery sticks.

In the next version I suppose I could just make an option in the options menu that allows the end user to select which custom recovery they want the toolkit to utilize, with the options; CWM, TWRP, or "other" for user selected recovery.img file. The only draw back to this idea is its going to make the file size much larger because I will have to include twrp img files for all the devices... That said, after this next release users won't have to redownload the whole toolkit ever again because I will be able to syndicate incremental updates via an in app updater/notification feature.. So maybe it's not a big deal if the file size is larger?

{{ WugFresh }}
[Nexus 7 Android Development] jayfried:
Excellent work on this program. One tool for all my babies.
[Nexus 7 Android Development] WugFresh:
No ill effect. Fully compatible. Regarding your problems;

http://wugfresh.com/Help/scr/Since_I_rooted_I_have_problem.htm

You could also try rebooting your device.

{{ WugFresh }}
[Nexus 7 Android Development] caanda45:
Hey wug small issue as I see it, or maybe I am just being daft, in the fastboot mode when I go to get into recovery mode the N7 stalls at the google unlock screen (padalock is unlocked) and the only way I get it out of that is a long press the start to reboot it.

So the only way to get into recovery is by an app. How do I fix this to be able to do this in the fastboot mode???

I did the new touch cwm that u suggested on page # 25 post #248 http://download2.clockworkmod.com/re....6-grouper.img using the advanced section of the toolkit, worked like a charm.

I have asked this a couple of times and no answer, just seems if we have a soft brick but can get into fastboot mode would be handy to get into recovery using that mode...please advise!!!! I also can`t be the only guy to have this problem!!!!
[Nexus 7 Android Development] danny8:
I have this issue as well -- that is I cannot enter CWM from my fastboot screen. I also updated my CWM to the 6.0.0.6 "grouper" image thinking that might correct the behavior.

I didn't post earlier because I was unfamiliar with fastboot.

It is now my understanding that the way to launch CWM (when cold booting) is to first enter fastboot by holding down volume-down key while booting, and then selecting recovery from the rolling menu.

Please let me know if I did not state that correctly. With my phone I was always able to enter CWM directly. There was no "fastboot" mode as far as I know. (Samsung Exhibit II)

As far as not being able to enter CWM that way' I suspect this issue lies beyond the scope of rooting or backing up. Please tell me if this issue indicates my phone is not set up properly.
[Nexus 7 Android Development] Galactic2:
i just updated to 4.1.1 my build number is JR003D ...

im not seeing it in the options.
[Nexus 7 Android Development] Ranger666:
AWESOME!!

Definitely one of the BEST tools I have used. Very simple and intuitive. Had my N7 unlocked and rooted with just a few clicks.

---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------

Make sure you are scrolling down to the Nexus 7 tablet section, all the way at the botton....its there.
[Nexus 7 Android Development] Galactic2:
It's not.

See:

They don't match...
[Nexus 7 Android Development] MWilt:
Use the JRO03c.....worked for me
[Nexus 7 Android Development] WugFresh:
Select JRO03C, it works. I have said this a bunch of times in this thread. I really need to add it to the OP.

{{ WugFresh }}
[Nexus 7 Android Development] caanda45:
I find that it will not boot into cwm that way from a cold boot for me, it hangs on the google screen.....I wish somebody with much greater knowledge here would help us!!!!!!!!
[Nexus 7 Android Development] zedorda:
This might help.
[Nexus 7 Android Development] WugFresh:
Please relax... No need for all those exclamation marks. This appears to be a reoccurring problem. I advise trying the following.

1. Try flashing CWM with ROM manager

2. Try flashing CWM the manual way with fastboot.

If both do not work, than the issue of cold booting into an alternate recovery is not related to the toolkit at all. It is most likely bootloader and/or recovery related and your questions about it should be directed at Koush (assuming that the above two suggestions do not work).

{{ WugFresh }}
[Nexus 7 Android Development] Galactic2:
thanks, it worked. wasn't sure... scared to brick a $250 device. lol
[Nexus 7 Android Development] WugFresh:
No problem. It's ok to want to play it safe. But believe me, if you want to brick a nexus, you will need to smash it with a brick. :)

{{ WugFresh }}
[Nexus 7 Android Development] danny8:
I think there's (perhaps) a nagging fear that being unable to access CWM from a cold boot puts one's tablet at risk in the event of a failed flash.

That was my initial reaction anyway. But there's ADB and probably several other ways for rescuing. I'm not planning to flash a new ROM any time soon, so no reason to freak out regardless.

I could have done more research before posting. Other people have been having this behavior too. I found it hard to sift through the extraneous commentary, so I figured I'd post about it.

My phone is now rooted which is what I was after. I'm going to watch and see what shakes out before I try anything more.
[Nexus 7 Android Development] WugFresh:
If you needed to, you could still access CWM from a cold boot using the boot Temp CWM button in advanced utilities of my toolkit. It will work if your device is in bootloader mode. You will have access to everything you would normally in CWM. This procedure does require a computer though. I understand why people want the ability to cold boot directly into CWM. I would want that too. However I currently believe that the problem is unrelated to my toolkit.

{{ WugFresh }}
[Nexus 7 Android Development] porkovich:
Hm i have a problem. I get a hashchech: failed error , trying to Flash Stock using the official image for my nexus 7. I have no idea why. I have redownloaded it several times , but with no luck ? Any ideas .....
[Nexus 7 Android Development] porkovich:
So that is why the hashchech is incorrect. So we should wait for them to fix the MD5 Chechsum or ..... i cannot see a way to bypassing it with the tool. (is it actually clever to buypass the chech ?
[Nexus 7 Android Development] WugFresh:
Just use these hashvalues instead when it asks you for it: https://plus.google.com/u/0/113329792100896065459/posts/5J1iFHMHZYM

{{ WugFresh }}
[Nexus 7 Android Development] ryomakun:
want ask something, when I want use "Flash Stock + Unroot" , i got a problem, i already download nakasi-krt16o-factory-db4a1a8a.tar and i want flash it by using "Flash Stock + Unroot" function, but when enter md5 , i always got error. I already using same md5 from google.. please help me
[Nexus 7 Android Development] WugFresh:
https://plus.google.com/113329792100896065459/posts/5J1iFHMHZYM

{{ WugFresh }}
[Nexus 7 Android Development] ryomakun:
ah really thaks for that.. but i have a problem :

nothing happened.. press any key just to close that dialog, my device still remain in bootloader and nothing changed
[Nexus 7 Android Development] porkovich:
All went well, thanks, but why is there no Select Runtime Option in the developer menu ? Is this ART (Android Runtime) not implementet for the nexus 7 (2012) ??
[Nexus 7 Android Development] dag1337:
Same thing happened to me. Stuck in bootloader still. Any idea how to get this up and running again?

---------- Post added at 05:11 PM ---------- Previous post was at 04:58 PM ----------

Also now ever time I try to flash stock anything below 4.4 from the toolkit I get a message that says fastboot.exe has stopped working. Which basically causes the whole thing to fail. When I try to flash 4.4 it fails at the end and stays stuck in the bootloader.

Not sure what to do at this point. Any ideas?
[Nexus 7 Android Development] cammel:
[MENTION=3110798]WugFresh[/MENTION] did you noticed that Google just changed some factory images names and md5 checksum numbers on their site?? What's going on here? Do you know or have any idea what they changed??

As far as I know n4 and n7 2012 have changed...

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 7 Android Development] WugFresh:
No, I am out at the bar drinking.. Lol.

I will check it out.
[Nexus 7 Android Development] cammel:
That's awesome! I wish I could be at a bar drinking right now! So jealous!! :beer::cool:

Don't worry, enjoy the night, there's no rush!

Cheers! ;)

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 7 Android Development] WugFresh:
:D just checked it on my phone. All is good. They changed the values to the same ones that I announced were correct earlier. Everything is straight. :)
[Nexus 7 Android Development] makbil:
I can confirm that. Now the md5 shown on the site matches the updated file.

Going to do a full wipe and reflash today using the new version of toolkit. Will post details on how it goes.

Thanks for providing this toolkit, makes life just that much easier :)