yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] ashyx:
Ok I've read through this thread and I'm getting confused as to the direction its going and I think a few others are too.

Which kernel is being used for the relevant devices as all 4 variants of the device have the firmware available, so is the stock kernel being used to boot the rom?

Why is a T710 rom being modified to work for the T810 when the T810 rom is available?

Why the need for a permissive kernel?

Also regarding the comment about the 90 degrees screen above.

The 8.0 and 9.7 models use completely different screens. The 9.7 uses a native landscape screen(yes that correct Samsung have used a Landscape screen in a portrait device). To make it work on a portrait device Samsung have modified the kernel and probably the ROM. This means the 8.0 and 9.7 kernels and rom are fundamentally different
[Galaxy Tab S2 Android Development] engine95:
1. Each Rom, which only the 710 is posted in the OP, has it's own kernel. And yes they are stock kernels.

Because everyone is still figuring out MM, there's a lot of testing/experimenting going on. Not just here.

2. I'm trying to keep the DL's for the testing ROMs as small and limited as I can. People from all over the world are Dl'ing these. And not eveyone has fast DL's.

When I first made these ROM's, OH1, I found that by changing out 4 files, the 810 would work with the 710 ROM. Making my work easier.

I have requested multiple times, a system.img but no one has obliged me. Other than ptfdmedic for OH7.

Using the .tar for the ROM doesn't make it flashable.

3. Choice. Some people still want a permissive kernel. And I'm sure removing Knox will follow. I think we all like the idea of having a Tab/phone that isn't so secure. (Not sure how to word that one)

Also, I need to see if MM will flash from L. I think using the permissive kernel may do that. But I haven't tested it out yet.

4. Answered in question 2. Also, a system.img will have all the correct symlinks and permissions. While an updater-script can cause issues. Case in point, the updater-script I have so far breaks wifi and something else I cant remember right now.

With L, I could make the 710 an 810, and vice versa. I'm going to try that again with M. Then when I get things figured out, I can upload a complete ROM instead of parts.

Right now, this thread is no different than what the OH7 thread was. Building blocks, for me.

Another thing is, with this being a Tablet and not a mainstream phone, there is a lot less requests/activity in these forums. So getting needed info is not as easy.

Case in point. My work for the G3 has over 67K DL's, This Tab and the one I had prior, are lucky to have 1K.

Sorry for another long winded explaination. :eek:
[Galaxy Tab S2 Android Development] engine95:
Ok. So. M is different from L. I've edited my above posts pertaining to the 810 for Neked Nook.

It will not work. So I've also removed the files and link.

What worked to bring Neked to the 810 does not work with M. I just tried to turn my 710 into an 810. And while all the correct files were there, (everything said it was an 810) it still ran as a 710.

So I need to rethink on how to go.

Option 1: Make a flashable zip of the needed files and changes that I have made to make the ROM.

Meaning, you remove the apps you want, and flash the file I make for everyone. This way everyone gets Neked_Nook. You just remove the apps you don't want.

I'm pretty sure I can do this as I haven't modified the build.prop. I just need to add some files to xbin, init.d scripts, and a couple other things. It'll be more work for you all, and you would basically be building your own ROM.

Option 2: I would need a system.img and boot.img fresh from Odin, made with TWRP with no root, for every S2 model that is interested in Neked. Meaning no work for you, but a lot for me.

It would be a simple flash in TWRP for you.

This would be slower for me to make and will be delayed as I still don't have a working updater-script.

These are my options for now. So WE have a lot to think about. Who knows, I may do both to cover people who are unsure of themselves.

Edit: And Aroma is not an option from me. It causes too many problems. And takes a long time to get the kinks worked out.
[Galaxy Tab S2 Android Development] jafangie:
Hi engine95,

With L some people asked me to do 1 rom for T815, (here), I replied that I don't have enough time... It was not the only reason!

I checked the structure of the two roms. There are so different, and as I cannot test on T815, I have chosen to do nothing for T815.

Concerning the MM, sure it is very special! I lost lot of time to deodex files. I always have FC with some apps. Now I have one rom base for T715 clean and working. But without permissive kernel!

I am tired of waiting for the sources of the T715, So I will try to build one permissive kernel from T815 kernel. Today I just download sources for T815 , and happily there are only few files to modify.

