yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note 4] SacrificedWalrus:
Changes to /system do not stick, but changes to subfolders and files inside /efs do stick. After running Kingroot I was able to copy the su binary to the /efs folder and run it out of there will full permissions. After a reboot the su binary was still there, and all permissions on the folders had stayed the same EXCEPT on the /efs folder itself. So I was not able to access the /efs folder until after running KingRoot.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
Does that mean u were able to use supersu since you got the binary installed?

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] dec3169:
I was doing this same exact thing last night. I looked at all the directories that were mounted and had more than 0 bytes space available and settled on /efs. However, I'd swear that when I chose /efs I looked and saw that the mount didn't have the nosuid flag set. After a reboot my su file was still there, and still mode 4755, but it couldn't be executed because /efs was mounted with nosuid.

If we can either tweak the initrams that gets mounted as root (unlikely since it is probably hashed), or fix/bypass the write protection (possible w/kernel mod) we will have permaroot. Barring that, we need to come up with ideas.

Something I've been doing is looking at everything that gets executed as root on bootup, and seeing if any commands are executed outside of their write-protected ramfs stuff. Most of the stuff in the init rc files is executed without using the full path in the script. For those of you not UNIX oriented, the init files might have for example "chmod 755 /test", and that would be executed on boot with the first instance of "chmod" found in root's path. If you could make a "better" chmod and put it higher up in the path so it gets executed before the real chmod then you could execute whatever you wanted as root. Most vendors would put /bin/chmod 755 /test to protect against that - very basic best practices stuff. Honestly I'm stumped as to why Samsung would do that.

Another vector is editing other files that seem to stick. I've heard that the bootprop edits will stick (haven't tried yet myself). If so, why and how? Is that file linked from somewhere writeable, does Android save it somewhere on reboot, or is there something else going on? If you can write to that and it stays over a reboot, there may be other config files that stay as well. I'll probably try that this weekend myself when I have more time.

I guess the point of this post is to try to get people that may not know how to make exploits or kernel mods to look at other stuff that they may be able to do themselves. I'm a die-hard Linux guy that has been running it since 1992 (Slackware from a case of floppies), and I have been doing assessment/pen-testing work since 1998. I however have never really focused on Android since I didn't run into that on customer sites, and my phones have always been rooted. Now I'm playing catch-up and focusing on applying what I know from other security work and specifically on Linux hacking (kernel and security both) to Android. It is taking me much longer than I would like to get a foothold on my phone's environment since the layout and config files are not where I expect them to be. Eventually I'll figure that out (like moving from Solaris to Debian), but I'll help with this kind of stuff until I am stronger on Android. I know some of you guys are competent enough in Linux to do the same, so do it. The more eyes on this kind of stuff the better.
[AT&T Samsung Galaxy Note 4] SacrificedWalrus:
I was actually able to access the su binary in the efs folder from Android Terminal without rooting, but it didn't really lead anywhere. In the /efs folder I stored the su binary and supolicy in the FactoryApp directory, and set the permissions to 7777, and after a reboot I was able to cd in the FactoryApp folder and us "ls" to list the contents. Attempting to execute su lead to a "Permission denied error" and my assumption is that there needs to be something else installed before the su binary can be run, because by default the user has permission to execute binaries from the /efs folder, without root. If we could get the su binary to execute and run as root, than that would be somewhat of a perma root, we would be able to run a script to install SuperSU and other various files into the system at boot that way, although it wouldn't fix the issue of losing things such as Xposed every reboot so maybe it would be a waste of time looking into this method, I think it just depends on how early we could get the script to run at boot.
[AT&T Samsung Galaxy Note 4] dec3169:
So I misspoke when I said it couldn't be executed. I meant it couldn't be executed as root. Like I said though, the reason it won't run properly is because /efs is mounted with the nosuid flag. There is no mystery there - you can see the exact mount command in one of the init files. Unless we can unmount and remount (if we could we would already be root) or change the mount command in the init file, our copies of su will never execute as root from the /efs mount. You are correct that we can execute binaries in /efs - just not setuid binaries.
[AT&T Samsung Galaxy Note 4] DroidHelp101:
Please excuse me if this is a dumb question..

Is their any info in these files that would be usefull?
[AT&T Samsung Galaxy Note 4] gatesjunior:
SuperSU running and KingUser gone...

So we have successfully been able to remove Kingroot and all of it's applications and are now running SuperSU full time. :) We will be releasing something soon to get you all off of the Kingroot junk as soon as we can firm up a couple of small items..

