yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note 4] dkmac:
I had the same thing happen to me today as well. I tried something different while routing my phone and everything went good. I went over to install supers and toward the end of install, the phone rebooted and when it rebooted it now shows the normal boots creek with an unlocked padlock and the word "Custom" underneath it. At the top of the screen it says in red: "KERNEL IN NOT SEANDROID ENFORCING". After that it goes to the screen stating that the device has non supported att software take to att store. When I boot into download mode I got something new. The script at the upper left displays the following:

ODIN MODE (HIGH SPEED)

PRODUCT NAME: SM-N910A

CURRENT BINARY: CUSTOM

SYSTEM STATUS: Official

REACTIVATION LOCK: ON

KNOX WARRANTY VOID: 0x0

QUALCOMM SECUREBOOT: ENABLE (CSB)

RD SWREV: S1, T2, R1, A2, PA

SECURE DOWNLOAD: ENABLE

U DC START

The custom binary is something that I have never seen before on this phone or can remember. I also went through the boot log dump and it looked interesting. What do you all think? Take care
[AT&T Samsung Galaxy Note 4] hllah66:
I had the same problem with my phone. After I've installed att 5.1.1 odin files, my phone worked again! Thank tonys.94 for his files. Please follow #1 post in topic: note 4 ATT 5.1.1 Odin Files in Progress.
[AT&T Samsung Galaxy Note 4] gatesjunior:
Below.
[AT&T Samsung Galaxy Note 4] gatesjunior:
Yes, indeed. Remember guys, as Surge is saying, the aboot is assigned to each DEV device individually. Signed for that specific DEV device. That's why, even if you have a dev edition aboot and try to give it to another user who has accidentally flashed a retail aboot to his dev device, it is not going to work. Unless something has changed, it is not as easy, even if you had the private key, to just sign an aboot and hope it works on your device. Now, if you had their flashing program, which I have seen floating around, and knew how to use it and had the private key, well maybe then. So, lets go way out there like Surge is saying. Even if you have a modified aboot and were able to modify it to take out some checks, there are other parts of the device checking the aboot signature and values, so you would literally have to modify several areas of the device all at once. I mean look, I remember someone who accidentally flashed a retail ODIN to their DEV device and even if another person gave them their aboot and recovery files from their DEV device, it will not work on their device, period. It is not just about modified files here, there are things flashed onto the device itself's chip that checks for certain values and signatures that you cannot modify without the right tools and signing keys.

Think of it like this. I have values that I expect flashed on the chip of the device. I check the bootloader, recovery, etc.. If any of these do not match up, I will halt the boot process. Now what I think I do know is that it doesn't necessarily know which one is what, meaning I can flash the aboot to recovery and boot into recovery and it will boot the device without any question. So that tells me, it is just checking for valid signatures, not necessarily what it is. But even with this, it doesn't change the checks on the kernel. So even if I could modify the kernel, if the checks do not match up to what I expect then it will still not boot. It goes around and around.

[MENTION=2376614]jcase[/MENTION] and [MENTION=4939386]Surge1223[/MENTION], want to jump in here ? These guys know this area much better than I. I am giving you the basic construct of it.
[AT&T Samsung Galaxy Note 4] kxhan15:
I cannot believe that ANYTHING digital can be THIS secure.apple is notoriously secure and people jailbreak those all the time. I just can't buy it. Nothing is that secure.

I mean hell look at every other version of this device on every other carrier accept Verizon. They all have unlocked bootloaders and are very root friendly. And they are all basically the same device . Samsung themselves are generally not against rooting. Why can't we use production certs and chains from one of those devices.
[AT&T Samsung Galaxy Note 4] kxhan15:
I have been able to dump some of the system files. 1. Android.policy.jar

2. Framework.jar

3. Framework-res.apk

4. Services.jar

5. SystemUI.apk

6. Twframework-res.apk

7. Build.prop

I have pulled a full bug report thru adb. And have recovery logs. If someone could give me the file path to the boot files that would be great. Thank you in advance
[AT&T Samsung Galaxy Note 4] Android.Ninja:
What is the possibility of a kernel being built that can / would bypass the security check while under temporary root, to eventually achieve permanent root, with a modified aboot, and other modified sections of the ROM. We are working on a way that modifies the original files, while still in proper format, without jeopardizing, changing, or modifying the original Hash Code. We have been successful in modifying sections of the ROM so far.

