yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] JW09I4:
That is not correct... the script does not format userdata as that step is commented out. I left it in for future use by yourself or another user, as 64GB Nexus 6 owners cannot flash the userdata partition in an update or reflash. In Windows command scripts, a double colon " :: " is used to comment something out, whether it be script options one does not wish the script to perform at that specific time or to keep a script organized with descriptions. I specifically stated in my prior post the user data partition was excluded in the script.

Flashing any ROM from a custom recovery, such as TWRP, does not wipe userdata unless told to do so, however, it is recommended to do so... This would be where a backup app like MyBackup Pro from Rerware comes in, which backs up both data such as call log, sms/mms, etc., as well as applications and application data. If one has a rooted device and does not have a backup app that backups up both regular data, as well as app data, they're playing with fire. TWRP also provides a per partition backup feature that should be utilized as well.
[Nexus 6  General] pcrussell50:
Pffft...

Now this quote below, is a decent, meaty, useful, DIRECT answer to a question asked, that does not rely on misleading inference, and forcing the user to read between the lines like your evasive, "read the last 10 posts" advice:

Right or wrong, it's a good, direct, and to the point answer. that explains the good and the bad about using cf-auto-root. and based on that, I'll not be using cf-auto-root for my M Nexus 6.

-Peter
[Nexus 6  General] NtG.M4v3r1ck:
[MENTION=7189066]JW09I4[/MENTION]

Thx again.

It was my fault, I didn't see the double colon. So it should like you wrote it ;)

Also I learned next thing about custom recovery and userdata. So CM becomes even more interstering to me. Thank you.

[MENTION=769204]pcrussell50[/MENTION]

So do you think to flash/install only SU with a custom recovery works and is the better solution?
[Nexus 6  General] pcrussell50:
I don't know. But if the guy I quoted is right, and I can't be sure he is or is not, it sounds more appealing to me than using the latest cf-auto-root.

I'm going to try it in a few days here when I get back from a trip. When I do things like that, I do clean installs, wiping all my data, which doesn't bother me. Ill report back what I get.

-Peter
[Nexus 6  General] najoor:
Hello,

I'm the "guy" you quoted. Let me give you a bit more info so you can decide better for yourself.

The page maintained by Chainfire, the author of CF auto root, is at https://autoroot.chainfire.eu and if you go there and scroll down you will find this line for Nexus 6 (as of today April 1 2016):

motorola Nexus 6 shamu shamu shamu msm8084 NPC56P N 14 359 367 Download c058f9cdc2b568d7dcf22c2caf5d3368 126 550

