Develop Bugs

Flashing Galaxy S kernel from update.zip : template update.zip

NEWS :
Koush's bmlunlock (a simple IOCTL send to the bml device) is just out and can replace redbend_ua !
http://github.com/CyanogenMod/android_device_samsung_bmlunlock
Hey
Is Flashing from update.zip the new trend ?
'Don't know but here is how you can do it quite easily using this template.
If you target a GT-I9000 on Eclair, you'll need to customize one thing :
In build-update-zip.sh, set DROID_HOME to the source code path for your local Android repository.
If you target another Galaxy S phone or another version of Android, you'll need to adjust ro.hardware and ro.build.id properties accordingly.
This template is done for Linux/Unixes/OSX.
If Linux cost too much for you or your employer, please contribute by sending a .bat equivalent to the .sh
Of course, you also need to put a valid zImage to replace the template's empty zImage
Feel free to adjust to your needs. License is WTFPL
Note : requirement are Java and Android source repo, already build.

Looks awesome!
I have a question though... why do you need to flash the kernel in an update.zip at boot?
As far as I know, the system will read the kernel at boot up time and load it into ram. It won't access the on-disk file again until the next boot. If that is true, then flashing while running should be 100% safe, right?

RyanZA it's an update.zip, not a ramdisk.
The point is getting an easy flashing method, requiring no computer.
And you don't even need to root your phone !

curio, as i see this script is quite simple, so dont u think this all could actually be done on the phone directly? i mean if people cant afford a linux machine...
edit:
sorry for major dumbness, but do you think this could also somehow be used to reflash a nandroid backup?

FadeFx said:
curio, as i see this script is quite simple, so dont u think this all could actually be done on the phone directly? i mean if people cant afford a linux machine...
Click to expand...
Click to collapse
I don't think the signing tool works on android -- maybe it does? Anyway editing scripts on a phone seems a bit silly!

FadeFx said:
curio, as i see this script is quite simple, so dont u think this all could actually be done on the phone directly? i mean if people cant afford a linux machine...
edit:
sorry for major dumbness, but do you think this could also somehow be used to reflash a nandroid backup?
Click to expand...
Click to collapse
Nope actually this is not dumb at all
Yes the flashing part run in updater-script can be started manually.
In the script :
Code:
"redbend_ua", "restore", "zImage", "/dev/block/bml7"
The update.zip presented here mainly targets custom kernel creators in order to give them another way to distribute their work.
This is a working example of how to use redbend_ua programmatically, hopefully it may help new ideas coming. redbend_ua usage is not limited at all to kernel flashing.
PS : you can use this template with windows as well, you'll just need to translate the ulta-basic .sh to a .bat script, or do the signing part manually.

supercurio said:
Hey
If you target a GT-I9000 on Eclair, you'll need to customize one thing :
In build-update-zip.sh, set DROID_HOME to the source code path for your local Android repository.
Click to expand...
Click to collapse
quick question, the build-update-zip.sh is not a must if i only want to flash zImage, rite?
looks like that, I need to modify updater-script (if needed), as well as putting a zImage into ur zip file, and finally remove the build-update-zip.sh from ur zip attached
then, ur zip file can be used for flashing
is it correct?
thx

So this will let people flash any rom from an update.zip (once the ROM makers take this into account) via RomManager without ever having to use Odin to get off stock?
Awesome!

Thanks for the update script curio! this looks great.
One quick question - ive noticed several update.zip scripts for the galaxy S
have update-binary included.
Does anyone know what that does?? where did you get yours?
ive had success in using update.zips without that file at all.
Could anyone post information on what that binary is/does?
supercurio said:
Hey
Is Flashing from update.zip the new trend ?
'Don't know but here is how you can do it quite easily using this template.
If you target a GT-I9000 on Eclair, you'll need to customize one thing :
In build-update-zip.sh, set DROID_HOME to the source code path for your local Android repository.
If you target another Galaxy S phone or another version of Android, you'll need to adjust ro.hardware and ro.build.id properties accordingly.
This template is done for Linux/Unixes/OSX.
If Linux cost too much for you or your employer, please contribute by sending a .bat equivalent to the .sh
Of course, you also need to put a valid zImage to replace the template's empty zImage
Feel free to adjust to your needs. License is BSD anyway.
Note : requirement are Java and Android source repo, already build.
I'll add some documentation later.
Click to expand...
Click to collapse

