Hey does anybody have a TUT in how to decompile an existing kernel so i can make some changes and then recompile it?
Sent from my GT-I9001 using XDA
Hey did you ever get your answer? I am also looking to do the same thanks.
EternalFame said:
Hey does anybody have a TUT in how to decompile an existing kernel so i can make some changes and then recompile it?
Click to expand...
Click to collapse
This is not the way it's done.
You'll have to get your kernels configuration. This is done either by see if there's a /proc/config.gz using the running kernel, or using the extract-ikconfig script shipped with the kernel source to extract the configuration from the kernel file.
Code:
$ extract-ikconfig kernel.img-kernel
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32.9
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_GENERIC_GPIO=y
CONFIG_GENERIC_TIME=y
[...]
This configuration you supply to the kernel source. If the vendor got some specific patches (they do), you'll have to get the kernel source from them, patches included. They must supply you the source, or be in violation of the GNU General Public License.
Building the Android boot image using mkbootimg, you'll also have to get the base address from this config.
Code:
$ extract-ikconfig kernel.img-kernel | grep PHYS_OFFSET
CONFIG_PHYS_OFFSET=[B]0x00200000[/B]
Now you have everything you'll need to build a correctly configured kernel and making the Android boot image. Detailed build instructions are included in the kernel source as well.
Wow thank you
Sent from my SGH-T989 using xda premium
Can we extract kernel with dsixda kitchen?
Edward Cullen
Kernel can be extracted, rename to *.zip
purrungo said:
Kernel can be extracted, rename to *.zip
Click to expand...
Click to collapse
it kernel.lz or etc format when use extractor it say corrupted archive
why manufacturers have to provide kernel to users when they don't want users to modify their products?. Many manufacturers just sell devices, and strangely there are many dev.er who CaN overclock or patch, modify the kernel with boot.img, HOW did they do thAt??? Kernel source code sometimes is their devevloper source code, not from manufacture stock source code.
i want to de and recompile kernel file for WSA
(windows subsystem for android)
any help?
foxhackerr said:
Any help?
Click to expand...
Click to collapse
Depending on what/how much you want to modify it can be easier to patch an existing kernel than to build from scratch. Me? I'm lazy. I never build anything.
Get boot image
Extract kernel
Decompress kernel
Extract kallsyms
Disassemble kernel
Come up with a patch and patch it
Put it back together
(Steps 4 & 5 may be combined depending on your tools. I do them separately.)
Renate said:
Depending on what/how much you want to modify it can be easier to patch an existing kernel than to build from scratch. Me? I'm lazy. I never build anything.
Get boot image
Extract kernel
Decompress kernel
Extract kallsyms
Disassemble kernel
Come up with a patch and patch it
Put it back together
(Steps 4 & 5 may be combined depending on your tools. I do them separately.)
Click to expand...
Click to collapse
How to do this??
kxrma said:
How to do this??
Click to expand...
Click to collapse
Use dd if rooted or EDL or extract from update
I use my imgutil.exe
I use my imgutil.exe
I use my kallsyms.exe or cat /proc/kallsyms on a running system
I use the stock objdump processed afterward with my own findref.exe (not really released yet). You could use Ghidra.
Use any hex editor. I also use my own kpatch.exe (not really released yet).
I use my imgutil.exe
Related
NEW:
Working .34-rc3 kernel available at http://forum.xda-developers.com/showpost.php?p=6290443&postcount=45
OLD:
Code:
This is an experimental .34-rc2 kernel for the Nexus One.
Provided in the zip file is a folder (2.6.34-rc2-termana-nexusone) and the kernel (zImage).
It is extremely experimental, so only follow this if you [B][I][U]really[/U][/I][/B] know what your doing and know how to reflash another kernel back to make it boot again if it doesn't boot. I'm not responsible if your device curls over and dies.
Use adb to push the folder into /system/lib/modules/ and then use fastboot to flash the kernel.
The kernel is a rebase of cyanogen's .33.1 kernel to the latest .34-rc2 kernel. So nothing particularly new about it, besides the satisfaction that not many people would be running this kernel version on devices.
Zip file: bit.ly/94Oo6m (To download it click the link next to the text "Save file to your PC:")
Edit: Being a new member of xda-developers forum, it wouldn't let me post the link properly, but just copy and paste it and you'll be fine.
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
I just flashed the zimage, and the phone went into a boot loop. Do I have to install anything else?
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Will give it a go nad logcat it
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
thanks, thought it was a mistake that you said push that folder, glad you clarified it for me
thanks again
jlevy73 said:
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
Click to expand...
Click to collapse
damn, that is long; won't bother reading that thing
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
I used this:
adb push 2.6.34-rc2-termana-nexusone /system/lib/modules/2.6.34-rc2-termana-nexusone
Click to expand...
Click to collapse
...and it still went into a boot loop for me.
hotweiss said:
I used this:
...and it still went into a boot loop for me.
Click to expand...
Click to collapse
You sure that wouldn't create a folder within a folder?
Not really sure just saying...
So is this working for you Termana?
I tried both have the subfolder and just pushing all the files to /modules and both produced a bootloop
i pushed the folder to /system/lib/modules/ and flashed zimage, but just get bootloop
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
I seriously thought, you tested it on your Nex before posting it....was a missunderstanding.
Termana said:
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
Click to expand...
Click to collapse
Did you cross compile the source against the ARM source?
hotweiss said:
Did you cross compile the source against the ARM source?
Click to expand...
Click to collapse
You might need to rephrase your question as the way you've said it doesn't let me know exactly what you mean by "ARM source". Do you mean using the Android ARM toolchain or what?
To anyone that is willing to help me test:
New build available at - bit.ly/c1tFqg (just the zImage, don't worry about pushing the modules for now)
Info:
This is a .33.1 kernel not a .34-rc2 kernel HOWEVER, I wanted to get the source that I'm rebasing off tested to make sure it boots, because if the source I'm pulling from doesn't boot, then obviously my rebases aren't going to either. So, please test it and tell me if it boots, if it does, I'll have another .34-rc2 kernel build up shortly after. If it doesn't, I may have to try rebasing from the official .32 kernel rather than the current source I'm rebasing from at the moment (which is .33.1).
Booted for me.
Code:
2.6.33.1-cyanogenmod
[email protected] #1
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Justin241982 said:
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Click to expand...
Click to collapse
I wouldn't post it yet. The first one he posted doesn't boot and the second one he posted I don't believe has any optimizations.
Both VPNC (e.g. get-a-robot-vpnc) and OpenVPN require tun.ko kernel module to work. The module is included in most popular ROMs but obviously not a part of SE kernel which we have to live with now.
Loading a tun.ko compiled for other kernels fails with a following message, for example:
adb shell dmesg
"tun: version magic '2.6.29-01117-g4bc62c2 preempt mod_unload ARMv7' should be '2.6.29-rel preempt mod_unload ARMv7".
I tried to see if I could compile the module myself from the posted SE kernel source and using this post as a reference - forum.xda-developers.com/showpost.php?p=5692491&postcount=12, but I'm lost in git and cross-compile toolchain. I also tried changing "2.6.29-01117-g4bc62c2" to "2.6.29-rel" in the existing module with a hex editor, but that made the module invalid.
So, I wonder if someone could help?
Thanks.
crimper said:
Both VPNC (e.g. get-a-robot-vpnc) and OpenVPN require tun.ko kernel module to work. The module is included in most popular ROMs but obviously not a part of SE kernel which we have to live with now.
Loading a tun.ko compiled for other kernels fails with a following message, for example:
adb shell dmesg
"tun: version magic '2.6.29-01117-g4bc62c2 preempt mod_unload ARMv7' should be '2.6.29-rel preempt mod_unload ARMv7".
I tried to see if I could compile the module myself from the posted SE kernel source and using this post as a reference - forum.xda-developers.com/showpost.php?p=5692491&postcount=12, but I'm lost in git and cross-compile toolchain. I also tried changing "2.6.29-01117-g4bc62c2" to "2.6.29-rel" in the existing module with a hex editor, but that made the module invalid.
So, I wonder if someone could help?
Thanks.
Click to expand...
Click to collapse
you need to recompile the kernel module (luckily kernel sources are available)
Please help
I don't know how to recompile kernel. Can you send this file here into forum? And tell us, inferior people who just want to use openvpn, how to put this file there it should be?
Why every linux/unix issue ends with advice "just recompile kernel" or "RTFM"... I don't know how to recompile it and don't know where is that f...g manual. If you mean google, please don't say that.
Thank you very much
pepouwek said:
I don't know how to recompile kernel. Can you send this file here into forum? And tell us, inferior people who just want to use openvpn, how to put this file there it should be?
Why every linux/unix issue ends with advice "just recompile kernel" or "RTFM"... I don't know how to recompile it and don't know where is that f...g manual. If you mean google, please don't say that.
Thank you very much
Click to expand...
Click to collapse
luckily for you, I made a guide in this board about how to recompile the kernel
Also in this topic about recompiling the kernel and there's infos about openvpn there too (search button will help).
And don't talk about inferior people, I really wish it was very easy to add all those stuffs but unluckily it's not. I can help you even if you're lost about kernel recompiling but I can't do all the stuffs for you.
how about searching instead of opening new thread......
http://forum.xda-developers.com/showpost.php?p=7054292&postcount=17
someone close this useless thread....
pepouwek said:
I don't know how to recompile kernel. Can you send this file here into forum? And tell us, inferior people who just want to use openvpn, how to put this file there it should be?
Why every linux/unix issue ends with advice "just recompile kernel" or "RTFM"... I don't know how to recompile it and don't know where is that f...g manual. If you mean google, please don't say that.
Thank you very much
Click to expand...
Click to collapse
We can't use a different kernel to the stock one yet, and there's no point in recompiling the 2.6.29 kernel again, as the devs are trying to run the 2.6.32 one instead for froyo - tun.ko probably should be compiled with this instead. (in fact, I think froyo is able to be run already)
I think the custom spl/bootloader now needs to be tweaked by goroh_kun, Bin4ry, jerpelea etc. to:
- Be autobooted or flashed safely
- To be stable when run
- To be able to boot to a recovery partition and/or bootloader with a key combination
Also, I think they need to:
-Sort out phone partitioning to be used with the new bootloader and recovery image.
-Then try to fix bugs in the CyanogenMod 6 rom, if there are any 'major' ones.
I think that's what the devs are trying to do.
@hunteron you are not completely right even though you can't boot a complete kernel image you can insert your own modules
Sent from my X10i using XDA App
sim-value said:
@hunteron you are not completely right even though you can't boot a complete kernel image you can insert your own modules
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'm sorry; you're right.
Mod. edit: reuse existing thread pls; CLOSED
Hi, I managed to build a kernel from Samsung's sources, but it doesn't work (boot loop). It also seems to be much smaller than the official builds (4.6 MB vs 8 MB). Here's exactly what I did, I wonder if someone could tell me where I'm going wrong:
1. Download & extract the kernel sources from here : https://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=I9100
2. Download and install the old code sourcery GCC as recommended in Samsung's readme from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release298
3. Move the code sourcery install to /opt/toolchains/arm-2009q3
4. Edit kernel/Makefile and change CROSS_COMPILE to
CROSS_COMPILE ?= /opt/toolchains/arm-2009q3/bin/arm-none-eabi-
(it was arm-linux-gnueabi- I think).
5. In kernel, make c1_rev02_defconfig && make
6. It worked, and I got a zImage. I flashed it using heimdall like this:
heimdall flash --kernel zImage
(That worked when I went back to stock so it is obviously correct, but using my kernel I get a reboot loop.)
Anyone have any idea what's so different with my build compared to Samsung's that results in it not working, and being so much smaller?
Timmmmmm said:
Hi, I managed to build a kernel from Samsung's sources, but it doesn't work (boot loop). It also seems to be much smaller than the official builds (4.6 MB vs 8 MB). Here's exactly what I did, I wonder if someone could tell me where I'm going wrong:
1. Download & extract the kernel sources from here : https://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=I9100
2. Download and install the old code sourcery GCC as recommended in Samsung's readme from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release298
3. Move the code sourcery install to /opt/toolchains/arm-2009q3
4. Edit kernel/Makefile and change CROSS_COMPILE to
CROSS_COMPILE ?= /opt/toolchains/arm-2009q3/bin/arm-none-eabi-
(it was arm-linux-gnueabi- I think).
5. In kernel, make c1_rev02_defconfig && make
6. It worked, and I got a zImage. I flashed it using heimdall like this:
heimdall flash --kernel zImage
(That worked when I went back to stock so it is obviously correct, but using my kernel I get a reboot loop.)
Anyone have any idea what's so different with my build compared to Samsung's that results in it not working, and being so much smaller?
Click to expand...
Click to collapse
you will be missing the initramfs. See supercurio's threads for compile scripts and info
You are using the wrong toolchain too!
http://www.codesourcery.com/sgpp/lite/arm/portal/release1039
also, check out this thread
http://forum.xda-developers.com/showthread.php?t=1123643
Hmm but the readme says "Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI." not ARM GNU/linux.... Is that just wrong? And what exactly is the difference?
(I actually did get the 2009 version, not the 2006 one I linked to.)
Thanks for the supercurio hint; very useful. I wish this stuff was in the wiki rather than in random forum threads though. Forums don't make for a good reference or learning format.
Timmmmmm said:
Hmm but the readme says "Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI." not ARM GNU/linux.... Is that just wrong? And what exactly is the difference?
(I actually did get the 2009 version, not the 2006 one I linked to.)
Thanks for the supercurio hint; very useful. I wish this stuff was in the wiki rather than in random forum threads though. Forums don't make for a good reference or learning format.
Click to expand...
Click to collapse
Well, based on what is in the make file you should use the one I linked
CROSS_COMPILE ?= /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-
I just compiled modules not whole kernel but the linux-gnu toolchain was the one which compiled a usable result and not the one that is in readme. That is sure.
richyy74 said:
I just compiled modules not whole kernel but the linux-gnu toolchain was the one which compiled a usable result and not the one that is in readme. That is sure.
Click to expand...
Click to collapse
Figured that would happen, I am trying the recommended one right now to see if it works, guessing I will have the same outcome.
edit: boots up just fine actually...
so, what is the right one ?!
Maybe both work? I dunno, anyway the linux one worked for me, and the kernel is over a MB smaller than the samsung one... weird.
Timmmmmm said:
Maybe both work? I dunno, anyway the linux one worked for me, and the kernel is over a MB smaller than the samsung one... weird.
Click to expand...
Click to collapse
Samsung only uses gzip, guessing you enabled LZMA.
I wouldn't use samsung recommended on, I am getting sleep death with it.
No I'm using gzip (or possibly even no compression, I can't remember). It booted fine but wifi and the vibrator didn't work. Weird 'cause the modules are definitely in there. Maybe it has something to do with the CONFIG_DEBUG... options that shouldn't be set.
Timmmmmm said:
No I'm using gzip (or possibly even no compression, I can't remember). It booted fine but wifi and the vibrator didn't work. Weird 'cause the modules are definitely in there. Maybe it has something to do with the CONFIG_DEBUG... options that shouldn't be set.
Click to expand...
Click to collapse
Read that thread I link above, that is the fix...
Code:
HOW TO BUILD KERNEL 2.6.35 FOR GT-I9100
1. How to Build
- get Toolchain
Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI.
Extract kernel source and move into the top directory.
$ toolchain\arm-eabi-4.4.0
$ cd kernel/
$ make c1_rev02_defconfig
$ make
After looking at this a bit closer. Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI is 4.4.1, not 4.4.0.. I think we should send an email and ask them what is correct.
hello guys!i'm asking for your help if it is possible!i am from the galaxy Y forum.i saw that you are good developers and i was wondering if anyone of you can make a custom kernel for our device with just a few mods.someone tried but with not succes and we dont have devs to do that.please help!!!!thanks
If i wanted to add the volume fix to an exsisting kernel how could i go about that? Is it located in the lib/modules? I have a bit of experience with this but wanted to make sure.
You need to pull the source from bit bucket for the kernel you want to use. Once you have the source tree downloaded, modify the code with the fix, then compile it. You will have just created the Zimage which in combination with RAMDisk creates the boot.img.
It is far from a easy task.
DroidTh3ory said:
You need to pull the source from bit bucket for the kernel you want to use. Once you have the source tree downloaded, modify the code with the fix, then compile it. You will have just created the Zimage which in combination with RAMDisk creates the boot.img.
It is far from a easy task.
Click to expand...
Click to collapse
Whats the fix? A line of code that has to be added? I may wanna play around tonight.
fixxxer2008 said:
Whats the fix? A line of code that has to be added? I may wanna play around tonight.
Click to expand...
Click to collapse
Here is the code....
http://code.tiamat-dev.com/7x30/htc...7760b9641d9c24af6787cc53f993f16455314cb/diffs
It has been merged into IMO 's latest kernel as well as in the modded kernel in my A05P ROM.
Sent from my PUR3 A05P using XDA App
Hello
I am thinking of porting a Galaxy S2 4.1.2 stock touchwiz jb rom to the galaxy player 5.0 probably using cm10 as a base.However, porting requires someone to modify the player 5.0 boot.img which I can't do and I can't compile a kernel as I don't know how to do so and I don't hav Linux.I can tell the volunteer what file in the ramdisk should be modified in order to possibly have a working s2 4.1.2 port.
So is there anyone with a player 5.0 willing to either unpack the player 5.0's boot.img or compile the kernel from source with the modification I will tell you?
This project may actually succeed with the help of the community so I hope that you can help.
Thanks
I98 said:
Hello
I am thinking of porting a Galaxy S2 4.1.2 stock touchwiz jb rom to the galaxy player 5.0 probably using cm10 as a base.However, porting requires someone to modify the player 5.0 boot.img which I can't do and I can't compile a kernel as I don't know how to do so and I don't hav Linux.I can tell the volunteer what file in the ramdisk should be modified in order to possibly have a working s2 4.1.2 port.
So is there anyone with a player 5.0 willing to either unpack the player 5.0's boot.img or compile the kernel from source with the modification I will tell you?
This project may actually succeed with the help of the community so I hope that you can help.
Thanks
Click to expand...
Click to collapse
I can modify, the kernel source to load a ramdisk.cpio from a static folder... I was planning on doing that any way...:good:
All you would have to do is create a ramdisk.cpio with the cpio command, I think...
Meticulus said:
I can modify, the kernel source to load a ramdisk.cpio from a static folder... I was planning on doing that any way...:good:
All you would have to do is create a ramdisk.cpio with the cpio command, I think...
Click to expand...
Click to collapse
Ok great, I might then start this project on the weekend
Thanks
I98 said:
Ok great, I might then start this project on the weekend
Thanks
Click to expand...
Click to collapse
I made the change for the kernel to load external ramdisks:
https://github.com/Meticulus/nutell...mmit/e5e17f478018d84c866f7ec829c17e0272bf0231
here is a build of the kernel with this change and the current carbon ramdisk. You can use the "cpio" tool to make/extract/repack cpio ramdisks..:good:
https://mega.co.nz/#!ZJVDWTxT!tep0VH1nmfCTxYqhDHmUfROxq-O1Joro2_RiJWqd6RI
Meticulus said:
I made the change for the kernel to load external ramdisks:
https://github.com/Meticulus/nutell...mmit/e5e17f478018d84c866f7ec829c17e0272bf0231
here is a build of the kernel with this change and the current carbon ramdisk. You can use the "cpio" tool to make/extract/repack cpio ramdisks..:good:
https://mega.co.nz/#!ZJVDWTxT!tep0VH1nmfCTxYqhDHmUfROxq-O1Joro2_RiJWqd6RI
Click to expand...
Click to collapse
Thanks
but when I'm using this command on Cygwin:
cpio -i -F ramdisk.cpio
I'm getting an error, bash: cpio command not found
Any suggestions?
Meticulus said:
I made the change for the kernel to load external ramdisks:
https://github.com/Meticulus/nutell...mmit/e5e17f478018d84c866f7ec829c17e0272bf0231
here is a build of the kernel with this change and the current carbon ramdisk. You can use the "cpio" tool to make/extract/repack cpio ramdisks..:good:
https://mega.co.nz/#!ZJVDWTxT!tep0VH1nmfCTxYqhDHmUfROxq-O1Joro2_RiJWqd6RI
Click to expand...
Click to collapse
Thank you very much
but when I'm using this command on cygwin:
cpio -i -F ramdisk.cpio
I'm getting an error, bash: cpio command not found
Any suggestions?
Thanks again
I98 said:
Thanks
but when I'm using this command on Cygwin:
cpio -i -F ramdisk.cpio
I'm getting an error, bash: cpio command not found
Any suggestions?
Click to expand...
Click to collapse
Looks like WinRAR has support for cpio?... never tried it but...
Meticulus said:
Looks like WinRAR has support for cpio?... never tried it but...
Click to expand...
Click to collapse
Yeah, I tried it with WinRAR but it still didn't work, I've tried another tool but it didn't work ..
btw, is it just possible to place the init.rc file in the folder as that is the only file that has to be modified?
I98 said:
Yeah, I tried it with WinRAR but it still didn't work, I've tried another tool but it didn't work ..
Click to expand...
Click to collapse
1. Linux on a virtual machine.
2. push the ramdisk to your player using adb. Then, use cpio in adb shell on device or terminal emulator.. :good: