yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] Prattham:
So when i flash twrp from the boot loader I should reboot to twrp without booting into system and flash super su right?

Lol really got messed up

Cheers ?

I really appreciate your help
[Nexus 6P General] MoistPicklez:
I followed your guide erased cache, and formatted userdata, then used the flash-all.bat, it showed on the terminal everything was flashed correctly. I restored my phone back to MMB29P.

---------- Post added at 07:58 PM ---------- Previous post was at 07:57 PM ----------

Yes sir. You got this.
[Nexus 6P General] Prattham:
So if i dont want to flash any custom rom and wanna be on shock root am i good to go?

I know I'm really troubling you alot

But i really love you so much :sly:
[Nexus 6P General] MoistPicklez:
LMAO no need for love bud, we can be friends though. And yes you are good to go.
[Nexus 6P General] Heisenberg:
Restored from what? I'm not sure I'm following what you did exactly. You did this before or after having app issues? If your app data was still present after wiping and flashing the ROM, you failed to wipe properly.
[Nexus 6P General] MoistPicklez:
Beforehand, I was previously on MMB29P VRToxin ROM, then decided to restore my phone back to MMB29P Stock. I lasted an hour on Stock before flashing Pure NeXus, and then noticed the issues I mentioned. I suppose the flash-all.bat clearly doesn't wipe everything after all.. I did however run the erase cache, and format userdata before using the flash-all.bat file so I thought perhaps everything worked just fine.
[Nexus 6P General] Heisenberg:
Ok, right before flashing Pure Nexus what did you wipe though?
[Nexus 6P General] MoistPicklez:
Data, System, Cache, Dalvik
[Nexus 6P General] Heisenberg:
I can't explain what happened then, if you wiped those your app data shouldn't have been retained.
[Nexus 6P General] MoistPicklez:
Odd because most apps I had to sign into fresh, but Imgur had me signed in already, and Shuttle+ (My music player) had my previous theme applied.. Thanks anyways man, I'll keep trying to figure this out.
[Nexus 6P General] kidbudi:
Great thank you very much. Just one more question. I flashed the systemless root and as far as I know everything worked out but I am trying to use android pay and it wont work.

I read other places i need to delete /su/xbin_bind directory but I cant find that, I don't even have an /su/ folder on my device. Is this a sign that something went wrong?
[Nexus 6P General] Heisenberg:
What version of SuperSU did you flash?
[Nexus 6P General] kidbudi:
I flashed 2.67
[Nexus 6P General] Heisenberg:
I've seen folks having issues with 2.66+, I believe 2.61 should be fine though.
[Nexus 6P General] kidbudi:
Let me check that out and I'll report back
[Nexus 6P General] kidbudi:
It worked! Thank you again :D
[Nexus 6P General] Heisenberg:
Excellent, you're most welcome.
[Nexus 6P General] JoKe_42:
As already covered 200 times in this thread... There is no modified boot.img for this version. You can use the systemless SuperSU and it will modify the boot.img for you. If you want a default system root then apply:

echo SYSTEMLESS=false>>/data/.supersu
echo BINDSYSTEMXBIN=true>>/data/.supersu

in a terminal in TWRP and before flashing the SuperSu.zip.

( or check 6. in the first post of this thread)

Regards,
[Nexus 6P General] adrman:
Actually, the commands you've quoted, will force a systemless root installation and prevent the creation of xbin_bind, enabling android pay.
[Nexus 6P General] JoKe_42:
Thanks, was tired and fixed it.

Regards,
[Nexus 6P General] TechMillz93:
Did u happen to get android pay to work?
[Nexus 6P General] E_Rock:
I did step 10, to upgrade stock ROM without it wiping my data but it wiped it whole phone. I followed the instructions to the T.
[Nexus 6P General] NPOA556:
But you skipped the step that says "fastboot format userdata" right? If you aren't reading the text in between the command lines carefully, you won't notice that this particular command is what you would enter if you DO want to wipe data. That's my only idea as to what might have happened to cause it.
[Nexus 6P General] E_Rock:
That's where I goofed.... thanks lol
[Nexus 6P General] Zewei lin:
Gewtting trouble when test for fastboot

