yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note 4] Kyuta Syuko:
If someone can point me to a tutorial on how to get these I can supply them from my AT&T Note 4 on the C4 firmware (still hopeful for Lollipop root). This is what I got from the build.prop:

ro.build.fingerprint=samsung/trlteuc/trlteatt:5.0.1/LRX22C/N910AUCU1COC4:user/release-keys
[AT&T Samsung Galaxy Note 4] DeathLord..:
Lol. :D
[AT&T Samsung Galaxy Note 4] SageChrono:
Right. 5.0+ isn't kitkat, which it does work no problem on 4.4 but king root thread stated worked on 5.0+ as well, which lead me to try. Clearing anything doesn't apply
[AT&T Samsung Galaxy Note 4] Surge1223:
This might only be relevant for n910a users but I recommend (--read request) that all users email samsung and ask for lollipop kernel source to be posted for 910a by following this http://xdaforums.com/galaxy-s4-verizon/general/lollipop-kernel-source-request-gpl-t3117226 but using SM-n910a as model number instead of SCH-i545 obviously.

Thanks
[AT&T Samsung Galaxy Note 4] patt2k:
Does that even work do they care?
[AT&T Samsung Galaxy Note 4] reydarz:
Legally they have to
[AT&T Samsung Galaxy Note 4] heXacode:
Why for Lollipop? Shouldn't we be asking for the one used for 4.4.4 KK? Or is there a source dropped already? I actually went looking for the kernel source for 4.4.4 for my research but found none. Just curious as to why Lollipop... or we could ask for source for both version?
[AT&T Samsung Galaxy Note 4] ThePublisher:
I submitted my request. I hope everyone else will also.
[AT&T Samsung Galaxy Note 4] Surge1223:
KK source is up, but I'm asking for lollipop because if we're going to attempt the module route of bypassing dm-verity then we need the lollipop kernel source. Also it's just annoying that US variants don't get lollipop kernel source posted in a reasonable amount of time.
[AT&T Samsung Galaxy Note 4] eklipz3:
I have the n910v so I will do it for that one just in case.

Sent from my VS985 4G
[AT&T Samsung Galaxy Note 4] DeathLord..:
I have submitted.
[AT&T Samsung Galaxy Note 4] heXacode:
Understandable. Could you point me to the 4.4.4 kernel source? I have no idea why it's difficult to find. Might be because it's the first time I'm searching for such thing and have no idea where they keep them.
[AT&T Samsung Galaxy Note 4] CJ74753:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-n910a is this what you're looking for?
[AT&T Samsung Galaxy Note 4] zxz0O0:
Write-protection is not dm-verity's job so what's exactly the point of bypassing dm-verity?
[AT&T Samsung Galaxy Note 4] stillthisguy:
Verizon Lollipop kernel source is already available.
[AT&T Samsung Galaxy Note 4] jcradio:
Lollipop Open Source is Up

opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-n910v

---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------

Lollipop Open Source is Up

opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-n910v
[AT&T Samsung Galaxy Note 4] patt2k:
hey guys a noob question from me but how does the open source kernel source/s help us in anything? does this only benefit DEV editions or retails as well? thank you.
[AT&T Samsung Galaxy Note 4] Bicknasty:
I would guess the most helpful thing about it is that it enables developers to scour for security holes.
[AT&T Samsung Galaxy Note 4] heXacode:
That's the one. Thank you.
[AT&T Samsung Galaxy Note 4] patt2k:
If you need a mirror somewhere samsung site was kind of slow I downloaded it even though I have no idea what it's used for but just in case someone ever needs it :D
[AT&T Samsung Galaxy Note 4] jo4mvp24:
Sorry for the ignorance but I've been up and down this thread looking for the link to block my note 4 from updating to LP and no luck so can someone please provide a link or point me in the right direction. ...thanks :)
[AT&T Samsung Galaxy Note 4] IceTwig:
Try other threads besides this one
[AT&T Samsung Galaxy Note 4] elliwigy:
sdm.apk
[AT&T Samsung Galaxy Note 4] heXacode:
I actually got it just fine. Thank you though.
[AT&T Samsung Galaxy Note 4] SacrificedWalrus:
Has anyone tried mounting and editing the /dev/block/mmcblk0p17 (boot partition)? I haven't been able to mount it myself, I've tried mounting as ext4, exFAT, ext2, and vfat but I keep getting a "Invalid Argument" error. Would editing this file get us anywhere? I'm assuming that we could disable dm-verity from here. Its risky but it may just work.
[AT&T Samsung Galaxy Note 4] tekjester:
DMVerify runs on startup within the protected bootloader. Need to survive that check for root to stick beyond reboot.
[AT&T Samsung Galaxy Note 4] psyciatrichelp:
If its the boot partition it should be fat or or ext2 or ext3. I have tried mounting several partitions but only able to do a couple so far. But i will keep trying.
[AT&T Samsung Galaxy Note 4] PaulPizz:
Forgive me if I'm wrong but isn't it in a .raw format in the device?
[AT&T Samsung Galaxy Note 4] psyciatrichelp:
The initial boot. On pc its bios/eufi is raw data. That tells the device what to look for. Boot data at the beginning of a partition. For windows this is a 100mb fat32 partition. Every linux distro i have used so far has given me 3 or 5 options of how to format /boot. Ext2 ext3 fat fat32.
[AT&T Samsung Galaxy Note 4] Venom0642:
Like i said few post back, most likely the Note 5 AT&T will get root as fast as SG6 AT&T did , one cause it will be 64 bit Hardware, i am pretty sure it will get root fast, Also it will probably come with Android M 6.0 think name is Muffin, Anyway back to topic let's not give up on root for Note 4 tho pretty sure it will happen.

Running On New Deadly Venom Note 4 v3.0
[AT&T Samsung Galaxy Note 4] kirewade:
Is anyone even working on root or everyone given up? I haven't heard much from the people who was working on it
[AT&T Samsung Galaxy Note 4] JChespirito24:
It's only been like 3 hours since gatesjunior has posted about it O.O
[AT&T Samsung Galaxy Note 4] CJ74753:
Samsung just uploaded the Lollipop source for AT&T Note 4. http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-n910a
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
I'm noticing something similar for the Verizon variant, just by searching "SM-N910V", but it appears to be "SM-910V_NA", not sure if that makes a difference. What would this do for anyone?
[AT&T Samsung Galaxy Note 4] CJ74753:
I believe the Verizon Note 4 Lollipop source had been posted beforehand. Samsung just finally posted the AT&T version. NA I believe is just for North American. The source information I think will let the devs dig into the code and possibly find a bug to exploit...if I understand things correctly.
[AT&T Samsung Galaxy Note 4] ThePublisher:
Got this email from Samsung this morning. Looks like the early risers beat me to posting it. Does this help us out?

--------------------------

Dear Customer,

We are pleased to provide you the OC2 source code of SM-N910A_NA.

You can download the source code from the site below: http://opensource.samsung.com

Thank you.

Sincerely yours,
[AT&T Samsung Galaxy Note 4] Venom0642:
Yes someone posted it already.

Running On New Deadly Venom Note 4 v3.0
[AT&T Samsung Galaxy Note 4] LordFergus:
I just got an update to kingroot. Anyone try it yet? It got to 35% before crashing with lollipop, and before it was more like 6%, so I'm a bit hopeful.
[AT&T Samsung Galaxy Note 4] Chad_Petree:
But does the exploit affect all 6 bit devices or only exynos 64 bit cpus? I on't think samsung will use the samsung cpu found on the s6 for the Note 5
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
Do you mean, before, your phone would crash after your phone drained BY 6% or DOWN TO 6%? And also, do you mean drained BY 35% or DOWN TO 35%?
[AT&T Samsung Galaxy Note 4] LordFergus:
Sorry for not specifying! I meant root progress. Before I updated, it would detect my phone, then fail. This time, it went all the way to 35%, trying to root the phone before it crashed. However, (the 6% was a poor estimate) it went to 15% and it said root failed. With it moving a step ahead on lollipop, I was hopeful that maybe they fixed the kitkat root, so I'm hoping someone tries it when they get the update.
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
Still confused. Check your PMs.
[AT&T Samsung Galaxy Note 4] Venom0642:
What's this ? Your off topic.

