yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] treIII:
Is there a way using fastboot or adb to install systemless root without installing twrp? I would like to have root but stay as sick as possible. I only want to make some changes to my build.prop. Also do I need to run the terminal emulator commands in order to make build.prop changes? Also after doing these steps if its possible and I don't have twrp installed can I still receive and install the monthly security updates like with a completely stock phone? Thanks to anyone who can truly answer these questions that really knows the answers. I know this is a lot but this phone is so good that I've not wanted to root it. I just want to change the headphone output in build.prop. I have SOME experience with adb, Fastboot but I am not a dev by any means. Again thanks
[Nexus 6P General] Heisenberg:
You can't have any modifications to system, boot, or recovery.

You can boot TWRP instead of installing it:

fastboot boot twrp.img

You can use a text editor to edit your built.prop, or use terminal commands. You won't be able to take any updates though because you will have modified your system partition.
[Nexus 6P General] treIII:
Has anyone been making any zips to flash with fastboot for the monthly security updates if possible. That sure seems like it would make root more fun again!!! And thanks Heisenberg for your dedication and threads to help us all

---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------

If I use a terminal to edit the build. Prop wouldn't I need to have root?
[Nexus 6P General] Heisenberg:
Double post
[Nexus 6P General] Heisenberg:
You'd need root regardless of which way you want to edit the build.prop. I'm not sure why we'd need zips when we can just flash the images.
[Nexus 6P General] treIII:
I meant .imgs got off track. So it seems to me I should just use systemless root and twrp to flash SU. Im not sure how to temporarily boot twrp. I'll have to find a reference for that. And when you say images what images are you speaking about other than the factory images when there's a security update? And thanks for your patience. I've been reading I just don't want to make a mistake. Things have certainly changed
[Nexus 6P General] Heisenberg:
I gave you the code to temporarily boot TWRP in one of my other replies. The security updates are contained in the factory images, so you just flash those.
[Nexus 6P General] Pain-N-Panic:
Can you explain how to do the manual update? I'm facing the same issue
[Nexus 6P General] subhjvlz:
Is there any dual boot app/patcher available?
[Nexus 6P General] Mesmurized:
Its covered thoroughly in post #1 :)
[Nexus 6P General] caniranges:
But the will be other ways of getting updates ... right?

lets say theres a 6.1.1? will thered be some way of flashing it?

thanks

This is honestly much, much more of a hassle than samsung & odin.... but im trying geek through it.

im on windows 10 and still struggling to get the adb and fastboot to work....

it somehow doesnt seem to on my pc
[Nexus 6P General] Pain-N-Panic:
So if I'm systemless rooted with no modifications to system partition I.e. xposed, will OTA updates work?
[Nexus 6P General] Mesmurized:
OTAs will not work if boot, recovery, or system are not stock.
[Nexus 6P General] Heisenberg:
You realise you're posting in a guide thread, right? :p

Not that I'm aware of.

I'm not sure I follow, why would there be? This is how you update, either by flashing the factory images or using the built in updater (can't have any modifications though). If you still have Samsung software and drivers on your PC it's very possibly interfering.

OTA updates only work if you have no modifications to your system, recovery, and boot partitions.
[Nexus 6P General] Pain-N-Panic:
Ok, I understand everything that I need to do now. Last question, the "security update" I'm being promoted to download and update to, is that included in the latest factory image? If not, is there a way to simply make the notification go away?
[Nexus 6P General] hello2ew:
Hi quick question guys, after I updated my Nexus 6P to MMB29P I keep getting prompter halfway through the boot process for my pin, and everytime I boot into TWRP I keep getting asked to enter my pin to decrypt partition. Is this part of the security updates for 29P, or is there something unusual about this?
[Nexus 6P General] JoKe_42:
This only means that your phone is encrypted and you need to enter the pin so that TWRP or the system can mount the /data partition.

Regards,
[Nexus 6P General] hello2ew:
If so, is there a way to get rid of this?
[Nexus 6P General] ^tyrant^:
Check the OP and look at section #10 to apply the update, then follow the instructions to reflash TWRP, and root and xposed is you use it.
[Nexus 6P General] Heisenberg:
The security update is in the latest factory images.
[Nexus 6P General] JoKe_42:
http://xdaforums.com/nexus-6p/help/how-decrypt-6p-t3271898

Regards,
[Nexus 6P General] srqrob:
Security updates

