yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] mankvl:
I wiped everything and again it won't boot (even formatted data where you tipe "yes"). About WiFi I rly doubt it. I use tab only at home and always connect to my 5Ghz Wifi :) So no I will try the Maker and the init.d kernel, but it wont be the same I guess :(
[Galaxy Tab S2 Android Development] DroidIt!:
Heya [MENTION=1280108]engine95[/MENTION] hope all's been going good. Just wanted to drop in and say that I picked up a 710 too before they ran out of stock, rooted and flashed your maker and running perfectly on the 710 as well. Thanks again dude. :)
[Galaxy Tab S2 Android Development] mankvl:
Just formatted and wiped everything, then Odin flashed MM, TWRP and rooted with UPDATE-SuperSU-v2.76-SYSTEMMODE.zip and also used your maker and then init.d kernel. Now all works so far, will see after few weeks I guess if I get a bootloop. :D
[Galaxy Tab S2 Android Development] DroidIt!:
Nope, afaik looking at the op, init.d works with the stock kernel if I'm reading that right. Well, I did the same as you: odin MM, flash TWRP, root, then flash the V2 Maker and all seems to be working well for me. I left stock kernel on both my 810 and 710. :) BTW, I was thinking with having bootloops and maker being a script, you should probably go from scratch. If you get more bootloops I can't imagine it'd be from the maker. If at some point you do get bootloops I'd go back to stock and stay there for a week and see if you get more. Never had a single loop on either of my tabs btw. :)
[Galaxy Tab S2 Android Development] mankvl:
Edited the post after flashing init.d kernel after reading OP again :) init.d scripts wont be used with stock kernel but the ROM will work, so I flashed the init.d kernel

I was getting bootloops when I flashed the 710 ROM, so now I wish all will be ok :)
[Galaxy Tab S2 Android Development] DroidIt!:
Ah ok. With the wording I was a bit confuzzled myself...overworking my braincells :p Good to know the route you took works though. I just rooted and flashed my 710 last night and left stock kernel and flashed the Maker V2. So if you do get loops I'd maybe try without the init.d kernel then. That COULD be a possible problem as I said I haven't had any loops keeping stock kernel. Well, glad you got it sorted. Maybe I'll try the init.d for my 810 and flash the V2 and see what happens. :)
[Galaxy Tab S2 Android Development] mankvl:
bootloops was happening only to 710 ROM users. Did't notice anyone saying they got bootloop with the maker :)
[Galaxy Tab S2 Android Development] DroidIt!:
Oopsies :angel: Must not have gotten the whole conversation. Wellp, no loops here on stock + Maker for the 710 or 810, so if you do find issues you could grab a log and maybe try the stock + Maker route then. I know [MENTION=1280108]engine95[/MENTION] said he's pretty pressed for time, but a log's always best. :)
[Galaxy Tab S2 Android Development] mankvl:
Anyone know why now after flashing all with the Make I can't instal VLC for Android? At google play it says not supported :(

Edit: managed to install VLC-Android-2.0.2-ARMv7.apk from here: https://get.videolan.org/vlc-android/2.0.2/

