yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S6] N920a root:
Answering your question

Its not necessary to run a root install command to make the rom boot up. The rom that i modified and flashed boots up and powers off like a normal phone. What I have done was copy and paste/overwrite the original rom build prop by putting the build prop from the combo bootloader into the rom which keeps it at permissive so it can be easily rooted again with kinguser after flashing the rom. Then you can easily change kinguser to supersu again using the terminal emulator method.

The other important ant things I had to put in the build prop was set factory binary to 0 and save. Also change ro.securesupport=true in had to change it to false and save.

I have done a lot of modifications to the original noble zero rom posted on XDA to make it work over the N920A 4APL1 Combination bootloader. To answer your question I am just talking about the build prop hack method I have used. I have done the modifications using root browser classic app it's great and easy to use. To also make a rom boot up you must add libs from the combination firmware that are not in the rom to the rom that you want to boot up.

I see you have only rooted with king root but what you must do is change it to supersu root using the terminal emulator method. The reason you need to do this is because the flashing tool for flashing roms etc is flashfire app and flashfire will only works with supersu root and not kinguser. Here is a short YouTube video with all the file links in the description necessary for Rooting N920A 6.0.1 along with the Rooting procedure and the link for the modified rom I successfully installed and booted up https://youtu.be/J6GXvtxq2aA
[AT&T Samsung Galaxy S6] oo3rex:
Guide works great, thanks! Have a couple problems though, wondering if anyone else is having trouble with the fingerprint sensor and wifi disconnecting.
[AT&T Samsung Galaxy S6] JfkJavi:
Working on 5.11 BV Boj9 (3/3/16 update)

Got it working after using the method [MENTION=6995376]dreamyy5[/MENTION] used After running root-Boot.cmd I opened up SuperSu and it said there was no bin installed. Closed and reopened and browsed the settings then checked root checker and it worked. Fingerprint scanner doesn't work, wifi is glitchy, & no knox changes.
[AT&T Samsung Galaxy S6] gursys:
Yeah, I'm having the same problem where is says the su binary isn't installed. What should I do? Root checker is saying that root isn't properly installed as well.
[AT&T Samsung Galaxy S6] metalcated:
WiFi and Fingerprint Sensor is probably related to the Kernel and unfortunately there is nothing I can do about that at this time. The kernel was a leaked kernel and may not work with all of the 5.1.1 builds or any that enables WiFi to be consistent without a data wipe and the fingerprint sensor working at all. I did notice that recently while trying to add a fingerprint but haven't had a chance to look into it. Again there is probably nothing I can do because its kernel related and without an unlocked BL, we cannot flash another kernel. I can try to flash a different kernel but I am certain I will get a teal Sammy screen saying unauthorized software detected. Kernels, BL, etc all need to be signed if the BL is locked.

As for Knox, the scripts that enable root don't remove Knox, you'll have to do that or Flash the bloat free ROM in the OP with Flashfire.

[MENTION=7339599]gursys[/MENTION] If you need help I can assist as I have done for others, same goes for anyone else as I have free time. One thing you can try is run the following command once you have your phone booted up:

adb shell "if [[ -z `ps -x|grep daemonsu` ]]; then /system/xbin/daemonsu --auto-daemon \&; else echo ". daemonsu already running"; fi"