Which tells you clearly that the kernel build ID is NPC56P for Android version N. Then if you go ahead and download this zip file you will find a Windows bat file in there which does only 2 things: 1- it unlocks your bootloader (which erases ALL of your data if this is the first time you're unlocking the bootloader) 2- it flashes the above mentioned N kernel onto your phone.

So if you insist on using CF autoroot then you have to look for a certain older version of it that matches your version of Android exactly. We have been through 6 Android versions on this device before Android N, so good luck finding the CF autoroot whose build ID matches your Android version exactly.

The only disadvantage that I see in using SuperSU zip is that you need to go through an extra step of installing a custom recovery, but having a custom recovery is actually a very useful feature in its own merit so I'm not sure that is even a disadvantage. In both methods you need to unlock the bootloader anyway.
[Nexus 6  General] JW09I4:
If one has issues, as you say, "reading between the lines", and making logical inferences from some very blatant information, one probably shouldn't be rooting their device...

btw... whatever you quoted had nothing to do with the question you asked. Since you seem to be missing the obvious, every time a user like yourself refuses to read the last ten posts/last page in a thread, you consciously make it that much harder for other users who need help. Some believe in not holding the user accountable for their laziness, believing it's easier to just give them the answer when they haven't made the slightest effort to read, however by doing so, one causes an exponential lengthening of the thread with useless posts consisting of questions from users who can't be bothered to take 5 minutes and

read

, all the while ensuring every subsequent user visiting the thread has that much harder of a time trying to find relevant info about the thread subject.

This isn't rocket science, however what it is is disrespectful to every other user who is actually trying to help themselves. To demonstrate the ludicrousity of your lack of personal responsibility: it's extremely rare to receive a reply back on a forum in 5 min or less, usually taking ~30 - 60 min on the low side. If one really does need help, and it only takes ~5 min to read the last ten posts/last page of a thread, why exactly would one forgo taking that 5 min in lieu of waiting for a reply?

XDA doesn't make viewing scripts all that easy on the end user, so I always recommend to everyone to install Notepad++, as it allows you to select what scripting language the script was written in (cmd and bat scripts are coalesced under BATCH in Notepad++), which then colorizes the applicable code, including syntaxes. For example, this makes it easier to identify commented out lines since comments are given their own color (green). If you choose to go this route, I've attached a registry file which will replace Notepad with Notepad++ as the default editor.
[Nexus 6  General] pcrussell50:
Your years too late on that one, mate. I've been rooting and flashing (without script kiddie tools kits) using the command line on mac and linux boxes since 2012. before that, i was jailbreaking iphones since 2008.... and i still missed your cryptic inferences.... and i wasn't the only one, either. seems to be a recurring theme with you.

and talk about crapping up a thread. you could have answered my question with one sentence. i wasn't asking for a technique, (such as how to root.), i was asking for an opinion, (if the latest cf-auto-root for M, is as smooth and bug-free as the older one was, with L.) easy to answer, and plenty of folks would like to know the answer. not that i need your opinion. i thought i'd ask and you didn't want to answer. no biggie. I'll try both the cf-auto-root AND the systemless root and report back my impression of how each works. cheers, mate.

-peter
[Nexus 6  General] P.Kosunen:
You can do it without installing, just boot it with "fastboot boot twrp.img".
[Nexus 6  General] NtG.M4v3r1ck:
Thanks a lot guys for discussion and answers.

The main question is:

Will it wipe any data, if I root an encrypted device (updated from 5.1.1 to 6.0.1)?

a) with CF-Auto-Root?

b) another way (flash twrp + install su.zip, etc...)?
[Nexus 6  General] alryder:
If your bootloader is not unlocked then unlocking it will delete your data. If your bootloader is already unlocked then you shouldn't (and most likely won't) lose any data. As is always suggested when performing these types of operations you SHOULD have a current backup in case something goes wrong.
[Nexus 6  General] pcrussell50:
Or as yet another alternative, you can flash TWRP, and as long as you don't do the following steps (pasted from the TWRP page), TWRP will be replaced by the stock recovery at next boot.

From the TWRP 3.0/Shamu site:

-Peter
[Nexus 6  General] NtG.M4v3r1ck:
Hi Peter,

how was your trip? Do you have some news for me?
[Nexus 6  General] pcrussell50:
Good call. Thanks for reminding me. I did the systemless root as soon as I got home from that trip and it worked in an easy and bug-free way.

One thing through. When I added a line to the bottom of the build.prop to turn off the tethering eligibility check, then rebooted, my phone went into a soft brick/boot loop, stuck on the "Google" logo. So I reflashed back to stock, then rooted again. I have not tried to edit the build.prop again but I really want to get rid of the tethering eligibility check, so I will try again.

I am happy enough with systemless root that I probably won't do the cf-auto-root method on marshmallow unless I get bored and feel like playing around a bit. Which I sometimes do.

-Peter
[Nexus 6  General] JW09I4:
Please use the search functionality of the thread and you will find the reason why, as well as a fix
[Nexus 6  General] pcrussell50:
You mean the answer doesn't lie in your infamous, last ten posts? J/k of course, and I wasn't asking for the answers, mate. I was reporting my results. But thanks for the pointer, anyway. Anyhow I'm get to it as it's priority rises on my list.

-Peter
[Nexus 6  General] JW09I4:
You'll eventually search the thread or search google, as no one is going to tell you on this thread (unless they plan on searching the thread for you). What is extremely apparent from your replies is you're insecure with anyone trying to provide you help, or perhaps it's just when someone tells you to stop being lazy and have some personal responsibility.

BTW... if you were as knowledgeable as your hubris attempts to make others believe, you'd have known the reason why you're experiencing what you're experiencing, as it's quite simple.
[Nexus 6  General] pcrussell50:
Yes, I know I will. I always do. Where I got crossways with you, was when I read the last 25 posts instead of just the last 10, and you gave me a beatdown for it. Nice message to send to everyone else you're trying to help.

