yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] JW09I4:
If you're on 6.01, open up build.prop and verify if your change actually took, as it more than likely did not. The terminal command for settings will take, but in order for the build.prop edit to take, you have to delete ~10MB from the system partition to free up space. I'd recommend /system/app/YouTube via:

mount -o remount,rw /system
rm -Rf /system/app/YouTube

You can then reinstall YouTube from the Play Store

Verify free space via:

adb shell df -h

I suspect Google purposefully insured the system partition did not have free space as an extra layer of security, since you're unable to edit or save anything to the system partition unless you've flashed a third party recovery image (remounting rw while booted in Android won't work until after as well)
[Nexus 6  General] JW09I4:
I mentioned the build.prop because you can edit and appear to save it, however if re-opened, it would be unchanged (until space is freed on the system partition)

Have you tried running it as su?

adb shell
su
settings put global tether_dun_required 0

OR

su
mount -o remount,rw /system
settings put global tether_dun_required 0

If you're still unable to get it to take, especially within recovery, something else is going on with your device specifically.

Have you verified USB Debugging is enabled? (if attempting while booted to Android)
[Nexus 6  General] fasthair:
I agree completely that there must be something wrong with my system. I can see ADB and get to a SU prompt and run commands in ADB in TWRP but for it just won't stick. I'm done messing with this and just going to flash this back to stock and start over with the phone.

Again thanks for the effort! I'll be back on the other side.

EDIT: God do I feel dumb!!! I've done this before using post 96 but for the life of me I couldn't make it work this time. That's because I forgot the "." between the net tethering... geesh... SOB... /me hangs head in shame and walks away....
[Nexus 6  General] Falinor:
Has anyone gotten this to work on tmobile on 6.0.1
[Nexus 6  General] examan:
I tried to let the OTA security update go through and it gave me the dead droid about 75% of the way through. Is there a way to get the update to go through? I don't really feel like reflashing back to stock. I'm not rooted the only thing that isn't stock is the one line of code at the end of the build.prop to enable tethering.
[Nexus 6  General] joshhayden10:
starting today att brought back unlimited data for tv subscribers for a limited time great right? there will be a 22gb limit then you will get throttled, not so great.* you'll also have to forfeit your tethering. do we think we could find a way to maintain tethering while going to the new unlimited data plan?
[Nexus 6  General] gohamstergo:
download the factory image, extract it, fastboot flash just system.img, go into twrp and wipe cache/dalvik, reboot, reapply build.prob mod. if you dont know how to do any of that, you may need to research.

read this thread and apply the mod
[Nexus 6  General] aiiee:
I added the net.tethering line to build.prop, now the phone won't progress past the initial "Google" screen! Did I bork the phone? January security update, stock, rooted 6.01
[Nexus 6  General] JW09I4:
You may have to reflash the system partition, however I have a hunch if you boot into recovery and cat your build.prop, it may be zeroed out
[Nexus 6  General] aiiee:
Thanks. adb pull can't seem to find a /system/build.prop

There is a /system/build.prop.bak and adb pull says it's transferring it but I can't find it in platform-tools or anywhere on my pc. What am I doing wrong?

OK, trying to flash system.img to /system and we're back!!

Thanks!!

They shouldn't tell you to do things like this!! Don't edit your build.prop!!
[Nexus 6  General] Ellises:
If you can't find the /system/build.prop file, but a build.prop.bak (don't know what would create the backup file...) you might be able to do this in adb shell: cp /system/build.prop.bak /system/build.prop
[Nexus 6  General] aiiee:
root explorer created the .bak when I edited build.prop using it's editor. Maybe that was the mistake? Anyway, I'm back, and that was a little nerve wracking!
[Nexus 6  General] JW09I4:
Do the following in sequential order

adb shell mount -o remount,rw /system

adb shell rm -Rf /system/app/YouTube

adb shell cat /system/build.prop.bak

If the output isn't a zeroed out backup:

adb shell cp /system/build.prop.bak /system/build.prop

To pull a file, in a terminal, change the terminal directory to whatever folder your working in, then issue the pull command

---------- Post added at 19:24 ---------- Previous post was at 19:21 ----------

