yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note 4] windstrings:
Bummer, good digging, your prob right... What a loser if he is.

He does promise way too much to be believable.... I'm. Wondering why it's not released yet if the other devices work...

What's he gonna do, test every device on the planet first?
[AT&T Samsung Galaxy Note 4] b3asty:
Trolling a root topic is the worst kind of trolling ever imo. I hope there some substance to this lead. On another note, THANKS for getting this thread back on topic.
[AT&T Samsung Galaxy Note 4] :
I deleted files in system/app and system/priv-app and they all came back after reboot.
[AT&T Samsung Galaxy Note 4] reydarz:
Same here with a Note 4 on NIE, all changes to system revert. Maybe the Edge is missing the kernel level system write protection.
[AT&T Samsung Galaxy Note 4] Redapple63:
Rather than delete, go to the application manager in settings and uninstall the updates. Then with temp root, uninstall the app. It won't come back.

Good Luck
[AT&T Samsung Galaxy Note 4] bbeelzebub:
Anybody tried to install the galaxy s6 theme engine while rooted to see if it stays?
[AT&T Samsung Galaxy Note 4] CJ74753:
Doesn't stay for me. Anything to do with the /system/ is reverting back upon reboot. Not sure how a few of our members have lucked up and gotten it to not restore file system back after reboot.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
Aperently some are lucky tried everything to get anything to stick and nothing works

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] DeathLord..:
Small question everyone.

Would it be possible to first root the ATT note 4 stock rom and while it's still in the rooted state rip the rom from the phone then possibly install the rooted rom with odin?

Only ask what opinions are not asking to be insulted or put down.
[AT&T Samsung Galaxy Note 4] Sippi4x4man:
I'm pretty sure this is supposed to be a root progress thread not a Q/A thread as pointed out here. I don't want it to get shutdown.
[AT&T Samsung Galaxy Note 4] DeathLord..:
I have not done anything that has not already been done several times. We are trying to help in any way possible to help get a permanent root. If the so called professional devs could find root with out any tips or questions or ideas we all would have had root by now and not rely on a program from Korea that has gotten closer then any one else.
[AT&T Samsung Galaxy Note 4] Sippi4x4man:
I agree with you and I was not referring to your post specifically.
[AT&T Samsung Galaxy Note 4] Android.Ninja:
Any serious ideas that are brought to our attention are notated in the case we would need to referrence them in the future. ?

Developers don't need no stinkin' signature!

If I've been able to help you, please hit the "Thanks" button. ;)
[AT&T Samsung Galaxy Note 4] DeathLord..:
I do apologize for my out burst. I have been attacked so much that it's a natural impulse now. I do apologize again.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
I'm no genius on this sort of thing but could the kingroot apk be modified to after in installs and root it runs a script that uninstalls Kingusers then Installs superuser and the binary because maybe if you activate the option to survive Ota updates maybe it cN survive a reboot

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] Android.Ninja:
I don't see an apology being necessary. A few of your ideas have been exceptionally helpful. :good:
[AT&T Samsung Galaxy Note 4] DeathLord..:
Jolly Rogers,

I believe that to be a fairly good idea if it is possible. I had mentioned that a day or two ago and I was practically cyber beat down but it seems possible. To take the kingoroot exe file unpack age it and install supersu and see what happens.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
Well like I said it would have to be more then that you would have to let it install the entire way then have it run something to make it unistall the programs it installed and install supersu and the binary files so it's all already there

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] DeathLord..:
I'm curious if we could find a Dev who is willing to test this or inform us if it would eveN be possible
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
I know a few devs but I. Doubt any of them. Want to even take a crack at it

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] DeathLord..:
Hi Ninja,

Thanks for the comment. :)

---------- Post added at 03:27 AM ---------- Previous post was at 03:26 AM ----------

I have my faith following one. I hope he sees this and can comment if possible.
[AT&T Samsung Galaxy Note 4] cstayton:
Its been tried but was not successful
[AT&T Samsung Galaxy Note 4] jinx10000:
I haven't written an android application in years but I know you used to be able to set permissions to run an application automatically on reboot. I know this wouldn't be perfect but I wonder if someone with a lot of smali experience could edit King Root to run on reboot and not require any button presses. Maybe a convoluted partial solution since it wouldn't root until after a full boot but it could remove the manual aspect. Or maybe talk them into adding that option....