hsbadr had mentioned the following:

"POTENTIAL SOLUTION: BUILDING A KERNEL MODULE TO DISABLE WRITE PROTECTION AFTER PATCHING MEMORY TO BYPASS KERNEL MODULE VERIFICATION AND LOAD OUR UNSIGNED KERNEL MODULE – UTILIZING THE TEMPORARY ROOT ACCESS. WE ARE INVESTIGATING THIS SOLUTION. HOWEVER, IT MAY TAKE A LONG TIME AND IS NOT 100% GUARANTEED !

I'm not a kernel developer so I'm not sure if this is logical. I follow what hsbadr is saying but unclear if it would actually work.

Is this a possibility or would DM verity along with the other sources undo what is changed?

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] PaulPizz:
I believe they're under

dev/block/boot/bootdevice/
[AT&T Samsung Galaxy Note 4] gatesjunior:
Believe it or not, it is.
[AT&T Samsung Galaxy Note 4] ProJ0e:
This feels like Jagex took away the wilderness again Kappa
[AT&T Samsung Galaxy Note 4] KennyG123:
The bootloader is the iron door with the Asgardian Destroyer in front of that. If you cannot get past that, you cannot flash an insecure kernel. T-Mobile, Sprint and international versions are shipped unlocked. They also are not the same hardware-wise.

As for the iPhone...did you not see the FBI petition Apple to get them into the San Bernardino's phone? Even their best hackers cannot get into that.
[AT&T Samsung Galaxy Note 4] Kyuta Syuko:
In the case of the iPhone isn't the issue the FBI is having is the phone's encrypted and if the pin is entered incorrectly 5+ times the data on the phone is destroyed?
[AT&T Samsung Galaxy Note 4] kxhan15:
First of all I have read every detail all over the Internet and even on this site, and I would ask you to tell me what is different hardware wise between the tmobile version an the att version? Or maybe, challenge you to head over to gsmarena and look up full phone specifications. It would seem to me they are exactly the same.

And the whole deal with the fbi and the iPhone is the laughing stock of the jailbreak community right now. Any jailbreaker could get access into that phone in ten minutes. And many jailbreakers have offered to get the info for the fbi. It's the fbi that says unless they get the info thru official means, the info will be considered tempered evidence
[AT&T Samsung Galaxy Note 4] Android.Ninja:
Yes, that's correct. They are concerned that if the password is not entered correctly, The phone will wipe itself, erasing any data they might be able to use.

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] gatesjunior:
It has nothing to do with the hardware. The bootloader and the chip are programmed from the factory to do the verification and checks. So, the hardware is not the issue. It is how they have been flashed from the factory. Just like the DEV devices hardware are the same as well.
[AT&T Samsung Galaxy Note 4] KennyG123:
At just a quick glance according to T-Mobile's own site they do not have band 20 support that AT&T does which shows there are differences. Can you use a T-Mobile Note 4 on AT&T? Absolutely! But they are not identical. You would need to get the component break down of all the chips on the motherboard to see the differences.
[AT&T Samsung Galaxy Note 4] Android.Ninja:
Hello kxhan,

Hardware; they are nearly identical. However, the motherboards inside are different, carrying a various configuration of different chipsets, to meet each carriers protocols, according to the white paper provided by Samsung.

IHMO, they can and do have the people who can hack into the phone. However they are wanting the manufacturer to provide them with an "Official Means" to gain access. That would look more politicaly correct and official, rather than a press releases that reads "After obtaining said device, they gained access by hacking into the device."

I think that it just opens to many doors for invasion of privacy.

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] gatesjunior:
Yes, but to my point. Obviously the band carrier differences on the radios and related chips is one thing, but as far as being able to do something to one device and not another when the hardware is the same essentially is a pointless conversation in this matter as far as what he was trying to elude to.
[AT&T Samsung Galaxy Note 4] KennyG123:
Right. We know for a fact that "essentially the same" and "the same" are 2 different things.

