yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] MitNasty:
Help with Step #6

I've Completed step #10 Followed by step #2 with no problems. But then I try to do step #6 System-less root.

After completing step #6, thinking I've successfully installed SuperSU, upon reboot my phone has the error message "Your data is corrupted, and can not be trusted" followed by being stuck in the boot animation.

Is this order of operations okay? 10,2,6.

I also saw mentioned somewhere in this thread to boot directly into TWRP, Ive been doing #10 then I do #2 then I boot into the system, mainly to download SuperSU, then reboot into TWRP to install SuperSU. Is this where I am messing up? should I download SuperSU BEFORE flashing the recovery so then I can do directly into TWRP with out ever going to the system?

P.S. even though I've been stuck on this for over 2 days now, this is still one of the best Guides I've ever seen. I'm 99% sure this is a user error, so please don't be bashful to tell me what I am doing wrong.
[Nexus 6P General] Heisenberg:
Oh, I was unaware about Android Pay being patched so I'm probably wrong about 2.61 working with Android Pay.

The question relates directly to the guide (which root to use), so it's fine here. It actually isn't your responsibility to remind anyone to follow the rules, that's what I meant, sorry if that wasn't clear before. Reminding a member to search or to follow the rules is considered moderation, and actually isn't the responsibility of anyone except moderators, nor is it allowed by anyone except moderators.
[Nexus 6P General] Heisenberg:
There only way I can think of is by starting fresh with flashing the factory images.

Are you wiping userdata during the flash of the factory images? Is that why you're booting into Android to download it after flashing TWRP? It's probably worth trying to have it already downloaded so you can flash it immediately after installing TWRP.
[Nexus 6P General] MitNasty:
I've tried both ways, Im thinking at this point I need to flash the stock rom, while clearing user data(because I'm corrupt at this point in time). then I feel like i'm forced to boot into the system to pick up supersu, then REflash the stock rom, without clearing user data, I'll be attempting this next which is fine. Im just stuck at, if I dont format userdata my supersu is corrupted, if I do format userdata, I no longer have supersu, and need to boot into Android.

Edit: If I flash the rom clearing user data, can I then use fastboot commands to transfer supersu from my /platform-tools/ folder onto my phone to avoid having to boot into Android?
[Nexus 6P General] Heisenberg:
How about this?

1. Flash factory images and format userdata.

2. Boot into Android, download SuperSU.

3. Flash TWRP, boot directly into TWRP and flash SuperSU.
[Nexus 6P General] MitNasty:
Im confused here. Ive tried this method while booting into Android, and it seems not to work. What do you mean by BoutBoot?
[Nexus 6P General] Heisenberg:
That's a Swype typo. What doesn't work? You can't boot into Android after flashing the stock images?
[Nexus 6P General] MitNasty:
Everything goes fine up until I try to install supersu from twrp, thats when I can no longer boot into Android and I get the animation loop.

I've also just noticed that now my google drivers aren't working. In Android my phone doesnt appear as storage. And in TWRP I tried to run adb push supersu.zip from the main TWRP screen and I got a return of device "null" I can not seem to get my phone to mount as storage now, even after downloading latest drivers and Uninstalling/reinstalling them, device manager detects no errors. I tried transfering supersu from a differnt PC which seemed to work but after installing I again got put in the same animation loop.

Right now I have a clean rom, flashed recovery, and Im just trying to find a way to install supersu with out ever going into Android. Seems to be a PC problem at this point, and not a user error which makes me feel a little better about my self I guess. :rolleyes:
[Nexus 6P General] Heisenberg:
Which version of SuperSU are you flashing? There's no reason why you shouldn't be able to boot into Android directly after flashing the stock images, but before flashing TWRP. At that point you have a 100% stock setup.
[Nexus 6P General] MitNasty:
So your assuming that I am a complete idiot, and for unknown reasons, instead of following your link for supersu, I google searched supersu and download the first BETA version I saw like a giddy school girl, which happened to be a version from like over a month ago. Is that really what you think I did? Well your right.

I apologize to anyone who reads my posts for wasting their time.