Not sure how helpful that would be if there wasn't some type of hibernation option/application that would save the rooted system state and rewrite it after boot up. Or how that would function with rooted apps that require a reboot.

Obviously removing write restrictions through a kernel module would work much better if you could figure out how to make it persistent after boot. However, I didn't think any kernel mods were feasible with a locked bootloader.

Mainly just thinking out loud and tired so don't be too hostile. :)
[AT&T Samsung Galaxy Note 4] DeathLord..:
[MENTION=3758230]cstayton[/MENTION].. Thank you for your input. This is all we are asking and even hoping is we all share our thoughts and ideas and communicate with Devs so we not only know how the process is going but we can learn at the same time. Thank you. :)

---------- Post added at 03:37 AM ---------- Previous post was at 03:33 AM ----------

[MENTION=1745731]jinx10000[/MENTION] you will never hear a complaint from me. I except any ideas or thoughts as to helping US the people achieve a permanent root. I like your idea. :)
[AT&T Samsung Galaxy Note 4] Android.Ninja:
Ok, here's an update on our teams progress.* Please read everything "Very Carefully" so there is no misunderstanding on our comments.

We have several people, including myself, contributing to this project, on our own time. There is absolutely no pay, but a lot of criticism, which somewhat can be understood, because everyone is hungry for a full root. Our group promises not to try and prove what we are accomplishing, as we dont want to release anything half finished and or incomplete, or give our work to someone else who would attempt to take credit for for the work that we've done. We are doing this voluntarily. We want you to know despite any speculation from others, that we are working diligently on obtaining full root. We are also willing to listen to any ideas, thoughts, or input that you might have. Resolutions are often found in the most obscure places. We do ask that you make these comments in the appropiate thread or waiting room as to not vex the mods. We may not be first to discover "Full Root." However we will do our best to perfect it.

Now on with the progress:

Yokyo is assisting me with the issue of losing root on every reboot. Write protection is the key to solving this issue, as why changes don't stick after reboot, and reverts back. Yokyo has taken some of my work and is in the process of trying to get root to stick after reboot. He mostly deals with phones overseas, but is very knowledgable.

We are working on this on several levels. Now to make this very clear. We are working on a method to deliver root, WHEN full root is obtained. WE HAVE NOT YET ACHIEVED FULL ROOT, BUT WE ARE CLOSE. We are not just going to stop working just because we are still trying to figure out one problem. We want to have a smooth delivery method or tool, that is easily and readily able to be used by most anyone. Please be patient, and we will work together to achieve root.
[AT&T Samsung Galaxy Note 4] DeathLord..:
Something a lot of people in this world have forgotten. All ideas or inventions in life at one time was considered Dumb or Stupid or impossible. But yet we have these ideas and those thoughts and those inventions. Now what once was stupid or dumb we as humans can not leave without. ;) :)
[AT&T Samsung Galaxy Note 4] GabrielOspina:
Mods are already vexed as is , and I understand why
[AT&T Samsung Galaxy Note 4] DeathLord..:
Thank You and Yokyo for all of your efforts and willing to make this possible. :)

---------- Post added at 03:58 AM ---------- Previous post was at 03:54 AM ----------

If you wouldn't mind share the reason why with us who are here to share and communicate and learn. :)
[AT&T Samsung Galaxy Note 4] mrcoolgli:
They keep shutting down the actual developer threads because people keep starting up conversation in them that is either already posted or has already been tried without reading the previous pages. While I agree there should be rules to post the developers forum, just delete the messages that are not relevant. That's what the moderator is for. Instead they just close the forum which makes it that much hard to obtain relevant knowledge. Frankly I am not surprised that most developers are not working on the NOTE 4 root due to the lack of support from the moderators on this site. I bet they delete this message though!
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
This may have been covered but where are we trying to write to that write protection has to be disabled

Sent From The EDGE

---------- Post added at 04:06 AM ---------- Previous post was at 03:59 AM ----------

i also found this but as im no good at terminal i dont know how to use it but its something called rootmyvalet

The Second way (app way):