dseo80 said:
Thanks for the update script curio! this looks great.
One quick question - ive noticed several update.zip scripts for the galaxy S
have update-binary included.
Does anyone know what that does?? where did you get yours?
ive had success in using update.zips without that file at all.
Could anyone post information on what that binary is/does?
Click to expand...
Click to collapse
Thats for the updater-script i believe. In most cases, theres a update-script in the zip's as well and the recovery picks that up in which case it doesn't need the binary and hence works.

Okay !
Answers hour
ykk_five said:
quick question, the build-update-zip.sh is not a must if i only want to flash zImage, rite?
looks like that, I need to modify updater-script (if needed), as well as putting a zImage into ur zip file, and finally remove the build-update-zip.sh from ur zip attached
then, ur zip file can be used for flashing
Click to expand...
Click to collapse
When you run ./build-update-zip.sh,
- it produce a temp zip file containing appropriate files in it.
- then there'is the signature part, building another .zip, ready to be used.
- this "final" update.zip is put in the same current directory and you can use it as it is.
No further complication
Brantyr said:
So this will let people flash any rom from an update.zip (once the ROM makers take this into account) via RomManager without ever having to use Odin to get off stock?
Awesome!
Click to expand...
Click to collapse
Yes, to flash a complete ROM (several partitions) one more thing is needed.
On command line, redbend_ua accept only one command.
In order to run several commands successively (ie flash multiple partition like Odin does), you'll need to write them in a file.
The file /cache/ota/command should do the trick, but it's untested right now.
There may be other method to prevent rebooting after flashing (hacking the redbend_ua binary, finding the appropriate command line option or removing the reboot command temporary)
dseo80 said:
Thanks for the update script curio! this looks great.
One quick question - ive noticed several update.zip scripts for the galaxy S
have update-binary included.
Does anyone know what that does?? where did you get yours?
ive had success in using update.zips without that file at all.
Could anyone post information on what that binary is/does?
Click to expand...
Click to collapse
Right, many update.zip done today are made without knowing anything about how it really works
I studied a bit before creating mine, here is a walk-through this fairly undocumented process :
- recovery mounts /sdcard/
- recovery search for a default file named : META-INF/com/google/android/update-binary in the zip and runs it : see the source in bootable/recovery/install.c
- update-binary is actually updater in sources
- updater looks into the zip file to the script file named updater-script, update-script is obsolete
- updater then runs the commands listed in updater-script : here is the list of commands.
- then reboot
The only documentation I know for this command is the recovery/updater/install.c file itself

supercurio said:
When you run ./build-update-zip.sh,
- it produce a temp zip file containing appropriate files in it.
- then there'is the signature part, building another .zip, ready to be used.
- this "final" update.zip is put in the same current directory and you can use it as it is.
Click to expand...
Click to collapse
ok,thx
but one more thing i want to know is, u said the path must be changed to the android repo, so do u mean the source code for the kernel like linux-xxx-2.xxx dir?
Thx

@ykk_five
Content of build-update-zip.sh v1 :
Code:
#!/bin/sh
DROID_HOME="/home/curio/dev/mydroid"
zip -r /tmp/update.zip META-INF/ redbend_ua zImage
java -jar \
$DROID_HOME/out/host/linux-x86/framework/signapk.jar \
$DROID_HOME/build/target/product/security/testkey.x509.pem \
$DROID_HOME/build/target/product/security/testkey.pk8 \
/tmp/update.zip update.zip
rm /tmp/update.zip
adb push update.zip /sdcard/
DROID_HOME="/home/curio/dev/mydroid" : you set here the directory of your Android AOSP directory.
See : http://source.android.com/source/download.html
Create an empty directory to hold your working files:
$ mkdir mydroid
$ cd mydroid
Run "repo init" to bring down the latest version of Repo with all its most recent bug fixes. You must specify a URL for the manifest:
$ repo init -u git://android.git.kernel.org/platform/manifest.git
* If you would like to check out a branch other than "master", specify it with -b, like:
$ repo init -u git://android.git.kernel.org/platform/manifest.git -b cupcake
Click to expand...
Click to collapse
This is this mydroid directory
The one that contains Android git source home directory, and compiled files in the out/ subdir