Mr Heisenberg sir, you are a superhero with out a cape, a god among men. Seriously man, or lady, or child, your my new favorite person of 2016.
[Nexus 6P General] Heisenberg:
Lol. I had a feeling you might have been flashing the wrong version when you said it was boot looping after flashing. Not a waste of time at all though, it's never a waste of time if we get the phone working. I'm just a dude who happens to have a bit of experience, but I appreciate the sentiment.
[Nexus 6P General] Shaftamle:
I don't know from personal experience but according to this XDA article, Android pay still works using systemless root as long as you disable it through supersu first. Not to knock anybody at XDA but there are a few things in this article that do seem rather suspect, so I'm not positive how correct his facts are. Just thought I'd share with everybody

http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)

Sent from my Nexus 6P
[Nexus 6P General] Heisenberg:
The article seems legit to me, we always knew that AP would be patched to detect systemless root too, I guess the time has come. Doesn't affect me though, I already have a wallet, so I really have no use for Android Pay.
[Nexus 6P General] fenchai:
[MENTION=4153349]Heisenberg[/MENTION] Please help!

I dont know what happened but I restored a backup of a recent backup (RRemix Rom) But now It doesnt boot, I tried restoring all of my other backups and none of them work! What should I do?

TWRP recovery is working fine. just stuck on boot logo on all my backups...

edit: Realized this happened because I restored the vendor img too. reflashing that should fix it :(
[Nexus 6P General] littleprince86:
hello, i install any roms and root systemless, but i don't have permissions in writing.. help me :(
[Nexus 6P General] bose301s:
Did the newest security update break Android Pay with systemless root? Flashed it, then flashed root and everything like I have before but Android Pay gives teh unable to verify message now. Hopefully it's not broken.
[Nexus 6P General] adrman:
It wasn't the security update. Google patched SafetyNet last Friday.
[Nexus 6P General] bose301s:
So no Android Pay with Root again? Oh well, I never use Android Pay, just like having the option.
[Nexus 6P General] gnadenlos:
Thank you for your tutorial. Everything worked without problems, but I have some questions to better understand the process:

1. On which partition(s) is SuperSU (systemless) installed if I install the ZIP through TWRP? Will it modify the boot image immediately or during first boot?

2. What happens with SuperSU (systemless) during an update (step 10 of your guide)? Will it modify the new boot image automatically or is SuperSU (systemless) lost during updates and has it to be installed again?

3. Is the behavior in question 1/2 different if I use the traditional SuperSU (non systemless)?

4. On which partition(s) is the Xposed framework installed if I install the ZIP through TWRP?

5. Will Xposed framework survive an update or do I have to install it again?

6. Will Xposed modules still work after updating the system (and reinstalling the framework if necessary)? I guess so, because as far as I understand the concept, Xposed doesn't change the real files on the system partition and applies changes on the fly.

7. On which partition(s) is AdAway installed? I guess the app is on the user partition and the changes to the host-file are on the system partition. Is that right?

8. Will it fix the host files automatically after updating the system or do I have to manually re-enable AdAway after updating the system.

9. Is there a general behavior of apps with root permissions when updating the system or do I have to research the behavior for every app?
[Nexus 6P General] EarlZ:
How ca I flash just rhe security updates w/o data wipe?
[Nexus 6P General] JoKe_42:
Check the 2.nd post #10 in this thread...

Regards,
[Nexus 6P General] SlimSnoopOS:
Please explain. What are you having issues writing to? Which apps have this issue?

1) /su and the boot.img (kernel). Boot.img is modified during initial SuperSU flash.

2 & 3) Does not matter, SuperSU will be lost. You must reflash SuperSU whenever updating. More SuperSU info.

4) /system

5 & 6) If updating via fastboot, you must reinstall Xposed. It would be removed when updating system partition. Modules should not work until Xposed is active. More info about Xposed.

7) Correct.

8) You must manually update Adaway because the Hosts file would be written back to stock after an update.

This is a case by case thing, for example Adaway needs to be manually updated in the app whereas Titanium Backup or Light Flow would only need SuperSU to grant root. Just reflash SuperSU and you should be set depending on the type of root app you are using.
[Nexus 6P General] Heisenberg:
You didn't actually read the guide before asking this, did you.
[Nexus 6P General] mbutandola:
I updated to the latest firmware but ads are still blocked out

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P General] rohit25:
a question if i may... so i ran the "fastboot format userdata" and didnt read through that it would also decrypt my phone along with wiping everything in it... just thought that it would wipe everything as i wanted a clean start for the phone....

