[frenetic]

I think it's hilarious how many posts I see saying Recovery doesn't work, when they select options, it just goes to a blank screen with the clockwork logo.

IT IS A TOUCH RECOVERY. touch it!

That said! I don't have root. Everything I see on the device says I have root, but can't edit system without adb

 

[Dbl_Tap]

I used the Nexus Root Toolkit v1.5.2 and went from a computer not setup for adb to everything working and connected, including drivers, and had my N7 unlocked and rooted in no time at all. I even used the Toolkit to fastboot and load the updated CWM Touch Recovery.

 

[sfreemanoh]

Maybe I'm doing something stupid...I downloaded the OEM image and extracted it. However, there's only a single file in it, named "nakasi-jrn84d-factory-8b0bd791". WTH?

Edit: Ignore this. WinWAR wasn't extracting it correctly...and neither was 7-Zip. BUT, using 7-Zip I was then able to open the extracted file, even though it didn't appear as an archive file, and the 4 files were in there. I'm all set now.

 

[Nickles]

Question folks.
My shiny new 7 will be arriving tomorrow.. I know there has already been a 4.1.1 OTA update pushing out.
should i power up and sign in, and wait to get this OTA, and THEN unlock?

or should i power up, sign in, and immediately unlock. if i do that, will i still be able to install the 4.1.1 initial OTA?

 

[k.electron]

Question folks.
My shiny new 7 will be arriving tomorrow.. I know there has already been a 4.1.1 OTA update pushing out.
should i power up and sign in, and wait to get this OTA, and THEN unlock?

or should i power up, sign in, and immediately unlock. if i do that, will i still be able to install the 4.1.1 initial OTA?

bootloader locking / unlocking has no effect on the ota.

 

[Dbl_Tap]

I took the update and then unlocked and rooted. No issues.

 

[Mike02z]

I'm not sure if it was mentioned in this thread (too lazy to read more than 4 pages) but most people will be unable to access recovery on the 7 via the Vol - + PWR buttons using either TWRP or CWM. This appears to be specific to the 7. Yes, there are multiple apps you can download that will allow you to boot into recovery with no issue. The problem is when you bork your OS and you need to get into recovery using the buttons.

The work around is to plug your 7 into your PC. When you do this, you should be able to get into recovery by using the buttons. I tested this multiple times with both TWRP and CWM and it worked every time. Not sure if you want to add this to the FAQ's for the 7.

 

[Kimboinatl]

NOTE: The reason you see "sudo" before all of my commands is because I'm running Linux.

OK, so I somehow managed to bork my tablet, then got it back up and running using a deodexed boot image someone posted up on here... but then I realized it was a 4.1 boot image, and could not get it to update to 4.1.1. Sooooo I decided to go back to stock.

Following the directions in the OP, I got to this step:

sudo fastboot -w update nakasi-jrn84d/image-nakasi-jrn84d.zip

And I get this error:

archive does not contain 'boot.sig'<br />
archive does not contain 'recovery.sig'<br />
archive does not contain 'system.sig'<br />
< waiting for device >

Doing a "fastboot devices" showed my tablet. I just could not flash the .zip file. After I got done cleaning the fudgie out of my pants, I tried unzipping the zip file and individually flashing each image file:

sudo fastboot flash recovery recovery.img<br />
sudo fastboot flash boot boot.img<br />
sudo fastboot flash system system.img<br />
sudo fastboot flash userdata userdata.img

All of these worked. I rebooted back into the bootloader, then started my device up, and everything appears to be good.

Just wanted to pass this along in case anyone runs into the same problem.

 

[k.electron]

fastboot -w update nakasi-jrn84d/image-nakasi-jrn84d.zip

And I get this error:

archive does not contain 'boot.sig'<br />
archive does not contain 'recovery.sig'<br />
archive does not contain 'system.sig'<br />
< waiting for device >

interesting.
never had this problem myself. thanks for bringing it to everyones notice.

 

[nhat]

does "fastboot -w update" work with any rom? or does it have to be the factory image?

 

[k.electron]

does "fastboot -w update" work with any rom? or does it have to be the factory image?

i think the community roms are structured differently and therefore need to installed via recovery and not fastboot. i personally would never try a custom rom with fastboot. just flash cwm and you are good to go.

experts: if i am wrong, please dont shoot me.

 

[Cannonball_CO]

Has anyone installed recovery-clockwork-touch-6.0.1.0-grouper.img and found it worked? I went with 6.0.0.6 yesterday, and it boots fine, then installed the bleeding edge today and it wouldn't boot into recovery. Reflashed 6.0.0.6 and I'm back in business.

Also, is there any reason I should install the custom bootloader? I'm rooted with CWM permanent... what does the custom bootloader do?

 

[yaoverstand]

So I tried to flash a rom and was stuck at the google screen. Long story short, I attempted to adb different roms and recoveries to the device to fix it and nothing worked, so I followed this guide exactly. When I try to boot the device, the Google screen shows with my unlocked bootloader symbol, but in the upper right hand corner it says "Booting Failed" and the bootloader arrow pointing to the power button is displayed. I am trying to go back to stock, and now I have nothing lol. Any ideas?

EDIT: Excuse my ignorance. the last command in the guide was not entered correctly by me. Works like a charm...THANKS!

 

[dansan]

If I just wanted to get rid of clockwork mod and stay on stock recovery would fast boot erase -recovery do the job? Like a moron I unlocked and rooted before I took the 4.1.1 update and it keeps bugging me to update. I kind of want to stay on stock rom for Noe though. Im either thinking I'll just do fast boot OEM lock but if I can just save time by just erasing clockwork, then loading the update and then reflashing clockwork

 

[exzacklyright]

I sort of made a noobier guide based off yours but included adb. Yes i was bored tonight

http://exzacklyright...ng-rooting.html

 

[nickmo]

Going back to stock tomorrow when my replacement arrives. Thanks for the info

 

[Kimboinatl]

If I just wanted to get rid of clockwork mod and stay on stock recovery would fast boot erase -recovery do the job? Like a moron I unlocked and rooted before I took the 4.1.1 update and it keeps bugging me to update. I kind of want to stay on stock rom for Noe though. Im either thinking I'll just do fast boot OEM lock but if I can just save time by just erasing clockwork, then loading the update and then reflashing clockwork

No, you have to also flash the stock recovery back to the ROM. If you just delete it then there would be NO recovery

Check out this post: http://rootzwiki.com..._60#entry833473

You would want to get the stock image, then unzip it and use the recovery image in it. Once you have that, delete it as you did above, then run this:

fastboot flash recovery recovery.img

 

[My_Name_Is_Neo]

What is the reasoning behind re-flashing the bootloader?
Is this not enough? oem Unlock -> new recovery -> recovery overwrite blocker -> flash root

 

[k.electron]

What is the reasoning behind re-flashing the bootloader?
Is this not enough? oem Unlock -> new recovery -> recovery overwrite blocker -> flash root

there is really no reason to flash bootloaders until they have more than one and have some discernible benefit over each other.

 

[exzacklyright]

1. fastboot flash bootloader nakasi-jrn84d/bootloader-grouper-3.34.img

Shouldn't it be

<br />
fastboot flash bootloader nakasi-jro03d/bootloader-grouper-3.34.img<br />