Database Users

How to root 4.4.2 nakasig

Hello! Can somebody help me with the question how can I root this device?
Please?

Try this man, i always use this guide for root and unlock with cwm.
https://m.youtube.com/watch?v=9C_QEYHzoEk

As far as I know there isn't a Exploit for 4.4.2, so you have to unlock the Bootloader at any rate.
If you just want to root, the easyiest way is just to boot the CF-Auto-Root boot image for your device: http://autoroot.chainfire.eu/
If you just want to flash custom roms, theres no need to root your actual ROM. Just flash the TWRP recovery Image via fastboot.

antila said:
Hello! Can somebody help me with the question how can I root this device?
Please?
Click to expand...
Click to collapse
Hi, antila...
Straightforward enough, if you know how to use fastboot...
------------------------------------------------
* Unlock the bootloader with fastboot oem unlock
-- BEWARE... THIS WILL FACTORY RESET THE NEXUS 7... and you will loose everything on it. All user installed apps and any files (music, video, pics etc.) will also be lost.
* Fastboot flash a Custom Recovery, such as CWM or TWRP, with fastboot flash recovery recovery.img
-- (where recovery.img is the name of the recovery image file to be fastboot flashed).
* Using that Custom Recovery, flash Chainfire's SuperSU root updater .zip.
* Reboot and you're rooted.
------------------------------------------------
I've written about this procedure in slightly more detail here.
The only thing that's changed since, is Chainfire's SuperSU root package has been updated to v1.86, and which you will find here...
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
If you prefer CWM to TWRP, then the latest CWM recovery can be found here...
http://www.clockworkmod.com/rommanager
(It's important you get the correct recovery for the particular type of Nexus 7 you have.)
For a fuller understanding of fastboot, checkout the 'stickies', particularly this one, which pertains directly to your question. It's a little out of date now... but the basic principles still hold.
This thread is also worth a look.
Good luck rooting your N7... (it's really not that difficult).
Rgrds,
Ged.

Root does't work
GedBlake said:
Hi, antila...
Straightforward enough, if you know how to use fastboot...
------------------------------------------------
* Unlock the bootloader with fastboot oem unlock
-- BEWARE... THIS WILL FACTORY RESET THE NEXUS 7... and you will loose everything on it. All user installed apps and any files (music, video, pics etc.) will also be lost.
* Fastboot flash a Custom Recovery, such as CWM or TWRP, with fastboot flash recovery recovery.img
-- (where recovery.img is the name of the recovery image file to be fastboot flashed).
* Using that Custom Recovery, flash Chainfire's SuperSU root updater .zip.
* Reboot and you're rooted.
------------------------------------------------
I've written about this procedure in slightly more detail here.
The only thing that's changed since, is Chainfire's SuperSU root package has been updated to v1.86, and which you will find here...
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
If you prefer CWM to TWRP, then the latest CWM recovery can be found here...
http://www.clockworkmod.com/rommanager
(It's important you get the correct recovery for the particular type of Nexus 7 you have.)
For a fuller understanding of fastboot, checkout the 'stickies', particularly this one, which pertains directly to your question. It's a little out of date now... but the basic principles still hold.
This thread is also worth a look.
Good luck rooting your N7... (it's really not that difficult).
Rgrds,
Ged.
Click to expand...
Click to collapse
Hello! Thank you for your help. I did everything as you wrote. Unlocked bootloader, installed TWRP but for some reason root still don't work. Can you give me a link on SuperSu where I can flash it trough TWRP? Please?
Thank you very much for your help.

Once you've got TWRP installed, just download the latest SuperSU (http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip), and flash it through TWRP.

antila said:
Hello! Thank you for your help. I did everything as you wrote. Unlocked bootloader, installed TWRP but for some reason root still don't work. Can you give me a link on SuperSu where I can flash it trough TWRP? Please?
Thank you very much for your help.
Click to expand...
Click to collapse
Hi, antila...
If you've unlocked the bootloader, and flashed TWRP... then you've pretty much done the 'hard' part..
As @jfmcbrayer says, download SuperSU v1.86 directly to your Nexus 7, and flash it in TWRP.
However, sometimes the SuperSU app icon doesn't always appear in the app drawer after the TWRP flash... although it's very likely you are actually (probably) rooted.
To fix this, see my post here.
If this **still** doesn't work... try flashing an older version of the SuperSU root .zip, available here...
http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
This will flash SuperSU v1.75... and then go to Google Playstore to update it to SuperSU v1.86. You will probably be prompted to do this anway, as soon as it is detected you're running a slightly out of date version...
Good luck.
Rgrds,
Ged.

Why didn't you just boot the CF-Autoboot bootimage as I suggested? It's the easyest way and you could have kept your stock recovery (less trouble with OTA Updates)
Just fastboot boot boot.img and a few seconds later your device is rooted...

Flashing stock recovery to Homecare TN7

I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.

Freeje said:
I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.
Click to expand...
Click to collapse
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.

e8hffff said:
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.
Click to expand...
Click to collapse
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.

Freeje said:
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.
Click to expand...
Click to collapse
Have you done an OEM unlock?
fastboot oem unlock

e8hffff said:
Have you done an OEM unlock?
fastboot oem unlock
Click to expand...
Click to collapse
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.

Freeje said:
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.
Click to expand...
Click to collapse
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.

e8hffff said:
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.
Click to expand...
Click to collapse
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back

homecare tegra note 7
Freeje said:
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back
Click to expand...
Click to collapse
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7

Tha T said:
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7
Click to expand...
Click to collapse
Don't know how to do that.

I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.

REcovry
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card

Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
so did the odex$.2.2 work fine or what solution did you use? And where did you get your 4.2 rom ?

Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.

Try using rootjunkie supertool and get new kit kat or flash another ROM very easy to use
Sent from my Moto G using XDA Premium 4 mobile app

Tha T said:
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card
Click to expand...
Click to collapse
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.

recovery
Freeje said:
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.
Click to expand...
Click to collapse
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen

e8hffff said:
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.
Click to expand...
Click to collapse
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.

Tha T said:
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen
Click to expand...
Click to collapse
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.

Freeje said:
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.
Click to expand...
Click to collapse
Yes try, TegraNote_bootimg_4p3p1rip.zip first as I haven't tested the 4.4 boot.img, and only use the boot.img within as there is another directory of the uncompress boot.

wifi
Freeje said:
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.
Click to expand...
Click to collapse
Does shaky156's version have a working wifi or any rom at all, (even 4.2) that has wifi, my TN7 is next to useless without it

New Factory Image and Custom Recovery

So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?

geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess

MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.

bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr

Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...

MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.

geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.

MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.

I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img

Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.

mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????

mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?

rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.

In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.

mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.

Rooted Nexus 6P - Possible to get OTA updates?

I recently unlocked the bootloader and rooted my Nexus 6P and just this evening received an update for the November Security Update. This downloads fine but when the phone reboots to install, it just goes to TWRP and doesn't install.
This is most likely incredibly simple and stupid for me even to ask, but is it possible to install one I've unlocked/rooted?
Any advice will be much appreciated.

You need the stock recovery to take otas Thats why it won't work
Sent from my Nexus 6P using XDA Free mobile app

Before, it initiates an update install. It checks root status. If it finds the device is rooted then it stops OTA install, to prevent any further damage to the phone.

In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Sent from my Nexus 6P using Tapatalk

Thanks for the quick answers guys. Many thanks.

rborg said:
In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you have gone as far as unlocking and rooting your phone, then you must have decided to go with some sort of ROM. If you do that, youll actually "typically" get the updates quicker from the developer than OTA. Just saying. And you dont lose your mods.

Does anyone have the stock recovery img handy? Should be easy to get OTA's with flashify that way.

HyperM3 said:
If you have gone as far as unlocking and rooting your phone, then you must have decided to go with some sort of ROM. If you do that, youll actually "typically" get the updates quicker from the developer than OTA. Just saying. And you dont lose your mods.
Click to expand...
Click to collapse
I was hoping to stay stock and use xposed when it is ready. So, no, I haven't gone that far in a long time.
Sent from my Nexus 6P using Tapatalk

The best way to get the ota updates for you would be to download the factory image from Google and Fastboot flash. If you dont wipe user data you should be able to keep most of your settings. You will also need to reflash chainfire's boot Img.

rborg said:
In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Click to expand...
Click to collapse
Here is what I do. So long as you do not flash or wipe userdata, this method should maintain all your app data and settings:
1. Download files:
* Latest factory image from: https://developers.google.com/android/nexus/images?hl=en and extract .img files to a folder on your computer with fastboot.
* Modified boot.img from: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 and extract boot.img to the same folder (I usually rename it to modifiedboot.img so I have have the original boot.img and modified images in the same folder).
* Latest version of TWRP from: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976 (direct link: https://dl.twrp.me/angler/) to the same folder
* Systemless SuperSU from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (do not unzip) to /sdcard/download folder on phone
2. Flash .img files using the following commands:
fastboot flash bootloader bootloader.img [using current name of bootloader image - not necessary if no change to bootloader from prior factory image]
fastboot reboot-bootloader
fastboot flash radio radio-angler.img [using current name of radio image - not necessary if no change to radio from prior factory image]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot modifiedboot.img
fastboot flash recovery twrp-2.8.7.x-angler.img [replace x with the current version]
3. Boot into recovery (TWRP), flash SuperSU.zip from /sdcard/download, wipe davlik and regular caches and reboot to system.
Upon reboot, Android will optimize all of your apps, so the first boot will take a while. However, the whole process usually takes me about 20 minutes - perhaps a bit more if I do a TWRP backup before upgrading (recommended).
---------- Post added at 10:25 AM ---------- Previous post was at 10:12 AM ----------
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP

rsmolen said:
Here is what I do. So long as you do not flash or wipe userdata, this method should maintain all your app data and settings:
1. Download files:
* Latest factory image from: https://developers.google.com/android/nexus/images?hl=en and extract .img files to a folder on your computer with fastboot.
* Modified boot.img from: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 and extract boot.img to the same folder (I usually rename it to modifiedboot.img so I have have the original boot.img and modified images in the same folder).
* Latest version of TWRP from: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976 (direct link: https://dl.twrp.me/angler/) to the same folder
* Systemless SuperSU from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (do not unzip) to /sdcard/download folder on phone
2. Flash .img files using the following commands:
fastboot flash bootloader bootloader.img [using current name of bootloader image - not necessary if no change to bootloader from prior factory image]
fastboot reboot-bootloader
fastboot flash radio radio-angler.img [using current name of radio image - not necessary if no change to radio from prior factory image]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot modifiedboot.img
fastboot flash recovery twrp-2.8.7.x-angler.img [replace x with the current version]
3. Boot into recovery (TWRP), flash SuperSU.zip from /sdcard/download, wipe davlik and regular caches and reboot to system.
Upon reboot, Android will optimize all of your apps, so the first boot will take a while. However, the whole process usually takes me about 20 minutes - perhaps a bit more if I do a TWRP backup before upgrading (recommended).
---------- Post added at 10:25 AM ---------- Previous post was at 10:12 AM ----------
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP
Click to expand...
Click to collapse
Thanks. This is helpful, even though it makes me feel like a baby. It's sad, considering we old-timers have been flashing **** that, at the time, seemed more complex. Or maybe it didn't. Never bricked a windows CE device. This isn't really 'complex' anyway. Just feels like far too many steps. I want a twrp flashable image, simply.
Sent from my Nexus 6P using Tapatalk

rborg said:
Thanks. This is helpful, even though it makes me feel like a baby. It's sad, considering we old-timers have been flashing **** that, at the time, seemed more complex. Or maybe it didn't. Never bricked a windows CE device. This isn't really 'complex' anyway. Just feels like far too many steps. I want a twrp flashable image, simply.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just use a custom rom and update as it gets updated.
More features, updated more often, flashable.
Easiest way to go.

Phazmos said:
Just use a custom rom and update as it gets updated.
More features, updated more often, flashable.
Easiest way to go.
Click to expand...
Click to collapse
Uhh how is flashing a custom ROM easier than just fastboot flashing system.img and vendor.img?

Cares said:
Uhh how is flashing a custom ROM easier than just fastboot flashing system.img and vendor.img?
Click to expand...
Click to collapse
Uhhh the most obvious answer would be no other peripherals required.

Phazmos said:
Uhhh the most obvious answer would be no other peripherals required.
Click to expand...
Click to collapse
Think about that for a second...you would have needed fastboot already to get a custom recovery onto your phone in the first place. You are flashing an entire ROM versus 2 files so it takes longer already. You'll need to update more files on first boot. Not faster or easier so not sure where your argument comes from.

Cares said:
Think about that for a second...you would have needed fastboot already to get a custom recovery onto your phone in the first place. You are flashing an entire ROM versus 2 files so it takes longer already. You'll need to update more files on first boot. Not faster or easier so not sure where your argument comes from.
Click to expand...
Click to collapse
Sorry, but if ya think it's slower or harder to download a rom and flash it, I don't know what to tell ya.

I really just want stock + xposed. So, I should really be looking for flashable security updates. Rooting doesn't necessarily imply that someone wants a custom ROM. *Not* needing a custom ROM to customize the OS is what xposed is all about. Making this choice doesn't mean we are idiots.
Sent from my Nexus 6P using Tapatalk

rborg said:
I really just want stock + xposed. So, I should really be looking for flashable security updates. Rooting doesn't necessarily imply that someone wants a custom ROM. *Not* needing a custom ROM to customize the OS is what xposed is all about. Making this choice doesn't mean we are idiots.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Xposed is very unstable. Most of the time causes reboots.

rsmolen said:
[/COLOR]
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP
Click to expand...
Click to collapse
Did anyone try this? Did it work? I am rooted but I have stock recovery (instead of flashing TWRP I just booted into it with fastboot for the SU install). Do I still need to flash the stock boot and recovery img's? I'm not sure what changes when SU is intalled. Thanks!
Edit - Does the "full unroot" button on SuperSU work? Is this all I would need to do since I did not permanently flash TWRP?

just did this. works perfectly. all data still there.
thanks!!!

Maybe I deleted my recovery, how can I fix?

I need some help. Just for context I was using these instructions here: https://www.cyanogenmods.org/download-twrp-oneplus-8-pro/
If you want some background, please read on and if not please skip to the next paragraph: I found the all in one tool on here with no instructions and lots of posts. I found some none TWRP possibilities but I don't know where those ROMs came from. I just wanted to root my phone and put a custom recovery. Is that even possible anymore? I researched this for a week and it seemed like everything was going to go well.
I got to:
Execute the below command to boot the TWRP temporarily:
fastboot boot recovery twrp-3.4.x-xx.img
Nothing happened. So I decided to replace "boot" with "flash" thinking it would work. Then, as I pressed it "temporarily" came into my head and I suspected I made a mistake. So when I tried to reboot to recovery and install MAGISK, it took me to the bootloader. This suggests that I have no recovery at all! Can anyone help me find the guide that will actually root my phone?

I think I fixed my problem. I looked around to see if there was another version of TWRP. I had issues with the 3T years ago and BluSpark made a custom TWRP recovery that worked for my phone at the time.
Anyway, I found this version: https://sourceforge.net/projects/mauronofrio-twrp/ I did the same command fastboot flash recovery and I was able to boot into TWRP and flash MAGISK!

reilus said:
I think I fixed my problem. I looked around to see if there was another version of TWRP. I had issues with the 3T years ago and BluSpark made a custom TWRP recovery that worked for my phone at the time.
Anyway, I found this version: https://sourceforge.net/projects/mauronofrio-twrp/ I did the same command fastboot flash recovery and I was able to boot into TWRP and flash MAGISK!
Click to expand...
Click to collapse
So this recovery is for oneplus 8 pro ?
Does it support flahing roms and img?

rowihel2012 said:
So this recovery is for oneplus 8 pro ?
Does it support flahing roms and img?
Click to expand...
Click to collapse
I am using the OnePlus 8 Pro. It's working on my phone so far as rebooting into the recovery and flashing the MAGISK 20.4 zip. I haven't tried ROMs or IMG. I used the 3.4.0-2.img