as such now my phone decrypted.. so i dont think there is any harm in having it as the same.... i'll get better transfer speeds if i am not wrong...

the other thing.. if i do plan to have it encryped.. i need to goto settings security and then encrypt... no other right?

thanks

Rohit
[Nexus 6P General] gruppe3942:
Hey guys, I am running into something odd. I have unlocked many phones (bootloaders) using this method and never had an issue. However, I am trying to unlock the bootloader of nexus 6p. I install the adb tool kit and installed the necessary packages. I open up the command promp and I perform adb devices and it fines the serial number of my device. It communicates just fine. I try adb reboot bootloader and it boots my phone into the bootloader. Here is where things get odd. Once it gets to the bootloader I can no longer communicate with the device. The device tells me to (Connect USB DATA CABLE--which it is connected) and it also says download mode: disable.

Am I missing something. I have enabled OEM unlocking and USB debugging.

Any ideas? Thanks guys!!!
[Nexus 6P General] adrman:
Bootloader uses fastboot. Try "fastboot devices".
[Nexus 6P General] Badger50:
What happens if you first put your phone into bootloader mode manually, then connect your cable, open up your command prompt, and type in....fastboot devices?? If it recognizes it, then your golden. If not, then usually a driver issue.
[Nexus 6P General] EarlZ:
Sorry my understanding for Step #10 is for flashing the full ROM and not just the feb specific patches. Sorry for asking.
[Nexus 6P General] Heisenberg:
The end result is the same, my guide instructs you to flash the factory images because it's the only way to update a rooted phone, and most of the audience here are rooted.
[Nexus 6P General] neverborn:
Bit of help?

Tried to restore my stock twrp backup, now im stuck at google screen. History:

1. Unlocked bl

2. Twrp

3. Nandroid backup system, boot, data, vendor

4. Backup efs

5. Installed supersu

Installed and ran with xposed for a few days, then uninstalled today.

10. Another nandroid with current setup

Finally, tried to restore the nandroid from #3, but i never get past the google screen now. When i restore from #10, it boots no problem though.

How do i get to my stock nandroid state?

Help!
[Nexus 6P General] a1exus:
Is MMB29Q build contains February update for 6p?
[Nexus 6P General] Badger50:
Affirmative. Just security stuff.
[Nexus 6P General] SlimSnoopOS:
Have your attempted to restore everything in your backup except vendor?
[Nexus 6P General] neverborn:
Yeah, I tried that just now but it still wouldn't go past the Google logo.
[Nexus 6P General] blacky305:
same problem

Im having the same problem. but im not able to enable OEM unlock because I dont have a rom
[Nexus 6P General] Heisenberg:
How did you end up in this situation? If you have no OS installed and your bootloader is locked (without the possibility of unlocking) there's really nothing you can do. Do you have TWRP installed of the stock recovery? What OS was installed on the phone?
[Nexus 6P General] SlimSnoopOS:
When you unlocked the bootloader then installed TWRP and made a backup, did you boot into the rom and setup everything before making that backup? Cuz if not, I do not believe you are restoring a bootable OS since the bootloader unlock wipes the device.

Aside from that, best I can suggest is to factory reset in TWRP and try restoring it again.

Edit: Initially quoted myself.
[Nexus 6P General] blacky305:
I still have TWRP installed...

---------- Post added at 04:47 AM ---------- Previous post was at 04:37 AM ----------

When trying to switch to the purenexus rom from chroma i accidently wiped internal storage somehow when i wiped cache/delvik after flashing the rom. now my pc wont recognize my device..

I was trying to switch from chroma rom to the purenexus rom doing a clean install. I know it was successful because i was able to install the rom... i wiped cache davik and it was stuck on the bootscreen. i went back into twrp and somehow wiped the internal storage

the device is LOCKED and NULL

so i cant flash any images... and when i try to UNLOCK i get "FAILED (remote: device is locked. Cannot flash images)

