yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note 4] raynan:
If you absolutely have be jerks about whatever may or may not be happening, please do it here before this thread gets shut down and development stops entirely...

http://xdaforums.com/showthread.php?t=3073034

I am really sick and tired of seeing this kind if crap anywhere...it does nothing except make the MODs annoyed.
[AT&T Samsung Galaxy Note 4] ZPaul2Fresh8:
Thanks, I didn't see that thread.
[AT&T Samsung Galaxy Note 4] Stryke_the_Orc:
Folks, as with any development, take any claims without absolute proof with a grain of salt. It definitely looks like someone jumped the gun claiming to have root working but incessant posting of doubts and outright flaming are unnecessary. If/when this comes to fruition we'll see, until then leave the guys that do this alone. Messaging other developers isn't going to achieve anything any faster.
[AT&T Samsung Galaxy Note 4] Jspex:
I'm very familiar with you and your reputation :) I've been hitting your thanks button for many years starting back on the first release o.g. Kindle fire.

I do also remember him saying when he pushed to bin he would reboot so maybe (nondev, probably talking out of my ass here) that's the first part of what he was saying. As for the rest,I have not the foggiest.
[AT&T Samsung Galaxy Note 4] thepianoman77:
Blaz. Why haven't you come out and said singing about root? I would have thought that with all the skepticism Blaz would have at least said areasuring word or just say that it didn't work. I know you work hard and I appreciate it, but it would be nice to at least let us know if you're still working on it or not. Just, =/.
[AT&T Samsung Galaxy Note 4] nemopsp:
Just relax, blaz stated in his post "We received root"

Now yea it's very questionable did he?

Where is proof?

Honestly at this point I think many users and even other devs want to see...

Just give it another week hopefully by then we will hear something from him.

Mayb he's decided to make both AT&T and Verizon variance on his own so he gets all the credit?

Plus it was just a holiday so I mean we all have personal life's mayb he got caught up into that for a few days...

I really don't even care for a release, I just want proof that it's real... Then he can take as much time as he needs on building a public release because its one thing to obtain a root, but it's another animal to make it so it works on every devices without issues and not bricking decives.
[AT&T Samsung Galaxy Note 4] elliwigy:
so you tell someone else to chill and maybe hes spending time on real life then go to ask for proof yourself in the same post? smh lol

these root threads amaze me every day haha
[AT&T Samsung Galaxy Note 4] nemopsp:
Honestly I'm just trying to stick up for Blaz...

cause if he received root, he should have a device rooted...

Wouldn't b hard to show 5min or less of proof...

Though I'm patiently waiting like everyone else...

Users are starting to spread rumors, and I'm just trying to stay positive about the whole thing, root will happen in time...

But if he's really trolling the community. It just makes him look bad.. and would lose my respect as a developer.
[AT&T Samsung Galaxy Note 4] xdadevnube:
There really isn't much to talk about here. Most of this discussion belongs in the off topic root thread.
[AT&T Samsung Galaxy Note 4] Venom0642:
Let's please talk off topic over on this thread please thanks: http://xdaforums.com/showthread.php?t=3073034

Running On New Deadly Venom Note 4 v1.2
[AT&T Samsung Galaxy Note 4] KennyG123:
What he said!!!!! I am starting to feel "Unfriendly!!!"
[AT&T Samsung Galaxy Note 4] heXacode:
Folks... none of you are discussing root in ways to help or brainstorm and ideas towards it or discussing anything related to inch us closer to it.

Please take your discussions here...

http://xdaforums.com/showthread.php?t=3073034

Venom0642 just told you that as well as KennyG123, the moderator.

Stop talking about how mad you are or bickering for the 100th time.

There are people working on root still and I have decided to join in and figure out how to get us root. You can see my statement here too...

http://xdaforums.com/showthread.php?t=3073034

I am doing research, learning and gathering info as well as setting up a couple tools tomorrow.

Please have respect on what the moderators have told you folks a hundred times. Discuss root only. That means bring some info to the table for us to look into or help contribute or share ideas.
[AT&T Samsung Galaxy Note 4] stealyourface1:
Umm. This may have been covered before. But boot to recovery, after the Lollipop update, and select "View recovery logs" Volume buttons to scroll thru.

That displays some SERIOUS looking info, and what appears to be a ton of keys, along with telling when it verifies signatures.

