[SOLVED] [Q] Nexus 7 (grouper) with CM11 and F2FS - Nexus 7 Q&A, Help & Troubleshooting

Hi.
First I have to apologize for being a noob, and if I am posting questions that has already been answered. I can't post these question in the original thread about F2FS file system, so I am posting this here.
I am currently running stock Android 4.4.4 on my Nexus 7 WiFi (2012), and because it has become very slow, I want to root, install Cyanogenmod and use F2FS file system.
I have used CWM-recovery and installed custom roms on a Huawei device before, so I have some experience with this. I have also some experience with Linux and using ADB. But I don't want to brick my Nexus 7, so I have some questions before I start:
I want to unlock the bootloader and install custom recovery. I want to avoid using toolkits, as I don't know what they installs on my Nexus 7. I found a tutorial here that I am using, but I am not 100% sure if I am following the correct steps?:
1. Install SDK and drivers
2. Enable Debug on the Nexus 7
3. Download CWM-recovery to the same directory as adb.exe on my PC running Windows 8.1
4. With CMD: run command "adb reboot bootloader" then run command "fastboot oem unlock" (I know this will delete all data on my Nexus 7)
5. After unlocking, flash CWM-recovery with the steps from the tutorial: run command "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img".
6. Permanent flash CWM-recovery: mount "/System" and rename/backup "recovery-from-boot.p" with the command "mv recovery-from-boot.p recovery-from-boot.bak" (Is this step necessary? I have seen other tutorials skipping this step.)
7. Backup everything from recovery, and move the backup from the Nexus 7 to my PC. (I don't know if this step is necessary, but I'll do it anyway)
Are these seven steps above correct, or am I missing something? If the steps above are correct, then can I now install CM11 Snapshot M7 with F2FS with these steps?:
1. Download and copy "CM11.zip", "gapps.zip" and "LegoKernel-F2FS-140228.zip" from PC to Nexus 7, then install them from CWM-recovery.
2. Download "recovery-F2FS-A.img" to the same directory as adb.exe
3. Reboot the Nexus 7 into Android(CM11), activate Debug, run command "adb reboot bootloader" then flash custom TWRP with the command "fastboot flash recovery recovery-F2FS-A.img"
4. Reboot into TWRP-recovery, go to Wipe menu and format data.
5. Reboot into Android(CM11)
Will these seven+five steps work, or am I missing something? I don't want to brick my Nexus 7, so if someone could verify that these steps is correct, that would be great.
And one more question: Can I change back to CWM-recovery without losing the F2FS file system, or should I just use TWRP?
~Liloolil

Hi!
Liloolil said:
I am currently running stock Android 4.4.4 on my Nexus 7 WiFi (2012), and because it has become very slow, I want to root, install Cyanogenmod and use F2FS file system.
I have used CWM-recovery and installed custom roms on a Huawei device before, so I have some experience with this. I have also some experience with Linux and using ADB. But I don't want to brick my Nexus 7, so I have some questions before I start:
I want to unlock the bootloader and install custom recovery. I want to avoid using toolkits, as I don't know what they installs on my Nexus 7. I found a tutorial here that I am using, but I am not 100% sure if I am following the correct steps?:
1. Install SDK and drivers
2. Enable Debug on the Nexus 7
3. Download CWM-recovery to the same directory as adb.exe on my PC running Windows 8.1
4. With CMD: run command "adb reboot bootloader" then run command "fastboot oem unlock" (I know this will delete all data on my Nexus 7)
5. After unlocking, flash CWM-recovery with the steps from the tutorial: run command "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img".
6. Permanent flash CWM-recovery: mount "/System" and rename/backup "recovery-from-boot.p" with the command "mv recovery-from-boot.p recovery-from-boot.bak" (Is this step necessary? I have seen other tutorials skipping this step.)
7. Backup everything from recovery, and move the backup from the Nexus 7 to my PC. (I don't know if this step is necessary, but I'll do it anyway)
Click to expand...
Click to collapse
The tutorial sounds ok to me even though adb is not even needed to unlock the bootloader and flash a new recovery.
Instead you might need "fastboot" for this. Oh and I would use TWRP instead of CWM on the Nexus 7 (it includes F2FS support out of the box):
Code:
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.7.1.1-grouper.img
Liloolil said:
Are these seven steps above correct, or am I missing something? If the steps above are correct, then can I now install CM11 Snapshot M7 with F2FS with these steps?:
1. Download and copy "CM11.zip", "gapps.zip" and "LegoKernel-F2FS-140228.zip" from PC to Nexus 7, then install them from CWM-recovery.
2. Download "recovery-F2FS-A.img" to the same directory as adb.exe
3. Reboot the Nexus 7 into Android(CM11), activate Debug, run command "adb reboot bootloader" then flash custom TWRP with the command "fastboot flash recovery recovery-F2FS-A.img"
4. Reboot into TWRP-recovery, go to Wipe menu and format data.
5. Reboot into Android(CM11)
Will these seven+five steps work, or am I missing something? I don't want to brick my Nexus 7, so if someone could verify that these steps is correct, that would be great.
And one more question: Can I change back to CWM-recovery without losing the F2FS file system, or should I just use TWRP?
~Liloolil
Click to expand...
Click to collapse
As long as you can boot through fastboot, it should be ok to make experiments. I don't think that you can brick the device permanently.
Your tutorial again sounds good but I would choose a few different files instead. LegoKernel is from February 2014, there are other kernels in newer versions available...
I have just posted a howto for this in another thread: http://forum.xda-developers.com/showpost.php?p=54004629&postcount=3342
Good luck!