many thx for ur detailed explanation, supercurio!

Thanks curio,
very helpful explanation!

Thanks supercurio for the template!
However, there is no need to spend many hours (depending on hardware and bandwidth) pulling down 100s of megabytes of source and compiling it all if all you want is to sign an update.zip with test keys (if you already have the zImage)!
Just google around for "signapk.jar test keys" and you will get there.
BTW: I know that koush, leshak and wesgamer have Samsung Galaxy S trees up at Github but are they fully merged with AOSP yet?
I'm planning to go build my own kernel for this beast to try to solve the mono FM radio mystery, but last time I checked around it was said that the SGS tree required the use of a custom toolchain to get it to work at all.
Any comments on this?

Hey miki4242 !
Good to know that signapk.jar doesn't require hundred of megs of dependencies
About toolchain, you can use the one indicated by Samsung (CodeSourcery) but you'll face the big and ugly WakeLag.
I recommend you crosstool-ng or buildroot to build toolchains, with gcc 4.3.x march=arm mcpu=cortex-a8 mtune=cortex-a8 (no 4.4.x with march=armv7-v)
The building tutorial will be a part of the documentation I'll publish with my lagfix opensource release
Right now these info are too hard to find.
PS : I send you a mail with attached .config for ct-ng !

supercurio said:
Hey miki4242 !
Good to know that signapk.jar doesn't require hundred of megs of dependencies
Click to expand...
Click to collapse
supercurio said:
PS : I send you a mail with attached .config for ct-ng !
Click to expand...
Click to collapse
Thanks for the info !

Sorry for my ignorance, but does this mean someone can package Froyo in an update.zip and we could update it directly on our phone without needing Samsung Kies or Odin?

@supercurio:
Thanks for this well working template.
In updater-script:
Code:
line 17: package_extract_dir("zImage", "zImage");
should be
Code:
package_extract_file("zImage", "zImage");
But it did work with package_extract_dir, for some reason, too.
Btw, could you send me the config for ct-ng ?
I'm also struggling with this wakelag.

[How To] [GSM] Getting started with porting