Running On New Deadly Venom Note 4 v3.0
[AT&T Samsung Galaxy Note 4] patt2k:
My verizon note4 with newer version posted on May 22 would go to 52% previous version 51% then phone reboots.

So guys did the source codes become any useful to any devs here?
[AT&T Samsung Galaxy Note 4] siriom:
Are you on 4.4.4 ?
[AT&T Samsung Galaxy Note 4] patt2k:
LP
[AT&T Samsung Galaxy Note 4] siriom:
Downgrade to 4.4.4 and you should be fine.
[AT&T Samsung Galaxy Note 4] patt2k:
I did sometime ago and went back to LP whenever root is perma I will downgrade for sure.
[AT&T Samsung Galaxy Note 4] siriom:
Kingroot was updated to version 4.1029 couple of days ago. I asked if root was perm and working on edge and people had a ***** fit over me simply asking....

Figure if it was perm i woulda heard something by now.

There are 2 other apps floating about vroot and Kingoroot but i figure they are only working with 4.4.4 as well and like you im on LP atm.
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
So the update made things worse by 1%?
[AT&T Samsung Galaxy Note 4] gatesjunior:
Update..

Well, we are now able to get permissive mode instead of enforced on system for SeLinux. Yes, a reboot will put it back, but we are continuing to work on it.
[AT&T Samsung Galaxy Note 4] liquidaluminum:
What is there to be confused about? He tried to run root on Lollipop and initially got to 6% complete before his phone crashed. After Kingroot updated, he tried root on Lollipop again and got to 35% complete before crashing again.
[AT&T Samsung Galaxy Note 4] kirewade:
Gates junior what is the difference between the two
[AT&T Samsung Galaxy Note 4] Xak:
Good work so far [MENTION=3178012]gatesjunior[/MENTION] please continue to keep us updated! I'm pretty sure most of us at this point don't care if it's an unconventional method. Heck even the noobs would be fine with a tutorial video and having to copy and paste the code line by line.
[AT&T Samsung Galaxy Note 4] FiniteTime:
Wow! That's great!! There was that tool that Surge suggested for writing memory, very short C program, I wonder if writes to memory are possible?

No idea where the read-only setting is, but changing it in memory then it should be good to go (I think?)

Great progress!!
[AT&T Samsung Galaxy Note 4] siriom:
I find it odd that thats even possible.

Back on my note 3 , getting permissive would mean tripping knox cos you'd need to flash a kernel.
[AT&T Samsung Galaxy Note 4] elliwigy:
on vzw note 3 hsbadr made a easy tut on how to do it with a locked BL that didnt trip knox at all..

not sure what note 3 you had lol
[AT&T Samsung Galaxy Note 4] patt2k:
when you run kingroot it shows progress bar if it achieved root or not,on LP I would have it go to 51%,with newer version it froze on 52%.
[AT&T Samsung Galaxy Note 4] siriom:
Anyone try vroot or kingoroot ?
[AT&T Samsung Galaxy Note 4] cstayton:
iroot uses the kingroot methods so although it may root it would still be a temp root
[AT&T Samsung Galaxy Note 4] gatesjunior:
It does not trip Knox. Trust me, I have even flashed TWRP to recovery, flashed a different kernel, none of which Trips Knox. It won't boot, but it does not trip Knox when restoring back the original and looking at the flags, nothing is tripped.
[AT&T Samsung Galaxy Note 4] elliwigy:
would the permissive SELinux work on a s6 edge? or is it specific to the note 4?
[AT&T Samsung Galaxy Note 4] heXacode:
I'll leave this here...