Let me know it goes! :good:
[AT&T Samsung Galaxy S6] gursys:
Havent been able to try out the code. Tried rebooting and phone is stuck on att logo. :(

---------- Post added at 10:01 PM ---------- Previous post was at 09:54 PM ----------

Also, at what point during the boot process should i run the code for root boot?
[AT&T Samsung Galaxy S6] JfkJavi:
As for the rom do I have to load up the boot script before launching?
[AT&T Samsung Galaxy S6] metalcated:
As soon as it reboots. Did you also see the part about Windows drivers? Have you tried that?
[AT&T Samsung Galaxy S6] metalcated:
Yeah the process for booting is the same.
[AT&T Samsung Galaxy S6] gursys:
Am I supposed to be using some sort of drivers? Everything was working fine so far... Also, I run the script before the phone boots, but it still hangs at the att logo.

---------- Post added at 10:12 PM ---------- Previous post was at 10:08 PM ----------

I am currently reflashing a oj7 recovery that I found on another thread; will see if that works. Also, in the original guide, when you mention going into developer mode before continuing, is that when you tap the build number 7 times? Thanks a lot for your help!!
[AT&T Samsung Galaxy S6] metalcated:
The hang is due to selinux being enforced, the boot script (root-Boot.cmd/sh) is what changes selinux to permissive so the phone will boot all the way up. If you get stuck at the ATT Logo, hold vol+up, vol+down and power until you see the post logo to force reboot the phone and try again to boot leaving the script open and waiting.

Yes Developer Mode. That is correct.
[AT&T Samsung Galaxy S6] gursys:
I tried but it is still getting stuck at the att logo. Maybe it is because I uninstalled the adb drivers as you posted in the original post... not sure.

---------- Post added at 10:39 PM ---------- Previous post was at 10:36 PM ----------

its also showing waiting for adb to connect in the boot script
[AT&T Samsung Galaxy S6] JfkJavi:
Where it at doe?

I don't feel like I'm doing this right but the rom doesn't show when looking for a .zip to flash in flashfire
[AT&T Samsung Galaxy S6] metalcated:
Don't uninstall the drivers completely, it shows to remove the driver and then rescan for new hardware so it picks up the phones adb again and begins the boot. It doesn't always do that but I did notice it happens a lot with the Samsung drivers.
[AT&T Samsung Galaxy S6] metalcated:
Where did you get the package or files your trying to flash?
[AT&T Samsung Galaxy S6] gursys:
Yeah, I think they automatically reinatalled, but the boot script hasn't been working and my phone is still stuck on the att logo.
[AT&T Samsung Galaxy S6] metalcated:
Lets take this off the forum into a PM, I will help you get this going.
[AT&T Samsung Galaxy S6] JfkJavi:
"g920a-5.1.1-rooted-debloated~metalcated.zip"

This one right here. I have both a .zip and a folder with the files and the only thing I can flash is the twrp.zip
[AT&T Samsung Galaxy S6] metalcated:
You unzip that directory and place it in the Flashfire recovery directory on your sdcard. Then open Flashfire and select a restore using this image.
[AT&T Samsung Galaxy S6] tuttle36:
Install went as expected. The Samsung mobile phone drivers seem to play nicely with Windows 7. I had not made any backups with Flashfire previously so I did not have a backups folder assigned by it, made a backup and then the directory shows up in SDcard. Also, it seems that the power volume (+) and home button combination give the best reboot option for me. Many thanks, and hopefully this evolves.
[AT&T Samsung Galaxy S6] shiacer:
Oh my gosh!sooo many thanks!

A question, can we install xposed framework after this root?
[AT&T Samsung Galaxy S6] Apexseal:
Great work! Awesome!
[AT&T Samsung Galaxy S6] metalcated:
I wasn't successful in getting it working thus far. Sends the phone into death mode! - causes me to have to reflash the system partition via Odin. I'll keep at it but so far no luck.
[AT&T Samsung Galaxy S6] Jimm.007:
So, if I understand, each time I woud like to boot my phone, it will stuck untill I plug it on a PC and run the cmd ?
[AT&T Samsung Galaxy S6] JfkJavi:
I actually got xposed framework to install and work. I used http://xdaforums.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 and flashed it over using flashfire. The only problem I was having with it was snapchat wasn't working went to uninstall framework via uninstaller.zip and phone was softbricked on att logo. Then booting cmd would go through but it would still hang at the logo.
[AT&T Samsung Galaxy S6] Alex311360:
You're now one of my new favorite people on xda-developers.

Root absolutely works, and so does the debloated ROM! Works much faster now and I'm glad to be able to have my root on something that seemed impossible! Thank you so much!! :D

I'll edit this post when I get this working -- just flashed and rebooted. It's optimizing apps, so maybe that's a sign??

EDIT: Xposed works, I won't uninstall it though because of the mentioned reason.

Amplify appears to work just fine -- it passed the Xposed test and appears to be doing its job.
[AT&T Samsung Galaxy S6] metalcated:
I was actually using a different method, this is good. I can use this to try and force selinux to permissive. I'll give this a try later and see what's causing the boot hang. I got that too which is why I said it doesn't work but you seemed to have gotten further.
[AT&T Samsung Galaxy S6] metalcated:
Yeah it's kind of a pain but that's the only way to do this at the moment.
[AT&T Samsung Galaxy S6] JfkJavi:
Yeah it was working fine till I uninstalled. Can't get it to root no more cause something is causing it to hang on att logo. After fresh odin restores and a BV downgrade to oj7 from oj9 I can't get it past the logo.
[AT&T Samsung Galaxy S6] shaneg79:
What about this root method? Has anyone tried it? http://samfirm.net/threads/kernel-root-android-5-1-1-galaxy-s6-edge-sm-g925a-at-t.59/
[AT&T Samsung Galaxy S6] Alex311360:
The method in this thread (as in on here, xda-devs) already is a mix of SamFirm and other things, so...
[AT&T Samsung Galaxy S6] shaneg79:
Thanks! Just curious because so far from what I read on here no one has achieved full root but that site doesn't say that you have to use adb every time you boot up.
[AT&T Samsung Galaxy S6] jrtran:
Thanks OP for this rooting. It works great! Can i use this for rooting G925A with out flashing the sboot file? Or do you sboot for 925A so i can try?
[AT&T Samsung Galaxy S6] metalcated:
I don't have a specific sboot for g925a but its possible someone could try to use this sboot to accomplish the same. I don't know if it would be different or cause an issue. But I would recommend if you are going to try this and it does flash and causes an issue that you have a Stock version available to flash over and fix the issue. Also be aware that if you do flash this there is a good change you could bit lock your bootloader and be stuck with this version and newer of a bootloader. What this version represents to the non-eng BL, I am also not sure. I would recommend you proceed with caution. Risk is half the battle with doing this stuff ;)
[AT&T Samsung Galaxy S6] zimgir124:
Any chance of this being made to work on any other variant?
[AT&T Samsung Galaxy S6] notobsessivejustcurious:
Greetings,