If you're like me, manipulating zips and flashing images is kind of a pain. I'd rather play with my phone than work on it. So I wondered if there is really the need to do some of these flashes and found the following link that details the security goals of the current (1/6) security update. I'm not a dev, but reading this changelog it looks like there are many vulnerability fixes that warrant the few minutes of zipping and flashing.

https://source.android.com/security/bulletin/2016-01-01.html

[MENTION=4153349]Heisenberg[/MENTION] did you consider that the flashing would go easier if users added the platform-tools folder to their system path? adb and fastboot would then run on a command line opened from the images location rather than from the platform-tools folder. You eliminate all of the folder typing on each flash command line. Easier for me to open the command prompt from the C:\Angler\Images folder and then run fastboot flash .\XXX.img An option anyway.
[Nexus 6P General] Mesmurized:
I put all img files in the platform-tools folder and flash from there :) No path needed.
[Nexus 6P General] ^tyrant^:
strangest thing... I just did the manual update like i did last month..

everything worked fine booted up after flashing all the new .imgs

used adb to reboot in bootloader to flash twrp that went fine, booted into twrp to flash SU,, i did not have the zip on my phone so i rebooted to put it on there..

used adb to reboot to recovery and i went to the android with red ! triangle..

rebooted back to bootloader, and reflashed twrp, and from bootloader told it to reboot to recovery it did. so i then flashed SU and rebooted.

some reason i had to flash the recovery twice, even tho i let the system boot after doing the main update.
[Nexus 6P General] NPOA556:
Same here.
[Nexus 6P General] Stranger_84:
I've had adb and fastboot in my system path/c: drive location since it started ... It's how I set it up years ago ... But to each there own we all love to tinker with our devices that's why we are here ;) ... But setting it up in the system path can be a bit difficult sometimes and will only confuse many trust me
[Nexus 6P General] AranelAlasse:
This tripped me up, too. When you booted back into your stock ROM, it reinstalled the original recovery.

[MENTION=4153349]Heisenberg[/MENTION], could you maybe add something to the guide to help us prevent the red triangle? It seems to be tripping a LOT of people up. Like...

Section 1 (unlock bootloader)

Section 1b: Boot to stock ROM and customize everything you want exactly how you want it to be before you make your stock ROM backups.

Section 1c: Download the SuperSU zip onto your phone before you flash twrp

Section 2 (twrp)

Section 2b: Either mount system as Read/Write OR do NOT boot to stock ROM because you'll lose twrp (but you can reflash it, right?)

Section 3 (decrypt)

Section 3b: If you kept your system Read Only, do NOT boot to stock ROM because you'll lose twrp (but you can reflash it, right?)

Section 4: make backup

Section 4b: If you kept your system Read Only, do NOT boot to stock ROM because you'll lose twrp (but you can reflash it, right?)

Section 5: make EFS backup

Section 5b: If you kept your system Read Only, do NOT boot to stock ROM because you'll lose twrp (but you can reflash it, right?)

Finally, root, etc...

Maybe that's overkill, but you get my gist.

Anyways, is it mounting system as read/write which keeps stock ROM from nuking twrp? or is it flashing SuperSU that keeps the stock ROM from nuking twrp? I can't figure out which... or is it either of them separately?
[Nexus 6P General] SlimSnoopOS:
Flashing SuperSU in TWRP will keep TWRP installed after reboots.
[Nexus 6P General] elsworth1983:
Thanks [MENTION=4153349]Heisenberg[/MENTION] for a great guide
[Nexus 6P General] Millz120:
Answered..
[Nexus 6P General] mbutandola:
That makes sense.

Envoyé de mon Nexus 6P en utilisant Tapatalk

---------- Post added at 11:51 PM ---------- Previous post was at 11:35 PM ----------

Rebooting into recovery after flashing twrp will keep it. But I agree that it trips a lot of people and think it could be added to the guide

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P General] srqrob:
Flashing images
[Nexus 6P General] fdaconta:
Lost Recovery

