yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note 4] Xak:
[MENTION=3178012]gatesjunior[/MENTION] I have had bad luck with hard reboots using super su using both the old and new file. Following steps exactly using NI3 firmware. Even with the soft boot app. How ever both king root and this modification work and I was able to get Viper4Android audio and Xposed working with both both kingroot and supersu mod. I found this a while ago, everything sticks using francos soft reboot app, to soft reboot. However if you do loose root all you have to do is root again with kingroot app and then re-allow permissions from previously install xposed modules or any app that needs su / kingsroot permissions. Then soft-reboot a couple of times with francos app and your back with all your modules still working. Note too, you'll also have to re grant permission to busy box and install it through the app every time you do hard reboots. I'll edit this post to add screenshots. GravityBox [KK] works and if hard rebooted mods will be gone but use kingroot app to re root and then soft-boot via francos and everything will return even viper4audio. You'll need to install the V4A driver every hard reboot too then dont click reboot when it asks just click your devices home button and soft-reboot via francos.

Note: Gravity boxes soft-reboot method via enabling the adv reboot doesnt work and acts as a normal hard boot!

Also the app will grey out driver status but I guarantee it works and it's awesome just change it to your default audio fx app in Device-Sounds-Advanced-Music Fx and select Viper FX

FYI I found a glitch when using these temp methods that when attempting to remove ATT wifi hotspot with titanium back_up it hard reboots your deivce. The only bloat app that cant be removed so far with temp root.
[AT&T Samsung Galaxy Note 4] soraxd:
well damn lmao.

anyyyyyways it's ready?? ? the moment I've been waiting for since November, time to go take the plunge!
[AT&T Samsung Galaxy Note 4] MiittchXD:
Losing root after 10-15 mins

I followed the video tutorial and I keep losing root after 10-15 minutes. I have re rooted 3 times now and it is still happening. Any ideas what is happening? On a AT&t Note 4 on 4.4.4
[AT&T Samsung Galaxy Note 4] Sizzlechest:
It was hypothesized that the issue with losing root was due to Knox, but if the issue is with Super SU, would it be a good idea to try a different SU (like ChainsDD) instead?

EDIT: I lost root again. Rebooted and re-rooted. However, right before the cleanup, I installed ChainsDD su and uninstalled Super SU. It rebooted and I verified root was still good with Root Checker. This su doesn't seem to give any notifications when an app requests root, but I do still have root. Time will tell if it will stick.
[AT&T Samsung Galaxy Note 4] MiittchXD:
Ok so what I did was not install super su and used the kingroot user app and now it is working fine. I used the soft reboot app a few times with the kingroot app and now everything is working. Super su wont even let me update binaries but this kingroot app seems to be working fine.

---------- Post added at 12:18 AM ---------- Previous post was at 12:00 AM ----------

Nvm... root was lost again, very annoying.
[AT&T Samsung Galaxy Note 4] DeathLord..:
Losing root

I must agree with everyone. Yes, gatesjunior and crew gave us Supersu and a way to install it. I have mastered the process shown to us by RootJunky. I have done this over at least 15 to 20 times since it was released. I do not take anything away from Gates and his crew but I must ask if there is a different package or process for AT&T Note 4. If I am not mistaken this is working 100 percent on Verizon and spotty on AT&T.
[AT&T Samsung Galaxy Note 4] howellcp:
In lose root.
[AT&T Samsung Galaxy Note 4] soraxd:
man its hard to keep track of all these threads, spiderman wants to see as many separate threads as possible .

DeathLord, are you on kitkat or lollipop?
[AT&T Samsung Galaxy Note 4] DeathLord..:
I am running kitkat 4.4.4.

AT&T Note 4 SM-N910A.
[AT&T Samsung Galaxy Note 4] Sizzlechest:
Nope. Lost root with other SU.
[AT&T Samsung Galaxy Note 4] gatesjunior:
Guys, as someone else already stated. this is not a SuperSU issue or Kingroot / KingUser issue. We have shown now that with any SU app running and enough messing around or time goes by, it appears people are loosing root.

I am going to dig into this more and find out what is causing this at a system level.