At Google play it shows change log of 2.0.3 maybe they f up smth so our device became unsupported ? :(
[Galaxy Tab S2 Android Development] engine95:
The Maker and Rom should be about the same, if I remember right. I was just trying to help with all the S2's since they were coming out at that time. That's why I went with the Maker.

The Rom was based on the German "M" and didn't have the higher 5g bands. That gave some people issues. So with the Maker script, it allowed every S2 to update to the "M" they preferred and have all the goodness of the ROM.

I have noticed that depending how people root, it's causing the init.d scripts to sometimes not run. I may need to rework the kernel or scripts and use su.d instead. But again, time is not on my side, and will take me a while before I can play with this Tab.

I thought about asking for logs, but if it's in a bootloop, the logs probably got messed up. I'm not sure though. And I couldn't recreate it and had no issues on mine.

Glad you got it figured out. I've seen some people have been having issues with VLC and M.

M created a ####storm of changes to how all things Android work. Security being the main theme anymore.
[Galaxy Tab S2 Android Development] skawtnyc:
The latest build of the ROM is for Brazil, but works fine in the US.

http://www.sammobile.com/firmwares/download/79061/T810XXU2CPF2_T810ZTO2CPF2_ZTO/

It has the recent security patches for June 1st, and is also capable of connecting to the upper 5ghz wifi channels (my router is set to 161). It also works fine with Neked Nook maker.
[Galaxy Tab S2 Android Development] sketchman16:
This works really nicely. It's so fast and smooth. I love the stock Samsung ROMs when they're debloated. Thanks.
[Galaxy Tab S2 Android Development] ivanox1972:
[MENTION=1280108]engine95[/MENTION] boss, can you make twrp flashable t810 rom (stock, or debloated no matter)?

There is no one twy rom for t810 6.0.1 for recovery... I have now cm13, I need to flash odin stock, root, twrp and your rom... every time when switch from cm13

thanks
[Galaxy Tab S2 Android Development] mysa50:
Hello, i have a weird bug the rom run without issue but 2 weeks ago i turned off the tablet and i get stucked in a bootloop when i turned it on, i couldn't pass the Samsung logo. Same thing happened today as i run out of battery. I had to restore from a back up i have on twrp. Any idea of what happened?
[Galaxy Tab S2 Android Development] DroidIt!:
Did you try to modify kernel values at all or have mods installed like xposed? Both of those can result in what you described. I would reflash through Odin, flash the maker, do a nand before installing anything else and go from there. I've been playing with engine's work since released though and personally haven't seen any issues like that.;)
[Galaxy Tab S2 Android Development] engine95:
Just backup stock ROM in TWRP and restore it. You should be good to go.

So Odin stock M, install TWRP, (I'd backup this up for bone stock restore), flash SU and make another backup.

Flash the init.d kernel, flash the maker and that'll get you a Rom to restore to.

Again, my android time is gone for a while.
[Galaxy Tab S2 Android Development] ivanox1972:
Ok, boss thanks. I had your rom month ago, done same as you said. Stupid, forgot to backup when installed cm. So must do all again...

Bit it is really strang that in moment we have only great cm and grat your twz, only 2 roms for 810... And nowhere to download stoch .zip rom...
[Galaxy Tab S2 Android Development] mysa50:
Nope didn't touch anything in kernel settings and no xposed installed. I Odin stock MM then the rom and the maker v2, nothing more. I'll try to make a fresh install when i'll get the motivation to restore everything!! I just have to watch for the battery atm.
[Galaxy Tab S2 Android Development] mankvl:
As stated before me and few other ppl had this problem with ROM, and now I can confirm I have the same problem with the maker... all was working ok, restarted tab and boom boot looped on Samsung loading window... clearing data only help. Rly sad, lowed the debloater... will try to flash firmware again, root and deblote my self with titanium backup, but it won't be the same :(
[Galaxy Tab S2 Android Development] jafangie:
edit: Concerning bootloop, I think that the best way is to follow suggestion below !
[Galaxy Tab S2 Android Development] ashyx:
Might I suggest building the rom without root for compatibility sake and let SuperSU take care of root?

An unpatched or not permissive boot.img will bootloop on Marshmallow.
[Galaxy Tab S2 Android Development] engine95:
I wished I had seen what you'd written before your edit.

Here's where I'm lost. Sorry, but this will be a long explanation.

There have been 28 DL's of the ROM so far. I figure half are installed. So that makes 14 legit installs. 2 of us have it working and 2 others do not. Granted we have a lot of lurkers, but I have to assume the rest have it working. Making me think that 12 installs are working. But with the lack of feedback I can't know what's going on with the ROM and have to assume all is well.

As for a permissive kernel, I only have the 815 as of now. It's in post #2. Which I need to make it's own thread after writing this.

I've requested source a few days ago for the 710 and am waiting for Samsung there.

But MM doesn't need a permissive kernel. In all the testing I did to make this work, the ROM I released worked the best. If I used SuperSU 2.65 or higher, which is rooted through the kernel (systemless), I had 3 apps that didn't have root. When I rooted the /system, root worked just fine.

The 2 extra kernels I've posted, and had people try, don't seem to help either. One of them, I left the padding in. The other, is rooted through SuperSU 2.71 and padded as well if I remember.

I'll post one more kernel after I finish this. It will be as you suggest. It'll be the bone stock kernel pulled from the .tar and I'll have them flash SuperSU 2.71.

I was amazed that MM didn't require a permissive kernel. I've flashed my rom over 15 times to get it right, with no issues.

I do know that the 2 of us that have the ROM working, have Odin'd MM before hand. Maybe I need to add the extra partitions from MM.

Hopefully this all makes sense to both of you. And I'll take any suggestions you both have. But with the lack of feedback, I can't know for sure if there is an issue installing the ROM for the majority of people.

So for now, I'll make a thread for the 815 permissive kernel (that's been requested already), and post the bone stock kernel in post #2.
[Galaxy Tab S2 Android Development] engine95:
[MENTION=4899305]ashyx[/MENTION] [MENTION=234631]jafangie[/MENTION]

I'm going to make a thread for all the Permissive MM kernels. I will give you both rights to edit that thread. That way, we don't all build separate permissive kernels. My git already has the 815 permissive kernel so you can use that for MM if you would like.

Let me know if you both are ok with this. Thanks
[Galaxy Tab S2 Android Development] engine95:
deleted for double post
[Galaxy Tab S2 Android Development] jafangie:
No problem for me...

Yesterday I worked very late on T715 6.0.1 rom w/o good results.

I have bootloop till I flashed bootloader, boot, recovery and cache from rom 6.0.1.

I just wrote that if you are coming from 5.0.2 or 5.1.1 you have to flash this files and gave a link for them.

But because I am not sure 100% what is the source of my other issues... I suggest that is better to follow ashyx suggestion.

For your other idea, I am not a specialist but if I can help It'd be my pleasure.

Jaf
[Galaxy Tab S2 Android Development] rumrunner4000:
Tried flash pre-ODIN MM and ended up with boot loop. Re-flashed with T710XAC2PB1, re rooted with twrp 3.0.0 and SU 2.71 beta(systemless root) then ODINed with MM stock. Flashed with NN -MM-6.0.1-710-V1, updated SU through playstore and flashed twrp 3.0.2-1.

All now working great,including root.

Best NN version so far!!

Thanks very much [MENTION=1280108]engine95[/MENTION]
[Galaxy Tab S2 Android Development] Josephigloe:
Sorry nothing to report since day 1 no issues, this rom is 100%.
[Galaxy Tab S2 Android Development] engine95:
Awesome! Thank you. :good: :highfive:

So you did have to odin MM to get it to work. That helps with things.

MAKE A BACKUP FIRST!! This goes for anything.:p

For all then

Try this first:

Here is the bone stock kernel as pulled from the .tar https://www.androidfilehost.com/?fid=24533100289590376

1. You can replace the boot.img in the ROM with the bone stock boot.img from above. and flash.

OR

Flash the ROM, then flash the bone stock kernel

THEN

2. Flash SuperSU from here. https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip?retrieve_file=1

3. Reboot

Try this second:

Even with the ROM as is, flash Rom then SuperSU. See what that does.

Third option, and I would suggest having PB1 Odin available just in case, is to flash each of these images in TWRP. https://www.androidfilehost.com/?fid=24533100289590377.

Extract the zip, place on int sd, flash images in TWRP, then flash the ROM.

This will give you all the MM partitions, minus /sboot.bin. Don't flash SuperSU

Fourth option, and this is what seems to be working:

Odin MM

Odin TWRP 3.0.0.2

Flash ROM only - no SuperSU

Profit

This may seem like a pain in the .......butt :p But for me to fix things, I need to know what is causing the issues on install. Pleas follow the above steps and let me know what's working and not. Then I have something to work with.

But the surefire way to install this ROM is to follow #4.
[Galaxy Tab S2 Android Development] Josephigloe:
Yes, I Odin'd the MM tar the day it came out, I was not able to root, but I installed twrp, made a backup and down installed the permissive kernel because I missed the part that said it was already included. And then wiped and flashed new rom and everything we as it normally would. :good;good.
[Galaxy Tab S2 Android Development] Moa1480:
Bootloop also. Will try MM-Odin and come back.
[Galaxy Tab S2 Android Development] engine95:
So none of the above steps worked? Even flashing those partitions? That's just lovely. :(

Well, I do know that Odin MM, then flashing the rom does work. Maybe that's the way we need to go.
[Galaxy Tab S2 Android Development] Josephigloe:
Flash the 5.1.1 boot tar
[Galaxy Tab S2 Android Development] ashyx:
I think there's some crossed wires here.

Basically what I'm getting at is that a rooted rom without a patched boot image or a permissive kernel will bootloop since 5.1.1.

This is due to Samsungs root restrictions in the stock kernel and an enforced SElinux policy blocking root and preventing boot.

A patched Sepolicy is required on an an SElinux enforcing kernel to prevent the boot loop.

If anyone installs your rom without either a patched boot image or a permissive kernel then it's highly likely to bootloop.

So as I said for compatibility sake its probably better to leave it up to the user to flash Supersu and let it do the boot patching at the same time as rooting.

At least this way there will be no false bootloop reports saving you from chasing something unrelated to the rom itself. :)
[Galaxy Tab S2 Android Development] engine95:
No crossed wires at all. I understand exactly what you're saying. But as I said, I've gotten it to work without a permissive kernel.