I messed up, I thought the boot loader was unlocked. The fastboot flashing unlock command wasn't recognized. I attempted to to flash twrp-2.8.7.2-angler.img, and recieved an error message in the terminal widow failed to flash boot loader locked. I thought ok no problem, now when I try to enter recovery from boot loader all I get is dead droid, red triangle with ! mark and no command message. No recovery is a bummer! Anyone have any Ideas?
[Nexus 6P General] Heisenberg:
Why don't you just unlock your bootloader so you can flash?
[Nexus 6P General] chris59264:
Thanks, please actualiser les links factory images page 1
[Nexus 6P General] Heisenberg:
Are you asking for links to the factory images? They're already there.
[Nexus 6P General] Millz120:
Will installing BetteryBatteryStats or Wakelock Detector as a system app break anything? I'm am on a systemless root with Android Pay working.
[Nexus 6P General] chris59264:
Sorry no , new boot images mmb29p, section root
[Nexus 6P General] SlimSnoopOS:
This would break Android Pay and also defeat the purpose of using systemless root. The recent BBS betas (2.2.0-betas) should work without installing to system.
[Nexus 6P General] fdaconta:
I would love to unlock the bootloader so that I can flash recovery and root phone. I have tried unsuccessfully to unlock bootloader several times. usb debugging enabled, oem unlock on in developer options, issue fastboot command at prompt /Android/Sdk/platform-tools $ fastboot flashing unlock and I recieve adb syntax error usage: fastboot [ <option> ] <command> and lists adb help menu. I have also tried fastboot oem unlock ... FAILED (remote: unknown command) finished. total time: 0.008s .

Any ideas on what to try next?
[Nexus 6P General] Heisenberg:
You're looking for the modified boot.img?

Don't bother with "fastboot oem unlock", it'll never work. If you're getting a syntax error your SDK and/or adb/fastboot package is most likely out of date.
[Nexus 6P General] @home:
Do we still get OTA updates with Systemless?

If so, do we have to re-root everytime we have installed on?
[Nexus 6P General] fdaconta:
I'm using Android Debug Bridge version 1.0.31 I think its the latest verion. The only thing I can come up with is th use fastboot to flash factory "angler" for Nexus 6P image 6.0.1 (MMB29P) found here https://developers.google.com/android/nexus/images#bullhead
[Nexus 6P General] ridobe:
I'm not at home and I may be mistaken, but I believe the latest version is 1.0.34.
[Nexus 6P General] fdaconta:
I just updated SDK on my windows machine showing version 1.0.32 , Im trying to update the linux machine now
[Nexus 6P General] hello2ew:
Hi guys, so recently I flashed the latest factory image MMB29P afresh, and was looking to flash Xposed v79 immediately after rooting my phone. So I flash TWRP, flashed SuperSu v2.66, rebooted to system and installed the Xposed Installer apk then flashed xposed-v79-sdk23-arm64.zip via TWRP. However after that, immediately after booting it up, all my apps started going into a meltdown, with both user and system apps crashing on a loop. I already had the Xposed Installer apk installed beforehand, and I tried enabling SU upon boot, but all my apps still continued crashing. Only after uninstalling Xposed then it went back to normal. Is there something wrong with what I am doing? Or is this new update screwing Xposed up? I didn't have this problem with MMB29M, does any MMB29P Nexus 6P users experience this issue?
[Nexus 6P General] Pain-N-Panic:
No. I had xposed installed on 29M with quite a few active mods. I flashed the latest image (29P), reflashed TWRP and SU. I did not reflash xposed installer, because it was already installed. So was the apk. After gaining root again all my mods came back to exactly the way they were. Did you follow step 10 in Heisenberg's guide? If you were smart and made a back up of 29M I would flash back to it. Follow the steps in his guide on step 10 to a T and do not reflash xposed installer or the apk as his method leaves all the data in tact.
[Nexus 6P General] OsistemX:
Please help me.

I write "fastboot devices" I can't see the serial number.

Sorry for me bad english..
[Nexus 6P General] wilflare:
just to make sure I don't destroy my phone.

to update to the latest 6.0.1 build with the Jan Security Update

Just follow instructions in 10. How To Update To A New Build Of The Stock ROM

and then flash TWRP and flash SuperSU

I'll be able to upgrade without losing my data right?
[Nexus 6P General] Badger50:
You won't lose any data as long as you don't format your user data partition.
[Nexus 6P General] Pain-N-Panic:
Correct. I was worried as well. Just make sure you follow the directions EXACTLY as Heisenberg laid out. Read them a few times before actually doing it and then go ahead with the process. You'll be fine.
[Nexus 6P General] ridobe:
Are you in fastboot? If not, you need "adb devices".
[Nexus 6P General] AranelAlasse:
You're still in adb mode. Use "adb devices/command/whatever" when your phone is booted up into your ROM. You need to reboot your phone into the bootloader before you can issue fastboot commands successfully.

You can either turn your phone off completely, and then hold the power and down volume buttons simultaneously until you see it starting to turn on. Then it should go to the bootloader. If you don't want to do it manually, then instead, when you're booted up into your ROM and "adb devices" shows your serial number, then you can use an adb command to get your phone to boot into the bootloader: "adb reboot bootloader". That should do the same thing as the manual key combination.

