yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] engine95:
For everyone

I have done these steps many times now. This will get you where you need to be for a base/starting point.

It's your choice what/how you want your root. But this way works with/for everything.

Boot to TWRP

wiped the 4 - this gets you CLEAN M. No leftovers from L

Odin M

get through setup screen

Odin TWRP - unselect auto reboot in options

reboot to TWRP

MAKE A BACKUP AND SAVE IT!!!!!!

flash SU 2.71

reboot tab to screen

reboot TWRP and install SU 2.46

reboot

Root will now work for everything

Install Neked_Nook_Maker

All is well, with no SEAdroid warning, apps removed, all scripts installed, xbin files added

But for the scripts to run, flash init.d kernel. SEAndroid warning is back

If you flash SU 2.71 again, you will lose root in Estrong again. But the SEAndroid warning will be gone.

Install SU 2.46 again, And ALL is rooted. Estrong and other apps all have root with the SEAndroid warning gone. And you have /system root

I would MAKE A BACKUP in TWRP!!!!!!

Now you can move on. It might be a lot of steps, but it works.

Edit: I don't know what going on yet with SU 2.74 and up. It might be a whole different ballgame.
[Galaxy Tab S2 Android Development] DroidIt!:
Hey [MENTION=1280108]engine95[/MENTION] :) Did quite a bit of experimenting myself with my 810 last night and here's what I figured out. I backed up everything before going to M just to be safe. I downloaded the M firmware from SamMobile, went to TWRP and wiped absolutely everything and then flashed M through Odin. Booted up transfered everything back to my tab, flashed TWRP 3.0.2-0 through Odin. Then I flashed your Maker2, SuperSU 2.72 binaries, a permissive script, and xposed. Booted up fine and everything looks really good. It took me awhile because I figured out if you try to encrypt an SD card, TWRP REALLY doesn't like it. :) But I have a permissive script that [MENTION=4684315]flar2[/MENTION] (a Nexus kernel dev) made to make any kernel permissive. I see he has removed it from his download section though. If he gives me permission to post it here, I'll post in the thread here. Just for my infos, what do we need permissive kernel for, just so I can tell him? :)

Edit: Oh and I guess if I can make a suggestion. :) I'm 99% sure the Makers just modify stock wich is why they're only 27 or so MB and there's no wipes. Maybe in the op just state that this is more of a stock mod, for now unless you change it. There was a dev for the nexii that did the same thing and kept his rom always that way. That's how he deved. Just leave stock as the base and just always build an updated, in this case maker, with new added or modified mods . :) So just a thought, you could leave your rom as makers and just make your changes in that space and leave the stock "main" part alone. That way the downloads would be smaller for all, you get the stability of stock, but still have all the mods anybody could want. Might also make it easier to make it compatable for all devices. Well :) just a couple thoughts on my end. I suppose if you did stay the maker way, the hard part might be including a script to wipe all the previous maker changes when flashing a new maker. Just an idea, and hope you're having a good day sir ;)
[Galaxy Tab S2 Android Development] engine95:
We posted about the same time so you might want to check the post right above yours.

The permissive kernel isn't needed for M. But some people still want it for whatever reasons. I'm really not sure why, now. It's probably about freeing up the phone, I guess.

As for the permissive script from flar2, I'm not sure how he's doing that. I know that with Nexus/LG you can get a permissive kernel through the ramdisk through the "command_line. But that hasn't worked for me on the S2. I've had to go through source to make it permissive. Ramdisk (mkboot) can be modified, but the zimage (source) can't be modified through any script. You might want to check "About" and make sure you have permissive. I'll need to look at his script out of curiosity.

There's a couple reasons why I've decided on going the "Maker" route.

This way, I can satisfy most all of the S2's, instead of just a few. And while it may look simple to a lot of us, not everyone is comfortable modifying their S2. Beginners mostly. (Just not a fan of the other term.)

Really, I'm just giving a simple base for anyone to work with/from.

This way saves me a ton of time so I can work on other things. Summer is here, or should be shortly. The weather has kept me indoors too much as seen in these threads. ;)