michael_ch said:
Hi!
The tutorial sounds ok to me even though adb is not even needed to unlock the bootloader and flash a new recovery.
Instead you might need "fastboot" for this. Oh and I would use TWRP instead of CWM on the Nexus 7 (it includes F2FS support out of the box):
Code:
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.7.1.1-grouper.img
As long as you can boot through fastboot, it should be ok to make experiments. I don't think that you can brick the device permanently.
Your tutorial again sounds good but I would choose a few different files instead. LegoKernel is from February 2014, there are other kernels in newer versions available...
I have just posted a howto for this in another thread: http://forum.xda-developers.com/showpost.php?p=54004629&postcount=3342
Good luck!
Click to expand...
Click to collapse
Thank you! I have now successfully rooted and installed CM11 on my Nexus 7.

Related

[Guide] Rooting Nexus 7 (Wi-Fi and 3G Edition) [Newbie-Friendly] [ADB/Fastboot]

Information: If you're experienced with ADB/Fastboot or Manual Android Rooting, you could read this thread and see if you find something that seems wrong and report to me, thanks!
Introduction​Hello there!
I decided to create a new Nexus 7 Rooting Guide, I know that there are some guides already, but I have a few reasons to make this guide.
Unlike many rooting guides, this one doesn't use an automated program (a.k.a Toolkit) and it works for both Nexus 7 Wi-Fi and Nexus 7 3G.
This guide has been tested with a Nexus 7 3G Edition, running Android 4.2.1/4.2.2.
Last Topic Update: Never
Last Minor Topic Update: Check thread edit date!
Requirements:
Nexus 7 (Wi-Fi or 3G Edition)
Android SDK
ADB/Fastboot Drivers
Unlocked Bootloader
If you don't have ADB/Fastboot drivers installed, please check out this thread:
http://forum.xda-developers.com/showthread.php?t=1907796
See Basic Knowledge and Driver Installation parts.
If you have Android SDK and ADB/Fastboot drivers installed and working, you can continue reading.
Make sure you have USB Debugging enabled in your Nexus 7.
Don't forget to unlock the bootloader!
Warning: You're the only one responsible if something bad happens to your device!
Nothing bad is going to happen, but there is always a small risk.
Personally, I recommend having +60% of Battery during ROM Changes (Flashing and etc).
I also recommend you to learn how to do a Factory Image Restore (Flash Stock ROM) before attempting to root...
Rooting your Nexus 7​
To root our device, we're simply going to put in our tablet a small program called "SuperSU", you might want to download it now to your PC:
SuperSU v1.04
Basically, we´re going to put SuperSU in /system partition, the file you downloaded is a "Flashable ZIP".
We're going to use TWRP (Team Win Recovery Project) to flash the Flashable ZIP (In this case, SuperSU), after flashing SuperSU you get root privileges!
Now, go to your Android SDK Folder where Fastboot (fastboot.exe) is located (platform-tools), open a command prompt and change directories to your Fastboot location, if you need help just search on Google.
Now, you have CMD (Command Prompt) open with the Android SDK Directory, and we need to reboot your device into Fastboot mode, to do that just type the following:
adb reboot-bootloader
Click to expand...
Click to collapse
You're now in Fastboot Mode (a.k.a Bootloader), type the following to make sure you're in Fastboot Mode:
fastboot devices
Click to expand...
Click to collapse
You should see something like this:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
Type "fastboot reboot" to reboot the device, then copy the SuperSU.zip you downloaded to your Nexus 7.
I also forgot to tell you to download TWRP, if you have the Nexus 7 Wi-Fi Edition, your board codename is Grouper, if you have the 3G Edition, your board codename is Tilapia.
TWRP for Nexus 7 [grouper]
TWRP for Nexus 7 3G [tilapia]
Copy the correct TWRP Edition to your Nexus 7, then boot into the bootloader.
Temporarily boot TWRP using the following command:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Replace "TWRP.img" with the correct file name.
You can also flash TWRP instead of temporarily booting.
Inside TWRP click "Install" and select the SuperSU ZIP File, then Confirm Flash.
After flashing, reboot your device and you should have SuperSU installed. (Open SuperSU just to test)
Congratulations! You now have a Rooted Device!
To make sure you have rooted, download "Root Checker" from Google Play.
Conclusion​As you can see, this tutorial is a little different from others, I explained what we were going to do and also explained the commands instead of giving you directly the commands.
This tutorial was written to teach the basics of ADB/Fastboot, I hope you rooted your device without problems and learnt/learned something, have a good day!
Feel free to give suggestions or corrections!
This work is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.​
Just for newbies wondering what this really means:
1. install and boot into TWRP/CWM recovery means you boot up a 'mini' linux which can do whatever it wants(as root) to any of the partition on the device(including the /system one)
2. the supersu package contains 2 files(an APK and the more importantly 'su') plus some update scripts that (1) would run and copy them to the appropriate places(mainly the 'su' which is the only file that is critical)
I think you need to mention the bootloader unlock someplace.
Perhaps you can find those specific instructions in another good reference thread; but if not then, at a minimum you should put it in your prerequisites list.
In the narrative as it stands, you casually mention the other thread
[GUIDE] Flashing a Factory Image with fastboot / return to stock
but don't insist that your reader looks at that thread.
But the time for doing the unlock sequence follows the begginers first (fastboot) driver installation, so unless someone reads that thread pretty thoroughly, they will skip it in your description here, and will get stopped out at
Code:
fastboot boot TWRP.img
which needs the privileges of an unlocked bootloader. Since unlocking the bootloader currently entails performing a full-phone wipe, the consequences of that are pretty significant and shouldn't be skipped over.
cheers. Thanks.
bftb0 said:
I think you need to mention the bootloader unlock someplace.
Perhaps you can find those specific instructions in another good reference thread; but if not then, at a minimum you should put it in your prerequisites list.
In the narrative as it stands, you casually mention the other thread
[GUIDE] Flashing a Factory Image with fastboot / return to stock
but don't insist that your reader looks at that thread.
But the time for doing the unlock sequence follows the begginers first (fastboot) driver installation, so unless someone reads that thread pretty thoroughly, they will skip it in your description here, and will get stopped out at
Code:
fastboot boot TWRP.img
which needs the privileges of an unlocked bootloader. Since unlocking the bootloader currently entails performing a full-phone wipe, the consequences of that are pretty significant and shouldn't be skipped over.
cheers. Thanks.
Click to expand...
Click to collapse
Hello!
Thanks for your answer, I completely forgot about the "Unlocking Bootloader" part, tomorrow when I get some time I will edit the thread...
Have a good day/night.
Edit: Added "Unlocked Bootloader" to the requisites list and a small note after "Make sure you have USB Debugging enabled in your Nexus 7", tomorrow I may edit the thread again.
Edit 2: I think the essential part is written, and because I'm a little busy, I will leave (temporarily) this thread. You're free to enhance this guide and re-publish it following Creative Commons Attribution-NonCommercial 3.0 Unported License.

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.