Push the su binary to /data/local/tmp using adb push su /data/local/tmp

Push the roothandler binary to /data/local/tmp using adb push roothandler /data/local/tmp

Set the roothandler binary permission using adb shell chmod 0755 /data/local/tmp/roothandler

Push the installsu.sh script to /data/local/tmp using adb push installsu.sh /data/local/tmp

Set the installsu.sh script the execution permission using adb shell chmod 0755 /data/local/tmp/installsu.sh

Install the APK using adb install RootMyValet.apk. If that does not work then type the full path to the apk. E.G. adb install /path/to/apk/app.apk

Start the app on the device, hit the button that says "Push SU Binary"

Wait about a minute

Enjoy your root!

SOURCE https://github.com/Unkn0wn-0nes/RootMyValet/wiki/Manual-installation-Instructions
[AT&T Samsung Galaxy Note 4] TechSavvy2:
Has the pingpong root that was released recently for the Galaxy S6 and S6 Edge been tried/adapted at all for this device? Would seem relevant as its Lollipop on Sammy device.

I searched the thread for pingpong and came up empty handed, sorry if its been brought up....
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
It's been tried

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] kirewade:
I believe the root used for pingpong is based on a processor exploit and since note 4 has a different processor then it would never work for the note 4
[AT&T Samsung Galaxy Note 4] killerocker:
That is correct
[AT&T Samsung Galaxy Note 4] Kyuta Syuko:
/system is write protected so that any changes that would provide a full root (and for some any changes at all) are reverted upon reboot.
[AT&T Samsung Galaxy Note 4] KennyG123:
You could not be more wrong. The entire section that thread is in is clearly marked as DEVELOPERS ONLY..so no one BUT developers should be contributing to the root thread in that section. Anyone else would be infracted or banned. There are threads in each of the General sections for people to discuss who are not developers. The thread is closed with a CLEAR closing message...but I will explain it...temp root was achieved. Developers left that thread to privately try to make it permanent. The message was posted that any developers can PM me to open it back up to collaborate...none have. It was closed also because no one read the sticky or the dozens of moderator warnings and would ask "Can I haz flashing file?" And FYI it was moderators who made a section JUST for developers to discuss these things where they cannot be bothered by all these questions...so it is the members posting in there that are NOT supporting the developers. I am sorry you are so misinformed.
[AT&T Samsung Galaxy Note 4] nyydynasty:
[off topic suggestion]

XDA should create a developer group and assign full edit permissions to that section for that dev group and readonly permissions for everyone else. That will solve all these issues (at least in that section)...just my .02

[/off topic suggestion]
[AT&T Samsung Galaxy Note 4] elliwigy:
so you want mods to literally sit there and dslete posts every few minutes that dont belong instead of having a life especially when they do not even get paid to moderate these forums?

Give them a break... Myself and countless others are also getting tired of reading the same repeated questions and useless "ideas" posted over and over and over again.. these rediculous posts should not be in a development thread at all since the people posting it have 0 knowledge on rooting or exploiting Android devices.. Its amazing how many people will use a Google search for useless knowledge to feel they are "contributing" but will not use it to see something was already attempted..

Root was already done! It is write protection that needs to be handled now which is another reason the dev "root" thread was closed since root was already achieved.

With that being said, its only a matter of time before people get this thread shut down becauze I see less talk on root progress in here by the hour.

I for one thank Kenny and the other mods for doing a great job (and all for free) and cant imagine how in the world they put up with all these threads they moderate in and all the useless and repeated questions on top of ppl not folllowing simple rules.
[AT&T Samsung Galaxy Note 4] azumandias:
So will there also be a section dedicated to root hackers attempting to get full write permission for the developer forums? :laugh:
[AT&T Samsung Galaxy Note 4] KennyG123:
So who is supposed to interview and vet all these "developers"? So a new member with developer knowledge would not be able to post? Geohot had 5 posts when he announced one of his root methods. Will a new member sit around and wait weeks while he is vetted to be" knowledgeable" enough to be put in the special group allowed to post there? How about instead members read the stickies, warnings and rules? Wouldn't that be easier on a volunteer staff?
[AT&T Samsung Galaxy Note 4] raynan:
And the Devs ;)
[AT&T Samsung Galaxy Note 4] nyydynasty:
Relying on users to read stickies, warnings and rules obviously does not work...not on this forum and not on any forum. Unless the mods are willing to start banning people temporarily who dont listen, instead of just threatening them with the ban stick, warnings and thread locks are not effective because it'll just keep happening over and over.