Give it a little time to boot into the bootloader, and then from your same command prompt on your computer, type "fastboot devices" see if it shows you your serial number. If it does, then you may begin issuing your fastboot commands. You will no longer be able to issue any adb commands if you're not booted into the ROM. You only have access through fastboot commands while you're booted into the bootloader.
[Nexus 6P General] OsistemX:
I resolve the problem my adb drivers is not correctly installed ^^
[Nexus 6P General] mehappyz:
I think that is correct.
[Nexus 6P General] Heisenberg:
Are you able to format the /data partition or won't it let you?
[Nexus 6P General] mehappyz:
No, it won't let me, same error. I think the issue is the boot.img isn't disabling encryption. It's still encrypted and I'm getting the device integrity verification.
[Nexus 6P General] Heisenberg:
Have you tried decrypting via the Settings menu?
[Nexus 6P General] mehappyz:
Under Settings > Security > Encryption it says Encrypt phone with Encrypted under that. I can tap it and nothing happens.
[Nexus 6P General] Heisenberg:
Ok, you can disable encryption via fastboot:

fastboot format userdata

Remember, this wipes all your data.
[Nexus 6P General] mehappyz:
Thanks! That did it! TWRP is working correctly.

Any reason why this happened?
[Nexus 6P General] Heisenberg:
Honestly, nope, not a clue, lol. Working for some, not working for others, and it's virtually impossible to diagnose the problem without being there physically. Glad we got you up and running though :good:
[Nexus 6P General] Kusanagi Fire:
I had a similar problem as the previous poster and wiping data in fastboot seemed to make TWRP work. However, once I booted up after making my backup, I encountered the dreaded Google process error. Tried to flash a different stock ROM, but none of them would boot beyond the Google screen (tried two different ROMs with and without SuperSU 2.52 Beta). Eventually, I ended up just reverting back to stock for now without a modified boot or TWRP. I'll try this again this weekend.
[Nexus 6P General] ridobe:
I just don't get it. I have the SDK fully up to date. Allow OEM unlocking checked in options. USB debugging on. I'm quite familiar with ADB and fastboot. But, when in fastboot, "fastboot flashing unlock" just gives me the list of commands. It really acts like the SDK isn't up to date but I know it is. So, I'm going to delete my current SDK that I've been updating for years and redownload. I must be missing something from the SDK. The only thing I see different from the OP is the linux USB drivers that aren't compatible. Any other ideas?
[Nexus 6P General] markwebb:
Ok, not a noobie: I unlocked bootloader, installed twrp and root and I can't make a back up. Says it can't mount data in twrp. Also, everytime I enter twrp i get the read partition warning all of the time.

My phone does say it is encrypted though I did flash that boot kernel.

What did I do wrong?
[Nexus 6P General] Heisenberg:
The kernel alone doesn't remove encryption. Did you format /data as stated in the guide?
[Nexus 6P General] markwebb:
Hmmm. Maybe I missed that step. So what do I do to correct it? reflash that kernel? Fortunately I have a new type c USB OTG so I did back up titanium, apps, etc.
[Nexus 6P General] Heisenberg:
You need to format the data partition in order to remove encryption. You can do this via the wipe menu in TWRP (just make sure you format, not wipe) or via fastboot:

fastboot format userdata

Obviously back up anything that needs backing up first.
[Nexus 6P General] airmark:
When I got the phone I unlocked the bootloader, but root was not available yet, so I proceeded configuring the phone etc. Also received the OTA update. If I install custom recovery and root now, will I be able to do it without wiping all my data?
[Nexus 6P General] Heisenberg:
If your only objective is to gain root then you should be able to use adb sideload to install the SuperSU zip. TWRP still won't be able to access the storage unless you format data afterwards though.
[Nexus 6P General] airmark:
Does that mean it's not possible to even boot into TWRP without flashing it?

Because if I could do that, I could at least do a nandroid backup to my pc, then wipe data, flash TWRP and restore that backup. I basically want to avoid reconfiguring anything.
[Nexus 6P General] just4747:
Np, thanks!
[Nexus 6P General] theRZA001:
For some reason when I type in adb devices, it comes up empty. I made sure to enable OEM unlock and USB debugging. How can I fix this?
[Nexus 6P General] Aridon:
Install the Universal USB drivers. You also might need to boot into android, connect the device to USB and change the type of USB connection to PTP. There will be a popup on your device that you can check to remember your computer connecting and allow. Do that after enabling USB debugging.