Team Members:

[MENTION=4246643]Tomsgt[/MENTION]

[MENTION=4939386]Surge1223[/MENTION]

[MENTION=5868929]hsbadr[/MENTION]

[MENTION=3178012]gatesjunior[/MENTION]

Tester:

[MENTION=3388697]freddy0872[/MENTION]

Yes, we are still working on permanent root. A reboot will remove this, but at least now you will be able to quickly get back to SuperSU.
[AT&T Samsung Galaxy Note 4] Venom0642:
Nice job [MENTION=3178012]gatesjunior[/MENTION] ??? and to the team as well ? ? ?

Running On New Deadly Venom Note 4 v3.0
[AT&T Samsung Galaxy Note 4] :
Kitkat still a requirement?
[AT&T Samsung Galaxy Note 4] freddy0872:
Progress made!

Here is your confirmation on root using SuperSU

Were not just blowing smoke up you know where; claiming this and that.
[AT&T Samsung Galaxy Note 4] Tomsgt:
yes as of right now the root exploits is kingroot and requires kitkat to get root access then you will be able to run another tool to fully remove kingroot and get supersu running instead.
[AT&T Samsung Galaxy Note 4] nemopsp:
My question to this is this still a temp root? Or is it full now?

Also, Kingroot seemed very buggy, like when you was to grant apps permission, the phone would freeze up and reboot. Another issue I had was being rooted over time the system would lose root access, and then reboot. Is this still an issue?

But wonderful new!

Thank you devs. for working hard.
[AT&T Samsung Galaxy Note 4] elliwigy:
he clearly says they are still working on perma root. it seems like its just to remove kinguser so you guys can use supersu instead.. reboot still resets it.. id imagine its less buggy temp root with supersu so seems like a step in the right direction
[AT&T Samsung Galaxy Note 4] bobloblaw1:
I'm not sure if it was an edit, but the post says at the bottom that they are still working on permanent root.
[AT&T Samsung Galaxy Note 4] IceTwig:
I guess the answer would be "yes" still temporary as Gates pointed out, as far as unstable, well Tom pointed out that the new process removes "Kingsroot" so you will no longer see "Kingsroot" be unstable. If you are asking if the "NEW" process is unstable, well, that's why I assume it's still in beta. He did say also that a permanent solution was being worked on as well.
[AT&T Samsung Galaxy Note 4] Tomsgt:
I have had Supersu installed for about 3 days now and it hasnt rebooted at all. with kingroot i was also getting the freezes and reboots. Supersu is still as you put it temp root at this time. we are working on getting past the write protect on the system but it has been really difficult so far.
[AT&T Samsung Galaxy Note 4] freddy0872:
Agreed.
[AT&T Samsung Galaxy Note 4] siriom:
How hard would it be to port this over to note edge ?
[AT&T Samsung Galaxy Note 4] howellcp:
Is it sticking? I'm confused on how that reads.
[AT&T Samsung Galaxy Note 4] IceTwig:
I wont pretend to know this answer BUT I have used Kingsroot for my edge and un-installed bloatware and backed up with TB. I would venture to guess that the new procedure will work since it will probably use the same vulnerabilities that "kingsroot" uses but permanent and without it being unstable :D
[AT&T Samsung Galaxy Note 4] freddy0872:
Supersu sticks as long as you don't reboot. If you reboot you lose root access still
[AT&T Samsung Galaxy Note 4] siriom:
Any idea hows its being done ? i mean getting SU on instead of kingroot ? I wouldnt mind trying it on my edge.
[AT&T Samsung Galaxy Note 4] howellcp:
Have you tried a softboot?
[AT&T Samsung Galaxy Note 4] IceTwig:
I am sure it's not an easy process since more than a few have tried. As they stated that "it will be provided" ONCE the testing is compete and a package can be delivered.
[AT&T Samsung Galaxy Note 4] kirewade:
So even with su if we need to reboot with exposed and ada we adaway it won't save the changes correct
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
No It will save your charger get but you will have to re root once you do everything will work again and reboot should not be needed you cN download a soft reboot app from the playstore which will do the same thing

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] Venom0642:
Yup basically it won't do a full reboot with the app from playstore called reboot and all you do with that app soft reboot and should still be rooted, but let's wait to see what [MENTION=3178012]gatesjunior[/MENTION] and team got coming they are trying to fix that.

