yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note 4] ZPaul2Fresh8:
I don't know how else to explain it. Read up. [MENTION=5868929]hsbadr[/MENTION] is testing his stuff on retail Verizon models right now. To use this on AT&T all we need is to change the rooted image to an AT&T he will be releasing. It's not a 1-click root by any means, but it's definitely good for me!
[AT&T Samsung Galaxy Note 4] MaStA819:
Because non-devs kept posting stupid questions in that thread so the mods got pissed and closed it down after giving a ton of warnings.
[AT&T Samsung Galaxy Note 4] ODSTZ3RO:
Has anyone gotten root on at&t yet?
[AT&T Samsung Galaxy Note 4] mattism78:
Did you even bother to read previous posts?
[AT&T Samsung Galaxy Note 4] yeswap:
I probably did this all wrong but I got BBS working. What did was:

Copied BetterBatteryStats_xdaedition_2.0.0.0.apk to /system/priv-app using Root Explorer

Set permissions to 0644

Tapped the apk in Root Explorer to install it

Ran BBS it said it needed to install as a system app so I let it do so which appeared to succeed and told me to reboot

Rebooted, reran King Root

Launched BBS, it again needed to install as a system app which succeeded.

Did not reboot when prompted. Instead exited and restarted BBS and it works
[AT&T Samsung Galaxy Note 4] elliwigy:
nice contribution to the root progress lol

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

glad you got it working.. usually you move bbs apk to system priv app and set perms to 0755 and reboot
[AT&T Samsung Galaxy Note 4] raynan:
Hell, even if it means typing in lines of shell scripts, I'm OK with it.
[AT&T Samsung Galaxy Note 4] ODSTZ3RO:
Oooo crap I thought it was the root waiting thread thanks for the heads up. yeah ,I did read what he said ,but merely skimmed over it sorry for being human and making a mistake. I only mentioned that since someone is trying it on at&t. I thought someone had already done it before him.
[AT&T Samsung Galaxy Note 4] Android.Ninja:
Using this method grants you "Temporary Root" until you reboot.

Working with Yokyo and team to see if we can find a more permanent root method.

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:
If you knew the vonerabilities they used could u not use them to build. An apk that could use supersu instead of Kingusers so it would be a permanent instead of temporary

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] elliwigy:
what happened to what you guys were working on and trying to implement?
[AT&T Samsung Galaxy Note 4] Android.Ninja:
I believe it would depend but thanks for the idea. If you don't mind, I'm going to pass your info over to Yokyo and see what she thinks. You might be on to something. Thanks!

Developers don't need no stinkin' signature!

If I've been able to help you, please hit the "Thanks" button. ;)

---------- Post added at 11:54 PM ---------- Previous post was at 11:51 PM ----------

Yokyo is still working on a way to get root to stick permanently. She said that she believes she knows why root is not staying after the reboots. Hopefully she will give me something to work with so we can get a permanent root.

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:
Thanks for the reply I'm not so good with the system stuff just a themer but just thought I'd throw out an idea hope you guys come up with something we apriciate you guys not giving up

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] freddy0872:
-1
[AT&T Samsung Galaxy Note 4] FiniteTime:
Has anyone tried doing Kingroot, then doing:

su
mount -o remount,rw rootfs
mount -o remount,rw /system

Then put su in /system/bin and /system/bin?

Got the idea from the instructions here: http://xdaforums.com/note-4-verizon/development/root-stock-rooted-lollipop-retail-t3103739

Might be a permaroot.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
That still won't give us the binary we need to get superuser to work as far as I know

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] freddy0872:
Yea tried that a few different ways last night. Ended up with a Custom logo on boot up at one point lol.

It wanted to work but binaries just simply wont work as [MENTION=5808364]jolly_roger_hook[/MENTION] stated.

Then phone got all sorts of unstable. Froze randomly. Rebooted on me. So that was the end of that
[AT&T Samsung Galaxy Note 4] FiniteTime:
Actually just saw this message at the top of that post I linked:

