When the kitchen works with the ship rom,it will drop the recovery img,only add the boot and system img into its work folder.How can I make a recovery img into a rom(update.zip) cooked by kitchen？
yubigfish said:
When the kitchen works with the ship rom,it will drop the recovery img,only add the boot and system img into its work folder.How can I make a recovery img into a rom(update.zip) cooked by kitchen？
Click to expand...
Click to collapse
Place the recovery.img in the root of your ROM and add this line to your updater-script.
Code:
assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
write_raw_image("/tmp/recovery.img", "recovery"),
delete("/tmp/recovery.img"));
dastin1015 said:
Place the recovery.img in the root of your ROM and add this line to your updater-script.
Code:
assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
write_raw_image("/tmp/recovery.img", "recovery"),
delete("/tmp/recovery.img"));
Click to expand...
Click to collapse
Further more ,if I want to replace the framework-res.apk or the fonts file,can I place the framework-res.apk and fonts file in the correct floders without any command?Just use kitchen to build the rom?
yubigfish said:
Further more ,if I want to replace the framework-res.apk or the fonts file,can I place the framework-res.apk and fonts file in the correct floders without any command?Just use kitchen to build the rom?
Click to expand...
Click to collapse
That's right!
Related
Hi,
I'm kinda new to flashing and upgrading my phone.
Therefore I got some questions:
Currently running on my Neo: AOSP 4.0.3 ICS BETA with kernel provided there
Baseband says: 56 as last two digits
I would like to upgrade my baseband to 62. (latest)?
As far as I understood I will have to flash 4.0.2.A.0.62 Baseband using flashtool.
Do I have to flash the kernel again after upgrading baseband or should I flash the 4.0.2.A.0.62 Kernel first and change it afterwards?
fastboot flash boot boot.img
Click to expand...
Click to collapse
Will changing the baseband or kernel delete anything?
When would be the right time to apply the RAISE your NEO userdata space patch? Before or after baseband, kernel flash?
Sometimes they say that a reboot is required after flashing a new ROM before flashing an update.zip in CWM. Do I have to reboot at other times?
Is there a tool or a possibility I missed which can flash anything like baseband, kernel, ROM and updates to it in one step?
If I want to edit a ROM like directly changing bootanimation and ringtones.
How should the zip file be packed? No compression, etc?
Is it a good idea to include updates which I would have flashed in CWM directly into the ROMs zip file?
Do I have to flash the kernel again after upgrading baseband or should I flash the 4.0.2.A.0.62 Kernel first and change it afterwards?
Click to expand...
Click to collapse
Kernel is not related to baseband. Simply flash baseband, no need to flash kernel after or before.
Will changing the baseband or kernel delete anything?
Click to expand...
Click to collapse
Flashing baseband won't delete anything, but flashing kernel might. I see that kernel in that thread have CWM inside, so if you flash stock kernel you will lose that.
When would be the right time to apply the RAISE your NEO userdata space patch? Before or after baseband, kernel flash?
Click to expand...
Click to collapse
Whenever you want. It's not related to kernel or baseband.
Sometimes they say that a reboot is required after flashing a new ROM before flashing an update.zip in CWM. Do I have to reboot at other times?
Click to expand...
Click to collapse
Yes, they say that so that ROM "settles down in it's place" then you can install fixes and stuff.
What other times?
Is there a tool or a possibility I missed which can flash anything like baseband, kernel, ROM and updates to it in one step?
Click to expand...
Click to collapse
There is flashtool, but only for stock rom's. Custom roms are installed as a .zip file via CWM recovery.
If I want to edit a ROM like directly changing bootanimation and ringtones.
Click to expand...
Click to collapse
You can do that with root explorer app(or any app which can access to system), create that bootanimation.zip on pc and upload it to sdcard, then move it to where it needs to be. For bootanimation.zip, yes, it's with no compression. How it's created, check other bootanimation.zip's over the net.
For other zip's which are flashed trough CWM, it's a bit more complicated to explain how to create them.
Is it a good idea to include updates which I would have flashed in CWM directly into the ROMs zip file?
Click to expand...
Click to collapse
Well depends. Most likely yes, but I would still ask creator/porter of each rom if that is advisable
Madfysh said:
seXneo said:
If I want to edit a ROM like directly changing bootanimation and ringtones.
How should the zip file be packed? No compression, etc?
Click to expand...
Click to collapse
You can do that with root explorer app(or any app which can access to system), create that bootanimation.zip on pc and upload it to sdcard, then move it to where it needs to be. For bootanimation.zip, yes, it's with no compression. How it's created, check other bootanimation.zip's over the net.
For other zip's which are flashed trough CWM, it's a bit more complicated to explain how to create them.
Click to expand...
Click to collapse
Thank you very much.
But in this point there was a misunderstanding.
I just wanted to know how the update.zip or rom.zip has to be packed and if it's save to replace bootanimation.zip inside rom.zip. Are there any checksums for apk or other files inside an CWM update.zip I need to change?
Most of the ICS based ROMs use MT15i_Neo_ICS_Kernel_V1.img. Where does it come from and where is it's original thread?
if it's save to replace bootanimation.zip inside rom.zip. Are there any checksums for apk or other files inside an CWM update.zip I need to change?
its safe to change bootanimations.zip and any other apk or file in side the provided update.zip file
but if u extract it n do changes then u will lose the signature of the developer n wont b able to install the update.zip properly
chintu1234 said:
its safe to change bootanimations.zip and any other apk or file in side the provided update.zip file
but if u extract it n do changes then u will lose the signature of the developer n wont b able to install the update.zip properly
Click to expand...
Click to collapse
Yes of course. If original zip file flashed and runs nice it will be my fault if it won't after my edits.
So no checksums in the update.zip directly. Thanks.
Signing of an altered apk file is required. Got it.
And I figured that there is no signing of the bootanimation possible.
Will post my question regarding the kernel in an extra thread.
Whe I change the boot animation in the rom's .zip do I then reflash the rom?
And if so do I do a wipe or just reflash without any wipe.
Thanks
you can just make a zip with the bootanimation and then flash that only.. no need to reflash the rom
Any time I have tried to just flash the zip with the boot animation it didn't take and the animation for the rom I am running (CleanRom) is still present.
Burkejt1 said:
Any time I have tried to just flash the zip with the boot animation it didn't take and the animation for the rom I am running (CleanRom) is still present.
Click to expand...
Click to collapse
Did you make sure that the bootanimation.zip in located in the in the same directory in the flashable zip as it is in the rom. For example, alot of roms the boot animation is located in system/media, therefore it would need to be in the same directory in the flashable zip. you can also just use a file manager like root explorer or es file explorer and just swap out the animations.
It seems like swapping them out is a tad easier
hardfallen87 said:
Did you make sure that the bootanimation.zip in located in the in the same directory in the flashable zip as it is in the rom. For example, alot of roms the boot animation is located in system/media, therefore it would need to be in the same directory in the flashable zip. you can also just use a file manager like root explorer or es file explorer and just swap out the animations.
Click to expand...
Click to collapse
Burkejt1 said:
It seems like swapping them out is a tad easier
Click to expand...
Click to collapse
if you need any more help shoot me a pm. i have no problem helping out, i was in the same boat at one point.
The format of recovery that we download from official website is .img. How can we make it a cm flashable zip?
Sent from my HTC One X+ using xda premium
Siddharth121 said:
The format of recovery that we download from official website is .img. How can we make it a cm flashable zip?
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
If you are talking about making a stock ROM (.img) into a flashable zip file then you will need android kitchen.
1. Place both boot.img and system.img into Original_Update folder
2. In kitchen click option 1
3. Pick the option that says system.img and boot.img
4. Follow the onscreen instructions
5. Build using option 99.
6. Flash in CWM or TWRP!
Siddharth121 said:
The format of recovery that we download from official website is .img. How can we make it a cm flashable zip?
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
To make the recovery.img flashable in CWMR recovery you would have to create a flashable zip that writes the raw .img file to the recovery partition. The commands to flash it to the recovery partition would be similar to this:
Code:
ui_print("ClockworkMod Recovery v6.0.3.1");
ui_print("for Your Device Name Here");
show_progress(0.500000, 0);
ui_print("Writing recovery image");
package_extract_file("recovery.img", "/tmp/recovery.img");
run_program("/sbin/busybox", "dd", "if=/tmp/recovery.img", "of=path/to/recovery/partition");
delete("/tmp/recovery.img");
ui_print("Complete!");
Note: The ui_print and show_progress commands are just to make it easier for the user to understand what is going on and for a clean look.
The structure for the folder of the flashable zip would be similar to:
META-INF->com->google->android->update-binary and update-script
recovery.img (In the same folder as your main zip do not put this in the META-INF folder)
I would also recommend checking out this guide to edify scripting and creating flashable zip's. Let me know if you still have questions .
I have an custom recovery and I want to edit some files but I an not able to open it does anybody know how to open it
mja123 said:
I have an custom recovery and I want to edit some files but I an not able to open it does anybody know how to open it
Click to expand...
Click to collapse
Use img boot tools packer and unpacker to unpack your img files
Some Basic things u need to Know before Porting
The rom which you want to port for your device is named here as PORT
The rom which is already working for your device is called here as BASE
First unpack system.new.dat in both port and base rom
For Ubuntu
Now we need to decompress .dat to ext4 img
Open terminal and
Now enter this command
./sdat2img.py system.transfer.list system.new.dat system.img
By running this command u can see a system.img
decompress ext4 img to output folder
Now we will mount system.img
Enter this command
sudo mount -t ext4 -o loop system.img output/
Now go to output folder and now u can see all folder and apk like a KitKat rom
Now do the same with port rom
Click to expand...
Click to collapse
For windows use System Extractor for unpacking
1. Delete app,font,framework,media and priv-apps in base rom
2. Copy app,font, framework,media and priv-apps from port to base
3. Copy handheld_core_hardware.xml and platform.xml in system/etc/permissions from port to base
4. Copy 00banner in system/etc/init.d from port to base
5. Now open build.prop in both base and port for editing rom version and other things.It is different in different roms. For CM edit
ro.cm.version=
ro.cm.releasetype=
ro.modversion=
ro.cmlegal.url=
ro.cm.display.version=
ro.config.notification_sound=
ro.config.alarm_alert=
ro.config.ringtone=
Note: You have copy the above lines from port to base. Don't forget to add your device name in place of port rom's device name
6. Copy these files in system/lib from port to base I repeat from port to base
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
For AOSP based ROMs other library files are also needed for boot up. For example Dirty Unicorn needs
libgui.so
libsurfaceflinger.so
libsurfaceflinger_ddmconnection.so
libwifi-service.so
If you are porting a 64 bit ROM copy these files in system/lib64 too from port to base
7. Unpack boot.img of both base and port rom and open init.environ.rc in ramdisk. Copy and replace all the lines starting from "bootclasspath" from port rom's environ.rc to base rom's environ.rc and repack boot.img . Use Android Image Kitchen for unpacking and repacking boot.img
8.Now we need to compress the base rom
For Ubuntu
Now enter this command
./make_ext4fs -T 0 -S file_contexts -l 1073741824 -a system system_new.img output/
Now u can see ur system_new.img
now we need to compress it back to .dat
Now enter command
./rimg2sdat my_new_system.img
Now u can see system.new.dat
Click to expand...
Click to collapse
For Windows, System Extractor has an option to repack but it causes bootloop for me. Ignore step 8 if it causes bootloop
NOTE: You'll need a different updater script for unpacked system
9. Zip it back and Flash
Downloads
sdat2img.py
make_ext4fs
rimg2sdat
Now Download all these tools and paste it to ur base and port rom directory then follow instructions to port lollipop roms
Click to expand...
Click to collapse
CREDITS
VigneshS007
xpirt
matrixex
How to fix bootloop
Some Roms may not boot even after doing everything correctly. This method should be only used when nothing works
1. Copy all the files in system/lib, and system/lib64 if it's a 64 bit ROM, from port to base except the these files and folders
drm
hw
modules
soundfx
libGLES_trace.so
libGLESv1_CM.so
libGLESv2.so
libGLESv3.so
I repeat you have to leave the above files and folders and copy all the other files in system/lib from port to base.
If it still doesn't boot follow the second method
2. Unpack boot.img of both base and port, enter ramdisk and copy these files from port rom's ramdisk to base rom's ramdisk
seapp_contexts
sepolicy
service_contexts
Repack boot.img and flash it
IMPORTANT: This method should only be used when nothing works and if it boots after copying all the lib files, you will have to figure out which lib files are causing bootloop because port rom libraries will create many bugs.
Reserved
From who smartphones we can ported roms ?
Sparco21 said:
From who smartphones we can ported roms ?
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/List_of_Qualcomm_Snapdragon_devices
6.2 Snapdragon 410 and 412
Missing in this list:
Ark Benefit
Elephone Trunk
thanks for releasing the guide
Thanks for the tutorial!
Tried porting slim6 from redmi 2 but got stuck on bootanimation forever.What Im I supposed to do with the build.prop?
I already tried
-not touching it
-replacing it
-replacing some things
all ended in just bootanimation :/ I use the nexus 6.0 rom for base
BTW should I replace kernel(zimage) in boot.img(havent done it)?
Whenv i try to repack the system folder to system.new.dat with the Extractor for Windows i always get the following error: "It seems like the extractor not worked with your provided system folder please contact me for help".
I have read that specially the CM roms give this error but i cannoy understand how to fix it even after search the solution.
The rom i was trying to port is a CM12.1 rom. Anyone knows how to solve this?
mustang_ssc said:
Whenv i try to repack the system folder to system.new.dat with the Extractor for Windows i always get the following error: "It seems like the extractor not worked with your provided system folder please contact me for help".
I have read that specially the CM roms give this error but i cannoy understand how to fix it even after search the solution.
The rom i was trying to port is a CM12.1 rom. Anyone knows how to solve this?
Click to expand...
Click to collapse
Do you have python installed ?
mshoaib7 said:
Do you have python installed ?
Click to expand...
Click to collapse
Should i had to install Python in Windows? I didn't know Python exists in windows.
mustang_ssc said:
Should i had to install Python in Windows? I didn't know Python exists in windows.
Click to expand...
Click to collapse
Yes it does exist for windows. And if it still doesn't work ask this in system extractor thread
mshoaib7 said:
Yes it does exist for windows. And if it still doesn't work ask this in system extractor thread
Click to expand...
Click to collapse
I have just tried it but still the same issue.
I saw that the dev of the system extractor tried to explain how to solve the issue but honestly i don't undestand nothing of the process he's talking about, i was completely confused. For example, for some reason he was talking about the updater-script but i don't understand what relation are between what i want to do (repack the system folder) and the updater-script (located in the meta-inf folder).
Not booting, porting same vendor ROM but different model similar specs
Followed your tutorial till the last solution but no luck. I am trying to port my own device ROM but of a different model. I have Qiku Q Terra 808, model CP8692_I02 with 360 OS v21 and was trying to port v109 360 OS of model CP8692. The specs and everything is same however I am still unable to boot. There was a very weird thing happened when I flashed the ported ROM and restored the backed up data before booting. The device booted but it reboots on it's own in less than a min of booting and the cycle goes on. And if don't restore the data it goes in bootloop right away. I get the display on, optimizing apps then reboots and cycle goes on. The 360 OS are known for security and the device has fingerprint scanner. Do you think the stored fingerprint is causing issue in flashing new ROM or incorrect update script is the culprit?? Please advise.
@mshoaib7 Awesome tutorial man...??
CM14 theme engine has not been integrated at present, many functions is still in the invalid state, would you be interested in transplantation AOSP 7.1?
Very good ?A great help ?Moto g 2015
mshoaib7 said:
How to fix bootloop
Some Roms may not boot even after doing everything correctly. This method should be only used when nothing works
1. Copy all the files in system/lib, and system/lib64 if it's a 64 bit ROM, from port to base except the these files and folders
drm
hw
modules
soundfx
libGLES_trace.so
libGLESv1_CM.so
libGLESv2.so
libGLESv3.so
I repeat you have to leave the above files and folders and copy all the other files in system/lib from port to base.
If it still doesn't boot follow the second method
2. Unpack boot.img of both base and port, enter ramdisk and copy these files from port rom's ramdisk to base rom's ramdisk
seapp_contexts
sepolicy
service_contexts
Repack boot.img and flash it
IMPORTANT: This method should only be used when nothing works and if it boots after copying all the lib files, you will have to figure out which lib files are causing bootloop because port rom libraries will create many bugs.
Click to expand...
Click to collapse
shoaib bhai is this guide also for nougat roms?
MR.HACKER5476 said:
shoaib bhai is this guide also for nougat roms?
Click to expand...
Click to collapse
No, only some of the nougat Roms boot with this guide
Some one can port VIVO Y21L ROM & kernel for Lenovo A6000....
VIVO Y21L has same SD410 chipset as Lenovo A6000. @With support of VoLTE and OTG....
It not complete Guide
If you port tw roms,You will not get bootup.
Tried to port J5 rom or grand prime rom?