I will keep you updated!

Jaf
[Galaxy Tab S2 Android Development] ashyx:
Fair enough, but can I ask why the request for the system.img from TWRP? Why not use the stock system.img?
[Galaxy Tab S2 Android Development] engine95:
Thanks

With L, I was able to combine 710 with the 810. We just lost mic, battery cap and Autobrightness. I never did find the files to fix that on L. But now we're moving on the M and a whole new learning curve as you well know.

I don't blame you for not waiting for source. But I did find that the defconfig's changed with M. As well as other obvious things. I've needed to wait for source to pull those and build the kernels. I've used the 815 source and built the 815 and 710 permissive kernels. Both seem to work fine, so far, using 815 source, and their respective defconfigs. So you shouldn't have any problems. Or just a couple. ;) Good luck. :good::good:

I took on too much at once. Which I know better.

It may just be my updater-scripts, but when I pull the system.img from the .tar, all the symlinks and permissions get messed up. But when pulled through ADB or TWRP everything is right.

I need to slow down and try it again. I have everybody's .tars already

I've been using system.img instead of updater-scripts on install because it always installs correctly. It lessens the chance of me messing up or having something break. Plus it's pulled from the Tab in working order. Basically it's built natively.

Once I know the system.img installs right, then I usually move on the updater-scripts for those that like to modify further. And I've got a little more time to work on things. Instead of the "I want it now". Which this forum has been very good about. :D

My problem is I try to please everyone, so I try to get things done too fast. I end up confusing myself.

Now that everyone has M, I'll slow down and work on things more specific now. I just need to be more thorough with everything.

Hopefully that answers you question.

Edit: [MENTION=4899305]ashyx[/MENTION] When I look at /system/bin when pulled from the .tar, it shows " Broken link" or "Unknown link".

I never got that with L pulled from abd. So it might just be me assuming things.

I'll find out.
[Galaxy Tab S2 Android Development] ashyx:
Maybe you do things differently to me, but I never usually have an issue modifying the stock system.img as it should be identical to the one on the device once inflated.

The way I do it is:

1. Pull system.img from stock firmware.

2. Convert from sparse to raw image using simg2img:

simg2img system.img system.raw.img

3. Mount as loop device

mkdir system_mnt

mount - t ext4 -o loop system.raw.img system_mnt

4. Then I modify what I need to, ensure permissions are set correctly on anything I've changed then repack it to a raw image. Then convert to sparse and finally convert the headers to 32bit.

5. Repack to tar archive.

Are you doing things differently?

I also agree you need to slow down you're doing great things here and I know how much effort your throwing at it.

Just don't burn yourself out. Take a break and come back afresh.;)
[Galaxy Tab S2 Android Development] engine95:
Thank you. Very much appreciated. :D

As I've said, Samsung is new to me, so it's a learning curve along with M.

I do what you do until #4 and just use the updater-script from there. I think my mistake is converting from sparse.

I need to break down an L .tar and compare the 2. Files just don't look right to me on M. /system/bin and /system being the ones I notice most.