So if the device controller is enforcing the write protection then you'd need to flash something. I hope a prerooted NK3 4.4.4 KitKat would work.
[AT&T Samsung Galaxy Note 4] elliwigy:
but the Bootloader is telling the controller to enforce write protection which is locked.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
I think the only way we could do this is if we found a way to get the su binary installed manually without the use of an app

You are correct but it seems we have the ability to write to system areas with use of programs like root Explorer so like I said we would have to install su binary manually to wherever it goes in the system partition

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] elliwigy:
not to burst your bubble but im sure hsbadr and others already tried that and were not successful.. if this was the case then no one would be talking about it since its very easy to manually push su binaries otherwise
[AT&T Samsung Galaxy Note 4] brewmeister:
my thoughts exactly. i believe he (android.ninja) claimed to have a perm root method before this kingroot came out and was working on packaging an apk for it.
[AT&T Samsung Galaxy Note 4] KennyG123:
No. He specifically stated he had no root and working on the delivery method apk for when it was achieved. So now they have something to work with at least.

As far as writes to system are concerned has anyone tried this in terminal?

SU

restorecon -FR /data/media/0

It worked for write problems on my LG G3. But I had to enter the restorecon line twice in a row.
[AT&T Samsung Galaxy Note 4] SacrificedWalrus:
Running root commands without KingUser

So I have found a few quite interesting things while messing around with this device. So after I ran kingroot, I opened up a shell with ADB and ran the su command (same works with Android Terminal) and than uninstalled KingUser and that other app that comes with it. I was still able to run commands as root from the shell. From there I changed permissions of the /data folder, the /sys folder, the /system folder, and a few other subfolders in those. I was able to modify those folders from an ADB shell without running su, but I was not able to modify them with Root Browser or ES File Explorer. I tried pushing supersu into the /system folder, and that worked. When I opened up Root Browser, the system crashed and rebooted. On the first boot up screen where it says "Galaxy Note 4" and "Powered by Android" there was a new symbol. It was a padlock that said "Custom" underneath it. On other devices, that usually means that the bootloader is unlocked and the system has been modified. I am running the AT&T variant, which has a locked bootloader so this was very interesting. When the boot completed, all the system folder permissions were back to normal and root was gone. But I am still wondering exactly what the padlock meant, and if I reboot my phone now its gone. If it meant that the bootloader was (temporarily) unlocked, do you think we could boot into recovery and flash a custom recovery or something of that matter? I am fairly new to this, and honestly I was just messing around with this to see what would happen. Maybe all of this means nothing, but I just thought I would share it so that someone with more experience may be able to give me and the community some insight on it. Let me know what you all think.
[AT&T Samsung Galaxy Note 4] blue5055:
First off I'm super excited to see real progress toward root. Round of applause to everyone working so hard.

I do have a question: with the temp root if u perform root actions (block ads, change status bar icons, titanium backup, etc) then reboot & lose root will those root actions stick or do they revert back?
[AT&T Samsung Galaxy Note 4] SacrificedWalrus:
All those actions revert back. I've even tried deleting system apps (ex. Evernote) and after a reboot it somehow comes back. Not sure how it does that, I would think there has to be a copy of the file stored on the device somewhere, but I'm not sure.
[AT&T Samsung Galaxy Note 4] scarygood536:
Because the write protection doesn't allow any changes to stick. That's also why you lose root after every reboot
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
Padlock means nothing as of right now it never ment an unlocked bootloader we had the Padlock in note three just Means system has been modified

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] SacrificedWalrus:
I see. Well at that point wouldn't that mean that the permissions that I set are still in place? If so that would mean that we would be able to modify the /system folder and the others I set without root, although I'm not entirely sure how we would modify the files/folders before the system boots.
[AT&T Samsung Galaxy Note 4] tampaboy1984:
Tried kingroot on At&t Note 4 and it sticks at 51% then reboot itself and then this pops up when I try kingroot again
[AT&T Samsung Galaxy Note 4] Xak:
I think everyone is excited. I personally can't wait with or without rom's I personally miss roms / the capability to flash them because I haven't compiled in a while last phone that I compiled for was the HTC One X AT&T. When the Note 4 AT&T is rooted I plan on compiling Cyanogen / AOSP based roms. I was the first person to bring AOKP 4.4.2 to the HTC One X and nightlies so I do have experience. I dismantled my project on that though because I was just starting college and now I am more time managed so will be able to.
[AT&T Samsung Galaxy Note 4] DeathLord..:
What's is the pop up?

