Hello, can you help me?
How to decompile a kernel.elf?
How recompile one with only zImage, RPM.bin and ramdisk.
Not have bootimg.cfg
How extract boot.img from your phone? What is partition?
Helpppp !
Wrong section bro, this should be in Q&A
this is Q&A right ?
DanielFlorin said:
Hello, can you help me?
How to decompile a kernel.elf?
How recompile one with only zImage, RPM.bin and ramdisk.
Not have bootimg.cfg
How extract boot.img from your phone? What is partition?
Helpppp !
Click to expand...
Click to collapse
ask nsdcars5
Grimlock007 said:
ask nsdcars5
Click to expand...
Click to collapse
Who? Me?
@DanielFlorin You want to decompile or recompile? To decompile, use Flashtool. Go to Tools > Extractors > Elf. You'll get a ramdisk, a bootcmd and a boot image.
If you want to add CWM or TWRP, change the ramdisk with whatever kernel you want.
If you want to add overclock, build a new kernel boot image (you'll need Linux for that). Follow this guide: http://forum.xda-developers.com/showpost.php?p=50651922&postcount=46, but change msm7627a to msm7627a-perf everywhere in the guide.
Now, to recompile, rename the ramdisk file to ramdisk.cpio.gz and the boot image you compiled to zImage. Now on a Linux machine, get this script: http://forum.xda-developers.com/xperia-j-e/orig-development/tools-build-kernel-elf-ics-t2532724
(If you don't know how to, just run this command:
Code:
git clone <link>
where <link> is the GitHub link in the thread)
Related
I have unpack system.img (in my android phone) and add 1 app but i can not repack this. HELP ME PLZ :angel:
Hii there
this is stupid but our phones update.zips have only META-INF , System & zImage or boot.img & when i extract the tar i get cache.rfs,datafs.rfs,factoryfs,rfs,logo.png,modem. bin,& zImage
out of which i can open only logo.png on windows
& when i take a CWM BKP
i get
.android_secure.vfat.tar
boot.img
cache.rfs.tar
data.ext4.tar
nandroid.md5.md5
sd-ext.ext4.tar
system.ext4.tar
so how do i get only META-INF & System & boot or zImage from there
PS: I m a noob
Kalp99670 said:
Hii there
this is stupid but our phones update.zips have only META-INF , System & zImage or boot.img & when i extract the tar i get cache.rfs,datafs.rfs,factoryfs,rfs,logo.png,modem. bin,& zImage
out of which i can open only logo.png on windows
& when i take a CWM BKP
i get
.android_secure.vfat.tar
boot.img
cache.rfs.tar
data.ext4.tar
nandroid.md5.md5
sd-ext.ext4.tar
system.ext4.tar
so how do i get only META-INF & System & boot or zImage from there
PS: I m a noob
Click to expand...
Click to collapse
Same question. Any support?
I'm a noob as well. Every backup i take of my phone, comes as .tar files....
please help!
@op I thought you lost your phone!!
Sent from my GT-I5800 using Tapatalk 2
Kalp99670 said:
Hii there
this is stupid but our phones update.zips have only META-INF , System & zImage or boot.img & when i extract the tar i get cache.rfs,datafs.rfs,factoryfs,rfs,logo.png,modem. bin,& zImage
out of which i can open only logo.png on windows
& when i take a CWM BKP
i get
.android_secure.vfat.tar
boot.img
cache.rfs.tar
data.ext4.tar
nandroid.md5.md5
sd-ext.ext4.tar
system.ext4.tar
so how do i get only META-INF & System & boot or zImage from there
PS: I m a noob
Click to expand...
Click to collapse
you can't get update.zip this way....if you want flashable
zip you need to use rom cooker tool with pc and pull whole system to pc then rom cooker will make an zip as you want above...
da.cappo said:
Same question. Any support?
I'm a noob as well. Every backup i take of my phone, comes as .tar files....
please help!
Click to expand...
Click to collapse
you both can restore from your nand backups with Titanium Backup....try it it's great
Sent fom my S-II running >>SlimBean build 5 OFFICIAL << powered with DorimanX kernel v. >>9.16<<
thanks a lot!!!
da.cappo said:
thanks a lot!!!
Click to expand...
Click to collapse
anytime ma8
Sent fom my S-II running >>SlimBean build 5 OFFICIAL << powered with DorimanX kernel v. >>9.16<<
Friends Please Help Me To Repack Boot.img Please!! i Try Many But Didn't Found Zimage I Go To Port Diffrent Chipset Rom
here u go!
Kishan Mahadevwala said:
Friends Please Help Me To Repack Boot.img Please!! i Try Many But Didn't Found Zimage I Go To Port Diffrent Chipset Rom
Click to expand...
Click to collapse
follow this guide and use this tool. ( http://forum.xda-developers.com/showpost.php?p=54644719 )
I hope you will success.
don't forget to hit thanks.
Kishan Mahadevwala said:
Friends Please Help Me To Repack Boot.img Please!! i Try Many But Didn't Found Zimage I Go To Port Diffrent Chipset Rom
Click to expand...
Click to collapse
Mostly we want to update zImage in boot.img. so suggest you not to go for unpack and repack. just update your custom zImage into defualt boot.img by running this command:
#abootimg -u boot.img -k zImage.
Then try to flash this boot.img in your phone. If you are r changing initrd.img also then you can go for unpacking and repacking
but always take backup of your default boot.img, because if anything gone bad with this custom boot.img then your defuault will help to bring back your phone.
Find
I Already Find Thank You For Your Help I Already Do With Kitchen
Hey guys,
I am trying to repack the stock kernel as I have made a change to the ramdisk (ro.secure=0) I wasn't able to split the boot.img using split_bootimg.pl as it could not find android magic in the header so used flashtool to extract the kernel.elf file which gave me 3 files.
These were "kernel.elf.Image" "kernel.elf.ramdisk.gz" and "kernel.elf.3"
I have managed to extract and make the changes to the ramdisk and recompile it but im stuck at merging these 3 files back into the flashable kernel.elf file any help would be much appreciated
Sonic5317 said:
Hey guys,
I am trying to repack the stock kernel as I have made a change to the ramdisk (ro.secure=0) I wasn't able to split the boot.img using split_bootimg.pl as it could not find android magic in the header so used flashtool to extract the kernel.elf file which gave me 3 files.
These were "kernel.elf.Image" "kernel.elf.ramdisk.gz" and "kernel.elf.3"
I have managed to extract and make the changes to the ramdisk and recompile it but im stuck at merging these 3 files back into the flashable kernel.elf file any help would be much appreciated
Click to expand...
Click to collapse
Maybe you should PM @DooMLoRD
I'm sure he will help you. He will surely reply to your message when he'll have some time.
Hello,
I'm just getting into Android, and I've been messing around with boot.img with Magisk.
The boot.img that I'm specifically looking at is Pixel 6a.
I used `magiskboot unpack boot.img`, but I only got a kernel file.
Now, I'm wondering where the ramdisk.cpio. From what I read, ramdisk determines what to mount and whatnot.
Even without a ramdisk, I can fastboot flash boot boot.img it to my device and it will still work.
If there is no ramdisk in boot.img, then how does the device know what to mount or what the file hierarchy is when I flash it?
If the stock boot.img doesn't have a ramdisk, does not mean I have to generate my own?
Thanks!
init is on system, no ramdisk required.
https://source.android.com/docs/core/architecture/partitions/system-as-root#sar-partitioning
alecxs said:
init is on system, no ramdisk required.
https://source.android.com/docs/core/architecture/partitions/system-as-root#sar-partitioning
Click to expand...
Click to collapse
does that mean if I do include ramdisk.cpio, it overrides the one on system?
Yes, if you modify the kernel so ramdisk is extracted and processed (that's what Magisk does)
alecxs said:
Yes, if you modify the kernel so ramdisk is extracted and processed (that's what Magisk does)
Click to expand...
Click to collapse
Thank you so much for the link. I read up on it, and as you said, boot.img just carries a kernel file and ramdisk is in system.img.
It looks like you can also unpack, modify, and repack system.img and flash it onto pixel devices, so do you know why Magisk decided to create ramdisk.cpio and repack it into boot.img when it could have modified system.img? Is it because boot.img has a kernel file?
Thanks
Magisk also mods the DTB from "skip_initramfs" to "want_initramfs".
drunk_santa said:
It looks like you can also unpack, modify, and repack system.img and flash it onto pixel devices, so do you know why Magisk decided to create ramdisk.cpio and repack it into boot.img when it could have modified system.img?
Click to expand...
Click to collapse
Because Magisk is systemless-root method
https://topjohnwu.github.io/Magisk/boot.html