yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note 4] raynan:
I'm definitely buying all my future devices unlocked from now on. It's not that they're impossible to root/unlock bootloader on, it's mostly a matter of how much time are you willing to use it the way it comes from the factory.
[AT&T Samsung Galaxy Note 4] eklipz3:
The FBI used hackers to unlock that phone.
[AT&T Samsung Galaxy Note 4] DamnCampers:
And yet the note 4 is one of, a very short list of, android based phone that is on an approved list of phones that are approved by the DoD. http://www.pcmag.com/article2/0,2817,2470758,00.asp This is probably why it has taken this long to get here.

Now let's keep on topic as much as we can. I know myself I'm getting antsy waiting to see if this bootloader unlock will work for our device.
[AT&T Samsung Galaxy Note 4] phaniblaze:
Dude, hacking into a locked phone is as hard as writing code for unlocking a bootloader or rooting or whatever you call it. It challenged the whole apple's security system. No one knows if the flaw would compromise apple protection layers.

And ATT note 4? Lol. I don't even want to talk anything about this s**t.
[AT&T Samsung Galaxy Note 4] soraxd:
Soo the Verizon guys got a root unlocked bootloader....

Hey.... good for them..... *vein pops*
[AT&T Samsung Galaxy Note 4] nemopsp:
Yup super crappy, just to know that the exploit would work on AT&T models, but we do not have developer edition...

Also sucks to watch their forums and see all the development progress and than you look at the AT&T forums and it's super quite... ._.
[AT&T Samsung Galaxy Note 4] p1gnone:
I still check in hopefully. But Samsung had best know that specs aside I and many others will never again buy one of its flagship handsets until it has been rooted.
[AT&T Samsung Galaxy Note 4] nemopsp:
Yes I check in too almost once a day... but very upsetting to this is the only model that hasn't obtained root yet... Wish these Yemen developers would come out and release root they claim to have.