I need/want to unify all of our Kernels also. (Snapdragon's/New S2's, I can't help there). That's gonna take me a while. But so far 815 source has been working for Exynos. I can't be that lucky though. Again, "Murphy's law", and Murphy is my best friend. Like it or not. ;)

So yeah, for now, I'm taking the easiest way so I can work on more things. Android and life.
[Galaxy Tab S2 Android Development] DroidIt!:
Well, just getting ready to step out for a bit. But I agree with you about possibly for good staying the maker route. :) I have no problems modifying anything myself, I was just giving the philosophy of one dev and what he did and he gave all the same benefits pretty much you just listed...and his system worked great. There's a whole lot you don't have to mess with and can just focus on the extra goodies you might wanna add or get requests for and not have to worry about compatability so much. Why remake the wheel eh? When I get back I'll pm you a link to the permissive script, no harm in that I suppose as long as kept private and credit's given if used. Flar had much the same philosophy about permissive too. If app devs are decent devs there should be no need for permissive. Security should come first.

---------- Post added at 04:28 PM ---------- Previous post was at 04:28 PM ----------

Edit: oh couple hours I'll pm ;)

---------- Post added at 10:44 AM ---------- Previous post was at 10:28 AM ----------

Hey [MENTION=1280108]engine95[/MENTION], pm sent. Now I gotta run :)
[Galaxy Tab S2 Android Development] skawtnyc:
I actually did that plus a factory wipe.

I copied everything in /su/bin to /system/xbin, which resolves the issue until something else overwrites that dir. However, there's another workaround that allows systemless root and doesn't break apps like ES File Explorer. Add this to your maker package, and make sure it occurs before someone installs SuperSU:

echo BINDSYSTEMXBIN=false>>/data/.supersu

2.72 seems to install fine without causing a bootloop. 2.74 just came out; I'll try it and let you know.

Would be nice to have a new performance kernel with better cpu governors. :)

I'm going to use some of your suggestions with the v2 maker and see where it gets me. Fortunately I have backups.
[Galaxy Tab S2 Android Development] stoehner:
So can I flash the Neked Nook maker on my 810? Will this be marshmallow or is that another process?
[Galaxy Tab S2 Android Development] skawtnyc:
Followup: 2.74 works fine with the NNv2 maker, but that echo command to /data/.supersu had no effect. However, copying everything in /su/bin to /system/xbin worked fine. Maybe adding that to a startup script would be useful.

I'm not seeing any issues so far with root (ES File Explorer root mode works), and Xposed Framework didn't break after using NNv2.
[Galaxy Tab S2 Android Development] engine95:
It'll work with whatever Rom or Android version you have installed. So if you follow post # 112, you'll have M. If you use it on lollipop 5.0.2 or 5.1.1, you have lollipop.

Chainfire/SuperSU is still working on M. Everyone is trying to figure it out. Post #112 has my recommendations for install. Is that what you followed? That's been proven to be working for me since M came out. No need to move any files. Or add lines to the install.

Until I find a better way, that's what I'd recommend. For now.

Edit: Aren't TWRP backups awesome! :)
[Galaxy Tab S2 Android Development] skawtnyc:
No need to go back to 2.46 for a system mode SuperSU install. There's a 2.65 stable and 2.72 beta available here:

http://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

And yes, TWRP nandroid backups are super awesome.
[Galaxy Tab S2 Android Development] engine95:
Edited OP and post #112 for install instructions. Mostly pertaining to have M installed. It can't hurt with L either. ;)

Restores of any kind or NOT clean installs will probably cause issues. We are using M now, not L. It's a whole different ballgame. And as a lot of people are finding out not everything is compatible.
[Galaxy Tab S2 Android Development] engine95:
My bad. Didn't even know that. Mine is systemless. Thanks tons.

Back to the drawing board. Again. :eek: lol
[Galaxy Tab S2 Android Development] skawtnyc:
I didn't even realize Chainfire was still doing a system mode one until I started digging around today. I don't need systemless root on my devices, so it makes things a lot easier.
[Galaxy Tab S2 Android Development] engine95:
Well, looking at everything, even installing 2.46 is still using 2.65 binaries. So I think everything is still OK. It just makes it /system root.

Whew! That's a load of my plate! I was a-scared for a second. Lol
[Galaxy Tab S2 Android Development] DroidIt!:
So how's the work coming along on porting the N dev preview? Almost there yet? :cool: :silly:
[Galaxy Tab S2 Android Development] DroidIt!:
Hey [MENTION=1280108]engine95[/MENTION] what's happening? :) Well, been running M with Maker2 for about a day and a half with no issues. Now I'm just trying to figure how to move OBB's on big games to my extSD. It doesn't seem to be quite as easily solvable as it was on L. No issues with your maker at all though. Looking really good. ;)
[Galaxy Tab S2 Android Development] mattbeau:
So can i jist ask a question. This is just a script correct?

