Database Users

Fastboot> Recovery dosen't find *.img file on SD card

Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks

What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.

You didn't unzip them did you?

You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.

Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.

Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery

I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?

[Q]root before updating?

I just purchased a N7 yesterday, and it's supposed to arrive in a couple of days. I'm using a Mac OS computer and comfortable with ADB, so which is better: root first before updating the firmware, or update to the most recent version of firmare and then root? And which rooting method do you recommend with a Mac?
Thanks for your suggestions!

mj56gt said:
I just purchased a N7 yesterday, and it's supposed to arrive in a couple of days. I'm using a Mac OS computer and comfortable with ADB, so which is better: root first before updating the firmware, or update to the most recent version of firmare and then root? And which rooting method do you recommend with a Mac?
Thanks for your suggestions!
Click to expand...
Click to collapse
I would update first then root, and use wug's toolkit to help you through the process.

mj56gt said:
I just purchased a N7 yesterday, and it's supposed to arrive in a couple of days. I'm using a Mac OS computer and comfortable with ADB, so which is better: root first before updating the firmware, or update to the most recent version of firmare and then root? And which rooting method do you recommend with a Mac?
Thanks for your suggestions!
Click to expand...
Click to collapse
I personally have done the following steps:
- I've rooted it first;
- installed OTA RootKeeper (to keep the root after updating - the app must be configured before updating firmware);
- I've updated the firmware to the last version.
I performed all those steps using my notebook which has Windows 7 OS, so for Mac OS I cannot make any recommendation.
I hope this helps you.

Thank you both for the suggestions! Is the Wug's toolkit for Windows OS? Any such toolkit for Mac OS or Linux system? Thanks!

Leonhan said:
I would update first then root, and use wug's toolkit to help you through the process.
Click to expand...
Click to collapse
Good Dog. The OP said he had a Mac.
@OP
May as well do stock firmware upgrade first if it is needed.* On the rare chance that you get a device that suffers some kind of infant mortality - the device will be pure stock for the first little bit of operation (in case an RMA is needed). And the flashing operations which take place IF an OTA is needed will give flash memory a little workout.
Just bear in mind that the bootloader unlock operation will erase everything from /data (factory reset) when the "fastboot unlock" command occurs. So, if you operate the device as pure stock for a while, you will either need to backup stuff or regard your initial customizations as disposable.
fastboot methods are the most expeditious way to proceed on a Mac.
If you use TWRP 2.4.4.0 as your custom recovery, it will peek in /system to see if you are rooted and offer to root your device with SuperSU for you (just before you reboot from within TWRP).
The way I see it, the rooting procedure is 4 steps total:
(Note: use the "tilapia", not grouper recovery image if you have the 3G/LTE Nexus 7)
Code:
fastboot unlock
fastboot boot openrecovery-twrp-2.4.4.0-grouper.img
... make a pure stock Nandroid backup
... reboot TWRP and it will offer to install SuperSU for you
(optionally: fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img )
Those 4 steps above will leave you with Pure Stock + Rooted ; even the recovery on the tablet will be pure stock until you flash it there (optional step 5 above).
It's up to you to get the Mac SDK (for fastboot & adb) installed and figure out using command lines - search for that, don't ask.
good luck
* I thought I saw a report recently that someone had JDQ39 on a device purchased less than 4 weeks after the last update - your device may not need upgrading yet.