[Q] Boot Loop (CM Recovery)

First of all, I know that there are many people asking same thing. I have checked those threads and I guess I am just a little bit more clueless. Last time I was able to use my Nexus 10 was 3 months ago. Since then I tried to solve it many times, but no luck so far. I will try to explain some of the issues I'm experiencing, but I'm afraid I'm not too good with all the expressions people are using on this forum.
1. ADB vs Fastboot
I see this mentioned often and I don't know what exactly it means. It's amazing to me that I can't google it, I'm usually good with googling. I can see that my N10 is sometimes listed under ADB and sometimes under Fastboot devices but I have no idea what I did to change that. I do know that whatever I try to do at certain point, it's always in "wrong" mode, waiting for adb etc. So if someone can point me to a thorough explanation, a wiki or something, that would be very nice.
2. The Loop
I managed to get ClockworkMod v6.0.4.3 installed and it's this loop that device is now inside. I've tried pretty much all possible combinations, wiped both caches, did factory reset, rebooted to system/bootloader/recovery... nothing. Always ends up on same CM menu.
3. Android Toolkit
I have installed this on my computer and tried so many things that I forgot about all details. I tried flashing the big 400 MB stock image to the device, but haven't been successful (says waiting for ADB, even if the device WAS listed as ADB device before I started the procedure). I am also expecting to see the N10 as another "drive" from my desktop, if you know what I mean, so that I could copy files to it. However I don't see it that way, I only see it registered as a Nexus 10 device, like a mouse or any other non-drive device. Is this normal?
So what to do? Can anyone tell me in a simple way, because I am obviously stupid enough to find threads I've seen so far not clear enough. And I would actually think that my computer literacy level is rather high, I think that this Nexus 10 is the only thing that brought me to my knees in last 20 years of working with computers.
And when I say "simple wiki style" I'm thinking of something like this:
Ok. no links allowed, great. It's a redmondpie article named
/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
This is easy enough for me... but do I assume correctly that all this has already been done with me installing Android Toolkit? If so, it uses a different path structure and I don't see all those folders...
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Sent from my Nexus 10 using Tapatalk
newellj79 said:
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Click to expand...
Click to collapse
You mean flashing ROM only with CWM, not through android toolkit? Through CWM menu I have tried (many times):
- wipe data / factory reset
- wipe cache partition
- wipe dalwik cache
I don't see way to do anything with:
- install zip
- backup and restore
- mounts and storage
Rebooting menu items do following:
- Reboot system --> reboots to same CWM recovery menu
- Reboot to bootloader --> reboots to the stock bootloader "menu" where I can choose between Start, Power Off, Recovery mode (picking this will reboot to CWM recovery menu) and Restart bootloader (picking this will reboot to this same menu)
- Reboot recovery --> reboots to same CWM recovery menu
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The first part worked ok. The second part doesn't.
ADB sideload - I went there in the Nexus menu
adb sideload kitkat2501.zip
returns this:
* failed to write data 'protocol fault (no status)' *
If I do it without starting adb sideload on nexus, then it just says "error: closed", so it does recognize the change.
I downloaded the latest sdk tool, 64-bit, and the stock nexus 10 rom from 25th Janaury.
Let's do this, grab the latest stock for manta from here
https://developers.google.com/android/nexus/images
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Let's do this, grab the latest stock for manta from here
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are a wizard. I got it all ok now and I added CWM to it, it was easy to root it from there.