Ok, so after having a million questions I thought I'd write up a quick little 'how to' with regards to porting.
And now the warning
Read and learn first, doing this could cause serious issues with your tab or even brick it. The tab is really tough, and hard to brick if you do everthing right but it could still happen. I'm not responsible if it does.
Where to start
Get good at reading, google searching and searching XDA. Lots of porting discussion regarding other phones can apply to the tab.
Learn to use Heimdell
Have a linux distro available, either by virtual box, or natively.
Technomancer where it all began
I've said it before and I'll say it again, without techs work miui wouldn't have been possible.
Reference technomancers thread here: http://forum.xda-developers.com/showthread.php?t=931857 on how to download the cm7 + sgt source, you're also going to want to follow the kernel making part, cause most likely you'll need to make adjustments to the init.rc which is inside the initramfs and requires building the kernel again.
porting x build
Get X build onto your computer and extract the update.zip for it.
Copy the boot.img into your linux environment and extract it using splitbootimg.pl script (note: Google it, plus this doesn't work with samsung builds). Compare the init.rc to your init.rc (from the sgt cm7 kernel source root folder). Specifically the most important part here is the PATH, LD_LIBRARY_PATH statement and BOOTCLASSPATH lines.
Build your kernel with the updated init.rc and flash with heimdell, it should still boot your cm7/miui build (if you were running it before) albeit with errors.
The system
Now following the awesome list of proprietary files (either from your source folder or technomancers github link) check the galaxytab-common-vendor-blobs.mk for the GT-P1000. It lists every file you need that's propreitary to the tab and where to put it.
Also you'll probably need the debuggerd from /system/bin on the cm7 build.
Compare the /system/build.prop of the cm7 build to your port, make sure the ril info is the same as well as the ro; model, brand, device, board, and platform lines.
Create an update.zip (or whatever you want to call it.zip) and try it.
It's not booting
Logcat is great, but I really suggest using the ddms from the android sdk tools. It's color coded, and gives a much nicer view of what's happening.
Using winmerge in windows or a linux file compare program start checking what other bin files may be missing that you require. Special notice to the xbin folder.
It works! I want to post it!
Ok, first up, make sure you have permission if this is someone elses custom build you've ported. Most people/groups are really good about it assuming you ask first and give them credit in your post.
Also credit everyone who helped, answered a question or sent you in the right direction. (it's just polite)
Second your going to want to make sure your update.zip flashes the kernel, read the update_script from the cm7 build to understand how it works.
So that's it for a start. roll up your sleves, gather your courage and get to it!
Please if you have other tips, add them to the thread, what's better 1 or 2 'developers/porters' or 100?

Thanks. This is very useful for me.

Thanks,
Following this method, with slight alterations to adjust, I was able to port an i9000 phone build to the tab in about 10 minutes, it's really not terribly that difficult once you have the right steps.
The first couple times are usually frustrating but after that you get the hang of it

Hi mssmison Thank you for your guide,it will be very useful in the future! I have only one request,how can I contact you? I have a proposal for you about a dev team (regarding an old think tank)

Thanks for the guide...
Is there any ROM left to port by the way?
Sent from my GT-P1000 using XDA Premium App

[Hot!] Wanna Be a Developer AkA Cook ?

I know nothing much of ROM Development but I do have the basic foundation knowledge and I wish to commence in releasing a modded ROM soon as a start...
As a start can anyone give a pointer of the following :
1. Boot image » what is required to extract / modify ?
Note : Please do not re-quote as I will be making changes as we go along
So let us discuss and explore so that we can learn together....
Sent from my GT-I8150 using xda premium

I was thinking of doing the same andy. Asked cow to see if he would like to point me in the right direction.
I had to abandon my idea as new house i moved into i dont have any internet to work off so had to put my plans on hold. But here is what i was told what is basically needed for cooking roms.
1) Download Kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
2) Download your stock ROM
3) Extract system.img.ext4, cache.img.ext4 and boot.img from stock ROM, put into Kitchen's original_rom folder
4) Do this for SGW: http://forum.xda-developers.com/show...8&postcount=12
- No need to upse KezzaPlane's updater script anymore
5) Run ./menu in kitchen and follow the instructions
On part 3. If you want to use a different kernal( Oc one or simply Cow's oc kernal) please make sure to ask for the use of the kernal first and then use that boot.img and replace it into the rom that you are going to cook.

hi, thank you very much for the information, so far i have downloaded eclipse ee, and the android sdk but had zero idea where to start lol
i was so motivated when arco started and released his ics rom that i wanted to do my share as well, i have experience in coding in java but also wanted to know what else to do, then i bumped on this post, thanks a lot man!

snwman said:
4) Do this for SGW: http://forum.xda-developers.com/show...8&postcount=12
Click to expand...
Click to collapse
um unfortunately that link doesn't seem to work, may i ask for the full link?

this is awesome, i will support this thread. pls someone provide clear informations on how and what needed

[Q][Help] B5510 - Building Kernel/boot.img Problem

Hi there.
First: Im a noob, so unless i have fewer than 10 posts i can only post in general forum - otherwise i would post on an existing thread (i will mention later).
Last week i got a new phone: Samsung Galaxy Y Pro (GT-B5510).
Its a nice phone, but im missing a thing: a firewall.
I tried droidwall and other, but they arnt working. So there is something wrong with the netfilter/iptables modul and ive to rebuild the kernel.
After a quick search i found this thread and this post.
I already set up a Ubuntu (10.04.4), downloaded the source from samsung and the toolchain from Sourcery (like they mention inthe infofile from samsung).
I build the kernel, like irfanbagus in his post, but for my device.
I got lots of compilerwarnings, but in the end i have had my zImage without errors.
I split my boot.img, which i got from my device with Terminal Emulator, with split_bootimg.pl.
Now ive got a kernelimage and a initrd and ive to put them together.
Presumably with mkbootimg, but ive to know the baseadress.
I tried the offset from the thread mentiond above.
I made a tar and flashed it with Odin1.85 and half bricked it.
[I only can see a grey battery on the diplay and if i reboot it it stuck on bott/splashscreen]
Maybe somebody can help. (please)
Is the problem the compiled kernel, due to the warnings?
Or is it the wrong baseaddress? Well i could not find the address inside the sourcecode (like kconfig), like i read somewhere, thats why i tried the one from s5360.
There is no problem with odin or the cable, cause i can flash my backup with it to 'unbrick' it.
And why is the bootimg around 700kb smaller than the original?
Thanks a lot in advance.

