Zip-file apparently doesn't perform a correct installation

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download Bricked Kernel v0.6 (MD5 matches)
2. Flash the zip-file
3. Reboot the system

What is the expected output? What do you see instead?
Working system. Instead there's no WiFi. 

What version of the product are you using? On what operating system?
v0.6 on stock Android 4.2.1

Please provide any additional information below.
During trying to perform the check for proper init.d-support I noticed there's 
no /sys/etc/init.d folder resulting in not being able to execute the script to 
start WiFi manually. Could there be a problem resulting in the files from the 
zip-File not being installed properly?

Original issue reported on code.google.com by jan.rin...@gmail.com on 22 Dec 2012 at 12:41

[GoogleCodeExporter]

Add.: This is on the Nexus 4. BusyBox is installed (to /system/xbin).

Original comment by jan.rin...@gmail.com on 22 Dec 2012 at 12:43

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

There is no /sys/etc/init.d
You are looking for /system/etc/init.d

Give me a dump of your boot partition and adb shell ls /system/xbin & adb shell 
ls /system/bin please.

Original comment by showp1984 on 22 Dec 2012 at 12:48

[GoogleCodeExporter]

The "sys/etc/init.d" was a typo, I was looking for it under 
"/system/etc/init.d". There's a file called init.d, though (in "/system/etc").

The requested dump and ls's are on their way to you.

Original comment by jan.rin...@gmail.com on 22 Dec 2012 at 12:57

[GoogleCodeExporter]

The ramdisk is prepared for init.d (aka my script did it's work ^^)

service userinit /system/xbin/busybox run-parts /system/etc/init.d
    oneshot
    class late_start
    user root
    group root

So you say that there is no folder under /system/etc/ called init.d? That is 
strange.
Is there one in the zip you downloaded? (under system/etc/)

Original comment by showp1984 on 22 Dec 2012 at 1:07

[GoogleCodeExporter]

Also: What recovery do you use? That's the very first time I heard of this 
issue. (The recovery not being able to extract files/folders.
I would ask you to delete that file and add an init.d folder under /system.
adb shell
su
mount -o remount,rw /system
rm -rf /system/etc/init.d
mkdir /system/etc/init.d
exit
exit

Then boot into recovery and reflash the zip.
The only reason I could think of is that because it found something called 
init.d in there it did not extract the data. That would be an edify bug though 
and has nothing to do with my zip.

The only thing under /system/etc called init.d should be a directory:

ls -al /system/etc | grep 'init.d'
drwxr-xr-x root     shell             2012-12-20 10:46 init.d

Original comment by showp1984 on 22 Dec 2012 at 1:13

[GoogleCodeExporter]

Exactly, there is just a file called init.d, but not the folder.
The zip-file contains the folder "system/etc/init.d" with three files inside of 
it (00wlan, 01cifs, 02tun), that's why I thought there must have been gone 
something wrong during installation.

The MD5 is also correct, so I think the file must be ok.

Original comment by jan.rin...@gmail.com on 22 Dec 2012 at 1:13

[GoogleCodeExporter]

I'm using ClockworkMod 6.0.2.3. 

Will now try your steps to manually create the init.d-folder and report back.

Original comment by jan.rin...@gmail.com on 22 Dec 2012 at 1:15

[GoogleCodeExporter]

It's working now. Manually creating that folder seems to have done it.

Thank you very much for your help!

Original comment by jan.rin...@gmail.com on 22 Dec 2012 at 1:28

[GoogleCodeExporter]

No problem.

Original comment by showp1984 on 22 Dec 2012 at 1:36

• Changed state: Done