I tried King root nothing happened at 51%. Just stops. I researched the site and it only shows working on Kit Kat.
[AT&T Samsung Galaxy Note 4] scarygood536:
If you're on lollipop that's the problem. The pop up is telling you root failed. If you're not on lollipop try running it again
[AT&T Samsung Galaxy Note 4] DeathLord..:
Let's hope Android.Ninja and his DEV partner can get a permanent root fix.
[AT&T Samsung Galaxy Note 4] phobia09:
Not necessarily. Galaxy S5's and other Samsung variants would show the "custom" padlock for the silliest reasons ranging from, yes, root to simply switching from DALVIK to ART in KK.
[AT&T Samsung Galaxy Note 4] Orito:
No go. Looks like restorecon no longer has the -F function... However, with it essentially being force, I dropped it and ran restorecon -R /data/media/0. Unfortunately, root did not stick after a reboot.
[AT&T Samsung Galaxy Note 4] DeathLord..:
If this sound dumb I can understand and if it needs deleted please do. But has one thought to unpack the Kingroot .exe and see if the binary for Supersu can be written in or do a comparison of a non rooted ATT galaxy note 4 vs. Rooted ATT galaxy NOTE 4 to see if the coding files are different some where then in turn locating the odd file to force permanent root.
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
I believe that I read somewhere that that's already been attempted.
[AT&T Samsung Galaxy Note 4] GabrielOspina:
Its like people ask the same question or try to figure out the same s**t over and over again
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
There's another thread where you might be able to get some cheese with your whine...not here.
[AT&T Samsung Galaxy Note 4] elliwigy:
i also thought this was not the thread for "ideas" that have already been discussed and dont work many times either.
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
It is...I come here to read those ideas, sorry. He was just complaining, which doesn't help anyone. At least, that's how I read it.
[AT&T Samsung Galaxy Note 4] elliwigy:
well him and others im sure felt that way about the idea posted lol. not trying to cheese anyone but i can see why he commented in that way.. its been discussed more than once.. heck the exploit and king user arent even in the kingroot apk lol decompiling it will help with nothing.

i just figured that stuff should go in the off topic room as this should be for devs who are updating the rest of the users on their progress (now id assume on trying to get past the write protection) and not for randoms ideas that make no sense or have already been attempted.
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
Agreed, hence the cheese and "whine" comment, but I felt that I was clear when I'd stated that I believe I'd seen that before. No need for others to attack others for ideas that seem "stupid" to them or have been said before. Whatever happened to being cordial? I know we're all chomping at the bit to get root, but still. I've said enough on this and won't be replying again to this particular matter. I'm no moderator, but it belongs in the waiting room.
[AT&T Samsung Galaxy Note 4] DeathLord..:
I do apologize to all. I shall remove myself from the subject. I shall remain silent till someone is intelligent enough to help make this happen and not degrade or demean others.
[AT&T Samsung Galaxy Note 4] KennyG123:
We know about root not sticking...but did this give you write access after without rebooting?
[AT&T Samsung Galaxy Note 4] Kyuta Syuko:
It's sounds to me like the issue isn't not being able to write to /system but the changes made being reverted on boot. Hence why some have seen the custom padlock on initial reboot but not on any boots following.
[AT&T Samsung Galaxy Note 4] BRIMS7ON3:
Question... In a developer thread that now I can't seem to find, the thread was closed because he said root was accomplished.. Yet I cannot find anything that works. Any idea what that was about?
[AT&T Samsung Galaxy Note 4] CJ74753:
Root has been achieved via KingRoot. Root does not stick after reboot though. Developers are working on this to make root stick permanently.
[AT&T Samsung Galaxy Note 4] greyhulk:
Yeah, I just tried this. Had everything working, including Adaway. Rebooted after installing App Ops to the system folder and everything reset. Pretty frustrating. So close. I was about to sell my Note 4, too and now I'm wondering if I should hold onto it.

