yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] imfaraz:
Battery life is not effected by this Kernel yet. I am trying to integrate different things in it. But because i am a part time developer, i need more time to get things done as i am only one working on this Kernel and as for BLN support, i added this my to-Do list.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] IvoDi:
Good job!

Works fine on A510F.

Can You implement init.d support?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Il lio:
Is normale that after flashing kernel i've to root again the device? :confused:

After the First reboot supersu does'nt work properly, I had to uninstall

And after install from the recovery the zip supersu file

Thanks in advance
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ashyx:
Yes it's normal. Systemless root patches the boot.img.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] PedroMarthon:
can I know the system size of A510F please
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] leonard208:
Flashed via twrp

Working good

Only thing that is bugging me now is the built in security

App is saying

Unauthorized actions detected

And it won't go away in notifications

Samsung a710fd.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Gi4nnelli:
Use titanium backup and freeze the SecurityLogAgent and the notification wont come back
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] leonard208:
Okay Thanks I'll do it.

Edit: Doesn't seem to work, still getting the notification
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ardybelu:
ardybelu@gmail.com

PLEASE MY MY PHONE SAMSUNG SM-A510F A510F APB1 U1 / APB2, CAN NOT UPDATE TO HELP MY SETTINGS FACTORY IS THERE Fireware FOR MY DEVICE

---------- Post added at 07:41 PM ---------- Previous post was at 07:37 PM ----------

PLEASE MY MY PHONE SAMSUNG SM-A510FAPB1 / APB2, CAN NOT UPDATE TO HELP MY SETTINGS FACTORY IS THERE Fireware FOR MY DEVICE:confused:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] leonard208:
Please Google sammobile for your firmware
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Interceptor13:
hello please tell me if in the future I want to get everything back to the sink, wipe and conventional flashing the factory firmware, the kernel will return to the drain? Or will be the same in the permissive mood
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] pl1997:
[MENTION=6098208]imfaraz[/MENTION] thanks for bringing some developper attention to our device :P

any news about BLN support yet ? thanks in advance
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] :
Thnks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 12ashu12:
after flashing the kernel I can see permisssive SELinux (in the software info section of the phone).

But, I'm losing root access.

After flashing the supersu in TWRP, I get supersu but now I cant see Permissive SELinux.

Please help !!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] leonard208:
Flash kernel . Then flash supersu. Zip

And start all over again before following these steps
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 12ashu12:
Thanks [MENTION=3293209]leonard208[/MENTION] ..

I'll do it right away :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] leonard208:
No problem [emoji1]
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 12ashu12:
I still cant see selinux as permissive.

this is what I did :-

1)Flashed SM Kernel via Odin.

2)Flashed twrp 3.2 via odin.

3)flashed supersu zip via twrp.

Now, when i first flashed SM kernel, i could see selinux as permissive, but when i flashed supersu zip , i can't see permissive selinux any more.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] leonard208:
[MENTION=7502278]12ashu12[/MENTION] Your doing something wrong . When you flash the supersu.zip there is no way you can loose permissive.

Then supersu patches the existing kernel( which is the permissive kernel ).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 12ashu12:
Yes, i got it right this time :)

I was actually flashing the "beta" version of Supersu.

when i flashed the "stable" version, everything got fine !!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] freshash:
hi anyone got viper to work when use the kernel? sorry for ask:D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sang024854:
hi! i got same problem but i cant fix that, can you tell me what i should do now?

My phone is A7(6)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Sophia.xda:
What is the benefits of new kernel?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ashwini215:
In this kernel, SELinux is Permissive, which means you can install some Awesome apps Like 'Viper4Android', 'Xposed' :D:D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] godtohcj:
Soft keys are not working

Hi guys, I need help in bringing the soft keys (menu and back button) back in working mode. I flashed this kernel on Samsung a5 2016 (A510Y) to get a "permissive" SELinux mode so I could get the viper4android working. I was able to get it in a permissive mode but the menu and the back button (as well as the back light) are no longer in function. I'm using LMT app in the mean time and any help will be pretty much appreciated.

:)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] _euphonic_:
could you make this one for sm a310f (a3 2016)?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] a.fontenele:
...and A710M too?