Regardless, I am going to mellow out and start at the beginning. Roms being first. Kernels being next. Now that M is out for most everybody, I feel better. (That's just one of my character flaws).

I'm hoping I can merge all the kernel sources for the now "Old S2" and build for all. So far, using 815 source has worked. And again, it'll be another learning curve for me with Git.

BTW. Thanks to you and [MENTION=234631]jafangie[/MENTION]. You two have helped me get my..... stuff together. Even though neither of you knew it.
[Galaxy Tab S2 Android Development] pickandrew:
I can not understand what is the right version for this ROM:

with SoC Exynos or Snapdragon? Support only WiFi or LTE device?

For which model?

Thank y very much
[Galaxy Tab S2 Android Development] davidzvi:
Thanks for the hard work. Just flashed it today.

I did an initialize through smart switch.

Followed the MM for 710 install directions.

Installed TWRN

And flashed this.

Everything up and running.
[Galaxy Tab S2 Android Development] engine95:
So now it begins.

I'm pretty sure everything in this forum right now is for Exynos. So you'll need to MAKE SURE you look for the model numbers.

I don't know if the new S2's will get they're own forum or not.

I'm pretty sure nothing here is gonna work for anyone having the Snapdragon CPU. I'm guessing you'll need a new TWRP too.

Edit: Model number being 710 or t710. I'm not sure what the new ones are numbered.
[Galaxy Tab S2 Android Development] engine95:
To everyone - New and old S2's

Because of the New S2's popping up, I've decided to not make a ROM. :(

But not to worry. :D

I'm just about done making a flashable zip that will work on ALL S2's. This will make ALL S2's into Neked_Nook. The only thing that will be needed is to have an init.d kernel which I will not include in the ROM. More on all that later.

This will also fix some mistakes that I noticed for the 710. Depending on how and what you've flashed. No need to worry about what you have already.

I should have them done in a day or two. Depending on busybox and getting run_parts right. That's the best way to have busybox. And we need it for init.d and future stuff.
[Galaxy Tab S2 Android Development] engine95:
If anyone wants to look me up on AFH, the "Neked_Nook_Maker is there. It's V1. It will work with new and existing ROMs. And will fix my mistakes on my ROM.

Make a backup first!!! You are responsible for TESTING this But there should be no issues. :D

Let me know how it goes, AND WHAT MODEL YOU TRIED IT ON!!!

More details when it gets put in the OP.

It DOES NOT include a Kernel. So all is well

Edit: This is not a rom! Do not wipe anything! Just flash and go.

Edit 2: V2 is there also with more bloat removed.
[Galaxy Tab S2 Android Development] Josephigloe:
Thank you for everything you have done for us S2 guys we do appreciate it.

---------- Post added at 02:40 PM ---------- Previous post was at 02:32 PM ----------

Search AFH with just Neked goes right to it.
[Galaxy Tab S2 Android Development] juniorr7710:
The steps from post 1 worked for me... Thanks! :good::D

---------- Post added at 11:30 AM ---------- Previous post was at 10:54 AM ----------

Sorry that i ask, a bit lost... But your last post mention V2, where can i find it?
[Galaxy Tab S2 Android Development] Josephigloe:
Google Android file host and search Neked and scroll down.
[Galaxy Tab S2 Android Development] engine95:
The only reason they're not posted here yet, is because they haven't been tested thoroughly yet. So if you want it early, you have to look me up on AFH.

The latest on AFH are not Roms. I'm trying to make a universal ROM maker for all S2's. Basically, just flash it over any rom and it will install and remove some apps/bloat. Do not wipe anything. Just flash it.
[Galaxy Tab S2 Android Development] lewmur:
I'd be happy to "look you up on AFH, if only I knew what AFH was.:confused:
[Galaxy Tab S2 Android Development] JekyllInside:
https://www.androidfilehost.com/?w=profile&uid=9390355257214632023
[Galaxy Tab S2 Android Development] lewmur:
Thanks, I found it.
[Galaxy Tab S2 Android Development] engine95:
Too funny. ;)

I could have just put the links here. But I'm trying to limit the number of people that try this. Just in case it doesn't work for all ROMs and models.

It'll work for L and M Roms in any way. But xposed it may not work with as it changes file names.

I'll just post the links in the OP in the next day or two. Depends how busy work is going to be. The time consuming part is gonna be listing and explaining it in the OP. It's not rocket science, but it'll take a little explaining. As it's different than full roms in what it does.
[Galaxy Tab S2 Android Development] engine95:
OP Updated with Neked_Nook_Maker. V1 and V2 READ!!! READ!!!! READ!!!!!

Should flash on ANY S2 and ANY ROM. It may not work if xposed is already installed.

Do not do any wipes. Everything is written in the zip already.

For full benefit, you should have a Kernel with init.d support. Kernel is not included!!

710, 810, and 815 permissive have init.d support already in post #2.

I just need boot.img pulled from the .tar or TWRP for any other S2's. Don't worry about the name, as long as it's boot.?????? it's fine.

In a rooted explorer, look in /data. It should have Test.log. Then you know it's working.

Let me know what model you have if you make comments.

Yes, this is very different from almost any ROM. But I'm trying to make this work for old and new S2's.
[Galaxy Tab S2 Android Development] skawtnyc:
From what I can tell,. I don't really need the Neked Nook script on my 810. I've already installed your init.d kernel and manually debloated my Rom using titanium backup. Is there anything extra in the NN package that I would want to add at this point? I actually prefer to keep the Google apps.
[Galaxy Tab S2 Android Development] engine95:
There's busybox and a couple extra files that go in xbin also. Those are needed for the scripts to run.

There's no need to keep the Google apps in /system when they all run from /data when you update them. The phone or tablet actually run better when /system has some wiggle room.

You can always make a backup then try it. See if theres any difference. :)
[Galaxy Tab S2 Android Development] skawtnyc:
Well I already had busybox installed on my own. However that was installed to /su/xbin. I've removed that, and made sure that the busybox installer updates to /system/xbin like yours does.

