Database Develop

[TUTORIAL] Full Steps to Acheive Root + ClockwordMod Recovery with new KA6 2.2

I have put together some steps to take your fresh KA6 2.2 Official update and add Root and ClockworkMod Recovery. It may look hard, but should only take a couple minutes.
This is without ODIN or ROMS.
Steps:
0. Have yourself a T-Mobile Vibrant and PC Running Windows.
1. Use SuperOneClick (latest) to root phone. When you run the application, click the first button on the left and wait for the process to complete. Details will be scrolling in the middle window.(http://forum.xda-developers.com/showthread.php?t=803682)
2. Use a file manager (ROOT EXPLORER) or adb with root access to mount /system/ and remove bloatware (SLACKERRADIO and AMAZONMP3 and such) from /system/app/
2a. TOTAL NOOBS: Get SUPER MANAGER from the market (FREE). Then grant it root by going into SUPER MANAGER and selecting File Manager > [Menu BUTTON] > Setup > Enable ROOT function. Then go up levels, the top button on the file manager which will take you up a directory, until you get to / and scroll to the bottom and select [system]. Then select [app]. Then click [Menu BUTTON] > Switch System to R/W and press R/W. Scroll down and long press the slackerradio.apk to delete. You can do this too amazon market to delete and other useless apps.​
3. YOU NEED STEP 2 TO DO THIS STEP! Install Busybox from Market and run Busybox Installer to ensure its properly working and the latest is installed.
4. Run SuperOneClick again to place phone into shell root ADB (Second button from the left). Allow the process to run and then a pop up will say something about rebooting the phone. DO NOT DO THIS, continue on to the next step.
5. While in shell root from the previous step, run (3e) to (2e) modified recovery script. The instructions are simple. Download, unzip, and run the batch file found inside. This is ran from the COMPUTER NOT YOUR PHONE. Use the menu system to complete and then reboot as recommended. (http://forum.xda-developers.com/showthread.php?t=833423).
5a. NOT NOOBS: you can copy over the recovery yourself to /system/bin as mentioned by some commenters. If you do not know what this is, then ignore it.​
6. Remove any update.zip files from /sdcard/ and also remove any ClockworkMod directories using your favorite file manager or by mounting to a computer with a wire and activating the drive for My Computer. This is the internal one, not external.
7. Use ROM MANAGER from market to install ClockworkMod Recovery and reboot. This is free to download. When you launch, select the top item to install the recovery and then a menu will pop up to choose the phone you have. Happily select Vibrant. Once that's done, select reboot into recover right below that.
8. Re-install packages and it should reboot. You can navigate the menu using VOL UP AND DOWN and power to select.
9. Re-install packages again and it should boot into Clockwork Recovery. It should change form BLUE TO GREEN
ALL DONE.
That should do it for ya! Let me know if it worked out. Please follow all steps and don't cut corners.
Should you need to get back to ClockworkMod Recovery, you can use "adb reboot recovery" and re-install packages, or reboot into recovery with ROM MANAGER.
Edit Rev.a: added a step (6) Made the instructions more precise and added additional steps to clear up some confusion.(1-22-11)
Edit Rev.b: Added step 2a from request. root explorer is not free so use super, that works too. (1-24-11)
Edit Rev.c: Added more detail to the steps and added supplemental info for replacing the recovery with the modified one. (1-27-11)
Edit Rev.d: Super1Click has updated, so latest? works.
Side note: I do step 4 because from my experience, I had trouble getting the modified 3e script to get root. Figured might as well just give it root to begin with.
Side note: Yes I am aware that there are other methods and different ways. This was the noob way for me to convey it to the masses. I still do appreciate all feedback regardless of what it is. Thanks!
jmcghee1973:
***For kicks you can do your 2.2 KA6 update the download Supercurio's KA6 voodoo kernel and ODIN it and have Root & CWM all in one shot.

***For kicks you can do your 2.2 KA6 update then download Supercurio's KA6 voodoo kernel and ODIN it and have Root & CWM all in one shot.
Not to hijack your thread...

Yea I know, but I wanted to find a way without ODIN.
added ur blurp

Reinstalling packages does not seem to work for me. Every time I click it and it reboots it keeps going into the samsung recovery menu... Help?

Does it give an error for signing or just looks like its working then reboots?

Looks like it works and then reboots
I didn't do this step though, would it affect anything?
2.Use a file manager or adb with root access to mount /system/ and remove bloatware (SLACKER and AMAZONMP3) from /system/app/

Double check if there is a update.zip and clockworkmod folder with a zip in it on your internal memory. I think the external card changed directories with the 2.2 update.
EDIT: infact, remove any update.zip and clockwork folder from the internal memory and run ROM MANAGER again and fresh download the clockwork 2.5.1.2. then check and confirm its on the internal. should be /sdcard/
once its confirmed there, then try again to reboot into recovery with rom manager

Nothingness00 said:
Double check if there is a update.zip and clockworkmod folder with a zip in it on your internal memory. I think the external card stopped working with the 2.2 update.
EDIT: infact, remove any update.zip and clockwork folder from the internal memory and run ROM MANAGER again and fresh download the clockwork 2.5.1.2. then check and confirm its on the internal. should be /sdcard/
once its confirmed there, then try again to reboot into recovery with rom manager
Click to expand...
Click to collapse
Tried that, still can't get into clockwork recovery...
I didn't do this step though, would it affect anything?
2.Use a file manager or adb with root access to mount /system/ and remove bloatware (SLACKER and AMAZONMP3) from /system/app/

I would highly suggest doing that step. The system is full to begin with. Use Root Explorer and grant access, then mount system into r/w and remove the stupid stuff. You should do this to get Busybox on (AS IN BEFORE YOU INSTALL BUSYBOX)

What does busybox do?

jmoreau10 said:
What does busybox do?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/BusyBox
ITS ESSENTIAL

Got it working man, thanks.

Awesome! Good to hear. This is my first tutorial and I'm stoked that its working well for others.

I've been an XDA visitor since my AT&T Titan WM6 days. I've done alot of flashing and modding since then and have always been able to find solutions without asking until now. This clockwork recovery issue is kicking my butt.
I am having trouble with steps 4 & 5.
what are the specific buttons to press on superoneclick in step 4?
How exactly do I use the file 3(e)_recovery_installer?
Thanks for any help.

dsilver981 said:
I've been an XDA visitor since my AT&T Titan WM6 days. I've done alot of flashing and modding since then and have always been able to find solutions without asking until now. This clockwork recovery issue is kicking my butt.
I am having trouble with steps 4 & 5.
what are the specific buttons to press on superoneclick in step 4?
How exactly do I use the file 3(e)_recovery_installer?
Thanks for any help.
Click to expand...
Click to collapse
4. Run SuperOneClick again to place phone into root shell ADB
For this step, run SuperOneClick from before, the same you used to root. The second button says "Shell Root". Click that Wait for it to say you have shell root until you reset.
5. Run (3e) to (2e) modified recovery script (http://forum.xda-developers.com/showthread.php?t=833423)
Just download the attachment in the first post and follow instructions. Its fairly simple process. Keep in mind, this may not work unless your phone is shell root from step 4

Thank you Nothingness. Cleared it right up. Worked perfectly.

dsilver981 said:
Thank you Nothingness. Cleared it right up. Worked perfectly.
Click to expand...
Click to collapse
Awesome! Great to hear it! Love them thanks

im a total noob, but im about to try this, wish me luck haha

thoetherguy said:
im a total noob, but im about to try this, wish me luck haha
Click to expand...
Click to collapse
Luck? ****'s easy as pi. Well... Er... Just follow the steps to a tee.

Nothingness00 said:
Luck? ****'s easy as pi. Well... Er... Just follow the steps to a tee.
Click to expand...
Click to collapse
haha, yeah it was easy , thanks...

[Q] Rooted with unrevoked but apps do not recognize it

Hello,
I am a DINC owner and I am working on my brother's VZW DINC2 and I am trying to gain root.
First I installed the the newest GB RUU. (His phone was stuck on stock froyo and but would not update.) It installed flawlessly.
( RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_3.02.605.1_Ra dio_1.09.01.0622_NV_VZW1.92_release_202929_signed from http://forum.xda-developers.com/showthread.php?t=1033922 )
Then I ran the unrevoked beta and it installed without error and then installed clockworkmod recovery from it as well.
Now after I installed Root explorer, TI, CWM, busy box and superuser but they all claim to not be able to access root? I rebooted and tried again but not dice.
I ran unrevoked beta again and it said it was already s-off. Is there a special DINC2 trick I missed? Any ideas or troubleshooting suggestions?
Thanks in advance,
-Paul

Nevermind I missed some steps. http://forum.xda-developers.com/showthread.php?t=1219246 RTFM!
10 - On your phone, back track to the main menu of HBoot using the volume keys and Power button and select recovery (2nd Option). In a few seconds your will be in CWM.
11 - As long as you copied the signed zip file to the root of your sdcard, perform the following:
"Install Zip From SDCard" (5th Option)
"Choose Zip From SDCard" (2nd Option)
Select the root/su zip file (su-2.3.6.3-efgh-signed.zip)
Choose Yes and wait.
Back track to main menu and reboot
Click to expand...
Click to collapse
An extra step that I did not have to do on my DINC... Live and learn, cheers!

[Q] Is it safe to root a ICS stock rom?

Hey dudes, I want to root my note to have more options to work with, but Im quite afraid that something wont go as planned.
I updated my note to ICS ( LPY ) stock from germany ( 4.0.3 ), and Ive seen a couple of post explaining how to do it, some of them through CMW, others through ODIN.
So Ive got two questions:
Is it really safe to root without any trouble? ( I know nothing is 100% safe, but as far as I know a lot of people have bricked their notes either flasing ICS custom roms or rooting ) So Im quite afraid by that.
And if its really safe to do, wich way is the safer?
Cheers.

Its relatively safe, its what you do before and afterwards thats probably not. Dont wipe anything, or factory reset on ICS unless you have read its safe (like cm9 from entrophy, xplodwild and co)
Just follow any of the many tutorials and you will be fine.
Notice: moment you root you loose warranty
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Its relatively safe, its what you do before and afterwards thats probably not. Dont wipe anything, or factory reset on ICS unless you have read its safe (like cm9 from entrophy, xplodwild and co)
Just follow any of the many tutorials and you will be fine.
Notice: moment you root you loose warranty
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I know that I loose warranty, but I also know that I can unroot
Yes I actually knew something about factory resets or wipe things can damage it.
Thanks

Please read here ;http://forum.xda-developers.com/showthread.php?t=1659768 .....Make sure to download the Toolkit from the link at the end of this post and put the "Root" .zip in your device's internal memory. You will enter Bootloader Mode, and then Recovery Mode as detailed in the FAQ above. You will now select "install zip from sdcard" then "choose zip from sdcard" and look for the Root.zip which you previously put in your SDcard. Select it with the Power button to flash it and then reboot your device. When your device finally boots, check if the Superuser app is available, if it is then you're rooted now.
*Fixing Root*
In some cases a ROM can come with a broken root. You will need to flash a file with root encountered in this LINK. Be sure to download from the device if possible and select the appropiate version, yes the one that as of this writing says "Eclair/Froyo/Gingerbread/Honeycomb/IceCreamSandwich (2.1 – 4.0.3)". It also works with Android 4.0.4. Flash that package using CWM Recovery, by selecting "install zip from sdcard" then "choose zip from sdcard" and you're set.
[Unrooting]:::::::::::::::::::::::::::::::::::::::::::
There are two ways to unroot: the automatic way (which consists of a CWM Recovery flashable little file provided in the Toolkit link at the end of this guide) and the manual way. For the manual way I will here quote phonic's excellent post (modified the word "program" with "app" to avoid confusion and added an app link):
So if you want to unroot your tablet, you simply need to remove the 'su' binary. There are various ways to accomplish this, but one of the easier methods would be to download/install a terminal app such as "Terminal Emulator", launch it, and issue the following commands:
Code:
su
mount -o remount, rw /system
rm /system/app/Superuser.apk
rm /system/bin/su (or "xbin" instead of "bin" in some cases)
umount -o remount, ro /system
exit

root is safe but u loose warranty...u can also unroot ur phone to get the warranty again
Sent from my Galaxy Mini using xda premium

[HOW-TO]Unlock, Root and install CWM step by step

This HOW-TO is meant for individuals who like to do things manually and see each process as they occur, versus using a toolkit. I prefer manually unlocking/rooting as I can confirm each step visually and I believe it makes for a more educational experience. Familiarity and confidence with fastboot/adb can be beneficial later on for restoring/troubleshooting/flashing etc down the road.
Unknown at this point if OTA updates will install after flashing CWM. There may be a check file in the OTA that could prevent installation if modified file structure is detected. I’ll edit when I confirm. At any rate, not really an issue as you can flash the OTA yourself as someone on XDA will most likely post it up, or you could re-flash the stock recovery using fastboot which you will now be comfortable with after using this guide! Additionally, if an OTA causes you to lose root you can revisit the appropriate steps to flash SuperSU again.
There are several ways to do these procedures, and I’ve certainly taken the long way on some of them. So by no means am I claiming this to the best or most efficient method, but my hopes are to make things a little more clear and simple based off some of the questions and challenges I’ve seen in a few threads.
This how-to was written for Windows and uses adb and fastboot for installation.
Please let me know of any corrections, additions or errors. Many thanks to the members and devs who made these files available.
1. Download all of the following files and place them in the same directory. I will note whether you need to extract them or not.
Download and extract platform-tools-v16.zip from here: (thanks to efrant)
http://forum.xda-developers.com/showthread.php?t=1626895
Download and extract [ADB/FB/APX Driver] Universal Naked Driver 0.72 from here:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Download SuperSU from here: (look for UPDATE-SuperSU-v1.25.zip or current version)
http://forum.xda-developers.com/showthread.php?t=1538053
Download ClockworkMod from here: (look for Galaxy Nexus 7, Download Recovery 6.0.3.1 or current version – Recommend non-Touch as of ver 6.0.10, some reported issues with the Touch version)
http://www.clockworkmod.com/rommanager/
2. Now we will install the drivers and verify they are working. If you cannot verify drivers are functioning in both normal boot and recovery you need to stop and figure out what you are doing wrong. Proceeding further would be pointless. If you are having trouble, visit the Naked Driver thread listed above or here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
a. Make sure you have USB debugging enabled on your Nexus: setttings ->develop options ->USB Debugging.
b. USB connect your Nexus to your Windows pc. If you get a notification for unknown/driver not found, look in Device Manager for the exclamation point, and right click for update driver software, then browse my computer, then point to where you saved and extracted the Universal Naked Driver folder. If you get a warning from Windows complaining the driver is not signed, hit ‘Install driver anyway’. After the driver installs, you should now have ‘Nexus 7’ listed under ‘Portable Devices’ with no exclamation point.
Now we will verify using adb. You will need to launch a command prompt from the directory you saved all the files from step 1 to. Easiest way is to navigate to the directory via file explorer, then hold down shift and the RIGHT mouse button, and select “Open command window from here”.
In the cmd prompt, type:
adb devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again. You should see something like:
List of devices attached
945d3339495 device
if instead you see:
List of devices attached
945d3339495 offline
then most likely you need to look on your nexus for a notice to allow the connected computer permissions to use usb debugging. If you don't see a notice, disable/enable usb debugging in "Settings -> Developer options" and then you should get the prompt. You should select 'remember this computer', if not you will have to do it again upon reboot.
c. Now we need to reboot into the bootloader and load the drivers again. So type:
adb reboot bootloader
and your Nexus should reboot into the bootloader. My laptop found the driver on its own, note that in Device Manager it is now listed as ‘Android Device’ instead of under ‘Portable Devices’. If your system does not find the driver, follow the same steps as above to update your driver after you located the exclamation point in Device Manager.
Now we will verify that the driver is installed correctly while in the bootloader. Again from a command prompt opened from the directory where you saved all the files from step 1, type:
fastboot devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again.
3. Perform device unlock. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! Please backup accordingly.
Your Nexus should still be in the bootloader. Type:
fastboot oem unlock
Your Nexus will prompt you to accept. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! After a short moment, the device should report unlocked under “lock state”. Reboot device by typing:
fastboot reboot
After rebooting, sign in, etc.
4. Copy over SuperSU . In windows explorer locate the UPDATE-SuperSU-v1.25.zip and copy it to your Nexus internal storage area. Don’t put it any of the folders, just dump it in there. Now reboot into the bootloader again by typing:
adb reboot bootloader
5. Flash CWM. Once in the bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
after you get ‘finished’ from the command window, reboot your Nexus into CWM recovery by navigating with the volume buttons to ‘recovery mode’, then press power button.
6. Root Nexus. Using the volume keys, navigate to ‘install zip from sdcard’ and hit the power button. Now select ‘choose zip from sdcard’ and hit the power button. Navigate down to UPDATE-SuperSU-v1.25.zip’ and hit the power button. Select ‘Yes’, hit power. Once done select ‘go back’, then ‘reboot system now’.
Congrats, you’ve unlocked and rooted your Nexus!
Now at this point CWM recovery may or may not still be present on your device. There have been mixed reports on whether it will ‘stick’ the first time you flash it. The stock ROM has a check file that will replace CWM with the stock recovery upon reboot. To determine if CWM is still present simply reboot into recovery and see if it is there. Type:
adb reboot recovery
Obviously if you see the droid with exclamation point CWM did not stick. If you have no need for CWM, and simply wanted root you could stop now. Wait a few minutes and your device will reboot on its own and you are all done.
However, if you desire CWM then proceed on.
7. Rename recovery-from-boot.p to prevent stock recovery re-installation. Your Nexus should be booted normally at this point.
a. Go to the Play store and install ES File Explorer File Manager. Under settings enable ‘up to root’, ‘root explorer’, and ’mount file system’.
b. Navigate to /system and rename:
recovery-from-boot.p
to
recovery-from-boot.bak
by long pressing and selecting ‘rename’. Note: Be careful while navigating your device with these options enabled, a typo or slip-up could cripple your device and require a restore. I suggest once this rename is competed to disable the above options to avoid any mistakes in future exploring.
8. Flash CWM again.
a. Reboot into bootloader by typing:
adb reboot bootloader
b. once in bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
c. reboot device by typing:
fastboot reboot
d. verify CWM stuck by rebooting into recovery:
adb reboot recovery
And that should be it!
Some additional notes: CWM does make notice on rebooting with a message ”ROM may flash stock recovery on reboot. Fix? This can not be undone”. I don’t know what CWM will do there, so I prefer to rename the recovery-from-boot file so that I could easily restore it if I wanted. But perhaps that is what CWM does, although the message persists even after I renamed the file. Maybe someone could clarify this.
Hope this helps some people out in enjoying this great device even more, thanks for reading.

4.1.2 and 4.2.1 updates...
Thought I would revisit the thread as we've had two updates since I wrote the above. I installed 4.1.2 OTA with no problems but as expected, I lost root and CWM.
Because I'm lazy, I didn't worry over it much and then 4.2.1 shows up and also installed perfectly. Finally got around to getting root back and here are the steps I used.
Notes:
* Need to make sure drivers are correctly installed. See first post.
* I never really used CWM so I elected not to permanently install it this time.
* This update is a brief synopsis of how I got root back. If the steps are not clear, review the first post as the procedure is very similar.
1.) Ensure USB debugging is still enabled. On 4.2.1 "Developers options" are hidden by default. To enable simply tap "Settings > About tablet > Build number" 7 times. Back out and "Developers options" should now be available. In my case USB debugging was still enabled.
2.) Download SuperSU v0.99 and CWM 6.0.1.9 from links in first post. I used non-touch version of CWM.
3.) Transfer SuperSU over to internal storage of your Nexus. Be sure you know where you dumped it.
4.) Reboot into bootloader: adb reboot bootloader
5.) Temporarily boot or permanently install CWM so we can install SuperSU zip.
for temp boot type: fastboot boot recovery-clockwork-6.0.1.9-grouper.img
for perm install type: fastboot flash recovery recovery-clockwork-6.0.1.9-grouper.img
6.) Once in CWM select:
a. install zip from sdcard
b. choose zip from sdcard
c. navigate to /0/ then wherever you put SuperSU
7.) Once finished back out and reboot system now. I selected "No" on allowing CWM to disable stock recovery. If you are only temp booting CWM then this likely won't matter either choice you make. If you perm flashed CWM then you may wish to choose 'Yes".
That should cover it. Thanks for reading, any questions or corrections be sure to let me know.

I have a question about this:
I rooted and installed CWM on my 4.2 N7, but now, then I try to install the 4.2.1 OTA update, I get this error:
Code:
assert failed: apply_patch_check("/system/lib/libweb rtc_audio_preprocessing.so", "bin_number", "big_number""),
E: error in /cache/jop40d-from-jop40c.zip
(Status 7)
It's wise to apply this if I already have a rooted+CWM N7?

Some root procedures, or third party apps like Titanium Pro can make changes to certain system files that will cause an official update to fail. In your case, it appears at least "rtc_audio_preprocessing.so" located in "/system/lib/libweb" has been altered.
The easiest solution is to flash the current factory image then root. You can find them here: https://developers.google.com/android/nexus/images#nakasi.
However, you will lose your data. So back up accordingly.
If that's not an option, you can try:
a.) figure out which app you have that caused the change, and see if it has a 'revert' option or if uninstalling will put the file(s) back to stock.
b.) find the unmodified contents of /system/app and /system/lib and replace yours. Needs to be from 4.2 in your case.
c.) find a modified manual update patch (either zip for CWM or .img for fastboot) that has been altered to ignore the integrity check.

Curious, just went looking for "rtc_audio_preprocessing.so" in a factory 4.2 system.img and can not locate it, or the lib/libweb directory. Perhaps a third party app made these additions and thus the integrity check is failing as the files are unknown/unaccounted for?
At any rate, I went ahead and sourced a 4.2 system.img and extracted the /app and /lib directories in case this helps you or anyone else searching along.
Extracted from: nakasi-jop40c-factory-6aabb391.tgz
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip.md5
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip.md5