Running On New Deadly Venom Note 4 v3.0
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
Even if they don't right away because of the wrote protection this will work for most of now I have had to reboot my phone like ever besides when kingroot forced it so I'll be good

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] GabrielOspina:
Love this , actual proof , gj
[AT&T Samsung Galaxy Note 4] dslrjunky:
can someone point me in the right direction on how to root using kingroot? I dl'd the kingroot app v4 but after running, it keep on failing, after initial scan with the app it says denied permission
[AT&T Samsung Galaxy Note 4] terpin32:
if your on 5.0.1 it wont work at all has to be kitkat
[AT&T Samsung Galaxy Note 4] dslrjunky:
forgot to mention I'm on att and still on kitkat ver 4.4.4
[AT&T Samsung Galaxy Note 4] killerocker:
Honestly, I'd suggest just waiting for the new version that has been recently mentioned on here rather than settling for a sketchier, less stable product.
[AT&T Samsung Galaxy Note 4] youshady2:
Quick question so at this point is it possible to be temp rooted and be on lollipop or do we have to stay on 4.4.4 if we do the process
[AT&T Samsung Galaxy Note 4] MikeyFid:
Has to be KitKat.

I believe it was stated as recently as the last page...

Good luck.
[AT&T Samsung Galaxy Note 4] Android.Ninja:
[MENTION=3178012]gatesjunior[/MENTION] & his team;

Our upmost & sincerest "Hats Off" & "Job Well Done!" ???from our team to yours. ???

I would like to personally congratulate you & your team, for the unprecedented hard work you've done to provide successful root to the Note 4 XDA Community. My team & I worked on trying to complete this impossible task, to get as far as we could in the time allowed. I'm not one to say lightly, that I've been beaten, (lol) ? in the race for root. However I am one that believes it's important & most honorable to give the proper mention & appreciation to those who were so committed & successful in completing a task that was labeled as an impossibility.

gatesjunior,

You & your team have raised the bar for us as developers & set a new level of expertise that I have to say I truly admire. I hope that one day we could utilize our knowledge together as a team, so we can complete whatever task lays ahead in the shortest amount of time, for the XDA community. It's been a long hard road in the race for achieving root. Maybe our eagerness & competitiveness helped push for what the Note 4 community longed for, for such a long time.

So, I want to personally say "Thank You" as a friend & XDA Developer.

"Rock On!"

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] 彩色的风:
could I install Xpose with this method？
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
You could install xposed with kingroot but yes this method will be more. Stable

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] gatesjunior:
Update !!

So, we have everything working well now. There will be a post shortly. This supports full SuperSU and Kingroot is completely removed. We have also gotten it to support full soft-reboot. So as long as you do not hard reset your device, it will maintain root and SuperSU.. Kingroot is completely gone..
[AT&T Samsung Galaxy Note 4] TYMO68:
Excellent work gentleman. Indeed developers like you are what really matter in this community and most appreciated.......Bravo!

Additionally, as I'm sure this will be posted along with your new & improved method. It will not work if we have already accepted the Lolipop OTA correct? I just want to be clear so that all can see and are aware.
[AT&T Samsung Galaxy Note 4] gatesjunior:
Correct, you will need to be on KK.
[AT&T Samsung Galaxy Note 4] TYMO68:
Ugh, bummer for me then. I took the OTA awhile back to update to Lollipop. Oh well, maybe it'll follow soon with a proven method for us who are on lollipop. Either way, I still give applause for your fantastic work! Cheers
[AT&T Samsung Galaxy Note 4] gatesjunior:
You can still ODIN back to KK. I mean, correct me if I am wrong here, but does Kingroot work on Lollipop for the Note 4?? I hadn't heard that it does yet..
[AT&T Samsung Galaxy Note 4] Vindicated777:
You could always roll back!!
[AT&T Samsung Galaxy Note 4] Venom0642:
[MENTION=3178012]gatesjunior[/MENTION] again nice job ????

Maybe in the future we can get it working on lollipop ? that's if it doesn't work now unless someone can test later when it's up.