We have SuperSU now, now we need to stabilize the system.
[AT&T Samsung Galaxy Note 4] cstayton:
this almost sounds like some form of chron job running at a system level meant to verify system integrity. I have used similar jobs in the past to due the exact same type of verification on linux/unix systems in an enterprise setting.
[AT&T Samsung Galaxy Note 4] DeathLord..:
[MENTION=3178012]gatesjunior[/MENTION] I believe I had seen a post where someone had said that they have had it running no problems for 3 days. Maybe we can locate that post and speak with them and see what they are running or what device they are using. Just trying to help.
[AT&T Samsung Galaxy Note 4] darkjedi7:
I'm on vzw and have been running this since first posted today, I am only using adaway right now but have had no reboots and have not lost root since installed so about 8 hours.
[AT&T Samsung Galaxy Note 4] DeathLord..:
That is what I was thinking. That it is working for Verizon not ATT version. I hope gates and crew can resolve this.
[AT&T Samsung Galaxy Note 4] CJ74753:
EDIT: I've lost root also.
[AT&T Samsung Galaxy Note 4] darkjedi7:
I don't think so because people on vzw forum are having issues as well. Just an FYI though I could not get adaway running after this I had to reboot root with kings root install adaway then run the program and adaway stuck after that.
[AT&T Samsung Galaxy Note 4] DeathLord..:
I am willing to take any advise you may have.
[AT&T Samsung Galaxy Note 4] CJ74753:
I had to shut down the Adaway program the first time I ran it after root cause it just opened a black screen, after that it ran fine and root request finally popped up.

I'll pm you to see if I can help.
[AT&T Samsung Galaxy Note 4] sTl2yk3l2:
This time I lost root after like 10 minutes. The people that are not having issues, are you guys using straight king root, or using the script to install super su and remove king? I haven't tried just using the king root without using this script. The su apps works, but sometimes it will work for an hour or 2, sometimes like 10 minutes and I lose root.
[AT&T Samsung Galaxy Note 4] MiittchXD:
I lost root when using only king root and with using the super su script.
[AT&T Samsung Galaxy Note 4] CJ74753:
EDIT: Just noticed after talking with Deathlord I've lost root also. Running Adaway I get "Unable to locate a partition to remount to write the hosts file to."
[AT&T Samsung Galaxy Note 4] SacrificedWalrus:
What we need to look at is Android's verified boot (https://source.android.com/devices/tech/security/verifiedboot/index.html). Basically what this does is checks the system at each boot and makes sure it meets the expected requirements, if it does not than it will make it so it does meet said requirements. This is also known as dm-verity if you want to look into that. Looking here (http://nelenkov.blogspot.com/2014/05/using-kitkat-verified-boot.html) we can see the steps to enable verified boot. I have personally tried editing the fstab file to disable verified boot, but the change was still reverted so if someone else wants to look at that or try a different approach we might be able to crack this.
[AT&T Samsung Galaxy Note 4] DeathLord..:
Losing root

..
[AT&T Samsung Galaxy Note 4] ShadowsDemise:
I find it interesting that only some of are having problems with loosing temp root randomly. I've tried both straight Kingroot and SuperSU Me and I loose root randomly no matter which method I use. I have even factory reset my phone and ran Kingroot before installing any extra apps (in case an app was making me loose root) and I still lost root after a while.

Here's my phone info if it'll help any devs:

Carrier: AT&T

Model: SM-N910A

Android Ver: 4.4.4

I'll definitely prefer the SuperSU Me method once they (hopefully) figure out why we randomly loose root and fix it because using SuperSU over Kinguser seems to be much more stable.
[AT&T Samsung Galaxy Note 4] tampaboy1984:
So is this only working on KitKat at the moment?
[AT&T Samsung Galaxy Note 4] DeathLord..:
Correct.
[AT&T Samsung Galaxy Note 4] EMDrNote:
Why don't you read the thread and then come back and tell us?
[AT&T Samsung Galaxy Note 4] spartan07:
Wonder if you set the phone in airplane mode if you lose the root? Maybe it's phoning home after a certain amount of time?
[AT&T Samsung Galaxy Note 4] Sizzlechest:
I'm wondering if there's some security service running in the background that's looking for root-level apps running more than an hour or so and shutting it down. Or heck, maybe it's some Samsung task-killer that happens to be killing root.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
if you look in the superme thread we have discussed how to stop the random reboot as well as what is causing the system to reinstall stuff

1. dont use anything to uninstall system apps(titanium backup, root uninstaller ect...) use debloater to disable them if you uninstall them you will no doubt have random hardboot and lose root we are working on this

2. dm_verity is causing all the issues look up info on that yourself unless you have major dev or programing experience you probably cant help fix this issue

please understand we are working hard on this stuff but it will take time we may never get it
[AT&T Samsung Galaxy Note 4] deathshead:
straight kingroot with just xposed+modules is holding just great for 6+ hours at this time.

anything else as other posters have noted will lose root in 30min, rootexplorer,titanium, viper, etc. anything that tries to write to system is a no go.