Im currently on MM stock with twrp and root(2.74).

I can just flash this and it will remove all the bloat?

Or is there alot morr going on then that. Sorry, i have been following this and things have cjanged around quite a bit
[Galaxy Tab S2 Android Development] engine95:
Kinda? There's a script that removes bloat. See the OP for how much you want removed. V1 or V2.

It'll also install some files so the scripts can run if you install an init.d kernel in post#2. It runs fine if you just use stock kernel also.

Just read the OP. I've rewritten it so it's less confusing. I hope anyway.

There is a full ROM for the 710 only also. Pretty much what you'll end up with, with the "maker".
[Galaxy Tab S2 Android Development] mattbeau:
Ok thanks. I tried installing this but still ended up with bloat in the end. Both v1 and v2. I also tried installing the lernal first from post 2.

Im using twrp and super su 2.74

This is with mm on my 710
[Galaxy Tab S2 Android Development] hurray:
The script (I used v2) works very well! Thank you very much.

My first trip to MM ends in a restore of the twrp-backup as it seems that I need a permissive kernel for FolderMount (which I use for mounting some folders to my external sdcard) :D

Everything else has worked as expected (systemless root, twrp, xposed, Bluetooth, wifi and so on).
[Galaxy Tab S2 Android Development] engine95:
I don't know why some are having issues. There's no reason too.

The one person I heard that did have a problem, ended up odin mm again. Then everything was fine.

I'm wondering if it's from dirty installs. You have to wipe all 4 then Odin M

The other option is to install the Rom since you have the 710.

It might be root. You might need /system root. There's a link 1 page back.

If you need permissive, there a thread for it.
[Galaxy Tab S2 Android Development] mattbeau:
Thanks engine. Im going to try the full rom. I have a good backup just in case.

Thabks for your haed work
[Galaxy Tab S2 Android Development] skawtnyc:
No rush, but it occurs to me that since you have the 810 source now, you could make a permissive, SEAndroid enforcing kernel. That would remove the need to install the systemless SuperSU again just to make sure it patches the kernel.
[Galaxy Tab S2 Android Development] hurray:
Thanks! It seems that I am right with my idea:

So I will have a look into the permissive Kernel Thread for my T810. :)

Btw: I will try this solution too (...after a backup of /system :D ):

FIX][ExtSD] ExtSD Fix (v2.1b - 2016-05-19)
[Galaxy Tab S2 Android Development] engine95:
My bad. It wasn't source they notified me about. It's being taken into consideration. We should have source in a week or so.

Definitely make a backup! I quickly looked through the script. MM, for us, has fixed the permissions for ext SD already. So I'm not sure we need this. That was one of the first things I looked into. I might have to look into this script more.

Permissive kernel will come when I get source as said above.

To everyone:

There are a couple ways to root now. /system and systemless. 2.74 is current. Systemless is at Chainfire's SU site. And, because I didn't find this, Look and Thank both here for /system root.

I think because it's Beta, the option to convert to /system root is grayed out in the SU app. So you'll need to flash the /system root.

MAKE A BACKUP FIRST!!!!

Using 2.74 we:

CAN update systemless root - and I would recommend it

CAN go from systemless to /system Root

CAN update /system root - Again, I would recommend it

CANNOT go from /system root to /systemless - the app will disappear.

Hopefully I got all that right. I really don't wanna go through it all again.

This is what I've found out so far. So now I SHOULD be able to move forward instead of having to start all over with things.
[Galaxy Tab S2 Android Development] DroidIt!:
Since extSD is being brought up so much :) I was trying to use the app Link2SD to move OBB files from internal storage to the extSD. I need to read more, but the app seems to think that the extSD is virtualized? I did try the app I used to use years ago App2SD, but that only moved the app itself. On L I could use Link2SD fine. It could just simply be an app thing. I have no problems at all reading/writing other stuffs to my SD. But with talk of the system vs. systemless, could it be root method? I flashed 2.72. Lol, only reason I'm looking so hard is because I have a 128 GB extSD and it's sitting largely empty while my internal storage is almost full between apps, games and school stuffs. Any thoughts appreciated. :)
[Galaxy Tab S2 Android Development] mattbeau:
I installed the full rom and that worked :good:

Ill report back if there are any problems.

Great Job!
[Galaxy Tab S2 Android Development] engine95:
For me, I went the /system root route. It seems to work for everything.

I really don't know if the Permissive kernel will help or not. I will build one for the 810 or any others that want it when source is available.

I'm looking though that ext sd card fix mentioned above. I THINK Super SU is already modifying it as there is a .mbak of the same file. And, all the permissions are there that we need. So I'm a little confused on it.

But then, we are all learning with M.

BTW, Bahahahahaha!!! on your "N" preview. ;) My plate is full enough.
[Galaxy Tab S2 Android Development] DroidIt!:
Ok :) Well, I just finished up some schoolwork and I'll be able to look at the exact error that Link2SD is giving me. It mentioned virtualization but also gave more technical reasons I couldn't remember off the top of my head. I'll take a look here shortly and then I can post what it's saying the exact error is and maybe that'll help. :)
[Galaxy Tab S2 Android Development] DroidIt!:
Hey [MENTION=1280108]engine95[/MENTION], sorry it took so long :) The screenie...
[Galaxy Tab S2 Android Development] DroidIt!:
But when I click OK, it asks to reboot. I do and then still get the same error.
[Galaxy Tab S2 Android Development] miloshdrown:
Anyone have success with the 810 init.d zip in the second post? I tried it yesturday and got stuck on the samsung logo. I let it sit for about 20 mins and tried a reboot but no dice. Had to restore my nandroid to get it to boot again. I odin'd MM and used the V2 script before trying the init.d zip if that helps.
[Galaxy Tab S2 Android Development] DroidIt!:
I actually wanted to ask about that now that you brought that up. I saw it said that's included in the maker, unless I was misreading.
[Galaxy Tab S2 Android Development] engine95:
Try /system root. Unless you already are.

Permissive may work? But it might just not be compatible with MM.

No kernel in the maker so it'll work with all S2's.

Did you DL it just recently? I had to make a little change in how it installed. It was wiping scripts but that wouldn't cause your issue.

I think SU is killing init.d but I haven't had time to get into it. For now, try system root. See if that works. Also, when you Odin, wipe all 4, then Odin. I think dirty Odin is the problem some are having.
[Galaxy Tab S2 Android Development] DeeXii:
So how is MM running on this tab? Anything I should know before diving into it?
[Galaxy Tab S2 Android Development] engine95:
It runs very well and battery is better.

Post#112 or whatever I have in the OP is best to follow. Use SU 2.74 instead of what I have listed.

I'd also suggest /system root. It's tried and true to always work.

You'll only lose higher than 44 5g wifi.
[Galaxy Tab S2 Android Development] miloshdrown:
I downloaded it on Friday. I'm not sure if init.d is working or not. Installing it gets me stuck at the samsung logo so I haven't gotten far enough for that. Tonight I'm going to nandroid my current setup and do a full wipe in twrp, Odin the German MM again and just install the init.d zip and see if that gets past the logo. Ill let you know how it goes.
[Galaxy Tab S2 Android Development] engine95:
I just had a thought. Root is probably the issue. It depends how you root. /system or systemless.

If systemless, you'll probably have to flash systemless root again.

So flash init.d kernel, then systemless root then reboot.

The init.d kernels I have in post #2 are not rooted systemless. I pulled them from the .tar clean.

Personally I prefer /system. Then everything works.
[Galaxy Tab S2 Android Development] DroidIt!:
So, I've read your posts. :) Just to get it straight in my head, if I flash 2.74 then boot up, we can go into the SU app and choose to change it to /system or /systemless with the caviats in your earlier post or if we want /system do we still need older binaries. Just making sure I have it right. :)
[Galaxy Tab S2 Android Development] engine95:
In SU, it's grayed out. So you'll need to manually flash either one.

I think one page back, is what works and doesn't as far as flashing SU. If I remember, we can go systemless to /system. But not the other way. I think that's all explained in that post.

I need to link that post in the OP. And here.

Edit: http://xdaforums.com/showthread.php?p=66956024
[Galaxy Tab S2 Android Development] miloshdrown:
Edit: [MENTION=1280108]engine95[/MENTION] ment to quote you on this one :p