I'm not sure what your point is, but your desperation to prove whatever it is, is causing you to stitch together incohesive and conflicting statements.

-Peter
[Nexus 6  General] JW09I4:
I can understand your perspective to a degree, however what was said to you wasn't personal. Take a step back and look at it within the bigger context... you weren't the first, nor will you be the last, user to ask something that was spoken about only a couple of posts back. Does one, two, or three people doing this create an issue, not at all. It does become an issue however when threads are overrun by this, with an end result being it makes it that much more difficult for anyone to find an answer to a question one might have in the thread.

For every one person that does this, it increases the thread size by a minimum three posts, resulting in threads growing exponentially the more users refuse to read, asking the same questions over and over again, even though their questions have been answered numerous times in a thread. For example, by the time another thread on here had accumulated 218 posts, 118 of them were about the same thing being asked over and over again by users refusing to read the last page/last 10 posts. To see this run amuck, one only has to check out the OpenWRT forum thread for the WRT1900, which is a ridiculous 10,767 posts long due to the OpenWRT forums lacking thread search. Because of this, every couple of days the same questions are asked and answered repeatedly.

If everyone's goal on a forum is to make it easy for everyone to easily find help, or easily give help, isn't it contradictory to then make it that much harder for help to be found? My problem isn't giving someone the answer when they've made no effort to discover it themselves, my issue is individuals that do so make it that much harder for other users to find the help they need, which then becomes a never ending cycle because other users are then forced to ask about something discussed multiple times before, but which they can't find because of the same information being repeated over and over again; thus inadvertently adding to the problem, ensuring the cycle will never end.
[Nexus 6  General] najoor:
[MENTION=769204]pcrussell50[/MENTION] and [MENTION=7189066]JW09I4[/MENTION], I think you guys made your points sufficiently. It's best to drop this back and forth now and let the thread be focused on what it is intended for, i.e. CF auto root.
[Nexus 6  General] pcrussell50:
Back on topic...

JW, you mentioned you found a workaround to the problem of rooted M not tolerating edited files in /system

I found your post 181 where you posted your workaround, in which you deleted the YouTube folder from the /app subdirectory. You said you did it from the adb shell, but is there any reason not to delete the YouTube folder (or whatever one you choose), using a file manager with (root permissions of course) that's already on the phone?

-Peter
[Nexus 6  General] TonikJDK:
Depends on the file manager. Mounting System in read write mode can be difficult. I just boot into TWRP and tell it to mount system and then use twrp's file manager to delete. If you just delete a couple keyboards you will be fine for adaway and a few mods. I usually delete Korean and Japanese. Dont delete Latin, that is English.

Unless you are Korean or Japanese....then my plan is bad.
[Nexus 6  General] JW09I4:
If removing something from the System partition for the first time in order to free up space, you can't be booted into Android. I don't know the actual reason why, so if someone does, I'd be curious to learn why. I have a hunch it's due to the system partition being filled to capacity, as even if you mount the system partition r/w, it won't actually mount itself with write permissions until space has been free'd up.

It doesn't seem to matter whether one issues the remount command via a terminal with root permissions or via a root explorer app, the device will report the system partition is mounted r/w, but refuse to allow anything to be removed.

When I was running stock android, I would always boot directly into recovery after a firmware flash to remove a folder from system/app, pull the build.prop to add custom entries, then push it and some other files (hosts, ipsec and ssl certs, etc.), and finally boot into the system for OOBE.

Just an FYI, anything removed from the /system/app folder will not be auto installed if a factory reset is performed (the app can still be reinstalled from Google Play). I personally recommend removing a folder that is at least 10MB in size, as that should free up ~1%. I would also recommend utilizing the command df -h after removing whichever folder you choose in order to verify it's freed up at least 1% of available space.

Also, for any other users who haven't freed up space on the system partition, please do so prior to editing the build.prop. Not doing so will result in the build.prop being zeroed out upon saving any changes (this applies to any file on the system partition), which will result in the device not being able to boot.
[Nexus 6  General] pcrussell50:
I actually have Adaway already up and running without having to directly edit anything myself in the system folder. of course, adaway didn't work right away, but it gave "suggestions" for settings to change in adaway's preferences menu, which i did, and then it worked fine.