bftb0 said:
@OP
May as well do stock firmware upgrade first if it is needed.* On the rare chance that you get a device that suffers some kind of infant mortality - the device will be pure stock for the first little bit of operation (in case an RMA is needed). And the flashing operations which take place IF an OTA is needed will give flash memory a little workout.
Just bear in mind that the bootloader unlock operation will erase everything from /data (factory reset) when the "fastboot unlock" command occurs. So, if you operate the device as pure stock for a while, you will either need to backup stuff or regard your initial customizations as disposable.
fastboot methods are the most expeditious way to proceed on a Mac.
If you use TWRP 2.4.4.0 as your custom recovery, it will peek in /system to see if you are rooted and offer to root your device with SuperSU for you (just before you reboot from within TWRP).
The way I see it, the rooting procedure is 4 steps total:
(Note: use the "tilapia", not grouper recovery image if you have the 3G/LTE Nexus 7)
Code:
fastboot unlock
fastboot boot openrecovery-twrp-2.4.4.0-grouper.img
... make a pure stock Nandroid backup
... reboot TWRP and it will offer to install SuperSU for you
(optionally: fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img )
Those 4 steps above will leave you with Pure Stock + Rooted ; even the recovery on the tablet will be pure stock until you flash it there (optional step 5 above).
It's up to you to get the Mac SDK (for fastboot & adb) installed and figure out using command lines - search for that, don't ask.
good luck
* I thought I saw a report recently that someone had JDQ39 on a device purchased less than 4 weeks after the last update - your device may not need upgrading yet.
Click to expand...
Click to collapse
Thanks a lot for the detailed information and the kind help, bftb0! I really appreciated it.
I had a two-year-old version of Mac SDK, and only used adb before. Just finished grabbing the most recent version. I prefer command lines instead of button pushing. Once N7 arrives, I will start to have fun with fastboot...

bftb0 said:
Code:
fastboot unlock
fastboot boot openrecovery-twrp-2.4.4.0-grouper.img
... make a pure stock Nandroid backup
... reboot TWRP and it will offer to install SuperSU for you
(optionally: fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img )
Click to expand...
Click to collapse
One more question. Is the first step (unlocking) necessary for the later steps such as root access? The reason I'm asking is that, unlike rooting, unlocking is irreversible, and would avoid the warranty.
Edit: I guess that the bootloader has to be unlocked to flash a custom recovery, right?

Unlocking is necessary to use fastboot commands and it's not irreversible as you can relock it with "fastboot oem lock" but if you want to unlock it another time it will wipe your device again. And if you flash recovery with fastboot then yes your bootloader must be unlocked but you can relock it after.

Nico_60 said:
Unlocking is necessary to use fastboot commands and it's not irreversible as you can relock it with "fastboot oem lock" but if you want to unlock it another time it will wipe your device again. And if you flash recovery with fastboot then yes your bootloader must be unlocked but you can relock it after.
Click to expand...
Click to collapse
That's great! Thanks a lot for the help...

Help rerooting after 4.3

My wife has a rooted nexus 7 2012 wifi and she unintentionally accepted the ota Android 4.3 update. So of course it unrooted her.
I originally had a hell of a time rooting this tablet using wugfresh nexus toolkit. Took me several days to succeed and the same thing is happening again. My Windows 7 laptop keeps installing the wrong drivers even though I selected the option to disable the auto driver configuration. Also USBDeview never shows the installed Samsung adb drivers yet when I try to install them I am warned they are already installed. It's already been hours and who knows how many retries and reboots!
So even though I'm a newbie I decided to go the Android sdk route.
1. Where do I download the files I need to just root the darn tablet?
2. What do I do next?
Please keep it simple........
Anyone want to walk me through it on the phone?
Thanks

If you are new to using SDK, check this out for a well laid out tut on how to get set up and rooted.

I now have android sdk set up.
What are the commands I should issue to root?
Thanks

now you need to flash a custom recovery then flash a root zip file via windows command prompt...Have you figured out how to interface with your device and the windows command prompt? eg;
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
-then you would issue "adb reboot bootloader"
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
-then while in bootloader toggle with the volume keys to "recovery" option and press power
-now you will be in your new recovery you just flashed and you can push the zipped root file you chose to the sdcard, "adb push rootyouchose.zip /sdcard/"
-once its been pushed you can flash it in recovery and reboot, and you are now rooted
-this is the latest cwm recovery that you could flash in fastboot as described above
-this would be the root file you want to push then flash in recovery
-this may be of some help, scroll down halfway