http://nelenkov.blogspot.com/2014/05/using-kitkat-verified-boot.html?m=1

This article/tutorial will benefit to those who are wondering why root is only temporary and what must be done to disable dm-verity.
[AT&T Samsung Galaxy Note 4] eklipz3:
This is reminding me of c++ and so, you know jump if equal or jump if not equal stuff, might be wrong but reading the article is bringing back memories.

Sent from my VS985 4G
[AT&T Samsung Galaxy Note 4] heXacode:
In a way yeah.

Since the article talks about enabling dm_verity, by creating a hash tree, CONFIG_DM_VERITY becomes established. This means the enable/disable switch is created if DM_VERITY wasn't enabled, or used, to begin with.

DM_VERITY seems to exist only on the Note 4 from what I'm finding out. The S6 doesn't have this. Why? It's for experimental purposes between Samsung and the OEMs to filter through and block out root kits or anything modified like system partition which will result in an I/O error in the blocks and not allow it to be used. When that block produces errors then a flag is thrown and the block becomes untrusted therefore changes are reversed to the way it was before modifications (i.e. temp root, modifying stuff on system partition, deleting system apps, etc).This is why it's relatively new and no surefire way has been presented to get around it just yet. DM_VERITY only exist on 4.4.+ versions and not on 5.0.1 from what I read.

So with DM_VERITY enabled then CONFIG_DM_VERITY is suppose to be established. I haven't dug into it to see if it is there but I'm going by what the article says. Therefore it shouldn't be too difficult to disable it. It does not explain reversing everything to disable DM_VERITY but to my understanding, the hash tree is already created and DM_VERITY is enabled which I presume the first half of the tutorial wouldn't be beneficial in needing to disable it.

I'm still looking into this.
[AT&T Samsung Galaxy Note 4] elliwigy:
are you sure dm verity is only on note 4?

These are pictures of my recovery on my g925v...
[AT&T Samsung Galaxy Note 4] heXacode:
I'm guessing that's the S6 Edge? I just read that DM_VERITY isn't on the S6 and S6 Edge from another article. Are you permanently rooted on that device?
[AT&T Samsung Galaxy Note 4] elliwigy:
yup.. vzw s6 edge.. i noticed dm verity off the bat when i went to recovery.. it is perm rooted with ping pong root.. im on my own extreme syndicate rom.

flashfire works lol.

att s6 edge also perm rooted.

my t807v (vzw galaxy tab s 10.5) is snapdragon processor but doesnt have dm verity.

from the read, dm verity can be used for many things so maybe they got rid of the WP on the s6 and s6 edge but use other dm verity stuff? either way, it says dm verity failed since i rooted but doesnt affect anything at all so far lol
[AT&T Samsung Galaxy Note 4] heXacode:
Ah. Ok. See I went and searched for what devices were experimenting with DM_VERITY and saw the S6 were not included with it. Must be a mistake by the author.

If DM_VERITY shows verification failed then I'm 100% sure no modifications were made to it for root reasons. So that leaves us with the write protection issue.

I had a user do a complete capture of Kingroot rooting the Note 4. He used Wireshark for it and handed me the file for inspection. I couldn't find much of it in action and what all it was doing to bring temp root. Everything is done through the servers. I'm still sifting through over 27,000 packets from that capture to find the ingredients used to root. I even did a find DM_VERITY among the packets and didn't turn up anything.

So, now I'm starting to believe they either shut off write protection somehow or disguised the rootkit for the S6 and Edge and didn't do anything to dm_verity. If I can find evidence of that in the capture then it might show as failed because of the structure differences between the S6 and Note 4.