Is this possibly some useful info (fingers crossed)??? If that is displaying the actual keys the update package uses........
[AT&T Samsung Galaxy Note 4] heXacode:
The logs are irrelevant at the moment. I did take a look at it and I don't see enough to pursue anything yet for Lollipop. All eyes are on KitKat version for right now because there's a bit more vulnerabilities there than Lollipop. In Lollipop there were a few patches done like to GraphicsBuffer overflow and new securities that will have to be worked around it. My concentration is solely on Kitkat. If root is achieved for Kitkat then myself and others will try to work a similar method for Lollipop or get root/Superuser to somehow survive through OTA which I doubt it will. It will take some time but we will get there eventually.
[AT&T Samsung Galaxy Note 4] elliwigy:
I agree this would be the way to go.. if you can get root on kk then hsbadr has his multizystem ready then you could essentially flash a rooted L rom. This is how it worked for us in the g900v forum.

If there is any way i can help let me know!
[AT&T Samsung Galaxy Note 4] darkbots:
If any of you achieve root. I will show you how to take any ota with root. It's fairly easy and only requires minor alterations to the ota updater plus a zip swap. I've been waiting for root on this device to make any post but... Im not too confident we'll get it. I've been around xda since the first htc evo,and root sometimes just doesnt happen. If it does,I have several dozen mods and touchwiz mods to hand out. I closed my old account a couple years ago due to frustration. Hopefully this time that won't happen. Good luck on rooting,I'm waiting with some awesome stuff.
[AT&T Samsung Galaxy Note 4] TechBSwift:
Does anyone know how kies flashes firmware? Is it the same process as odin? This is way I ask...

The easiest way to obtain firmware for any Samsung device is to connect to kies and restore/flash device. During this process kies downloads the firmware, after firmware downloads kies decrypts the file, resets the phone to download mode and restores the phone. (During the restore process you can copy the decrypted tar file) Unless kies checks the md5 after decrypting the file and prior to pushing the file, what's stopping us from pushing supersu to system file prior to kies flashing the firmware? The window would be very small, but I'm thinking outside the box. I know odin checks prior to pushing the tar file, but does kies follow the same check process?

Sent from my SM-N915V
[AT&T Samsung Galaxy Note 4] heXacode:
Injecting supersu, which would be just an apk, is not enough. It would achieve nothing and there's no way to just push that file in the process you described.

We need to be able to create /system/bin/su for that. In order to do that we need to gain permission to overwrite. In order to gain overwrite permission we need a vulnerability to exploit. The focus is to exploit graphics buffer overflow vulnerability. In order to exploit a buffer overflow on the heap we need to overwrite critical data which will intentionally make it crash or change a value that can be exploited later. This is the main goal of mine that I'm looking into from what others were trying to do.

Read this...

https://developer.apple.com/library...cureCodingGuide/Articles/BufferOverflows.html
[AT&T Samsung Galaxy Note 4] cornflaku:
Would it be possible to cause an overflow within the AT&T Mobile Locate app? Maybe the backup function. IIRC some of the 'features' it boasts require write/overwrite permission.

Maybe it's possible to create a tunnel to mimic backup server via usb tethering/turn off mobile data.
[AT&T Samsung Galaxy Note 4] jocarog:
Any way to exploit the my files apk? It is the only way to write to external SD which third party apps can't do without root access...

one'd frome my one+1
[AT&T Samsung Galaxy Note 4] raynan:
I think what [MENTION=3508760]heXacode[/MENTION] is trying to say is that even though they are system apps and have more access, it's not enough to write into the system other than maybe it's own odex file...it would most likely have to be a system process running at root level that needs to be "hijacked" and used to write a specific file in a specific location.

Correct me if I'm wrong.
[AT&T Samsung Galaxy Note 4] heXacode:
Correct in a way. What I'm looking in is located in /system/framework where much of the stuff is taking place and from lib.

They have much of the stuff pieced together in this screenshot...

I need to look at the PoC and CVEs mentioned and see what is going to be altered and maybe go from where they left off. They supposedly have all they need but jcase states that it will need a way to drop to root shell and inject supersu. Without that he states that it'll probably do nothing but restart the device. All that will have to be combined together and a script has to made to tell it what to do then and after.

I have to read through all that thoroughly and understand what it all does and if it will do anything at all. I'm starting to understand all they were looking into and trying to do but I cannot just jump in and attack it right away till I understand the function of all that.