Edit: Aaaaand my phone now reboots itself after a few minutes being rooted (3 times now), so this won't even work as a temporary root method for now. Good grief.
[AT&T Samsung Galaxy Note 4] BRIMS7ON3:
I know...I used it, got all my apps installed, but then took the OTA for lollipop, and now root does not work at all. I guess my question is, why would that thread be closed if there was no permanent solution found for lollipop?
[AT&T Samsung Galaxy Note 4] CJ74753:
Possible progress?

http://xdaforums.com/showpost.php?p=60640937&postcount=185

Not sure if it's worth much but messing around with TB, freezing all apps will result in a boot loop. If this is the case then wouldn't it be more than likely it's one of the system apps that restores the apps and kicks root out or am I missing something? Considering it didn't revert all of the changes and now I have a boot loop? Does anyone know the bare minimum system apps that need to run in order for the phone to boot up?
[AT&T Samsung Galaxy Note 4] elliwigy:
not sure what debloating has to do with root progress lol
[AT&T Samsung Galaxy Note 4] K-alz:
Thread was closed because some don't wanna stick to the rules. Some users kept posting in the thread and it's for developers only. Mods warned several times, but no one stuck to the rules.
[AT&T Samsung Galaxy Note 4] CJ74753:
What I meant is it seems that some app is reverting all the changes that are made. Kind of like how the program "Deep Freeze" is used on personal computers to keep users from making adjustments to any settings, at the end of the day when they restart everything that was done is gone. Was just a thought, I apologize if it is complete nonsense.
[AT&T Samsung Galaxy Note 4] blue5055:
Not sure if this has been tried or mentioned before, just trying to help anyway I can.

Once root has been granted, has anyone removed or tried to remove Knox files & apps associated with it? Just thinking Knox may preventing or reverting changes made to the system files
[AT&T Samsung Galaxy Note 4] cstayton:
Ok let's see if I can explain this so it makes sense.

Consider those devices out there that have locked bootloaders but are able to root, you ca nview the root partition and even adb push files to it/edit existing files etc. yet when you reboot the device everything is back to stock. The way this works i s handle by the BL the main /rootfs partition is copied into a memory location (Not run from the partition itself) so what you are changing is the files in the root memory location not the root partition (This is a common practice even with some unix/linux installs)

the same (Apparently) set of circumstances are likely in play for us here on the note 4, your obtaining root editing, debloating, modifiying etc. yet once you reboot all original OEM is restored. (Without the ability permaroot i can't confirm this 100%) but it does appear to be the scenario as it would also explain the loss of root on reboot.
[AT&T Samsung Galaxy Note 4] KennyG123:
The development thread was to collaborate amongst developers to attain root. Temp root was achieved. Instead of the thread being used by developers to find a permanent root solution it became Q&A by non-devs. As posted in that thread if any developers need it reopened to collaborate they can PM me.
[AT&T Samsung Galaxy Note 4] raynan:
Just to clarify (sorry if it's redundant); the changes you make on a temp root are saved to the RAM of the device which would get cleared upon loss of power to the hardware?
[AT&T Samsung Galaxy Note 4] chronicaust:
So a couple questions we could ask are:

1. Where exactly is the rootfs stored on the disk? Is it accessible from within Android?

And

2. Could we somehow capture the root exploit as it is being run, and schedule it to run on every boot? If we can do that then it's really just a matter of increasing stability and fixing the random reboots we seem to be getting, which I'd say are likely to be coming from all the Chinese software on the phone. Kingoroot has always made my phones act strangely until I got SuperSU installed.
[AT&T Samsung Galaxy Note 4] BRIMS7ON3:
No..
[AT&T Samsung Galaxy Note 4] cstayton:
essentially that is how it would work, Keep in mind this is just one theory that could explain the dificulties with maintaining root and with the large number of reports of apps and system partition returning to stock even thos apks were deleted.
[AT&T Samsung Galaxy Note 4] raynan:
"The way this works i s handle by the BL the main /rootfs partition is copied into a memory location" is where I got that idea from...is it then a temporary location?
[AT&T Samsung Galaxy Note 4] cstayton:
yes it is a temporary location.. like i tried to explain the boot or root files are copied to ram and executed from there thats why you can modifiy/edit/delete files from "/" and have the changes be gone when you reboot.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
With I phone they used to have a tethered jailbreak would it be possible to do a tethered root it's not practical but if it would work

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] CJ74753:
Digging around trying to understand Samsung's rootfs I found this about the Samsung Epic 4G http://xdaforums.com/showpost.php?p=12323553&postcount=4 Developer mkasick stated "However, the root filesystem is actually a ram disk (initramfs), so any changes to it aren't persistent across reboots. You can modify the initramfs, but it requires rebuilding it and packaging it with a kernel, and flashing the kernel containing the new initramfs." Does this apply to our Note 4?
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
Locked bootloader means no custom kernels so no It does not and a small search would have answered that for you

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] houch80:
The locked bootloader sends a flag to ufs controller to write protect partitions including system. There are developers investigating a workaround to remove write protection but it may take a long time and is not guaranteed to work.
[AT&T Samsung Galaxy Note 4] cstayton:
1. rootfs is stored in one of the mmcblk** partitions and no it is not accessible from within android (Locked BL Prevents this)