:D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] vip009:
Help , error : system rev check fail device 1 , binary 0 .
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ashwini215:
its not working in marshmallow, A710FD :(

Could you please provide one for 6.0 !
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] darwin345:
Hello,

I get this message in red when my SM-A510FD boot : "Kernel is not seandroid enforcing".

I'm on android 6.

Any Idea ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] SliperHR_:
Getting error on A510FD Mashmallow

Error : kernel is not seandroid enforcing

Running on :

-GRACE UX - system UI

-TWRP and rooted device

Need urgent reply .

---------- Post added at 01:08 AM ---------- Previous post was at 12:47 AM ----------

Recently ,

I got the same problem as you . While waiting for dev to solve the problem . U can try ADM Kernel which is download link

-https://www.androidfilehost.com/?fid=385035244224400203 http://forum-lw-1.xda-cdn.com/images/smilies/fingers-crossed.gif

Instruction .

1. boot to download mode

2. Odin using AP flash .
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ashwini215:
You will need to flash your rom again.

And you can use this kernel if you want permissive kernel.

http://xdaforums.com/samsung-a-series/orig-development/kernel-adm-team-a510f-v1-marshmallow-t3506297
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] SliperHR_:
I tried 3 rom with this kernel and the result is same .
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ashwini215:
I've A510FD & I had no problems as such.

When you get the error, try to boot into download mode and reflash the stock rom, MM in your case.

After this, flash the twrp provided by Ashyx for A510FD for MM.

You will find different zips for MM & LP. Choose the one for MM.

Directly boot into twrp & then only restart your device.

After that flash the permissive kernel zip & hopefully things will work for your. :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] darwin345:
Thanks !!! I'm installing now, I'll tell you if it's working !
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] IvoDi:
Hi!

Can You post .config?

Thanks...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrjoy:
Any more updates?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Ciprum:
Getting "Kernel is not seandroid enforcing" at boot logo. Doesn't even get to the boot animation, the phone just shuts off.

Booting into download mode and recovery still worked so I was able to restore the backup and get the phone up and running again.

Galaxy A510F (Croatia), 6.0.1

If you need any files/info about the phone just ask here. (make sure to [MENTION=5764334]janekmuric[/MENTION] me)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] deepray:
Flashed using Odin on SM A510FD indian version. Got error on Galaxy Logo : Kernel is not SeAndroid Enforcing and got blank screen. Recovered by flashing stock ROM. Dont know the issue. Any suggestions ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ashwini215:
This kernel is for Lollipop.

If you are using Marshamllow, then you will have to flash other kernel like ADM kernel.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] leejunsong:
Plz build for MM and add variants A7108 :D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] brocken__heart:
A510fd android 6.0.1

Didn't work for me bro. It say kernel is not seandroid enforcing something and bootloop. I had stock rom flashed boot back. What can be problem. A510FD Running on android 6.0.1 UAE ROM.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ashwini215:
I hope you read the posts before posting your question :)

This kernel is for Lollipop & not for Marshmallow.

Try some other kernel, if u r using marshmallow.

kernels for MM are already available in the forum of A series device :good:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] NetfariousIntent:
If you can add AOD support please?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] brocken__heart:
Bro the information is not there it says it supports a5 & a7 not marshmallow or lollipop. I already did with the link provided in one of the comments. Thanks anyway.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Adyssx:
Tested on SM-A510F

Hey

I,ve first made an backup with twrp.

than i flashed your file with odin and got a bootloop.

so it doesn,t works for me ;( i belive its bacause i have an android 7? downloaded form here: https://xdaforums.com/samsung-a-series/general/android-nougat-t3598530

Also i have SuperSu root verson 2.82 installed.

I will try your Kernel again if its get updated ;)

Edit: After restoring boot with twrp com.android.phone prozess keeps crashing... bluetooth also doesn,t works anymore. I belive its not because of the kernel but it happend directly after my try to flsh it
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Mizan96:
Help

Can I try it with Samsung galaxy a7 2016 marshmallow?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Mizan96:
Thanks. But can you make one for Marshmallow or Nougat, please? Just permissive for stock rom and nothing else\
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kalyan22@:
Plz try to made super stock kernel for use Samsung pay after root

Like this I see this post from other device

https://xdaforums.com/s7-edge/development/kernel-superstock-v1-3-5-t3453462
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Maxim228:
Hello [MENTION=6098208]imfaraz[/MENTION],

Im A710F owner.

I can be a beta tester. I made 2 ROMS for A7 (on 4pda - ported A5 infinity rom and modded Advanced Seven called Advanced Nougat), I know some little things. I hope that this project wont be discounted, becouse there is only one kernel for A7 16 - Advanced Seven Kernel by jjjhitel. His kernel old, but very well working, supports blue light filter for example. Also I hope, that your kernel will support fake knox 0×0 :fingers-crossed:

Or just make new, well working kernel.

Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Maxim228:
I posted your kernel on 4pda forum :D

http://4pda.ru/forum/index.php?showtopic=829339&view=findpost&p=69526953
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Mr.J#:
anyone help me to port this rom. PROBLEMS VIE FLASH

AROMA INSTALLER version 3.00

(c) 2013-2015 by amarullz.com

ROM Name : BASIC ATTACHER STOCK A51xxx PURE ROM

ROM Version : 1.0.1

ROM Author : MR.J

Device : SAM GALAXY A5

Start at : Fri Apr 13 03:00:22 2018

************************************************

* Installing BASIC ATTACHER STOCK A51xxx PURE ROM

* For SAM GALAXY A5

* Running android 25

* Developed by MR.J

************************************************

-- Preparing device partitions

Extract: /tmp/efs_backup.sh

Extract: /tmp/flash_kernel.sh

Extract: /tmp/wipe.sh

about to run program [/sbin/mount] with 4 args

mount: mounting /dev/block/mmcblk0p20 on /system failed: Device or resource busy

run_program: child exited with status 255

about to run program [/sbin/mount] with 4 args

mount: mounting /dev/block/mmcblk0p23 on /data failed: Device or resource busy

run_program: child exited with status 255

-- Backing up efs partition

about to run program [/tmp/efs_backup.sh] with 1 args

__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!

__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!

mount: mounting /dev/block/mmcblk0p23 on /data failed: Device or resource busy

__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!

__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!

tar: removing leading '/' from member names

-- Continue without safe format

-- Continue without hard format

-- Extracting system & data

-- Creating symbolic links

symlink: failed to remove /system/csc_contents: Read-only file system

symlink: failed to symlink /system/csc_contents to /system/csc/INS/csc_contents: Read-only file system

script aborted: symlink: some symlinks failed

symlink: some symlinks failed

Installer Error (Status 7)

End at : Fri Apr 13 03:00:22 2018

PLZ HELP me
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] M_J_Nazari:
It seems sbin/mount cannot run on device and partitions didn't mount to modify.

its a script problem, author must mount partitions on other methods.

The problem is about to mounting partitions or right permissions to executive applets
[Xperia Z3 Compact Q&A, Help & Troubleshooting] artie_ficial:
Hi,

I hope somebody is willing to help me; I couldn't find a guide covering exactly the same problem. Actually, I'm "just" looking for the right order of steps I should perform in order to restore the factory state of my Z3C. I'm currently running Cyanogen Mod 12.1 with unlocked bootloader (obviously). I would like to return to being able to use the DRM Camera functions. Afterwards I'd probably like to try another ROOTED stock-based firmware. (Thus the DRM functions should still be available again, right?)

Current setup: CM 12.1 + bootloader Unlocked + TA Backup has been performed

Aim: flash stock firmware + restore DRM functions + install (pre-rooted) stock-based firmware

What I don't understand: If I re-flash stock firmware the phone won't be rooted anymore, Custom Recovery is going to be lost, right? Is it right to T H E N restore the TA backup? (As the bootloader will be automatically relocked?) Or do I need to perform additional steps or the above mentioned in another order?!?!?

And: Can I then simply flash a stock-based ROM without losing the DRM functions again?

Thanks in advance!
[Xperia Z3 Compact Q&A, Help & Troubleshooting] marshalpear:
You simply can not restore back to factory state of your phone unless you have backed up your DRM keys. I'm thinking that you haven't so...

Anyways, you can use a pre-rooted stock ROM and you will have stock state of the Z3C and also root. To do this, you simply download any of the many alternatives in xda. I, myself, recommend you to use Wajk's SlimROM. It has good features, good debloat and awesome battery life. You'll be on stock ROM and have root but you won't be able to use DRM functions. If you want the DRM functions so badly there's a way to spoof it. You can visit here: http://xdaforums.com/z3-compact/development/unlocked-update-conceptmm-root-recovery-t3291722 and follow the instructions. It will give you the concept version of Marshmallow, root and DRM functions!