In order for anything to be saved/modified on the system partition, space must be made available. You can verify free space by running the command df

I recommend removing the /system/app/YouTube folder since its of sufficient size and can be reinstalled from the playstore
[Nexus 6  General] aiiee:
What I ended up doing was reflashing my /system, as you first suggested, and that allowed the system to boot up and function normally. I'm not sure why adb pull showed a file being transferred but not appearing on my pc . Isn't that was adb pull is supposed to do, transfer a file from the phone to the pc?

EDIT: to those who don't know, the platform-tools directory is apparently not user-writable ( at least on my pc ) which is why I could not save build.prop on my pc. Once I saved it to another dir I could write to, it wrote build.prop on my pc.

Thanks again btw :)

---------- Post added at 02:29 AM ---------- Previous post was at 02:26 AM ----------

The lack of space must be the culprit here, root explorer made the bak file and then oops, no more room, we'll just fail silently.....
[Nexus 6  General] JW09I4:
What folder where you pointed to in the command/powershell terminal, your current working directory of system32?

A push wouldn't have worked without freeing space, however a pull should always work provided your pulling to a directory you have write privileges to.

For example, shift + right clicking in a folder provides you the options to open a terminal in the folder you want to save the pulled file to; then issue the command:

adb pull /system/build.prop C:\Temp

Note the proper backward/forward slash must be used (forward for Android [*nix/bsd], backward for Windows).

---------- Post added at 19:39 ---------- Previous post was at 19:35 ----------

