yashsingh1/xdaforums huggingface dataset:
[AT&T Galaxy Note 3 Android Development] xXPINCARXx:
[MENTION=5575828]Walter.White[/MENTION] Dude you are the man! This would be AMAZING if this turns out to work! +1 my friend [emoji106]
[AT&T Galaxy Note 3 Android Development] zaptear:
So... If 4.4.4 comes out soon shod we hold off updating to see if this gets us to aosp?
[AT&T Galaxy Note 3 Android Development] clothednblack:
I would hold off on updating for now, this is worth being patient for.
[AT&T Galaxy Note 3 Android Development] mikep90:
It works for me perfect. I'm on all the way NC2 everything running dynamic kat 6.1. I try the temporary one where you have to after every boot and it did it the first time I try it.
[AT&T Galaxy Note 3 Android Development] Namelesswonder:
I was able to get it to work! But it was the manual method and not the automatic method. I'll post up some pictures also to show you what I did, but here are some details about my phone:

DK 6.1

GPE Theme

MLG Bootloader

NC2 Modem

NC2 Kernel

Not network unlocked

Edit: Could an init.d script run the sh script to get it working?

---------- Post added at 09:29 PM ---------- Previous post was at 09:17 PM ----------

Sorry for the double post... but I have figured out how to get the automatic script to work!