If I find these evidence in the capture then I'll definitely post my findings here and see if we can set it correctly to work for the Note 4.
[AT&T Samsung Galaxy Note 4] elliwigy:
if its similar to ping pong then you can find the root method in the ping pong apk.. early versions he would add support in the actual apk.

ping pong and king root dont work on my snapdragon tablet on 4.4 or 5.0 with no dm verity.

quite odd s6 and s6 edge with dm verity has perm root.. on the note 4 does it say failed in recovery like ours?

if they are the same then maybe look into the s6/s6 edge root process with ping pong since it might seem that it disables the dm verity which allows root to stick after a reboot.

ping pong does need support to be added by giving them the boot.img and build prop.. not sure why the build prop is needed but the boot.img should be obvious
[AT&T Samsung Galaxy Note 4] eklipz3:
My grandson is gonna root his s6 edge tomorrow hope I can report to you guys with something.

Sent from my VS985 4G
[AT&T Samsung Galaxy Note 4] heXacode:
No it doesn't say anything in the recovery. I guess I could look at ping pong root and see what their methods are. I'm pretty sure they aren't touching dm_verity stuff. Although I need evidence of that. I found the tool used by Kingroot to root the Note 4 but it's all garbled text. I'll have to use Android Studio to view it correctly.

I don't think there's much you guys can provide other than maybe confirm dm_verity verification failed message in recovery after rooting?
[AT&T Samsung Galaxy Note 4] COA4178:
And a bunch of promised cash h