The thing is you have lost your DRM functions by unlocking your bootloader. So flashing any other Stock ROM will not bring it back as it has something to do with the system of the phone. If you are OK with a Stock ROM without DRM functions, there are plenty Stock Pre-Rooted Firmwares on xda. You can download one, do a factory reset, and wipe dalvik/cache, then flash the Stock ROM.zip through your recovery. Have the best of luck! :)

EDIT: I don't know about the TA backup as I have never used it :/
[Xperia Z3 Compact Q&A, Help & Troubleshooting] artie_ficial:
Solution

Thanks for your effort! But you misunderstood me, I have a working backup of my "former" TA partition/DRM keys. All I was wondering about was WHEN exactly I should perform the restore process. But I found out anyway. For whoever should have the same question:

- revert back to the firmware you used when performing the ta/drm backup

- if necessary: root (as the ta-backup tool needs root permissions)

- restore drm key backup with the ta-backup tool

- do whatever ... I installed a pre-rooted stock based fw and it works with DRM keys and root/recovery
[Xperia Z3 Compact Q&A, Help & Troubleshooting] karimsarsar:
HI :)

Restoring TA backup Will NOT relock your Bootloader but it will simply restore the DRM keys that you backed up while unlocking Bootloader

So you will restore the DRM keys

flash stock Firmware

flash TWRP via fastboot and the you will be able to root with chainfire auto root flashable zip

or just download a prerooted stock firmware and flash it :)
[ZenFone 2 Q&A, Help & Troubleshooting] mastermarkofroms:
So my zenfone 2 seems to have an issue if I use adb I can access recovery but if I press the volume up and the power button it just gets stuck on asus bootlogo yet if I turn it on normally it boots up into android I am not sure whats going on is there a way to get the fastboot bootloader back or?

Edit: Problem solved its self bootloader is now working o.O out of no where rebooting from recovery into bootloader worked
[Upgrading, Modifying and Unlocking] superuser#1508:
Moderation please remove this thread as it was started by mistake.
[Sony Xperia M4 Aqua] Ferramont103:
Hi :D

I followed the guide here: http://goo.gl/b7NTn9

My problem is, I keep getting the error FAILED (remote: Command not allowed) as soon as I press "unlock" after I pasted the unlock code.

Can anyone perhaps help , please? I'm at my wits end on this one.

Log Dump:

24/052/2016 13:52:13 - INFO - Please connect your device into flashmode.
24/052/2016 13:52:21 - INFO - Device connected in flash mode
24/052/2016 13:52:21 - INFO - Opening device for R/W
24/052/2016 13:52:21 - INFO - Reading device information
24/052/2016 13:52:21 - INFO - Phone ready for flashmode operations.
24/052/2016 13:52:21 - INFO - Opening TA partition 2
24/052/2016 13:52:21 - INFO - Current device : E2303 - [COLOR="red"]DEVICE_CODE_HERE[/COLOR] - 1294-6067_R9A - 1291-5963_26.1.A.2.167 - GENERIC_26.1.A.2.167
24/052/2016 13:52:21 - INFO - Closing TA partition
24/052/2016 13:52:21 - INFO - Processing loader.sin
24/052/2016 13:52:21 - INFO - Checking header
24/052/2016 13:52:21 - INFO - Flashing data
24/052/2016 13:52:22 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_36 / Bootloader status : ROOTABLE
24/052/2016 13:52:22 - INFO - Max packet size set to 512K
24/052/2016 13:52:22 - INFO - Opening TA partition 2
24/052/2016 13:52:22 - INFO - Start Reading unit 000008B2
24/052/2016 13:52:22 - INFO - Reading TA finished.
24/052/2016 13:52:22 - INFO - Closing TA partition
24/052/2016 13:52:22 - INFO - Ending flash session
24/052/2016 13:52:22 - INFO - Now unplug your device and restart it into fastbootmode
24/052/2016 13:52:22 - INFO - Device connected in flash mode
24/052/2016 13:52:23 - INFO - Device disconnected
24/054/2016 13:54:13 - INFO - Device connected in fastboot mode
24/054/2016 13:54:32 - INFO - Unlocking phone using key [COLOR="red"]UNLOCK_KEY_HERE[/COLOR]
24/054/2016 13:54:32 - INFO - ...
24/054/2016 13:54:32 - INFO - FAILED (remote: Command not allowed)
24/054/2016 13:54:32 - INFO - finished. total time: 0.005s

