yashsingh1/xdaforums huggingface dataset:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] kenar2:
Very wierd.The only explanation is that I was on Agni and I didn't use Agni Cleaner tool. I'll try latter.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Hbohd:
Tested myself and it booted.. Maybe clearing caches would help? Or clean install? :p
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] LeoDeos:
flashed two times with wipe cache and dalvik
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Hbohd:
Weird then :( The only thing I might recommend now is clean install (but who wants to do that frequently) or go back to earlier version.

However, if similar reports will appear, I should take a look at it.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] kenar2:
Again tested, used Agni Cleaning toll, wiped cache and it boots.

SELinux Permissive.

Edit: [MENTION=5022895]LeoDeos[/MENTION] same rom different result :( wierd wierd
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] LeoDeos:
i used agni cleaner, but i have the same result

now i try with full wipe

Edit: [MENTION=4731772]Hbohd[/MENTION], I also tried with full wipe but nothing has changed...forever stuck on samsung screen.

Now do the last test and let you know.

Edit2: ok, i give up.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] P$T:
I'm sorry, I forgot to answer your question. At this time 5.1 and 5.2 kernel build already has NA2 ramdisk, so if you need build with some older ramdisk just send me boot.img from other rom :good:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] djb77:
That's ok mate :)

I didn't know what ramdisk you guys used, so I guess the question was just more to see what you guys are using.

Still trying to work out how to get a splash screen to work properly with the kernel, when I figure it out I'll pass on the info to you and Hbohd.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] djb77:
A new XXUENC1 Kernel has come out, I did a comparison on the Ramdisk and found there was only a few differences:

/lib/modules/dhd.ko

/lib/modules/scsi_wait_scan.ko

xbin/adbd

I don't know if there is any differences elsewhere since I'm not that good at kernels yet.

Anyways, here's the Stock XXUENC1 boot.img and I've attached the different files in this post.

Hope this helps you with your development :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ridanxvi:
I also tested it and stuck on samsung logo, using kenar2 deodexed rom
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
SELinux permissive version boots and works well here on TGP v15.30 ROM...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Hbohd:
Heh, then we have two different reports (it booted fine for me too, so I uploaded it). I have no idea why it is so, yet :(
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] kazoum:
I've tried the last Permissive kernel available in this thread and it booted with no problem. I came from AGNI and before installing Boeffla, I flashed AGNI cleaner and then wiped Dalvik and cache.

It has been 24h since I flashed it and, although I am not having the instability problems I had with previous Boeffla versions, I still notice some more instability when comparing to AGNI (which I used for 3 weeks, +-). Today I had no problems yet but yesterday I had a Samsung Keyboard FC and 2 automatic reboot.I also had CPU overheat and battery drain (with zzmoove optimal) but I really hope all this only happened because my phone is still "getting used" to the kernel. Anyway, I removed all undervolt I had to see if the phone works better. Will report in a few days.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ShonkUK:
Doesnt boot for me with 4.1.2 bootloader and my rom
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
[MENTION=4131406]kazoum[/MENTION] and [MENTION=3725242]ShonkUK[/MENTION]: I am testing also the Kernel v5.2 SELinux permissive version.

I have the "old" bootloader (from Samsung official JB4.1.2 rom).

The ROM I use is TGP v15.30 (JB4.3).

Kernel permissive is booting fine; however I also noticed few hot reboots time to time...

The reason for testing the permissive version is that with the SELinux "disabled" version, I was unexpectedly and randomly losing root (su binary deleted!!!).

I am not sure that losing root has something to do with SELinux being on "disabled".

Only time will tell... Did anyone hear about similar strange random su binary deletion?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] djb77:
[MENTION=4731772]Hbohd[/MENTION]

I'm about to do a new TGP release soon (XXUEMC1 base), do you want me to include the SELinux permissive beta or hold off until it's more tested / stable ?

---------- Post added at 10:53 AM ---------- Previous post was at 10:49 AM ----------