this is what I'm getting too, what was the remedy for this.

much obliged

0J9 920A

odin went through

status : custom, but no root root checker says no, and of course SU says no binary
[AT&T Samsung Galaxy S6] elesbb:
If someone hasn't already posted it:

Try this to make selinux permissive on each boot.

1. Create the following directory if it doesn't already exist:

/system/su.d

2. Create a file inside that directory named "selinuxpermissive.sh"

3. Open that newly created file, and add this inside of it:

#!/system/bin/sh
su
setenforce 0
exit
exit

4. Set the file's permissions to "rwxrwxrwx" via command line as well as the newly created directory:

chmod 777 /system/su.d{,/selinuxpermissive.sh}

5. Reboot.

You should now have selinux set to permissive on each device boot. Give me 15 minutes and I'll create an app to do the above mentioned in one click of a button.
[AT&T Samsung Galaxy S6] flar2:
I have a Galaxy S6 temporarily. I can't trip knox on this device and it has to go back to stock state.

Build number: LMY47X.G920W8VLU3BOJ7

Can I try this without tripping knox and uninstall root to go back to completely stock state?

The directions are not very clear.
[AT&T Samsung Galaxy S6] jrtran:
Just rooted mt S6 edge G925A baseband BOJ7 with this with out flashing the sboot. Thanks again OP. Good to go guys
[AT&T Samsung Galaxy S6] shiacer:
Thanks for your quick reply!
[AT&T Samsung Galaxy S6] elesbb:
From what I got, I don't even have an S6, just trying to help, it will NOT trip Knox (judging from his picture in the beginning posts)
[AT&T Samsung Galaxy S6] flar2:
I saw that, which is why I'm looking into this.

I'm just really not clear what exactly we're flashing in ODIN.

Do we need to flash both the sboot and kernel for this to work? Are we flashing the sboot simply to get the correct sboot version or is it modified?

I assume the kernel is modified, so would need to be flashed. Is there a stock version that can be flashed back, or is this just flashed temporarily to get root (since the bootloader is still locked) .

I'm also unclear about when the scripts are run.

It seems like it should be simple, but I'm very confused by the instructions.
[AT&T Samsung Galaxy S6] metalcated:
I updated the main post, Xposed does work and I am working on Deodexing this ROM and to possibly begin making some modifications. We will see! ;)
[AT&T Samsung Galaxy S6] elesbb:
Without decompiling anything, it appears that the modified sboot allows the modified boot.img to be flashed. If you need to restore to stock, just download the stock tar file and it will put EVERYTHING back to stock. All at once, takes about 10 minutes or so. But yeah, it looks like a modified kernel and sboot partition are being flashed in odin.

Then once the stuff is flashed in Odin, then run the root-install scripts to actually obtain root. It looks like from that script, that the kernel gives temporary root privileges which allows you to fully install the su binary and everything else that normally gets done through a custom recovery flash.

But like I said, getting the fully stock from Samsung tar file (can usually be found on Sammobile) will set you back to complete stock. Even with a locked bootloader, you should be able to flash a factory signed image to it.