havocinside said:
Hi there.
First: Im a noob, so unless i have fewer than 10 posts i can only post in general forum - otherwise i would post on an existing thread (i will mention later).
Last week i got a new phone: Samsung Galaxy Y Pro (GT-B5510).
Its a nice phone, but im missing a thing: a firewall.
I tried droidwall and other, but they arnt working. So there is something wrong with the netfilter/iptables modul and ive to rebuild the kernel.
After a quick search i found this thread and this post.
I already set up a Ubuntu (10.04.4), downloaded the source from samsung and the toolchain from Sourcery (like they mention inthe infofile from samsung).
I build the kernel, like irfanbagus in his post, but for my device.
I got lots of compilerwarnings, but in the end i have had my zImage without errors.
I split my boot.img, which i got from my device with Terminal Emulator, with split_bootimg.pl.
Now ive got a kernelimage and a initrd and ive to put them together.
Presumably with mkbootimg, but ive to know the baseadress.
I tried the offset from the thread mentiond above.
I made a tar and flashed it with Odin1.85 and half bricked it.
[I only can see a grey battery on the diplay and if i reboot it it stuck on bott/splashscreen]
Maybe somebody can help. (please)
Is the problem the compiled kernel, due to the warnings?
Or is it the wrong baseaddress? Well i could not find the address inside the sourcecode (like kconfig), like i read somewhere, thats why i tried the one from s5360.
There is no problem with odin or the cable, cause i can flash my backup with it to 'unbrick' it.
And why is the bootimg around 700kb smaller than the original?
Thanks a lot in advance.
Click to expand...
Click to collapse
upload your boot.img

boot.img
Here it is.
boot.tar = compiled
boot-stock.tar = original from my device

Size is not problem as long running well.
In my sgy always fail when size >
5.5mb
For boot-stock.tar u get from dd or pda stock-rom ??
Mmm i thing irfan has answer so ur save dude.

its dd.

i don't find any problem with boot.img. offset is equal (0x81600000). the problem maybe in your zImage. make sure you build with correct defconfig. mine is bcm21553_totoro_05_defconfig, i don't know yours, see in text info inside zip file from samsung. and make sure using the same compiler version with text info said. using different version make prebuild kernel module inside initramfs not working. start with default config from xxx_defconfig just to make sure your step is correct. and if still not working your best hope is build your module as loadable module (.ko), add init.d support in init.rc (inside initramfs), and load your module using init.d script.
about the size, it's nomal boot.img from dd command bigger than normal boot.img because it's copy whole partition and include unused bytes behind the original boot.img.

hm, ok.
thank you irfan.
i followed the instructions from the txt inside the archive:
"bcm21553_luisa_03_defconfig" with "g++ 2009q3-68 arm eabi"
ill try again.

my bad. i download wrong files, and end up with comparing the same original boot.img
your compiled boot.img don't have md5 checksum. i am not sure it have effect, i make that tutorial based post from harish2704 here. mkbootimg from harish2704 have --kernelMD5 param. try use that one.

savie said:
Size is not problem as long running well.
In my sgy always fail when size >
5.5mb
For boot-stock.tar u get from dd or pda stock-rom ??
Mmm i thing irfan has answer so ur save dude.
Click to expand...
Click to collapse
our kernel partition only 5 mb my friend...

Boot.img from dd not work with me so i pick from pda stock-rom
(i use from doky thread).
Mmm that why i fail when boot.img more than 5mb.
Trying other method to compile, irfan say merruk use lzma or someting like that.

I can only suggest the method irfanbagus described (loadable kernel modules) because the source code Samsung released probably isn't up to date. The benefits of compiling the needed modules into the kernel are too little compared with possible bugs which are in the released code but not in the stock kernel.