Yeah I flashed the standard 2.72 su but have a .supersu with SYSTEMLESS=false so it would install system less. I prefer es file Explorer as my root browser and it hasn't been updated to support system less correctly yet. The common denominator I see so far is if I get the kernel is not seandroid red txt the 810 won't boot. I extracted the boot image out of the tar.md5 unpacked it and added init.d using one of the methods I used a while ago and still had the same issue. I also tried installing systemless su after flashing both my version and your version which got rid of the seandroid warning which allowed it to boot but init.d support didn't work. I'll have to hack on it some more this weekend when I can deticate more time to it. I'm new to Samsung devices so I'm still getting used to the differences. Do you know what about the boot image triggers the seandroid error? Obviously the method chainfire uses in the su zips seems to work without creating the error.
[Galaxy Tab S2 Android Development] DroidIt!:
:) I'm still digging around myself and getting used to Samsung. My first Sammy too. :) AFAIK the text you see on boot up is just text. It doesn't really matter. As far as ES explorer...when was the last update on it? Systemless has been out for awhile and if the app still hasn't been updated, might be time to find a good alternative. I personally use Root Explorer and it's worked fine since M came out through /system and /systemless su updates. I can't recall off the top of my head what triggers the seandriod though. But, you probably meant your post for the dev anyhow, which is [MENTION=1280108]engine95[/MENTION] ;)
[Galaxy Tab S2 Android Development] miloshdrown:
Lol. Yup totally quoted the wrong post but thanks for the info anyway. I have Root Explorer Pro also as a backup when es doesn't want to detect root. I use a lot of network shares to access stuff on my nas so it's more of a convince thing with es.
[Galaxy Tab S2 Android Development] DroidIt!:
Ah, got ya. :) Well, if ES doesn't update really soon or hasn't for quite awhile, then I'd grab something different that has similar capabilities. It can actually be a good thing to be forced to switch away from an app. I've been trying to move OBB's to my extSD for a couple days and just found a really promising app that can partition the extSD without needing to remove it. :) Have a look around, apps pop up all the time.
[Galaxy Tab S2 Android Development] :
What is the link for T810 ?

And what is the goal of Neked Nook ROM ?

And of the NN_Maker (not ROM) ?

Thank you very much
[Galaxy Tab S2 Android Development] miloshdrown:
Thanks for all the info it really helps. Im going to wipe and start again following your steps exactly. I'm just not going to get a chance till this weekend. I more wanted to understand the internal process better. I'm a Sr software dev and system admin by day so it's in my nature to be extremely inquisitive when I don't understand something lol
[Galaxy Tab S2 Android Development] drharder:
Im also having issues installing the "Maker" on the 810. It seems after installing the kernel for the 810 the tablet wont boot past the Samsung logo.

This is off a clean fresh install of MM. I followed the steps to the letter and everything seems fine until I get to the kernel.
[Galaxy Tab S2 Android Development] engine95:
Try installing the kernel before the maker. Once the kernel is there, it'll stay until you flash something over it. The "maker" has no kernel. So this should work.

Or

Now that the init.d kernel is installed already, flash the ROM again. If bootloot, try flashing SU 2.74 and that SHOULD fix it. If that doesn't, then I'm pretty sure flashing /systemmode SU will work.

Again, it's systemless root that is causing the issues. I need to check again, but I'm pretty sure all the kernels do not have root. So systemless should be able to fix it. But it doesn't for whatever reason.

I'm confusing myself each time I try to explain how to make anything work on M. I think I have novels in 4-5 threads now.

In the Permissive kernel thread, someone used systemmode SU on the 810 and everything is working fine. They even list their steps and install xposed. Which proves that if everyone would just go to a /system root, everything will work. Also, in this thread, others have installed on the 810 with xposed.

I'm not going to rebuild the kernels until everyone either, uses /system root, or the dust settles for SU. They've already been redone 3 times. And it's getting confusing what I'm doing to fix them each time.

So to recap. It's SU that is messing things up. The "Maker" has nothing in it to mess up. systemless SU is rebuilding the kernels and killing init.d. And sometimes, re-root. All this is explained in the post, 2 above your's. So no sense writing it again.

Check to OP, read the links I have posted there, and I'm sure it'll fix the problems. Install SU SYSTEMMODE-2.74

I'll add more links to the OP again for extra infos.

Edit. SU made a big change in 2.72. So my instructions, that it looks like you read, may be off now. Read those links again in the OP, which I just updated and fixed, and see if that helps at all.
[Galaxy Tab S2 Android Development] stinka318:
Can this be

Can I flash this on a Australia t815y telstra branded but unlocked thanks in advance