[Root] Zenfone 2 Official Android 6.0 Root + Xposed and Downgrade

**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca. If you like his work, please make him a small donation for encouragement.
2. This is a systemless root. Yet you need to unlook Lollipop before upgrading to Marshmallow.
3. Flashing the attached SuperSU file modifies stock boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
Root:
1. Unlock your device in Lollipop, then upgrade to Android 6.0
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. This TWRP is recommended.
HTML:
adb reboot-bootloader
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp. /OR install the SuperSU in twrp if you saved it in device storage.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Unroot:
Just flash back stock boot.img
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: Download Xposed Installer here
Downgrade to Lollipop:
In case you need to downgrade to Lollipop, follow the instructions with care. Do it at your risk.
Refer to Asus Zentalk Forum and grab the required files from there.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot reboot-bootloader
Now you are back in Lollipop. You can flash back stock recovery(.184 recommended), wipe the device(cache/userdata/system) and then sideload back stock LP or MM as you wish. OR, you can flash custom recovery/boot/system.img start from here.
Good luck!
It worked!Thank you master!I bow now....
I just need root on 6.0.1. Is this going to achieve that?
MikeyLee said:
I just need root on 6.0.1. Is this going to achieve that?
Click to expand...
Click to collapse
According to op it will
Sent from my ASUS_Z00AD using Tapatalk
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
pokey006 said:
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
Click to expand...
Click to collapse
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
samcjtsai said:
1. All credits go to @shakalaca and I just try to recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum but, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Works like a charm !! Thanks !!
kamyk70 said:
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
Click to expand...
Click to collapse
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
when update to 6.0. bootloader unlocked again ! how can i flash twrp ?
pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
No it does not
Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thank You for explaining that to me, appreciated!
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
euthic said:
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
Click to expand...
Click to collapse
You need to adb sideload all LP .184 images first then use Asus FlashTool to flash RAW Firmware.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
root works perfect along with systemless xposed, but i still cant pass safenet check..(super su disabled, and also xposed) so no AP.. is that normal ?
pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
ponhei9502 said:
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
Click to expand...
Click to collapse
Guess your ZF2 is not unlocked in LP first, so that you can't see twrp booting. Since you are in Android 6.0 now, try to downgrade to LP, Unlock it, upgrade to 6.0 and then root.
samcjtsai said:
**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca and I just recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Where are these files again? They aren't in the zip
thanks, works great, was able to downgrade to lollipop with no problem what so ever. Install twrp, gain root again, and rockin custom roms...

