Linux kernel error “No working init found"
0
Currently I am doing Android update for our custom device. Updating from known working Android 4.3 with u-boot 2015.04 and Linux kernel 3.2 to Android 7.1.2 with u-boot 2015.07 Linux kernel 4.5. The u-boot 2015.07 and Linux kernel 4.5 are known working on our custom device. While integrating the u-boot and Linux kernel into Android 7.1.2, the Linux kernel failed to boot.
Here is the log:
[ 3.667772] sr_init: No PMIC hook to init smartreflex
[ 3.673780] sr_init: platform driver register failed for SR
[ 3.716721] vdd5_reg: disabling
[ 3.720220] regulator-wl18xx-wl-en: disabling
[ 3.724826] regulator-wl18xx-bt-en: disabling
[ 3.959011] usb 2-1: new high-speed USB device number 2 using musb-hdrc
[ 4.099854] usb 2-1: New USB device found, idVendor=0424, idProduct=2513
[ 4.106939] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.120895] hub 2-1:1.0: USB hub found
[ 4.126728] hub 2-1:1.0: 3 ports detected
[ 4.311994] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.320977] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 4.331395] devtmpfs: error mounting -2
[ 4.336827] Freeing unused kernel memory: 452K (c09b5000 - c0a26000)
[ 4.348323] Starting init: /etc/init exists but couldn't execute it (error -13)
[ 4.377888] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 4.391965] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 77.048831] random: nonblocking pool is initialized
The file system for root (label as system) is ext4 format. When the kernel is built, there are /bin/sh, /etc/init/ in it, but no /sbin/ folder and /bin/init /etc/init files. I tried to change the permission to anyone can execute the files, but it doesn't work. Do anybody knows what is wrong with that?
Edit: I think the major problem is the file system is not mounted.
[ 4.295699] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.304608] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 4.314750] devtmpfs: error mounting -2
Do anyone know what causes this error?
filesystems kernel linux-kernel android kernel-panic
edited 3 hours ago
Rui F Ribeiro
41.5k1483140
asked Aug 22 '17 at 0:09
Jason LiuJason Liu
46
|
show 3 more comments
0
Currently I am doing Android update for our custom device. Updating from known working Android 4.3 with u-boot 2015.04 and Linux kernel 3.2 to Android 7.1.2 with u-boot 2015.07 Linux kernel 4.5. The u-boot 2015.07 and Linux kernel 4.5 are known working on our custom device. While integrating the u-boot and Linux kernel into Android 7.1.2, the Linux kernel failed to boot.
Here is the log:
[ 3.667772] sr_init: No PMIC hook to init smartreflex
[ 3.673780] sr_init: platform driver register failed for SR
[ 3.716721] vdd5_reg: disabling
[ 3.720220] regulator-wl18xx-wl-en: disabling
[ 3.724826] regulator-wl18xx-bt-en: disabling
[ 3.959011] usb 2-1: new high-speed USB device number 2 using musb-hdrc
[ 4.099854] usb 2-1: New USB device found, idVendor=0424, idProduct=2513
[ 4.106939] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.120895] hub 2-1:1.0: USB hub found
[ 4.126728] hub 2-1:1.0: 3 ports detected
[ 4.311994] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.320977] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 4.331395] devtmpfs: error mounting -2
[ 4.336827] Freeing unused kernel memory: 452K (c09b5000 - c0a26000)
[ 4.348323] Starting init: /etc/init exists but couldn't execute it (error -13)
[ 4.377888] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 4.391965] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 77.048831] random: nonblocking pool is initialized
The file system for root (label as system) is ext4 format. When the kernel is built, there are /bin/sh, /etc/init/ in it, but no /sbin/ folder and /bin/init /etc/init files. I tried to change the permission to anyone can execute the files, but it doesn't work. Do anybody knows what is wrong with that?
Edit: I think the major problem is the file system is not mounted.
[ 4.295699] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.304608] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 4.314750] devtmpfs: error mounting -2
Do anyone know what causes this error?
filesystems kernel linux-kernel android kernel-panic
edited 3 hours ago
Rui F Ribeiro
41.5k1483140
asked Aug 22 '17 at 0:09
Jason LiuJason Liu
46
Often iOT kernels are heavily hacked by the original vendor. You might not be able to upgrade to any random version at all, and it is a fairly common occurrence to be tied forever to the particular version it came with, or having random updates hacks to that version by the vendor. If you are the vendor, than I would get worried.
– Rui F Ribeiro
Aug 22 '17 at 0:22
The old kernel is 3.2, it is not even compiled on the Android 7.1.2, newer compiler throws whole bunch errors. Fixing them is tough. Generally speaking, the Android runs on top of the Linux kernel and they are independent. I feel there are some sort of configuration problems only, because the Linux kernel 4.5 is proven working on Yocto project. Last, you can assume I am the vendor.
– Jason Liu
Aug 22 '17 at 0:40
1
Your sentence "there are /bin/sh, /etc/init/ in it, but no /sbin/ folder and /bin/init /etc/init files" is a bit ambiguous. Do you mean that/etc/initexists but is not a file? Could you provide us with the result ofls -ld /etc/init?
– xhienne
Aug 22 '17 at 0:44
We do not know what you are doing, how you are compiling it, or your specific set of patches. (...) You might also not be using the right header files (i.e) using the headers of the wrong kernel version. There are too many unknowns.
– Rui F Ribeiro
Aug 22 '17 at 0:49
ls -ld /etc/initshowsdrwxr-xr-x 2 root root 4096 Aug 21 13:50 /media/yangjiel/system/etc/init, it is a folder not an executable file. There is 29 rc files in it. I tried using the upstream kernel provide by Android (branch name call android-4.4-n-release, Linux kernel v4.4), but I got the same error. I am using the old/device/vendorfolder for the new Android system which probably where the problem is.
– Jason Liu
Aug 22 '17 at 16:32
|
show 3 more comments
0
0
0
Currently I am doing Android update for our custom device. Updating from known working Android 4.3 with u-boot 2015.04 and Linux kernel 3.2 to Android 7.1.2 with u-boot 2015.07 Linux kernel 4.5. The u-boot 2015.07 and Linux kernel 4.5 are known working on our custom device. While integrating the u-boot and Linux kernel into Android 7.1.2, the Linux kernel failed to boot.
Here is the log:
[ 3.667772] sr_init: No PMIC hook to init smartreflex
[ 3.673780] sr_init: platform driver register failed for SR
[ 3.716721] vdd5_reg: disabling
[ 3.720220] regulator-wl18xx-wl-en: disabling
[ 3.724826] regulator-wl18xx-bt-en: disabling
[ 3.959011] usb 2-1: new high-speed USB device number 2 using musb-hdrc
[ 4.099854] usb 2-1: New USB device found, idVendor=0424, idProduct=2513
[ 4.106939] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.120895] hub 2-1:1.0: USB hub found
[ 4.126728] hub 2-1:1.0: 3 ports detected
[ 4.311994] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.320977] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 4.331395] devtmpfs: error mounting -2
[ 4.336827] Freeing unused kernel memory: 452K (c09b5000 - c0a26000)
[ 4.348323] Starting init: /etc/init exists but couldn't execute it (error -13)
[ 4.377888] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 4.391965] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 77.048831] random: nonblocking pool is initialized
The file system for root (label as system) is ext4 format. When the kernel is built, there are /bin/sh, /etc/init/ in it, but no /sbin/ folder and /bin/init /etc/init files. I tried to change the permission to anyone can execute the files, but it doesn't work. Do anybody knows what is wrong with that?
Edit: I think the major problem is the file system is not mounted.
[ 4.295699] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.304608] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 4.314750] devtmpfs: error mounting -2
Do anyone know what causes this error?
filesystems kernel linux-kernel android kernel-panic
edited 3 hours ago
Rui F Ribeiro
41.5k1483140
asked Aug 22 '17 at 0:09
Jason LiuJason Liu
46
Currently I am doing Android update for our custom device. Updating from known working Android 4.3 with u-boot 2015.04 and Linux kernel 3.2 to Android 7.1.2 with u-boot 2015.07 Linux kernel 4.5. The u-boot 2015.07 and Linux kernel 4.5 are known working on our custom device. While integrating the u-boot and Linux kernel into Android 7.1.2, the Linux kernel failed to boot.
Here is the log:
[ 3.667772] sr_init: No PMIC hook to init smartreflex
[ 3.673780] sr_init: platform driver register failed for SR
[ 3.716721] vdd5_reg: disabling
[ 3.720220] regulator-wl18xx-wl-en: disabling
[ 3.724826] regulator-wl18xx-bt-en: disabling
[ 3.959011] usb 2-1: new high-speed USB device number 2 using musb-hdrc
[ 4.099854] usb 2-1: New USB device found, idVendor=0424, idProduct=2513
[ 4.106939] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.120895] hub 2-1:1.0: USB hub found
[ 4.126728] hub 2-1:1.0: 3 ports detected
[ 4.311994] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.320977] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 4.331395] devtmpfs: error mounting -2
[ 4.336827] Freeing unused kernel memory: 452K (c09b5000 - c0a26000)
[ 4.348323] Starting init: /etc/init exists but couldn't execute it (error -13)
[ 4.377888] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 4.391965] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 77.048831] random: nonblocking pool is initialized
The file system for root (label as system) is ext4 format. When the kernel is built, there are /bin/sh, /etc/init/ in it, but no /sbin/ folder and /bin/init /etc/init files. I tried to change the permission to anyone can execute the files, but it doesn't work. Do anybody knows what is wrong with that?
Edit: I think the major problem is the file system is not mounted.
[ 4.295699] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.304608] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 4.314750] devtmpfs: error mounting -2
Do anyone know what causes this error?
filesystems kernel linux-kernel android kernel-panic
filesystems kernel linux-kernel android kernel-panic
edited 3 hours ago
Rui F Ribeiro
41.5k1483140
asked Aug 22 '17 at 0:09
Jason LiuJason Liu
46
edited 3 hours ago
Rui F Ribeiro
41.5k1483140
asked Aug 22 '17 at 0:09
Jason LiuJason Liu
46
edited 3 hours ago
Rui F Ribeiro
41.5k1483140
edited 3 hours ago
Rui F Ribeiro
41.5k1483140
edited 3 hours ago
Rui F Ribeiro
41.5k1483140
41.5k1483140
asked Aug 22 '17 at 0:09
Jason LiuJason Liu
46
asked Aug 22 '17 at 0:09
Jason LiuJason Liu
46
asked Aug 22 '17 at 0:09
Jason LiuJason Liu
46
46
Often iOT kernels are heavily hacked by the original vendor. You might not be able to upgrade to any random version at all, and it is a fairly common occurrence to be tied forever to the particular version it came with, or having random updates hacks to that version by the vendor. If you are the vendor, than I would get worried.
– Rui F Ribeiro
Aug 22 '17 at 0:22
The old kernel is 3.2, it is not even compiled on the Android 7.1.2, newer compiler throws whole bunch errors. Fixing them is tough. Generally speaking, the Android runs on top of the Linux kernel and they are independent. I feel there are some sort of configuration problems only, because the Linux kernel 4.5 is proven working on Yocto project. Last, you can assume I am the vendor.
– Jason Liu
Aug 22 '17 at 0:40
1
Your sentence "there are /bin/sh, /etc/init/ in it, but no /sbin/ folder and /bin/init /etc/init files" is a bit ambiguous. Do you mean that/etc/initexists but is not a file? Could you provide us with the result ofls -ld /etc/init?
– xhienne
Aug 22 '17 at 0:44
We do not know what you are doing, how you are compiling it, or your specific set of patches. (...) You might also not be using the right header files (i.e) using the headers of the wrong kernel version. There are too many unknowns.
– Rui F Ribeiro
Aug 22 '17 at 0:49
ls -ld /etc/initshowsdrwxr-xr-x 2 root root 4096 Aug 21 13:50 /media/yangjiel/system/etc/init, it is a folder not an executable file. There is 29 rc files in it. I tried using the upstream kernel provide by Android (branch name call android-4.4-n-release, Linux kernel v4.4), but I got the same error. I am using the old/device/vendorfolder for the new Android system which probably where the problem is.
– Jason Liu
Aug 22 '17 at 16:32
|
show 3 more comments
Often iOT kernels are heavily hacked by the original vendor. You might not be able to upgrade to any random version at all, and it is a fairly common occurrence to be tied forever to the particular version it came with, or having random updates hacks to that version by the vendor. If you are the vendor, than I would get worried.
– Rui F Ribeiro
Aug 22 '17 at 0:22
The old kernel is 3.2, it is not even compiled on the Android 7.1.2, newer compiler throws whole bunch errors. Fixing them is tough. Generally speaking, the Android runs on top of the Linux kernel and they are independent. I feel there are some sort of configuration problems only, because the Linux kernel 4.5 is proven working on Yocto project. Last, you can assume I am the vendor.
– Jason Liu
Aug 22 '17 at 0:40
1
Your sentence "there are /bin/sh, /etc/init/ in it, but no /sbin/ folder and /bin/init /etc/init files" is a bit ambiguous. Do you mean that/etc/initexists but is not a file? Could you provide us with the result ofls -ld /etc/init?
– xhienne
Aug 22 '17 at 0:44
We do not know what you are doing, how you are compiling it, or your specific set of patches. (...) You might also not be using the right header files (i.e) using the headers of the wrong kernel version. There are too many unknowns.
– Rui F Ribeiro
Aug 22 '17 at 0:49
ls -ld /etc/initshowsdrwxr-xr-x 2 root root 4096 Aug 21 13:50 /media/yangjiel/system/etc/init, it is a folder not an executable file. There is 29 rc files in it. I tried using the upstream kernel provide by Android (branch name call android-4.4-n-release, Linux kernel v4.4), but I got the same error. I am using the old/device/vendorfolder for the new Android system which probably where the problem is.
– Jason Liu
Aug 22 '17 at 16:32
Often iOT kernels are heavily hacked by the original vendor. You might not be able to upgrade to any random version at all, and it is a fairly common occurrence to be tied forever to the particular version it came with, or having random updates hacks to that version by the vendor. If you are the vendor, than I would get worried.
– Rui F Ribeiro
Aug 22 '17 at 0:22
Often iOT kernels are heavily hacked by the original vendor. You might not be able to upgrade to any random version at all, and it is a fairly common occurrence to be tied forever to the particular version it came with, or having random updates hacks to that version by the vendor. If you are the vendor, than I would get worried.
– Rui F Ribeiro
Aug 22 '17 at 0:22
The old kernel is 3.2, it is not even compiled on the Android 7.1.2, newer compiler throws whole bunch errors. Fixing them is tough. Generally speaking, the Android runs on top of the Linux kernel and they are independent. I feel there are some sort of configuration problems only, because the Linux kernel 4.5 is proven working on Yocto project. Last, you can assume I am the vendor.
– Jason Liu
Aug 22 '17 at 0:40
The old kernel is 3.2, it is not even compiled on the Android 7.1.2, newer compiler throws whole bunch errors. Fixing them is tough. Generally speaking, the Android runs on top of the Linux kernel and they are independent. I feel there are some sort of configuration problems only, because the Linux kernel 4.5 is proven working on Yocto project. Last, you can assume I am the vendor.
– Jason Liu
Aug 22 '17 at 0:40
1
1
Your sentence "there are /bin/sh, /etc/init/ in it, but no /sbin/ folder and /bin/init /etc/init files" is a bit ambiguous. Do you mean that
/etc/init exists but is not a file? Could you provide us with the result of ls -ld /etc/init?– xhienne
Aug 22 '17 at 0:44
Your sentence "there are /bin/sh, /etc/init/ in it, but no /sbin/ folder and /bin/init /etc/init files" is a bit ambiguous. Do you mean that
/etc/init exists but is not a file? Could you provide us with the result of ls -ld /etc/init?– xhienne
Aug 22 '17 at 0:44
We do not know what you are doing, how you are compiling it, or your specific set of patches. (...) You might also not be using the right header files (i.e) using the headers of the wrong kernel version. There are too many unknowns.
– Rui F Ribeiro
Aug 22 '17 at 0:49
We do not know what you are doing, how you are compiling it, or your specific set of patches. (...) You might also not be using the right header files (i.e) using the headers of the wrong kernel version. There are too many unknowns.
– Rui F Ribeiro
Aug 22 '17 at 0:49
ls -ld /etc/init shows drwxr-xr-x 2 root root 4096 Aug 21 13:50 /media/yangjiel/system/etc/init, it is a folder not an executable file. There is 29 rc files in it. I tried using the upstream kernel provide by Android (branch name call android-4.4-n-release, Linux kernel v4.4), but I got the same error. I am using the old /device/vendor folder for the new Android system which probably where the problem is.– Jason Liu
Aug 22 '17 at 16:32
ls -ld /etc/init shows drwxr-xr-x 2 root root 4096 Aug 21 13:50 /media/yangjiel/system/etc/init, it is a folder not an executable file. There is 29 rc files in it. I tried using the upstream kernel provide by Android (branch name call android-4.4-n-release, Linux kernel v4.4), but I got the same error. I am using the old /device/vendor folder for the new Android system which probably where the problem is.– Jason Liu
Aug 22 '17 at 16:32
|
show 3 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f387537%2flinux-kernel-error-no-working-init-found%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f387537%2flinux-kernel-error-no-working-init-found%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Often iOT kernels are heavily hacked by the original vendor. You might not be able to upgrade to any random version at all, and it is a fairly common occurrence to be tied forever to the particular version it came with, or having random updates hacks to that version by the vendor. If you are the vendor, than I would get worried.
– Rui F Ribeiro
Aug 22 '17 at 0:22
The old kernel is 3.2, it is not even compiled on the Android 7.1.2, newer compiler throws whole bunch errors. Fixing them is tough. Generally speaking, the Android runs on top of the Linux kernel and they are independent. I feel there are some sort of configuration problems only, because the Linux kernel 4.5 is proven working on Yocto project. Last, you can assume I am the vendor.
– Jason Liu
Aug 22 '17 at 0:40
1
Your sentence "there are /bin/sh, /etc/init/ in it, but no /sbin/ folder and /bin/init /etc/init files" is a bit ambiguous. Do you mean that
/etc/initexists but is not a file? Could you provide us with the result ofls -ld /etc/init?– xhienne
Aug 22 '17 at 0:44
We do not know what you are doing, how you are compiling it, or your specific set of patches. (...) You might also not be using the right header files (i.e) using the headers of the wrong kernel version. There are too many unknowns.
– Rui F Ribeiro
Aug 22 '17 at 0:49
ls -ld /etc/initshowsdrwxr-xr-x 2 root root 4096 Aug 21 13:50 /media/yangjiel/system/etc/init, it is a folder not an executable file. There is 29 rc files in it. I tried using the upstream kernel provide by Android (branch name call android-4.4-n-release, Linux kernel v4.4), but I got the same error. I am using the old/device/vendorfolder for the new Android system which probably where the problem is.– Jason Liu
Aug 22 '17 at 16:32