There's a lot of info to process through this but it's slowly clicking together to better my understanding of it.
[AT&T Samsung Galaxy Note 4] elliwigy:
Thanks for some further clarification.. maybe check with the other devs and work with them? just a suggestion as its always best to work as a team vs. on your own.
[AT&T Samsung Galaxy Note 4] heXacode:
That's what I would love to happen because it would speed up the learning process for me versus going at every far reaching angle to learn one thing and connect it to another. It seems like most of them have disappeared so I have no idea.

I'm just doing what I can to inch us closer till more people come to help. Most of them probably won't talk to me directly cause they have no idea who I am which is ok and understandable if that's the case.

[MENTION=2376614]jcase[/MENTION] [MENTION=4558078]ZPaul2Fresh8[/MENTION] [MENTION=3975929]zxz0O0[/MENTION] [MENTION=3669069]idler1984[/MENTION] [MENTION=3178012]gatesjunior[/MENTION] [MENTION=2260077]Android.Ninja[/MENTION]
[AT&T Samsung Galaxy Note 4] Kyuta Syuko:
Most of the Devs seem pretty open to helping people learn so long as the one learning has a willingness to learn.
[AT&T Samsung Galaxy Note 4] Surge1223:
Wrong thread
[AT&T Samsung Galaxy Note 4] ZPaul2Fresh8:
[MENTION=3669069]idler1984[/MENTION] is your man after getting system privileges.
[AT&T Samsung Galaxy Note 4] jorgasm209:
Also some interesting reading Here on CVE 2015-1474 in the Kindle Fire forum. Looks like some progress was made, but then it just died off. Perhaps [MENTION=4276415]p1gl3t[/MENTION] or [MENTION=3556718]Phate123[/MENTION] could help further explain any possible avenues they discovered?
[AT&T Samsung Galaxy Note 4] Surge1223:
Oh I had not seen that.... Interesting...
[AT&T Samsung Galaxy Note 4] Thoth7475:
Is it possible to buy whatever chip or board that's different in a dev edition or tmobile phone and replace it in an att phone so it would be rootable?

Just a thought I had today

Sent from my sad unrooted SAMSUNG-SM-N910A locked by those bastards at at&t
[AT&T Samsung Galaxy Note 4] vdub12:
I beleve the screen has to be removed to get to the motherboard. It would be a hard swap.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
It's easy to get to the motherboard of these phones and it wouldent help cuz all you would be doing is changing cases really the radios and antennas would all still be the same and sometime the cases have small differences that won't let you swap. Pieces

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] heXacode:
Changing motherboards will do nothing. That is all hardware. Root is all in the software area. Do not attempt to try that.
[AT&T Samsung Galaxy Note 4] JoseGR52:
Since all Android versions before 5.1 are vulnerable, does that mean if there's a root for Kit Kat then thered also be one for lollipop? Or we still gonna need to downgrade?
[AT&T Samsung Galaxy Note 4] wolfy287:
I'm not sure but I have the stock firmware for kitkat if ur looking for the stock firmware zedomax has a website with all the stock firmware
[AT&T Samsung Galaxy Note 4] stealyourface1:
link?
[AT&T Samsung Galaxy Note 4] Venom0642:
http://xdaforums.com/note-4-att/general/roll-to-4-4-4-5-0-1-ota-t3063452
[AT&T Samsung Galaxy Note 4] heXacode:
Just a quick question... what are some of you, that are working on root, using as programs to work with? I'm in the process of converting to Linux Mint since windows 8.1 is giving me so many issues. I also am using Android Studio for some things but I haven't been able to find anything on what other devs use besides Notepad++ for little things. I know command prompt is also used for other things but I figured people use programs for better interaction with readouts and stuff to work in.
[AT&T Samsung Galaxy Note 4] jolly_roger_hook:
I would contact surge1223 he helped me with setting up Linux mint with alot of stuff you would need for Android development he's a wiz when it comes to linux

Sent From The EDGE
[AT&T Samsung Galaxy Note 4] ZPaul2Fresh8:
Linux Mint and Sublime for coding. Atom is also good.
[AT&T Samsung Galaxy Note 4] heXacode:
Ok. PM sent to him. Thanks for the info.

Noted and thanks for the info.
[AT&T Samsung Galaxy Note 4] taz44410:
Tmo and att parts are interchangeable

But as mentioned it's hardware change so will not help with root for att
[AT&T Samsung Galaxy Note 4] vsn4:
CVE-2015-2824

Published : 2015-04-06

