Database Users

4.3 Factory image with custom recovery?

I apologize for the noob question but I've never found myself in this particular situation...
I've decided to stick with the 4.3 JWR66V factory image while I wait for a working rooted version to be released or even an updated SuperSU or Superuser zip (that doesn't drain the battery or lose root with certain apps).
I used the factory image found HERE and followed the detailed instructions found HERE. I followed the instructions under section "D" vigorously which meant that I installed the stock recovery image as well. Everything is running as it should. However, I was curious if it was safe to flash TWRP 2.6.0.0 recovery through fastboot with my current setup. I'd like to use that recovery to wipe cache/dalvik and possibly fix permissions. However, I'm not sure if this will break something so I am hesitant to try it.
I have made sure the bootloader is unlocked. But I am curious if it's safe to flash and use TWRP while I am not rooted.

You can install recovery with no problem, root has nothing to do with it. however i think upon a reboot your recovery will be replaced with factory.

Interesting. I wonder why/how the system would flash back to stock recovery if I've pushed the TWRP recovery image over the factory image?

I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app

otariq said:
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Without root would there be any functionality within TWRP that I shouldn't touch? Or does recovery functionality have no dependency on root?

What is there you wanna do? I just replaced stock with twrp so I can just flash the su zip when its out because I don't always have access to a PC. Also, Franco released his initial 4.3 kernel which I'm thinking about flashing.
When rebooting from twrp it'll ask if you wanna flash the su.apk because you don't have root I chose no because it wouldn't do anything for us right now without the binaries
Sent from my Nexus 4 using xda app-developers app

Good point. As of right now I guess I don't have a huge need for it. I'll just leave everything as is until a proper SuperSU is released. At which point I'll install the latest TWRP and root.

Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.

skinniezinho said:
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
Click to expand...
Click to collapse
No idea. I use a Mac and flash back to stock via Fastboot. You should just learn to do that anyway so you have a better sense of exactly what is going on and if something fails you'll know exactly which step is failing in order to correct it. Relying on a toolkit is like never taking the training wheels off your bike.

[Q] Lose root and recovery on every boot. What gives?

I'm on stock 4.4.2. I can fastboot flash CWM and flash SuperSU in recovery. When I boot, SuperSU says there is no su binary. If I reboot into recovery, it's the stock recovery.
I tried CF-Auto-Root as well. That gave me root. Next reboot, I lost root, however (no su binary). Any ideas?
I'm thinking about restoring from a factory image and starting over, but I don't want to lose data.

sgp77 said:
I'm on stock 4.4.2. I can fastboot flash CWM and flash SuperSU in recovery. When I boot, SuperSU says there is no su binary. If I reboot into recovery, it's the stock recovery.
I tried CF-Auto-Root as well. That gave me root. Next reboot, I lost root, however (no su binary). Any ideas?
I'm thinking about restoring from a factory image and starting over, but I don't want to lose data.
Click to expand...
Click to collapse
Try twrp. Also It looks like you might just be booting recovery and not fishing it. Though that doesn't explain why you lose root. Wugfresh toolkit has something that makes recovery stick when you flash it. Try using that and maybe another recovery like twrp or philz touch( this is the one in using and it's solid and reliable)
Sent from my Nexus 5 using xda app-developers app

abdel12345 said:
Try twrp. Also It looks like you might just be booting recovery and not fishing it. Though that doesn't explain why you lose root. Wugfresh toolkit has something that makes recovery stick when you flash it. Try using that and maybe another recovery like twrp or philz touch( this is the one in using and it's solid and reliable)
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thanks. Not sure what you mean by fishing it, though
I flashed just the system.img from the 4.2.2, and now CWM sticks when I fastboot flash recovery. Flashing SuperSU is not working, however. SuperSU still tells me no su binary. I should only need to flash CWM-SuperSU-v0.98.zip in recovery, right?

sgp77 said:
Thanks. Not sure what you mean by fishing it, though
I flashed just the system.img from the 4.2.2, and now CWM sticks when I fastboot flash recovery. Flashing SuperSU is not working, however. SuperSU still tells me no su binary. I should only need to flash CWM-SuperSU-v0.98.zip in recovery, right?
Click to expand...
Click to collapse
Try downloading and flashing the latest SuperSU binary. http://download.chainfire.eu/supersu

sharksfan7 said:
Try downloading and flashing the latest SuperSU binary. http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
Yes, that's exactly what I've been doing. It flashes without errors, but when I open the app, SuperSU says no su binary.
Sent from my Nexus 5 using Tapatalk

sgp77 said:
Yes, that's exactly what I've been doing. It flashes without errors, but when I open the app, SuperSU says no su binary.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I meant flashing lol. And you said you were using .98 super su. Have you tried version 1.85?
Sent from my Nexus 5 using xda app-developers app

abdel12345 said:
I meant flashing lol. And you said you were using .98 super su. Have you tried version 1.85?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Ah ha! I feel stupid. If you Google "SuperSU download", the first link takes you directly to an old version. I'm sure this is my problem. Thanks guys
Sent from my Nexus 5 using Tapatalk