What he is asking is essentially this analogy...2 impenetrable gates are there...one is T-Mobile which is wide open with no locks and the other AT&T which is locked tight with a lock that requires 256 keys to be used in a specific order to unlock it and if you use just one in the wrong order the lock is locked forever (bricked phone). You cannot compare the open gate to the locked gate. There is nothing you can learn from the open gate except maybe which direction it opens :silly: One option is to purchase a T-Mobile motherboard and swap them out.

If you all check the S7's they are ALL shipping with locked bootloaders for the US. So only the international version is unlocked. LG is doing the same...only the T-Mobile V10 is unlocked. Please...for the sake of your own sanity, start considering Nexus devices. This will only get worse before it gets better...and that is killing the US forums and development.
[AT&T Samsung Galaxy Note 4] gatesjunior:
Nice, you and I just talked a bit about the killing of the development and forums, etc.. As you know, agreed 120% on that one.
[AT&T Samsung Galaxy Note 4] kxhan15:
Some, seemingly good info here

https://www.samsungknox.com/en/products/knox-workspace/technical
[AT&T Samsung Galaxy Note 4] Android.Ninja:
Good information, kxhan! I had seen this info as well. While it seems that it wouldn't be all too complicated to compile a kernel which would root a device. Unfortunately, I'm no kernel dev, so I don't really know how realistic this would be, when referring to the locked down Note 4.

I had mentioned this in an earlier post as well.

What is the possibility of a kernel being built that can / would bypass the security check while under temporary root, to eventually achieve permanent root, with a modified aboot, and other modified sections of the ROM. We are working on a way that modifies the original files, while still in proper format, without jeopardizing, changing, or modifying the original Hash Code. We have been successful in modifying sections of the ROM so far.

hsbadr had mentioned the following:

"POTENTIAL SOLUTION: BUILDING A KERNEL MODULE TO DISABLE WRITE PROTECTION AFTER PATCHING MEMORY TO BYPASS KERNEL MODULE VERIFICATION AND LOAD OUR UNSIGNED KERNEL MODULE – UTILIZING THE TEMPORARY ROOT ACCESS. WE ARE INVESTIGATING THIS SOLUTION. HOWEVER, IT MAY TAKE A LONG TIME AND IS NOT 100% GUARANTEED !

I'm not a kernel developer so I'm not sure if this is logical. I follow what hsbadr is saying but unclear if it would actually work.

Is this a possibility or would DM verity along with the other sources undo what is changed?

On the site you linked above, they state:

On most Android devices, the Android Boot Loader does not verify the authenticity of the kernel on the device. Those who want more control over their device can install a hacked Android kernel that roots a device. A hacked kernel provides superuser access to all data files, apps and resources. If the hacked kernel is corrupted the result can be a denial of service. If the kernel contains malware it can compromise the security of your enterprise's data.

Seems like we might be able to possibly get somewhere with root, if we were, to be able to, flash a temp rooted kernel, and then prevent the system checks from overwriting or replacing it until, a final permanent root could be achieved via exploit. superuser install, or etc.

Anyone with some extensive kernel knowledge want to chime in here with some input? Our team has already been able to modify sections of the firmware and flash those modified sections, without losing the original hash code.

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] howellcp:
From what I have read about the Note 3 Root method this is exactly what those guys have done.
[AT&T Samsung Galaxy Note 4] gatesjunior:
This will not work. It is also a signed kernel image as well. And you cannot write to system, permanently, with the write-protection being enabled to even try and load a wp module for the kernel to use. This device is well protected from the top of the boot process all the way down. It will even overwrite system changes while up and running if you have tried to modify it while being rooted without even a reboot.
[AT&T Samsung Galaxy Note 4] jcase:
I'll chime in. A kernel wont impact power on write protection, and your "team" has not "modified sections of the firmware" without losing the "original hash code".
[AT&T Samsung Galaxy Note 4] Android.Ninja:
thank you for your input jcase. My only question would be then why did the hash not change, because we did modify it.

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] jcase:
If you post both files, ill gladly show you they have different hashes.
[AT&T Samsung Galaxy Note 4] Android.Ninja:
Will do, I'll get it fowarded to me and send to you via pm if that's OK? I'm no kernel developer, so any insight you can shed on this would be greatly appreciated. I've seen the hash via remote, and it matches, so unless there's something going on that I'm unaware of or can't see, I think you're the man to look at it, and let us know what's going on. We modified aboot, kernel, etc on temp root, in an effort to see if we could get around the security check. hsbadr had mentioned this possibility as well.