From the bounties
[AT&T Samsung Galaxy Note 4] holywhitebread:
So today is the big day for Mr. Anthony...I'm anxious to see what happens.
[AT&T Samsung Galaxy Note 4] thanitos:
I vote nothing will happen, but I'd love to see root on our phone, and an unlock would be amazing
[AT&T Samsung Galaxy Note 4] alicepattinson:
Please someone answer this. :( I do also need to root mine. :(
[AT&T Samsung Galaxy Note 4] MrPlNK:
Read the thread alice, there's no root for us, not yet. Might happen today, although most are skeptical.

Back to lurking I go
[AT&T Samsung Galaxy Note 4] tee00max:
Man I have to go back and do some reading in this thread. I fell off it for awhile since i thought it would take forever. To see someone is going to report back is pretty nice though.

---------- Post added at 11:16 AM ---------- Previous post was at 11:13 AM ----------

Did he say he would have an answer to us today??
[AT&T Samsung Galaxy Note 4] holywhitebread:
He said it would be released today, so we'll see.
[AT&T Samsung Galaxy Note 4] tee00max:
Gotcha. I see it. That would be huge. I just wished we only could get an unlocked bootloader but root would be fine for me for right now.
[AT&T Samsung Galaxy Note 4] v3ngence:
I got tired of waiting for you guys, so I planted a tree on top of my Note 4 to force-root it

But just my luck, all the roots missed the phone...
[AT&T Samsung Galaxy Note 4] holywhitebread:
Yeah, root is all I want. I don't really care about the locked bootloader since I never mess with the kernel.
[AT&T Samsung Galaxy Note 4] tee00max:
Well I mostly want recovery in order to load up custom roms. I don't mess with kernels either.
[AT&T Samsung Galaxy Note 4] holywhitebread:
Then root is all ya need. :p
[AT&T Samsung Galaxy Note 4] robg2008:
Please be real. I greatly want root. Once i can get xposed framework on my note 4 it will be perfect.
[AT&T Samsung Galaxy Note 4] Reinaldo33897:
I'm not sure if everyone has noticed but the rooting post is originally posted in the galaxy s5 forum. Now not sure if this perma root was meant for the s5 and s4 only. Unsure if anyone is even testing it on the note 4. So is this actually being tested for us or is it a trick post.
[AT&T Samsung Galaxy Note 4] holywhitebread:
He said it works for all devices.
[AT&T Samsung Galaxy Note 4] Ghstudent:
Can you give me a link to your source of this info please?
[AT&T Samsung Galaxy Note 4] holywhitebread:
http://xdaforums.com/showpost.php?p=57615695&postcount=953
[AT&T Samsung Galaxy Note 4] thanitos:
If it works I'll be very happy and it will also turn the rooting community upside down as far as what is able to be accomplished from this point forward. I always assume the worst though and assume this won't work for the note 4
[AT&T Samsung Galaxy Note 4] holywhitebread:
Yeah, I was optimistic up until around noon today when no one had heard from him. Oh well, nothing lost, nothing gained. It'll happen eventually.
[AT&T Samsung Galaxy Note 4] Martinjv71:
Didn't sound legit anyways
[AT&T Samsung Galaxy Note 4] elliwigy:
confirm its not there before then see if it says dm verity failed after root.

maybe they dont touch dm verity but exploiting the device causes dm verity to fail.

i believe it uses a ping exploit so i dont think it touches dm verity now that i think about it. probably a similar method to king root except king root is for 32bit devices mainly. either way, seems ping pong is kernel specific so he needs kernel modules from a boot.img to add support

i tried to look at ping pong w

hen it came out but the added support was in a raw file i couldnt view.. it could even be in chinese raw data.. notepad++ couldnt read it by itself..
[AT&T Samsung Galaxy Note 4] heXacode:
The write protection is on the kernel level as stated in that link a few post back. If it's shut down, modified, or rootkit disguised then it's gonna throw a dm_verity verification failed message.

Has anyone even talked to or given the Note 4 boot.img and build.prop files to the ping pong root team?

It won't do us much good if ping pong root is only for 64bit devices. I'm still curious to see the methods though. The apk has to be decompile in order to view everything.

So tomorrow I'll check out the methods and also see if I can find anything about shutting off write protection.

---------- Post added at 06:55 AM ---------- Previous post was at 06:36 AM ----------

Good place to start researching how to turn off WP by compiling kernel source and making the necessary adjustments. Basically streamlining your own kernel with WP off.

http://xdaforums.com/showthread.php?t=2701816
[AT&T Samsung Galaxy Note 4] elliwigy:
too bad we cant use a custom kernel.. maybe talk to a kernel dev to see if they can take a look
[AT&T Samsung Galaxy Note 4] heXacode:
I know just the guy for it. I'm gonna contact him tomorrow and see if he's willing to take a look. You might know him as [MENTION=4608636]bsmitty83[/MENTION].
[AT&T Samsung Galaxy Note 4] zxz0O0:
dm_verity is a feature to verify the integrity of blocks. It's not a write protection. This means, it will throw an error message if the block is tampered but it will not 'revert' changes to a partition. dm_verity is in the kernel and it shouldn't be too hard to shut it off by calling dm_unregister_target or clearing the _targets list.

I haven't really looked into the write protection but I believe it's applied in a lower level (as also pingpong root dev idler1984 stated). If you believe it's kernel side, can you quote the code from the Note 4 kernel?
[AT&T Samsung Galaxy Note 4] gatesjunior:
https://source.android.com/devices/tech/security/verifiedboot/index.html

First paragraph..
[AT&T Samsung Galaxy Note 4] zxz0O0:
This confirms what I just wrote so what are you trying to say?
[AT&T Samsung Galaxy Note 4] siriom:
So the dm verity check fails on boot and resets whatever changes were made ?
[AT&T Samsung Galaxy Note 4] gatesjunior:
dm-verity helps prevent persistent rootkits that can hold onto root privileges and compromise devices

Explain the above. Let me turn this around, define what you think they mean by this statement.
[AT&T Samsung Galaxy Note 4] siriom:
I understand it as "it verifies changes on some parts of the system (blocks)" and "prevents" it by doing the checking and un doing the changes?

Which could explain why changes are undone on reboot ?
[AT&T Samsung Galaxy Note 4] gatesjunior:
Another article

http://www.xda-developers.com/google-taking-aim-at-device-modders-in-android-4-4-kitkat/