Hey guys!
I finally did it and downloaded the liquid smooth's and device's repos. But now when I type 'make otapackage -j4 -i' after 4 hours(!) of compiling it stucks at a certain file and then I can't move the mouse, type someting or anything, Ubuntu 14.04 freezes and I have to press the power button to force the PC close.
Please anyone help? I'm posting a picture with my PC:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lefterios said:
Please anyone help? I'm posting a picture with my PC:
Click to expand...
Click to collapse
You might have a corrupted gvfsd-metadata. Do pkill gvfsd-metadata, rm -rf ~/.local/share/gvfs-metadata.
And compiling time depends on the computer specs and can easily take more than 3 hours on an average core processor(i3).
MasterAwesome said:
You might have a corrupted gvfsd-metadata. Do pkill gvfsd-metadata, rm -rf ~/.local/share/gvfs-metadata.
And compiling time depends on the computer specs and can easily take more than 3 hours on an average core processor(i3).
Click to expand...
Click to collapse
Okay I'll try it today I'll report if this worked.
I have an Intel core i5 with 3GB Ram and I think that it's quite long...
But thanks anyway!
Okay so I compiled again and now no freezes. Unfortunately however when it was going to end an error occured:
The weird thing is that all folders like system, recovery etc are there
Can you help?
lefterios said:
Okay so I compiled again and now no freezes. Unfortunately however when it was going to end an error occured:
The weird thing is that all folders like system, recovery etc are there
Can you help?
Click to expand...
Click to collapse
Can you paste the error here? With screenshots I can really help you. Just paste the error like this:
Code:
Error
GeekyDroid said:
Can you paste the error here? With screenshots I can really help you. Just paste the error like this:
Code:
Error
Click to expand...
Click to collapse
Ok sure:
Code:
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files",line 1123, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files",line 1091, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files",line 539, in WriteFullOTAPackage(OPTIONS.input_tmp,"BOOT")
File "/home/lefteris/working/build/tools/releasetools/common.py", line 361, in GetBootableImage
info_dict))
File "/home/lefteris/working/build/tools/releasetools/common.py", line 836, in __init__
self.size = len(data)
TypeError: object of type 'NoneType' has no len()
make: [/home/lefteris/working/out/target/product/golden/liquid_golden-ota-userdebug.lefteris.zip] Error 1 (ignored)
Sorry I may have made a mistake because I copied from the image. If you want full changelog you can right-click the image and press 'open image in a new tab'
lefterios said:
Ok sure:
Code:
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files",line 1123, in
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files",line 1091, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files",line 539, in WriteFullOTAPackage(OPTIONS.input_tmp,"BOOT")
File "/home/lefteris/working/build/tools/releasetools/common.py", line 361, in GetBootableImage
info_dict))
File "/home/lefteris/working/build/tools/releasetools/common.py", line 836, in __init__
self.size = len(data)
TypeError: object of type 'NoneType' has no len()
make: [/home/lefteris/working/out/target/product/golden/liquid_golden-ota-userdebug.lefteris.zip] Error 1 (ignored)
Sorry I may have made a mistake because I copied from the image. If you want full changelog you can right-click the image and press 'open image in a new tab'
Click to expand...
Click to collapse
Did you type make -i (ignoring the errors?) If you did that, the zImage might not have been built because of errors and the boot image is not built due to this. It might also be because of fs size constraints. In your out folder of your device, check if you have the kernel and the root directory.
And in the py file the typecasting might have been done wrong since it says "object of type 'NoneType' has no len()"
MasterAwesome said:
Did you type make -i (ignoring the errors?) If you did that, the zImage might not have been built because of errors and the boot image is not built due to this. It might also be because of fs size constraints. In your out folder of your device, check if you have the kernel and the root directory.
And in the py file the typecasting might have been done wrong since it says "object of type 'NoneType' has no len()"
Click to expand...
Click to collapse
Ιn the out folder I have the root directory but not the kernel... And yes I typed -i because there were many errors and I couldn't build the ROM. So what do I have to do now? Please note that I'm beginner and I don't know very much for ROM development...
lefterios said:
Ιn the out folder I have the root directory but not the kernel... And yes I typed -i because there were many errors and I couldn't build the ROM. So what do I have to do now? Please note that I'm beginner and I don't know very much for ROM development...
Click to expand...
Click to collapse
As I said the error must have been in the kernel and ignoring that will not build the kernel, you will have to fix it manually the errors you face in the kernel building stage, post it here.
MasterAwesome said:
As I said the error must have been in the kernel and ignoring that will not build the kernel, you will have to fix it manually the errors you face in the kernel building stage, post it here.
Click to expand...
Click to collapse
Sorry I don't know how to do that :crying:
A question: Can I build the ROM with existing kernel image(boot.img) from another ROM? I don't make changes to kernel...
lefterios said:
Sorry I don't know how to do that :crying:
A question: Can I build the ROM with existing kernel image(boot.img) from another ROM? I don't make changes to kernel...
Click to expand...
Click to collapse
Yes you can, in the boardconfig.mk add a flag
TARGET_PREBUILT_KERNEL := $(DEVICE_FOLDER)/prebuilt/kernel
Be sure to define the DEVICE_FOLDER at the top of the make file.
Although its deprecated. But it'll work in your case if the kernel is a kitkat kernel.
MasterAwesome said:
Yes you can, in the boardconfig.mk add a flag
TARGET_PREBUILT_KERNEL := $(DEVICE_FOLDER)/prebuilt/kernel
Be sure to define the DEVICE_FOLDER at the top of the make file.
Although its deprecated. But it'll work in your case if the kernel is a kitkat kernel.
Click to expand...
Click to collapse
I tried it but again no luck What am I doing wrong? It produces all files and folders except kernel!
lefterios said:
I tried it but again no luck What am I doing wrong? It produces all files and folders except kernel!
Click to expand...
Click to collapse
I believe you forgot to remove the kernel directory flags from the board config.mk. attach it here.
MasterAwesome said:
I believe you forgot to remove the kernel directory flags from the board config.mk. attach it here.
Click to expand...
Click to collapse
Ok I attached the file found under ~/working/device/samsung/golden. I hope you can help me. I created the folder prebuilt and I put there a zImage. Is that right?
lefterios said:
Ok I attached the file found under ~/working/device/samsung/golden. I hope you can help me. I created the folder prebuilt and I put there a zImage. Is that right?
Click to expand...
Click to collapse
You named it as zImage and specified it as prebuilt/kernel. It should be $(DEVICE_FOLDER)/prebuilt/zImage.
MasterAwesome said:
You named it as zImage and specified it as prebuilt/kernel. It should be $(DEVICE_FOLDER)/prebuilt/zImage.
Click to expand...
Click to collapse
Firtsly is everything alright with the boardconfig file? So should I rename the file to zImage and that's it? And also which difference there is between kernel and zImage and which should I use?
lefterios said:
Firtsly is everything alright with the boardconfig file? So should I rename the file to zImage and that's it? And also which difference there is between kernel and zImage and which should I use?
Click to expand...
Click to collapse
Everything else seems fine... The path must be the path to your kernel or what ever you renamed it as.
I'd recommend you try and compile the kernel alone to check if it work
MasterAwesome said:
Everything else seems fine... The path must be the path to your kernel or what ever you renamed it as.
I'd recommend you try and compile the kernel alone to check if it work
Click to expand...
Click to collapse
I compiled the kernel alone and it didn't show any error. It made a zImage file successfully. So where is the problem?
lefterios said:
I compiled the kernel alone and it didn't show any error. It made a zImage file successfully. So where is the problem?
Click to expand...
Click to collapse
Trying doing a "make" without the -i and see where the build stops.
Related
Hello dev community
I am currently trying to build my own kernel / zImage, but for some reason it doesn't work, when I flash my zImage the SGS2 crashs at the bootscreen with the yellow triangle.
Not even the battery animation when charging while off works anymore *lol*
Here is what I did so far:
extracted a stock initramfs from a samsung stock kernel
got the Samsung kernel sources and extracted on my PC
got the codesourcery toolchain and installed it
edited the path to the toolchain into kernel/Makefile
ran
make c1_rev02_defconfig (as stated in the readme.txt of the src download)
set the path to the extracted iniramfs files in the config
ran
make zImage
It eventually tells me "kernel zImage ready at ...."
padded with 0x00s to the 8MiB size, .tar'ed and flashed via Odin
But it doesn't boot.
When I throw my zImage at the initramfs extractor script, I get the proper initramfs files dumped, so they seem to be fine.
Searched around this forums for two days now, found a few "zImage repacker scripts" but none work or clear up any of my questions.
Any hints on what I missed or did wrong are appreciated
And while we're at it, another question:
At new FW builds, does the actual kernel itself change too, or is it only changes in the initramfs? Because there is only one set of sources from Samsung.... so I assume the actual kernel stays the same and using the initramfs of the targetted FW will suufice?
Why did you pad it up to 8mb?
also, when setting the initramfs source, did you set these to you uid you are compiling with?
CONFIG_INITRAMFS_ROOT_UID=1000
CONFIG_INITRAMFS_ROOT_GID=1000
Hm, padded to 8MB as all kernels are (padded to) 8MB, aren't they?
Tried flashing an unpadded version too, still no go.
And yes, UID and GID are set to the ones my user is running as....
Close to the end of the compiler run, I get a "found 14 module section missmatches" kind of message - could that have something to do with my zImage not working? And how would I fix that?
Oh c'mon, it can't be that hard, so many people are making their own zImages.... what am I missing here.... :-/
First of all, you cant just use a stock initramfs image, shove it into another kernel and expect it to work. There are kernel modules in there which need to be updated first before you do the last "make zImage".
Try this:
0. make sure your config is correct. you should copy c1_rev02_defconfig from inside arm/ to source_root/.config and do a "make oldconfig". Then adjust your configs as necessary ("make menuconfig" etc)
1. "make modules"
2. "INSTALL_MOD_PATH=~ make modules_install"
3. goto your home dir and pick out the modules and put them into the path of your initramfs files (/lib)
4. finally, make zImage.
5. theres no need to pad to 8mb. that is an urban legend
OK, did all that.... still no go.... :-/
Try this script:
Code:
#!/bin/bash
# Set Default Path
TOP_DIR=$PWD
KERNEL_PATH=/home/neophyte-x360/kernel/GALAXYS2/2.6.35.7
# TODO: Set toolchain and root filesystem path
TAR_NAME=zImage.tar
TOOLCHAIN="/home/neophyte-x360/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-"
# TOOLCHAIN="/home/neophyte-x360/toolchain/bin/arm-none-eabi-"
ROOTFS_PATH="/home/neophyte-x360/kernel/GALAXYS2/initramfs-SGS2"
echo "Cleaning latest build"
make ARCH=arm CROSS_COMPILE=$TOOLCHAIN -j`grep 'processor' /proc/cpuinfo | wc -l` clean
cp -f $KERNEL_PATH/arch/arm/configs/c1_rev02_defconfig $KERNEL_PATH/.config
make -j4 -C $KERNEL_PATH oldconfig || exit -1
make -j4 -C $KERNEL_PATH ARCH=arm CROSS_COMPILE=$TOOLCHAIN || exit -1
cp drivers/bluetooth/bthid/bthid.ko $ROOTFS_PATH/lib/modules/
cp drivers/net/wireless/bcm4330/dhd.ko $ROOTFS_PATH/lib/modules/
cp drivers/samsung/j4fs/j4fs.ko $ROOTFS_PATH/lib/modules/
cp drivers/samsung/fm_si4709/Si4709_driver.ko $ROOTFS_PATH/lib/modules/
cp drivers/scsi/scsi_wait_scan.ko $ROOTFS_PATH/lib/modules/
cp drivers/samsung/vibetonz/vibrator.ko $ROOTFS_PATH/lib/modules/
make -j4 -C $KERNEL_PATH ARCH=arm CROSS_COMPILE=$TOOLCHAIN || exit -1
# Copy Kernel Image
cp -f $KERNEL_PATH/arch/arm/boot/zImage .
cd arch/arm/boot
tar cf $KERNEL_PATH/arch/arm/boot/$TAR_NAME zImage && ls -lh $TAR_NAME
And try with other initramfs, maybe could be this.
PD: I forgot that with my script you have to select your initramfs inside .config
Very interesting thread!
Im about to study computer science and software engineering for 3 years in august.
Hoping/wishing/expecting to get into this eventually!
put this in your build script:-
export LOCALVERSION="-I9100XWKE7-CL215725"
this is just an example set its value to the same as the initramfs you used, e.g. the magicver in the modules.
sounds like your initramfs are incomplete...or more likely your toolchain is not quite right. even without recovery, your zimage should be 6-7mb...(no padding, and there is no need to)
OK, done a clean rebuild, taking care of everything you guys said:
made new initramfs dump from a stock zImage
make mrproper
make c1_rev02_defconfig
make menuconfig - set the paths/prefixes for toolchain, localversion and initramfs (also set my users UID and GID for mapping to UID/GUI 0) there, left everything else untouched and at defaults
make
copied the freshly built modules into my initramfs dir (checked with a hexeditor for the proper versionmagic, looks OK)
make zImage
resulting zImake size: ~5.7MB and no go, still doesn't boot.
I'll try now with another toolchain (using the last one available for d/l so far, just got the 2009-something one mentioned in the sources readme and going to try to use that one now) as well as different initramfs dumper....
I have not much hope this will change the outcome, but it's at least worth a try....
// EDIT (a few hours later xD)
SUCCESS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(anyone knows what the #9 is? where it comes from, what it says?)
I *finally* managed to get a completely self built kernel to boot \o/
So, what was it that played showstopper the whole time: THE TOOLCHAIN!
I had the latest (2011-something) version of the CodeSourcery toolchain installed - that does not seem to be a good idea.
Did exactely what I did before, but now with the 2009q3 version installed (like the readme of the source states) - and tadaa, it works!
// EDIT 2
Figured out the #9 as well, it's the build number / version; how many times I ran "make" since the last "make mrproper"
LET THE MODDING BEGIN (now the fun starts)
Glad to see someone's happy. I'm also trying to compile a kernel from source. However, mine's an I9100G. Managed to compile, flash and boot up my phone, but battery status and Wifi don't work. After looking through the dmesg log, apparently the battery driver is not being initialised. I wonder if anyone can help me? Maybe someone with knowledge of the OMAP platform?
aidfarh said:
Glad to see someone's happy. I'm also trying to compile a kernel from source. However, mine's an I9100G. Managed to compile, flash and boot up my phone, but battery status and Wifi don't work. After looking through the dmesg log, apparently the battery driver is not being initialised. I wonder if anyone can help me? Maybe someone with knowledge of the OMAP platform?
Click to expand...
Click to collapse
You can give me initramfs?
I cqn give it a try.
Sent from my GT-I9100
How to
HellcatDroid said:
Hello dev community
I am currently trying to build my own kernel / zImage, but for some reason it doesn't work, when I flash my zImage the SGS2 crashs at the bootscreen with the yellow triangle.
Not even the battery animation when charging while off works anymore *lol*
Click to expand...
Click to collapse
Could you please give a few mn to write a min How To? I would like to build my own, but as a noob, I am a litle lost in all the info I gathered.
It would be nice to profit from your experience.
Or maybe do you have any good links?
TY
netchip said:
You can give me initramfs?
I cqn give it a try.
Sent from my GT-I9100
Click to expand...
Click to collapse
Well, if you think it can help, here's the download link for my initramfs:
http://dl.dropbox.com/u/13796854/initramfs.zip
It's for an I9100G, though. Do you have one to test with?
aidfarh said:
Well, if you think it can help, here's the download link for my initramfs:
http://dl.dropbox.com/u/13796854/initramfs.zip
It's for an I9100G, though. Do you have one to test with?
Click to expand...
Click to collapse
I haven't one for testing.
I am a kernel developer here for SGS2, check the development part.
We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
cd /boot
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5-Now, unpack your boot.img by running the following command:
./extractboot boot.img
Click to expand...
Click to collapse
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide
So.. NEXT step to change a kernel logo is here
Requiredment
1-a picture what are u like to look into the 1st boot screen (kernel logo) (make sure it size/resolution same your device resolution)
2-boot_screen_logo_creation_package.rar
3-some infos and knowledges here
4-window machine like i explained on 1st post
My quick guide
-extract the tool.rar
-move extracted files into new folder (name it 'rle' folder without quote)
-move into cygwin folder (to make it easy to follow my simple guide)
-copy your own logo.png (a picture u want to use on a kernel) into same rle folder
(for 4 steps above it shold look like tis)
-now launch cygwin.bat
cd /rle
Click to expand...
Click to collapse
./convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
Ah...my mistake..don't forget to move/copy/replace new logo.rle into
C/cygwin/boot/out/ramdisk/here
if you done good...follow next step on next post (to repack your moded kernel)
Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
./packboot
Click to expand...
Click to collapse
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do
I need this for extra (extra thanks..)
(may U?)
nelikp said:
I need this for extra (extra thanks..)
(may U?)
Click to expand...
Click to collapse
ähem lol thats not needed...?
jader13254 said:
ähem lol thats not needed...?
Click to expand...
Click to collapse
hahahahaa
Happy theme-ing
Thanks for the tutorial, I think I'll try this at the weekend just for fun. :good:
Nice tutorial, almost n00b proof. But I use kernel kitchen instead of cygwin. ?
Sent from my LT15i using xda premium
datagubben said:
Nice tutorial, almost n00b proof. But I use kernel kitchen instead of cygwin. ?
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
Seriously ??? Whats This?
$ ./extractboot boot_9.587c.IMG
./extractboot: ./split_bootimg.pl: /usr/bin/perl: bad interpreter: Permission denied
./extractboot: line 17: cpio: command not found
gzip: ../../boot.img-ramdisk.gz: No such file or directory
Click to expand...
Click to collapse
YeoZy96 said:
Seriously ??? Whats This?
Click to expand...
Click to collapse
What kernel? Give me the link kernel
YeoZy96 said:
Seriously ??? Whats This?
Click to expand...
Click to collapse
What kernel? Give me the link kernel
nelikp said:
What kernel? Give me the link kernel
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=31910339&postcount=2304
nelikp said:
We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
5-Now, unpack your boot.img by running the following command:
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide
Click to expand...
Click to collapse
nice tutorial...how about working with ftf (kernel.ftf) can u make tutorial?
YeoZy96 said:
https://forum.xda-developers.com/showpost.php?p=31910339&postcount=2304
Click to expand...
Click to collapse
I can't pm u..
ad me
Android Magic Header ?
Code:
$ ./extractboot boot.img
Android Magic not found in ./boot.img. Giving up.
gzip: ../../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
Rom
Doesn't work for me :/ Can everyone make it from this kernel : forum.xda-developers.com/attachment.php?attachmentid=916452&d=1330029354 The ICS (SONY) logo? please
just want change to the old SE boot logo
nelikp said:
What kernel? Give me the link kernel
Click to expand...
Click to collapse
how to get boot.img from kernel
---------- Post added at 07:46 PM ---------- Previous post was at 07:40 PM ----------
anishkrsuman said:
how to get boot.img from kernel
Click to expand...
Click to collapse
plz make me clear how to get boot.img from any kernel and after that where to put them??
On windows using cygwin:good:
---------- Post added at 07:52 PM ---------- Previous post was at 07:46 PM ----------
nelikp said:
What kernel? Give me the link kernel
Click to expand...
Click to collapse
plz make this kernel with sony ericsson default logo
http://minicm.googlecode.com/files/E15_nAa-14_2.6.29.6-nAa-14.ftf
The main thing here is how you can successfully install cygwin . I see a lot of people get stuck with this software. You can follow the guide by jimbo77 (as mention in first post) for some error.
I think no one can do help for changing kernel logo.Because it's not right for kernel's owner
YeoZy96 said:
Seriously ??? Whats This?
Click to expand...
Click to collapse
install perl & cpio package in cygwin installer & run as admin
We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
cd /boot
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5-Now, unpack your boot.img by running the following command:
./extractboot boot.img
Click to expand...
Click to collapse
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide
So.. NEXT step to change a kernel logo is here
Requiredment
1-a picture what are u like to look into the 1st boot screen (kernel logo) (make sure it size/resolution same your device resolution)
2-boot_screen_logo_creation_package.rar
3-some infos and knowledges here
4-window machine like i explained on 1st post
My quick guide
-extract the tool.rar
-move extracted files into new folder (name it 'rle' folder without quote)
-move into cygwin folder (to make it easy to follow my simple guide)
-copy your own logo.png (a picture u want to use on a kernel) into same rle folder
(for 4 steps above it shold look like tis)
-now launch cygwin.bat
cd /rle
Click to expand...
Click to collapse
./convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
Ah...my mistake..don't forget to move/copy/replace new logo.rle into
C/cygwin/boot/out/ramdisk/here
if you done good...follow next step on next post (to repack your moded kernel)
Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
./packboot
Click to expand...
Click to collapse
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do
I need this for an extra (extra thanks maybe)
(may U?)
great work man
:laugh:
i got this eror what to do?
Theliakos said:
i got this eror what to do?
Click to expand...
Click to collapse
run as administrator
Thanks for this tutorial. But how about when the ramdisk is lzma? I tried changing commands from extractboot and packboot (from "gzip.... " to "lzma........." ) everything works well, the phone boots, but I don't have recovery mode anymore. In rest the kernel is perfect. But I need recovery mode, for installing things. I guess changing the command "gzip - or gunzip, whatever" to "lzma" is not all I have to modify. Any chance for a help?:crying:
LaShto34 said:
Thanks for this tutorial. But how about when the ramdisk is lzma? I tried changing commands from extractboot and packboot (from "gzip.... " to "lzma........." ) everything works well, the phone boots, but I don't have recovery mode anymore. In rest the kernel is perfect. But I need recovery mode, for installing things. I guess changing the command "gzip - or gunzip, whatever" to "lzma" is not all I have to modify. Any chance for a help?:crying:
Click to expand...
Click to collapse
same problem
Nice and awesome tutorial brother! :good::fingers-crossed::highfive:
Deleted
yamin8000 said:
same problem
Click to expand...
Click to collapse
Finally. I made it. For lzma ramdisks use this http://forum.xda-developers.com/showthread.php?t=1659584&highlight=lzma but I modified it to something like this (see attachment). All credits must go to the original developer, I only changed some "gzip -c" word to "lzma -dc". And I managed to modify any kernel with lzma compressed ramdisk. :good:
LaShto34 said:
Finally. I made it. For lzma ramdisks use this http://forum.xda-developers.com/showthread.php?t=1659584&highlight=lzma but I modified it to something like this (see attachment). All credits must go to the original developer, I only changed some "gzip -c" word to "lzma -dc". And I managed to modify any kernel with lzma compressed ramdisk. :good:
Click to expand...
Click to collapse
So all the step is the same with the one on the OP except we need to change gzip -c into lzma -dc?
Sent from my ST15i using xda premium
Singgih4050 said:
So all the step is the same with the one on the OP except we need to change gzip -c into lzma -dc?
Click to expand...
Click to collapse
Yes, but unfortunately it doesn't work with this tutorial (at least for me, because I lost recovery - In rest the kernel behaves normal, but we all need cwm recovery). It only fully works (again, for me) with that modified version of android kernel kitchen 0.3.1.
Will this method work with LOCKED bootloader?
mine can't be unlocked
No it will not working because this is tutorial about to change a kerenl bootlogo (Sony Ericsson) word on startup phone..
Your phone cant be unlocked and no chance to change/flash custom kernel with custom bootlogo.
GSUKeitarou said:
Will this method work with LOCKED bootloader?
mine can't be unlocked
Click to expand...
Click to collapse
---------- Post added at 03:46 AM ---------- Previous post was at 03:45 AM ----------
Good job mate :good:
works for me after i edit bootlogo for Xperia play kernel by doomlord and i managed to enter cwm
LaShto34 said:
Finally. I made it. For lzma ramdisks use this http://forum.xda-developers.com/showthread.php?t=1659584&highlight=lzma but I modified it to something like this (see attachment). All credits must go to the original developer, I only changed some "gzip -c" word to "lzma -dc". And I managed to modify any kernel with lzma compressed ramdisk. :good:
Click to expand...
Click to collapse
thanks for the guide:fingers-crossed:
Al ok but phone not booting after bootlogo changed!!!!
Code:
[email protected] /boot
$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 5920144 (0x005a5590)
Ramdisk size: 4617107 (0x00467393)
Second size: 0 (0x00000000)
Board name:
Command line: androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-h
cd.park=3 vmalloc=400M androidboot.emmc=true
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
13874 blocks
[email protected] /boot
$ ./packboot
Using base address 0x80200000
Using command line 'androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F
ehci-hcd.park=3 vmalloc=400M androidboot.emmc=true'
[email protected] /boot
$
Whas is my erros?? My phone can't booting after flash boot.img (new), i don't change bootlogo, only unpack and repack .Thank for help
But now WORK when i change with android kitchen =))
I've been getting this error. I'm already run as administrator. What's the problem?
Hello, everyone!
This is intended for everyone who want to modify kernels they are using. Since I could not find tutorials on how to repack kernels for our Novathor devices, I decided to write my own tutorial. Maybe there are other ways, but this is how I do it and it is 100% failsafe. I took transcendence CM 1.1.6 kernel as an example in this tutorial. So, let's start!
Requirements:
- Flashtool
- Linux (Ubuntu preferable), you can also use builduntu if you don't want to install linux to your hard drive
- Files provided in attachment
- Not to close terminal in linux at any price
- Brains
STEP 1: Unpacking
First of all, you want to unpack the kernel. This is the easiest one.
Fire up Flashtool, select tools/extractors/elf
Easy, right? Now, click on those three dots and find kernel you wish to modify. Kernel MUST have .elf extension for this to work, so if you have "boot.img" at you disposal, please rename it to "kernel.elf" (without quotes). Once you loaded your kernel, just click unpack. Do not close Flashtool yet. In it you will see logs that kernel is unpacked. Please take a screenshot of that window as we will need that report later. Screenshot should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After you have saved screenshot somewhere, look in the folder where your kernel is, and you will find two or three files additional files, sometimes even four, depending on the kernel itself. They should be named this way:
kernel.elf.ramdisk.gz (very rarely, this file may be called kernel.elf.2)
kernel.elf.Image (sometimes this file may be called kernel.elf.1)
kernel.elf.3
kernel.elf.cmd
It depends on the kernel how much files you're going to have. Now, please rename them, so that you delete kernel.elf from names. Now they should be named like this:
ramdisk.gz
Image
3
cmd
Bolded files are needed for our modifications. Now to the next step!
STEP 2: Modifying
Now that we have needed files at our disposal, it's time to do the modifications.
Image file
This file is zImage of the kernel. This is the core of the kernel, where CPU frequencies, drivers, governors, etc. are stored. This file you cannot really modify but if you have built your own specific zImage, you can replace it. I don't recommend touching this file unless you know what you're doing (in other words, unless you're developer or programmer).
So, noobs: don't modify this file; pros: Go ahead
ramdisk.gz
You want to change that sweet boot image, that's why you want to unpack kernel in the first place? On how to create boot image, go here.
This file contains the rest of the tweaks developers apply to kernel. Here you will find CWM, bootsplash image, autoroot files, etc, all depending on kernel you are modifying. Now, hot to unpack this bloody file? some suggest to use 7zip, but this way you will break symlinks and your kernel will definitely not boot. Proper way of unpacking ramdisk.gz goes like this:
First of all, boot up linux (or load builduntu into virtual machine, your choice).
We want to set up working folders, right? Fire up terminal and enter following commands, one line at the time:
mkdir kernel-working
mkdir ramdisk-working
cd ramdisk-working
mkdir ramdisk-contents
cd ramdisk-contents
Click to expand...
Click to collapse
Don't close terminal, or I will break you fingers Now in your home folder you will find folders we've just created. Nice, isn't it? Remember those files we've unpacked earlier? copy them to these folders. ramdisk.gz goes to ramdisk-working folder, while the rest goes to kernel-working folder.
Download kernel_repack.zip from the attachment und unpack files which are in it to kernel-working folder.
Now we're all set up for modifying
Go back to the terminal. Copy and paste following command and run it:
gunzip -c ../ramdisk.gz | cpio -i
Click to expand...
Click to collapse
Again, don't close the terminal. This time I will break your legs if you do so Now ramdisk.gz is unpacked in ramdisk-contents folder (which is in ramdisk-working folder). There you will find bunch of files and folders. After you have done all your modifications, it's time to pack it up. To do so, run the following command in terminal:
find . | cpio -o -H newc | gzip > ../newramdisk.gz
Click to expand...
Click to collapse
In ramdisk-working folder you will find newramdisk.gz file, besides ramdisk.gz. Copy newramdisk.gz to kernel-working folder and rename it to ramdisk.gz.
Now all files for compiling new kernel are prepared. To the next and final step.
STEP 3: Packing kernel back
In terminal, run following commands (and yes, you run cd .. twice in a row):
cd ..
cd ..
cd kernel-working
Click to expand...
Click to collapse
Remember that screenshot we've took earlier? This is where we need it Told you so
And finally, here is the mother of all commands which neatly packs all of our files back into kernel, but don't use it just yet, I will explain why:
sudo python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],cmdline
Click to expand...
Click to collapse
Take a look at the my screenshot and you will see that each of the files have its own adress. For example Image is at the adress 0x00008000 and ramdisk.gz is at the adress 0x01000000,ramdisk and 3 is at the adress 0x00000000,cmdline. By writing proper names and adresses, I'm telling computer where to pack files inside the kernel. You will have to change adresses in this command according to your screenshot, because not all kernel have the same adresses for same files. This is the most important step because if you do this wrong, kernel will not properly compile!
If you did all the work correctly, in kernel-working folder you will find new kernel.elf file. If it was named boot.img before editing, rename it back, if it was named kernel.elf then leave as it is. If you want, you can test if you packed kernel properly by trying to unpack it in Flashtool. If flashtool reports that you have some files to unpack, than all is OK, if it reports nothing, then something went wrong.
Ta-da! Your kernel is finally packed and is ready to be flashed to your phone. Hopefully, if you didn't messed up something when you did your modifications and alterations to ramdisk.gz, it should properly boot.
You can flash kernel in your preffered way.
Final words:
I tried to make this tutorial as user-friendly as possible. It is pretty straightforward once you get into it.
I hope that I clarified some thing, and more importantly, that I helped you.
Cheers everyone, and happy, repacking/flashing/modifying
Not a bad guide! Keep it up!
Sent my Carbonised Xperia P
Nice! :good:
Another good reference for kernel unpacking is this: http://forum.xda-developers.com/xperia-u/general/tutorial-explaining-stock-boot-image-t2126924
Enviado desde mi ST25i mediante Tapatalk
great guide
I just have windows , so am i doomed ?? I just wanted to change my kernel to Candy instead of Sony
Johnt880 said:
I just have windows , so am i doomed ?? I just wanted to change my kernel to Candy instead of Sony
Click to expand...
Click to collapse
Run builduntu in virtualbox.
If i got a sony kernel that sorted with the word sony out that will do my phone ?Just a standard kernel
I didn't quite understand you, can you clarify a little?
kernel 4.4.2
is there a way to modify the kernel aosp 4.4.2. This method does not work
kosmos-2011 said:
is there a way to modify the kernel aosp 4.4.2. This method does not work
Click to expand...
Click to collapse
Try that > http://forum.xda-developers.com/showthread.php?t=2073775
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
attached is recovery log sir
Er. Aditya said:
attached is recovery log sir
Click to expand...
Click to collapse
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
SuperR. said:
sepolicy-inject is not available for windows currently. I should have removed the option for Windows, and will in the next update. Is this a feature that still needs to stick around? I am not sure if I can get it working in Windows due to the pre-compiled Linux libs in the source. I am also not sure if you can compile libsepol on Windows. If you can get this source compiled for Windows, I can add the feature
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
Click to expand...
Click to collapse
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Er. Aditya said:
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Click to expand...
Click to collapse
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
bcrichster said:
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
Click to expand...
Click to collapse
These wheels are rolling faster each day. We will ride
SuperR. said:
These wheels are rolling faster each day. We will ride
Click to expand...
Click to collapse
Lmao. Right on! If anyone can get this right, it's You and these guys helping here @SuperR. [emoji41] Catching some air!
Sent from my N9515 using Tapatalk
SuperR. said:
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Click to expand...
Click to collapse
yes both were created using latest kitchen 3.0.1.4 , same firmware and procedure
here are the scripts sir
SuperR. said:
v3.0.1.8
Changes:
Windows: Use 7-zip (included) to extract img files instead of Imgextractor.
Windows: Fixed missing symlinks in updater-script.
Windows: Fixed many file contexts not being set correctly.
Windows/Linux: Fixed system/SYSTEM on devices that use SYSTEM.
Linux: Do not create metadata lines for symlinks.
I think this will fix most of the flashing problems. Let me know how it goes
WINDOWS NOTE: It is important that the tools get updated. The updater should take care of it, but if you get errors that 7z is not found, go to Misc tools > Reset tools.
IMPORTANT: Start your rom fresh and extract from system.img again. Make sure you delete 00_project_files directory if you are reusing an existing project.
Click to expand...
Click to collapse
i still got the error 7 even i clean cloned kitchen sir
Er. Aditya said:
i still got the error 7 even i clean cloned kitchen sir
Click to expand...
Click to collapse
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
SuperR. said:
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
Click to expand...
Click to collapse
u have been a rock and we are so glad ur trying to get this to work sir i am attaching a working script and supeR script with recovery log
edit : the modified one again gave that error
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
samsung device ?
SuperR. said:
v3.0.1.9
Changes:
Windows: Fixed b key press not being recognized.
Added a Back option to the root method options.
Only allow key presses that correspond to menu options.
Fixed project name adding an extra superr_ when creating new project from the project selection menu.
Set permissions of configure.sh to 777 instead of /tmp to 755.
@Er. Aditya - This includes the change I sent you in the PM. No clue if it will work for you, but worth a try. No need to extract the system.img again if you extracted using v3.0.1.8. Just change perm types to something else and then back to set_metadata and it will update the updater-script for you.
Click to expand...
Click to collapse
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
SuperR. said:
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
Click to expand...
Click to collapse
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Er. Aditya said:
samsung device ?
Click to expand...
Click to collapse
HTC
Er. Aditya said:
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
Click to expand...
Click to collapse
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
OMJ said:
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Click to expand...
Click to collapse
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently. I could switch this over to 7-zip in Windows if needed now that it is included anyway.
SuperR. said:
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently.
Click to expand...
Click to collapse
i have been having issues since this config.sh has been introduced sir
Er. Aditya said:
i have been having issues since this config.sh has been introduced sir
Click to expand...
Click to collapse
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
SuperR. said:
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
Click to expand...
Click to collapse
[emoji23] [emoji23] Nice!! [emoji41] [emoji41]
Sent from my N9515 using Tapatalk
Er. Aditya said:
I am ready!
Click to expand...
Click to collapse
Here are 3 to try. I may come up with some others if they don't work. When you flash it, we want to see the by-name path on the screen and not get errors. Let me know how it goes