Multiple SQL injection vulnerabilities in sam-ajax-admin.php in the Simple Ads Manager plugin 2.5.94 and 2.5.96 for WordPress allow remote attackers to execute arbitrary SQL commands via a (1) hits[][] parameter in a sam_hits action; the (2) cstr parameter in a load_posts action; the (3) searchTerm parameter in a load_combo_data action; or the (4) subscriber, (5) contributor, (6) author, (7) editor, (8) admin, or (9) sadmin parameter in a load_users action.
[AT&T Samsung Galaxy Note 4] taz44410:
I only have a basic knowledge of jtag that being said

Would there be any way to attain root through a a modified jtag process
[AT&T Samsung Galaxy Note 4] StayingSober:
And posts like that my friends is why this thread has been locked by mods before, and on track to being locked again.
[AT&T Samsung Galaxy Note 4] jcase:
This has nothing to do with android...
[AT&T Samsung Galaxy Note 4] vsn4:
Oops sorry I realized that after I posted but then couldn't figure out how to delete!! Sorry again
[AT&T Samsung Galaxy Note 4] cepsbow:
Yea, it's called vim/nano/emacs. That's where all the magic happens in *nix anyway, GUI is overrated and typically slows down workflow. Learn to live by the commandline, it's your friend.
[AT&T Samsung Galaxy Note 4] vdub12:
this may be a stupid question and if it is I apologize in advance. can't we just root this phone manually with adb?
[AT&T Samsung Galaxy Note 4] nyydynasty:
if it were only that simple
[AT&T Samsung Galaxy Note 4] Android.Ninja:
Already tried and currently not possible.

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] AtlAndroid:
Can one of you guys educate educate the rest of us as to why? It seems that ADB and/or kies can do just about anything to the phone, except insert su. why is that?
[AT&T Samsung Galaxy Note 4] ZPaul2Fresh8:
Because as soon as you boot the phone it is write protected. It's called a locked bootloader. Protected by keys which are encrypted. 512 bit I believe, can't remember exactly.
[AT&T Samsung Galaxy Note 4] JoseGR52:
How difficult would it be to learn how to root devices?
[AT&T Samsung Galaxy Note 4] AtlAndroid:
I'm not certain about ADB, but KIES writes to the system area post boot.

Furthermore, you can have root on a locked bootloader. Many phones do. All you need is the ability to insert SU.
[AT&T Samsung Galaxy Note 4] ZPaul2Fresh8:
Right, but phones that have root with a locked bootloader are the result of successful exploits that were written to gain write privileges to "insert" su into system.

Furthermore, firmwares have a digital signature, if it's invalid then the phone will reject Kies or Odin flashes. dmverity I believe is the term I found in the bootloader images.
[AT&T Samsung Galaxy Note 4] vdub12:
I don't know if this means anything or not but just playing around I pushed the SU binary to /data/local/tmp and changed the.permissions to 6755 and tried to run it and didn't get any permission denied error. I still had a $ prompt and not # but it didn't register permission denied. I tried remounting /system/ as rw with busybox after and it did deny me.

Its like so close yeT might as well be a million miles away. If we could just run one command we would have root.
[AT&T Samsung Galaxy Note 4] ZPaul2Fresh8:
You're not close at all. Been down this roads months ago. The latest exploits like the one from Retme7 and others which use the 7911 cve use this method to execute their exploits.
[AT&T Samsung Galaxy Note 4] AtlAndroid:
The first paragraph is non-responsive to the question. The question is not how had it been done previously, but why can ADB and KIES seemingly write to the system area but not insert SU?

The second is partially responsive. I'm not discussing ROM flashes, I'm talking about file level modifications while the OS is running. KIES does this during backup/restore, doesn't it?
[AT&T Samsung Galaxy Note 4] ZPaul2Fresh8:
I clearly answered it, but let me explain it a little easier for you. If you can write to system with ADB then you already have super user. I've only used kies once in 5 years. You cannot write to system at all unless you have su.

The only system writing without root would be while a flash is being performed with a signed packaged.
[AT&T Samsung Galaxy Note 4] AtlAndroid:
Thank you for clearing that up.

The question is NOT "can I?" The question is why can't I, especially considering the current version of KIES appears to write to areas restricted to processes with system level privileges.
[AT&T Samsung Galaxy Note 4] warriorpluto:
Has to be a missing link somewhere in the kies software to allow us to do something.
[AT&T Samsung Galaxy Note 4] raynan:
So does ADB compared to the user; I think it just runs with higher privileges that aren't quite system.
[AT&T Samsung Galaxy Note 4] AtlAndroid:
But there aren't "levels" in *nix. You either have write permission or you do not. You either are root, or you are not.