The rest of the init.d scripts (if you have DK I'm assuming) all have numbers before them (e.g. 00runthis, 04runafterthat, 08sdcardstuff, 99runlast).

You have to rename the script to

99SE_Status_Change_via_kmem

and set the permissions to 0777.

[IMG="It works!"]http://i.imgur.com/9ruPcKb.png[/IMG]
[AT&T Galaxy Note 3 Android Development] Walter.White:
Finally some success story. For me it even works without the number first.
[AT&T Galaxy Note 3 Android Development] Walter.White:
Another success story. Not sure why it works on this devices.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Dang it, still didn't work, I will keep trying
[AT&T Galaxy Note 3 Android Development] mikep90:
I didn't try the automatic one just the temporary one so it wouldn't apply after I have rebooted the phone until I knew how to change it back after doing the automatic one. But I believe it would work if I would try it.

---------- Post added at 02:42 AM ---------- Previous post was at 02:39 AM ----------

Is there a way to change it back after the automatic one at boot and if so I will try it out to see if that will work.
[AT&T Galaxy Note 3 Android Development] Namelesswonder:
I guess the other thing to try is to do the manual one first, then put the automatic one in place. That might work.
[AT&T Galaxy Note 3 Android Development] pctechdroid:
Tried the auto and the manual. Still get enforcing. This is my current settings, do I need to change my baseband and kernel to NC2?
[AT&T Galaxy Note 3 Android Development] clothednblack:
I have the manual one in place and the automatic one in its place, rebooted and nothing. Renamed with 99 and nothing. This is irritating
[AT&T Galaxy Note 3 Android Development] mikep90:
I had got the manual one just like how he said to do it. I never try the automatic one until I know how to change it back.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Maybe I will reflash the rom then do this before any mods, it's still not working
[AT&T Galaxy Note 3 Android Development] mikep90:
Here is my proof
[AT&T Galaxy Note 3 Android Development] Namelesswonder:
You'll need to update the kernel to NC2, not your bootloader (if it is on MLG). To do so just download the file Walter.White linked in the OP and open up Odin and click AP and then select the downloaded file and flash it. This only changes the kernel, which can be freely changed.

All you would have to do is remove the init.d script and reboot, the automatic one just does what the manual one does except when your phone boots.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Your screenshots show hardware at the bottom, mine doesn't, doubt that has anything to do with it, just noticed is all

---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------

I have that
[AT&T Galaxy Note 3 Android Development] Walter.White:
You will see the hardware. Just scroll up. Mine shows everything in one screen because I changed the dpi to 400.

[MENTION=5875864]mikep90[/MENTION] you can try the automatic one. Just delete the script from the init.d folder and it will revert back automatically after reboot.

We need to figure out the common thread between mine, [MENTION=5875864]mikep90[/MENTION] and [MENTION=5689426]Namelesswonder[/MENTION] phone, so that we can figure out why it only works on this 3 phones.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Nope
[AT&T Galaxy Note 3 Android Development] mikep90:
Ok for the automatic to work I had to put 99 In front of the file and when I did that it works but it wouldn't without doing that first.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Lol I have done all of this
[AT&T Galaxy Note 3 Android Development] mikep90:
U on the NC2 and all that. Try using Rom toolbox pro. That could be the reason

---------- Post added at 04:05 AM ---------- Previous post was at 04:01 AM ----------

U don't you have a hardware version. How's that u don't have that.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Just re-flashed rom, now it shows hardware

But still enforcing

---------- Post added at 08:17 PM ---------- Previous post was at 08:07 PM ----------

I'm on NC2 from the op, everything else is a match. I have tried everything mentioned

---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------

I changed it to 777 but after a reboot, it changed back
[AT&T Galaxy Note 3 Android Development] mikep90:
What could it be that you have different from us. Once I did it works without any problems.
[AT&T Galaxy Note 3 Android Development] Namelesswonder:
This is becoming a real doozy. The only thing I could think of is that the app you are using to change permissions is not actually changing permissions. I used ES File Manager to change the permissions and that worked. Hopefully we'll find a way to get it working.

Edit: Also does anyone know any applications to test out that use SELinux permissive? I tried out Paragon NTFS, but it turns out that permissive is actually no longer needed to mount NTFS drives.
[AT&T Galaxy Note 3 Android Development] mikep90:
Yeah your permissions are off. It looks like it's your root browser that is giving you problems. You should use rom toolbox pro.
[AT&T Galaxy Note 3 Android Development] bri315317:
The hardware version showing is a csc edit, most likely an xposed app wrecked your csc.
[AT&T Galaxy Note 3 Android Development] Surge1223:
I would mount system rw first

su

mount -o remount, rw /system

Then i would type

echo 0 >/proc/sys/kernel/kptr_restrict

Id also uninstall any security software and uninstall any SEPolicy updates.

Oh maybe freeze Sysscope as well.

We could also break the script into parts, since it does about 6 or 7 commands linked together and uses variables from the output of one as input for the next.

Essentially, it searches kallsyms for selinux enforcing, takes the address and converts it from virtual mem to physical mem then uses dd to skip to amount of bytes equivalent to the address in memory that selinux enforcing is at and overwrites it
[AT&T Galaxy Note 3 Android Development] Namelesswonder:
Will it be possible to bake something like this into the next update of DK? It should because it is just an init.d script, and at least that'll remove some headaches for some people (still have to get them on the NC2 kernel if they aren't).
[AT&T Galaxy Note 3 Android Development] clothednblack:
Reflashing DK fixed it
[AT&T Galaxy Note 3 Android Development] mikep90:
Did you try a differnt file manager. The one he was talking about is free and it works Ok and the one I use it cost money. I bet you try ez file manager and I bet it will fix your problems
[AT&T Galaxy Note 3 Android Development] clothednblack:
Just bought rom toolbox pro
[AT&T Galaxy Note 3 Android Development] mikep90:
That is a good choice haves a lot of functions and can do everything with it

---------- Post added at 04:50 AM ---------- Previous post was at 04:48 AM ----------

Let me know what happens.
[AT&T Galaxy Note 3 Android Development] clothednblack:
I used 3c toolbox pro too, nothing works
[AT&T Galaxy Note 3 Android Development] mikep90:
Did you set the right permissions and it kept them too and put 99 In front of it after renaming it.

---------- Post added at 04:57 AM ---------- Previous post was at 04:56 AM ----------

