Related
Boot Animations:Tutorial & A Place To Post Your Own. UPDATED 04/10/2011 NEW ANIMATION
How To Create Your Own Boot Animations
Here is a flashable zip from sparksco that will install any bootanimation placed on the root of the sdcard
Download Here
Just place the bootanimation on the root of the sd, then flash this from recovery.
Created Boot Animations Are At The End Of This Post
There are five steps in creating a boot animation:
1. Creating the images;
2. Creating the desc.txt file;
3. Creating the bootanimation.zip file;
4. Pushing the boot animation to the phone;
5. (Optional) Adding a boot audio file.
Click to expand...
Click to collapse
1. Creating The Images.
If you have even seen a flip book (flip the pages fast enough, and a succession of images appears to become animated), then you understand the basics of a boot animation. This is nothing more than a flip book for the digital age, and so all that is required is a collection of images, that when viewed very quickly in succession, appear to be animated (of course with most filming being done digitally these days, one could argue that this is all movies).
Creating these images will take days if you choose to create each one individually, so here is the trick to make this worth doing. Either create a flash animation, or find one you enjoy (you tube is a good place to look for flash animations, and if you do a quick google search you can see how to download youtube videos).
Once you have the flash animation you like, use video editing software to convert it into a series of JPEG or PNG images. I suggest using Avidemux ( http://fixounet.free.fr/avidemux/ ), which is a free, cross-platform, open-source video editor.
This will chop it up to many files. Since you do not want too large of a bootanimation.zip, I suggest the removal of intermittent files (such as every 5th file) to end up with 50-150 images.
Now on to the editing, for which I suggest using GIMP ( http://www.gimp.org/ ), which is a free, open-source, cross-platform graphics editor (similar to photoshop). To ensure that the images appear as you would like when turned into an animation, you can resize each image to 480 x 800 (or place each image on a background of these dimensions). The nice thing about GIMP is that it works with terminal commands, so it is possible to resize the entire folder of images with one line of code in the terminal. It should be noted that this step is optional, as the desc.txt file will allow you to choose the proper rendering size. While in GIMP you can do any graphical edits you like to the images, but be sure to make these as small as possible to ensure a smooth running boot animation.
I will say no more about graphics editing, as there are plenty of online tutorials for this.
Be sure to save each image as a JPEG or PNG, and rename each in succession. Thus the first image will be named something like
Code:
image_001.png
, the second
Code:
image_002.png
and so on (look in any boot animation if this is unclear).
The last thing to note on these images, is that you can choose to have an initial animation run, then at some point have the image start looping. Consider for example the Cyanogen boot animation which comes at you, bounces, then starts with the spinning blue flames. If you desire to have it loop at some point in the animation, this will be taken care of with the desc.txt file, just keep this in mind while creating the images.
Click to expand...
Click to collapse
2. Creating The desc.txt File
The purpose of the desc.txt file is to (i) define the dimensions for which the image should be rendered, define the speed at which images are changed, and define the looping (if any).
The desc.txt file for the stock shift boot animation looks like
Code:
480 800 15
p 1 1 android
The 480 800 refers to the image size, this is what you need for the shift.
The 15 refers to the frames per second. Depending on the images you used, this can vary widely for the best look. When I make these, I try many different values and see which looks best.
p refers to "pointer" leave this as is.
The first number after p refers to the number of times to play, thus in this case, it is played once. If you desire it to loop, set the value to 0.
The next number refers to the number of freezes on the last frame (in FPS). Thus, in this case, 1 FPS.
Finally, android refers to the folder in which the images files are contained, and tells the phone to execute an audio file.
Now, if you desire to only have part of the images loop, then you will need more than one folder. Suppose you have 120 images named image_001.png through image_120.png, and it is desired to have all of your images play through once, then restart at image_090.png and loop until boot is complete. You would make two folders, say part0 and part1. In folder part0 you would then place all 120 images and in folder part1 you would place image_90.png through image_120.png. In this case a desc.txt file could look like
Code:
480 800 25
p 1 0 part0
p 0 0 part1
Note that there is a blank line left after the last folder. Be sure to include this.
There are a multitude of combinations that will work on the desc.txt file, and it will usually take some trial and error before you have one that is right for your particular animation.
Click to expand...
Click to collapse
3. Creating the bootanimation.zip
Though this seems like the simple part, it is where most of the issues occur. This is due to the fact that if the file is zipped with any level of compression, the phone will not be able to read it. IF THE ZIP IS NOT MADE WITH ZERO COMPRESSION, THIS WILL RESULT IN A BLANK SCREEN DURING BOOT
Create a folder named "bootanimation" on your desktop. In this folder place only the folders containing your images and the desc.txt file, AND NOTHING ELSE (in the previous example one would place the folders part0 and part1, along with desc.txt into the folder bootanimation).
If using windows, 7zip will do zero compression zipping. Since I do not use windows, I will leave this up to you to figure out. With Linux, open the terminal and enter
Code:
cd ~/Desktop/bootanimation
zip -0 bootanimation * */*
If all was done correctly, you will now have a working boot animation.
Click to expand...
Click to collapse
4. Pushing The Boot Animation To Your Phone.
BEFORE DOING THIS, MAKE A NANDROID BACKUP
This can either be done using adb, or via the phone terminal.
ADB & Linux: Place the bootanimation.zip file on your desktop, then open the computer terminal and enter
Code:
adb push ~/Desktop/bootanimation.zip /system/customize/resource/bootanimation.zip
adb reboot
ADB & Windows: Place the bootanimation.zip file on your desktop, then open the computer terminal and enter
Code:
adb push C:\Your_User_Name\Desktop\bootanimation.zip /system/customize/resource/bootanimation.zip
adb reboot
Phone Terminal: Place bootanimation.zip on the root of your sdcard, then in the phone terminal enter
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p26 /system
cp /mnt/sdcard/bootanimation.zip /system/customize/resource/bootanimation.zip
Then reboot the phone.
If your boot animation is not working, recheck all of the above steps.
Click to expand...
Click to collapse
5. (OPTIONAL) Adding A Boot Audio File
Find a desired audio file in .mp3 format, and rename it to VERSION11SAMELENGTH.mp3.
To make it executable you will need to edit the desc.txt file to
Code:
480 800 25
p 1 0 android
p 1 0 part0
p 0 0 part1
The new line
Code:
p 1 0 android
tells the phone to play the audio file once, with no freeze. You can of course edit the number of times it should play (the first number after p), but should not mess with anything else.
Now you need only to push the file to your phone
This can either be done using adb, or via the phone terminal.
ADB & Linux: Place the VERSION11SAMELENGTH.mp3 file on your desktop, then open the computer terminal and enter
Code:
adb push ~/Desktop/VERSION11SAMELENGTH.mp3 /system/customize/resource/VERSION11SAMELENGTH.mp3
adb reboot
ADB & Windows: Place the VERSION11SAMELENGTH.mp3 file on your desktop, then open the computer terminal and enter
Code:
adb push C:\Your_User_Name\Desktop\VERSION11SAMELENGTH.mp3 /system/customize/resource/VERSION11SAMELENGTH.mp3
adb reboot
Phone Terminal: Place VERSION11SAMELENGTH.mp3 on the root of your sdcard, then in the phone terminal enter
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p26 /system
cp /mnt/sdcard/VERSION11SAMELENGTH.mp3 /system/customize/resource/VERSION11SAMELENGTH.mp3
Then reboot the phone.
You now have a custom boot animation with a custom audio file.
Click to expand...
Click to collapse
Enjoy, and be sure to post your creations.
My Bootanimations
Click to expand...
Click to collapse
Hyper Surface Animation
{
"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"
}
Download Hyper Surface Animation
Shell Animation
Download Shell Animation
Download Shell Animation Audio File
Click to expand...
Click to collapse
Rain Animation
Download Rain Animation
It is designed to move to the music in this file:
Download Rain Animation Audio File
Try them together, if the music is not to your liking (Clip from Beethoven's Bagatelle in A minor), just replace it with whatever you like.
Click to expand...
Click to collapse
Animations by Nitro3a
Download
Click to expand...
Click to collapse
Animations by riggsandroid
Download
Blue Bee
Orange/Red Bee
Green Bee
Pink Bee
Grey Bee
BIOS Bee
Click to expand...
Click to collapse
Did this simple one.
Only looks grainy because of resizing. Looks fine full size.
DL zip here - rename to appropriate .zip name based on ROM you are on.
yeah great wu clover. thanks for the time
No problem, I used to love making these, but found it so tricky at first. With a few tips it is really easy.
Has anyone tried this?
Boot animation Simple.
cloverdale said:
Has anyone tried this?
Click to expand...
Click to collapse
I made a simple boot ani the only problem I did was try to use the desc.txt to call a different sound file following the rules that Motorola uses for their phones. Needless to say it still plays the original boot sound from sprint. I put the custom mp3 file in /system/customize/resource and it still plays the default sprint sound when booting. I haven't figured out where the sound file is supposed to go yet, but I haven't looked very hard either.
Here is the simple boot ani I made. The Background is transparent not white. Also note that this update zip will only work with CWM 2.5.X
Here is smaller size boot ani.
7zip commands for Windows 7
These are the commands that I used to make a boot animation using 7zip on a windows platform.
Code:
7za a -mx0 nitro3a.zip part0
7za a -mx0 nitro3a.zip part1
7za a -mx0 nitro3a.zip desc.txt
a = add to zip
-mx0 = Zero compression
nitro3a.zip = If you can't figure this out hmmm.....*Think happy thoughts*the zip file name (at the time the rom I was using you could put as many zip files on your sd card and it would randomly pick one as your boot animation)
part0 = First folder in the sequence
As I said earlier you might be able to zip it all in one command and I just did it the wrong way but I do it this way because I know it works. You might be able to switch up which image folder zips first I don't know I just did it on order because it seemed logical , but I am sure that all the image folders have to be added before you add the "desc.txt" file.
Nitro3a said:
These are the commands that I used to make a boot animation using 7zip on a windows platform.
Code:
7za a -mx0 nitro3a.zip part0
7za a -mx0 nitro3a.zip part1
7za a -mx0 nitro3a.zip desc.txt
a = add to zip
-mx0 = Zero compression
nitro3a.zip = If you can't figure this out hmmm.....*Think happy thoughts*the zip file name (at the time the rom I was using you could put as many zip files on your sd card and it would randomly pick one as your boot animation)
part0 = First folder in the sequence
As I said earlier you might be able to zip it all in one command and I just did it the wrong way but I do it this way because I know it works. You might be able to switch up which image folder zips first I don't know I just did it on order because it seemed logical , but I am sure that all the image folders have to be added before you add the "desc.txt" file.
Click to expand...
Click to collapse
Thank you. I have no idea how to things on windows these days. I always appreciate someone filling in the details.
I am going to start moving the posted animations to the OP. If anyone has an issue with this, please let me know.
I've made one successfull animation, using the factory desc file and just changing the file names to match the original.
I have now made a different version that I'm having issues with...
I'm editing the file like you said, but for some reason I get white screen flashes during the animation. One at the very start and another everytime the second part of the animation repeats itself.
Any ideas why this is happening?
currently my desc file looks like this
480 800 15
p 1 0 android
p 1 0 part0
p 0 0 part1
I also tried this one (and some with different FPS values)
480 800 15
p 1 0 android
p 1 1 part0
p 0 1 part1
BuddahWolf01 said:
I've made one successfull animation, using the factory desc file and just changing the file names to match the original.
I have now made a different version that I'm having issues with...
I'm editing the file like you said, but for some reason I get white screen flashes during the animation. One at the very start and another everytime the second part of the animation repeats itself.
Any ideas why this is happening?
currently my desc file looks like this
480 800 15
p 1 0 android
p 1 0 part0
p 0 0 part1
I also tried this one (and some with different FPS values)
480 800 15
p 1 0 android
p 1 1 part0
p 0 1 part1
Click to expand...
Click to collapse
Search through all of the image files, and make sure the numbering is consecutive, and that there are no missing numbers (such as image0005.png, image0007.png).
No, there weren't any... but I did delete some trying to fix it and that did make it worse.
Any chance it could be something with how the pngs are saved? I didn't use photoshop this time like I did the first time. I used After Effects to save my movie as a png sequence.
EDIT: I figured out the flashes. There are hidden files in the folders that contain pictures. On windows7 they are "ds.store" or something. Pretty much the same as .thumb files that allow you to see thumbnail previews. These must be removed or they will show as white flashes in your animation.
BuddahWolf01 said:
No, there weren't any... but I did delete some trying to fix it and that did make it worse.
Any chance it could be something with how the pngs are saved? I didn't use photoshop this time like I did the first time. I used After Effects to save my movie as a png sequence.
EDIT: I figured out the flashes. There are hidden files in the folders that contain pictures. On windows7 they are "ds.store" or something. Pretty much the same as .thumb files that allow you to see thumbnail previews. These must be removed or they will show as white flashes in your animation.
Click to expand...
Click to collapse
That makes a lot of sense. Damn windows
well I figured out it may not have been windows! I usually do everything on mac, but didn't have an easy way to zip without compression... so I used windows for that part and the ADB part because it is slightly simpler.
I tried a couple different ways and some terminal commands on mac that also ended up zipping the ds_store files, so I guess they are a file that is hidden when you zip stuff that way.
Anyways tonight I figured out that I can just run the command you listed in step (3) and it works just fine without putting the ds_store files in!
So now after editing my images and videos, I wont have to switch to windows to zip and push them anymore!!!
I used root explorer to replace the bootanimation.zip.
Just backed up my original to my sdcard and then overwrited it with a custom one after.
I just wanted to let everyone know that I will not be around much for awhile, so please do not get upset if you think I am ignoring questions. I am working on a huge project at work (I am a researcher at the NIH, working on a major project from the SSA), and have been putting in 60 hour work weeks. People with terminal illness are dependent upon my work, so it comes before my health, my hobbies, and definitely before a phone. When things settle down a bit, I will become more active again. Talk to you all soon.
Work has been too much, and I had to take a break and make myself a new boot animation. Check the OP for this update.
So I tested this out I was able to get a premade boot ani to work but when I make my own it dosent work I think its the zipping part because I took the orignal boot an unzipped and rezipped just to test and it still dosent work is there an app I can DL on my phone or something special I have to do on my windows 7 7-zip program... I made a family guy boot ani will try to load once I get it to work
Sent from my PG06100 using XDA App
Try changing the zip compression level from Normal to Store after you've added your files to the archive. I think that's what he meant by a zero compression zip file. :S
EDIT: OP states:
The nice thing about GIMP is that it works with terminal commands, so it is possible to resize the entire folder of images with one line of code in the terminal.
What is the terminal command for windows? Where would I find that? Thanks in advance.
If you open the start menue search cmd it will open then in the 7-zip help section under contents cmd line ver then syntax it explains it but I can get it to work termanal tell me that its not a program or batch file
Sent from my PG06100 using XDA App
UPDATED: 12-19-2011
This is to be a community project on theme's. Anyone with any information on theming, please feel free to post. If you post a how to I will try to update OP with a link to the post. If you come across anything on theming while adventuring threw the internet please post in thread and again I will update the OP as I have time.
Post 6: A How-To Post by KTT16
http://forum.xda-developers.com/showpost.php?p=19556664&postcount=6
What's Included in post:
1)How to Change Boot Logo and Boot Animation
2)How to Theme BlurPhone.apk
3)How to Theme Parts of the Notification Drop Down
4)How to Change Contacts Image in Contacts list
5)How to Change Notification Delete Button
6)How to Change Settings Images
7)How to Change Pop-Up Window Radio Button and Top Bar
8)How to Theme The WIFI-3G-Signal Icons
9)How to Get a Themed Swype
Post 26: BlurDialer.apk Theming Post by Medicstuder
http://http://forum.xda-developers.com/showpost.php?p=19998441&postcount=26
Post 30: More info on Bootanimations Post by Admirlj21 http://forum.xda-developers.com/showpost.php?p=20064730&postcount=30
Icon List by Falloutboy2000
http://forum.xda-developers.com/showthread.php?t=824656
Guide to learn to theme by theimpaler747
http://forum.xda-developers.com/showthread.php?t=916814
Link to XDA's Theme Area
http://forum.xda-developers.com/forumdisplay.php?f=527
If you use any of the links please hit the thanks button on the appropriate thread/post of the original author helped you out. If you use someone's work please ask for permission first. Don't forget the thanks button. Again if you have info to add please post a link and I will update OP when I have time and feel free to post anything that has to do with theming. Please don't forget to rank this thread if it help's you.
Special shout out to KTT16 and Admiralj21. It has been great working with you two and thank you for all your hard work and kind words. You two are great examples of what this community is all about.
MedicStuder said:
Hello Community,
Let me start by saying that I still a noob at theming but thought I would post a small tutorial on how I themed the BlurDialer.apk. Anyone else that has done theming please feel free to add input tips and tricks. Hopefully we ccan make this a great how to that might get stickied. Remember I am still learning also. this will be a simple how-to. I know there is a lot more to theming and I will update as I figure things out. So here we go.
Tools used: 7-zip and GIMP 2.6 (google for downloads)
1) Install 7-zip and GIMP 2.6.
2)Download the apk you want to theme.
3) Right click on the apk and navagate to 7-zip then extract. (I recommend desktop) Make sure you leave the orginal apk intact. VERY Important!!!
4)Open the extracted file. Leave META-INF alone. There should be a file named res. Open it.
5)Inside res you will find a few files. Inside a lot of the files are the png files.
6)Using GIMP make the changes to the pngs that you want to theme.
7)When done theming re-open the original apk file using 7-zip.
8)Now copy the new res file into the 7-zip window. This will update the current file in the archieve.
9)Install apk file and enjoy your new theme.
Let me say this sounds easier said then done. If you are porting over a theme it may take longer as file names are different from each device. The reason to keep the original apk intact is so you don't have to resign it when you are done. That makes things a lot easier. Feel free to ask any questions, justt remember I am still learning. Please google for answers as that is what I have done to learn what I have. Like I said above anyone currently theming please feel free to add any tips and tricks.
If you do use anyone else's work please ask for permission first and don't forget to give credit where credit is due. If this helps you at all please don't forget the thanks button.
Click to expand...
Click to collapse
Anything helps I been to theme a rom for a couple days but can't get it to compile
Sent from my MB855 using xda premium
edward.hidalgo said:
Anything helps I been to theme a rom for a couple days but can't get it to compile
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Is a rom u made or one u downloaded?
If one u downloaded use 7zip to extract the framework and systemui apks. Then use 7zip again to extract the contents of each apks. Then when done theming copy files back into original apks then copy apks back into zip file. You shouldnt have to complie unless its your own ROM.
Sent from my MB855 using xda premium
If someone could please add in how to change the font color. That is one thing i cant figure out. Thanks.
Sent from my MB855 using xda premium
And how to change the font color of the font of the keyboard itself please.
Sent from my MB855 using XDA App
THIS POST WILL BE SPECIFIC HOW TO'S
I AM A NOOB: I don't pretend to know what I'm doing, because I don't. This post is for people like me that need visuals or step-by-step guides without all the jargon. The hope is that I'll be adding stuff so that we all become good at themeing, and can help each other out! If you have any questions or can improve on my methods, then please let me know, and post your method here too! Disclaimer: If you brick your phone, I am in no way responsible!
-------------------
1 - HOW TO CHANGE BOOT LOGO AND BOOT ANIMATION - Thanks to thewarhawk
FOR BOOT LOGO (prior to bootanimation)
What you'll need:
Image Editor - I used Photoshop
Binary Editor (I used FHRED -- it's free)
Fastboot
Logo-header
Creating Your Logo
First: Open up your image editor, and make your boot image the dimensions must be 540x960. Important: you must flip the image vertically (so that it is upside down).
Second: Save your boot logo as a .BMP file, but it must be saved in 565 format. To do this in photoshop, save as the BMP file, then when the extra options come up push the advanced modes button, and select the R5 G6 B5 option.
Third: Open up the .BMP file with your binary editor (FHRED) and delete the first 70 Bits (pairs of numbers), and the last 2 bits (with FHRED, just highlight and hit delete)
Fourth: Copy the header from the linked logo-header file and paste it at the top of your bin. Your file should be 1036820 bits. Save as logo.bin.
Applying a Logo
Fifth: Unzip fastboot and move your newly created logo.bin to the same directory.
Sixth: put your phone in fastboot by booting the phone holding the volume down, and then once you see fastboot on the screen, press voume up. connect your phone and open command prompt and use the cd command to navigate to where your fastboot and logo.bin is and enter:
fastboot flash logo logo.bin
fastboot reboot
ENJOY!!!
Disclaimer: I am in no way responsible for any bricked phones
_________
FOR BOOTANIMATION:
Step 1: Create a series of images that will be your animation. Dimensions (540x960) and name each of them in sequential order. I used _00001.jpg as the numbering method. I ended up going up to _00010.jpg and then looped the animation.
Step 2: You'll need to edit the desc.txt so it'll play your animation as you want. When you open it, there are lines that describe everything. I just haven't figured out where to put the sounds...(I prefer that my phone load up silent anyway...) If you notice, in the text, you can call out specific folders (which you can rename to anything..I've kept it as sprint had). In the file it'll show you how to loop the animation (repeat count) I've chosen 0 for the animation part so it'll loop until the phone completely boots. You can keep playing around with timing and frames/sec...so you can essentially make a movie out of it.
Step 3: Zip your folders containing your images and your desc.txt in one .zip file. DO NOT COMPRESS IT. When saving it choose STORE as the compression mode. Name this file bootanimation.zip and save to your SD-Card on your phone
Step 4: Using Root Explorer, go into System/Media. Click on Mount as R/W. Then rename the current bootanimation.zip to bootanimation.zip.bak to save it if you want. Next, move the bootanimation.zip you created into that /media folder. You'll need to change the permissions by long pressing the file. rw-r-r
Click OK
Step 5: Reboot! Enjoy!
-------------------
2 - HOW TO THEME BLURPHONE.APK (Since MedicStuder themed the Dialer 1st, I'll leave it to him to show you guys )
{
"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"
}
There are three main parts to the "In-Call" status (this is when you are making a phone call) which I've labeled with red numbers
1) Unknown/known caller image
2) In-call options section
3) In-call background
- The first thing you need to do is to copy the BlurPhone.apk to your desktop from your phone
- Make a copy of it for safekeeping if you mess up
- With the copy you want to edit, use 7zip to "open archive" and you'll see a folder called "res"
- Copy this res folder to the desktop and keep the 7 zip archive open
- You should have these folders side by side (one which you'll edit with - the desktop one, and one that you'll save the edited files over - the 7zip archive)
- Open both res folders and each should have many folders within. The important ones are "drawable" and "drawable-hdpi" and ignore the rest of them
- Open both "drawable" folders so they are side by side
- In the Desktop "drawable" folder, there is bg_in_call - Double click on it to open it in your Photo-editor..I used Photoshop. I created a new layer over this one, blacked it out using the bucket, and Merged the layers. I think when working with PNG files don't flatten them, or you'll probably get the stupid white background to show..I digress.
- subchrome - Search for this image. Open it. I noticed a transparent line above it, but didn't do anything about it the first time I did this and had to do this all over again...that transparent line will cause a visible separation between the background where it says "Connected" and the Duration of Call. So, when I fixed it, I essentially closed the gap by painting over it. Remember, layer on top and then merge down.
- incall_bkgnd - This is where the "options" part is, where you can end the call, go to the dialpad, etc. - Again, with this PNG file, do not flatten it. All I did was delete all the squares except for the end button and changed it's color...simple enough right?
- Now, select all images, or just the one's you've edited and drag them over the 7zip archive ones to overwrite them.
- Close the archive window.
- Open up "drawable-hdpi" folders in both the desktop and 7zip archive so they are side by side
- incall_bkgnd - Look familiar? Change that one again
- ic_pane_unknown_caller - Change this as you want! I took Alien-Theme's and made it blue to go with my battery/dialer
- ic_pane_contact_photo - I made it the same as the unknown caller image
- subchrome - same as before
- bg_in_call - same as before
- Now, as before, save it and copy them over to the 7zip archive in the same "drawable-hdpi" folder to overwrite them.
- Close the archive window
So, if you want the in-call status to update, follow these steps:
- MAKE A NANDROID BACK UP FIRST!!!!!!
- Move the Phone.apk to the /system/app/ folder and overwrite the existing BlurPhone.apk
- YOU WILL FORCE CLOSE. Tap the force close a few times.
- Pull battery
- Power up
- Once the phone boots up, you will get a couple force closes, don't worry about it.
- Go to file manager (In this case I use Root Explorer) and go to /system/app/
- Find the BlurPhone.apk file and change the permissions to rw-r-r and then hit OK
- Reboot and enjoy!
-------------------
3 - HOW TO THEME PARTS OF THE NOTIFICATION DROP DOWN - Thank you to: on21st at: http://forum.xda-developers.com/showthread.php?t=1213071&highlight=
Hi everyone, I'm learning bit by bit here. I've found ways to edit some parts of the notification drop down and will be updating this very soon.
There are a few main parts of the notification drop down that I started out with cuz I hate this navy blue crap that this phone has going on:
1 - Title bar
2 - Background
3 - I call it the handle, but yeah whatever that's called
----
Important - Make a nandroid backup first! I am not responsible if you mess up!!
Start by copying the framework-res.apk and SystemUI.apks to your computer
To change the Title Bar Color
- Extract SystemUI.apk so you have a folder you can play with and edit.
- Open up the SystemUI.apk (that you've copied to your desktop) in 7zip by "open archive"
- Open up Drawable-hdpi folders in both the archive and the desktop folder so you have them side by side
- Find title_bar_portrait.9.png
- Open it in Photoshop or another editor - Here, I've made it completely black (I think it might still be transparent, so I'm gonna change it a bit more)
- Save and copy it over to the 7zip archive drawable-hdpi folder so it overwrites the archive
- Close the archive
- Upload the new SystemUI.apk to your sd card
- Move it to system/media
- Change the permission to rw-r-r
- Move to system/app overwriting your old one (You saved a copy of it though, didn't you?)
- Reboot and enjoy!
To change the NOTIFICATION BACKGROUND
- Extract framework-res.apk so you have a folder you can play with and edit.
- Open up the framework-res.apk (that you've copied to your desktop) in 7zip by "open archive"
- Open up Drawable-hdpi folders in both the archive and the desktop folder so you have them side by side
- Find status_bar_background.png
- Open it in Photoshop or another editor - Here, I've made it more transparent by changing the opacity to I think 70%
- Save and copy it over to the 7zip archive drawable-hdpi folder so it overwrites the archive
- Close the archive
- Upload the new framework-res.apk to your sd card
- Move it to system/media
- Change the permission to rw-r-r
- Move to system/framework overwriting your old one (You saved a copy of it right????)
- Reboot and enjoy!
To change the NOTIFICATION HANDLE
- Extract SystemUI.apk so you have a folder you can play with and edit.
- Open up the SystemUI.apk (that you've copied to your desktop) in 7zip by "open archive"
- Open up Drawable-hdpi folders in both the archive and the desktop folder so you have them side by side
- Find status_bar_close_on.9.png
- Open it in Photoshop or another editor - Here, I've desaturated the color
- Save and copy it over to the 7zip archive drawable-hdpi folder so it overwrites the archive
- Close the archive
- Upload the new SystemUI.apk to your sd card
- Move it to system/media
- Change the permission to rw-r-r
- Move to system/app overwriting your old one (You saved a copy of it though, didn't you?)
- Reboot and enjoy!
4 - HOW TO CHANGE CONTACT IMAGE IN CONTACTS LIST
- Extract framework-res.apk so you have a folder you can play with and edit.
- Open up the framework-res.apk (that you've copied to your desktop) in 7zip by "open archive"
- Open up Drawable-hdpi folders in both the archive and the desktop folder so you have them side by side
- Find ic_contact_picture.png - There are 3 of them
- Open it in Photoshop or another editor
- Save and copy it over to the 7zip archive drawable-hdpi folder so it overwrites the archive
- Close the archive
- Upload the new framework-res.apk to your sd card
- Move it to system/media
- Change the permission to rw-r-r
- Move to system/framework overwriting your old one (You saved a copy of it though, didn't you?)
- Reboot and enjoy!
- Extract BlurContacts.apk so you have a folder you can play with and edit.
- Open up the BlurContacts.apk (that you've copied to your desktop) in 7zip by "open archive"
- Open up Drawable-hdpi folders in both the archive and the desktop folder so you have them side by side
- Find ic_contact_list_picture.png
- Open it in Photoshop or another editor
- Save and copy it over to the 7zip archive drawable-hdpi folder so it overwrites the archive
- Close the archive
- Upload the new BlurContacts.apk to your sd card
- Move it to system/media
- Change the permission to rw-r-r
- Move to system/app overwriting your old one (You saved a copy of it though, didn't you?)
- Reboot and enjoy!
5 - HOW TO CHANGE NOTIFICATION DELETE BUTTON
- Extract framework-res.apk so you have a folder you can play with and edit.
- Open up the framework-res.apk (that you've copied to your desktop) in 7zip by "open archive"
- Open up Drawable-hdpi folders in both the archive and the desktop folder so you have them side by side
- Find zz_moto_btn_control_remove
- Open it in Photoshop or another editor GIMP work well here..PS seems to screw with the image.
- Save and copy it over to the 7zip archive drawable-hdpi folder so it overwrites the archive
- Close the archive
- Upload the new framework-res.apk to your sd card
- Move it to system/media
- Change the permission to rw-r-r
- Move to system/framework overwriting your old one (You saved a copy of it though, didn't you?)
- Reboot and enjoy!
6 - HOW TO CHANGE SETTINGS IMAGES
- Extract Settings.apk so you have a folder you can play with and edit.
- Open up the Settings.apk (that you've copied to your desktop) in 7zip by "open archive"
- Open up Drawable-hdpi folders in both the archive and the desktop folder so you have them side by side
- Find ic_settings_(the image you want to change) - There are like 15 of them if you want the entire list
- Open it in Photoshop or another editor..GIMP works well here.
- Save and copy it over to the 7zip archive drawable-hdpi folder so it overwrites the archive
- Close the archive
- Upload the new Settings.apk to your sd card
- Move it to system/media
- Change the permission to rw-r-r
- Move to system/app overwriting your old one (You saved a copy of it though, didn't you?)
- Reboot and enjoy!
7 - HOW TO CHANGE POP-UP WINDOW RADIO BUTTON AND TOP BAR
- Extract framework-res.apk so you have a folder you can play with and edit.
- Open up the framework-res.apk (that you've copied to your desktop) in 7zip by "open archive"
- Open up Drawable-hdpi folders in both the archive and the desktop folder so you have them side by side
- Find btn_radio_on and radiobutton_on_background
- Open it in Photoshop or another editor GIMP work well here..PS seems to screw with the image.
- Save and copy it over to the 7zip archive drawable-hdpi folder so it overwrites the archive
- Close the archive
- Upload the new framework-res.apk to your sd card
- Move it to system/media
- Change the permission to rw-r-r
- Move to system/framework overwriting your old one (You saved a copy of it though, didn't you?)
- Reboot and enjoy!
- Extract framework-res.apk so you have a folder you can play with and edit.
- Open up the framework-res.apk (that you've copied to your desktop) in 7zip by "open archive"
- Open up Drawable-hdpi folders in both the archive and the desktop folder so you have them side by side
- Find popup_top_dark.9.png This is one of the .9.png's that you might need to edit with the draw9patch tool.
- Open it in Photoshop or another editor GIMP work well here..PS seems to screw with the image.
- Save and copy it over to the 7zip archive drawable-hdpi folder so it overwrites the archive
- Close the archive
- Upload the new framework-res.apk to your sd card
- Move it to system/media
- Change the permission to rw-r-r
- Move to system/framework overwriting your old one (You saved a copy of it though, didn't you?)
- Reboot and enjoy!
8 - HOW TO THEME THE WIFI-3G-SIGNAL ICONS - Please see [THEME] - Blackout - WIP
- You'll need: SystemUI.apk, 7zip, Photoshop, Illustrator or another program. In this case, I used Illustrator to build the icon since it's clean, and then imported into Photoshop
- Copy the SYSTEMUI.APK to your computer (make a copy of that just in case)
- Extract the SYSTEMUI.APK to your computer
- Open up the SYSTEMUI.apk using 7zip "open archive"
- In in the extracted folder and the 7zip folder, open up to drawable HDPI side by side - you'll see a crapload of icons
- The icons that our Photons will call for (unless you've modified the xml) are the stat_sys_ wifi_signal, stat_sys_data_, and zz_moto_stats_sys_signal_6bar... icons. I didn't call out the 4G ones, since I'm unlocked and don't care for 4G cuz it apparently sucks in Beantown.
- Each icon is 38x38 pixels..keep that in mind as you build your icons. I laid out guides in Illustrator and photoshop that allowed me to snap the drawings to the grid/guides which helped a lot.
- The colors I used to match the no-signal and not-connected were hex: 232323 and 848484. For the 3G icon, i used: 666666 to make the arrows darker than the non-connected background.
- Once I built the icons in Illustrator, I dragged them over to Photoshop, and saved as .png
- After making all the icons, I dragged them over to the open 7zip archive window (remember this is the drawable-hdpi folder)
- Click yes and close the archive when you've transferred them over
- Upload the new systemui.apk to your sd card
- Move it to system/media
- Change the permission to rw-r-r
- Move to system/framework overwriting your old one (You saved a copy of it though, didn't you?)
- Reboot and enjoy!
----
9 - HOW TO GET A THEMED SWYPE - Please see [THEME] - Blackout - WIP
Thanks to:
djdarkknight96
Dominic83
TexasRebel
THIS THREAD ROCKS: THEMED SWYPES
HOW-TO:
- Clear data from any version of swype (I used Ti-Backup to do this)
- Uninstall any version of swype you currently have (swype.apk, swype installer, and lib.swypecore.so (from system/lib)
- Reboot into recovery, wipe cache/dalvik cache
- Download any swype.apk from this dude's website
- Open it up in 7zip and remove the lib folder to your desktop
- Close the archive and rename it Swype.apk
- Open up the lib folder you saved to desktop and rename that file to: lib.swypecore.so
- Save the newly renamed Swype.apk and lib.swypecore.so to your sdcard
- Change the permissions to rw-r-r for each and move the Swype.apk to your system/app folder
- Move the lib.swypecore.so file to the system/lib folder
- Reboot
- ENJOY!!!
- FINALLY!!!
I would have to guess the keyboard font would be part of the rom so it prolly would be the same as changing the color in a themes apk. Just my guess.
Sent from my MB855 using xda premium
MedicStuder said:
I would have to guess the keyboard font would be part of the rom so it prolly would be the same as changing the color in a themes apk. Just my guess.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
I think the font color is changed through an xml file in the systemui.apk or framework-res.apk...I can't be sure, but I remember reading about it somewhere..
KTT16 said:
I think the font color is changed through an xml file in the systemui.apk or framework-res.apk...I can't be sure, but I remember reading about it somewhere..
Click to expand...
Click to collapse
I believe u r correct. My problem is i cant find a program or settings for a program that allows me to view the files so i can edit them.
Sent from my MB855 using xda premium
MedicStuder said:
I believe u r correct. My problem is i cant find a program or settings for a program that allows me to view the files so i can edit them.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
There is a program called FHRED. I've used it to make the boot splash screen. Since you're themeing, here's a thread I had in Android Forums that deals with how to make Boot Splash/Animations
Have you guys checked this? they have a four part guide..
http://forums.acsyndicate.net/forumdisplay.php/67-Tutorials
bearw815 said:
Have you guys checked this? they have a four part guide..
http://forums.acsyndicate.net/forumdisplay.php/67-Tutorials
Click to expand...
Click to collapse
Yeah, I've bookmarked this tutorial, but for someone like me, I need something even simpler. I plan on editing my 1st post in this thread with really simple HOW-TOs for the noobs like myself. Ex: HOW TO CHANGE YOUR DIALER in 5 Easy steps with photos or something...Thanks for posting it though! The smarter people who know how to follow instructions will probably benefit most! LOL!
Updated Post #6 with [HOW TO] - Create Boot animations, Boot Logos, and How to Theme the Blurphone.apk - I know it's not much folks, but it's all I've got...
KTT16 said:
Updated Post #6 with [HOW TO] - Create Boot animations, Boot Logos, and How to Theme the Blurphone.apk - I know it's not much folks, but it's all I've got...
Click to expand...
Click to collapse
Looks great man. Thanks alot.
Sent from my MB855 using xda premium
Thanks man...you got me excited about theme ing, so really, thank you...
Sent from my MB855 using xda premium
Updated Post #6 with Notification Menu! I still have a few more things that I want to change...Hope you all find it useful!
EDIT: Anyone know how to change the Notification Title (where it says "No Notification" or "ongoing") color? I'd like to make this black...Thanks!
Will post some new How-to's tonight!
- Contacts images - still having trouble with "in-dialer" contact image
- Dialer Delete arrow
- Notification Menu - Clear button
- Radio button
- Title bar image
- Changing the images in the settings menu (colorwise)
It's been a busy day!
Thank both of you for this. Ill release skinny 2 within a couple days hopefully. Id love to see some themes for it and thanks to your posts that might be possible
Sent from my MB855 using XDA App
Coming from you it means a lot. Im really still fresh at this themeing game as ive only been doing it for a few days. I hope people do use this resource and add to it...
Sent from my MB855 using xda premium
I never really cared much for theming. But i do want people to have access to themes for my roms. So you guys are doing a great job.
Sent from my MB855 using XDA App
Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you
{
"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"
}
Please read the usage instructions in post #3 and the troubleshooting in post #4 below before asking for help. Thanks
Free Changelog
Download/Install
Donate version for Windows/Mac/Linux/WSL:
Dedicated thread found here
Free Kitchen (Linux terminal):
**NOTE: The free kitchen will not work in WSL**
Download the kitchen.zip from here. Extract to a new directory.
Enter the following commands one by one pressing ENTER after each line where "/location/of/kitchen" is the directory where the kitchen lives:
Code:
cd /location/of/kitchen
./superr
Dependencies:
Java 8 or higher (8 is recommended)
Python (to run the launcher (could be bypassed by running tools/source/superr in the terminal from the main kitchen directory))
Video tutorials by @chevycam94
Credits:
@osm0sis - For Busybox Installer and Android Image Kitchen
@Chainfire - For SuperSU
@JesusFreke - For [Bak]smali
@nkk71 - For creating the TWRP minzip patch
@Captain_Throwback - For providing a pre-compiled update-binary with the minzip patch and squashing bugs
@_riddle - For oat2dex
@iBotPeaches - For Apktool
@AOSP - For zipalign, adb, aapt, img2simg, simg2img, make_ext4fs
@xpirt - for img2sdat
@bcrichster - For extensive testing
XDA:DevDB Information
SuperR's Kitchen, Tool/Utility for the XDA Community Apps
Contributors
SuperR.
Version Information
Status: Stable
Created 2017-04-27
Last Updated 2020-07-24
Usage:
Run "superr" from it's location in terminal
Create new project using the menu
Copy ROM zip into the superr_NAME directory of this tool (NAME = the name of your new project).
OR
Copy system.ext4.tar and boot.img into the superr_NAME directory of this tool.
OR
Copy system.ext4.win and boot.emmc.win into the superr_NAME directory of this tool.
OR
Copy system.img and boot.img into the superr_NAME directory of this tool.
OR
Copy official Nexus tgz into the superr_NAME directory of this tool.
OR
Copy Samsung firmware zip into the superr_NAME directory of this tool.
OR
Copy Moto firmware zip into the superr_NAME directory of this tool.
OR
Leave superr_NAME directory empty to extract from rooted device or custom recovery
Extract for new ROM from the Main menu.
Enjoy!
Example:
In your terminal, type the following where "/home/user/kitchen/" is the directory where the kitchen lives:
Code:
cd /home/user/kitchen/
./superr
NOTE: the above code is 2 separate commands and requires ENTER to be pressed after each command
OR
Double-click the superr file and choose "Run in Terminal" if your OS supports it.
Add your own device support:
Create a new project in the kitchen.
Add your files to the project directory (system.img/boot.img, system.ext4.tar, win, zip, etc.)
Extract for new rom from the menu
When asked how to get your partitions, choose detect by-name from boot.img. If it gives you an error, put a recovery.img in your project directory and choose detect mmc from recovery.img.
Enjoy
Features:
*Extract and create ROM from:
Rooted Device
Custom Recovery
Existing ROM zip
system.img/boot.img (and cache.img on Samsung devices)
system.ext4.tar/boot.img
system.ext4.win/boot.emmc.win (including multi-file *.win000, *.win001, etc)
Moto and other factory firmware zips containing sparsechunk files
cm12 + roms with sparse dat files
Zips that contain system.img and boot.img
Samsung firmware zips that contain tar.md5 file
Official Pixel/Nexus firmware tgz
Official Pixel/Nexus preview tgz
SpreadTrum firmware that includes a pac file
system directory that contains symlinks and boot.img
*Create flashable zips of many varieties including:
Full ROM
Switch between set_perm, set_metadata (KitKat+), raw_img, and sparse_dat (Lollipop+)
Kernel
Recovery
Media
app, priv-app, and framework
*Deodex the following:
Pie ROMs
Oreo ROMs
Nougat ROMs
Marshmallow ROMs
Lollipop ROMs
KitKat and earlier ROMs
*Root features:
Root/unroot
Choose SuperSU or Magisk zip (add other versions to /tools/root/root_zips directory)
Choose system OR systemless root for M+ and Samsung 5.1.1 roms (SuperSU only)
*Boot features:
Unpack/repack boot/recovery img (Big Thanks to @osm0sis for mkbootimg source!!!)
Add/remove su.d support
Add/remove insecure boot
Remove dm-verity
Remove forceencrypt
*By-name auto-detection from:
Device
Existing ROM
boot.img
kernel.elf
**OR**...manually enter it
*mmcblk auto-detection from:
recovery.img
*Kitchen updater:
View the last 3 changelogs when an update is available.
Incremental update for updating the most recent previous version
Option to check for updates when the kitchen starts
*Create system.img
*Device database for mmcblk devices (currently very small, but will grow over time)
*Add devices to the assert
*Add custom asserts
*Zipalign apks
*Debloat ROM
*Custom Debloat list support
*Remove Knox
*Add/remove busybox (Big thanks to @osm0sis for his Busybox Installer)
*Add/remove user app support (/data/app)
*Sign zips
*Translatable with language files
*Donate version additional features:
Cross-platform - Windows, WSL, Macos, Linux
tarfs - Get original permissions, contexts, and capabilities from tar/win backups.
Create system.img with identical permissions, contexts, and capabilities as the original system.img or tar/win backup.
Plugins - Probably the best part! Currently over 20 extra features and growing
Root - Use a custom root zip (not the included Magisk or SuperSU)
Custom directory - can be included in your ROM and flashed to a specified partition
Custom Signature - No Built with SuperR's Kitchen, anywhere, plus add your own
Custom Build Display in About Phone, or leave it as default
AutoROM - Automation for ROM creatiion using a congig file (there's a plugin for that)
Convert updater-script to an update-binary script
No mounting img files. One less thing requiring your password and interrupting extraction.
Upload support.zips and device.zip directly from the kitchen for review
Download language files directly from the kitchen
Restore original boot.img after modifying and repacking
Remove asserts from the updater-script
Configurable compression level for packing zips
Remove all placeholder tags (#ASSERT, #SYM, #PERM, etc.) before packing the ROM
Create ext4 img file from any partition you include in your ROM.
zipalign without building ROM
Fix ext4.img files automatically if block count is higher than actual blocks
Troubleshooting/FAQ:
When asking for help, please provide as much of the following info as possible so I can help as easily as possible. I am a busy person and would prefer not to ask all of these questions every time someone has a problem. Thank you for understanding.
What Kitchen version?
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
What device are you working on (make/model)?
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
What Android version?
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
What did you do after extracting and before building?
Were there errors on the screen if you scroll up in the terminal?
Send a recovery.log after flashing if you have problems flashing the ROM.
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
Use the support option in the Misc Tools menu and attach the support.zip to your post.
Ubuntu4Kitchen
An Ubuntu 16.04 distro with all the things you need to get the kitchen working easily.
Visit the dedicated thread here
Language Files (translations)
English - Default/Included in the kitchen
Download additional language files here
Once the language zip has been downloaded, extract to /kitchen/tools/language and restart the kitchen.
Does this kitchen support Windows CYGWIN?
CYGWIN is not supported and will not work. Try the donate kitchen for Windows, Linux, and Mac.
WSL (Bash on Ubuntu on Windows)
WSL is not supported in the free kitchen and will not work. Try the donate kitchen for Windows, Linux, and Mac.
Which perm type should I choose?
Here is a very brief summary of set_perm, set_metadata, sparse_dat, and raw_img.
set_perm : The oldest of the 4. Sets file/directory permissions when flashing a rom. Not recommended for KitKat and above.
set_metadata: Also sets file/directory permissions when flashing a rom, but also adds file contexts. It was introduced with selinux in KitKat. Recommended for KitKat and above.
sparse_dat: The newest of the 4, and only works on Lollipop +. The permissions, symlinks, and file contexts are all added inside a sparse image. A sparse image is an image with a more efficient space usage. Only for Lollipop and above. The free kitchen uses AOSP permissions/capabilities when building system.img. If your device requires different permissions, this method will not work for you in the free kitchen.
raw_img: This is literally raw images that are flashed to your device. The permissions, symlinks, and file contexts are all added inside the raw image. Works for all Android versions. The free kitchen uses AOSP permissions/capabilities when building system.img. If your device requires different permissions, this method will not work for you in the free kitchen.
Flashing error:
This package is for "xxxxx" devices; this is a "yyyyy"
The problem is the asserts and it is easy to fix. In the kitchen menu, go to ROM Tools > Asserts > Add/Remove device asserts. At the bottom it will say "xxxxx". Edit the line to say "xxxxx,yyyyy" and press enter. Build your rom again and flash.
Why is my ROM zip so small?
blkdiscard failed: Invalid argument
These are generally due to the partition size detection method. You need the correct partition size for ALL partitions you are creating sparse dat and raw_img images for. The kitchen will ask for each one that is included in your rom when you choose to build the full rom zip. If none of the provided auto-detect methods work, you will need to find the partition size on your own and enter it manually in the kitchen.
Root problems?
You can replace the SuperSU.zip and Magisk.zip in the kitchen with any flashable SuperSU/Magisk version you want. It is located in kitchen/tools/root/root_zips. Delete the one that is there (if it exists) and add yours. Then, unroot, re-root and your replacement will be used.
Auto check for updates when kitchen starts
To enable the auto update check, go to "Check for updates" in the main menu. After it checks, you will be asked if you want to enable it.
I added root and busybox but there is no su or busybox in my project. Why?
The kitchen does not add Busybox or SuperSU/Magisk files to the project. Instead it adds flashable zips inside the rom.zip. There are many variables to deal with (Android version, device architecture, manufacturer, system/systemless, etc.). Flashing the zips with the rom accounts for all of these variables and there is no reason to re-invent the wheel.
Debloat and custom debloat
There are 2 options in the debloat menu (besides knox which is self explanatory):
1) Debloat ROM
This option removes all files included in the kitchens standard bloat list file - /kitchen/tools/root/bloat
2) Custom Debloat
This option removes all files included in the bloat_custom file - /kitchen/tools/root/bloat_custom OR kitchen/superr_project/00_project_files/bloat_custom
This file is empty by default and is there for you to add whatever you want to remove. You can either add everything you want to remove and use only option 2, or you can add new files here and use option 1 and 2.
I suggest you take a look at /kitchen/tools/root/bloat to see the format of the listed bloat files. Use the same format for the bloat_custom file.
When you use either option, the files are not deleted. Instead they are moved to the 00_project_files directory in case you want to restore them later.
Deodexing
Deodexing Samsung roms may or may not work. If your rom does not boot after deodexing, try it without. If it works and you must deodex your rom, try a different tool. I hear svadev deodex tool works well for Samsung roms.
boot.img errors
If the kitchen gives you errors about unpacking boot.img, there is a good chance I will not be able to help. I suggest you figure out how to unpack it using Linux commands/binaries and let me know how you did it. You may also find a tutorial about how to unpack your boot.img. If so, please send a link. It does not help me to know another tool works. I need the commands/binaries used in order to update the kitchen.
Feel free to upload your boot.img AND the build.prop from the same rom so I can check to see if I can fix it. I will ignore you if you don't upload both mentioned files
I do not answer support questions through PM. There are no exceptions. Post in the thread if you want help so others can give suggestions and learn from your solution
I will not answer questions if it is clear that you have not read the OP, the info posts after the OP, and searched the thread for answers. I do not have time to answer the same questions over and over. Many questions are already answered in this thread and if you want help, I expect you to try and solve it on your own before posting. If your question has not been answered in the thread, I am happy to assist in any way possible.
If I ask you to upload files, they need to be uploaded on a server that does not require registration for full speed downloads, or registration for downloads at all. Drive, Dropbox, AFH, and Mega are examples of acceptable servers. There are many other good ones, but I hope you get the point.
Thanks for understanding
reserved
Looks promissing, gonna try it asap :good:
I suppose it to work for many devices but are there any already tested for?
Looks great mate. Can't wait to give it a go
Its been an honor, testing this out! This deserves to be stickied!!
Sent from my N9510 using Tapatalk
---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------
Androidwizzard said:
Looks promissing, gonna try it asap :good:
I suppose it to work for many devices but are there any already tested for?
Click to expand...
Click to collapse
Zte Concord 2
Zte Warp4G
Moto E 2015
LG Exceed 2
LG Realm
Still waiting on results from:
MediaTEK VKworld (VS6050S)
SuperR. said:
Disclaimer: I am not responsible for anything bad that may occur from the use of this tool, but I will take all the credit you can give me if it works for you
Sent from my N9510 using Tapatalk
Click to expand...
Click to collapse
Nice and finally something for Linux. To bad I'm out of town can't wait to test this...
Nice work
Sent from my SM-G928T using Tapatalk
bcrichster said:
Its been an honor, testing this out! This deserves to be stickied!!
Sent from my N9510 using Tapatalk
---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------
Zte Concord 2
Zte Warp4G
Moto E 2015
LG Exceed 2
LG Realm
Still waiting on results from:
MediaTEK VKworld (VS6050S)
SuperR. said:
Disclaimer: I am not responsible for anything bad that may occur from the use of this tool, but I will take all the credit you can give me if it works for you
Sent from my N9510 using Tapatalk
Click to expand...
Click to collapse
Think it needs to be in xda portal as well
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
I'll give it a shot on Samsung Galaxy Note 5 - if there aren't any objections against @SuperR.
Is portal different than Chef Central?
Sent from my N9510 using Tapatalk
bcrichster said:
Is portal different than Chef Central?
Sent from my N9510 using Tapatalk
Click to expand...
Click to collapse
Xda portal is video review and goes on xda Facebook as well
Sent from my SM-N920C using Tapatalk
Androidwizzard said:
I'll give it a shot on Samsung Galaxy Note 5 - if there aren't any objections against @SuperR.
Click to expand...
Click to collapse
Right on, should have Knox removal as well. By all means, plz report back
Sent from my N9510 using Tapatalk
Good! I can test with a mtk6582 device with lollipop stock rom... sounds great!! SUPPORT!
Regarding MTK devices, I have never owned one so I am totally unfamiliar with special requirements they may need. I will add support for everything I can as issues come up
SuperR. said:
Regarding MTK devices, I have never owned one so I am totally unfamiliar with special requirements they may need. I will add support for everything I can as issues come up
Click to expand...
Click to collapse
I think you need to add mkbootimg ( https://github.com/osm0sis/mkbootimg ) for work with mtk based boot.img and maybe edit the img extraction of stock imgs.... I dont't now bro, you're the chef hahaha
Regards and support
duniel said:
I think you need to add mkbootimg ( https://github.com/osm0sis/mkbootimg ) for work with mtk based boot.img and maybe edit the img extraction of stock imgs.... I dont't now bro, you're the chef hahaha
Regards and support
Click to expand...
Click to collapse
This kitchen already uses Android Image Kitchen by osm0sis, which includes his mkbootimg. Maybe it will already work for MTK. Let me know if you encounter problems.
SuperR. said:
This kitchen already uses Android Image Kitchen by osm0sis, which includes his mkbootimg. Maybe it will already work for MTK. Let me know if you encounter problems.
Click to expand...
Click to collapse
Yes, It should work.
When I try with my device I'll tell you the results
Regards
Anyone know what is trim.txt on bootanimation?
can anyone explain how to use it and how to make it ?
Because I see the PA (Paranoid Android) rom bootanimation using trim.txt
You can download from here https://github.com/AOSPA/android_vendor_aospa/tree/sapphire/apex/bootanimation/media
in the folder there are also images that do not use a background
Is there anyone here who can explain in detail to me? Or can you make me a video how to use it until it bootanimation ?
The documentation is here: https://android.googlesource.com/platform/frameworks/base/+/master/cmds/bootanimation/FORMAT.md
I tried to get trim.txt to work but even when you specify background in desc.txt it doesn't seem to work, at least on my system.
Although I looked in bootanimation -> libbootanimation.so and it seems to support trim.txt
Edit: So I solved it. None of the files inside the bootanimation.zip may be compressed.
The PNG files obviously don't need it, but if the text files (like trim.txt) are compressed they will be ignored.
Usually desc.txt is so small that it will not be compressed, but while trim.txt is longer (and repetitive) it could be compressed.
Easy (-est) solution if your zipper is stuck? Rename trim.txt -> trim.jpg, compress as usual, then hexedit the zip in two places to turn jpg into txt.
The attached file is an example of trim'ed animation. It's designed for 1072x1448 so smaller screens will not see anytihng.
OTOH, this will work with any size display if you adjust the numbers in trim.txt
(It shows a countup in the lower right corner.)
Hello guys,
After a little research, I have successfully ported MIUI 13 (v22.2.17) to Mi 8. I do not have any permissions to share the changed files as a rom, so I am writing this guide. I hope it will help
TO BEGIN WITH, WE NEED TO DOWNLOAD THE FOLLOWING FILES:
1) MIUI 13.0.10 for Mi 8
2) POCO OS for Pocophone F1 (choose the latest)
3) A custom kernel (personally, I prefer No Gravity Kernel v2.4.1)
4) An image extractor you prefer (Brotli Extractor, Jancox Tool, etc.)
AND HERE WE START:
--> Firstly, we extract the 2nd zip file using the image extractor (4) [vendor patch]
--> While waiting, we extract the same zip (the 2nd one) with a common extractor (such as WinRAR) and take system.img and boot.img [base "system" and "boot"]
--> Then, we extract the 1st zip and take vendor.new.dat.br, vendor.patch.dat, and vendor.transfer.list and META-INF and we navigate to META-INF/com/google/android and edit updater-script replacing the following lines: [base "vendor"]
Code:
ui_print("Patching vendor image unconditionally...");
show_progress(0.500000, 0);
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
set_progress(1.000000);
When done, we add the above vendor files and META-INF folder to (another) archive
--> When the extraction with the image extractor (4) finishes, we navigate to vendor and copy the following folders [vendor patch continue]:
* overlay
* etc/selinux
IN THE END WE HAVE...
> To flash system.img as image ["base system" step]
> To flash the .zip archive which only contains the vendor files (and, obviously, "META-INF") ["base vendor" step]
> To mount "/vendor", to delete the folders "overlay" and "etc/selinux" and, then, to replace these from the ["vendor patch continue" step]
> To flash the extracted boot.img ["base boot" step]
> (And, finally,) to flash the custom kernel (3), which makes the rom bootable.
Due to deodex, the whole boot should be finished in approximately 4 minutes
MISSING FEATURES:
> No NFC support
> No multilingual rom (but there are also some MIUI R roms here)
SPECIAL THANKS TO:
> romKTpro (for POCO OS)
> UOTAN (for vendor files)
> Tech Karan (for his similar guide)
> and to all the other developers who made the required and useful tools and mods
Link for this this "Tech Karan (for his similar guide)"?
I was able to install it mate thanks.
Working fine, very smooth.
Mi Login doesnt work tho, which i dont mind.
nsfnd said:
Link for this this "Tech Karan (for his similar guide)"?
Click to expand...
Click to collapse
You are right, sorry for forgetting this link. I have just edited the first post
nsfnd said:
I was able to install it mate thanks.
Working fine, very smooth.
Mi Login doesnt work tho, which i dont mind.
Click to expand...
Click to collapse
Yes, I have found this bug, too. This happens because there is the same one on Poco F1 (base rom).
Also, there are some missing applications, which can be installed as normal .apk files from APKMirror:
-> Mi Browser
-> Mi Cleaner
-> Mi Scanner
They made an Android 12, MIUI 13 version for Poco F1.
I tried to do the same technic explained above for that.
But Jancox Tools failed to extract with errors.
(imgextractor.py and ext4.py, NameError: name 'xattr' is not defined)
Link for the rom.
PocoOs Stable Channel (Official)
╭━┳━┳━┳━╮╭━┳━━╮ ┃╋┃┃┃╭┫┃┃┃┃┃━━┫ ┃╭┫┃┃╰┫┃┃┃┃┣━━┃ ╰╯╰━┻━┻━╯╰━┻━━╯ MIUI 13.0.4 EU rom Based on Android 12, Code name:Ignition🔥 ======================= Maintained by @facerracer4u ======================= About PocoOs: PocoOs comes with all poco standards We do not include harmful mods, and we...
t.me
Maybe you want to check it out.
Unfortunately, we have to make a compatible vendor.img for Mi 8. Otherwise, every MIUI 13 (Android 12) ROM cannot be booted (the existing vendor files are compatible with Android 11 MIUI ROM's). I will try to port /vendor, but I am not promising anything
At least, there is a compatible kernel (No Gravity v3.x.x)
Edit: NoGravityKernel does not support /system_ext (so for most MIUI S ROM's it is not compatible)
OK, ιt's been a long time since my last post, but I have found a bootable Android 12 version of MIUI 13, but I have not managed to fix the common bugs from Pocophone F1:
<!> audio
<!> camera
<!> slow motion while watching videos (due to the audio bug)
Also, this ROM does not have NFC support (Poco F1 does not come with)
In order to install it, I have flashed:
-> the ROM (by deleting the first line in /META-INF/com/google/android/updater-script
-> permissiver v5
-> dfe (disable forced encryption)
-> XDKernel-2.6
Camera is now fixed, after replacing some vendor files (there is no need to chmod):
Code:
vendor/etc/camera/age_gender_bg
vendor/etc/camera/beauty_ui9_intelligent_params.config
vendor/etc/camera/camxoverridesettings.txt
vendor/etc/camera/crown_156_128.bin
vendor/etc/camera/dualcamera.png
vendor/etc/camera/eyelineblush.cng
vendor/etc/camera/face_goodly_208_180
vendor/etc/camera/face_ravishing_238_224
vendor/etc/camera/face_splendid_274_200
vendor/etc/camera/female_bg.png
vendor/etc/camera/female_icon.png
vendor/etc/camera/hdr_ui9_params.config
vendor/etc/camera/lf_facerank_model.bin
vendor/etc/camera/male_bg.png
vendor/etc/camera/male_icon.png
vendor/etc/camera/Miui-Light.ttf
vendor/etc/camera/MIUI_Time.ttf
vendor/etc/camera/people_gender.dat
vendor/etc/camera/score_bg.png
vendor/etc/camera/score_icon.png
vendor/etc/camera/sdm_ys_32p_120_21_5_perturb50.bin
vendor/etc/camera/watermark_font_2300_3199.dat
vendor/lib/camera/com.qti.sensor.imx363.so
vendor/lib/camera/com.qti.sensor.ov7251.so
vendor/lib/camera/com.qti.sensor.s5k3m3.so
vendor/lib/camera/com.qti.sensor.s5k3t1.so
vendor/lib/camera/com.qti.sensormodule.imx333.bin
vendor/lib/camera/com.qti.sensormodule.imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx333.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.ov7251.bin
vendor/lib/camera/com.qti.sensormodule.s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1_qtech.bin
vendor/lib/camera/com.qti.tuned.default.bin
vendor/lib/camera/com.qti.tuned.liteon_imx363.bin
vendor/lib/camera/com.qti.tuned.liteon_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.qtech_s5k3t1.bin
vendor/lib/camera/com.qti.tuned.semco_imx363.bin
vendor/lib/camera/com.qti.tuned.semco_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.sunny_ov7251.bin
vendor/lib/camera/com.qti.tuned.sunny_s5k3t1.bin
vendor/lib/camera/components/com.arcsoft.node.capturebokeh.so
vendor/lib/camera/components/com.arcsoft.node.capturefusion.so
vendor/lib/camera/components/com.arcsoft.node.hdr.so
vendor/lib/camera/components/com.arcsoft.node.hdrchecker.so
vendor/lib/camera/components/com.arcsoft.node.realtimebokeh.so
vendor/lib/camera/components/com.arcsoft.node.skinbeautifier.so
vendor/lib/camera/components/com.arcsoft.node.smoothtransition.so
vendor/lib/camera/components/com.arcsoft.node.superlowlight.so
vendor/lib/camera/components/com.mi.node.aiadd.so
vendor/lib/camera/components/com.mi.node.aiasd.so
vendor/lib/camera/components/com.qti.eisv2.so
vendor/lib/camera/components/com.qti.eisv3.so
vendor/lib/camera/components/com.qti.hvx.addconstant.so
vendor/lib/camera/components/com.qti.hvx.binning.so
vendor/lib/camera/components/com.qti.node.dummyrtb.so
vendor/lib/camera/components/com.qti.node.dummysat.so
vendor/lib/camera/components/com.qti.node.eisv2.so
vendor/lib/camera/components/com.qti.node.eisv3.so
vendor/lib/camera/components/com.qti.node.gpu.so
vendor/lib/camera/components/com.qti.node.memcpy.so
vendor/lib/camera/components/com.qti.node.photosolid.so
vendor/lib/camera/components/com.qti.node.remosaic.so
vendor/lib/camera/components/com.qti.node.sr.so
vendor/lib/camera/components/com.qti.node.swregistration.so
vendor/lib/camera/components/com.qti.node.watermark.so
vendor/lib/camera/components/com.qti.node.xiaomigenderage.so
vendor/lib/camera/components/com.qti.stats.aec.so
vendor/lib/camera/components/com.qti.stats.aecwrapper.so
vendor/lib/camera/components/com.qti.stats.af.so
vendor/lib/camera/components/com.qti.stats.afd.so
vendor/lib/camera/components/com.qti.stats.asd.so
vendor/lib/camera/components/com.qti.stats.awb.so
vendor/lib/camera/components/com.qti.stats.awbwrapper.so
vendor/lib/camera/components/com.qti.stats.pdlib.so
vendor/lib/camera/components/com.qti.stats.pdlibsony.so
vendor/lib/camera/components/com.qti.stats.pdlibwrapper.so
vendor/lib/camera/components/com.vidhance.node.eis.so
vendor/lib/camera/components/com.xiaomi.node.mibokeh.so
vendor/lib/camera/components/etc/GpuKernelRepo.pb
vendor/lib/camera/components/etc/model_back.dlc
vendor/lib/camera/components/etc/model_front.dlc
vendor/lib/camera/components/etc/morpho_lowlight4.0.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high_1.xml
vendor/lib/camera/fdconfigpreview.bin
vendor/lib/camera/fdconfigpreviewlite.bin
vendor/lib/camera/fdconfigvideo.bin
vendor/lib/camera/fdconfigvideolite.bin
vendor/lib/hw/camera.qcom.so
vendor/lib/hw/com.qti.chi.override.so
vendor/lib/libarcsoft_beautyshot.so
vendor/lib/libarcsoft_dualcam_image_optical_zoom.so
vendor/lib/libarcsoft_dualcam_refocus.so
vendor/lib/libarcsoft_dualcam_refocus_front.so
vendor/lib/libarcsoft_dualcam_refocus_rear_t.so
vendor/lib/libarcsoft_dualcam_refocus_rear_w.so
vendor/lib/libarcsoft_dualcam_video_optical_zoom.so
vendor/lib/libarcsoft_high_dynamic_range.so
vendor/lib/libarcsoft_low_light_hdr.so
vendor/lib/libarcsoft_portrait_lighting.so
vendor/lib/libarcsoft_portrait_lighting_c.so
vendor/lib/libarcsoft_supernight.so
vendor/lib/libc++_shared.so
vendor/lib/libcamera_dirty.so
vendor/lib/libcamera_scene.so
vendor/lib/libcamxfdalgov7.so
vendor/lib/libcamxfdengine.so
vendor/lib/libcamxstatscore.so
vendor/lib/libcamxtintlessalgo.so
vendor/lib/libcom.qti.chinodeutils.so
vendor/lib/libFaceGrade.so
vendor/lib/libft2vendor.so
vendor/lib/libHalSuperSensorServer.so
vendor/lib/libmibokeh_845.so
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libmmcamera_faceproc2.so
vendor/lib/libmpbase.so
vendor/lib/libnanopb.so
vendor/lib/libremosaic_daemon.so
vendor/lib/libSNPE.so
vendor/lib/libSuperSensor.so
vendor/lib/libSuperSensorCPU.so
vendor/lib/libswregistrationalgo.so
vendor/lib/libsymphony-cpu.so
vendor/lib/libsymphonypower.so
vendor/lib/libtonemapalgo.so
vendor/lib/libvidhance.so
vendor/lib/libXMFD_AgeGender.so
vendor/lib/lib_denoiser3.so
vendor/lib/mibokeh_845_opencl.bin
vendor/lib64/libcamxfdalgov7.so
vendor/lib64/libcamxfdengine.so
vendor/lib64/libcamxstatscore.so
vendor/lib64/libnanopb.so
vendor/lib64/libremosaiclib.so
vendor/lib64/libremosaic_daemon.so
vendor/firmware/bu64748gwz.prog
vendor/firmware/CAMERA_ICP.elf
vendor/firmware/dipper_ois.coeff
vendor/firmware/dipper_ois.prog
vendor/firmware/dipper_ois_liteon.coeff
vendor/firmware/dipper_ois_liteon.prog
Advanced Gears said:
Camera is now fixed, after replacing some vendor files (there is no need to chmod):
Code:
vendor/etc/camera/age_gender_bg
vendor/etc/camera/beauty_ui9_intelligent_params.config
vendor/etc/camera/camxoverridesettings.txt
vendor/etc/camera/crown_156_128.bin
vendor/etc/camera/dualcamera.png
vendor/etc/camera/eyelineblush.cng
vendor/etc/camera/face_goodly_208_180
vendor/etc/camera/face_ravishing_238_224
vendor/etc/camera/face_splendid_274_200
vendor/etc/camera/female_bg.png
vendor/etc/camera/female_icon.png
vendor/etc/camera/hdr_ui9_params.config
vendor/etc/camera/lf_facerank_model.bin
vendor/etc/camera/male_bg.png
vendor/etc/camera/male_icon.png
vendor/etc/camera/Miui-Light.ttf
vendor/etc/camera/MIUI_Time.ttf
vendor/etc/camera/people_gender.dat
vendor/etc/camera/score_bg.png
vendor/etc/camera/score_icon.png
vendor/etc/camera/sdm_ys_32p_120_21_5_perturb50.bin
vendor/etc/camera/watermark_font_2300_3199.dat
vendor/lib/camera/com.qti.sensor.imx363.so
vendor/lib/camera/com.qti.sensor.ov7251.so
vendor/lib/camera/com.qti.sensor.s5k3m3.so
vendor/lib/camera/com.qti.sensor.s5k3t1.so
vendor/lib/camera/com.qti.sensormodule.imx333.bin
vendor/lib/camera/com.qti.sensormodule.imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx333.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.ov7251.bin
vendor/lib/camera/com.qti.sensormodule.s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1_qtech.bin
vendor/lib/camera/com.qti.tuned.default.bin
vendor/lib/camera/com.qti.tuned.liteon_imx363.bin
vendor/lib/camera/com.qti.tuned.liteon_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.qtech_s5k3t1.bin
vendor/lib/camera/com.qti.tuned.semco_imx363.bin
vendor/lib/camera/com.qti.tuned.semco_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.sunny_ov7251.bin
vendor/lib/camera/com.qti.tuned.sunny_s5k3t1.bin
vendor/lib/camera/components/com.arcsoft.node.capturebokeh.so
vendor/lib/camera/components/com.arcsoft.node.capturefusion.so
vendor/lib/camera/components/com.arcsoft.node.hdr.so
vendor/lib/camera/components/com.arcsoft.node.hdrchecker.so
vendor/lib/camera/components/com.arcsoft.node.realtimebokeh.so
vendor/lib/camera/components/com.arcsoft.node.skinbeautifier.so
vendor/lib/camera/components/com.arcsoft.node.smoothtransition.so
vendor/lib/camera/components/com.arcsoft.node.superlowlight.so
vendor/lib/camera/components/com.mi.node.aiadd.so
vendor/lib/camera/components/com.mi.node.aiasd.so
vendor/lib/camera/components/com.qti.eisv2.so
vendor/lib/camera/components/com.qti.eisv3.so
vendor/lib/camera/components/com.qti.hvx.addconstant.so
vendor/lib/camera/components/com.qti.hvx.binning.so
vendor/lib/camera/components/com.qti.node.dummyrtb.so
vendor/lib/camera/components/com.qti.node.dummysat.so
vendor/lib/camera/components/com.qti.node.eisv2.so
vendor/lib/camera/components/com.qti.node.eisv3.so
vendor/lib/camera/components/com.qti.node.gpu.so
vendor/lib/camera/components/com.qti.node.memcpy.so
vendor/lib/camera/components/com.qti.node.photosolid.so
vendor/lib/camera/components/com.qti.node.remosaic.so
vendor/lib/camera/components/com.qti.node.sr.so
vendor/lib/camera/components/com.qti.node.swregistration.so
vendor/lib/camera/components/com.qti.node.watermark.so
vendor/lib/camera/components/com.qti.node.xiaomigenderage.so
vendor/lib/camera/components/com.qti.stats.aec.so
vendor/lib/camera/components/com.qti.stats.aecwrapper.so
vendor/lib/camera/components/com.qti.stats.af.so
vendor/lib/camera/components/com.qti.stats.afd.so
vendor/lib/camera/components/com.qti.stats.asd.so
vendor/lib/camera/components/com.qti.stats.awb.so
vendor/lib/camera/components/com.qti.stats.awbwrapper.so
vendor/lib/camera/components/com.qti.stats.pdlib.so
vendor/lib/camera/components/com.qti.stats.pdlibsony.so
vendor/lib/camera/components/com.qti.stats.pdlibwrapper.so
vendor/lib/camera/components/com.vidhance.node.eis.so
vendor/lib/camera/components/com.xiaomi.node.mibokeh.so
vendor/lib/camera/components/etc/GpuKernelRepo.pb
vendor/lib/camera/components/etc/model_back.dlc
vendor/lib/camera/components/etc/model_front.dlc
vendor/lib/camera/components/etc/morpho_lowlight4.0.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high_1.xml
vendor/lib/camera/fdconfigpreview.bin
vendor/lib/camera/fdconfigpreviewlite.bin
vendor/lib/camera/fdconfigvideo.bin
vendor/lib/camera/fdconfigvideolite.bin
vendor/lib/hw/camera.qcom.so
vendor/lib/hw/com.qti.chi.override.so
vendor/lib/libarcsoft_beautyshot.so
vendor/lib/libarcsoft_dualcam_image_optical_zoom.so
vendor/lib/libarcsoft_dualcam_refocus.so
vendor/lib/libarcsoft_dualcam_refocus_front.so
vendor/lib/libarcsoft_dualcam_refocus_rear_t.so
vendor/lib/libarcsoft_dualcam_refocus_rear_w.so
vendor/lib/libarcsoft_dualcam_video_optical_zoom.so
vendor/lib/libarcsoft_high_dynamic_range.so
vendor/lib/libarcsoft_low_light_hdr.so
vendor/lib/libarcsoft_portrait_lighting.so
vendor/lib/libarcsoft_portrait_lighting_c.so
vendor/lib/libarcsoft_supernight.so
vendor/lib/libc++_shared.so
vendor/lib/libcamera_dirty.so
vendor/lib/libcamera_scene.so
vendor/lib/libcamxfdalgov7.so
vendor/lib/libcamxfdengine.so
vendor/lib/libcamxstatscore.so
vendor/lib/libcamxtintlessalgo.so
vendor/lib/libcom.qti.chinodeutils.so
vendor/lib/libFaceGrade.so
vendor/lib/libft2vendor.so
vendor/lib/libHalSuperSensorServer.so
vendor/lib/libmibokeh_845.so
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libmmcamera_faceproc2.so
vendor/lib/libmpbase.so
vendor/lib/libnanopb.so
vendor/lib/libremosaic_daemon.so
vendor/lib/libSNPE.so
vendor/lib/libSuperSensor.so
vendor/lib/libSuperSensorCPU.so
vendor/lib/libswregistrationalgo.so
vendor/lib/libsymphony-cpu.so
vendor/lib/libsymphonypower.so
vendor/lib/libtonemapalgo.so
vendor/lib/libvidhance.so
vendor/lib/libXMFD_AgeGender.so
vendor/lib/lib_denoiser3.so
vendor/lib/mibokeh_845_opencl.bin
vendor/lib64/libcamxfdalgov7.so
vendor/lib64/libcamxfdengine.so
vendor/lib64/libcamxstatscore.so
vendor/lib64/libnanopb.so
vendor/lib64/libremosaiclib.so
vendor/lib64/libremosaic_daemon.so
vendor/firmware/bu64748gwz.prog
vendor/firmware/CAMERA_ICP.elf
vendor/firmware/dipper_ois.coeff
vendor/firmware/dipper_ois.prog
vendor/firmware/dipper_ois_liteon.coeff
vendor/firmware/dipper_ois_liteon.prog
Click to expand...
Click to collapse
Well done, That's great!!!
Hoping to see a fully working android 12 and MIUI 13 soon on our MI8
So, after replacing some audio policy files from /vendor/etc, the sound comes out normally. However, I still have bugs such as slow videos and silent sounds coming as media when earphones are not connected. Are there some files at /vendor/etc to be replaced? I haven't found anything else, yet
(Also, I haven't looked for the required files for NFC support)
OK, now it's ported with no bugs.
Missing features: NFC support (Due to my inexperience, I cannot make bootable system and vendor .img files by using image kitchens and it's more difficult to set the correct permissions to files in the /bin folders from recovery)
The files to be changed are mentioned in this uploaded .txt file
Hello, again. Because the previous guides were time-consuming, I have made a patch which replaces all the required files. Unfortunately, I have not managed to add NFC support.
Instructions:
We flash system.img, vendor.img, cust.img (system_ext.img), boot.img, DFE, XD/Etude kernel
We mount /vendor
We flash the patch
Advanced Gears said:
Hello, again. Because the previous guides were time-consuming, I have made a patch which replaces all the required files. Unfortunately, I have not managed to add NFC support.
Instructions:
We flash system.img, vendor.img, cust.img (system_ext.img), boot.img, DFE, XD/Etude kernel
We mount /vendor
We flash the patch
Click to expand...
Click to collapse
Thanks for sharing your progress, its exciting indeed.
Is it possible for you in the future to share a simpler way for us non advanced users to easily upgrade to MIUI 13, e.g through recovery zip from TWRP.
Because I don't own these ROM's, please check some Telegram channels. The file name of this one (with the mentioned changes) may remind you something
Advanced Gears said:
Hello guys,
After a little research, I have successfully ported MIUI 13 (v22.2.17) to Mi 8. I do not have any permissions to share the changed files as a rom, so I am writing this guide. I hope it will help
TO BEGIN WITH, WE NEED TO DOWNLOAD THE FOLLOWING FILES:
1) MIUI 13.0.10 for Mi 8
2) POCO OS for Pocophone F1 (choose the latest)
3) A custom kernel (personally, I prefer No Gravity Kernel v2.4.1)
4) An image extractor you prefer (Brotli Extractor, Jancox Tool, etc.)
AND HERE WE START:
--> Firstly, we extract the 2nd zip file using the image extractor (4) [vendor patch]
--> While waiting, we extract the same zip (the 2nd one) with a common extractor (such as WinRAR) and take system.img and boot.img [base "system" and "boot"]
--> Then, we extract the 1st zip and take vendor.new.dat.br, vendor.patch.dat, and vendor.transfer.list and META-INF and we navigate to META-INF/com/google/android and edit updater-script replacing the following lines: [base "vendor"]
Code:
ui_print("Patching vendor image unconditionally...");
show_progress(0.500000, 0);
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
set_progress(1.000000);
When done, we add the above vendor files and META-INF folder to (another) archive
--> When the extraction with the image extractor (4) finishes, we navigate to vendor and copy the following folders [vendor patch continue]:
* overlay
* etc/selinux
IN THE END WE HAVE...
> To flash system.img as image ["base system" step]
> To flash the .zip archive which only contains the vendor files (and, obviously, "META-INF") ["base vendor" step]
> To mount "/vendor", to delete the folders "overlay" and "etc/selinux" and, then, to replace these from the ["vendor patch continue" step]
> To flash the extracted boot.img ["base boot" step]
> (And, finally,) to flash the custom kernel (3), which makes the rom bootable.
Due to deodex, the whole boot should be finished in approximately 4 minutes
MISSING FEATURES:
> No NFC support
> No multilingual rom (but there are also some MIUI R roms here)
SPECIAL THANKS TO:
> romKTpro (for POCO OS)
> UOTAN (for vendor files)
> Tech Karan (for his similar guide)
> and to all the other developers who made the required and useful tools and mods
Click to expand...
Click to collapse
Hello, is this manual suitable for mi mix 3?
Advanced Gears said:
Hello, again. Because the previous guides were time-consuming, I have made a patch which replaces all the required files. Unfortunately, I have not managed to add NFC support.
Instructions:
We flash system.img, vendor.img, cust.img (system_ext.img), boot.img, DFE, XD/Etude kernel
We mount /vendor
We flash the patch
Click to expand...
Click to collapse
Hello I am new to this, but I already have an unlocked bootloader.
Can you please confirm :-
1. Which tool I need to use to flash the ROM .img files, Xiaomi Flash Tool?
2. Which latest MIUI 13 ROM is most suitable, POCO OS •13.0.12.0 EU [ IGNITION 4.0 ].zip?
3. Which beryllium2dipper-patch.zip patch I need to use for the Mi 8?
4. Only bug is NFC right? Will audio, camera, safetynet, banking apps, xiaomi account and cloud work?
Edit:
I am not sure if the steps are correct and which beryllium2dipper-patch.zip patch file I should use
To begin with, the steps are not difficult. we have to flash the following files:
--> system.img, cust.img (system_ext), vendor.img (the patched one), boot.img
as images from a recovery which supports cust images, such as OrangeFox.
--> DFE (disable forced encryption), the latest stable patch, permissiver and XD kernel as .zip files
--> base.apk is Mi Video if someone wants to install the provided version and not this from Play Store, APKmirror etc..
(?)> If the ROM is not bootable, we have to make sure the previous ROM was not encrypted or /data is formatted.
(?)> And, of course, we also need to have the latest firmware from Xiaomi (Global/China)
Moreover, the bugs are the same: NFC, perhaps AOD (some developers have removed it on Poco, on Ignition 2.0 there is AOD support) and Dual GPS (but normal GPS works normally). Only these.
When it comes to Ignition 4.0, both are nice. Personally, I would choose the first version of Ignition 4.0 (not the reuploaded one), which is probably more stable.
Last but not least, it is likely that these ROM's can be ported to other devices, such as Mi Mix 3 (similar device), in case a suitable kernel is found and the correct proprietary files are replaced (usually, by testing).
Advanced Gears said:
To begin with, the steps are not difficult. we have to flash the following files:
--> system.img, cust.img (system_ext), vendor.img (the patched one), boot.img
as images from a recovery which supports cust images, such as OrangeFox.
--> DFE (disable forced encryption), the latest stable patch, permissiver and XD kernel as .zip files
--> base.apk is Mi Video if someone wants to install the provided version and not this from Play Store, APKmirror etc..
(?)> If the ROM is not bootable, we have to make sure the previous ROM was not encrypted or /data is formatted.
(?)> And, of course, we also need to have the latest firmware from Xiaomi (Global/China)
Moreover, the bugs are the same: NFC, perhaps AOD (some developers have removed it on Poco, on Ignition 2.0 there is AOD support) and Dual GPS (but normal GPS works normally). Only these.
When it comes to Ignition 4.0, both are nice. Personally, I would choose the first version of Ignition 4.0 (not the reuploaded one), which is probably more stable.
Last but not least, it is likely that these ROM's can be ported to other devices, such as Mi Mix 3 (similar device), in case a suitable kernel is found and the correct proprietary files are replaced (usually, by testing).
Click to expand...
Click to collapse
Thanks for the explanation, I have flashed successfully with minor tweaks.
To resume:-
Prerequisites:
1. MIUI13 Android 12 firmware (POCO OS IGNITION 2.0) feels more responsive
2. Phone ROM with unlocked bootloader and OrangeFox recovery.
3. Phone ROM must be on latest Official ROM (Global/China)
4. Phone ROM must not encypted or /data formatted
Boot to OrangeFox recovery:
1. Flash .img files; system.img, cust.img (system_ext), vendor.img, boot.img (POCO OS IGNITION 2.0)
2. Flash .zip files; DFE (disable forced encryption), latest stable beryllium2dipper-patch, permissive and XD kernel
3. Reboot phone to system and enjoy
Edit:
I have reverted back to my old ROM (xiaomi.eu MIUI12.5} as I feel its more polished and optimised but its nice to see Android 12 with MIUI13 fully working ported to the Mi 8.