I have a hunch Google did that for security, as it prevents any modifications to files in the system partition. You must remove the YouTube folder (or another of sufficient size that's at least 10MB in size) within the /system/app directory while booted in recovery, as the system partition won't allow the deletion while Android is booted.
[Nexus 6  General] aiiee:
Well I did not specify a destination directory with my pull cmd. I was using a terminal window opened up in platform-tools under android-sdk. I didn't see any destination directory in the earlier instructions in this thread, hence I didn't think they were necessary. Obviously that's not correct :) And you are right about permissions I think. Only administrator can write to platform-tools for some reason, and I was not getting any error when the write failed, just a silent fail.
[Nexus 6  General] JW09I4:
I believe it's adb pull [source] [destination] however you can verify by issuing adb /? and scrolling to the Pull/Push section

I recommend adding the platform-tools path the windows system environment path, which allows you to open any command/powershell terminal and issue adb commands.

In a terminal, to specify the current folder, use a period and a backslash (if in windows) or a period and a forward slash (if in a *nix/bsd OS).

Windows: .\

linux/bsd: ./

---------- Post added at 19:57 ---------- Previous post was at 19:48 ----------

When a pull command is issued, it doesn't immediately create the file, as first the OS must recompile all the raw data it was sent, verify checksums (if applicable, not sure if adb does so), then export that raw data into human readable information in the form of a file. On our end, its seamless and almost instantaneous, especially if it's a small text file. Most likely all but the last step was completed, since adb was never told where to save [export] that information to, meaning its probably still in RAM
[Nexus 6  General] RickyBush_:
Im on three as well I use 60gb plus a month just on tethering I didn't have to change any setting my was already at tether_dun_required 0 but now I want to be on a note 5 rom the setting want let me change it from tether_dun_required 1 so I had to change back to old rom for now ?

WHAT SHOULD I DO! ??
[Nexus 6  General] JW09I4:
Did you mount /system as r/w? If not, it can be done via a file manager like root browser or via:

mount -o remount,rw /system

Have you verified if the system partition has any free space, as 6.01 was designed to fill the system partition to 100% capacity. To view space usage:

df

If capacity is at 100%, boot to a non-stock recovery, mount the /system partition r/w, and delete YouTube from the system partition (it can be reinstalled via the PlayStore):

adb shell mount -o rw /system

if the system partition is already mounted

adb shell mount -o remount,rw /system

adb shell rm -Rf /system/app/YouTube
[Nexus 6  General] mjmixer:
Tethering working!!

I've been having the same issue with editing build.prop and getting stuck at the Google logo after it would delete my entire build.prop. What I did and it seems to have worked was delete files from the /system/app newstand and books as others have been stating..went into root explorer and edited the build.prop so it would create a .bak file, then added the "net.tethering.noprovisioning=true" save..reboot and it worked. Hope this helps with 6.0.1 January update.

FYI. I used TiBu to remove the system apps
[Nexus 6  General] JW09I4:
It's due to the system partition being filled to 100% capacity by default, which results in an inability to save any new data to the system partition and zeroes out any file where an edit was attempted.

A quick FYI: when deleting apps from the /system/app directory, be aware these are the apps that are auto installed by default whenever a factory reset is performed, so don't delete any app from there you want available when a factory reset is performed.

Some have had issues attempting to delete items from the system partition while Android is booted. If any user does have an issue, boot into a custom recovery and issue these commands in the recovery terminal (or via a pc, by adding the following in front of the commands: adb shell)

mount -o rw /system

rm -Rf /system/app/[folder to delete]
[Nexus 6  General] discslinger:
This was the key for T-mobile/Sprint on 6.0.1

Success finally here too, thanks to performing the 2nd part in the terminal emulator on my phone, after this failed via adb.

Specifically:

Code: su

Code: adb shell settings put global tether_dun_required 0

Thanks!!!!
[Nexus 6  General] Falinor:
So I need root in order to do it via the terminal emulator and not through adb? If that is the case, hwat method of root did you use that is quickest and easier? Do you have to SU first before adb shell settings put global tether_dun_required 0 via terminal?
[Nexus 6  General] JW09I4:
In order to modify system files, including com settings, root is required. The only instance in which you may be able to modify system files, without being rooted at the time, would be if you had a custom recovery installed, as adb always runs as root within a custom recovery.

Either method can be used to modify the com setting, however you will need to ensure you have free space on the system partition in order for the write to occur. 6.0 was designed to fill the System partition to 100% capacity, and unless at least ~10MB is removed, you will be unable to save any changes, with some files being zeroed out upon trying to write to them. I personally recommend removing one of the non-critical system apps from the /system/app folder, such as /system/app/YouTube. The terminal command would be: rm -Rf /system/app/YouTube

Please be aware, any app removed from /system/app will not be included as an installed app upon a factory reset; One would need need to manually install YouTube from the PlayStore, for example.
[Nexus 6  General] discslinger:
Yep; you need root. I used Heisenberg's method to root, and looked at one video - links below:

http://xdaforums.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930

http://android.wonderhowto.com/how-...indows-mac-linux-the-foolproof-guide-0166128/

The second link is another tutorial with a video - which I think is good to see,

specifically the TWRP menu where you come to "Do not Install"

the terp version of SuperSU. It's easy to see why someone might screw this up - even if you have read not do to so.

Once you are rooted, SU is installed. So you can download terminal emulator for the final command:

Specifically:

Code: su

Code: adb shell settings put global tether_dun_required 0

Of course, this is after I pulled out and modified the build.prop via adb.

Good luck!
[Nexus 6  General] JW09I4:
If using a terminal emulator, adb shell isn't needed - adb shell, in this context, would only be required if issuing the commands from a PC
[Nexus 6  General] discslinger:
Hey JW09I4 - a quick question, which might be useful info for others too on this thread.

Would converting a system app like youtube via Titanium get the same result to free up space?

Speaking of converting and deleting certain apk's - does anyone know of a barebones list that exists for Marshmallow system apps to either disable or delete?

Thanks in advance.
[Nexus 6  General] Falinor:
how come issuing adb shell settings put global tether_dun_required 0 from pc doesnt work anymore?
[Nexus 6  General] JW09I4:
That's a good question and one I don't have an answer to. I would try it and the check the folder size of whichever app one moves (open a terminal and issue: busybox ls -lsah /system/app/<folder>

---------- Post added at 12:05 ---------- Previous post was at 11:55 ----------

You must first free up space on the system partition
[Nexus 6  General] vtmoon:
Success!

Success! At last on VZW with 6.0.1. My main issue was the not enough space to edit and my system becoming read only.

Thanks to JW09I4 for helping me figure out how to handle the space issue I was facing in 6.0.1, using his solution in #123. After that was done, I was able to use tabormeister solution in #96 to get my Hotspot back in action.

I haven't tested Android Pay yet, but I have never been able to get it to work yet even after removing xbin_bind, I can add cards and everything I just get nothing when I go to the store to try to get it to work, will see if any of this somehow change it but doubt it.
[Nexus 6  General] JW09I4:
I haven't had the time to research it yet, but if Android Pay isn't working when its been setup correctly, it may be blocked from working with rooted and/or with the bootloader unlocked. VZW's pay app, for instance, won't work on rooted devices.

If this is the case, unless you are hyper vigilant about your device's security (i.e. not utilizing any other app store but the play store, not side-loading apps unless you 100% trust the developer, utilize strong passwords that are different across logins, etc.), it would be unwise to try and get Android Pay to work on a rooted device if that's what the issue is. I'm not sure if Android Pay uses hardware encryption, as if it does, its not probable someone would be able to gain access to the protected spaces those keys reside in even if they had remote access to the device. (However the protection level hardware encryption provides depends on how its implemented, what security the processor provides, etc.)
[Nexus 6  General] vtmoon:
According to this article they finally blocked it anyways.

Android Pay no Longer Working with Systemless root
[Nexus 6  General] JW09I4:
Simply put, rooted devices should never be allowed to run applications that tokenize CC info as its a quagmire waiting to happen... Not only is it insecure for the user doing so, its a massive liability waiting to happen for the app developer and financial institutions. Sure, financial institutions could force a user to sign a contract stating if their device is rooted, they, not the financial institution, are liable for all fraudulent purchases made on the account, whether from the device or not. That's a liability no consumer is going to agree to, and therefore no one can [nor should] expect a financial institution to do so either.
[Nexus 6  General] jiggyman:
I can confirm Android Pay works with Stock Marshmallow 6.0.1 build MMB29S, with TWRP and non-rooted.
[Nexus 6  General] JW09I4:
The issue was he was rooted
[Nexus 6  General] jiggyman:
Ahh OK.
[Nexus 6  General] Padron26:
everything went well, rooted stock rom nexus 6 6.0 on Verizon
[Nexus 6  General] Jnewell05:
It works for me, just rebooted afterwards and bam working
[Nexus 6  General] Falinor:
Yeah I got it working. Had to delete BOOKS from the system/apps folder (never used it) w/root. issued the command, rooted, gtg! even using android pay while rooted is beautiful as well :)
[Nexus 6  General] Jnewell05:
I actually pay for tethering, 15gb bring your own phone plan with AT&T, but hate that the notification quick settings tile doesn't work unless you go into settings and enable it there.
[Nexus 6  General] JW09I4:
Are you disabling SU, then using Android Pay, or how are you getting it to work, as the API will refuse access if you're rooted.
[Nexus 6  General] Falinor:
I'm not disabling anything.

http://xdaforums.com/nexus-5x/general/passing-safetynet-root-t3307659

-Starting from stock 6.01

-Flashed systemless SuperSU 2.67 from TWRP (See UPDATE 3 below to make sure you have a systemless install)

-run "adb shell"

-from adb shell run "su"

-from adb shell run "chmod 751 /su/bin"

- if you have a "/su/xbin_bind" folder, make sure that is deleted too.

Been rooted and I've been using android pay the past 4 days as root. Passes SafetyNet checker as well.
[Nexus 6  General] JW09I4:
That's interesting, but makes sense.

Just an FYI:

Using a finance app, like Android Pay, which generates token and authorization keys on the physical device itself, is downright dangerous on a rooted device. I understand why rooted users want to use Android Pay on their rooted devices, however there are very real, and extremely serious, consequences that are not a matter of if, but when, they will occur.

Android Pay is different than say using a web browser to make payments, such as one click on Amazon or PayPal. Services like that generate all of their tokens on a remote, highly secured server. In contrast, Android Pay does not, generating both on the device itself. This allows for a few things if used on a rooted device:

An exploit would be able to generate tokens and use them them to make fraudulent purchases, all the while preventing the physical funds from being transferred to the merchant.

An exploit would be able to generate tokens and make fraudulent purchases without the knowledge or consent of the user.

This has far reaching consequences, affecting both the US and World economies. It is not a matter of if an exploit will be created to do the above, but when, and when it does occur, it will cause disastrous consequences if rooted users insist on using Android Pay.
[Nexus 6  General] Falinor:
Make sure to share this with /r/android.
[Nexus 6  General] JW09I4:
Great suggestion, I didn't think of that =]

No one can force a rooted user from using Android Pay if a way around the API is utilized, however if a user insists (as Android Pay is an amazing app), please do a couple of things to lock it down:

Password protect the app with a complex password (Sophos's free UTM app allows doing so, as do other apps), preventing the app from being accessed.

Explicitly deny the app root access within SU

Do not download apps outside of the Google Play Store, and when doing so, take care to read the permissions being requested.

Do not side-load apps unless you 100% trust the developer and keep unknown sources disabled until one needs it to be enabled, disabling it again once done.
​

These may or may not prevent an exploit from exploiting the API, but it's at least an attempt to make it more difficult to exploit. I understand why many rooted users may not take the time to thoroughly research the financial implications of using Android Pay on a rooted device, however if a rooted user insists on using Android Pay on their device, please take 15min or so to do a bit of research on Google as to why utilizing Android Pay on a rooted device is a bad idea, not just for the user themselves, but also everyone else. I'm not involved in finance or financial security and there are individuals who have written about the above, offering in depth explanations for the lament.
[Nexus 6  General] cybertec69:
The new TRWRP broke the tethering feature, you can not modify the build prop anymore, the tethering feature via modification of the build.prop has been working for me since 5.0, the February Google update and the new TWRP broke it, and the same goes for simultaneous LTE/DATA which does no longer work with the new TWRP build, and handing off from wifi to LTE takes forever. Once I went back to stock device with locked bootloader the LTE/DATA feature works like a charm as does the wifi/LTE handoff, tethering on the other hand you need to have a rooted device, which as of this moment TWRP is a mess. I need my tethering damnit.:crying:
[Nexus 6  General] JW09I4:
Can you be more specific, as I think I'm missing something.... TWRP is a custom recovery and has zero to do with the build.prop. As has been repeatedly stated several times in this thread, the last time this was addressed being post 152, the build.prop is editable.. please read post 152 to learn why and post 147 to learn how
[Nexus 6  General] jashton23:
You are correct on how the build prop isn't working. TRWRP is just a recovery so it has zero effect on the build prop. On a new update on my nexus 6 it wouldn't let me update the build prop..... well it would but then my phone wouldn't save it without getting stuck in a boot loop... I have however found a fix assuming you have the nexus 6. I installed the ROM "Pure nexus" it has the build prop built into it. I have found this to be my fix without dealing with build prop issues anymore. This is my favorite rom on the nexus 6 and I have had zero issues on it due to the awesome developers.

---------- Post added at 08:28 PM ---------- Previous post was at 08:27 PM ----------

Here is the link to that rom

http://xdaforums.com/nexus-6/development/rom-pure-nexus-project-t3148214
[Nexus 6  General] JW09I4:
Editing of the build.prop has not changed, nor does TWRP have anything to do with the initial refusal to save any changes to the build.prop. If you were to utilize the command df, you'd immediately see Google ensured, most likely as a security feature, the system partition was filled to 100% capacity. Since by default its at 100% capacity, its impossible to save any changes made to files, as there's literally no free space in which to save changes.

All of this has been covered extensively in the thread, and since this thread does have a search feature, it would save the users having issues time if the search function was utilized. All that needs to be done is ~10MB of data must be removed from the system partition in order for changes to be allowed. I personally recommend removing the YouTube app folder, which can be accomplished via: rm -Rf /system/app/YouTube

Be aware, whatever app you decide to remove from the system/app directory will no longer be auto installed when a factory reset is performed, and will need to be reinstalled via the PlayStore.
[Nexus 6  General] jashton23:
That makes sense. I never even looked into that issue. I just found a new rom that did it for me. Thanks for the feedback for future use.:D
[Nexus 6  General] aiiee:
I just modded build.prop yesterday, using adb pull and push. Just like JW0914 said, just make sure you've got some free space in /system before you start and it works .