I'm going to try JW's suggestion to:

1) delete the youtube entry in system/app/youtube (i guess I'll do this from TWRP?)

2) add the line to the build.prop to disable tethering eligibility test, and then save

3) the i'll re-add youtube from the play store

-Peter
[Nexus 6  General] JW09I4:
You can do it from within TWRP or you can do it via adb while booted into recovery:

adb shell mount -o remount,rw /system
adb shell rm -Rf system/app/YouTube
adb shell settings put global tether_dun_required 0
adb shell echo "net.tethering.noprovisioning=true" >> /system/build.prop
adb shell reboot

One could also copy the actual commands (w/o "adb shell") into a script and simply run the script from recovery whenever one updates/flashes the firmware.

Script attached

If copying/pasting, ensure you add the end of line row below "reboot")

Remove .txt extension, leaving .sh, & change it's permissions to include execute (755 or +x)

Also, if you don't know about the MVPS hosts file, I'd recommend taking a look at the site. One could use the hosts file (/system/etc/hosts) over an app, resulting in lower system resources being utilized to block ads
[Nexus 6  General] pcrussell50:
Already done... Via twrp. I was away from my computer that had the adb and fastboot so that was out. Thanks for the script, but I usually do it long hand, plus i'm in the bsd/unix-like terminal that comes with osx. Deleted YouTube, edited build.prop saved rebooted and the tether check is gone. All is well. Thanks all.

And thanks for finding the workaround for editing the build.prop

-Peter
[Nexus 6  General] JW09I4:
If you don't pay for hotspot, don't forget to add the settings com edit, which disables entitlement
[Nexus 6  General] pcrussell50:
Did not know about that one. What does it do?

I don't pay for tethering, but I also hardly ever do it. That said, it works like a champ on the occasion that I do tether... Just with the eligibility check removed.

I don't imagine the relevant post is in this thread?

-Peter
[Nexus 6  General] JW09I4:
It disables entitlement.

In order to utilize a device created hotspot [w/o paying for a hotspot plan], two settings must be set:

The first is the build.prop edit which enables networking over USB

The second is the settings com edit to disable entitlement.

Entitlement causes the device to direct you to your carrier's web page when trying to access the internet, which will inform the user they don't have a hotspot plan and will ask if they want to add one to their data plan.

The com edit used to be accessible via the settings com using an sql editor program, like SQL Lite, however due to security hardening with SELinux, most, if not all, com files are no longer directly editable via SQL.

It's baffling why carriers even try to enforce this on a Linux OS, as root exploits exist for most phone models, enabling the user to root, turn entitlement off, then unroot if they choose. There used to be a valid reason for entitlement (think pre-android devices), as mobile web pages were smaller in size that desktop versions, which is no longer the case for most sites (especially if they've upgraded to HTML5).

I always recommend people disable it regardless if they actually get sent to the carriers webpage when utilizing it or not, as some customers on certain carriers who left entitlement enabled have been hit with massive data charges when the carrier was able to detect hotspot usage on non hotspot data plans. There's no way to track hotspot vs non-hotspot internet traffic, as the internet doesn't function that way, however I would assume a pattern of behavior was detected (for example, substantial traffic to xbox live servers would be a giant red flag).
[Nexus 6  General] pcrussell50:
hmmm...all i did was disable the tethering subscription check by adding a line to the build.prop and wifi tethering works like gangbusters... in fact, i'm on my desktop imac right now with the LAN/cat5 cable pulled, wifi tethering to my nexus6 and all seems to be working well.

before i edited the build.prop to disable the tethering eligibility check, when i tried to turn on wifi tethering with my att sim in, it would perform a check, and then tell me i needed to change my plan to one that allowed tethering (fat chance, i have grandfathered unlimited). now, after editing build.prop it just hooks right up and works.... and works well, too.