So I have just now Odin'd back to Lollipop PB1, from Marshmallow PD9. So we can have the best of both worlds.

Anyway, I'll work on the Rom from this end now and see what's up.

Thanks for the reply
[Galaxy Tab S2 Android Development] ashyx:
So just to clarify the rom is rooted with supersu, but no permissive kernel or patched boot image required? :what:

How did you manage that, please tell?
[Galaxy Tab S2 Android Development] engine95:
Kids just showed up, so don't have much time.

But I do know that if you Odin M, install root, everything is fine. No permissive kernel needed.

More later....
[Galaxy Tab S2 Android Development] ashyx:
Right, so that implies the boot.img got patched by SuperSU.
[Galaxy Tab S2 Android Development] JekyllInside:
I tried with the alternative kernel + supersu, and it result worse. I got stuck in the first screen with the samsung logo. I don't want to odin MM, just to help to solve this from, like me, who came from PB1
[Galaxy Tab S2 Android Development] engine95:
Right. But to build a rom and flash it, it doesn't work. Patched or not patched.

To make the rom work, I had to install SU in the system. Used SuperSU 2.46 and all is well. Confusing to me, but it worked.

I'll be working on this tomorrow to see if I can get things figured out without using odin. And coming from PB1. Then I can see what's going on.

Strange thing to me is how I can bounce between L &M. Odin and TWRP restores. I've never had that happen with anything Android. And I started messing with Android since Cupcake. Yeah, I'm old. :)
[Galaxy Tab S2 Android Development] :
Hello,I have a T810, what can I do ?
[Galaxy Tab S2 Android Development] efebe:
You can start by reading post #1, right where it says:
[Galaxy Tab S2 Android Development] :
And why don't you port it on T810 ?

