I try several methods to activate init.d support on leaked 4.4.2 with stock kernel ,but no one was successful.
Can someone help me ?
you placed the service in the init.rc of the kernel right?
No,when I try this and flash kernel , phone's goes to bootlop.
I try with several scripts , but they don't work.
mom4ence said:
No,when I try this and flash kernel , phone's goes to bootlop.
I try with several scripts , but they don't work.
Click to expand...
Click to collapse
Do it manually. The scripts are probably getting the repacking incorrect.
Related
Hai ,
I downloaded my phones kernel source and compiled with some additional configuraton..
Now I got these files .vmlinuz,image,zimage,and a tar'ed archive of zimage with name kernel_......_.tar
how can I make odin flashable (or any how flashable) rom file from this?
I tried to make boot.img with mkbootimg and initrd extracted from original stock rom
Flashing was succes according to odin But It doesnt boot.
any one please help me
I also like to know is there any way turn off splash screen and see the debug msgs from kernel during boot?
Any one please help
My phone is galaxy young GT-S5360
Update:
I figured out that problem is not with the additional configuration options I given during kernel compilation.
Problem is with the tools (or incorrect usage of tools) .
I tried making boot.img with original kernel and initramfs and that also not worked (flashing was successful.but
Booting failed).
I don't have much experience in android.i only know some linux
Any one please help me
Please please please.......
Update:
Finally I think I found how to make boot.img from kernel(zImage).The problem was with the "--base-address" option in the mkbootimg toool. I found my device's base address from kernel configuration file (.config).
now , boot.img produced from the kernel which was extracted from stock rom works well.
but boot.img produced from my custom kernel boots,but nothing displys in the screen.
I dont know how to debug it . I cant even see the debug messages from the kernel
Any one knows any clues,hints or any thing regarding this please please help me
i dont know why any no one replay to my post.
I dont have privilege to post this question in developers thread.thats why i am asking it here
Is it a wrong way? I dont know.
Click to expand...
Click to collapse
Thank you sir to be the first succefully create custom kernel...
Far before anyone can create it...
I'm always waiting ur great work again into sgy device...
hi guy! i'm a new user and i have a problem with my galaxy y: my computer does not read my device in download mode because it doesn't install a particular driver (i've already tried to fix this error without any result but this is not my problem), i'm testing the AOSP custom rom and until now i've tried it with jarvis kernel and percy's kernel. actually i'm using the percy one but i want to return to jarvis. how can i install it without reinstall stock rom (due to my computer's problem)? thanks in advance for any help!
Blade.94 said:
hi guy! i'm a new user and i have a problem with my galaxy y: my computer does not read my device in download mode because it doesn't install a particular driver (i've already tried to fix this error without any result but this is not my problem), i'm testing the AOSP custom rom and until now i've tried it with jarvis kernel and percy's kernel. actually i'm using the percy one but i want to return to jarvis. how can i install it without reinstall stock rom (due to my computer's problem)? thanks in advance for any help!
Click to expand...
Click to collapse
read the instructions on the op of the kernel thread - you should already be on ext4 so just do following
Jarvis-CM:
1. Download Kernel
2. Reboot Into Recovery (if on percy kernel it will be cwm)
3. Mount System
4. Install From sdcard Select Jarvis-CM Kernel
6. Reboot
marcussmith2626 said:
read the instructions on the op of the kernel thread - you should already be on ext4 so just do following
Jarvis-CM:
1. Download Kernel
2. Reboot Into Recovery (if on percy kernel it will be cwm)
3. Mount System
4. Install From sdcard Select Jarvis-CM Kernel
6. Reboot
Click to expand...
Click to collapse
i have another question about this: ì've also installed ad-blocking and amarullz script. after flashing jarvis kernel should i reinstall all of these or will they remain on the device?? i'm sorry if my english is not perfect...
Blade.94 said:
i have another question about this: ì've also installed ad-blocking and amarullz script. after flashing jarvis kernel should i reinstall all of these or will they remain on the device?? i'm sorry if my english is not perfect...
Click to expand...
Click to collapse
if they are init.d scripts and the kernel supports them then they should remain
marcussmith2626 said:
if they are init.d scripts and the kernel supports them then they should remain
Click to expand...
Click to collapse
ok thanks a lot for your help! i gave you 2 thanks for each reply! i'll try it!
Hello
well i also faced this issue,if ur not aware of it then let me explain a liitle.. if you have upgraded to the latest version via OTA then there are some patch files in the system which do this trick.. so in order to get permanent recovery if u flashed it via ur phone with apps like flashify or recovery tools then you need to go to
System and there you will see a file with name Recoveryfromboot.p just delete that file and flash chinese cwm and ur done :]
btw i'll try to build the english cwm as soon as i get some free time.. thanx to burakgon for releasing the kernel sources..
Thanks simmer14, works perfectly after removing that file from system. So that confirms it's not bootloader lock issue. No idea why custom kernels and twrp not working then?
1manshow said:
Thanks simmer14, works perfectly after removing that file from system. So that confirms it's not bootloader lock issue. No idea why custom kernels and twrp not working then?
Click to expand...
Click to collapse
i will build the cwm for our phone but i'm not getting any time to sit in front of my pc :'(
edit :
custum kernels are not working ? did you tried to compile one from the sources ? or the sources are not complete ?
I didn't tried to compile anything, but some guys did here -
http://forum.xda-developers.com/showthread.php?t=2712586
If you want, you can take a look there and contribute in your own way to resolve the issue. Thanks for your efforts so far though.
Hi,
I have Samsung Galaxy Grand Prime SM-G531F, rooted with TWRP and I tried to set SElinux to permissive to be able to install Viper4Android driver, I tried changing SElinux with command setenforce 0, tried with SElinuxModeChanger apk, some build.prop editing and with .sh scripts, but nothing worked. Then I tried compiling permissive kernel, used ramdisk from stock kernel, created boot.img, flashed through Odin and rebooted. When the device boots on top of the screen it writes in red KERNEL IS NOT SEANDROID ENFORCING and won't boot, it's stuck there. If I flash stock kernel it will continue like nothing happened. Is there any other way to set SElinux to permissive other than this? If not, how to remove KERNEL IS NOT SEANDROID ENFORCING warning? I've read somewhere that I need to set bootloader to permissive, but I don't know how. Any help would be appreciated. Thank you in advance.
(I apologize for any mistakes, english is not my native language.)
Are you specifying a DTS file when you are rebuilding it? I can't help you much as I don't have my Linux Environment anymore I will try to help you once I reinstall it. I also had a lot of problems trying to build a kernel for this phone.
I end my school for this year in 2 days so I will be rebuilding the Linux the same day. May I know why you want a permissive kernel anyway?
fabiossilva21 said:
Are you specifying a DTS file when you are rebuilding it? I can't help you much as I don't have my Linux Environment anymore I will try to help you once I reinstall it. I also had a lot of problems trying to build a kernel for this phone.
I end my school for this year in 2 days so I will be rebuilding the Linux the same day. May I know why you want a permissive kernel anyway?
Click to expand...
Click to collapse
Sorry for late reply. What DTS files? I haven't seen any when unpacking stock kernel. I followed instructions that came with kernel I downloaded from opensource.samsung.com. I needed to tweak two things in Makefile: ARCH=arm64 and CROSS_COMPILE path. Then I changed this flag EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=true to false in SElinux Makefile. This is flag that forces enforcing SElinux. Then I typed: make pxa1908_grandprimevelte_eur_defconfig and it created .config. After that I typed make and waited until it compiled. When I unpacked stock kernel I had these files: rmdisk(folder), kernel(file), pagesize.txt, ram_disk(file) and ram_disk.gz. All I did was deleted kernel file, replaced with compiled one, repacked and flashed with Odin. KERNEL IS NOT SEANDROID ENFORCING. If I reflash stock kernel it continues booting normally. I want permissive kernel mainly because I want to use androidexpert35's XTREMEMusic mod.
su_root_ said:
Sorry for late reply. What DTS files? I haven't seen any when unpacking stock kernel. I followed instructions that came with kernel I downloaded from opensource.samsung.com. I needed to tweak two things in Makefile: ARCH=arm64 and CROSS_COMPILE path. Then I changed this flag EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=true to false in SElinux Makefile. This is flag that forces enforcing SElinux. Then I typed: make pxa1908_grandprimevelte_eur_defconfig and it created .config. After that I typed make and waited until it compiled. When I unpacked stock kernel I had these files: rmdisk(folder), kernel(file), pagesize.txt, ram_disk(file) and ram_disk.gz. All I did was deleted kernel file, replaced with compiled one, repacked and flashed with Odin. KERNEL IS NOT SEANDROID ENFORCING. If I reflash stock kernel it continues booting normally. I want permissive kernel mainly because I want to use androidexpert35's XTREMEMusic mod.
Click to expand...
Click to collapse
Ok, so as I don't build a kernel for this phone for a while I will start setting my Linux up, build one and then put some instructions how to build one for this variant! I did have some problems so that's why I'm going to make a guide.
fabiossilva21 said:
Ok, so as I don't build a kernel for this phone for a while I will start setting my Linux up, build one and then put some instructions how to build one for this variant! I did have some problems so that's why I'm going to make a guide.
Click to expand...
Click to collapse
Thank you.
su_root_ said:
Thank you.
Click to expand...
Click to collapse
So I just built and flashed a kernel I made with the same modification you made to the selinux make file and it is still enforcing. I will try to see if I can make it permissive once I finish this year of school which is tomorrow. I just posted a guide on how to build a kernel for this phone good luck and tell me if you got it running!
EDIT: Go to security\selinux\Kconfig and have a look at the bools, before making the kernel do a "make menuconfig" and go through the options of security and try disabling them there! I'm going to sleep now, tomorrow I will recompile a kernel with those changes and checking if it works. If it does I will upload it here!
EDIT2: It doesnt work sorry! Everytime I build a kernel not SEANDROID Enforcing it will simply reboot into recovery!
su_root_ said:
Hi,
I have Samsung Galaxy Grand Prime SM-G531F, rooted with TWRP and I tried to set SElinux to permissive to be able to install Viper4Android driver, I tried changing SElinux with command setenforce 0, tried with SElinuxModeChanger apk, some build.prop editing and with .sh scripts, but nothing worked. Then I tried compiling permissive kernel, used ramdisk from stock kernel, created boot.img, flashed through Odin and rebooted. When the device boots on top of the screen it writes in red KERNEL IS NOT SEANDROID ENFORCING and won't boot, it's stuck there. If I flash stock kernel it will continue like nothing happened. Is there any other way to set SElinux to permissive other than this? If not, how to remove KERNEL IS NOT SEANDROID ENFORCING warning? I've read somewhere that I need to set bootloader to permissive, but I don't know how. Any help would be appreciated. Thank you in advance.
(I apologize for any mistakes, english is not my native language.)
Click to expand...
Click to collapse
Can i please have your permissive boot.img ? i will try to make Flashable .zip, then give it back to you packed in Kernel.zip then flash it through TWRP Recovery and it should fix it. Don't flash roms through odin. or kernels, if you do your phone will not boot up
NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootloopedcredits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
in cmd window :fastboot flash boot new_kernel.img
IMP:steps 1 & 2 are can also be used when u have met with an unexpected bootloop/restart problem at any time( if u don't want to flash the complete stock ftf,this boot image will help u in letting ur device come out of bootloop.
3.proceeding to our main thread....now boot into recovery & flash "magisk.zip"
4.wipe cache & dalvik.and reboot.
PROPERTIES OF THE KERNEL (new_kernel.img:---
Build 32.4.A.1.54
1. Sony RIC- disabled.
2. DM-Verity- disabled.
3. TWRP- disabled.
4. DRM Fix- enabled.
5. Superuser / root- Not present. ( flash magisk its better)
6. Busybox- Not present
7.many more tweaks to reduce heat & increase battery backup
LINK TO THE CONTENT
https://drive.google.com/drive/folders/1ic9zsMi576s1P9H6s1z4_g0ofSJJktIs?usp=sharing
I just want stock rooted rom with magiks
doctorsworld99 said:
NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootloopedcredits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
Click to expand...
Click to collapse
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp
Sumantomar1709 said:
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp
Click to expand...
Click to collapse
u can try flashing magisk over stock.but whenever i did that my device used to go into bootloop.thats why i've to experiment with different twrps,kernels to detect the culprit.
finally i got this awesome kernel which helped me to come out of bootloops everytime.so i will suggest to use this [near to stock ] kernel .
but u can try flashing magisk over stock.....if anything goes wrong ,,,just flash the new_kernel,,and ua fine to go with magisk.
Thnx. I will try & let u know.
thank u sirThis kernel help me from bootloop .how did u make this kernel
Champsingh909 said:
thank u sirThis kernel help me from bootloop .how did u make this kernel
Click to expand...
Click to collapse
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime
This kernel really working in bootloop.thnx
doctorsworld99 said:
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime
Click to expand...
Click to collapse
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot
Champsingh909 said:
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot
Click to expand...
Click to collapse
creating a separate thread isn't a good idea ,i'll update the details of the kernel in this thread itself,plz give me some time.
Kernel properties added.
Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.
LoaderFabi said:
Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.
Click to expand...
Click to collapse
i got frequent bootloops on installing it over stock kernel and also over m-rom .i think the kernel was the culprit.
Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?
chrnodroid said:
Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?
Click to expand...
Click to collapse
Hopefully yes,flash it as instructed.best of luck:good:
Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.
MrHands0m3 said:
Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.
Click to expand...
Click to collapse
confirmed!! this kernel is the ****!.. try it... (don't blame me if you brick your device)
The link to download the kernel won't work anymore, is there a mirror?