Running On New Deadly Venom Note 4 v3.0
[AT&T Samsung Galaxy Note 4] patt2k:
awesome gatesjunior,excuse my noob question, does this mean tools like safe strap (or whatever is same I think flashfire) would work with TW roms? I like lolipop actually that's why I hope for some safestrap'ish rom soon :)
[AT&T Samsung Galaxy Note 4] gatesjunior:
We are working on this.. As well as perm root. But for now, it would be safe to say no..
[AT&T Samsung Galaxy Note 4] patt2k:
Cool thanks for the answer.
[AT&T Samsung Galaxy Note 4] gatesjunior:
I appreciate the extension of the "olive branch". I am not one to return with a 4x4, that is not who I am. I would agree that the competiveness is healthy, we just cannot cross the line of anything other than that or take it personal. I want you to know that the reason I was calling you out, was because I was feeling as if you were potentially misleading the community with promises and hopes you could not deliver on. With that said, I am hopeful you will understand my position. I also realize that I am not one to judge your motives or your intentions. So I do apologize for that. I wish you and your team the best.
[AT&T Samsung Galaxy Note 4] motumbo:
Flashfire is installed to my s5 active, it does require su but it does not requires reboot to work ok. It would be safe to say that at least we could have this app installed ok? Then, don't you believe it'll be matter of time to flash a modified ota or full system to make root to stick? Please correct me if I'm wrong.
[AT&T Samsung Galaxy Note 4] gatesjunior:
Yes, you can install the application. But any attempt to try and put an image on the device will be unsuccessful at this point.
[AT&T Samsung Galaxy Note 4] KennyG123:
You would have to stay on KitKat. Xposed does not work for Samsung stock based ROMs on Lollipop currently.
[AT&T Samsung Galaxy Note 4] terpin32:
So how would we go about blocking the ota's after getting a perm root so it doesn't auto update ive done the ota blocking and knox and it doesn't work
[AT&T Samsung Galaxy Note 4] IceTwig:
This has stopped mine for updating. AT&T NoteEdge
[AT&T Samsung Galaxy Note 4] patt2k:
You can use gatejuniors debloater to block OTA's like I asked him b4 he said the are working on bringing us later "safestrap roms or flash fire I think it's newer version of safestrap"

once he or his team give us instructions on how to do I will also revert to KK on my vzw note4:)
[AT&T Samsung Galaxy Note 4] nickp27:
Mobile Odin/ Flashfire

If this means you could temporarily get root on KK; could you then install mobile odin and use everroot and upgrade to lollipop (or KK) which would then have a permanent root?

I expect you'd have to use the trick they had on the S4 booting to DL mode and then flashing the bootloader via odin on PC. I guess it would depend if this would bypass the issues stopping a permanent root at the moment.
[AT&T Samsung Galaxy Note 4] edpete97:
But xposed on KK will work then?
[AT&T Samsung Galaxy Note 4] Venom0642:
Xposed only works on KitKat, not lollipop ?as [MENTION=3125148]KennyG123[/MENTION] explained.

Running On New Deadly Venom Note 4 v3.0
[AT&T Samsung Galaxy Note 4] brentsalinas714:
What build do I need to be on?
[AT&T Samsung Galaxy Note 4] waco2hot33:
From what I gather from past post you still need to be on kk for this to work successfully ... With further work being done to acquire perma root for all
[AT&T Samsung Galaxy Note 4] DeathLord..:
I have dg'd to kitkat and ready for the release from gatesjunior and team so ready for this. :)
[AT&T Samsung Galaxy Note 4] youshady2:
Is there a video of the process yet I'm tempted to try but I'm not sure I fully know how to do every step like choose what format to petition my SD card is there an app for that ?
[AT&T Samsung Galaxy Note 4] Bicknasty:
You should avoid attempting to do anything until gatesjunior's team releases a working superSU installation method.
[AT&T Samsung Galaxy Note 4] Vindicated777:
I don't believe it has been released yet.
[AT&T Samsung Galaxy Note 4] StayingSober:
Someone correct me if I'm wrong please, but I believe you are mixing up the current root method from [MENTION=3178012]gatesjunior[/MENTION] and his team, with the rooted lollipop MultiSystem method from [MENTION=5868929]hsbadr[/MENTION]
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
What are the requirements for MultiSystem? I just know it doesn't currently work for Verizon Retail phones.
[AT&T Samsung Galaxy Note 4] StayingSober:
http://xdaforums.com/showthread.php?t=3103739
[AT&T Samsung Galaxy Note 4] youshady2:
Oh you are correct I am mistaking the two I thought I saw a bunch of posts saying he got it working with super user and softboot being stable can someone post a link to the two so I can read through them and what's the difference between the two I though we had a temp root that can be used with superuser as long as we don't reboot?
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
So translation:

MultiSystem: Root Not required

Both Root & Multisystem: basically both have a problem with the locked bootloader sending a flag to the kernel, enabling write protections on system and other partitions on the retail editions, thus disabling functionality at reboots.