Try to do it manually first than try automatic. You have any xposed modules install that could be messing it up. What theme are you on. I'm use gpe.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Rom toolbox pro shows its already 777
[AT&T Galaxy Note 3 Android Development] mikep90:
Now just make sure you rename it right and put 99 In front of it and reboot. But try it manually first.
[AT&T Galaxy Note 3 Android Development] clothednblack:
I'm done trying Tonight, it didn't work
[AT&T Galaxy Note 3 Android Development] mikep90:
Well I'm sorry it didn't work for you. I have no clue y it didn't work for ya. Maybe one day back it up and restore back to stock than root it again and install dynamic than try it again one day but I hope we can figure it out for you.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Tried without xposed on, I'm on GPE too and tried manually and it said enforcing then rebooted.

---------- Post added at 09:20 PM ---------- Previous post was at 09:19 PM ----------

Tried on stock DK too lol
[AT&T Galaxy Note 3 Android Development] mikep90:
If you do it manually you can't reboot the phone or it will change back like it was
[AT&T Galaxy Note 3 Android Development] clothednblack:
I meant before reboot
[AT&T Galaxy Note 3 Android Development] mikep90:
Or it could of been a bad download of the file. Maybe try to re download it and try it again

---------- Post added at 05:46 AM ---------- Previous post was at 05:44 AM ----------

Did you copy the whole command I didn't see su in front of it.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Tried that too and what Surge said, oh well.
[AT&T Galaxy Note 3 Android Development] mikep90:
Copy and paste it in su -c /data/local/tmp/SE_Status_Change_via_kmem.sh
[AT&T Galaxy Note 3 Android Development] clothednblack:
Already did that and then opened terminal and typed in exactly what is in the op. It says changing from enforcing to enforcing and yes I checked the su box.
[AT&T Galaxy Note 3 Android Development] mikep90:
Or you can try this In rom toolbox go to scripter and import that script in it and follow the commands and it work for that way to also.
[AT&T Galaxy Note 3 Android Development] mikep90:
Awww dawn I don't know y. Every time I do it says permissive.
[AT&T Galaxy Note 3 Android Development] clothednblack:
I appreciate all your help, maybe something will be discovered later on, I know I'm not the only one that this doesn't work for, just seem to be the only one determined to make it work lol
[AT&T Galaxy Note 3 Android Development] carl1961:
[MENTION=4020863]clothednblack[/MENTION], Your not alone mine does exactly like your, I also do not have the Hardware Rev 3.0 at bottom of about page. I am completely NC2 stock from the NC2 odin files.

---------- Post added at 06:48 AM ---------- Previous post was at 06:33 AM ----------

[MENTION=5875864]mikep90[/MENTION], Your bootloader is A3?
[AT&T Galaxy Note 3 Android Development] clothednblack:
I got the hardware Rev back after Reflashing DK, this is very strange indeed. I know we all have our own settings but what could cause a issue with permission? Crazy.
[AT&T Galaxy Note 3 Android Development] mikep90:
Yes it is
[AT&T Galaxy Note 3 Android Development] ahmarchi:
mine does same thing,set it up in init.d forlder..came back to check still says enforicing. bummer,hope we get this working!!
[AT&T Galaxy Note 3 Android Development] mikep90:
Try this rename it and put 99 In front of it. That's how I had got it to work.
[AT&T Galaxy Note 3 Android Development] gangpe:
MLG bootloader question

Yo Mr. White,

Do you think it's possible that MLG bootloader is a prereq for this script? I ask because the n900A I bought had NC2 right out of the gate, so I'm guessing either it came directly from AT&T like this or the original owner installed NC2. When I had my S3, I remember that once you loaded the kitkat bootloader, you couldn't go back to jellybean....

Are those who have been successful on the MLG bootloader? Just curious....
[AT&T Galaxy Note 3 Android Development] ashman5:
Based on what I read, all that were successful were on MLG bootloader and NC2 kernal.
[AT&T Galaxy Note 3 Android Development] Face_Plant:
Didn't work for me either.
[AT&T Galaxy Note 3 Android Development] Walter.White:
Not true. Bri is on MLG and it didn't work for him. whereas [MENTION=5875864]mikep90[/MENTION] is on NC2 BL and it works for him.