mikstev said:
I can only suggest the method irfanbagus described (loadable kernel modules) because the source code Samsung released probably isn't up to date. The benefits of compiling the needed modules into the kernel are too little compared with possible bugs which are in the released code but not in the stock kernel.
Click to expand...
Click to collapse
i find relative new kernel for sgy, but still cannot make running. it's from galaxy pocket source. there is small change related to power management, but still don't have time to studying.

After a weekend full of trouble, today i found time to continue the bootimg-thing.
I now compiled only the modules and load them now with initd, because i was unable to build a runnable kernel from source.
(Thank you irfan and mikstev)

irfanbagus said:
i find relative new kernel for sgy, but still cannot make running. it's from galaxy pocket source. there is small change related to power management, but still don't have time to studying.
Click to expand...
Click to collapse
are you sure that we can use that kernel for our sgy?

[Q&A] [kernel][stock][D85520P][init.d][bumped]Stock EXperience (for) You -- SEXY

Q&A for [kernel][stock][D85520P][init.d][bumped]Stock EXperience (for) You -- SEXY
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [kernel][stock][D85520P][init.d][bumped]Stock EXperience (for) You -- SEXY. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Sexy kernel question
Hello . Is it possible to create a version of the set selinux permissive . Alternatively, if there is any init.d script that is changing. Greetings

mnkowalski said:
Hello . Is it possible to create a version of the set selinux permissive . Alternatively, if there is any init.d script that is changing. Greetings
Click to expand...
Click to collapse
Hello,
I did it and i can share if you want but you better use init.d to do this:
Create a file named 07setpermissive in /etc/init.d folder with inside this simple code, and give 755 permission to this file (with a root explorer).
Code:
#!/system/sh
setenforce 0
Reboot, and it's done (SELinux is set to "permissive"). If you want to disable it, you can tape in a terminal emulator;
Code:
su
setenforce 1
If you really need, i can share the same thing done in ramdisk.

I would be grateful for it
For many people this will be useful . I would appreciate it if he had se linux kernel permessive

mnkowalski said:
For many people this will be useful . I would appreciate it if he had se linux kernel permessive
Click to expand...
Click to collapse
Done, links are in original thread OP http://forum.xda-developers.com/lg-g3/development/kernel-stock-experience-sexy-t3120751
or
http://forum.xda-developers.com/showpost.php?p=61061948&postcount=8
You can hit thank's if it helps

Maybe I'm doing something wrong but the scripts in the init.d do not work, so it just me . I created a script to test init.di was not a log file . When installed with supermarket universal program init.d script then she began to move. I installed both kernels and nothing

mnkowalski said:
Maybe I'm doing something wrong but the scripts in the init.d do not work, so it just me . I created a script to test init.di was not a log file . When installed with supermarket universal program init.d script then she began to move. I installed both kernels and nothing
Click to expand...
Click to collapse
Did you give the right permissions to your script?
What does this script (code)?

permission is ok
Script :
#!/system/bin/sh
echo init.d is working >> / storange /emulated/0/initdsupport.txt
Using the program -> script starts , uninstall the program and stops working script
Sorry for bad english

mnkowalski said:
permission is ok
Script :
#!/system/bin/sh
echo init.d is working >> / storange /emulated/0/initdsupport.txt
Using the program -> script starts , uninstall the program and stops working script
Sorry for bad english
Click to expand...
Click to collapse
Try to write in /data, it should work
echo "init.d is working" >> /data/initdsupport.txt

None of this after the change does not work still , but with the application from google play test log appears and init.d works. I give up. If I ask for a hint
https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=pl
with this application works

mnkowalski said:
None of this after the change does not work still , but with the application from google play test log appears and init.d works. I give up. If I ask for a hint
https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=pl
with this application works
Click to expand...
Click to collapse
It didn't work because the path of sdcard is not good in your script.
If you want to write log in sdcard (internal storage) the code must be
Code:
#!/system/bin/sh
echo "init.d is working" >> /mnt/sdcard/initdsupport.txt
instead of your
Code:
#!/system/bin/sh
echo "init.d is working" >> /storage/emulated/0/initdsupport.txt
I just tested it, and it works well with my moded 20p ramdisk, without need of another system mod.
You just have to use /mnt/sdcard instead of /storage/emulated/0
App you are talking about is an emulation of init.d (not real init.d, as ramdisk supports), it uses install-recovery.sh.
http://forum.xda-developers.com/showthread.php?t=1933849