Hi, thank you for your guide and now I am trying to follow your step by step to unlock my bootloader. However, when I tried to test my fastboot, I typed in fastboot devices, and it replied my nothing but a new line I have successfully installed those four parts of tools on SDK manager, and boot into bootloader mode and connected my device, but why it showed nothing? Plz help me out....:(:(
[Nexus 6P General] Heisenberg:
Have you tried rebooting your PC since installing the drivers? Have you confirmed that the drivers are actually installed?
[Nexus 6P General] Zewei lin:
Hi thank you for your help, actually I have successfully installed Chroma, actually I have tried to reboot my PC but din't work, and I tried NRT root kit, and it can download google USB drives, and finally it work, but I don't know why the drivers that I installed through SDK manager didn't work····
[Nexus 6P General] kristiangmez:
Hi to everyone ! I can't restore a backup from the TRWP revovery as it says something about only read mode. I m on the latest 6.0.1 and systemless rooted, I also have xposed. I dont really care about android pay as in Spain doesn't exist xD Someone knows if is there a way to restoring backups from Twrp ? Thanks in advance ! :)
[Nexus 6P General] Shaftamle:
When twrp boots up you should see an option to write to system or keep read only. To restore a backup you have to select modify/write system.

Sent from my Nexus 6P

---------- Post added at 07:34 PM ---------- Previous post was at 07:21 PM ----------

I was reading back trying to find the answer to an issue I'm having with Super SU. It says the binary need to be updated. I click OK and it fails every time. I have super su 2.66, I'm wondering if this is one of the issues that you were saying people seem to be having. If so, would downgrading help fix this? Thanks

Sent from my Nexus 6P
[Nexus 6P General] stm8:
I unlocked the bootloader, installed TWRP and rooted (systemless) using your guide. THANK YOU for making the instructions very clear and concise!

When the January security update came out, I used the steps in Section 10 to apply the update. I did nothing else to the system after that.

I am now going to sell my 6P to someone, and I want to return it to the way it was out of the box, locked bootloader and all. If I am understanding correctly, all I need to do is wipe data and lock the bootloader? Are there any precautions before re-locking the BL?

Thanks again for making this guide as clear and concise as you have!
[Nexus 6P General] Mesmurized:
Post # 2, Section 11 covers a complete return stock :)
[Nexus 6P General] stm8:
Yes, but that uses TWRP, which is no longer installed. Section 10 looks identical to section 11, except for wiping data. I really don't want to brick this thing right before I sell it.
[Nexus 6P General] Mesmurized:
No TWRP is required. It's all fastboot commands.
[Nexus 6P General] stm8:
The first step is to boot into TWRP.
[Nexus 6P General] Mesmurized:
Not sure what you're reading, but the first step

is from the phone settings.
[Nexus 6P General] stm8:
Whoops. My bad. I was looking in the wrong place. :confused:

The steps in section 10 look identical to section 11 except for wiping data at the beginning. Can't I just wipe data AFTER following the steps in Sec 10, the lock the BL?
[Nexus 6P General] Mesmurized:
Maybe, but I suggest following the guide 'to the letter'. It's been tested and tested again.
[Nexus 6P General] stm8:
Thanks. It just seemed redundant. But better safe than sorry! Thanks for taking the time to answer my question.
[Nexus 6P General] dirtyreturn:
adb/fastboot devices

I am having a bit of difficulty here with being able to access my device while in fastboot and I am not sure what's going on. Upon typing adb devices my 6p is recognized. Though, after typing fastboot devices and hitting enter all I get is another command line. I did a quick search and did not find an answer. Any help would be appreciated. I am reinstalling the drivers. Thanks.
[Nexus 6P General] ridobe:
You need to be in the bootloader. Type "adb reboot bootloader" then your fastboot commands will work.
[Nexus 6P General] mds2004:
I just received my phone today and have the same issue.

---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------

I am having the same issue and I am definitely am in the bootloader.
[Nexus 6P General] Nos_20:
I just got my phone today too. I had the same problems.

It is driver related on your PC. I opened the manage devices on my laptop, found the device android.

Then I went to install driver, I navigated to where I installed the google USB driver from the SDK install. Installed the driver and the laptop recognised the phone from the bootloader.

#whiteuimustdie
[Nexus 6P General] mds2004:
That was it. Thanks.
[Nexus 6P General] sgtduckyboy:
I took my time, reread several times, it presents some choices and steps unlike any other i have encountered in rooting HTC and samsung devices. but so far, works great after making decisions and following the steps for those.

Great job, great write up. not sure why so many other posts are written so poorly and take for granted that everyone knows what they are talking about!:good:
[Nexus 6P General] kevindejarnette:
Fastboot Problem

My device is recognized as a FASTBOOT DEVICE, but when I enter, "fastboot flashing unlock", all I get is a list of commands. I can't figure out why. Any suggestions?
[Nexus 6P General] sgtduckyboy:
my 6P ran great after root, following the directions. went the systemless route but not sure if i was supposed to, but seems to be the way i should have went. but once i put Xposed on it, its just lagging bad about 30-50% of the time and takes 3 times longer to boot.

any ideas? should i be on a deodexed rom to use Xposed? should i be decrypted for Xposed?

thanks in advance for any ideas, suggestions or assistance.

---------- Post added at 06:28 PM ---------- Previous post was at 06:26 PM ----------

Kristian,

does your run fine on Xposed? once i put Xposed on mine, its lagging about 30-50% of the time.. i thought about flashing it again.

any ideas?
[Nexus 6P General] kristiangmez:
I also got strange behaviour with Xposed, battery drained faster and the phone got warmer than it normally was, I m not sure if it was a module that produced the issue or Xposed itself, anyway I uninstalled Xposed and now everything s back to normal again.
[Nexus 6P General] Heisenberg:
Did you take the time to read the FAQ before posting this?
[Nexus 6P General] Californio:
Stuck at Step 2 (TWRP Recovery Reboot)

I tried searching, but this thread is like a billion pages long, so I figured I'd just post instead. It's not in the FAQs, so I figured this problem is probably not common if anyone has posted it at all.

In step 2 of this process, selecting "Reboot Recovery" brings me back to the bootloader. I also tried

adb reboot recovery

, but upon reboot it simply says "No Command".

Things I have definitely done.

Android SDK, Java, and every package on my system is fully up-to-date. I run Arch, and did a full system upgrade immediately prior to starting this guide.

The developer options (OEM unlock and USB debugging) were set both before unlocking and before attempting to flash.

adb devices

and

fastboot devices

(when in bootloader) both work, listing my device.

fastboot flashing unlock

is successful. I initially went through the system prompts to set up the device, but once I ran into this problem I also tried factory resetting my device. Furthermore, running

fastboot flashing unlock

again says it's already unlocked, as does the bootloader screen.

fastboot flash recovery <filename>.img

works perfectly, albeit very fast (0.44s to send, 0.246s to write).

Not sure what to do at this point. If anyone has any pointers, they'd be greatly appreciated. Again, apologies if this has been posted before.
[Nexus 6P General] :
What does this mean for systemless? I have to connect to pc and flash twrp every time I want to access it to flash or make a backup????
[Nexus 6P General] WhiteReign:
Great work here!
[Nexus 6P General] drothenberger:
There are two ways to get TWRP to stick: allow TWRP to modify system or install SuperSU.

Systemless root works fine even if TWRP modifies system. But if TWRP has modified your system partition, you won't be able to take OTAs and AP may break now or in the future. So it's best to have TWRP leave system read-only and then root systemless unless you really don't care about those things.

Note that if you do this, you have to flash TWRP and SuperSU before you boot into Android the first time. If you just flash TWRP and then boot to Android, TWRP will be lost.
[Nexus 6P General] Roche173:
Okay, I have been messing with this for long enough. I am having some trouble restoring my phone to factory state. I am looking at step 2 through 4 on number 11. When I download the factory image for my device and unzip it I do not get the other files listed, I only get a single file with the name angler-mdbo8k ect. I have downloaded it twice and still only one file. Have I missed something or have I skipped a step or am I just a complete moron that needs to sit down and shut up.

Thanks for any help.
[Nexus 6P General] LONGMANi:
Hi. I have rooted Nexus 6P (systemless). Now I got OTA update, what I must to do? Seems like this is small patch update and full image for this not exists. If I install OTA, I will lose root?
[Nexus 6P General] :
Thanks for clearing this up. Definitely flash twrp and su before booting.

If I install twrp as system, what does that mean for systemless root and how it behaves? Will it give me better compatibility with apps? I don't use AP but use a lot of root apps that might break because of systemless.

Basically, is there anything I should do to twrp or su if I don't use ap or ota?
[Nexus 6P General] tbv2005:
You get a tar. Gz... file. Unzip with 7zip for example and you will get a ". Tar" file. Unzip this file once again with 7zip and you will get the files described in tutorial
[Nexus 6P General] drothenberger:
You don't really "install TWRP as system". You just control whether TWRP will modify /system to defeat the built-in Android behavior that restores the stock recovery every boot. Your decision about whether to allow TWRP to do this or not is unrelated to how you root.

These days you need to do systemless root if you're on the stock ROM. Some custom ROMs still have a system root. "systemless" root just means the installation is done in a fancy way that avoids modifying /system, instead installing it to /data and then making it magically appear in /su/bin. The systemless root installation will update the PATH (how apps fine the root binary), so most well-behaving apps will work fine that way. Some poorly written apps will look for su in /system/xbin. SuperSU 2.67 has a work-around for this that is enabled by default that also makes su appear in /system/xbin. This should prevent these poorly written apps from breaking.

This /system/xbin trick does break AP, but if you don't care about it and are using the stock ROM, you can just:

Install TWRP. It doesn't matter whether you have it keep /system read-only or not.

Boot immediately into TWRP and flash SuperSU 2.67.
[Nexus 6P General] :
You're so helpful you don't even know. Thanks again.
[Nexus 6P General] kidbudi:
Hey quick question again. How do I do an OTA update with systemless root? Also, I have elementalx kernel so does that mean I can't do the update?
[Nexus 6P General] treasureking:
With systemless root, if I want to modify /system/build.prop, shall I still remount /system as rw and replace the file? Am I changing /system?
[Nexus 6P General] drothenberger:
I haven't done this myself, but I believe that in order to take an OTA, you have to have unmodified system, boot, and recovery partitions. This means no system changes (build.prop, Xposed, system root), no custom kernel, and the stock recovery.

I've never tried to take the OTA because I've always felt it easier to just flash the update's files directly as per step 10 in this guide.

Yes, you would need to remount /system rw and change the file. Yes, this is changing /system. It will block you from taking an OTA (see above). It may break AP; I've seen conflicting reports about that.

The "systemless" in systemless root just means that the root method itself doesn't modify /system; it doesn't mean that you or other apps can't modify it.
[Nexus 6P General] syintiphic:
Clarification when to Swipe To Allow Modifications in TWRP

Hey All, I'm hoping to get some clarification on when to swipe and allow modifications in TWRP. Back in mid-December I followed this guide and I rooted my phone without issue. I used the systemless root method originally posted and didn't have any issues. Now I'm not sure if something has changed since modifying my device back in December and if the guide was restructured and additional instructions added. But recently I noticed a many people asking if they should swipe to allow modifications in TWRP or if keep read-only. From what I recall when I followed the guide I essentially did the following and TWRP has persisted without me having to reflash it.

Unlock Bootloader

Install A Custom Recovery (TWRP). When I booted into TWRP the first time I swiped to allow modifications.

Skipped step 3 in the guide since I installed a new version of TWRP

Made a Nandroid Backup

Backed up my EFS in TWRP

Installed Systemless Root (version 2.60)

Rebooted my device and did not allow TWRP to install SuperSU

After performing the above steps TWRP has persisted for me every time I reboot into recovery. I haven't had to reflash TWRP except when I updated to the latest factory image (6.0-->6.0.1). That was the only other time I had to reflash TWRP.

So my question is has something changed? I know the guide has been updated since I last went through the steps and I think now it specifies more detail and incorporates additional precautions for users. I guess I'm not sure how I'm able to have TWRP persist (not that I'm complaining :victory: ) following the above steps when it seems based on recent posts that I should have pressed the read-only button in TWRP in order for TWRP to persist, which in my case I didn't press.

Someone please enlighten me. Oh, in case some of you are wondering AP works everytime for me as well. I haven't had it break or any issues.

Cheers.
[Nexus 6P General] drothenberger:
Stock Android attempts to restore the recovery partition to stock recovery on every boot. TWRP will disable this for you if you allow it to modify system. SuperSU also disabled this, so you can keep custom recovery if you flash SuperSU before booting Android, even if you didn't allow TWRP to modify system.

I think the guide is wrong when it says you have to have TWRP keep system read-only to use systemless root.

For some phones, just mounting system as read-only will break some security checks, even if you don't actually modify anything in /system. It's possible AP will break in the future too if SafetyNet is modified to detect this. I believe this is why TWRP is giving you this option. I also think this is what the guide was getting at - I think it is using the term "systemless root" to really mean "keep system unmodified" in some places.

I hope that clarifies things a little.
[Nexus 6P General] Dr.DL:
I unlocked the device, flashed the recovery and checked it, it asked me to enter a password for decryption, after few trials , I was able to open it and create backup, but now the device fails to reboot into system, get stuck at android loading logo.

any ideas?
[Nexus 6P General] Dr.DL:
Solved. :D

thanx :cowboy:
[Nexus 6P General] SlimSnoopOS:
Please post how you resolved your issue, for anyone who may have a similar problem in the future.
[Nexus 6P General] Dr.DL:
well, I searched for *stuck* word in the post, I noticed that xda team had warned about flashing SU equipped with TWRP, then I remembered that I did accidentally flash that SU. (which by itself is quit simple, just flash the SU img and you are ready to go).

By that time,System was deleted by me, in a wait for downloading stock rom *which was very stupid behavior*.

So I downloaded stock google rom, flashed it, then repeated process of flashing recovery again without installing TWRP SU, which went quite well.

Then CM13 was installed :D .

So, don't install TWRP provided SU. It's not compatible, and if u did, download compatible SU and flash it through adb.
[Nexus 6P General] dalvarez0312:
Can someone explain to me the difference between traditional and systemless root? What benefits does one have over the other? Android pay has supposedly stopped working with all systemless root so does this mean it will still work with traditional root?

I ask this because I want to customize my UI as much as possible and install things like adaway, greenify, and be able to theme things up a bit. I want to do it without losing key features of android like android pay, is this possible?
[Nexus 6P General] force70:
Search function works last time i checked. .

But yes AP did work with systemless before and now it does not.

It never worked with traditional root.

That said systemless can still be useful on a device like say the note 5 where acquiring traditional root needs a modded kernel. Systemless will patch the stock kernel which can be beneficial .

All that said i still use 2.52....no need for systemless for me yet

Theres much more to it than that but as mentioned the search button is your friend.

That and this is not a Q&A thread either.:thumbup:

Sent from my Nexus 6P, Note 5, Note 4 or Nexus 6
[Nexus 6P General] Heisenberg:
The difference is traditional modifies your systemless partition, where systemless doesn't, or at least it didn't, I believe there latest versions do indeed modify the system partition. The main benefit of using an Android Pay compatible version of systemless SuperSU is obviously that you can still use Android Pay. Android Pay has never worked with traditional root, it does work with the 2.61 version of systemless SuperSU though.

In fairness, plenty of questions get asked in this thread, and get answered. I'm the OP and I've never once stated that I don't want questions in this thread, they're perfectly fine as long as they relate to the guide, which these questions do. Please remember that only moderators moderate other members.
[Nexus 6P General] dalvarez0312:
Thanks for the information! I read in a separate thread that Google patched android pay so that it doesn't work with any version of systemless. However if it still does work with 2.61 the I will go that route to enjoy the benefits of rooting. Thanks again.
[Nexus 6P General] force70:
I know your the OP, ive always had alot of respect for your contributions to the board actually.

However as that was a very basic question as opposed to a "how to" would asking here in this thread you created not be more appropriate?

http://xdaforums.com/showthread.php?p=62924109

Just trying to help remind people to follow the rules my friend..search 1st etc...I am not nor pretend to be a mod lol but as member its our basic responsibility to try and remind people to follow the rules (thus keeping threads cleaner) especially these days with the way xda is going.

The mods can't be everywhere.

But I digress... its your thread and i 100% respect how you want it run so going forward i will keep my yap shut here.

Sent from my Nexus 6P, Note 5, Note 4 or Nexus 6
[Nexus 6P General] brockkk:
Sorry to post another question here but I'm having a little trouble. I used this guide to unlock my bootloader and did systemless root with no issues, everything worked great. Problem is I use android pay on a daily basis and as we all know Google fixed android pay so it won't work with root. So I went into the superuser app and chose to uninstall root. The phone boots up fine but I get a message saying the phone is corrupt before boot. If there a way to get rid of this? The phone boots just fine, its just annoying. Lol.