You have done T710,T715, T815...
[Galaxy Tab S2 Android Development] Fis2:
Wait

He needs a T810 MM kernel. Waiting for Samsung ROM release.
[Galaxy Tab S2 Android Development] engine95:
It's all good.

The only MM source that is out yet is for the 815. So all of our kernels are on hold. That's why only the 815 has a permissive kernel.

Besides, I need to get this rom to install though TWRP. Without using odin first. I'll be working on that today.

Source for the 710/810 was tied together on PB1, so now I'm curious if they"ll combine the 2 now.

Each S2 has its own ramdisk also. Which is needed even if source was posted. So I need MM kernels to pull those.

So just give me some time. It's a whole new learning curve with MM.

I do need a tester for the 815 though. I have a very Alpha ROM I need someone to test.
[Galaxy Tab S2 Android Development] :
ok thanks
[Galaxy Tab S2 Android Development] ashyx:
You need to ensure su.img is installed in data as that is where the magic su binaries are.

The ramdisk mounts this at boot time. It won't work with a patched boot image alone.
[Galaxy Tab S2 Android Development] engine95:
Yeah, I found that when I tore through SU this morning.

I think what I did was removed some SU files I shouldn't have to get the rom to work.

And coming from Odin'd MM, everything was working fine. I just assumed it would flash from PB1.

I did too many projects at once. My desktop has all kinds of scattered files. So now I'm confusing myself. Lol

Guess I need to slow down and start from scratch.

At least there's a MM ROM for people to use if they Odin MM first.
[Galaxy Tab S2 Android Development] jafangie:
I don't know why.... But it is exactly the same thing for me!

Jaf :)
[Galaxy Tab S2 Android Development] engine95:
Does anyone know if sboot.bin goes to mmcblk0p1 or mmcblk0boot1? Samsung doesn't list it like LG does. [MENTION=4899305]ashyx[/MENTION] since you're the recovery guru. :good:

I'm pretty sure that's what's messing things up. B to C being whats needed - CPD9 vs BPB1. But I don't want to flash the wrong partition to find out.
[Galaxy Tab S2 Android Development] ashyx:
Neither, they are both the same partition. The bootloader has a different address. It doesnt even get listed in the partition list. Also it cant be flashed as it is read only. Only ODIN can flash the bootloader as it contains code which allows it to communicate with the nand chip and write to it. Even heimdall cant flash the bootloader.
[Galaxy Tab S2 Android Development] engine95:
Samsung is just full of surprises. Glad I didn't try that then. I was hoping. Thank you.
[Galaxy Tab S2 Android Development] engine95:
To everyone:

I have tried every single thing possible to get MM to flash through TWRP from PB1. I have Odin'd L & M multiple times, I've tried a NO Root ROM with no mods, Rooted ROM with no mods, and nothing will work. Everything just bootloops. I can't even get the logo.

So if you want M early, then you will HAVE TO ODIN M first. Install TWRP 3.0.2.0, and flash the ROM if you want it. I will add this to the OP also.