I've heard of the "su binary deletion" I'm pretty sure, it's one of the issues of 4.3 when dealing with SELinux or KNOX. The author of SuperSU had a new method of installing su which I also incorporated into my ROM. Unlike the old says, the su binary isn't just copied to /system/xbin, it's set up in /system/bin and /system/etc/init.d as well. The next time you get the error of su being deleted, try rebooting your phone and see if that gets su back. There's an init.d script which is incorporated with the su binary and it may fix it.

Please let us know how this goes.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
WOW!!! I googled, I searched XDA, I searched the Web... I could find only 1 poor guy asking for help relatively to "su deletion". However, he was just talking about "losing root" on a Note 2 or 3... and no one could find an answer for him...

So I'm happy you heard of it! It means I'm not alone!!! ;) Thanks for sharing your knowledge/experience!

When I say "su binary is randomly deleted" - it is something happening approximately once in a week time - so it's not too dramatic, but very irritating!!!

Ok, I see what you mean with the init script 99SuperSUDaemon calling /system/xbin/daemonsu.

I have seen this first after flashing AGNi kernel, and I now see it is in your ROM TGP as well (that I stated to use 7-10 days ago...).

Some remarks:

1. The use/presence of daemonsu does not prevent su binary from being deleted

2. I never tested the method you mention: "reboot and it should be back", because when it happens, I just go ahead and reboot into recovery and flash CF rooting zip again. I will try next time.

3. I searched all methods/ways to get rid of KNOX and created my own script to "totally remove" KNOX, because all those that I could find were incomplete (I mean they were all deleting something specific that others didn't delete) - but su binary still gets randomly deleted

4. I thought it could come from the custom recovery so I flashed the stock one - but su binary still got randomly deleted

5. My only hope at this point is to have a kernel which is SELinux permissive instead of disabled... I cannot flash stock kernel since I am with old JB4.1.2 bootloader...

So far so good with remark #5... I'll let you know...

Any comment/remark/idea from the community is welcome!!! Thanks!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] showmany:
Where I can find 4.x kernel for 4.1.x roms? I don't see any link in OP. I'm asking, because I want to try the latest MIUI V5 4.4.4.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
[MENTION=4280397]djb77[/MENTION] [MENTION=4731772]Hbohd[/MENTION]

Ok, this morning I lost su again (su binary deletion).

This was with permissive version of the kernel... so no luck on that side...

I am out of ideas as of what is causing this random deletion or how to prevent it...

I immediately rebooted. No stop at recovery, no flashing rooting zip, just plain usual simple reboot.

And 99SuperSUDaemon did the job! After reboot, su binary was back! Nice feature that I didn't know...

Trying to go further, wouldn't it be possible to trigger 99SuperSUDaemon periodically to make sure su binary is reverted on the fly in case of deletion?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Hbohd:
I never had that issue (or I haven't noticed it), but now I will investigate it. Thanks for reporting and your devoted time! :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
By the very low number of people talking about / experiencing this issue, I am sure that it is not common.

Not common = difficult to track down and debug...

On my side (and I'm not a newbie) I tried everything I could think of...

I'm just thinking... maybe the kernel could trigger 99SuperSUDaemon (or call /system/xbin/daemonsu with appropriate command line) periodically so that su is revereted on the fly in case of deletion...???

Or the kernel could periodically (or permanently) monitor the presence (or not) of the su binary and trigger 99SuperSUDaemon only when su is not there...???

Would that be possible at all?

Cheers
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] P$T:
little kernel update

Small update from me: ramdisk NC1 + linaro 4.9

Enjoy!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] djb77:
Cool, I give this a test drive and throw it in the new ROM.

Is there any chance the SELinux permissive version can get the same update?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] P$T:
Me and [MENTION=4731772]Hbohd[/MENTION] still thinking about it but this version is still not prepared properly. I'm out on this weekend, but after back to home try to something to do with this.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] djb77:
OK no worries.