This is all meaningless however as this only opens up a fraction of what we need....
[AT&T Samsung Galaxy Note 4] reydarz:
[MENTION=2823580]deathshead[/MENTION]

Which modules?
[AT&T Samsung Galaxy Note 4] awinterstale33:
I've been using MW Window all day now.
[AT&T Samsung Galaxy Note 4] stillthisguy:
I too decided to just use kingroot to see how things go, and after 12 hours still have root. Just running xposed with exchangebypassforsm, gravitybox, minminguard, xinsta, and xposed GEL Settings. Also have SimpleReboot and xmodgames installed using root.
[AT&T Samsung Galaxy Note 4] Bob the tomato:
I have tried to install exposed but lose it upon soft reboot.
[AT&T Samsung Galaxy Note 4] stillthisguy:
Don't use the soft reboot option in xposed, download SimpleReboot from the play store by Francisco Franco.
[AT&T Samsung Galaxy Note 4] heXacode:
[MENTION=3178012]gatesjunior[/MENTION] did any of you see exactly what Kingroot exploits at all? Is it exploiting the processors like it's meant to do for the s6 or is there more to it? I haven't seen anybody mention exactly what Kingroot sends over to get the job done.
[AT&T Samsung Galaxy Note 4] psyciatrichelp:
I think when I get home I will try and setup an ad-hoc network connection on my laptop and wireshark my phone as it runs kingsroot. who would be interested in the captures?
[AT&T Samsung Galaxy Note 4] heXacode:
It would be nice to have it and know what exactly the tools are exploiting then we can have another alternative to possibly use to root. It would need to be modified though since it was meant for the s6 and not the Note 4 even though it partially worked.
[AT&T Samsung Galaxy Note 4] ad44891:
Great work & much respect to Dev. Group that has giving us this great opportunity... [MENTION=568179]gates[/MENTION] & crew.... But I must say.... PLZ.....STOP ✋ ✋ with all the *****in & complaining... Grow up and respect the work given... If u have nothing good or positive to say Or helpful info... Keep quiet and take a chill pill!! This is just the 1st phase.. It will get better with time ⌚.. Thx and have a great week! ?
[AT&T Samsung Galaxy Note 4] butchieboy:
+1+1+1

Galaxy Mega..(MegaKatV30)
[AT&T Samsung Galaxy Note 4] psyciatrichelp:
Ok I was able to capture all packets from my phone while running kingroot. I would prefer to only PM this to DEVs. I opened kingroot then started the root and stopped capturing right after successful root. Please PM me if you would like me to send you a copy of my capture.
[AT&T Samsung Galaxy Note 4] adamrpostjr:
Freegee

This may be the wrong place to post but

I was reading about freegee and how it bypassed the bootloader on some lg devices, I was wondering if something like that could be done on the note 4
[AT&T Samsung Galaxy Note 4] spexwood:
I'm not flaming you ;)

but I did suggest this before and was told it wasn't possible or something like that. I'd think it would be possible though, but maybe Samsung's bootloader is harder to bypass than LG's.

Also, my last phone was an LG and Freegee was what we used to install a custom recovery, not to actually root or install SuperSU/Superuser.

After suggesting that someone look at Freegee, someone pointed out to me that on Freegee's Play Store listing, it lists Root as being needed. So root has to be achieved BEFORE using Freegee.
[AT&T Samsung Galaxy Note 4] adamrpostjr:
Oops sorry I didn't see that I was doing some reading on the boot loader and came across that, but we have temp root now could it be possible or would the write to system block that? .. Sorry haha this is my first time every looking into android.. Being a network security guy I've never looked into it!
[AT&T Samsung Galaxy Note 4] patt2k:
hey guys hopefully this is not off topic but did you guys kingroot 4.1? maybe it will be a better solution to root instead of the older version ( I am backo on Lolipop and it gets stuck at 51% and reboots my phone)
[AT&T Samsung Galaxy Note 4] bghouse10:
I just went to their site & only see version 4.0 as the latest. Did you dwnld 4.1 from their site? I'm willing to test it....;)
[AT&T Samsung Galaxy Note 4] patt2k:
http://xdaforums.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461

English version is in there. Let me know what happens I am curious.
[AT&T Samsung Galaxy Note 4] bghouse10:
Thanks Patt2k,