[MENTION=4020863]clothednblack[/MENTION] this may sound crazy or something but this is the only other thing I could think off. Just try this as last ditch effort.

1. Boot into SS.

2. Go to Advanced and then fix permissions.

3. Wipe Dalvik & cache.

4. Try doing it manually now.

If it still doesn't work, try this.

1. Open up 3C Toolbox Pro.

2. Go to 'Quick optimization and clean-up

3. Select the following and press OK. 'Optimize apps loading', 'Optimize database access', 'Fix permissions', 'Clean memory', 'Trim all partitions' & 'Clear caches'.

4. Reboot.

5. Try doing it manually now.

If it still doesn't work.

1. Open up your build.prop

2. Change ro.sf.lcd_density= to 400

3. Reboot.

4. Try doing it manually now.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Ok, I'm off to try it now

Edit: [MENTION=5575828]Walter.White[/MENTION]

Step one failed

Step 2 won't let me change those

Haven't done step 3 yet
[AT&T Galaxy Note 3 Android Development] Namelesswonder:
I haven't changed my DPI and it still worked for me. However I have done the optimizations with 3C toolbox and I've cleared my dalvik cache many times from me trying to get the new play store. I guess we can try making a flashable file and see if that works.
[AT&T Galaxy Note 3 Android Development] Walter.White:
What SuperSU version are you on?
[AT&T Galaxy Note 3 Android Development] clothednblack:
It finally was highlighted and running
[AT&T Galaxy Note 3 Android Development] Walter.White:
Okay. One last thing. Can you tell me what are the permissions of the following files.

1. /proc/kallsyms

2. /dev/kmem
[AT&T Galaxy Note 3 Android Development] mikep90:
You think that might be it I'm on 2.13 and it works real good.
[AT&T Galaxy Note 3 Android Development] clothednblack:
1. Is 444

2. I don't have that one

Step 2 from previous post failed
[AT&T Galaxy Note 3 Android Development] Walter.White:
I think there is your problem. /dev/kmem is needed and permission on it has to be 600. While the permission on your /proc/kallsyms is correct.

[MENTION=5875864]mikep90[/MENTION] and [MENTION=5689426]Namelesswonder[/MENTION] Do you guys have /dev/kmem ?? And if so, whats the permission of that file?
[AT&T Galaxy Note 3 Android Development] clothednblack:
Now I'm curious as to why I don't have that
[AT&T Galaxy Note 3 Android Development] mikep90:
All of mine have 04:17 in front of everyone
[AT&T Galaxy Note 3 Android Development] clothednblack:
Send me yours, then I will have it too lol
[AT&T Galaxy Note 3 Android Development] Walter.White:
I don't think that would be a good idea since its kernel related.
[AT&T Galaxy Note 3 Android Development] clothednblack:
I was kidding, strange that you are on DK and so am I, yet I don't have that file and Mike doesn't either. I tried everything except the lcd as I don't see that changing the outcome.
[AT&T Galaxy Note 3 Android Development] Walter.White:
That file is definitely needed for this script to work. I have no idea as to why you dont have it.

[MENTION=4020863]clothednblack[/MENTION] Can you type the following in the Terminal and post output?

su
printf '\x00' | su -c dd of=/dev/kmem seek=$( printf '%d\n' '0x'`cat /proc/kallsyms | grep ".*\ selinux\_enforcing" | cut -f 1 -d " "` ) bs=1 count=1 conv=notrunc
[AT&T Galaxy Note 3 Android Development] mikep90:
Here goes mine I don't have it but my is differnt than yalls
[AT&T Galaxy Note 3 Android Development] clothednblack:
I will use Odin again for the NC2 kernel and see if I get it