Also, v2 did work fine even with Xposed installed, at least on my 810 tablet. I think the debloating I did may be even more in-depth than yours since I used a deep dive debloat app and then manually went over it after that one ran. You can find it here:

http://xdaforums.com/galaxy-s6/themes-apps/s6-debloat-script-mentalmuso-t3155802
[Galaxy Tab S2 Android Development] skawtnyc:
Correction: this is the thread where I got the debloat script:

http://xdaforums.com/s7-edge/themes/samsung-galaxy-s7-s7-edge-bloat-list-t3359654
[Galaxy Tab S2 Android Development] engine95:
Good to know about xposed and the 810. Thank you

This debloat script is in stages and is specific to the S2.

I noticed there are quite a few DL of the removed apps. So I try to keep it simple to reinstall apps. I could cut a lot deeper but that would make things more difficult to reinstall.

These are tablets, so their use can be a lot different from a phone.

I've looked through a few debloat scripts. To me, they're just to generic and may touch on things that could break.
[Galaxy Tab S2 Android Development] JekyllInside:
Maybe is my tablet, but neither Neked Nook Maker V1 or V2 made any different on over my CPD9. I'm still having all the Samsung and MS apps. I tried V1 first, nothing. Everything looked good on TWRP and it boot with a "12 apps optimization". Later tried V2, same thing, same message, same apps in the tablet.
[Galaxy Tab S2 Android Development] engine95:
What model are you on? Are the apps on their own? Or in a group? Very strange that they're still showing up. Cache and dalvic are wiped automatically.

Are you rooted? That's the only reason I can think of why it wouldn't work. You need root to modify /system.
[Galaxy Tab S2 Android Development] JekyllInside:
S2 8.0. Apps remain in the same place. I opened up every one just to make sure they still there and they function.

I wasn't rooted first, but did it later and try again with both files. I even flash your init kernel and try again. Nada. I wiped cache and dalvic by myself. Nop.
[Galaxy Tab S2 Android Development] engine95:
Check /data and see if you have" Test.log". You'll need a rooted explorer to check. If you can't see /data, then your root is either broken or you're not actually rooted.

That's the only reason I can think of as to why is not working. Use SU 2.65 /(systemless)or higher. Personally, I like /system root which is SU 2.46. Either way, SU might say you have root when you actually don't. You have to use root to make sure.
[Galaxy Tab S2 Android Development] law16:
All s2? Does this work with tmobile 817t?
[Galaxy Tab S2 Android Development] JekyllInside:
Ok, a had to ODIN MM again and SuperSU 2.72 (2.46 got me stuck in splash screen) to make this thing (V2) work.
[Galaxy Tab S2 Android Development] engine95:
It should. Make a backup first though, just in case.

I would need your boot.img from TWRP or the .tar to make an init.d kernel for you. Don't worry about the ext, as long as it's boot.???? It'll work.

Interesting. And doesn't make sense, but glad you got it working.
[Galaxy Tab S2 Android Development] law16:
Sounds good I'll get you the boot.img as soon as I can
[Galaxy Tab S2 Android Development] stoehner:
So is the new flashable v2, MM for the 810?
[Galaxy Tab S2 Android Development] DroidIt!:
Hey [MENTION=1280108]engine95[/MENTION] :) Just catching up here as I've had some family issues going on. I'll have some decent time for tomorrow but if you still need a boot.img for the t810 I can provide one. I'm still on LL. What would you need me to do. I'll have from 8 of so in the morning on Thursday till about 4 in the afternoon...well and actually probably 4 or 5 hours tomorrow come to think of it. :)
[Galaxy Tab S2 Android Development] engine95:
All S2's. So, yup.