Even if it just was TouchWiz root it better it could get these forums alive. I'd love to have a bootloader unlock, but that looks very unlikely which is upsetting because now Verizon will have the 6.0.1 update before us. They are normally last to see the update. Plus now with AOSP roms they already have 6.0.1 roms...
[AT&T Samsung Galaxy Note 4] spocko:
Yeah, me too. I was hoping that someone would figure out how to apply the Verizon exploit to the AT&T models, but that hope is fading. :(
[AT&T Samsung Galaxy Note 4] elliwigy:
have you guys reached out to devs? when i reached out on my vzw s6 edge i asked if in theory it would work to change the cid to another variant such as the international and i was told in theory it could work but of course i couldnt try because the s6e has ufs and no eMMC..

makes me wonder if you could change cid to vzw de cid and unlock BL then with twrp flash an att rom? essentially youd just need to unlock the BL..

devs can shoot this theory down but if anything for someone to attempt would be risking their device lolif it works tho ull all be set
[AT&T Samsung Galaxy Note 4] giga8547:
If i knew who to reach out to i would and i would most likely be willing to risk my phone to test things out. For some reason my phone never bricked with the latest or any kingroot so i would try it.

---------- Post added at 08:37 PM ---------- Previous post was at 08:24 PM ----------

Oh and i have an extended amount of android knowledge including ADB, apk modding and creation rooting system file editing. Plenty of experiance flashing and debricking. I also have insurance on my phone lol
[AT&T Samsung Galaxy Note 4] ndmoh1:
This has been a wake-up call for me when picking up a new device. Perhaps, there is a Dev out there silently working on freeing this device's potentials. I am still hopefully.
[AT&T Samsung Galaxy Note 4] Jaytronics:
This is why my last Samsung device was a Note 3 and 10.1 2014. Granted, I have the Note 4. But that was given to me by my employer. Happy though to be able to have root and unlocked bootloader. Unfortunately though, that will not happen until I have a working computer at my disposal. Besides the point. Even though I am not on AT&T. I am looking forward to you guys getting root. I hope that it happens for you guys soon.

On a somewhat side note, I wish someone. Even though it would disrupt our lives somewhat. Would take Verizon and AT&T and shut them down hard. Make life a living hell for them. Let them know that they should drop this controll garbage thing all while charging as much as they do for these devices. Any way, pun intended. I am Rooting for you guys.
[AT&T Samsung Galaxy Note 4] iRashawn229:
If root never comes to our at&t devices I would just recommend getting the Moto X Pure Edition. I own both the at&t note 4 and the Moto X Pure and you have more freedom with the Pure.
[AT&T Samsung Galaxy Note 4] sweetboy02125:
Give up guys, LOL, it's 2 years old, stop hoping when new techs coming out everyday. heheheh (still using it now)
[AT&T Samsung Galaxy Note 4] Crimson Ghost:
The Verizon edition is the same age and it was fully unlocked a few days ago. The same exploit should work for the AT&T edition with some tweaking. I wonder if the bounty is going to get back up to where it was because of that. A lot of people have pulled their pledge after getting new phones.

---------- Post added at 07:33 PM ---------- Previous post was at 07:31 PM ----------

I would settle for root. I rarely like custom roms.
[AT&T Samsung Galaxy Note 4] manbat:
Verizon method will not work for ATT. The Verizon method turns the VZW retail Note 4 into a Verizon Developer Edition Note 4. There never was an ATT Developers Edition Note 4 to turn the retail into.

Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.2-0.trltevzw
[AT&T Samsung Galaxy Note 4] nemopsp:
Yes but there could be a tweak that might be able to be made to use Verizon aboot and eMMC CID just to unlock the bootloader once unlocked you can flash TWRP and install a AT&T rom. The chances it working is low probably but I'm no developer. And might be worth looking into to modify it to work on AT&T model. Some claim they modified it working on the AT&T Galaxy S5 using the same bootloader exploit that uses Verizon Galaxy S5, which ultimately is the same eMMC CID change / SamDunk exploit.
[AT&T Samsung Galaxy Note 4] ndmoh1:
Perhaps it's time we make a Developer Edition for At&t ????
[AT&T Samsung Galaxy Note 4] giga8547:
What information was required to convert a verizon note 4 to a dev edition was ot a specific number code or what? I have read alot on the verizon method and from what i had gathered it could possibly be duplicated on other devices with similar bootloader as long as it is a emmc.
[AT&T Samsung Galaxy Note 4] jboucher614:
AT&T released an update with security enhancements yesterday, any word about this and how this affects us?
[AT&T Samsung Galaxy Note 4] dkmac:
I am not sure. I know that I have my OTA blocked; however, I too find it interesting that a sudden security update is released now about two weeks after the Verizon hack is discovered and rolled out. It is stuff like this that tells me that their devs know something that we have yet to discover.
[AT&T Samsung Galaxy Note 4] Reinaldo33897:
My apologies my comments were not necessary. I will delete as I admit you are correct, my mistake.
[AT&T Samsung Galaxy Note 4] play2loud:
Note 4 Root

The Problem is that there is no release for the, Android 4.4.4 KTU84P, which is the specific OS for the AT&T KNOX version with TIMA and ODE and SHA2 encryption

locked boot loader

They won't release the source code. so it literally has to be hacked old school fashion on a Linux platform. Needless to say this is not an easy task. the Devs who wrote

the source code made it difficult on purpose. Why you ask? It's not what you think, its because The Galaxy Note phone was the first phone in the world to pass

DOD and DOJ Security clearance protocols for classified document handling. As some of you may know Samsung Teamed up with the NSA. I know This sounds like

conspiracy theory, however you can look it up. Just Google "Knox NSA" Because the NSA had a hand in developing the Knox application they don't want people gaining

root and exploiting the code. Once root is achieved they have to start over and increase security more. The Dev's who are trying to achieve a root exploit are directly messing with the NSA's baby. That is not a fun game to play. It sucks for regular Joe's like me who own a Note 4 and just want to make a few mods. However, I think the dam code should be released and the freaking DOD & DOJ should have their own Proprietary devices. Let us have our toys and don't intermingle civilian tech with government tech. On the flip side

that's how they build the most secure devices in the world by allowing the public and geniuses like XDA Developers to try to exploit their work. Then the weakness is exposed and allows for NSA & Samsung Dev's to modify and correct exploits. Eventually root will be achieved, Then its just a matter of blocking OTA Updates that compromise SU privileges. Even on the Note 3, I don't think True root was ever achieved. Towel root just side stepped the knox counter and added a SU Privilege that allowed for lots of tweaks. The De La Vega Hack may have achieved access to the Kernel, I'm not sure on that one. I do know it pissed off AT&T, LMAO. I hope XDA Cracks the NOTE 4 and gets something like towel root. For now the closest thing you can do is to download note 3 OS and side load the entire OS in a note 4 then run safe strap & towel root and tweak it from there. The later is just an idea I am not sure if it would work given the locked boot loader. It may just brick the device. Just my humble thoughts on the topic.
[AT&T Samsung Galaxy Note 4] android-DEP:
You want the source code?

Here's the link to every SM-N910 firmware source code.

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-n910

It's been available for over a month.

I downloaded the AT&T sources, and forked the 4.4.4_r2 branch. Built everything from source code, the platform and kernel I rebuilt entirely from source code as their instructions stated but could not get the files to flash. Keeps failing because of the SecureBoot bull**** system they put in place. It's like the UEFI BIOS on Windows 8 which has a security boot checkpoint and normally disables booting from any other media than the Boot Manager.

It's really a pain because you have to explicitly disable the secure boot setting in the BIOS if you wanted to boot from a flash drive for example but I haven't seen anything about disabling this SecureBoot on Android anywhere. :rolleyes:
[AT&T Samsung Galaxy Note 4] cepsbow:
And that's because you have to be able to spoof the checksums of the img's that SB loads, the 'bootloader exploit' that everything hinges on... The white paper on it can be found here: https://www.samsungknox.com/en/products/knox-workspace/technical

Security implementations such as this are difficult but not impossible to subvert. Only time and patience will shed any light on these issues.
[AT&T Samsung Galaxy Note 4] play2loud:
Note 4 Root

Security implementations such as this are difficult but not impossible to subvert. Only time and patience will shed any light on these issues.[/QUOTE]

With my bloated rant that':eek:s what I was getting at. LOCKED BOOT LOADER = NO ROOT

Like I said eventually someone will side step it an gain elevated privileges. its just a matter of time and patience.

They just made this one super difficult.

---------- Post added at 11:20 PM ---------- Previous post was at 11:08 PM ----------

Does that source code give you the bootloader, meaning how its built? from what I understand it uses an emulated drive to mirror the boot loader to verify the integrity against a known true image. Like you said its a matter of spoofing the check sums during boot. I believe that's how towel root worked, Forgive me if I'm wrong I'm no Dev I'm just learning. I was trying to build a virtual machine and download the N910a OS to run it on VMWare and see how it worked. Like I said I'm not even in the same league as these guys working on it. I'm a noob when it comes to physical application.
[AT&T Samsung Galaxy Note 4] android-DEP:
Well said, I haven't even thought spoofing checksums, I assumed something of that nature would indefinitely be impossible to pull off past the NSA's strengthened Android. Then again, nothing is impossible. With these systems become so complex now a days, it inevitably would introduce some other sort of a weakness somewhere unintentionally.

The only exploit I truly think could hold water is the settings priv. leak which exposes a PendingIntent that can be broadcast to any other receiver using the system's credentials. Theres source code out there that shows the proof of concept of this exploit existing where it can crash the system to force an instant reboot after hitting the button. This is interesting because I've tried multiple apps that I've used previously on the S4 rooted and not a single app I've found was capable of rebooting the phone. It's not even possible to open terminal on the phone and get it to reboot by commandline. Yet this proof of concept app is capable of instantly rebooting phone.

One other example it displays is to receive a text message from 911. Where surprisingly if you hit that button, you will receive a text message from 911 dated December 31st, 1999.

So going by these examples, this app's source code can be adjusted to pass some command using the system's context through a pendingintent broadcast.

If someone with knowledge of how to broadcast intents and how to work with receivers could come up with somehow to utilize this to maybe do something like:

a. execute "setprop ro.build.selinux 0" in terminal which under system context with system credentials should change selinux from enforcing(blocks actions) to permissive(logs violations of policy but doesn't block actions)

b. preload busybox, su, supolicy, sugote, sugote-mksh, daemonsu, supersu.apk, in /data/local/tmp. Then using system credentials to copy binaries to /system/xbin.

Just my thoughts, but i dont have all the pieces of the puzzle to put together here as this is a complex situation so I think this would require a team effort to pull off. Any useful ideas would be great here, I'm sure many people are getting frustrated\annoyed checking back to the thread daily without any real progress taking place otherwise

Not exactly. Towelroot utilized a futex exploit explained in detail here
[AT&T Samsung Galaxy Note 4] COA4178:
Aaaaaa we'll get there! The phone is good at the moment without root but imagine what setcpu would do jiji:cool:
[AT&T Samsung Galaxy Note 4] phobia09:
For what it's worth, Dan's SMC exploit was released just after the VZW/ATT GS4 came out to circumvent the bootloader. Both carriers patched the exploit a few months later. What I've heard from some much more well-versed in this topic than I, there's a lot we can learn from Dan's exploit, such as looking into TIMA for more possibilities, but no actual retranslation in today's security is possible. Thanks for taking the time to dig into this, everyone here appreciates it.
[AT&T Samsung Galaxy Note 4] play2loud:
Note 4 root

Ironically enough I think the way to hack the N910a is through the Knox EMM Admin portal I bought knox emm and knox premium and they allow for custom apks to be built and pushed from pc through cloud server to phone. I can do almost anything to this phone remotely from Samsungknox.com remote wipe, screen lock, shutdown, reboot, I'm just think with the option to build and push a custom apk directly into the phone as a system app, if someone knew what to build this would be an easy way to load it. it only costs a dollar a month. just a thought. hey how did you go about decompiling the bootloader?
[AT&T Samsung Galaxy Note 4] FiniteTime:
Thanks ZPaul2Fresh8, good investigating.

We're at the point where we need to find an exploit. Finding an exploit isn't straightforward and is quite tricky but it can be done. Digging up resources for finding exploits and looking for exploits is the best use of our time for gaining root.

For those with enough experience that they think they can help find an exploit or exploits, some info about custom kernels and general stuff required for root:

"kexec is developed and you figure out a way to enable loading of insecure kernel modules"

http://xdaforums.com/showpost.php?p=56949341&postcount=581

Info from Chainfire and thoughts by Surge1223: http://xdaforums.com/note-4-verizon/general/talk-root-t2908919/post56823482#post56823482

"Spoofing checksums" assumes a collision in the hash used so currently impractical.

Basically finding an exploit. Either through a CVE coming out or someone being awesome to the point of finding stuff in the above links like:

"Potential useful user/dev: it looks like kernel memory is being leaked at 0xsomeaddress. Looking at the zimage assembly from source we might be able to do so and so."
[AT&T Samsung Galaxy Note 4] android-DEP:
And on that note, here is something I've been exploring that I believe could be utilized. It apparently was patched in 5.0 Android and I've tested this on Android 4.1.2 but using the example PoC that was put together by this one researcher named retme here: https://github.com/retme7/broadAnyWhere_poc_by_retme_bug_17356824, it had no effect at all whereas on my Note 4 running Android 4.4.4, the PoC app worked exactly as described in the disclosure

This was a vulnerability thats disclosed under CVE-2014-8609

More information is also on retme's website but is entirely written in Asian so the page needs to be translated to English to be able to read. Here's the link to his page on this exploit: http://retme.net/index.php/2014/11/14/broadAnywhere-bug-17356824.html
[AT&T Samsung Galaxy Note 4] ZPaul2Fresh8:
I've been doing some more researching and I wanted to post this before I forgot. Then I will go through your post [MENTION=6122418]FiniteTime[/MENTION]. Well here goes:

A Change of Mind on CVE-2014-8609

I originally said I didn't think that CVE-2014-8609 would be of any use to us but after doing some in-depth searching I think it could be the answer. But it's going to be a cross platform jump. Here's what what may have to happen if this exploit were to be used.

1. Write an Android App to register itself as an "account authenticator" to send the intent to the Settings App. Upon receiving such an intent, Settings app will (automatically) call the method addAccount and send the pendingIntent to OUR app's addAccount method.

Since the pendingIntent's actions and components will be blank(thus causing our exploit), Our app can fill in arbitrary action and extra information into this intent and resending this pending intent, with the permission of SYSTEM.

Now since we have NO root and NO BusyBox, we have VERY few linux commands with the shell we currently have so we will have to outsource to a server and have the server send them back for achieving root. I believe this was used in GeoHotz TowelRoot too. I think this is how it should be done, Let's see what we can do!

This is getting VERY interesting. I see these exploits working for us and other devices!
[AT&T Samsung Galaxy Note 4] ODSTZ3RO:
Awww wtf ^ just when progress was being made I guess we'll see in 3 months if root is achieved I'll wait until the 3rd week of next month if not I'm afraid waiting will come to an end and I'll have to update to 5.0 or whatever Version is pushed out I really don't like waiting
[AT&T Samsung Galaxy Note 4] Simsron1:
Well at least this thread was cheerful for a minute.
[AT&T Samsung Galaxy Note 4] ODSTZ3RO:
I hope people don't get discouraged I really want a rooted device I'm going to rage so bad if it never happens
[AT&T Samsung Galaxy Note 4] Stryke_the_Orc:
Threads open again. Let's keep things civil.
[AT&T Samsung Galaxy Note 4] ODSTZ3RO:
Now ^post #375 doesn't make sense thanks though we need positive attitudes here I'll spectate meanwhile people working on this work this out
[AT&T Samsung Galaxy Note 4] howellcp:
Following the links around the exploit you are all talking about lead me to this: http://xdaforums.com/mate-7/general/wip-mate-7-root-bl-unlock-t2995086. Can this be modified to work for the Note 4? I am sure the developer gods have already looked at this but I figured I ask.
[AT&T Samsung Galaxy Note 4] giga8547:
Thats exactly what i said in another thread. As soon as kingroot partialy started working again on 5.1.1 then they released a security patch and everyone aeemed to have the take the phone to att to fix message i personaly did not get that message and i never took the security patch then. And now that verizon has unlocked bl by making the phone dev edition. Att releases yet another security patch. Hmmmmm coincidence?? I personaly think it is not and they are actively tryng to thwart any attempt or progress of unlocking the bl or root. And as soon as my contract is at a poit i can buy out of it i will be moving on.
[AT&T Samsung Galaxy Note 4] elliwigy:
theyre always working and pushing updates to block expkoits.. nothing new there lol..

how many "security" updates does every device get lol
[AT&T Samsung Galaxy Note 4] raynan:
That's what they get paid to do lol. If I remember correctly, Jcase works or worked in Linux security; I'm sure he could tell you all about it :p
[AT&T Samsung Galaxy Note 4] killaj419:
So no news on the root status for the at&t?
[AT&T Samsung Galaxy Note 4] wildbil:
I have successfully rooted with kingroot 0n 5.1.1 blocked updates in March it doesnt last long but i want to try .Is there a custom recovery that will work safely with at&t note 4 and is there any way to boot directly to that recovery without rebooting I have seen warnings on cwm and twrp there must be one that can work for our device or be modified to do so . I have already tried safestrap for the note 3 and the s5 both failed note 3 recovery button in app that says reboot to recovery did light up but did nothing . Question is phone still rooted when you get rebooted and says secure kernel fail return to at&t for service what I call the dread screen. Kingroot does root my phone but not only is root temp it also seems to lose ability over a short time . If I can get a recovery that will work for this phone get it installed and get into it could I then flash the pre rooted rom in the development forum will this work .

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

Sorry if its a noobish question but everyone has to somewhere
[AT&T Samsung Galaxy Note 4] giga8547:
No it will not work as long as the bootloader is locked you can not install any form of custom firmware or recovery because the bootloader will stop any atempt and lock up period. The message you get is the bootloader locking the phone out because the kernel os no longer secure or modified.
[AT&T Samsung Galaxy Note 4] elliwigy:
as stated already, it will not work due to locked BL and the write protection.

also to add, I would tread carefully.. you can potentially brick your phone messing around like that if you dont know what your doing.
[AT&T Samsung Galaxy Note 4] eklipz3:
I would continue to chill like most of us with VZW did, I didn't think it was ever gonna happen but thank God I continued to wait. I'm sure the devs are still working on you guys.

Sent from my SM-N910V DE
[AT&T Samsung Galaxy Note 4] amsgh:
Same here. There's no other device out there right now with the options of a TWIZ device (importantly the expandable storage and remov battery) so it's not like I can buy anything else better anyway.

sent from my SM-N910A
[AT&T Samsung Galaxy Note 4] Teknoshamn:
Have you tried cf autoroot using your carrier/model's 5.0.1 version? I, and others on here have had success rooting, despite the MM OTA upgrade.