My question to the OP:

Why don't you put the necessary scripts into the boot.img ramdisk and have them executed by the kernel itself? Or does the device need to be fully running before installing the su stuff? Couldn't you do it on post init then? Or in the very last line of the init.rc?
[AT&T Samsung Galaxy S6] Lilchampsean:
Goodluck, I'll be happy to check in on this from time to time.
[AT&T Samsung Galaxy S6] robikonobi:
Were you able to use the g920 files that were posted by the op or did you have to mix it up with other g925a files to get it to work on your g925a? Did you need to modify the files or script to get it working on your g925a?
[AT&T Samsung Galaxy S6] flar2:
Knox tripped, warranty void, and bootlooping. Yay.
[AT&T Samsung Galaxy S6] elesbb:
From what I read, bootlooping is caused by the selinux not being permissive. I think while its bootlooping you need to use the boot script.

Weird how it tripped knox for you and not the OP..... I figured a modded kernel would cause knox to trip, but then again, it is probably a modded ramdisk and not a full custom built kernel, so I wasn't sure.
[AT&T Samsung Galaxy S6] flar2:
I could go in with adb shell and poke around, as root. Still won't get past the bootanimation even in permissive mode.

I guess I'll have to reflash the system or soemthing.

Oh well, I guess I'll be keeping this s6 now, although it's not much use to me without kernel source.
[AT&T Samsung Galaxy S6] notobsessivejustcurious:
Are these instructions for in general, or for making the script install su. The kernel loads up and boots,but su files are not in any folders. Still learning here.
[AT&T Samsung Galaxy S6] meraz9000:
This is just the engineering kernel floating around for months with insecure adbd enabled which allow you # root shell access...obviously as this point is a "tethered" root which means is not very convenient. Don't expect a full root without being able to flash a real custom kernel but we all know that wont happen because of the locked bootloader and won't trip your knox because this kernel was made by Samsung
[AT&T Samsung Galaxy S6] elesbb:
Sorry man :/ don't know what else to say.

What I posted does nothing but makes the selinux to permissive on boot. It will not install su.

Well according to a few posts up it does trip knox.

But thank you for clarifying what the heck is actually happening lol.
[AT&T Samsung Galaxy S6] Rick1684:
The script he is referring to making is to put in system after the phone is already rooted in hopes that after the sh script is in place that it will make the phone boot permisssive at every reboot thus allowing to reboot and if phone dies or whatever you wouldn't have to do all the adb criznap
[AT&T Samsung Galaxy S6] flar2:
I should have checked more carefully, my firmware didn't match exactly with this, so that's probalby why knox was tripped for me.
[AT&T Samsung Galaxy S6] shichemt:
After trying to root my S6 twice, I ended up getting stuck in a bootloop every time.

If you messed up or got stuck in the boot animation (like me) and don't know how to restore your device back, here's how:

1. Go to this thread and download the file.

2. Restore it using ODIN 3.10.7. (older versions didn't work for me).

3. Wait couple minutes, the device will reboot. Wait another 5-10 minutes and that's it.

If the root tripped your KNOX, don't worry by restoring it to stock, it will get back to 0x0 (at least that what happened in my case).

Finally, I guess the only option left, for me and fellow S6 users who are stuck in a bootloop, is Systemless Root.

I would also like to thank @metalcated for taking the time and helping me trying to make it work.
[AT&T Samsung Galaxy S6] PMDColeslaw:
Sorry for asking, but are you guys sure is actually tripping Knox and not just giving you the warning and asking you to reboot? That's not the same thing. Knox is still 0x0 when you get that warning.
[AT&T Samsung Galaxy S6] vang2k:
tried the .tar method in AP slot and than did the root install bat than restarted. after i run root-boot but it just hangs on the AT&T screen? how long do you have to wait on the boot?
[AT&T Samsung Galaxy S6] billa:
That makes perfect sense why an auto enabled root script cannot be patched into the kernel. It's only manual or nothing, for now. However, still useful for those who wish to tinker.
[AT&T Samsung Galaxy S6] notobsessivejustcurious:
Greetings, I saw that you were on OJ9, too, so am I. you had the same issue as me, But metalclad pm you to do a private session, I guess. would you share the info? or did he specified not to? Did you get it working? :)
[AT&T Samsung Galaxy S6] flar2:
Mine is 0x0301