Would it be a problem if I put the 5.2 SELinux test version in my ROM as an option, or would you prefer for me to leave it out?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] P$T:
Sure, if you want :good:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ShonkUK:
I have been thinking about 5.2 permissive failing to boot on my stock based rom

Something knox related must be needed that i have pulled

here are all the pulled files from it if anyone is bored..

http://pc.cd/ft8
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] dedelamalice:
someone as this kernel in stock: i9305-Boeffla-4.0stable-by-hbohd-13-11-2013.zip

Thanks
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
Here you go! I never delete anything... o_O :D

This is the kernel for Samsung Stock ROM on JB4.1.2, you know that, right?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] dedelamalice:
Thanks a lot
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
"Dédé la malice"... that sounds so french! Bienvenue compatriote!

You could as well hit the "thanks" button... ;)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] kazantip1288:
and what about 4.1 stable? do you have it?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
Sorry I don't have that one...

When I bought my S3, it came with 4.1 but 4.1.2 was already out, so I immediately updated and started from there...

---------- Post added at 08:52 AM ---------- Previous post was at 08:22 AM ----------

@Hbohd & [MENTION=2045619]P$T[/MENTION]... what about recent updates?

The i9300 kernel has been updated to v5.3b2 yesterday...

Thanks!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Hbohd:
5.3-beta3

New 5.3-beta3 for you guys.

SE version is with selinux permissive. Version without SE in name, is with disabled selinux.

Based on the newest ramdisk provided by djb77 and compiled with linaro 4.9.1

Consider this NO TESTED at all, because I am on AOSP for now. Report bootloop, strange bugs etc. You may always go back to previous kernel by going into recovery (home + volume up + power for few seconds) and flashing it.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] djb77:
I can give the disabled SELinux version a test drive.

The only way I'd be able to test the SE Permissive version would be if I had KNOX right?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Hbohd:
You may look into 'device info' at the bottom of settings and check 'selinux state' (or sth similar) :p
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
You could test either version if you don't have KNOX (both should work).
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] kenar2:
I confirm status SELinux Permissive with SE version, i'm on old bootloader. No bootloop.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Jarmezrocks:
Hey guys,

The CWM reset script doesn't work? It holds onto GPU settings? How do I reset the GGPU settings. I accidentally went overzelous with the GPU in the app not thinking settings would be immediate! Straight away the device became unstable with fragments, so I figured I would reboot seeming I had not committed the settings just now....but unfortunately rebooting was a bad idea; I could not use the phone at all after rebooting so could not get into the config app to reset anything. I rebooted and attempted to use the reset script from recovery and it reset everything except GPU? Why? I booted and the standard profile notification appeared and then soon after GPU fragments and complete lockup frozen unresponsive.

I have had to perform a wipe to get back to usable phone but did a nandroid before I did. I would really like to restore that nandroid and undo the settings rather than resetting up the whole device again. Even Titanium is time consuming to reset up everything, so if you can share a way for me to reset the GPU settings that would be great.

Thanks
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] showmany:
[MENTION=3857816]Jarmezrocks[/MENTION], This is not helping?

http://boeffla.df-kunde.de/sgs3/other/boeffla-config-reset-v2.zip
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Jarmezrocks:
WORD OF WARNING DON'T USE THE LATEST CWM RESTORE SCRIPT ON I9305!!!! WIPE EFS/ IMEI.

I have notified Boeffla after doing some testing on the latest kernel. If you need to reset, for now (at least until he updates the script to use more generic calls to mount the data partition) remove settings manually.

I have suggested a new script like so

ui_print("");
ui_print("******************************");
ui_print("* Boeffla-Config Reset V2 *");
ui_print("* *");
ui_print("* (current profile will be *");
ui_print("* reset to stock settings) *");
ui_print("* *");
ui_print("* (c) andip71, 23.10.2013 *");
ui_print("******************************");
ui_print("");

run_program("/sbin/busybox", "mount", "/data");

delete("/data/.boeffla/startconfig");

unmount("/data");