I rooted successfully & verified in root checker. Installing xposed now & will advise if pandora patcher is allowed root access. I was able to install xposed successfully & activate the pandora patcher w/ 4.0 before but I could not get it to work. I noticed anytime I would open the app, neither SU or kingroot would grant root access for it which is why I am assuming it would not work. That is the ONLY module I enabled & tried to use. I will update the thread shortly...
[AT&T Samsung Galaxy Note 4] br3w3r:
Rooted fine with new version. But doesn't bypass/patch the write protection so a reboot still removes root. Was able to install xposed framework too.
[AT&T Samsung Galaxy Note 4] bghouse10:
Same here & it's the same as 4.0, no perm root unfortunately... :(
[AT&T Samsung Galaxy Note 4] elliwigy:
lool.. thats because its only for root.. not for write protection.. they are two completely seperate things
[AT&T Samsung Galaxy Note 4] scottjoshuac:
MD5 Hash Cracking

I ran across this article where Nat McHugh made two different pictures that had the same MD5 hash. I was wondering if anyone would be able to use this information to make a modified bootloader that hashes correctly, but is actually modified to allow permanent root, or flashing of other ROMs.

I'm unable to post links at this time, but if you google "How I created two images with the same MD5 hash" the top link will bring you to the website. Also in that website is a tech white paper that explains it more.
[AT&T Samsung Galaxy Note 4] 彩色的风:
root level？
[AT&T Samsung Galaxy Note 4] scottjoshuac:
What?
[AT&T Samsung Galaxy Note 4] ad44891:
It's alotta idle chatter goin in... ?
[AT&T Samsung Galaxy Note 4] tekjester:
It's not actually using MD5, it's using SHA 256. Which while similar, the hash is done using a large private key that is not going to be broken during the life cycle of this device. Pretty good info on it if you check slide 4 of this deck.

Intro to eMMC

This thing is crazy secure - my guess is that a hardware hack is going to be what finally breaks it.
[AT&T Samsung Galaxy Note 4] warriorpluto:
Sort of like a jtag or test point? I remember the old test point days on the Motorola flip phones. The good old days
[AT&T Samsung Galaxy Note 4] Chad_Petree:
Are you on lollipop or on kit kat?
[AT&T Samsung Galaxy Note 4] SageChrono:
doesn't work on my at&t 5.0.1 note 4, it stops then goes past 51% compared to the previous version but it still fails in the end
[AT&T Samsung Galaxy Note 4] Chad_Petree:
Thanks for letting me know, sorry for the mistakes lol, SwiftKey sometimes does what It wants!!
[AT&T Samsung Galaxy Note 4] alienundies:
Uninstall supersu and kingroot. Clear cache. Reboot and then retry. Works for me. Must be on kitkat. Doesn't work on lollipop.
[AT&T Samsung Galaxy Note 4] JOSHSKORN:
On 5.0.1? Thought it was only for KitKat. It's been stated hundreds of times.
[AT&T Samsung Galaxy Note 4] lamarwallace:
i have a at&t note edge on 4.4.4 and i rooted with kingroot. i found this site that claims it can unlock the bootloader with ez-unlock. i install the apk and clicked on the unlock bootloader button and it said bootloader is now unlocked. then i rebooted the phone and root was gone. could one of you wizard have a look and see if this can help us. thanks.

MODERATOR EDIT, LINK REMOVED BEFORE SOMEONE DESTROYS THEIR PHONE
[AT&T Samsung Galaxy Note 4] nemopsp:
The post say Galaxy S3 not Note 4
[AT&T Samsung Galaxy Note 4] heXacode:
You're really lucky you didn't hard brick your device. That's just stupid in my opinion.

If you would've read the entire article you would've seen nothing stating support for the Note 4. You might have seen the word "universal" but there is still NO support for the Note 4. They even list some of the devices supported by using certain rooting programs like Kingo and others.

Please read throughly before you go bricking your device. This is also a warning to those who venture into the unknown without reading and having substantial evidence that it works or not for whatever device. You will also have to be careful about which carrier you're on too.

Everyone needs to just leave the bootloader unlock stuff alone and quit asking about it because when you go leaving the wrong info and others see it and go test it without any common sense then it creates headaches for people who have to help a user return it to normal along with all the desperation and panic of the user with the hard brick device.

Just leave the bootloader alone! You're not going to get it unlocked!
[AT&T Samsung Galaxy Note 4] lamarwallace:
Advice taken.
[AT&T Samsung Galaxy Note 4] MiittchXD:
I thought I read somewhere that kingroot 4.1 got rid of AT&T losing root after around 15 mins. I am still losing root after 10-15 mins without touching a single system app
[AT&T Samsung Galaxy Note 4] thanitos:
The way to keep root is to avoid anything that writes to the system. If it writes to the system it will cause a reboot but everything else is safe. So exposed works but only a select few modules
[AT&T Samsung Galaxy Note 4] MiittchXD:
The only two apps I used were root checker and franco's safe reboot and I lost root
[AT&T Samsung Galaxy Note 4] thanitos:
Did you try changing settings or removing apps like att bloat
[AT&T Samsung Galaxy Note 4] MiittchXD:
No that's the weird thing. I flashed a fresh os with odin, used kingroot, used SuperSU me, downloaded root check and simple reboot, soft rebooted, checked back 20 mins later and root was gone. On a AT&T Note 4 4.4.4.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
Root for these devices are not stable you will lose root eventually could be 20 mins could. Be five days it's a shot in the dark when you root AT&T or vzw note 4

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] deathshead:
Hey Guys, Kingroot team is working on this but they need the following,.