Getting my 6p tomorrow. Suggested first steps?

Been looking through the root guide and of course will be unlocking and rooting. Should I first unlock, flash TWRP, load stock. Set up stock with my accounts and settings. Reboot to TWRP. Make NAND back up. Then root and then flash a rom? I'm still confused about the library IMG file. Will I need to do anything with it assuming the phone I receive was manufactured within the last 2 months?
Any other tips/suggestions would be much appreciated.
Sent from my LG-D851 using XDA Free mobile app

If you plan on unlocking bootloader, do that first. Device has to be wiped clean when doing so.

update to the March MHC19I update before modifying the system partition. It'll save you the headache of doing it via fastboot and re-rooting.

sirdizzle415 said:
update to the March MHC19I update before modifying the system partition. It'll save you the headache of doing it via fastboot and re-rooting.
Click to expand...
Click to collapse
So unlock bootloader. Flash TWRP. Load stock. Update to latest update (can I do this via OTA?) Then NAND back up and flash ROM?
Sent from my LG-D851 using XDA Free mobile app

Don't forget to flash SuperSU
Sent from my Dope 6P using Tapatalk

Unlock Bootloader, Ota or flash by other means, then root and flash twrp
Sent from my Nexus 6P using Tapatalk

Starzboy77 said:
So unlock bootloader. Flash TWRP. Load stock. Update to latest update (can I do this via OTA?) Then NAND back up and flash ROM?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I'll give it a try. Comments from anyone?
Unlock bootloader then upgrade to latest FW by OTA (or vice versa?), then flash TWRP and nandroid. Now root.

Great. I hope the OTA will pop up as soon as possible or is there a way to manually search for updates through system settings? By the way, thank you everyone.
Sent from my LG-D851 using XDA Free mobile app

Starzboy77 said:
So unlock bootloader. Flash TWRP. Load stock. Update to latest update (can I do this via OTA?) Then NAND back up and flash ROM?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
Unlock your bootloader, then take the OTA(s) to the latest build (MHC19I). You can't take an OTA with TWRP installed so don't flash that first. If for some reason the OTA doesn't appear you can just flash the factory images for the latest build in order to update. Once you're fully up to date you can flash TWRP and make a nandroid backup. Then just flash whatever ROM you want to use. Keep in mind that after flashing the ROM + gapps you also need to flash the appropriate vendor image to suit the build of the ROM you're flashing. You can flash it with fastboot, or use the "install image" option in bottom-right corner of the install menu in TWRP (TWRP can flash some images now).
I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

How to update Nexus 6P without losing root?

I haven't downloaded any security patches since I followed the main guide and rooted my phone.
I now have seen the news regarding the security update and how many critical flaws there are so I would like to update.
How can I do so without losing root?

Losing root shouldn't really be a concern. All you need to do is flash SuperSU again afterwards, which takes about a minute.

https://play.google.com/apps/testing/eu.chainfire.flash
This is an app by Chainfire called Flashfire. It works perfectly for what you want. I have used it myself on a few occasions. Let me know how it worked for you.
Sent from my Nexus 6P using XDA-Developers mobile app

+1 FlashFire

If you are impatient and don't want to wait for the OTA zip, just download the factory image and flash the following files using flashfire.
boot.img
system.img
vendor.img
Remember to disable security before you flash or you will have an issue with the vendor.img.

Heisenberg said:
Losing root shouldn't really be a concern. All you need to do is flash SuperSU again afterwards, which takes about a minute.
Click to expand...
Click to collapse
Hey, so I'm rooted with stock ROM and EX kernel but received the April update, any info why I got it?
I thought if you're rooted you weren't supposed to get an OTA update.
Sent from my Nexus 6P using Tapatalk

Doodsz said:
Hey, so I'm rooted with stock ROM and EX kernel but received the April update, any info why I got it?
I thought if you're rooted you weren't supposed to get an OTA update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You'll still receive the OTA, you just can't flash it via the traditional method.

I remember using the FlashFire method a month ago. The update worked and I didn't lose root, but I lost TWRP in the process.

ZabiGarma said:
I remember using the FlashFire method a month ago. The update worked and I didn't lose root, but I lost TWRP in the process.
Click to expand...
Click to collapse
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Sent from my Nexus 6P using XDA-Developers mobile app

dratsablive said:
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Click to expand...
Click to collapse
I couldn't flash it with FlashFire. I had to reinstall it from PC, which ended up with TWRP asking for a password, meaning I had to end up wiping the phone, which was worse than doing the regular OTA update.

ZabiGarma said:
I couldn't flash it with FlashFire. I had to reinstall it from PC, which ended up with TWRP asking for a password, meaning I had to end up wiping the phone, which was worse than doing the regular OTA update.
Click to expand...
Click to collapse
The new version of twrp 3.0.2.0 has been fixed. At least for me it worked.

Nice, I haven't installed the latest TWRP. I'll give it a try.
What I don't recall, though, is if last time I lost the applications I installed by flashing them with TWRP (like viper4android) or which rely on root.