ui_print("Finished!");
ui_print(" ");
ui_print("Please reboot now.");

Current script is below. I have highlighted the issue in red. For our devices we would need "/dev/block/mmcblk0p16"

However for simplicity I have suggested the above cause this should work on all devices.

ui_print("");
ui_print("******************************");
ui_print("* Boeffla-Config Reset V2 *");
ui_print("* *");
ui_print("* (current profile will be *");
ui_print("* reset to stock settings) *");
ui_print("* *");
ui_print("* (c) andip71, 23.10.2013 *");
ui_print("******************************");
ui_print("");

mount("ext4", "EMMC", [B][COLOR="Red"]"/dev/block/mmcblk0p12"[/COLOR][/B], "/data");

delete("/data/.boeffla/startconfig");

unmount("/data");

ui_print("Finished!");
ui_print(" ");
ui_print("Please reboot now.");

Here is a safe version of this script if someone would like to test it for me (while I restore my IMEI) The download is >>> here

---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------

DO NOT use that script on our device!!!! I repeat

DO NOT

use this restore script
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] showmany:
Strange, I used this script yesterday without any problems with my IMEI number. :confused:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] .NetRolller 3D:
As I read the "bad" script, it just deletes a single Boeffla-specific file, it doesn't wipe the mounted partition. So, it should have no effect at all on the I9305, as the Boeffla config file should not exist on the EFS partition.

Besides, on the I9305, the IMEI doesn't reside in EFS, but in the Qualcomm modem's own NVRAM.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Jarmezrocks:
I'm telling you this wiped my EFS. If you want to use it go right ahead. The partition that it is calling to mount data is incorrect! This is exact same issue we've had when people flash I9300 ROMs on I9305. I no longer have an EFS and I am in the process of working out how to restore it from my backup.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
Strange... according to: http://xdaforums.com/galaxy-s3/development-i9305/info-i9305-information-regarding-t1926813

mmcblk0p12 is CACHE partition

DATA is mmcblk0p16

and EFS is mmcblk0p3

This doesn't seem consistent with your observations...

However... it's true that according to http://xdaforums.com/showpost.php?p=28196126&postcount=14, mmcblk0p12 is USERDATA for i9300.

So in any case, mmcblk0p12 is not pointing to the same thing depending on the variant i9300 or i9305...

Bottom line is: script needs to be corrected and made "universal".

Strage however, that no one had any issue with the official script until today...!!!???
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Jarmezrocks:
Yes I noted this already >>> here

I have provided an alternative script here for people to be able to test/try >>>> here

This script uses non-explicit mounting points by using the busybox binary included within the script. This also accounts for any differences between Samsung and AOSP ROMs having local busybox in different locations.

Quoted from the other thread my personal take on things
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] areyie9292:
boeffla config v2 and SE state..