Developers don't need no stinkin' signature!

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

---------- Post added at 09:52 PM ---------- Previous post was at 09:40 PM ----------

According to Team Yemen and also what's posted here on their website, this is how they achieved root on the Note 3. A modified kernel was loaded under temporary root, then specialy written root app is executed to Install superuser / full root. Final flash.

www.androidalyemen.com/vb/

*Edit*

We have decided to consult with someone else.

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] atx84:
Why does this feel like a long drawn out April fools day. Every time ninja says he is consulting with someone known in the community it seems that he is not..he says certain people are on his "team" which are not, he just conversed with them in a thread once or twice

All I see is a bunch of techno mumbo jumbo being thrown out of ninjas mouth, mostly ideas that work on other devices, but no actual....well anything of importance. Seems like he is a team lead delegating work to other people trying to come up with something. Don't get me wrong, it's totally fine not knowing everything and wanting to learn.... but I think your trying to get your name out there kinda the wrong way. That's how I feel with what ice been reading for the past year anyways.
[AT&T Samsung Galaxy Note 4] nemopsp:
You know what? This is kinda funny to read :) I've been wanting to say something my self. Just didn't want to stir up drama, kinda the last thing needed on xda and the note 4 community.

I've seen [MENTION=2260077]Android.Ninja[/MENTION] been posting for months on here an I haven't seen anything from him... just been all talk. One thing is he keeps a positive chat trying to keep hope although at the same time he try to act like a developer when he doesn't have the proper knowledge. Its a good thing that he keep a positive chat tho we need to look at reality, he doesn't have anything. Which is why he won't send anything to [MENTION=2376614]jcase[/MENTION]. He ask for help than changes his mind saying he's unprofessional. To me just sounds like a bunch of bull****.

I don't see [MENTION=2260077]Android.Ninja[/MENTION] or his called "team" rooting this phone. He won't give up the names of his called "team". Also kinda funny that he been quite for months, but as soon as these Yemen developers post something he tries to act like he has something too.

I see Yemen team actually rooting this phone. Bugs me that I can't find much pervious information about them. But they did release a Verizon Note 3 root for 5.0 lollipop, so that gives them a little more uper hand on things. I seen the posted screenshots of the note 4. Although I haven't seen a proof video yet. As they did with the Verizon Note 3, so I feel like we are going to be waiting a couple weeks yet. Even still they can take their time, we have waited this long what is another month.
[AT&T Samsung Galaxy Note 4] KennyG123:
How about I make everybody stop?!!! Very selfish of you all to take up everyone's time watching you measure e-peen sizes and chest puffing.

Thread cleaned and closed until.......

now
[AT&T Samsung Galaxy Note 4] PaulPizz:
Potential root / bootloader unlock may be happening soon!

http://xdaforums.com/showthread.php?t=3346422
[AT&T Samsung Galaxy Note 4] amsgh:
Emphasis on may. But it is a nice glance of hope.

sent from my SM-N910A
[AT&T Samsung Galaxy Note 4] ProJ0e:
Does anyone know if this new update will affect the possibility of this potential root method to work?
[AT&T Samsung Galaxy Note 4] elliwigy:
always is a concern lol this is why its advised to not update right away until said information can be determined
[AT&T Samsung Galaxy Note 4] dkmac:
I was concerned about that as well due to my phone automatically doing the update overnight, but I am thinking that I may be able to odin back since it is still on 5.1.1 and hopefully it will work. Will be able to validate once this is released.
[AT&T Samsung Galaxy Note 4] elliwigy:
just bcuz its the same firmware number (5.1.1) doesnt mean the BL is not incremented.. they can increment the BL in any update..

