Hi,
My Question is
How do i extract initramfs from a Kernel.bin file ?
the Galaxy S Advance uses Kernel.bin instead of a boot.img
I tried dsixda's kitchen, but it couldn't recognize the file format
I just want to replace a certain binary in the /sbin folder and repack the kernel.
Edit:this phone is kinda different,
it seems that the recovery and kernel partitions are the same
Figured it out
The zImage created after compilation process is actually the same, a kernel binary aka kernel.bin
I just had to rename the zImage to kernel.bin and add md5sum to the kernel.bin and pack it into a tarball to make it flashable via odin.
that can be done like this
Code:
md5sum -t kernel.bin >> kernel.bin
mv kernel.bin kernel.bin.md5
tar -cvf mykernel.tar kernel.bin.md5
As for packing the ramdisk into the kernel.bin
that can be done before compiling by editing the .config file or any config you gonna use
just have to add the path to the ramdisk at CONFIG_INITRAMFS_SOURCE="path to your ramdisk"
There's also a script to unpack the ramdisk from the kernel.bin, i'll attach it here
usage:
place the script at the same location of the kernel.bin
Code:
chmod +x unpack-initramfs.sh
bash unpack-initramfs.sh kernel.bin.md5
OR
/bin/sh unpack-initramfs.sh kernel.bin.md5
Hope this helped Others who were facing the same problem
how to repack it?
U all must be thinking that there are a hell lot of guides for this than what this guide is here for?
And the answer is that i have used almost all guides to extract our kernel for latest builds like cm7,cm9 etc but after using the guides present here on xda , after the last step i didn't get any directories instead got two files name ramdisk.gz and recovery.cpio now this guide will tell what to do next!!!
First of all download the perl scripts from
HERE
Now after download do this:
1. Create two directories and sub directories:
$ mkdir -p old-boot/ramdisk
$ mkdir new-boot
2. Copy the zImage file which ye have made to the "new-boot"
3. Put your old directory boot.img to the "old-boot"
4. Extract the directory bootimgutils.zip to "old-boot"
5. Split boot.img with the command:
$ cd old-boot
$ ./boot.img split_bootimg.pl
or
$ perl split_bootimg.pl boot.img
there will be an appearance of more or less like this (depending on the type of your device):
Page size: 2048 (0x00000800)
Kernel size: 1388548 (0x00153004)
Ramdisk size: 141 518 (0x000228ce)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend = 1
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
of the split will produce two files, namely boot.img-kernel and boot.img-ramdisk.gz
boot.img-kernel = kernel/zImage
boot.img-ramdisk = ramdisk
6. Now to edit the ramdisk then unpack the boot-img-ramdisk.gz with the following command :
$ cd ramdisk
$ gzip -dc ../boot.img-ramdisk.gz | cpio -i
after that u will have two files "ramdisk.gz" and "recovery.cpio"
7. Now go to ubuntu software center n download a application know as Ark
8. now right click on ramdisk.gz choose open with ark after that extract all the files
9.Now u will have all those directories n files u want!!!!
10. After editing repacking them by drag n drop method i.e. open ramdisk.gz file again using ark than select all those files u just extracted drag them and drop them on ramdisk.gz (opend in ark)
11.Now do the same with recovery.cpio if u want to edit something from it else skip
12 Now u have to repack all that stuff for that do
first repack ramdisk for that use
"find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz"
After that u have to repack boot.img for that use this
(if u have editing ramdisk)
$ ./mkbootimg --kernel /home/your user_id/new-boot/zImage --ramdisk /home/your user-id/old-boot/newramdisk.cpio.gz --base 0x80000000 --pagesize 2048 -o /home/user-id/new-boot/boot.img
(if u have not edited ramdisk that use)
$ ./mkbootimg --kernel /home/your user_id/new-boot/zImage --ramdisk /home/your user-id/old-boot/boot.img-ramdisk --base 0x80000000 --pagesize 2048 -o /home/user-id/new-boot/boot.img
Note: if u have made ur own zimage than place it in the "New-boot" folder n delete all other files
if u want repack the old zimage than rename the ur extracted "boot.img-kernel" to "zimage" n place in "New-boot" folder
Remeber u will have ur new boot.img in "New boot folder"
========================================================
Now for those who can't Download ark using Software center
1. download ark from this site
2. upack the ramdisk.gz/recovery.cpio using this command
ark --extract /home/your user-id/old-boot/ramdisk/ramdisk.gz
3. repack using
ark --add /home/your user-id/old-boot/ramdisk
it will promp the name of archive to add files to
choose the ramdisk.gz file!!!
The End
"HAVE A HAPPY KERNELING"
sachin sharma said:
U all must be thinking that there are a hell lot of guides for this than what this guide is here for?
And the answer is that i have used almost all guides to extract our kernel for latest builds like cm7,cm9 etc but after using the guides present here on xda , after the last step i didn't get any directories instead got two files name ramdisk.gz and recovery.cpio now this guide will tell what to do next!!!
First of all download the perl scripts from
HERE
Now after download do this:
1. Create two directories and sub directories:
$ mkdir -p old-boot/ramdisk
$ mkdir new-boot
2. Copy the zImage file which ye have made to the "new-boot"
3. Put your old directory boot.img to the "old-boot"
4. Extract the directory bootimgutils.zip to "old-boot"
5. Split boot.img with the command:
$ cd old-boot
$ ./boot.img split_bootimg.pl
or
$ perl split_bootimg.pl boot.img
there will be an appearance of more or less like this (depending on the type of your device):
Page size: 2048 (0x00000800)
Kernel size: 1388548 (0x00153004)
Ramdisk size: 141 518 (0x000228ce)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend = 1
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
of the split will produce two files, namely boot.img-kernel and boot.img-ramdisk.gz
boot.img-kernel = kernel/zImage
boot.img-ramdisk = ramdisk
6. Now to edit the ramdisk then unpack the boot-img-ramdisk.gz with the following command :
$ cd ramdisk
$ gzip -dc ../boot.img-ramdisk.gz | cpio -i
after that u will have two files "ramdisk.gz" and "recovery.cpio"
7. Now go to ubuntu software center n download a application know as Ark
8. now right click on ramdisk.gz choose open with ark after that extract all the files
9.Now u will have all those directories n files u want!!!!
10. After editing repacking them by drag n drop method i.e. open ramdisk.gz file again using ark than select all those files u just extracted drag them and drop them on ramdisk.gz (opend in ark)
11.Now do the same with recovery.cpio if u want to edit something from it else skip
12 Now u have to repack all that stuff for that do
first repack ramdisk for that use
"find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz"
After that u have to repack boot.img for that use this
(if u have editing ramdisk)
$ ./mkbootimg --kernel /home/your user_id/new-boot/zImage --ramdisk /home/your user-id/old-boot/newramdisk.cpio.gz --base 0x80000000 --pagesize 2048 -o /home/user-id/new-boot/boot.img
(if u have not edited ramdisk that use)
$ ./mkbootimg --kernel /home/your user_id/new-boot/zImage --ramdisk /home/your user-id/old-boot/boot.img-ramdisk --base 0x80000000 --pagesize 2048 -o /home/user-id/new-boot/boot.img
Note: if u have made ur own zimage than place it in the "New-boot" folder n delete all other files
if u want repack the old zimage than rename the ur extracted "boot.img-kernel" to "zimage" n place in "New-boot" folder
Remeber u will have ur new boot.img in "New boot folder"
========================================================
Now for those who can't Download ark using Software center
1. download ark from this site
2. upack the ramdisk.gz/recovery.cpio using this command
ark --extract /home/your user-id/old-boot/ramdisk/ramdisk.gz
3. repack using
ark --add /home/your user-id/old-boot/ramdisk
it will promp the name of archive to add files to
choose the ramdisk.gz file!!!
The End
"HAVE A HAPPY KERNELING"
Click to expand...
Click to collapse
It is use with Linux
Sent from my Droid X using XDA Premium HD app
I wish to quote all post too
Sent from my GT-I9003 using XDA
yes it is to be done in linux
loukalok said:
It is use with Linux
Sent from my Droid X using XDA Premium HD app
Click to expand...
Click to collapse
if possible plz remove quoted post
sachin sharma said:
U all must be thinking that there are a hell lot of guides for this than what this guide is here for?
And the answer is that i have used almost all guides to extract our kernel for latest builds like cm7,cm9 etc but after using the guides present here on xda , after the last step i didn't get any directories instead got two files name ramdisk.gz and recovery.cpio now this guide will tell what to do next!!!
First of all download the perl scripts from
HERE
Now after download do this:
1. Create two directories and sub directories:
$ mkdir -p old-boot/ramdisk
$ mkdir new-boot
2. Copy the zImage file which ye have made to the "new-boot"
3. Put your old directory boot.img to the "old-boot"
4. Extract the directory bootimgutils.zip to "old-boot"
5. Split boot.img with the command:
$ cd old-boot
$ ./boot.img split_bootimg.pl
or
$ perl split_bootimg.pl boot.img
there will be an appearance of more or less like this (depending on the type of your device):
Page size: 2048 (0x00000800)
Kernel size: 1388548 (0x00153004)
Ramdisk size: 141 518 (0x000228ce)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend = 1
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
of the split will produce two files, namely boot.img-kernel and boot.img-ramdisk.gz
boot.img-kernel = kernel/zImage
boot.img-ramdisk = ramdisk
6. Now to edit the ramdisk then unpack the boot-img-ramdisk.gz with the following command :
$ cd ramdisk
$ gzip -dc ../boot.img-ramdisk.gz | cpio -i
after that u will have two files "ramdisk.gz" and "recovery.cpio"
7. Now go to ubuntu software center n download a application know as Ark
8. now right click on ramdisk.gz choose open with ark after that extract all the files
9.Now u will have all those directories n files u want!!!!
10. After editing repacking them by drag n drop method i.e. open ramdisk.gz file again using ark than select all those files u just extracted drag them and drop them on ramdisk.gz (opend in ark)
11.Now do the same with recovery.cpio if u want to edit something from it else skip
12 Now u have to repack all that stuff for that do
first repack ramdisk for that use
"find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz"
After that u have to repack boot.img for that use this
(if u have editing ramdisk)
$ ./mkbootimg --kernel /home/your user_id/new-boot/zImage --ramdisk /home/your user-id/old-boot/newramdisk.cpio.gz --base 0x80000000 --pagesize 2048 -o /home/user-id/new-boot/boot.img
(if u have not edited ramdisk that use)
$ ./mkbootimg --kernel /home/your user_id/new-boot/zImage --ramdisk /home/your user-id/old-boot/boot.img-ramdisk --base 0x80000000 --pagesize 2048 -o /home/user-id/new-boot/boot.img
Note: if u have made ur own zimage than place it in the "New-boot" folder n delete all other files
if u want repack the old zimage than rename the ur extracted "boot.img-kernel" to "zimage" n place in "New-boot" folder
Remeber u will have ur new boot.img in "New boot folder"
========================================================
Now for those who can't Download ark using Software center
1. download ark from this site
2. upack the ramdisk.gz/recovery.cpio using this command
ark --extract /home/your user-id/old-boot/ramdisk/ramdisk.gz
3. repack using
ark --add /home/your user-id/old-boot/ramdisk
it will promp the name of archive to add files to
choose the ramdisk.gz file!!!
The End
"HAVE A HAPPY KERNELING"
Click to expand...
Click to collapse
Can I build a custom kernel for Android using any distros that is based on Ubuntu?
Silentkiller101197 said:
Can I build a custom kernel for Android using any distros that is based on Ubuntu?
Click to expand...
Click to collapse
Just above ur post plz read my post. Plz remove quoted post.
Silentkiller101197 said:
Can I build a custom kernel for Android using any distros that is based on Ubuntu?
Click to expand...
Click to collapse
Yes, you can use any *nix system
Few observations:
To make boot.img use:
Code:
mkbootimg --kernel zImage --ramdisk bootimg-ramdisk.cpio.gz --cmdline [URL="https://github.com/teamhacksung/android_device_samsung_galaxysl/blob/ics/BoardConfig.mk#L20"]"console=ttySAC2,115200 consoleblank=0"[/URL] --base [URL="https://github.com/teamhacksung/android_device_samsung_galaxysl/blob/ics/BoardConfig.mk#L21"]0x10000000[/URL] --pagesize [URL="https://github.com/teamhacksung/android_device_samsung_galaxysl/blob/ics/BoardConfig.mk#L19"]4096[/URL] --output boot.img
Use BBCODE to make the guide easier to read.
You don't necessarily need Ark, nearly every file archiver in linux can do that and there are also command line tools that are surely included in your linux distro (see the content of the script attached).
You need to sign up to download the scripts.
Are you sure about this?
Code:
./boot.img split_bootimg.pl
I think you swapped the names (I can't verify it, the reason is right above )
___
Here attached there's a script I made to easly unpack and repack CM kernels. It's based on this: http://forum.xda-developers.com/showthread.php?t=1242675
How to use it:
Place your boot.img in the same directory of the scripts and then run:
Code:
./unpack
It will extract the kernel and the compressed ramdisk.
Code:
./unpack -a
Same as above, but it will completely extract the ramdisk.
Code:
./repack
To make the new boot.img. It will also create kernel-updater.zip to flash the kernel from recovery.
If you put a directory named modules inside ./outfiles/ (it's created after you run ./unpack) with your self built modules (those that will go in /system/lib/modules/), they will be included in the updater zip.
Thanks to alfrix for the updated mkbootimg and the "teamhacksung styled" updater-script .
loSconosciuto said:
Few observations:
To make boot.img use:
Code:
mkbootimg --kernel zImage --ramdisk bootimg-ramdisk.cpio.gz --cmdline [URL="https://github.com/teamhacksung/android_device_samsung_galaxysl/blob/ics/BoardConfig.mk#L20"]"console=ttySAC2,115200 consoleblank=0"[/URL] --base [URL="https://github.com/teamhacksung/android_device_samsung_galaxysl/blob/ics/BoardConfig.mk#L21"]0x10000000[/URL] --pagesize [URL="https://github.com/teamhacksung/android_device_samsung_galaxysl/blob/ics/BoardConfig.mk#L19"]4096[/URL] --output boot.img
Use BBCODE to make the guide easier to read.
You don't necessarily need Ark, nearly every file archiver in linux can do that and there are also command line tools that are surely included in your linux distro (see the content of the script attached).
You need to sign up to download the scripts.
Are you sure about this?
Code:
./boot.img split_bootimg.pl
I think you swapped the names (I can't verify it, the reason is right above )
___
Here attached there's a script I made to easly unpack and repack CM kernels. It's based on this: http://forum.xda-developers.com/showthread.php?t=1242675
How to use it:
Place your boot.img in the same directory of the scripts and then run:
Code:
./unpack
It will extract the kernel and the compressed ramdisk.
Code:
./unpack -a
Same as above, but it will completely extract the ramdisk.
Code:
./repack
To make the new boot.img. It will also create kernel-updater.zip to flash the kernel from recovery.
If you put a directory named modules inside ./outfiles/ (it's created after you run ./unpack) with your self built modules (those that will go in /system/lib/modules/), they will be included in the updater zip.
Thanks to alfrix for the updated mkbootimg and the "teamhacksung styled" updater-script .
Click to expand...
Click to collapse
NO i tried most archives but they dont work they again give the same file i.e. ramdisk.gz
try it than say anything!!!
n there are many ways to unpack / repack anything so don't say that this is not neccessary or that is not neccessary
this thread is just about my preferred way!!!
if have ur own way than we will be happy to see ur guide thread!!
waiting for ur thread!!!
unpacking repacking can b easily done with Skin's unpack repack tools i use those best way to split kernels and ramdisk works like a charm
sachin sharma said:
NO i tried most archives but they dont work they again give the same file i.e. ramdisk.gz
try it than say anything!!!
n there are many ways to unpack / repack anything so don't say that this is not neccessary or that is not neccessary
this thread is just about my preferred way!!!
if have ur own way than we will be happy to see ur guide thread!!
waiting for ur thread!!!
Click to expand...
Click to collapse
I'm sorry, I didn't want to bother with my post.
I won't open a new thread, I was almost adding my scripts to skin's thread, but then I saw this one and it was about unpacking a CyanogenMod boot.img, so I added it here. There's no need to open a new thread in my opinion, because I don't have nothing more to say.
For the file archiver thing, I'm pretty sure of what I'm saying. Maybe you couldn't open it with other programs because you need to do it twice. The ramdisk is first gzip compressed and then cpio compressed. Maybe Ark does it twice automatically, but in linux there's not so much difference between a file archiver and another, they are all frontend and use the same tools almost always or maybe when you installed Ark other needed programs where automatically installed.
Regarding the mkbootimg arguments. I downloaded your tools and they confirmed what I wrote and I'm not surprised of this, because I'm using the same arguments amit/codeworkx/waleedq/dhiru used/are using in their kernels (as I linked you in my previous post).
Code:
Page size: 4096 (0x00001000)
Kernel size: 3429280 (0x003453a0)
Ramdisk size: 2957744 (0x002d21b0)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttySAC2,115200 consoleblank=0
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
It doesn't mean that you must use them, I've never said anything like this, but I'm pretty sure they all know better than me what they are doing, so I prefer to stick with those values and that's what I wanted to say in my previous post, but I admit that it sounded like "you are wrong, you must do this like this".
I really appreciate your effort, it was not easy for me at first to understand the differences between a stock boot.img and a CM one, so a guide like this would have been really helpful.
shriomman said:
unpacking repacking can b easily done with Skin's unpack repack tools i use those best way to split kernels and ramdisk works like a charm
Click to expand...
Click to collapse
So you are saying that with those tools you were able to unpack and repack the ramdisk changing things in it? Because I can't see this in his tools, so if they are working it simply means that you are not completely unpacking your boot.img, but simply splitting the kernel and the ramdisk.
loSconosciuto said:
I'm sorry, I didn't want to bother with my post.
I won't open a new thread, I was almost adding my scripts to skin's thread, but then I saw this one and it was about unpacking a CyanogenMod boot.img, so I added it here. There's no need to open a new thread in my opinion, because I don't have nothing more to say.
For the file archiver thing, I'm pretty sure of what I'm saying. Maybe you couldn't open it with other programs because you need to do it twice. The ramdisk is first gzip compressed and then cpio compressed. Maybe Ark does it twice automatically, but in linux there's not so much difference between a file archiver and another, they are all frontend and use the same tools almost always or maybe when you installed Ark other needed programs where automatically installed.
Regarding the mkbootimg arguments. I downloaded your tools and they confirmed what I wrote and I'm not surprised of this, because I'm using the same arguments amit/codeworkx/waleedq/dhiru used/are using in their kernels (as I linked you in my previous post).
Code:
Page size: 4096 (0x00001000)
Kernel size: 3429280 (0x003453a0)
Ramdisk size: 2957744 (0x002d21b0)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttySAC2,115200 consoleblank=0
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
It doesn't mean that you must use them, I've never said anything like this, but I'm pretty sure they all know better than me what they are doing, so I prefer to stick with those values and that's what I wanted to say in my previous post, but I admit that it sounded like "you are wrong, you must do this like this".
I really appreciate your effort, it was not easy for me at first to understand the differences between a stock boot.img and a CM one, so a guide like this would have been really helpful.
So you are saying that with those tools you were able to unpack and repack the ramdisk changing things in it? Because I can't see this in his tools, so if they are working it simply means that you are not completely unpacking your boot.img, but simply splitting the kernel and the ramdisk.
Click to expand...
Click to collapse
ok thnx for ur suggestions
but i have tried all the steps i have written
i successfully complete compiling kernel using this guide n will sill use it
if u dont want to use this guide or like another guide that its ur choice
have a good day!!!
So you are saying that with those tools you were able to unpack and repack the ramdisk changing things in it? Because I can't see this in his tools, so if they are working it simply means that you are not completely unpacking your boot.img, but simply splitting the kernel and the ramdisk.
Click to expand...
Click to collapse
Skin's tool splits kernel and ramdisk.... after that you can use gunzip from the command line to extract, modify and repack the cpio archive into the gz archive. Then again use skin's tool to repack the boot.img
Sent from my GT-I9003 using XDA
Do u guyz think that i shud delete this thread?
if so plz do tell me i will request mods to delete it!!!!!
Why?
Sent from my Droid X using XDA Premium HD app
loukalok said:
Why?
Sent from my Droid X using XDA Premium HD app
Click to expand...
Click to collapse
see all post above!!!!
all stating other ways to do the same!!!
sachin sharma said:
see all post above!!!!
all stating other ways to do the same!!!
Click to expand...
Click to collapse
Buddy u are taking this in wrong way. Nobody is saying that your guide is wrong or not useful. People are just sharing different way of unpacking & repacking kernel. If in future if any new member visit this thread then he can find different ways of kernel unpacking & repacking. Take people suggestion in positive way buddy We all really appreciate ur work buddy.
Guys can also refer to my thread which i created a long time back.
http://forum.xda-developers.com/showthread.php?t=1500889
sachin sharma said:
Do u guyz think that i shud delete this thread?
if so plz do tell me i will request mods to delete it!!!!!
Click to expand...
Click to collapse
We're just sharing buddy... chill...
Sent from my GT-I9003 using XDA
About
These two applets ( mkbootimg + unpackbootimg ) are used to pack and unpack any standard android kernel with 4096 / 2048 page size . Most of tools that pack and unpack boot.img files such as Dsixda kitchen , Kernel kitchen or. ... use these applets .
These applets were compiled only for X86 so we could only (un)pack boot.img in Windows or Ubuntu but I compiled and fixed these applets for Arm7 platform on android devices from Android sources. So you may pack and unpack boot.img on any android device !!
How to use
1- First download applets package
2- Unzip it and push two files in it to /system/bin or /system/xbin
3- Set their pemissions to 777 ( rwxrwxrwx )
For unpacking a kernel
* Assuming that you have boot.img in /sdcard
* Open terminal and type : [ this is just an example , you can change it ]
Code:
su
unpackbootimg -i /sdcard/boot.img -o /sdcard/ -p 4096
*You will have extracted boot.img at /sdcard
* Save ouput information that applets gives you at the end . you need them in future
For packing a kernel
* Copy ramdisk.gz , zimage , cmdline , pagesize , base you got from unpacking boot.img into /sdcard
* Open terminal and type :
Code:
su
mkbootimg --cmdline cmdline --kernel zimage --ramdisk ramdisk.gz --base base --pagesize pagesize -o boot.img
* You will have output ( boot.img ) at /sdcard/boot.img
Download
Download build 1 @ Uploadboy
* Initial build
Credits
* Alireza7991 - for fixing , improving and cross-compiling for arm^7
* Andrew Huang ( [email protected]) - for sources
* Android Open Source Project - for sources
This applet is under GPL 2.0
Using this is free but you have to ask me if you want to use this in your tools or ...
Reserved for OP
First!!! Another great job alireza!!
Sent from my GT-I9001 using Tapatalk 4 Beta
very nice tnx 4 u
-------
dash daset tala
its awesome :good:
tnx alireza
any way to use on armv6 ?
s27moto said:
any way to use on armv6 ?
Click to expand...
Click to collapse
Hi
Test it on arm^6 , if you couldnt tell me to compile it for arm^6
Great job Alireza just saw this topic while doing a quick browse through the i9001 forums. this may really become handy sometime
In Android:
I unpacked the file boot.img from within the K^Kernel_ICS_3.0_v2.0_Linaro-4.7.4_OC_UV_360MB_Signed.zip
next
# unpackbootimg -i *.img -o . -p 4096
# gunzip -d boot.img-ramdisk.gz
# gunzip: invalid gzip magic
I have a question.
Do boot.img-ramdisk.gz file is corrupted or protected?
ze7zez said:
In Android:
I unpacked the file boot.img from within the K^Kernel_ICS_3.0_v2.0_Linaro-4.7.4_OC_UV_360MB_Signed.zip
next
# unpackbootimg -i *.img -o . -p 4096
# gunzip -d boot.img-ramdisk.gz
# gunzip: invalid gzip magic
I have a question.
Do boot.img-ramdisk.gz file is corrupted or protected?
Click to expand...
Click to collapse
Hi
Ramdisk is compressed by two gzip and cpio methods . you have to use this ( I suggest to run this on ubuntu or cygwin :
Code:
cd ramdisk_place
gunzip < ramdisk.gz > ramdisk.cpio
cpio -i < ramdisk.cpio
alireza7991 said:
Download build 1 @ Uploadboy
Click to expand...
Click to collapse
Hi,
does someone still have the build somewhere? The download link is not working anymore.
Thanks.
frantisek.nesveda said:
Hi,
does someone still have the build somewhere? The download link is not working anymore.
Thanks.
Click to expand...
Click to collapse
Look here:
http://forum.xda-developers.com/showthread.php?t=2364447
alireza7991 said:
Look here:
http://forum.xda-developers.com/showthread.php?t=2364447
Click to expand...
Click to collapse
Already found that in the meantime, it turns out I had that thread open too, but I didn't realize they were two different threads, as they look nearly the same. But thanks
frantisek.nesveda said:
Already found that in the meantime, it turns out I had that thread open too, but I didn't realize they were two different threads, as they look nearly the same. But thanks
Click to expand...
Click to collapse
I think I made first one in SGS+ section then I found it should be in Android section and I made one there too .