---------- Post added at 06:29 PM ---------- Previous post was at 06:25 PM ----------
[AT&T Galaxy Note 3 Android Development] Walter.White:
Run it with that su box checked.

Also there is a space between su and printf. In your terminal it looks like they are together 'suprintf'
[AT&T Galaxy Note 3 Android Development] carl1961:
I do not have kmem either

but when I try this:

su

printf '\x00' | su -c dd of=/dev/kmem seek=$( printf '%d\n' '0x'`cat /proc/kalls

yms | grep ".*\ selinux\_enforcing" | cut -f 1 -d " "` ) bs=1 count=1 conv=notru

/dev/kmem: cannot open for write: Permission denied
[AT&T Galaxy Note 3 Android Development] mikep90:
Will it make a difference if my is doing it automatically
[AT&T Galaxy Note 3 Android Development] carl1961:
[MENTION=5575828]Walter.White[/MENTION] I even installed MGL Kernel and still no /dev/kmem

I even added or changed in my build.prop

ro.build.selinux=0

ro.kernel.qemu=0

ro.config.tima=0

ro.config.knox=0

[MENTION=5875864]mikep90[/MENTION] verified he has no showing kmem, yet he gets Permissive

:confused:
[AT&T Galaxy Note 3 Android Development] majortaylor:
I've tried all of the above and I'm still getting enforced. Also I'm missing the kmem as well
[AT&T Galaxy Note 3 Android Development] mikep90:
Will it have anything to do with supersu bc I have 2.13 install. It sounds like me it can't write to it.

---------- Post added at 03:07 AM ---------- Previous post was at 03:04 AM ----------

I will help tho anything you need me to check or try I will to help everybody out.
[AT&T Galaxy Note 3 Android Development] carl1961:
[MENTION=5875864]mikep90[/MENTION] did you update to NC2 using the latest odin files or did you update through OTA

just wondering if the latest Odin files or more security fixed.
[AT&T Galaxy Note 3 Android Development] mikep90:
It was already on there I try to do the warranty exchange trying to get 4.3 but it came to me on 4.4.2
[AT&T Galaxy Note 3 Android Development] clothednblack:
Same thing and this is my SU I run
[AT&T Galaxy Note 3 Android Development] mikep90:
Upgrade it to 2.13. You should get this app aptoid it will help with updates and such not that you haven't received yet
[AT&T Galaxy Note 3 Android Development] Walter.White:
Okay. Update to this SuperSU http://d-h.st/afU Open it and update the binary. Reboot.
[AT&T Galaxy Note 3 Android Development] mikep90:
That's one thing I have differnt than him
[AT&T Galaxy Note 3 Android Development] Walter.White:
I'm also on SuperSU 2.13. And I started using this script after I upgraded to 2.13. So maybe that was the problem :/
[AT&T Galaxy Note 3 Android Development] carl1961:
[MENTION=5875864]mikep90[/MENTION] You where right, I updated supersu

[MENTION=5575828]Walter.White[/MENTION]

also kmem showed up and also I'm still on the MGL kernel I tested with.

C:\Users\carl>adb shell

shell@hlteatt:/ $ su -c /sdcard/SE_Status_Change_via_kmem.sh

su -c /sdcard/SE_Status_Change_via_kmem.sh

SELinux is set to: Enforcing

Please wait...done

SELinux is now set to: Permissive

shell@hlteatt:/ $
[AT&T Galaxy Note 3 Android Development] mikep90:
I had mention that way back in the pages lol. But I still don't have kmem in that spot but I'm also doing it as automatic
[AT&T Galaxy Note 3 Android Development] Walter.White:
Alright so it is the SuperSU!

Update it to the 2.13 and it will work for you guys :)
[AT&T Galaxy Note 3 Android Development] mikep90:
We finally solve the problem.
[AT&T Galaxy Note 3 Android Development] Walter.White:
So it works with MLG and NC2 kernel too nice.