I always remove security before flashing updates. Only issue is setting up the Imprint and adding cards back to Android Pay.

dave2metz said:
https://play.google.com/apps/testing/eu.chainfire.flash
This is an app by Chainfire called Flashfire. It works perfectly for what you want. I have used it myself on a few occasions. Let me know how it worked for you.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Is FlashFire no longer available?

dratsablive said:
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
If you use FlashFire just deselect recovery from the list when you load the latest update.
Sent from my Nexus 6P using XDA-Developers mobile app

Flash stock recovery and then ADB sideload the update. Links can be found in general. Then when it's done reflash twrp and SuperSU. Pretty easy. I've done it.

Installing OTA 7.1.2 whilst having TWRP installed caused soft brick.

I have just installed went to install the new OTA onto my angler, which was done through TWRP, except it seems to have either corrupted or erased my system partition, because now I just get the "No Command" on boot. TWRP still works and my files are intact, should I just flash a stock 7.1.1 image from Google? (7.1.2 is not yet provided outside OTA for angler it seems)

fuj1n said:
I have just installed went to install the new OTA onto my angler, which was done through TWRP, except it seems to have either corrupted or erased my system partition, because now I just get the "No Command" on boot. TWRP still works and my files are intact, should I just flash a stock 7.1.1 image from Google? (7.1.2 is not yet provided outside OTA for angler it seems)
Click to expand...
Click to collapse
I would download the 7.1.1 stock like you said and then flash boot, system, vendor, and Recovery. You have to be completely stuck before you install any OTAs. This should leave your data intact but I would make sure you have a backup somewhere before you begin
Sent from my Nexus 6P using Tapatalk

funnel71 said:
I would download the 7.1.1 stock like you said and then flash boot, system, vendor, and Recovery. You have to be completely stuck before you install any OTAs. This should leave your data intact but I would make sure you have a backup somewhere before you begin
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thank you, I downloaded the stock image, deleted userdata.img from the zip and used fastboot update <image>, that worked like a charm and all my data was left intact. Will update when Google decides they want to let me install the OTA again.

fuj1n said:
Thank you, I downloaded the stock image, deleted userdata.img from the zip and used fastboot update <image>, that worked like a charm and all my data was left intact. Will update when Google decides they want to let me install the OTA again.
Click to expand...
Click to collapse
If you still have a copy of the OTA you could install that using ADB sideload from stock recovery not TWRP. But as you say a safer route might be to just wait for the OTA to appear within your stock installation. Completely up to you
Sent from my Nexus 6P using Tapatalk

Related to this issue: I have TWRP, root and the Pixel package flashed to my 7.1.1 installation. I got the beta notification update this morning.
How would I proceed with flashing the update?
Flash stock recovery and system and download the OTA then or something else?

Puck24 said:
Related to this issue: I have TWRP, root and the Pixel package flashed to my 7.1.1 installation. I got the beta notification update this morning.
How would I proceed with flashing the update?
Flash stock recovery and system and download the OTA then or something else?
Click to expand...
Click to collapse
My recommendation is to flash boot, system, recovery, and xender. That should leave your data intact and put your to complete stock. I cannot advise on beta programs because I have never done it and I don't wish to just for the simple fact that it is beta. But if you are brave it sounds like you have the right idea.
Sent from my Nexus 6P using Tapatalk

I was able to flash on rooted 6P by flashing stock recovery. Took a long time at boot animation, and also security is back to January level.

Did you have the Pixel modifications?

Puck24 said:
Did you have the Pixel modifications?
Click to expand...
Click to collapse
I did before I applied the update, I had to modify build.prop afterwards to get the Assistant back. Haven't applied the pixel mod since it hasn't been updated for the 7.1.2 release.

How can I remove the OTA notification? I don't want to update but notification is annoying.

thegios said:
How can I remove the OTA notification? I don't want to update but notification is annoying.
Click to expand...
Click to collapse
If you are rooted you can freeze the update notification process.
Sent from my Pixel XL using XDA-Developers Legacy app

thegios said:
How can I remove the OTA notification? I don't want to update but notification is annoying.
Click to expand...
Click to collapse
Just slide the notification just a little too the side and hit block all notifications for it it go into developer settings and turn off auto updates
Sent from my Nexus 6P using Tapatalk

dratsablive said:
I did before I applied the update, I had to modify build.prop afterwards to get the Assistant back. Haven't applied the pixel mod since it hasn't been updated for the 7.1.2 release.
Click to expand...
Click to collapse
Thx for the info. I'll hold off for now, since i like the Pixel nav keys, tinted navbar and boot animation

Well you can also apply the boot animation. Works for me.
Sent from my Pixel XL using XDA-Developers Legacy app

just flash the stock recovery that matches your build number and you all be fine like me .

Is there a way to do that without a PC? I would like to flash stock recovery for 7.1.1.

RockZors said:
Is there a way to do that without a PC? I would like to flash stock recovery for 7.1.1.
Click to expand...
Click to collapse
The only way you can do that is if your phone is rooted and you flash it with something like Flashify.
Sent from my Nexus 6P using Tapatalk