SHA-1 and MD5 Fingerprint keys.

Anyone have an eclipse/studio rig setup to get some keys and pm me possibly?
[AT&T Samsung Galaxy Note 4] DeathLord..:
[MENTION=2823580]deathshead[/MENTION]. You get that to happen and they can correct it. You will be a hero to a ton of people.
[AT&T Samsung Galaxy Note 4] cstayton:
unfortunately your not going to get the SHA hash keys those are closely guarded by Samsung, and if we did have those there would be no need for kingroot because we could sign a custom bootloader and root the device by any method we choose.
[AT&T Samsung Galaxy Note 4] DeathLord..:
[MENTION=3758230]cstayton[/MENTION].. I didn't know that. Thanks for the lesson.
[AT&T Samsung Galaxy Note 4] siriom:
You just had to go ruin his day didnt you ?

and its a friday of all days ....

For future reference , if you're gonna ruin someones day do it on a monday please.
[AT&T Samsung Galaxy Note 4] cstayton:
Haahaa I'll try to keep that in mind next time
[AT&T Samsung Galaxy Note 4] deathshead:
I think this is what they mean.

http://www.truiton.com/2015/04/obtaining-sha1-fingerprint-android-keystore/
[AT&T Samsung Galaxy Note 4] cstayton:
I see what they might be looking for however, they would still need the initial signing keys to even begin to make use of that info that is just the hash results of the file being signed and the md5 of the file. the best way to explain it is consider taking a calculus test in college the SHA hash is the answer but the test doesn't provide you the preceding formula that created that answer, therefore rendering the answer useless.
[AT&T Samsung Galaxy Note 4] gatesjunior:
Or as I sent in a pm, they might have just simply wanted the device fingerprint from the build.prop..
[AT&T Samsung Galaxy Note 4] tekjester:
There's no point in seeing what the fingerprint is. It's impossible to cause a collision with SHA256, which eMMC is using to protect the bootloader.

---------- Post added at 09:16 AM ---------- Previous post was at 09:12 AM ----------

"Hash Keys" and the Hash itself are two totally different things. The fingerprint is the result of the hash key and hashing function. It's theoretically possible to crack SHA1, which is why it's being deprecated. However, SHA256, which is the check that's occurring, is impossible to crack.
[AT&T Samsung Galaxy Note 4] deathshead:
Yes and thank you! - Can anyone provide a device fingerprint from thier build.prop for the ATT version?

I never claimed to be a developer, I was basically just relaying what Kingroot team was asking me, and we are dealing with a very large language barrier here. So don't shoot the messenger. lol
[AT&T Samsung Galaxy Note 4] adamrpostjr:
Auto Update???

Don't know if this is the place to post... But I wanna let you guys know that I was in the middle of running Kingroot again to root I got the 63% then my phone crashed once it rebooted it booted into the recovery screen and started to update my phone to lollipop I have a Verizon note 4 on 4.4.4
[AT&T Samsung Galaxy Note 4] Lenny2311:
I assume you were on wifi at the time. Same thing happened to me but happened when the lollipop update came out. So much for the "blocking ota updates"
[AT&T Samsung Galaxy Note 4] eklipz3:
Just a thought and it's probably been mentioned before and I apologize if it has but could these random reboots be caused by some system stuff running or doing a check in the background? Again I apologize if this was mentioned already.

Sent from my VS985 4G
[AT&T Samsung Galaxy Note 4] cstayton:
It is the DM_VERITY that is checking partition integrity and resetting if it finds an issue. We need to get past the write protection and verified is to resolve tuis
[AT&T Samsung Galaxy Note 4] gatesjunior:
Two different things here. The device fingerprint that is in the build.prop is for essentially identifying the device, etc.. They did not ask for the anything with the word "hash" in it. I believe that was misrepresented from their question..
[AT&T Samsung Galaxy Note 4] psyciatrichelp:
New packet capture uploaded to drive and PM'd to several DEVs. Please let me know if you need more.