Perhaps they have rw to lots of "sensitive" areas, just not /system. But does SU have to live in system? Not on any other flavor of *nix. SU itself runs with root perms.

So what's different here that I'm missing? Perhaps their are angles us sysadmin types can run down while the developers are working on the more sophisticated techniques.

Put 3000 monkeys on a tank and sooner or later one will crank it.

I tend to think so. Every piece of software has undocumented admin features. But obviously better men than I have tried and failed. I would like to understand why for my own edification. Root 101 class...
[AT&T Samsung Galaxy Note 4] raynan:
Aren't there different users with different permissions, ie. Root, user...?

Or am I thinking of shell commands?
[AT&T Samsung Galaxy Note 4] AtlAndroid:
As I understand it, outside the kernel you are either root or you are a user. Obviously file permissions vary by user, but
[AT&T Samsung Galaxy Note 4] raynan:
Ahh, I see. Thanks. Guess I'm still thinking in terms of the system.
[AT&T Samsung Galaxy Note 4] AtlAndroid:
If you think I'm wrong, please say so. What I'm stating is only my understanding, and based on non-android *nix. As such, it is certainly -not- authoritative on the subject.
[AT&T Samsung Galaxy Note 4] raynan:
Not at all. I'm just trying to turn this problem into a learning opportunity for myself.
[AT&T Samsung Galaxy Note 4] AtlAndroid:
Ditto.
[AT&T Samsung Galaxy Note 4] ryanmclamb4:
As much as I tend to agree that having more knowledgeable people in these forums will greatly help our chances of achieving root.... This thread is however for the purpose of root progress, and not really intended to be a tutorial.
[AT&T Samsung Galaxy Note 4] vdub12:
I didn't mean to open a can of worms here with my question about adb. However, adb clearly uses a different account.

For instance I can't even run ls on /data/local/tmp from a console on the phone or even through SSH on the phone but I can, and have full write permissions, on the same directory in adb shell. Being adb is open source couldn't we just try and change the user adb uses?

What's stopping us from running adb as system or even root? Has this angle been explored?
[AT&T Samsung Galaxy Note 4] taz44410:
May be a dumb question

Is there not a way you access the Odin tar and inject su without breaking the original signature

I know there is a way to convert it to another format just not sure if that'd break the signature
[AT&T Samsung Galaxy Note 4] jinx10000:
That was done before when they found an exploit in the signature process that allowed them to attach a specific length of extra data. I remember it being used to root an older device (Original Droid maybe?). But that hole was patched and I don't remember many details. Plus it was device specific at bootloader level if I remember right.
[AT&T Samsung Galaxy Note 4] taz44410:
Thank you for the info

I love learning new stuff

I aspire to be a dev one day and that'll never happen if it don't learn
[AT&T Samsung Galaxy Note 4] spexwood:
I was just thinking something similar, but with Kies.

Capture an update after its downloaded (it has to be somewhere on the computer once downloaded), crack it open, inject SU, fix SU permissions, fix signature, close file. Then replace the original with the modified file and let Kies install it.

On paper, it'd be easy to do.

In practice... I can't begin to know.
[AT&T Samsung Galaxy Note 4] scoder:
Doesn't work like that. Repackaging the update with ANY differences will change the checksum of the package, and the install will fail at the key verification stage.
[AT&T Samsung Galaxy Note 4] bobloblaw1:
Yup exactly. Which is why I had the idea about adopting the QDLoader root process which breaks the bootloader and the check and has been successful on locked Motorola devices. But, we don't have fastboot and Odin reintroduced the checks I believe.... Easy on paper indeed

If anyone can figure how to adopt the process, and the following is my understanding of it. The important part appears to be breaking the bootloader so the device boots in an extremely low level mode:
[AT&T Samsung Galaxy Note 4] gatesjunior:
Let us not forget about adb backup and restore. That in fact, can and will write to the system and data without root. Look into it. I have already mentioned this a month or two ago about looking into a vulnerability with this. Now, is it system/app or system/priv-app ? Sure, but still in system.
[AT&T Samsung Galaxy Note 4] spexwood:
Like I said, on paper, it'd work. ;)

Can't you just regenerate the checksum based on the modified package though? When I used to get Clockwork Mod backups that were good, but always failed at the md5 check phase, I used to just regenerate the md5 and then the backup would restore.