Then check and see if you can see the device via adb.
[Nexus 6P General] _m0r0n_:
Can i check?

I am satisfied with my nexus 6p stock rom and all I want is to root so I can use the apps that required root.

Will I still get OTA update if there is new update?

Which steps to follow? Is it must to flash factory img etc...?

Thanks.
[Nexus 6P General] asj0422:
Questions: 1. when making a backup in recovery, what's the difference between system image and system? Also, what's the vendor partition?

2. when i made a backup (per the guide) i noticed that the time on my backup was really messed up... it said it was from march 1970, which clearly isn't the case. could this be a symptom of other problems?

[MENTION=4153349]Heisenberg[/MENTION] thanks for a great guide. i've done this stuff before, but it's always nice to have a guide to follow just in case stuff doesn't go as planned, especially with the new boot verity stuff marshmallow brought us.
[Nexus 6P General] Heisenberg:
Please read the faq in the second post.
[Nexus 6P General] Heisenberg:
1. Not sure what system image is, you don't back it up though. Vendor image contains proprietary binaries, Layers information is stored there for example.

2. Not sure about this.
[Nexus 6P General] asj0422:
1. it says its size is over 3 gb, so does it perhaps contain any user data associated with the system? (though i guess that would all be stored in the "data" partition, right?) Just want to make sure that when i do a nandroid backup i can restore my phone to exactly how it was.

1b. another note on that, is it a problem if i do the efs backup and the regular backup all at once in the same backup?

i'm also having a problem unzipping the file that i downloaded from google's site. the extension is .tgz, any ideas what can i do to open it? that's the only thing stopping me from being able to update my phone right now, other than that (*knocks on wood*) I'm good.
[Nexus 6P General] Badger50:
Change the .tgz extension to .tar and then extract it. That should do the trick.
[Nexus 6P General] asj0422:
That doesn't work either...
[Nexus 6P General] Badger50:
What program are you using to extract the files. 7zip works well for me.
[Nexus 6P General] SlimSnoopOS:
I'm fairly certain your EFS backup should be done by itself. You would need to restore that if your IMEI were to be rewritten.
[Nexus 6P General] Heisenberg:
1. I really don't know.

1b. Do your EFS backup separately.

Use 7zip or winrar to extract the archives.
[Nexus 6P General] Shockz:
Doesn't matter, when you restore you can choose what partitions actually are restored.
[Nexus 6P General] Heisenberg:
This is true, but it's easier to manage an EFS backup on its own.
[Nexus 6P General] asj0422:
Thanks a ton for the help guys. I'm afk right now, but I'll try 7zip when I get back to my laptop.
[Nexus 6P General] SlimSnoopOS:
Ahh, didn't know that was possible. This is my first device where EFS can be backed up in TWRP. On my last device, the only way to backup EFS was using a developer's custom zip.
[Nexus 6P General] a1exus:
Settings -> About phone -> Build number shows me "MMB29M", yet via Factory Images for Nexus Phones - Android — Google Developers, I'm seeing two version for 6.0.1: MMB29M and MMB29P.

Do I need to go with same MMB29M оr MMB29P? Does it go by "Android security patch level" (December, January, etc)?
[Nexus 6P General] mobileman88:
You are on December release. Mmb29p is for January
[Nexus 6P General] @home:
Don't think I got a reply to my question yesterday so I'll try again....

Do we still get OTA updates with Systemless?

If so, do we have to re-root every time we have installed on?

Ta
[Nexus 6P General] elsworth1983:
#scrap#
[Nexus 6P General] @home:
I don't see the answer to my question there?
[Nexus 6P General] elsworth1983:
http://xdaforums.com/showthread.php?t=3288198
[Nexus 6P General] @home:
Thanks
[Nexus 6P General] a1exus:
uh huh, that's what I thought) I just wanted to make sure) thanks!

[MENTION=4153349]Heisenberg[/MENTION]: this is more semantics than anything else, but still:

mbp:angler-mmb29p alexus$ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.037s]
finished. total time: 0.037s
mbp:angler-mmb29p alexus$

perhaps changing that line to:

fastboot format cache

other than that, I think it went okay, so far anyways... "Android is upgrading..."/"Optimizing app X of X" is happening right now) next thing to boot into twrp and flash BETA-SuperSU-v2.66-20160103015024.zip)

Thanks again for your guide!