Hope everything's OK.

I have 810 boot.img from the .tar. Its source I need for 810 to make a permissive kernel. Although we don't need it now, but people still want it.

I do need boot.img for anything other than 710, 810, 815, so i can make them init.d kernels. I don't need source for that.
[Galaxy Tab S2 Android Development] DroidIt!:
Got ya :) Looks like you're doing a lot of work so wanted to see if ya needed anything to make life easier. ;)

---------- Post added at 08:20 AM ---------- Previous post was at 07:22 AM ----------

Oh, if it's requests you're looking for :) mine are rather simple but big functionality changers IMO. I've always liked the status bar brightness slider. Sammy did an ok job with the qs tiles, so I think I'm good with that setup since they have qs tile rearrangement built in. But, if we could change the number shown or make rows instead of having some hidden, that would be cool. Only other thing is if we could center clock with date and maybe battery bar and hide battery icon. Well, all of my stuffs revolves around status bar and qs since you see status bar all the time no matter what you're doing (unless gaming maybe). Well, if I had any requests, those would be mine. :)
[Galaxy Tab S2 Android Development] skawtnyc:
DO NOT USE THIS DEBLOAT SCRIPT.

I discovered that they went too far and actually deleted some necessary files/apps that result in noticeable issues shortly afterwards.
[Galaxy Tab S2 Android Development] DroidIt!:
Oopse, old post :)
[Galaxy Tab S2 Android Development] engine95:
Interesting. I thought maybe. ?
[Galaxy Tab S2 Android Development] skawtnyc:
Deleting the gallery app, for instance, breaks the ability to select wallpapers for the lock screen.

I've also had to stop using your NN maker, as it's doing something that causes weird issues with Xposed modules, and also breaks root access to apps like Titanium Backup. I can use it to backup, but when I try to remove system apps it doesn't remove them. It also breaks ES File Explorer in the same way, blocking r/w access to /system. I haven't tried to add the init.d kernel back yet, I want to make a nandroid backup before I try that.
[Galaxy Tab S2 Android Development] skawtnyc:
Followup: looks like the init.d MM kernel also breaks root and Xposed. I guess I'm on manual until you have the source code to fix things.
[Galaxy Tab S2 Android Development] engine95:
I'm not quite sure where to start.

I would have to say that the Debloat script you installed has reeked havoc on your tab. You probably need to Odin M again.

There is nothing in any of the Rom's/Scripts that would give you the issues you're having.

As for root:

Again, nothing in the "maker" will mess up root, as it has no kernel. In the Rom for the 710, I ended up putting SU in /system instead of systemless. It seemed to work the best and ALL apps worked then. Not all apps , Estrong being one of the main ones, can work with systemless root. There are others I use and that's why I went /system root on the 710 ROM.

I've flashed the 710 ROM, "maker", init.d kernel, permissive kernel, and SU 2.46 and am still running it with no issue. I've also came straight from Odin M and flashed all the above except the Rom with no issues either. I'm still using /system root from 2.46.

I guess my point is, flashing SU 2.65 and higher after installing any of the ROM's/Kernels will mess up root. So is you must flash root, use 2.46 to gain /system root.

(I just flashed 2.46 on top of what I have and all is fine. But when I flashed 2.71, bootloop. So it's the newer SU's that are causing issues. M is new so we all have to figure/work out the kinks.)

xposed. oh lovely xposed:

I was surprised the "maker" even worked. But since it did, again, it's not the "maker" that messed things up.

If you have to have xposed, Odin, flash the "maker" then install xposed. Everything will work then.

Source:

810 source just posted last night. But I don't need it to make init.d kernels. Only for permissive and above kernels. ;)

So here's where were at:

Odin or restore and go from there.

Flash Su 2.46 and there should be no issues. (That's where I'm at) And deal with the useless SEAndroid notice on reboot.

Don't use the "maker" and remove the apps manually. But you can pull the scripts and find the added xbin files and the init.d kernel to use the scripts.

Edit: I'm going to retrace my steps from Odin. and I'll post them here and in the OP.

I think what I did was Odin, install SU 2.71, get to setup screen, reboot to TWRP, THEN flash SU 2.46. Then root will work for everything. But let me make sure first.