Thank you so much for helping. You can't know how much it is appreciated.
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
Got that. It works!!
-then you would issue "adb reboot bootloader"
Worked! Got the Android on his back.
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
Is recovery image on my pc or the tablet?
Why do I have to indicate the img name here if I will later select it

When I write
Fastboot flash......... Img
I get
Unknown partition 'the image file name'
"error : cannot determine image filename for. '.......'

You need to have downloaded a recovery image, that is what you flash I linked to one on my last post, that file is called "recovery-clockwork-touch-6.0.4.3-grouper.img" so you would issue,
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img
"fastboot flash recovery" is telling it to flash a recovery file and "recovery-clockwork-touch-6.0.4.3-grouper.img" is the recovery file in this case to be flashed so, combined its, "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img"
I do not use Windows, I use a terminal instead of windows command prompt so I can't be specific as I am not too familiar with windows command prompt. With terminal it is much easier in my opinion but you need to be running nix or Mac OS to have a terminal

OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks

Anderson2 said:
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks
Click to expand...
Click to collapse
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.

GedBlake said:
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.
Click to expand...
Click to collapse
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.

Anderson2 said:
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
Click to expand...
Click to collapse
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it.
...but I assume your Nexus 7's bootloader is already unlocked, given it's been rooted once before.
And so swiftly skipping forward to step 2...
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.

GedBlake said:
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it. I assume your bootloader is already unlocked.
So swiftly skipping forward to step 2....
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.

Anderson2 said:
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
Click to expand...
Click to collapse
Hello again, Anderson2...
Well, you sort of are already doing something in return.... you're asking questions.
Questions that require answers. Those answers, whoever posts them, may be of assistance to somebody else. Somebody else looking for a solution to a similar problem.
I always look upon these forums as a means of sharing. Not everybody can know everything. God knows, I don't know everything.... and I've been messing around with Android for three years now. So don't worry so much about it being a quid pro quo sort of arrangement.
I know what I know primarily as a result of my own experiences and what I've learned here from the many (in most cases, more knowledgeable) posters here on XDA. What you learn today, you can pass on to others, tomorrow (metaphorically speaking). We, all of us, stand on the shoulders of each other.
With regard to the second generation Nexus 7 (2013)... I'm afraid I really don't know much about it... but I'd be surprised if rooting it deviated significantly from rooting the first generation Nexus 7....
Namely...
1). Unlock the bootloader.
2). Flash a Custom Recovery.
3). Using that Custom Recovery, flash some SU root package... probably from Chainfire.
Anyway, I've found this tutorial here...
http://forum.xda-developers.com/showthread.php?t=2382051
...and it appears to follow a very similar template.
The Nexus 7 (2013) forum itself, which is also worth visiting, is located here....
http://forum.xda-developers.com/nexus-7-2013
Rgrds,
Ged.

[INFO] How to sideload 5.1.1 (LYZ28E), & maintain no encryption - no wipe required