More importantly, If XDA is really trying to get devs to use their forum to collaborate on whatever they're working on, requiring them to PM a moderator to post in a locked developers thread is not the way to promote that. I totally understand why it's locked...believe me, i do understand that. But something else should be done to get those guys to actively post in that section.

Its a problem I'm glad I dont have to deal with :D

anyway, back on topic....if there was one.
[AT&T Samsung Galaxy Note 4] Clark Joseph Kent:
The Judge is willing....and yes I will give a warning, just one warning....just ask.

And what was the topic here?
[AT&T Samsung Galaxy Note 4] eklipz3:
Maybe make the warnings blink

Sent from my VS985 4G
[AT&T Samsung Galaxy Note 4] GabrielOspina:
Wow you are completely clueless , it was shutdown due to non devs posting
[AT&T Samsung Galaxy Note 4] raynan:
http://xdaforums.com/showthread.php?p=60640937

…
[AT&T Samsung Galaxy Note 4] Dawayne:
Thread closed

since no one can read and root was achieved
[AT&T Samsung Galaxy Note 4] xlr8shun:
Cant we all get back on topic.. dont need users and mods going off on tangent.. use PM's..
[AT&T Samsung Galaxy Note 4] GabrielOspina:
Read that non devs aren't supposed to post..... Smh
[AT&T Samsung Galaxy Note 4] KennyG123:
It was shut down because the goal of THAT thread was achieved. The devs left! So what was left? An announcement of an upcoming rooted ROM and a dozen questions by non-devs. The ONLY time it was closed and suggested that a developer PM me to open IF there is more needed to discuss is the final closing message...so no one here knows where you are getting this all from. And there were no idle threats, members were banned.

Now back on topic

Isn't this root sticking for other Sammy phones? And other phones can replace it with Supersu. What's different?
[AT&T Samsung Galaxy Note 4] CyberZion:
Sammies write protection is reverting the partition back to its default settings. Now we just have to figure out how to kill the write protection before reboot.
[AT&T Samsung Galaxy Note 4] Android.Ninja:
After reading the below, DO NOT POST anything other than "Galaxy Note 4 Root Progress" Topics.

Ok, enough please... I'm a Developer searching for root related information and ughhh, (hand slapping forehead)

I'm saying this with the upmost respect for each XDA member, Developer, etc.;

Respectfully: I understand why the Mods are so frustrated. The XDA Mods work tirelessly & extensively on keeping thousands of threads on track, deleting unnecessary post, dealing with various issues, problems and so on, etc. They do this voluntarily, and for one reason only...for the benefit of the XDA community.

2 of the most respectable mods I know are KennyG123 and Judge Joseph Dredd. I have the upmost respect for both of them, as they have the hardest jobs here on XDA. Both of them have posted time after time, to keep the threads on track, without warning or banning people unless it's absolutely the last resort. Everyone including myself, should follow the rules, read the stickies, read the thread titles, read the rules of posting, etc, etc, etc.*

I don't want to see anyone get warned, banned, or whatever... I just want root for you guys!

Please don't post anymore off-topic discussions here. This is the Galaxy Note 4 Root Progress Thread. To discuss only directly related Note 4 Root Progress as it says on the thread title.

Take all Off-Topic discussions to the Root Waiting Room, located here:

http://xdaforums.com/note-4-att/general/off-topic-roor-waiting-t3073034

Respectfully,

Android.Ninja
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
MOD EDIT QUOTE REMOVED

No I see it and why is the write protection so much more secure on our phones is there something In knox or the system that is so different I've looked through the system files many times without actually decompliling down to smali lvl(which I'm going to do next) and see nothing

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] Android.Ninja:
•Thank you Mod.