I did mention SuperSU 2.13 in this post on 10/11 :p http://xdaforums.com/showpost.php?p=55968140&postcount=54
[AT&T Galaxy Note 3 Android Development] clothednblack:
Dang it, I don't know why I didn't already have the latest su but that was the issue.

Thank you everyone for your help!
[AT&T Galaxy Note 3 Android Development] carl1961:
[MENTION=5575828]Walter.White[/MENTION],

Now what or we going to do next LOL
[AT&T Galaxy Note 3 Android Development] Walter.White:
Now we follow this thread here http://xdaforums.com/showthread.php?t=2500826&page=160 and root for [MENTION=4939386]Surge1223[/MENTION] to get the kexec working :)
[AT&T Galaxy Note 3 Android Development] pctechdroid:
So I updated to the latest SuperSU and ran the script from Root Explorer. After running the script for auto, it set to permissive. I did a reboot and it reverted back to enforcing.
[AT&T Galaxy Note 3 Android Development] mikep90:
You had set it up using the manually way that haves to be really after every boot.

---------- Post added at 04:17 AM ---------- Previous post was at 04:15 AM ----------
[AT&T Galaxy Note 3 Android Development] ast11:
After upgrading to supersu 2.13 manually running the script does change selinux to permissive.

But I cannot get it to automatically apply the script at boot. I've tried it both with a 99 prefixed and not. I'm running the script manually from /system/etc/init.d so I know the file is fine.
[AT&T Galaxy Note 3 Android Development] clothednblack:
Hmm, strange that 99 helps some but knowing 2.13 helps all so far, that's great. I didn't even try manually. I already had the other file in place and after updating su, the binary failed to update so I had to reboot for it to take, that's when the automatic script took effect.
[AT&T Galaxy Note 3 Android Development] mikep90:
What is your settings
[AT&T Galaxy Note 3 Android Development] clothednblack:
Bootloader... MLG

Kernel..... NC2

Running DynamicKat 6.1
[AT&T Galaxy Note 3 Android Development] mikep90:
Maybe that's y my ain't working without the 99 and having the file in place bc my bootloader is MLG. It got me just going bonkers trying to figure it out y my won't do it normally. Do you have the manually script in to or just the perment one.
[AT&T Galaxy Note 3 Android Development] clothednblack:
I have them both in place, but never use the manual one since I updated su and rebooted
[AT&T Galaxy Note 3 Android Development] mikep90:
Ok I don't know what happen but I deleted supersu from inside it to reinstall it and now my SU binary will not stick or install.
[AT&T Galaxy Note 3 Android Development] carl1961:
[MENTION=5575828]Walter.White[/MENTION]

I reinstalled NC2 from scratch, went through rooting,busybox,safestrap, Init.d Support Installer,SuperSu 2.1.3 and everything worked,

So I'm full NC2 from the Latest Odin files, Latest SuperSU and your SELinux init.d script Permissive a boot.

attached is Installer for your script, and Init.d installer for those without init.d support. pictures before and after SuperSu Update verifing kmem needed for script to work.
[AT&T Galaxy Note 3 Android Development] carl1961:
install this from recovery SuperSu 2.13 SuperSU from playstore is older SuperSu 2.01

you might have to reroot with TR.apk if safestrap does not start
[AT&T Galaxy Note 3 Android Development] Walter.White:
Clear cache of SuperSU app.
[AT&T Galaxy Note 3 Android Development] mikep90:
Can you help me out with my problem I made. I was trying to make it work without the 99 so I deleted the supersu app from inside to install from another source now it won't stick or install talking about the binaries.

---------- Post added at 06:10 AM ---------- Previous post was at 06:05 AM ----------

OK thabks I think that fix it

---------- Post added at 06:30 AM ---------- Previous post was at 06:10 AM ----------

OK that fix my problem with the binaries not updating. Here is my thing now after reboot and don't show permissive right away it takes about under a min to show and I still don't have that file that everybody haves. What do I need to install now to where it's working right after boot and also to have that file.