and when i reboot it says "Your Device is Corrupt. It can't be trusted and may not work properly."

Even though it is locked TWRP recovery is still accessible
[Nexus 6P General] SlimSnoopOS:
Oh! Sorry, I was helping the other guy who was having issues restoring his nandroid. I quoted myself by accident so I will edit my post. For you, you should be able to push the rom zip onto your phone while still in TWRP then flash. The "ADB Push romname.zip" command should work, using ADB of course. Then enable "OEM Unlocking" and leave that enabled forever.

Edit: You may need to go into "Mounts" and check Data before using ADB.

---------- Post added at 11:16 PM ---------- Previous post was at 10:59 PM ----------

Transfer speeds are the same, you may have better write speeds to the phone storage.

That is one way to encrypt. Any time you fastboot flash a new OTA AND the boot.img, you will be encrypted again once you boot into the rom. You will stay decrypted if you root or install a custom kernel that disables "forceencrypt" in the boot.img.
[Nexus 6P General] blacky305:
thanks slimsnoop... very much appreciated
[Nexus 6P General] neverborn:
You may have something there. In all the excitement I don't actually remember if I did set it up before making a backup.

In any case, the guy I'm selling it to says he's ok with the phone being rooted, so I guess that's that.

Many thanks for your input - I'll remember to do that (actually go in and complete set up before nandroid) next time!
[Nexus 6P General] M_Shaaban:
Would root still work if I flash the stock recovery after rooting (system less root)?
[Nexus 6P General] MitNasty:
Hello all, I am a beginner and I had a few questions. A few days ago I did my very first unlock/systemless root.

I haven't downloaded any apps or themes or layers or anything I simply have the stock ROM with Supersu installed to root it.

Today I got an OTA system update for the February 2016 patches. Do I install it?

Also in the future I'm planning on loading a custom ROM( most likely pure nexus project). How does this effect updates. Do I do the OTA or is there some sort of manual way to install them? Again I'm new to rooting and custom ROMS so I literally have no idea whats going on. Any reply's would be greatly appreciated. Thanks in advance
[Nexus 6P General] omametsnor:
You should manually flash the OTA's there is a complete guide at the second post of this thread, you can download the factory images for your google device @ https://developers.google.com/android/nexus/images
[Nexus 6P General] MitNasty:
Awesome thank you so much, Do I need to flash all the files (boot,vender,system,cache, radio) or just certain ones? Again thank you much.
[Nexus 6P General] omametsnor:
This is the correct format

fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img

you can skip the recovery one, you don't need the stock recovery to complete the upgrade. DONT ever flash the userdata img.
[Nexus 6P General] eminembdg:
Anyone else have issue running SDK manager exe on Windows 10? I try to run it and it immediately closes. I found something with a search about installing jre and then editing Android.bat to make it point to the java location and so I did that but SDK manager still won't run.

I have already and used with my nexus 5, minimal fastboot and adb but since the guide says explicitly to not use those , I wanted to do it the correct way and not use minimal.

Any help would be appreciated.

Thank you
[Nexus 6P General] MitNasty:
Awesome, a million thanks, that's kind of what I thought I should do. I just have one(two) more questions If you don't mind.

So after I flash all those things mentioned above, I need to reflash TWRP, and reinstall SuperSU, correct? And then re-install any custom roms/kernels that I may have been using. If this is true should I go ahead and install pure nexus rom now, or wait; I guess what I'm asking is .. When a new update is released , is it likely that pure nexus and other ROMs will also have an update of their own following the OTA? (I noticed they added a new version just yesterday, which I would assume is stable, so I'm kind of asking about in the future?)

Again thanks a million this community is incredibly helpful, reliable and quick to respond. :good:
[Nexus 6P General] omametsnor:
You didn't had to overwrite TWRP with the given stock recovery, but if you did you can re-flash TWRP.

SuperSU shouldn't be gone within this process, but if it did u can install the zip once again from twrp.