but goid suggestion on waiting since someone who updated can try to downgrade..
[AT&T Samsung Galaxy Note 4] ShamanVR:
Is their a working root if I dont need service on my deactivated note 4 ? Im on 5.0.1
[AT&T Samsung Galaxy Note 4] Tmobilefan906:
Nope
[AT&T Samsung Galaxy Note 4] joeydcamo:
Someone has successfully booted the note 4 into Download mode and there's more updates in the bounty thread.
[AT&T Samsung Galaxy Note 4] elliwigy:
to be more specific (any note 4 can boot into download mode) a user has booted into DL mode and the device shows as in developer mode (is originally a retail Note 4.)
[AT&T Samsung Galaxy Note 4] Farukh77:
So no body getting root access... :(
[AT&T Samsung Galaxy Note 4] dkmac:
Be patient, the people on the other forum are working on a resolution for the att variant as well, for both permanent root and unlocked bootloader. This is a positive step in the right direction and appears that it will affect multiple phones including ours.

BTW, DO NOT UPGRADE TO MM, Sammy may have patched it to where this method will not work!
[AT&T Samsung Galaxy Note 4] exxTErno:
Good to hear that, I was eagerly waiting for the MM upgrade to hit, i´ll be a bit more patient and wait for root instead!
[AT&T Samsung Galaxy Note 4] nemopsp:
They just released the Verizon bootloader unlock... Congrats for Verizon users

http://xdaforums.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913

Sadly it won't work for AT&T models... we are still in the dark...
[AT&T Samsung Galaxy Note 4] spexwood:
Please don't let this derail the thread. Just 1 answer is all that's needed, not a conversation, debate, etc.

If we do not update to MM (assuming it releases first), and a Lollipop bootloader unlock comes out, then we should be able to: unlock the bootloader via Lollipop, install a custom recovery, intercept the MM update (update.zip), root it externally, and then flash the rooted update?

I do want MM soon. My Moto 360 got it and the battery life improved by 25%. After 8 hours, the battery used to be at 50%, but now it's at 75% after the same amount of time and usage.
[AT&T Samsung Galaxy Note 4] giga8547:
I just read the entire thread on the bl unlock for verizon what im taking from it is that it will not work for att bl because att never released a dev edition of the note 4 therefore the required information is not there.
[AT&T Samsung Galaxy Note 4] HTC_Vivid:
Could someone give an estimate for a possible release, even if it is exaggerated?
[AT&T Samsung Galaxy Note 4] dkmac:
There are some people that are working with that dev to test our phone currently. Remember they were able to do this by using a leak for the eMMc for all newer Samsung phones. I would speculate with the talent that we have on this board that it won't be long before not only our phone, but many others will be fully unlocked soon. Just keep faith, and everyone be positive, because we will have some rocking phone here soon. Again I will reiterate, DO NOT UPGRADE TO MM! Take care
[AT&T Samsung Galaxy Note 4] elliwigy:
in theory it could work actually. CID would need to be changed to that of a vzw dev ed so you can use the aboot and unlock the device..

again this is in theory but let them get it working on vzw first then im sure others will make it happen if possible.

reason i say this is because i asked the devs if i could change my vzw s6e (also no dev edition) to say a international variant to unlock and they said in theory it would work but at the same time i was shot down because s6 and up utilize UFS instead of eMMC so im out of luck entirely but you do have an eMMC device so changing the CID is definitely possible and once CID is changed you can use odin to flash tars from whatever device you changed cid to all be it they are the same type device ie Note 4 is Note 4 s5 is a s5 etc.
[AT&T Samsung Galaxy Note 4] nemopsp:
Yes I heard that the note 5 and s6 can't be done due to it doesn't use eMMC, as for us AT&T users not sure what's going to happen, but I look at it this way they would probably try to get it to work on the AT&T Galaxy S5 first... which some have stated it's worked but no info on how or to true info on it working...

But in theory if they made it work on the AT&T Galaxy S5, they should b able to use same method on the AT&T Note 4.

I just hope they don't leave us AT&T users out of the fun... I hope someone can make it work within the next few months... and if we can't have a bootloader unlock at least a permanent root. All I can say is Verizon users are lucky... its one thing for wait for root this long but it's another they got root and bootloader unlock as a lot of people long ago said it would never happen.
[AT&T Samsung Galaxy Note 4] phaniblaze:
The irony is FBI was able to hack an IPhone. But why not this creepy ATT Note4? I seriously regret for buying an ATT mobile. Will never do that mistake.