i have flash SE version, but does show SE permissive.. i'm on new bootloader.. i also have a problem with boeffla-config v2.. before this, it working perfectly.. but now, it doesn't work..
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Hbohd:
Firstly, thanks for your report! If you are sure that you flashed SE version and you still have 'enforcing' then something is wrong :(

I will try to investigate that again in coming day or two.

And second one: it happens to me sometimes too. What you can do is

- delete boeffla-kernel-data from /sdcard (your custom profiles will be deleted too!)

- remove root rights for boeffla config in supersu and give them again

- reinstall boeffla config app

- reflash kernel

One of these above should do the trick :p
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] areyie9292:
1st flash, it show permissive, and config boeffla working.. after i reboot my phone, it show enforcing, config boeffla also doesn`t work.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ShonkUK:
Triangle Away doesnt work this these btw

i9305-Boeffla-5.2-pst-20140424

i9305-Boeffla-5.3-beta3-by-hbohd-20140513

had to roll back to

i9305-Boeffla-5.2-by-hbohd-20140327
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
What precisely doesn't work?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ShonkUK:
umm unsure if your joking or not

triangle away does one thing...

im clearly not talking about knox 0x1 as triangle away doesnt do that
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
No joking! ;)

There are different opinions about what TA should do...

Usually from day one on my i9305:

* Flash counter remains at 1 with TA (can be put from any flashing value down to 1 easily but not down to 0...)

* The red sign on booting splash screen remains as long as custom kernel is used

Some people would thing that the 2 above limitations are equivalent to "TA is not working".

Here I understand TA doesn't have any effect at all on flash counter.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ShonkUK:
It resets it back to 0

if you boot straight into odin mode it will show 0

then on first boot it will goto 1 due to having a custom kernel

ofc if you had a stock kernel with matching bootloader it would stay 0
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] djb77:
Here's a fixed version of 5.3 beta 3 for you all.

The CWM recovery script has been repaired and will now work as intended.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ShonkUK:
can i get a copy of the source

I have decided to dabble with the kernel and

just did a git pull only to find out there hasnt been a commit since november 2013
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] paffo:
Anyone have link for latest Boeffla for 4.1.2 stock rom?

I belive that was 4.0 stable or 4.1 ?! and dont know why link for that disapeared from op!!

I know that kitkat "may" come, but what I need is stable system, not new features and downgrade looks like good idea for me.

I also know that I am not a good example for developers here cause they need a lot of meat to test their new compiled code, but Im just tired to try new roms and to old to play with my phone and want to give this device very last chance :)

Hbohd: can you restore links to 4.x version of your kernel, please ?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
You could use the search function.

You are not the only one who asked for this...

http://xdaforums.com/showpost.php?p=52288826&postcount=646
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] paffo:
I already searched, but in conversation Hbohd mentioned next version after 4.0

And my question was to restore links in op
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
I'm following this kernel since v4.0 stable.

Unless I missed it (which is still possible) - I don't think there was ever a higher version for JB4.1.2.

In my mind v4.0 stable is the latest version for JB4.1.2.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Hbohd:
I don't think I might 'restore' those kernels. In fact, I erased them from EVERYWHERE, so I haven't got any backup :(

4.0 stable posted by Looki is the latest available version for 4.1.2 Sammy JB, sorry.

I think that there is nothing bad at updating your system to 4.3 Sammy JB.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Looki75:
Agreed - Sammy JB4.3 is a very stable and bug-free ROM. Works flawlessly.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] P$T:
I was compiled latest beta version for you guys. Unfortunately for now only version for old bootloader, because I don't have settings for SE version. This should be later or maybe [MENTION=4731772]Hbohd[/MENTION] compile this one faster than me.

You must forgive me for my oversight, on settings kernel version should be beta6 ;)

Enjoy!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] LeoDeos:
thanks for the new kernel.

on settings kernel it is beta5
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] 1Ishara:
Hi guys im on new bootloader can i use new virsion with it.. i heard that selinx su be permiv. So can i use new virsion.. or else is there any virsion i can use?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] djb77:
A did a comparison on the NC1 and NC2 Ramdisk, and here's the differences.

2 files this time: /lib/modules/dhd.ko and /lib/modules/scsi_wait_scan.ko
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] paffo:
Recall old problems with your kernel:)

While charging cpu freq stays at top and thats is reason you delete I think :)

Happily I bought a while ago Tasker, and prepared profile that is lowering max cpu freq when screen is off, and next one for runing navi in a car while charging.

And rom 4.1.2 is much better for this device, faster and battery stays twice longer. Its not that smooth like 4.3 ofcourse, but its nothing compared with stability it gives.

Long live the Jelly 4.1.2 !
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] josito801:
What version of boeffla I use Miui 4.1.1 with Stock? Is it enough flasearlo for recovery? Thank you.

Edit: ok 4.0 Stable: https://copy.com/tNF8Jd3dJSExOmMe
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] jonoathome:
I've come across this problem before with boeffla can't remember the fix. .

No sound in call with the latest beta.. On Alliance Rom..

Any ideas.. Thanks in advance
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Hbohd:
Reboot? Resetting app? Reflashing kernel? Wiping cache?