Believe me, this is 700 bucks I did not want to spend. On the positive side, all my apps will start working perfectly on Samsung in the next week or two.
[AT&T Samsung Galaxy S6] PMDColeslaw:
I used the recovery files from the OP to Odin back to OJ7 and then was able to achieve root. You'll still get the Knox warning until you flash the debloated version or manually remove Knox yourself. Knox should stay at 0x0 though. You'll also lose data [factory reset] when you Odin OJ7. Metalcated was a huge help. I recommend sending him a PM.

---------- Post added at 07:14 AM ---------- Previous post was at 07:12 AM ----------

What build were you on?
[AT&T Samsung Galaxy S6] elesbb:
Ahhhh. Yes that would do it. The bootloader's signature for the kernel didn't match that for which was installed. Well hopefully restoring to stock will clear the KNOX counter, but I have never heard of that before.
[AT&T Samsung Galaxy S6] metalcated:
If you look at the installer script, it actually does this and I had hoped it would also work but it didn't :-/ - Thanks for throwing this out though, working towards a full root is what the end goal is!
[AT&T Samsung Galaxy S6] metalcated:
Sometimes with Windows the drivers don't work or its some other thing that doesn't work. Either way removing the driver as shown in the OP will get you past this point. I have found that I need to do this nearly every time and its becoming a bit of a pain! So I am working towards getting past this in some way or another. Its a slow process since I also have my normal Job that is demanding as well as 5 children to Juggle ;)

I also want to thank the others who are also helping answer peoples questions in this thread, this is great community and another reason why I enjoy doing this stuff! :good:
[AT&T Samsung Galaxy S6] metalcated:
What have you tired up to this point in resetting Knox? This is a first for this method.

Please provide as much details about your phone that you can so we can help you get things back up and working!
[AT&T Samsung Galaxy S6] flar2:
I was under the impression you can't reset Knox?

Anyway, it's my fault for attempting this on a 920w8. I reflashed the stock firmware and Knox is still tripped.

Is there any work being done on resetting Knox? If so, this is the type of challenge I like, but I want to see what others have attempted first. I heard it was an efuse, which would be impossible to reverse, but is this confirmed?
[AT&T Samsung Galaxy S6] metalcated:
Ah I see yeah your phone is a different variant. Well I also have not seen anyone come back from a Knox trip on recent phones. But everyone also said root was impossible on this phone so I would say anything is possible. BUT! Do you have the time and patience to wait it out? Something that could never happen? Anyways, questions to ask yourself.

Are you able to do anything with your phone besides turn it on? Can you get to Download mode?
[AT&T Samsung Galaxy S6] flar2:
My phone is fully restored and working. I've been around the block a few times.

I was asking about knox reset because I was thinking about taking a crack at it, now that I have a Samsung phone to play with.
[AT&T Samsung Galaxy S6] elesbb:
It should work if that is all that needs to be applied. I would add a test line to it to ensure its being executed. Something simple like "echo "test" > /data/test.txt" to make sure the script is running. It could also be running too soon as well. But this is the script I need to enable my phone to have selinux permissive. So putting a delay on it could work.

But, if you have root, using the tethered method with the insecure adbd, then you should be able to dd some images to the proper partitions. This will 100 percent trip knox though because it detects a different kernel/recovery at boot.

Like in your install-root.cmd you could have the adb shell push a new recovery image to the /data/tmp directory, then mount then dd if=/data/tmp/recovery.img of=/recovery/block/goes/here (don't actually type that, I have no clue what the actual partition is for the recovery) then you can disable the install-recovery.sh script. Heck, try putting setenforce inside the install-recovery.sh script.
[AT&T Samsung Galaxy S6] therealduff1:
I have the time to develop this, but i dont actually have an s6 to test it on. And i wouldent want to go breaking anyones device during the testing ;)
[AT&T Samsung Galaxy S6] Adrao123:
Can't you make a startup script while having root in the init.d folder,

with

setenforce = 0

???
[AT&T Samsung Galaxy S6] rockrack:
thank you so much !!!
[AT&T Samsung Galaxy S6] virulentt:
I'm really wondering how you thought a AT&T trick would work on your canadian variant. If you would have read forums more carefully, our phone is similar to T-Mobile...
[AT&T Samsung Galaxy S6] flar2:
I have a whole pile of phones, and with every other manufacturer, the AT&T model is the same hardware as the Rogers/Bell/Telus model. I have managed to avoid Samsung until now. I've never found it so difficult to find reliable or detailed information about a phone, Samsung is very confusing and given all this, I'm not surprised at the lack of development compared to other brands.