I am trying to reassemble a boot.img a split up from my installed ROM.
This is what i did
Split the boot.img using split_bootimg.pl
Split the ramdisk using "gunzip -c ../ramdisk.gz | cpio -i" from within an empty folder
Then reassemble the ramdisk "find . | cpio -o -H newc | gzip > ../newramdisk.gz"
Reassemble the boot.img "mkbootimg --kernel kernel --ramdisk ramdisk.gz -o newboot.img"
An no, I made no changes at all to anything. I just split, reassemble and flash the image.
When I flash this newboot.img, my phone just stops at the alpharev boot image. adb is not yet started, so can't get any logcat either.
How in "someones name" do you successfully assemble a kernel and ramdisk image? All tutorials I can find, use this method, and I have tried them with different boot.img, different ways and such and nothing works.
EDIT:
I flash it using an update.zip with the fallowing updater-script content
Code:
mount("MTD", "system", "/system");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
unmount("/system");
Figured it out. HTC Desire needs "--base 0x20000000" added to the mkbootimg command.
So new question. Is it different from each phone? Because these tutorials are not phone variant specific, they talk in general.
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
Could someone point me to some instructions on how to unpack, modify, and repack a boot.blob out of a kernel?
I'm trying to update bryce's kernel to use Data2SD mod, and I'm following the instructions from here:
http://forum.xda-developers.com/showpost.php?p=29532041&postcount=15
However, I tried unpacking and repacking without even modifying anything and I just get bootlooped.
Read this: http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
Do you want to use the Data2SD mod with CM or with CROMI? For CROMI I posted a kernel with auto-detection of Data2SD in bryce's thread - only for CM you'd have to do it yourself.
Thanks for the help. I actually just figured out a different way right before seeing your reply. I use blobpack and blobunpack from BlobTools git, and abootimg installed from Ubuntu repository. This script has the extracted bryce kernel zip in a directory called result, so I overwrite his boot.blob with my new one.
Code:
#!/bin/bash
#Clean:
rm out boot.img new_boot.img boot2.blob linux_processed.zip -r
mkdir -p out
echo;echo "**** Unpacking boot.blob to boot.img";echo
cp result/boot.blob .
../linux/blobunpack boot.blob
mv boot.blob.LNX boot.img
cd out
# now in out
echo;echo "**** Unpacking boot.img";echo
abootimg -x ../boot.img
#zcat initramfs|cpio -tiv
echo;echo "**** Extracting initrd.img";echo
mkdir -p initramfs
cp initrd.img initramfs/initramfs.gz
mv initrd.img old_initrd.img
cd initramfs
# now in old/initramfs
gzip -d initramfs.gz
cpio -i < initramfs
echo;echo "**** Modifying boot information";echo
perl -pi -e 's/mmcblk0p2/mmcblk1p3/g' *
perl -pi -e 's/mmcblk0p8/mmcblk1p2/g' *
echo;echo "**** Recompressing initrd.img";echo
find | cpio -H newc -o | lzma -9 > ../initrd.img
cd ..
# now in out
echo;echo "**** Creating new_boot.img";echo
abootimg --create ../new_boot.img -f bootimg.cfg -k zImage -r initrd.img
cd ..
#now out of out
echo;echo "**** Pack boot2.blob";echo
../linux/blobpack boot2.blob LNX new_boot.img
cp boot2.blob result/boot.blob
cd result
echo;echo "**** Zip it all up";echo
zip ../linux_processed.zip * -r
cd ..
I am trying to get bryce's CM10.1 kernel working with Data2SD. I thought all I needed to do was change the mount commands in fstab.cardhu so that data (and I'm trying to do cache too) moved to external partitions.
Those perl pie commands in the middle were supposed to change internal data partition and internal cache partition into the external SD card partition 2 and 3, respectively. As far as I can tell, the changes were made correctly and the blob and zip were re-created, but it didn't work when I booted with the new blob.
Any ideas why it doesn't seem to have worked? Are there other changes I'm missing?
Edit:
Looks like my boot.blob is not being applied. I've tried both flashing the zip and dd'ing it to mmcblk0p4, but in both cases, I do not get the bootloader update screen on reboot, it just boots straight into my old settings. What am I missing?
Edit again:
Oops, I had stopped adding the signature on the blobs for some reason, looks like I'm off a few steps, because now I get bootloops again.
AW: [Q] Need help modifying boot blob
oblib__ said:
Thanks for the help. I actually just figured out a different way right before seeing your reply. I use blobpack and blobunpack from BlobTools git, and abootimg installed from Ubuntu repository. This script has the extracted bryce kernel zip in a directory called result, so I overwrite his boot.blob with my new one.
Code:
#!/bin/bash
#Clean:
rm out boot.img new_boot.img boot2.blob linux_processed.zip -r
mkdir -p out
echo;echo "**** Unpacking boot.blob to boot.img";echo
cp result/boot.blob .
../linux/blobunpack boot.blob
mv boot.blob.LNX boot.img
cd out
# now in out
echo;echo "**** Unpacking boot.img";echo
abootimg -x ../boot.img
#zcat initramfs|cpio -tiv
echo;echo "**** Extracting initrd.img";echo
mkdir -p initramfs
cp initrd.img initramfs/initramfs.gz
mv initrd.img old_initrd.img
cd initramfs
# now in old/initramfs
gzip -d initramfs.gz
cpio -i < initramfs
echo;echo "**** Modifying boot information";echo
perl -pi -e 's/mmcblk0p2/mmcblk1p3/g' *
perl -pi -e 's/mmcblk0p8/mmcblk1p2/g' *
echo;echo "**** Recompressing initrd.img";echo
find | cpio -H newc -o | lzma -9 > ../initrd.img
cd ..
# now in out
echo;echo "**** Creating new_boot.img";echo
abootimg --create ../new_boot.img -f bootimg.cfg -k zImage -r initrd.img
cd ..
#now out of out
echo;echo "**** Pack boot2.blob";echo
../linux/blobpack boot2.blob LNX new_boot.img
cp boot2.blob result/boot.blob
cd result
echo;echo "**** Zip it all up";echo
zip ../linux_processed.zip * -r
cd ..
I am trying to get bryce's CM10.1 kernel working with Data2SD. I thought all I needed to do was change the mount commands in fstab.cardhu so that data (and I'm trying to do cache too) moved to external partitions.
Those perl pie commands in the middle were supposed to change internal data partition and internal cache partition into the external SD card partition 2 and 3, respectively. As far as I can tell, the changes were made correctly and the blob and zip were re-created, but it didn't work when I booted with the new blob.
Any ideas why it doesn't seem to have worked? Are there other changes I'm missing?
Edit:
Looks like my boot.blob is not being applied. I've tried both flashing the zip and dd'ing it to mmcblk0p4, but in both cases, I do not get the bootloader update screen on reboot, it just boots straight into my old settings. What am I missing?
Edit again:
Oops, I had stopped adding the signature on the blobs for some reason, looks like I'm off a few steps, because now I get bootloops again.
Click to expand...
Click to collapse
I had a hard time getting this done too. I couldn't find working blob tools at first. So I ended up using blob tools for windows. They also sign them directly. But I am also running Ubuntu in a vm
Sent from my Nexus 4 using xda premium
Hello to everyone,
I'm trying to boot my Nexus 10 with another kind of kernel version,because I'm not interested to use the Android kernel,but the Ubuntu pure kernel. I've chosen to use the linux-kvm-arm kernel version 3.13 :
These are the commands that I have used :
git clone git://github.com/virtualopensystems/linux-kvm-arm.git
cd linux-kvm-arm
git checkout origin/chromebook-3.13 -b chromebook-3.13
curl http://www.virtualopensystems.com/downloads/guides/kvm_on_chromebook/config > .config
and then I've added these lines to the .config file :
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ASHMEM=y
CONFIG_ANDROID_LOGGER=y
CONFIG_ANDROID_PERSISTENT_RAM=y
CONFIG_ANDROID_RAM_CONSOLE=y
CONFIG_ANDROID_TIMED_OUTPUT=y
CONFIG_ANDROID_TIMED_GPIO is not set
CONFIG_ANDROID_LOW_MEMORY_KILLER=y
CONFIG_ANDROID_SWITCH is not set
CONFIG_ANDROID_INTF_ALARM is not set
CONFIG_FB_TILEBLITTING=y
CONFIG_PHONE is not set
CONFIG_USB_WPAN_HCD is not set
CONFIG_WIMAX_GDM72XX is not set
CONFIG_ARM_PLATFORM_DEVICES=y
CONFIG_ARM_CHROMEOS_FIRMWARE=y
CONFIG_CHROMEOS=y
CONFIG_CHROMEOS_VBC_BLK=y
CONFIG_CHROMEOS_VBC_EC=y
CONFIG_CHROMEOS_RAMOOPS_RAM_START=0x41f00000
CONFIG_CHROMEOS_RAMOOPS_RAM_SIZE=0x00100000
CONFIG_CHROMEOS_RAMOOPS_RECORD_SIZE=0x00020000
CONFIG_CHROMEOS_RAMOOPS_DUMP_OOPS=0x1
CONFIG_CLKDEV_LOOKUP=y
and then I did :
ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make uImage dtbs
from here I've followed the tutorial that I've found here :
http://forum.xda-developers.com/showthread.php?t=1981788
and here :
http://forum.xda-developers.com/showthread.php?t=1981788&page=2
mkdir -p newkernel
cd newkernel
wget -c https://dl.google.com/dl/android/aosp/mantaray-kot49h-factory-174ba74f.tgz
tar xvzf mantaray-kot49h-factory-174ba74f.tgz
cd mantaray-kot49h
unzip image-mantaray-kot49h.zip
wget -c http://android-serialport-api.googlecode.com/files/getramdisk.py
chmod +x getramdisk.py
./getramdisk.py boot.img --> ramdisk.img
wget -c http://android-serialport-api.googlecode.com/files/android_bootimg_tools.tar.gz
tar xvf android_bootimg_tools.tar.gz
./mkbootimg --kernel ../../linux-kvm-arm/arch/arm/boot/zImage --ramdisk ramdisk.img --cmdline bootimg.cfg -o new-boot.img
fastboot flash boot new-boot.img
I think that something is wrong here,because it is not able to boot....I see a black screen and nothing else happens...any ideas ?
Hello,
I am facing error when flashing image on Xperia Z3. I rooted the device using the link posted on "theunlockr.com"
Now, I am trying to flash a new image on the device. I am extracting the exisiting image from the device, modifying the init.rc file and repacking the image (myboot.img) and then flashing it using fastboot method. This is when it gives me this error.
When I flash the original image that I extracted, it works fine.
I tried following methods: -
1. Changing init.rc file and repacking the .img file and flashing it
When I extract initrd.img (using abootimg), it shows me only these files ( I usually find init.rc file when I extract initrd.img but not in this device, is this expected?): -
- XZ3-AdvStkKernel_DooMLoRD_ramdisk.gz
- logo.rle
- init (linking to sbin/init.sh)
- sbin/bootrec-device
- sbin/ramdisk-recovery-cwm.cpio
- sbin/busybox
- sbin/ramdisk.cpio
- sbin/init.sh
I extracted sbin/ramdisk.cpio file to get the init.rc file using the command: -
cpio -idmv < ramdisk.cpio
After modifying the init.rc file, I repacked the cpio file using the command: -
ls | cpio -ov > ramdisk.cpio
I made sure that none of the extra stuff was not there in the folder before repacking the cpio file.
Now that my ramdisk.cpio file is updated, I created new image using the command: -
find . | cpio -o -H newc | gzip -9 > ../newramdisk.cpio.gz
and created myboot.img using abootimg
When I flashed this image file, I get the "dtb not found" error
2. Second method that I tried was I simply unpacked the boot.img (original image) and repacked it using abootimg in to myboot.img without changing anything.
This also gives the same error.
It looks like there is some issue with the unpacking and repacking of the boot image.
Is there any other way to resolve this issue?
asurion.acc said:
Is there any other way to resolve this issue?
Click to expand...
Click to collapse
use this instruction and tools, but when you will build your boot.img, use this cmd line
Code:
./mkbootimg --base 0x00000000 --kernel zImage --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 --pagesize 2048 --cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0xb7 ehci-hcd.park=3 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y" --ramdisk ramdisk.cpio.gz --dt dt.img -o boot.img
with that instruction all work fine. I've tested many times
Thanks for replying to me.
I just want to modify init.rc file to add few lines. The only file that I see is ramdisk.cpio which contains init.rc. I unpacked it , modified it and repacked ramdisk.cpio. Instead of creating new dt.img, I directly flashed the new img file onto the device and that soft bricked the device. :crying: The steps that you suggested mentions creating a new kernel and creating a new dt.img. Do I need to do that even though I just need to modify just init.rc file?
At this point, I am just trying to unbrick the device using flash tool. I tried cwmrecovery but it did not work so trying flashing tool now. once its done, if it is necessary to create a new dt.img and new zImage using toolchains, I will use that method. Please let me know if you think that is the step that I am missing which caused the device to brick.
Thanks a lot.
UPDATE:
Device is unbricked.!
I just need to root it again and follow the steps that you mentioned. Please confirm if I need new ZImage and dt.img even if I just need to edit init.rc.
Thanks a lot.