-peter
[Nexus 6  General] JW09I4:
What value are you referring to... Net.tethering? That's the value that enables networking over USB. The settings com value (the "settings put" command back a few posts) is what disables entitlement... Unless I have them backwards
[Nexus 6  General] pcrussell50:
Yes, this line added to the bottom of build.prop:

net.tethering.noprovisioning=true

I'm pretty sure it's the one that tells the phone not to check with the carrier for tethering eligibility, and just turns on tethering outright. In any event, that's how it behaves since I inserted that line into the build.prop. Before I did that, if I tried to turn on hotspsot, it would block it, then check with AT&T, and get back to me telling me tethering is not on my plan and to contact them to have it added.

-Peter
[Nexus 6  General] JW09I4:
After doing some research, both edits control tethering, however the settings com edit is the main entitlement check. It is carrier specific, as carriers determine whether they will require one or both to be set correctly for entitlement verification (TMobile for example utilizes only the settings com for entitlement verification, whereas Verizon uses both).
[Nexus 6  General] pcrussell50:
my phone is working and tethering great on att with the net.tethering edit to the build.prop. still for my own education, i'd like to learn and try the "settings com" edit, but for the life of me, i'm having no luck googling a useful answer as to how to do it. is it just an apn change in settings?

-Peter
[Nexus 6  General] JW09I4:
Prior to SELinux incorporation in Android 5.0, the coms were directly editable via sql editors, like SQL Lite, however one now must use cli. For this specific setting, the command would be:

settings put global tether_dun_required 0

or via ADB

adb shell settings put global tether_dun_required 0
[Nexus 6  General] NtG.M4v3r1ck:
Hey guys,

last weekend I updated successfully my Nexus 6 from 5.1.1 to 6.0.1.

The way i did:

- make backups

- download the newest factory image/twrp and SuperSU 2.65

- get into fastboot mode

fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot-bootloader
fastboot boot twrp.img

- flash supersu.zip

- start device

And everthing seems to work fine. So I thank all of you for hints, solutions and discussions.
[Nexus 6  General] JW09I4:
please encapsulate your code within

brackets. Also, majority of your steps aren't relevant to rooting with CF Auto Root, only the last two, boot and supersu
[Nexus 6  General] DON2003:
does this still works for all stock Nougat on Nexus 6? thanks
[Nexus 6  General] spastico:
It works for me.

I just rooted Nexus 6 Nougat - Build # NBD90Z
[Nexus 6  General] alryder:
Out of curiosity, what version of SuperSU does this install?
[Nexus 6  General] spastico:
I'm not sure because I flashed a rom soon after.
[Nexus 6  General] cpufixrman:
Anyone have success with a Nexus 6 on N6F27C? I had this working before updating via sideloaded OTA, having forgotten I could have used FlashFire.... now I get an errror when trying.

downloading 'boot.img'...

FAILED (command write failed (No error))

finished. total time: 0.016s​
[Nexus 6  General] pcrussell50:
I'm on N6F27C. Working great. I flashed it instead of side loading because I was previously running a rooted custom ROM, so side loading wouldn't work. Anyhow, it seems to be working just right. Haven't discovered any bugs in the week or more I've been running it.

Maybe unlock the bootloader and try flashing? :shrugs:

-Peter
[Nexus 6  General] cpufixrman:
Already unlocked, I did that when I first rooted it. I'm trying to get root back after installing the OTA update. =/
[Nexus 6  General] pcrussell50:
if you're trying to root it, does that mean that you eventually got the OTA working right?

-peter
[Nexus 6  General] cpufixrman:
I wasn't the one with the OTA issue. I think that was another respondent. I've never had an issue installing the OTA, and had no issue initially OEM unlocking and rooting after a previous update. Just this latest N6F27C that I can't seem to get rooted. adb devices and adb fastboot both detect my phone, and I even tried a USB 2.0 port after reading somewhere that USB 3.0 might cause issues. I'm going to table this for now and take a look at it again over the weekend when I have time.
[Nexus 6  General] pcrussell50:
What root method are you using? I've been using a variant of SuperSU, called MagiskSU and works really nicely.

-Peter
[Nexus 6  General] cpufixrman:
Well, considering this is a Nexus 6 CF Auto Root thread... :confused:

I have been using it for a while without fail. I will try MagiskSU. Thanks for the suggestion.