you won't be able to update OTA while being rooted on stock android, custom firmwares like cyanogenmod and such do allow OTA since they got a different system. it will neither be likely that we will ever be able to push updates throu OTA within android 6.0+, once you root your device your boot.img will become modified and will cause conflicts (bootloops) while overwriting it with the unmodified boot img from the OTA update.
[Nexus 6P General] a1exus:
[MENTION=4153349]Heisenberg[/MENTION] I visit thead, per "6. How To Root – Systemless" section, it says "Download the SuperSU for systemless root method (2.60+) to your phone.", and thread is closed. XDA suggests, I follow to another thread [WIP][2016.01.21] Android 6.0 Marshmallow [CLOSED] (which is also closed).

Would you mind please to confirm that it is safe to ignore thread being closed and it is safe to still proceed with your current directions. I'm getting around to update from Jan. to Feb. update)
[Nexus 6P General] SlimSnoopOS:
They are safe to use. Those threads are a central place to read about any changes to SuperSU, so therefore they are closed. Chainfire updates them whenever he has new info to post (i.e. the latest SuperSU apks) Any discussion is directed to beta or main release threads for SuperSU. SuperSU has its own forum on XDA and what you ask is intentional.
[Nexus 6P General] Heisenberg:
Looks like Chainfire has decided that it's no longer a work in progress and has integrated it into the main beta branch. Here's the link:

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

I'm going to edit the guide now.
[Nexus 6P General] a1exus:
thank you) ok, i'll go ahead with update now... offline &)
[Nexus 6P General] Heisenberg:
He actually states in his closing message that it's no longer a WIP:

It's closed because there's no longer a need for a separate thread, because it has been integrated into the main beta branch. That thread will not be updated anymore, so the main beta thread is the place to watch now.
[Nexus 6P General] SlimSnoopOS:
Ahh, I missed that. I knew those specifically were originally closed to keep things separate. Glad I'm in the know now!
[Nexus 6P General] Dr.DL:
well, I previously unlocked my 6P's bootloader and flashed TWRP+CM13

if I wanted to restore the device to factory status *with locked bootloader*

I should do as follow:

1-Formatting *system, data ,cache...etc* through TWRP advanced wipe.

2- Installing stock Google rom latest edition.

3.booting into system and checking that there's no boot loop or other issues and that the device is functional.

4.Locking the bootloader.

correct?
[Nexus 6P General] a1exus:
I'm not sure if this is the place to ask this question, but after I removed "/su/xbin_bind", "Android Pay" still isn't working for me(
[Nexus 6P General] Az Biker:
The word around is that Google patched the "systemless" root exploit that allowed AP... Now the only way to get AP is without root. There were reports that using SU 2.61??? was giving intermittent use of AP...
[Nexus 6P General] a1exus:
ahh crap... even if i disable superuser? i'm 2.67
[Nexus 6P General] Az Biker:
I never used AP, but those in the PN thread who did, say that you can unroot, use AP, reroot (sounds like too much work to be convenient), and some were saying that one of the SU2.6x was intermittently allowing AP to work... Sorry I can' be of more help than that. Common feeling is that users of AP will need to remain unrooted to use it. Google's doing security patches monthly, so they're on it :)
[Nexus 6P General] IlyaKol:
What I missing here?

I've installed ADK (using the other downloads method) to my C drive, I've enabled debugging and OEM unlock, adb devices works but fastboot devices does not. Device manager shows just "Android" when in bootloader and connect.

I've done this a million times for other phones and can't get this working. WTF.

EDIT: Evidently, I needed the Android Studio to get fastboot, etc.

This snippet in the OP has you download the .zip which does NOT contain these tools:
[Nexus 6P General] Heisenberg:
You don't need Android Studio to get fastboot working, the snippet in the OP contains everything you need to get fastboot working, hundreds of people can vouch for that. I'm not sure why it wasn't working for you, but fastboot has nothing to do with Android Studio, that was just a coincidence.
[Nexus 6P General] IlyaKol:
When I unzipped the .zip file downloaded per op....it does not contain a file called fastboot anywhere in it's entire structure. Android studio, when installed, did contain it. Not sure either.

Anyway, I got it sorted. Just got my 6P and it is now rooted...now to install everything. Thanks for the rest of the guide though, worked like a charm!
[Nexus 6P General] Heisenberg:
It isn't meant to contain a fastboot file, you use the SDK Manager as per the instructions to install the fastboot package.