I'm at a loss and have spent most of a day and a half trying to work this out. And I'm spent. :eek:
[Galaxy Tab S2 Android Development] mangui:
Hi engine95, we appreciate your efforts. I have a Note 4 (exynos 5433), and the community there is on the same boat. They haven't been able to do a complete installation from TWRP. Hani K. however, provided the bootloader as a separate file to be flash with ODIN, followed by the modem, and then the ROM from TWRP. It saves not having to download the entire MM firmware. After I installed the bootloader and modem once, I have not had to do it again. I have flashed the Hani ROM and Erobot multiple times from TWRP. I don't know if it will simplify the process until the permanent solution comes along. If any developer cracks it in the N4 forums I'll let you know. Again thanks for the efforts to you and the other developers.
[Galaxy Tab S2 Android Development] engine95:
Thank you.

I'm thinking about doing that same thing. But I'm outta time for a couple days. So for now, it's the whole enchilada from me. ;)
[Galaxy Tab S2 Android Development] engine95:
Brain cramp. Posted this in the wrong thread.

http://xdaforums.com/showthread.php?p=66802990
[Galaxy Tab S2 Android Development] bitelmaniaco:
Do you think now in us?

http://samsung-updates.com/device/?id=SM-T810

;)
[Galaxy Tab S2 Android Development] engine95:
It should be just like what we've done with the 710. Now that the 810 has a kernel, I can start working on it.

I still don't have a working updater-script. It breaks wifi and something else.

But I haven't spent much time working on that yet. So I may need to have the 810 flash a second file for now.

Once I have a working updater-script, I can take an 810 image and go from there.
[Galaxy Tab S2 Android Development] bitelmaniaco:
Thanks, take your time!!!
[Galaxy Tab S2 Android Development] engine95:
Major Edit: It is not working for the 810 to get Neked Nook. I tried L tricks on M. And as I thought, (but was hoping) it didn't work.

810 users that want MM now. MAKE A BACKUP FIRST!! And to cover yourself, I would have PB1 and MM Odin files handy.

This is what us 710 users are doing: This may not work for the 810 but SHOULD.

Odin MM

Install TWRP

Make a backup in TWRP!! I would do it before rooting

Flash SU 2.65 or higher

Reboot

There is also an 810 init.d kernel in post #2. It's already included in files2.

For my past 810 testers: [MENTION=5193466]DroidIt![/MENTION] [MENTION=5660714]Billy06010[/MENTION] and [MENTION=3271104]skawtnyc[/MENTION]
[Galaxy Tab S2 Android Development] Billy06010:
Am I missing something?? how can i odin marshmallow on the t810 in the US?? i will try you're method engine95 as soon as i can odin MM in the US
[Galaxy Tab S2 Android Development] engine95:
It's all good.

It works on the US. I've been using it since it came out. And I can restore back to L also.

But don't feel obligated. It's your choice. :)
[Galaxy Tab S2 Android Development] Billy06010:
so i odin the German version on my US t810?? then if i want to use you're rom i flash that?? and flash the t810 file after?? or do i just flash your rom even though i'm still on 5.1.1 and then the second file. sorry i'm a bit confused and trying to understand.
[Galaxy Tab S2 Android Development] engine95:
Edit: Disregard this whole post!! It is not working. I tried L tricks on M. And as I thought, (but was hoping) it didn't work.

If you want Neked Nook MM

Odin MM - Germany works in US. You'll only lose upper bands of 5g Wi-Fi.

Odin TWRP 3.0.2.0

Make a backup in TWRP without root, and do not root

Flash Neked Nook

Flash 810 file2

Then reboot

Not everyone wants Neked Nook. So that's why it has that wording. But if you follow it, its the same as what I have above.

I have Odin'd PB1 and MM multiple times. And I have restored back to PB1 from MM multiple times. So there shouldn't be any issues for fixes.

Again, dont feel obligated. :)
[Galaxy Tab S2 Android Development] skawtnyc:
The 810 is going to need an 810-specific ROM. The method above resulted in the same issues as the last time we tried this: Screen unresponsive and turned 90 degrees, display glitching. Going back to the default German 810 6.0.1 firmware until we have a working ROM. In the meantime I'll try the permissive 810 init.d kernel.
[Galaxy Tab S2 Android Development] engine95:
Now that's interesting. I modified the same files, plus one more, that got it to work on OJ7

Remember, I haven't had a system image for the 810. And these files should make it the 810. Unless it didn't flash.

OK. I'll pull it and test it on my tab. Thanks.