Thank you for reading!
[Sony Xperia M4 Aqua] ardentis:
Have you checked to see if unlock is allowed? And if it says it can be unlocked, did you put the right imei for unlock. I found that the unlock code for the Xperia M worked fine
[Sony Xperia M4 Aqua] swizzyneck:
hy :)

exactly the same problem is occuring to me !

i tried to unlock the bootloader with different options for example the new and the old version of flashtool but it´s not working. :(

the rooting status is: Bootloader unlock allowed: Yes

i also noticed that when you put in your imei code on the sony developer page you have to put in 15 digits to get the ul-code but the flashtool just shows 14 digits of the imei code when you have to enter it.

i have the e2303 8Gb

build number 26.1.A.2.167

Android 5.0

Thank you !
[Sony Xperia M4 Aqua] Ferramont103:
Thanks for replying! Yeah, I did all that, I tried the M and M2 unlock code, unlock is allowed, it just isn't doing anything though :(
[Sony Xperia M4 Aqua] ardentis:
Make sure you use the imei from the phone and not the unlock tool. It's purposely wrong to protect your imei if you share a picture of the unlock tool. Just keep trying
[Sony Xperia M4 Aqua] TomTOm_83:
I have also the Problem, in the settings is Allowed, but the Software can't unlock the

the Bootloader well (remote: Command not allowed),

I have with Blu install't .1.128 but no way.

Do have tips for me?

i have read the Driver can under windows 8.1 a problem, but he find my Smartphone,

also must it work or?!

Greetz
[Sony Xperia M4 Aqua] fault-tolerant:
Unlocking the bootloader in M4 Aqua

Was stuck with the same problem. M4, says its bootloader can be unlocked.

13/034/2016 22:34:37 - INFO - Unlocking phone using key XXXXXXXXXXXXXXX

13/034/2016 22:34:37 - INFO - ...

13/034/2016 22:34:37 - INFO - FAILED (remote: Command not allowed)

13/034/2016 22:34:37 - INFO - finished. total time: 0.005s

The solution is to enable OEM unlocking in the developer options. Also, in some cases, it helps to perform a factory reset before unlocking.

Good luck!
[Sony Xperia M4 Aqua] ethoms:
I had the same problem with " FAILED (remote: Command not allowed)", even though my device was stated as unlockable. It turned out all I needed to do was turn on "Allow OEM unlocking" in Developer options, on the phone. Then after power off again, fastboot eom unlock worked.
[Sony Xperia M4 Aqua] htcity:
Thanks bro. It worked
[Sony Xperia M4 Aqua] beniusc:
Hi

Same problem, and thanks for oem unlocking in developers menu option.

The unlock option works fine now
[Sony Xperia M4 Aqua] mamun88:
i have same problem, but my device bootlop so i can't allow OEM unlocking. someone help me please? tanks
[Sony Xperia M4 Aqua] Sexy scientist:
This thread is dead, but I'll post anyways. I am using xperia xz1c. Bootloader unlock is allowed. OEM unlocking is allowed. Device is being detected on fastboot devices command. On fastboot, the output I am getting is "FAILED (remote: command did not succeed)". I have tried latest platform tools 28.0.1, older platform tools 25.0.5 and 26.0.0 with no success. Thanks for reading.
[P3300, MDA Compact III  upgrading etc.] trifo13:
cmon guys whats wrong with you...

there are few here who knows how to unlock it...

but they are keepin it in secret and they are asking for money...

thats stupid...

yea i know that iam a newbie and i havent done anything for you but im sure ur not making money with that...

so please...

share the sim unlocking solution for Artemis...

PLEASE!!!
[P3300, MDA Compact III  upgrading etc.] TryOG:
Heh, just drop it...

I'm here since the HTC Blue Angel came out freshly :)

And what I can tell you about the changes is that this website lost its meaning.

I miss developers like buzz_lightyear from buzzdev.

Heh, but it could be just me.