Correct?
[AT&T Samsung Galaxy Note 4] TYMO68:
Thks [MENTION=2698170]gatesj[/MENTION]r. but I'd rather just wait and be patient until a method for Lollipop comes available. I certainly miss root but I have the faith in devs like you that soon enough there will be a root method made available for Lollipop. As for Kingroot on Lollipop, I am not sure if it had been achieved yet......does anyone know?
[AT&T Samsung Galaxy Note 4] waco2hot33:
Nope!! not as of yet many tried but it conks out at 51% and reboots every time
[AT&T Samsung Galaxy Note 4] TYMO68:
Arrrrggh!!! I guess until then....... Stay Tuned :P
[AT&T Samsung Galaxy Note 4] reydarz:
Did the same thing on NIE using ART for me so it may not be their exploits but their deployment of them.
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
Does anyone know, does this happen on just our devices or does it happen on other devices?
[AT&T Samsung Galaxy Note 4] DeathLord..:
Using kingroot on lollipop will do nothing at all. Clearly shows only workin on kitkat.

I hope that helps.
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
OK, but have you seen Kingroot do nothing on other phones (NOT the Galaxy Note 4) with Lolipop?
[AT&T Samsung Galaxy Note 4] DeathLord..:
I must apologize. I must say no I have not.
[AT&T Samsung Galaxy Note 4] youshady2:
King root does work on lollipop I rooted both my tablets that are on lollipop with king root there is also a English version availble
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
OK so THAT is what I was looking for. Lolipop doesn't fully patch any sort of exploit used by KingRoot but something obviously breaks when it comes to Lolipop on the Note 4.

Here's a thought...if someone can or wouldn't mind trying this for me...granted it may be stupid. Turn off Fast Charging and see what happens, if you're forced to reboot. I seem to remember something about Fast Charging and 50%, 51% seems close enough. Correct me if I'm wrong, but isn't Fast Charging only currently supported on the Note 4 and probably not on those tablets that you speak of?
[AT&T Samsung Galaxy Note 4] Randolph17:
blocking lollipop update

I am sorry if this is a stupid question. But can somebody help me? I use the gatesjunior debloater, but I am not sure what the files are to block the OTA update.

Thank you.
[AT&T Samsung Galaxy Note 4] IceTwig:
Try These
[AT&T Samsung Galaxy Note 4] elliwigy:
its sdm.apk
[AT&T Samsung Galaxy Note 4] youshady2:
I think it's write protection and the locked bootloader that Verizon and Samsung implemented so it will work on most lollipop just not our note 4 Verizon it even worked on the s6 wich just came out
[AT&T Samsung Galaxy Note 4] ODSTZ3RO:
So will this possibly be today?
[AT&T Samsung Galaxy Note 4] Randolph17:
blocking lollipop update

Thank you. This is exactly what I need.
[AT&T Samsung Galaxy Note 4] waco2hot33:
No ETA's please !! Work is in progress just hold your horses young grasshopper!![emoji106]?
[AT&T Samsung Galaxy Note 4] Dudmaster:
If you can get deleted apps to stay deleted on reboot, is it possible to install SuperSU as a system app and get it to stay permanently rooted?
[AT&T Samsung Galaxy Note 4] soraxd:
well way to show up in the club like ..

[br]

sooo ima be that dude[/] and bring up that bounty. Kingroot team (person?) discovered this exploit? well at least they were the first to implement it for our phone. it's not a permanent root, and there's also that pulling from their server thing, so they never actually 'released' it. gatesballer did his gates thing and RE'd it with his team. and then there's the fact that it's not actually a permanent root. soo community, it's your money, what you guys feeling on this?

mmm if i had dat temproot booting up all on its own where it just does its own thing and i dont even gotta think about it, man thats where its at for me right there. ima gonna be a happy note4 owner.

and I'm feelin I wanna split up my $50 pledge 25 Kingroot, 25 gates team if they can get it running behind the scenes at boot.
[AT&T Samsung Galaxy Note 4] cstayton:
no a reboot will remove root, the package they are working on will only replace kingroot with supersu the root is still just a temp root. a hot boot just restarts the shell and UI not the whole system.
[AT&T Samsung Galaxy Note 4] soraxd:
hshsjsjdhjsjshajaj jsh
[AT&T Samsung Galaxy Note 4] cstayton:
Well IMHO, Temp root only allows for minimal control and modifications (none of which stick after a reboot) should not count. We need full root so that mods and roms can be created and successfully implemented. Just my opinion