so I factory-reseted my N7, but it didn't helped. I found the file /system/lib/libwebrtc_audio_preprocessing.so so I tried to replace it with the file you posted (thanks btw!), but while using a console (su, then cp file.so file.so.backup) I get the error saying it's a read-only system, so I can't replace that file
any other idea?
EDIT: So I was playing around with the N7 (although I can really remember, I think I formated /system ?):
So, yeah, I actually formated /system for some unknown reason and there is no OS to boot, so I'm downloading at 25 KBps (yes...I know) and I'll be installing the JOP40D version for the N7.

ah, so the file is actually:
/lib/libwebrtc_audio_preprocessing.so
not
/lib/libweb/rtc_audio_preprocessing.so
That makes a little more sense. On cp over the original file, as you discovered the /system partition needs to be remounted as writable before you would be able to make changes. You could easily accomplish this with one of the root file explorers from the market. I use "ES File Explorer" as its free. Then simply copy over your file.
Or if you prefer adb: mount -o remount rw /system
Regardless, you are starting over from scratch so no worries. One of the things I love about this device is the option to start fresh-from-factory with minimal fuss.

igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA

cub0ne said:
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
Click to expand...
Click to collapse
I am also on 4.2.1 unlocked and rooted with wugfresh toolkit. I downloaded CWM from the play store, the app can download the latest CWM recovery and flash it for you. That is what I did, All I have used CWM for is a nandroid backup, but have booted into recovery and wiped cache and fixed permission
Has anyone had issue is SuperSU and CWM running Fix Permissions in the CWM app? I get an error...

Thank you!
Thank you very much for the excellent guide, your explanations were very clear!
It was a lot of fun following it, and I am very happy for choosing this guide over the 'one-click' toolkits.

I'll give it a try
After trying a "all in one toolbox" to unlock and root I think I'll give this a shot. I got stuck at not being able to root and like your OP said, doing it manually would help with the learning curve.
Quick questions that has popped up is.
Do I lock my bootloader back to use your guide?
I've noticed drivers I have in device manager have different names. Does this mean there are dif drivers that do the same thing? Should i delete them and use the ones in the OP?

Late response, but I'll answer for future users following this thread...
Once your bootloader is unlocked by any means, no need to relock in order to follow this guide. We simply have to have it unlocked so we can gain root
Drivers are probably the most common issues people have in any instance of trying to interact with their device. While its not imperative that the names are the same, what is most important is that you can communicate with the device. There really isn't the right or wrong driver name, just that the driver works! Having said that, if you are wondering whether you have the correct drivers installed, simply follow the steps and attempt a "adb devices" or "fastboot devices" command depending on your device status as is outlined in the tutorial. If you do not have the appropriate response, then you need to stop and determine the issue.

Update after OTA 4.2.2
Lost root as expected, and followed procedure in post #2 to gain root back. Also updated OP file versions to current as of this post as they all worked successfully.
Only thing I would note: If you get a "offline" notice after trying 'adb devices', be sure to check your nexus for a notification to allow the connected computer access for USB debugging. If you don't see one, go to "Settings -> Developer options" and disable/enable USB debugging and it should pop up. I don't remember this behavior when I first wrote the tutorial, so it may be something new for 4.2.2. After reboot it will require approval again, so you may wish to select 'remember this computer'. I added this note in the OP as well in the appropriate step.

Problem with Hasoon2000's all in one kit

I noticed that in the most recent version of Hasoon2000's kit, when I tried to use the "APK Installer" function, a file was missing, and thus I was unable to install SuperSU Binary. If there is a fix or a work-around, it would be incredible useful if someone could tell me about it. (I am new to this place, and I can't post on the dev's thread or else I would)
I also can't post images it seems.. uggh.

I would recommend just flashing the SU package manually. If you already did the step of flashing a custom recovery, the next step is really simple.
Here's all you have to do:
1) Go into the folder of Hasoon's tool, then into Data, then into SU
2) Copy the SuperSU.zip to your SD card
3) Reboot your phone into recovery (hold pwr button and vol down as the phone powers up)
4) Choose Recovery
5) In which ever recovery you have, find the install option, browse for the SuperSU.zip
6) Flash!
7) Reboot and enjoy root
Hope that helps!
Edit: Ha! I just looked at the script for installing root from Hasoon's tool. Literally all it does is copy that SuperSU.zip to your SD card, then displays the same instructions I have above but in less detail.