Thor & 4.5.5.2 : Easy to root and Unlock Bootloader

Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work. Some even report success after 20 tries.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in the thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Added another instructions from another forumer who think my instructions is not complete:-
1. Install the moto driver and then plug in your device while running normal
2. Run the get_code.bat (from this link)
3. once unlock.code file is created, run "adb reboot bootloader". It will show [Fastboot] with the kf logo.
4. Once bootloader comes up, change driver in device manager for "Other Android" to use the Android -> Mot Adb Composite Driver. It should say "Ready" on the KF
5. Run the stuff from this post (do the bottom steps with fastboot erase first)
6. After you are done in bulk mode, hold the power button for 15 secs to reboot. It will automatically boot into Fastboot
7. When you run the unlock command, use the "unlock.code" file.. not the "0xmmssssssss.unlock" example from that link.
8. Now unplug and hold power again to shut down. Hold VolUp + Power. About 3 secs after you see the KF logo, you can let go of the power button (possibly both buttons) and you get TWRP
From here you can flash CM and gapps (5.1).
Click to expand...
Click to collapse
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
BatmanDC said:
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
Click to expand...
Click to collapse
You do not need to be on 4.5.5.2 or any specific version of FireOS for that matter. Is the device rooted?
BatmanDC said:
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
Click to expand...
Click to collapse
As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.
kkcheong said:
As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.
Click to expand...
Click to collapse
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
are those instructions as daunting as they sound?
it seems if you kingroot and wipe everything it negates any malware?
barrist said:
...it seems if you kingroot and wipe everything it negates any malware?
Click to expand...
Click to collapse
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.
draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
Davey126 said:
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.
Click to expand...
Click to collapse
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?
barrist said:
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?
Click to expand...
Click to collapse
There are no bad/unstable HDX ROMs. Fire Nexus has the advantage for those needed full Bluetooth and/or LTE support. Otherwise LineageOS 14.1 is a solid choice. Regardless of direction you'll want to unlock the bootloader and wipe the device immediately after rooting if KingRoot is utilized. Also know Amazon devices have their own set of quirks and don't behave like a typical Android gizmo.
Thanks maybe I'll give lineage a shot as I don't really don't need LTE or bt .. just hoping for stable app support and wifi
draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:
nice, instructions worked, running lineage 14.1 and no problems so far!
kkcheong said:
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:
Click to expand...
Click to collapse
No problem.
Given that you wipe 'data' (which I prefer not to, because I'm too lazy to make backups),
you should be fine with KingRoot, it just takes much longer, but that's your choice.
The real risk is making a mistake when flashing aboot and TWRP, which is the same on both paths.
kkcheong said:
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Click to expand...
Click to collapse
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?
xyluss0 said:
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?
Click to expand...
Click to collapse
Have you put both file in the adb directory?
Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".
xyluss0 said:
Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".
Click to expand...
Click to collapse
Please print screen. Did you cd to ADB directory?
Root hdx 7 (3rd Gen.), FireOS 4.5.5.2 with towelroot
Hi,
I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.
Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.
Do i need working internet connection during rooting process with APKs ?
Thx in advance
Achimbub
Root fails
kkcheong said:
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Click to expand...
Click to collapse
I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?
achimbub said:
Hi,
I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.
Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.
Do i need working internet connection during rooting process with APKs ?
Thx in advance
Achimbub
Click to expand...
Click to collapse
- TowelRoot is ineffective on FireOS v4
- recommend desktop version of KingRoot for 4.5.5.2 (still may not work)
- device does not need an active internet connection with desktop version
---------- Post added at 04:58 AM ---------- Previous post was at 04:55 AM ----------
bobcat131 said:
I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?
Click to expand...
Click to collapse
KingOroot is the only other tool that reportedly works on 4.5.5.2. It also has a reputation for screwing up devices. Risky choice.

Categories

Resources