2. Unfortunately no that can't be done it would require the ability to have init.d support which you can't setup unless you have root.
[AT&T Samsung Galaxy Note 4] Orito:
Not sure what I should be looking at, but I have write to system...
[AT&T Samsung Galaxy Note 4] elliwigy:
if you dont know what youre looking at how do you know if you have write to system? can others confirm?
[AT&T Samsung Galaxy Note 4] liquidaluminum:
A tethered jailbreak meant that the phone lost root every time it was powered down. The tethering part came in when you had to reconnect the device and run root again after a fresh reboot.

This root is more or less the same thing.
[AT&T Samsung Galaxy Note 4] Orito:
Just because he didn't mention what to look at, doesn't mean I don't know how.
[AT&T Samsung Galaxy Note 4] nemopsp:
Coming from iPhone, I understand what you talking about, but I say it's less, since most everything involves reboot and with the bootloader write protection, every reboot everything resets. Where as in tethered jailbreak, once rebooted an rejailbroke, you still had everything
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
That's what I'm saying maybe with something tethered we can retain root somehow

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] liquidaluminum:
I had an iPhone for several years as well. The release for tethered jailbreak was on the iPhone 4. I'm sure there have probably been others, but that's the last model I ever had a hands on experience with.

The tethered jailbreak for it was one of Geohot's Rain releases. None of the changes took hold after reboot. The only thing that would still stay on the device were actual applications. Even though Cydia had been installed and even manually updated with new repos, the app along with any app that required root immediately lost all functionality as soon as the device rebooted. Tethering doesn't make anything "stick" it just means that it's a temp jailbreak that requires reconnect every reboot.

If anyone is worried about changes being permanent, I would recommend using TB to just completely uninstall any app that's being frozen, unless it's a mandatory system app that would require some sort of substitution. Essentially just delete any bloatware to make those certain changes stick until a definitive and permanent root is achieved.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
Even the titanium backup changes don't stick anything you unistall or freeze reverts on next boot

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] reydarz:
How do you suggest using TB to remove apps while system is read only?
[AT&T Samsung Galaxy Note 4] liquidaluminum:
I'm not sure how to respond to this, because TB works just fine for me for deletion purposes. Anything I've deleted hasn't come back after reboot. The phone doesn't automatically start downloading system apps that were built into the factory apk.

I've successfully deleted several items that stayed deleted after reboot. Anything I froze obviously became unfrozen, but anything I perma-deleted is gone and I no longer have update notices for them in the play store.

---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------

Meant to say ROM instead of apk. Sorry about that.
[AT&T Samsung Galaxy Note 4] reydarz:
That's interesting on my system I've found the opposite, everything I froze still shows as disabled upon reboot but no system changes stick
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
I deleted files such as kindle and the audio book program and they are still there after a reboot

Sent From The EDGE