•We know so far the write protection will cause a system revert upon reboot if any changes are made. (we've tried various changes only to fail.) What we would like to determine is if there is a way to supersede those changes by implementing sometype of script that would re-run the temporary root command without keystroke to achieve a somewhat full root for the time being until someone with more knowledge than myself can determine the best way to get around this dilemma. I believe someone mentioned this method earlier, I'm just not sure how realistic it would be..

Developers don't need no stinkin' signature!

If I've been able to help you, please hit the "Thanks" button. ;)
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
Correct me if Im wrong but with a locked bootloader we cannot run anything before the phone actually boots into the Android os so a script would have to be somehow implemented in a fraction of a second right when the phone goes into the os

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] elliwigy:
wouldnt the system revert back prior to the os being booted?
[AT&T Samsung Galaxy Note 4] Kyuta Syuko:
Has anyone managed to figure out if the restoration is bootloader related or kernel related? If it's bootloader related would it even be possible to get around it?
[AT&T Samsung Galaxy Note 4] ODSTZ3RO:
Yeah I raged pretty bad when I found out it hadn't even been tested on the AT&T/ Verizon models. If gatesjunior and his team already have their own thread and will update us if they find a working permanent root method then what is this thread for? I guess we'll have to keep on waiting or ideas could be spammed here unless the mods object. And yes I do realize root achieved with kingroot is still root .
[AT&T Samsung Galaxy Note 4] thanitos:
So.... since we have temp root wasn't one of the past pocs to get temp root, inject the PoC and create permanent root that way?
[AT&T Samsung Galaxy Note 4] DeathLord..:
I think you maybe on to something there. But the question is will any of the Holy Grail Devs here will actually look into it or simply say ya got half root job done. Not by us but done.
[AT&T Samsung Galaxy Note 4] KennyG123:
I can assure you that a solution for permanent root is being worked on but due to the drama and interruptions they have taken it off site...which is exactly what the Developers ONLY thread was meant to prevent. I guess most here do not realize that the one closed thread means nothing...ANY Developer can open another thread to work on permaroot for this device. As long as the guidelines to the section are followed...they weren't and the devs took it off site. I guess we mods should be even stricter with that section and create more drama in these threads of people screaming "Ban me! Ban me!"

Again, nothing is stopping a new thread for a new goal...but the same rules apply.
[AT&T Samsung Galaxy Note 4] Android.Ninja:
KennyG123, Well said indeed ^?

Developers don't need no stinkin' signature!

If I've been able to help you, please hit the "Thanks" button. ;)
[AT&T Samsung Galaxy Note 4] CJ74753:
Continuous "Custom padlock" on bootup

Not sure if it's worth mentioning, but I've successfully got my phone to continuously have the "Custom" message on my bootup screen and I enabled Factory Mode which is enabled at each boot. I managed to edit the /efs/FactoryApp enabling "Factory Mode" and not have the system restore the changes to the /efs/FactoryApp folder. Is this partition handled differently or is this any progress?
[AT&T Samsung Galaxy Note 4] ZPaul2Fresh8:
If I may...

http://xdaforums.com/note-4-att/general/thinktank-t3107629/post60713495#post60713495
[AT&T Samsung Galaxy Note 4] eklipz3:
seems to be the same people everytime, but thanks for what you do KennyG
[AT&T Samsung Galaxy Note 4] bobloblaw1:
I'm having a little trouble following, but are you saying your changes to the system folder are sticking or just the changes to the efs partition?

I mean, the phone will automatically boot into factory mode if you corrupt the efs. Are you sure that you didn't corrupt the partition? If not and the flag to boot into efs is sticking, maybe it is something to look into. Others could definitely say more on this.
[AT&T Samsung Galaxy Note 4] CJ74753:
/efs/FactoryApp/FactoryMode by default shows "ON", changing this to "OFF" and saving it and then pressing the Power button bypasses the power menu and shuts the phone off completely. If you do the exact same save but change the entire folder of"FactoryApp file permission to 0644 including all subfolders after saving it the Power button shows the normal power menu and rebooting will give you the custom message at boot each time(I've currently lost the custom message at startup, but FactoryMode is still enabled as before reboot). Each time it boots up it turns Wifi off and talks about the phone being in "Factory Mode". Oddly after you change the folder permission to 0644 you can open the files but they all appear to be blank. Opening in text editor won't even allow you to type into it.