Can I install any of these kernels over one of your previous 5.x ROMs ( such as Androidnow HD). Or do I need to install the entire new ROM ?
If I can install just the kernel then do I need to root it ?
Many thx

soupratt said:
Can I install any of these kernels over one of your previous 5.x ROMs ( such as Androidnow HD). Or do I need to install the entire new ROM ?
If I can install just the kernel then do I need to root it ?
Many thx
Click to expand...
Click to collapse
Hi,
I don't know if i understand well your questions.
I didn't test all possibles combos (all possibles shared stock or based stock) roms with these kernels (ramdisks) moded, i think you can understand that
You can easily test it and report the result if you want, I (we) 'll be interested to read this.
For that, you need to know how to flash a kernel (custom recovery is the best solution), how to backup the one you used before, how to boot on custom recovery with hard key for eventually restoring this one you backuped before, how to quit a secure boot error screen (removing battery) that you can meet with a bad kernel, and, of course, that root is really needed for doing all of that.
Posted without using google translation, sorry for my english

6ril1 said:
Hi,
I don't know if i understand well your questions.
I didn't test all possibles combos (all possibles shared stock or based stock) roms with these kernels (ramdisks) moded, i think you can understand that
You can easily test it and report the result if you want, I (we) 'll be interested to read this.
For that, you need to know how to flash a kernel (custom recovery is the best solution), how to backup the one you used before, how to boot on custom recovery with hard key for eventually restoring this one you backuped before, how to quit a secure boot error screen (removing battery) that you can meet with a bad kernel, and, of course, that root is really needed for doing all of that.
Posted without using google translation, sorry for my english
Click to expand...
Click to collapse
Hi 6ril1 and thank you for your response.
I probably wasn't very clear. What I wanted to know is whether I can install just the 20p kernel on phone which has a rom with an earlier kernel (like 20i or similar). Would the 20p kernel have any issues with a ROM designed for an earlier kernel. Up to know I used Seven's Androidnow HD ROM but unfortunately he has pull out support for newer ROMs due to some asshat distributing his ROMs without consent. The last ROM he had was 14 but it wasn't fully optimised. I am using his earlier 10.3 Androidnow HD ROM. So I was wondering if your 20p kernel will work ok with having to install a whole new ROM.
Cheers

soupratt said:
Hi 6ril1 and thank you for your response.
I probably wasn't very clear. What I wanted to know is whether I can install just the 20p kernel on phone which has a rom with an earlier kernel (like 20i or similar). Would the 20p kernel have any issues with a ROM designed for an earlier kernel. Up to know I used Seven's Androidnow HD ROM but unfortunately he has pull out support for newer ROMs due to some asshat distributing his ROMs without consent. The last ROM he had was 14 but it wasn't fully optimised. I am using his earlier 10.3 Androidnow HD ROM. So I was wondering if your 20p kernel will work ok with having to install a whole new ROM.
Cheers
Click to expand...
Click to collapse
Hi,
Just try it, after the usual precautions (Make kernel backup before in custom recovery. It means backup boot partition)
Flash kernel, and if it doesn't work on your rom, restore the last one you backuped, that's all
I tried it with an older lp stock with succes (these moded boot worked with older stock firmware).
As i answered you before, if you have a security error screen (following by a black screen without any possible acces) on boot with the new kernel, remove battery, reboot in custom recovery with hard key combo (=> buttons power + volume down, release when logo appears, and again power + vol down, until custom recovery acces appears), and restore your previous kernel that worked. As simple like that
Of course, prerequisite is that you have twrp installed.

Hi
Im using zenfone 4 a400cg stock rom with android lollipop.i need help to enable init.d on my device as i have done all method found on the internet but still no result...please some 1 help x.x
Sent from my ASUS_T00I using XDA Free mobile app