[INFO] How to sideload 5.1.1 (LYZ28E), & maintain no encryption - no wipe required
Simplified procedures with LMY47M / LYZ28E now available as a factory image.
Hopefully this isn't blatantly obvious to everyone, it is a little different than the normal sideload procedure. Thought it might be useful to some who want to load 5.1.1 (and get Wifi calling with T-Mobile!) and not be forced to encrypt.
Requirements:
1. I'm assuming you have adb/fastboot working on your computer / connecting to your device and you understand a little bit about using adb / fastboot with an android phone.
2. Your phone cannot be encrypted, if you're encrypted already - this will not un-encrypt your data - you need to turn off forced encryption and format the "userdata" partition to disable the encryption.
3. You need to have an unlocked bootloader for this to work of course.
How to follow this procedure:
1. If you're on LMY47M (T-Mobile) and unencrypted, you can follow option 2, starting with Step 3 - only a small ~150MB download required.
2. If you're on anything other than LMY47M, you should use option 1 unless you have a desire to flash LMY47M and sideload LYZ28E.
I didn't do much here - except spent a bunch of time writing the procedure.
All Credit for tools / ideas goes to:
- efrant for his explanation of how to get OTA updates to work with TWRP ( http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919/page4 )
- hlxanthus for the NO FORCE ENCRYPT mod ( http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788 )
- Q9Nap and mhous33 for the LMY47M factory image ( http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 )
- bbedward and others for the original disable forced encryption boot.img ( http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715 )
- TeamWin - the TWRP Developer ( https://twrp.me/ )
——————————————————————————————————
OPTION 1 - Easy Method - Flash the LYZ28E factory image directly:
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Download LYZ28E for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lyz28e-factory-b542b88a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img (OPTIONAL - If you have TWRP or another alternative recovery you can skip this step)
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Restart the Bootloader, and flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the Bootloader again and then go to Recovery (TWRP). Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!
———————————————————————————————————————————————————
OPTION 2 - SIDELOAD Method (Makes sense if you’re already on LMY47M):
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Follow the normal procedure, if you're already on LMY47M you can skip to step 3. Download LMY47M for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lmy47m-factory-5228e84a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Now flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the bootloader, and enter recovery mode (TWRP). Once in TWRP, go to Advanced -> ADB Sideload. You may need to unplug/plug in the USB cable to your computer again.
Download my version of LYZ28E from here: https://www.androidfilehost.com/?fid=23991606952609905
Note: I modified this version to work with TWRP, it will not work with the stock recovery (because I modified it, the signature on the file is now invalid). The only thing I changed was I edited the updater-script to remove the release keys check which seems to fail on the stock recovery and doesn't work right with TWRP).
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
5. After it finishes, do not reboot yet. Go back and I recommend rebooting to recovery again. Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!

why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.

simms22 said:
why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.
Click to expand...
Click to collapse
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.

liqice said:
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.
Click to expand...
Click to collapse
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.

simms22 said:
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.
Click to expand...
Click to collapse
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?

Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.

cam30era said:
Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.
Click to expand...
Click to collapse
Thanks, updated the original post.

liqice said:
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?
Click to expand...
Click to collapse
easier/harder isnt an option here, since any way takes seconds. im just saying there are several options for this, thats all

liqice said:
Code:
fastboot flash f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
Click to expand...
Click to collapse
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?

So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?

Chahk said:
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?
Click to expand...
Click to collapse
Oops, you're right. Thanks!

Gage_Hero said:
So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?
Click to expand...
Click to collapse
This is where I was, LMY47E, rooted, unencrypted and with TWRP. I followed the entire procedure - went back to LRX22C using fastboot, then sideloaded LMY47M (T-Mobile version) - then flashed the no force encrypt boot.img - booted, after it finished booting, rebooted to the bootloader and so on ...
When you go to LRX22C you flash back to the stock recovery. So you need to boot into the stock recovery, pick "apply update from adb" and then run the adb sideload command from the PC.

Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?

With the factory images being posted, I just did the following:
Flashed the factory images
While still in bootloader, flashed TWRP
Rebooted into TWRP
Pushed SuperSU and the No_Force_encrypt to the /sdcard/ partition
Installed via TWRP
Profit.

lamenting said:
Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?
Click to expand...
Click to collapse
For LMY47D you need to get to LMY47M first, so you would follow the entire procedure, downgrade to LRX22C and then sideload LMY47M and so on.

Heavily updated the procedure since LMY47M and LYZ28E factory images are now available directly from Google.
Should be a lot easier and more straight forward now!

I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?

Boot loader and radio only...
So if I understand the instructions correctly, if you are still encrypted but rooted, from any Lollipop installation, fast boot flash the factory images... then flash TWRP ... root and done right? Then I have another question... the kernel I am running EX 1.07 along with Flar's app is running perfect for me.... any dangers in just flashing the boot loader and radio? I would like to wait on the system part until the kernel has been updated.....
Also, if I needed to do a restore, if I only flash the boot loader and radio have I pooched being able to go backwards to a nand backup?

FYI, step 3 in option one should read:
fastboot flash recovery twrp-2.8.6.0-shamu.img
vs
fastboot flash twrp-2.8.6.0-shamu.img

frater said:
I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?
Click to expand...
Click to collapse
Starting with Android Lollipop (5.0) and newer - at least on the Nexus 6 - encryption is turned on by default for the userdata partition.
You would - if you wanted to - backup all of the data on your userdata partition (e.g. Any pictures you've taken with the phone, etc - all of the data basically that shows up when you plug your phone into your computer).
Then you need to be running an OS that doesn't force encryption (for example if you follow my instructions) - this would also get you running 5.1.1.
After that you need to format your userdata - it wouldn't be encrypted at that point, and then copy your data back if you want to.
If you don't care about encryption, you can simply flash the factory 5.1.1 image following my instructions and skip the TWRP parts.

Unable to root using Nexus Root Toolkit 2.1.0 and Nexus Player Marshmallow MRA58N

I am having a difficult time rooting my Nexus Player on Marshmallow 6.0 MRA58N
I select the "Root" option and it pushes 3 files to my Nexus Player. Then it boots into TWRP and I plug in my mouse so I can flash:
-beta-supersu-v2.52.zip and
-busybox-signed
Then I reboot system but that's when I get the stuck logo.
I flash the provided files in recovery and then I reboot. However, when I reboot, I just see the animated logo (the one with the balls bouncing from left to right). It is stuck there. What am I doing wrong?

Same problem here, someone help plez.

I haven't even been able to get ADB or Fastboot to detect my NP.

fastboot flash in bootloader (do it manually) and heres all the stuff you will use/need:
http://forum.xda-developers.com/nexus-player/orig-development/marshmallow-mra58n-root-t3256647
I would recommend flashing PureNexus rom if your rooting. Million times better then stock, in my opinion. Its MM and pre rooted too. If your up for that, check it here:
http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232

I am unable to sideload PureNexus.
dfl said:
fastboot flash in bootloader (do it manually) and heres all the stuff you will use/need:
http://forum.xda-developers.com/nexus-player/orig-development/marshmallow-mra58n-root-t3256647
I would recommend flashing PureNexus rom if your rooting. Million times better then stock, in my opinion. Its MM and pre rooted too. If your up for that, check it here:
http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
Click to expand...
Click to collapse
Hi I have tried to sideload to PureNexus using the instructions from http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
I am receiving Footer is wrong and Signature validation failure errors.
Unlock your bootloader using fastboot. (fastboot oem unlock)
Flash PureNexus recovery. (fastboot flash recovery "purenexus_fugu_recovery-112515.img")
Reboot Bootloader (fastboot reboot bootloader)
Once in bootloader short press bottom button once until you see recovery option then long press the bottom button.
Once in recovery short press until you get to ADB then long press to get to the ADB sideload screen.
Sideload Rom (adb sideload pure_nexus_fugu-6.0-2015xxxx.zip) where xxxx is the date of the rom you are flashing..THIS IS WHERE I RECEIVE ERROR.
Sideload Gapps (adb sideload purenexus-gapps-mm-x86-leanback-20151202-signed.zip)
Short press until you get to Wipe data/factory Reset then long press (Clears data & cache)
Select reboot now
Once booted setup everything including Kodi
Then go back to recovery and sideload Kodi Mapping zip file. (adb sideload NexusPlayer-kodi-keymap-streaming-fix-signed.zip
Can you please help?
My Nexus Player just upgraded to Android 6.0 using the instructions from, http://forum.xda-developers.com/nexus-player/general/guide-nexus-player-how-to-unlock-t2961989.
Thanks...

dfl said:
fastboot flash in bootloader (do it manually) and heres all the stuff you will use/need:
http://forum.xda-developers.com/nexus-player/orig-development/marshmallow-mra58n-root-t3256647
I would recommend flashing PureNexus rom if your rooting. Million times better then stock, in my opinion. Its MM and pre rooted too. If your up for that, check it here:
http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
Click to expand...
Click to collapse
I installed PureNexus as well, it's pretty nice. I lost adb debugging though, can't get adb to detect the nexus player unless I boot into recovery oddly.